[Bug 282298] Re: Intrepid Beta: No Access to NAS samba share any more.

2008-10-25 Thread Robert Garshaw
I am plagued with exactly the same problem. I can can see the shares but they are empty, I can read and write to them (blindly) but nautilus doesn't list any files. I think this has something to do with the server version, I'm also running an older samba server (a freesco router) with version

[Bug 282298] Re: Intrepid Beta: No Access to NAS samba share any more.

2008-10-25 Thread Robert Garshaw
Forgot to say, this is on a box upgraded to intrepid and current with updates (so rc atm). I tried the shares yesterday with the livecd and had the same problem. -- Intrepid Beta: No Access to NAS samba share any more. https://bugs.launchpad.net/bugs/282298 You received this bug notification

[Bug 282298] Re: Intrepid Beta: No Access to NAS samba share any more.

2008-10-26 Thread Robert Garshaw
At the moment it's giving me the Transport endpoint is not connected message when I try to cd into .gvfs but previously I could do an ls and see the shares listed. But when I cd into one I got an error message and the share disappeared. The same as you I believe. I'm out of my depth here but

[Bug 282298] Re: Intrepid Beta: No Access to NAS samba share any more.

2008-10-29 Thread Robert Garshaw
Hi, I don't think anybody here has a problem with accessing the shares normally like that. I can mount them with smbmount //server/share /mountpoint just fine. The problem seems to just lie with gvfs so traditional access is unaffected. What version is the samba server you are connecting to? So

[Bug 282298] Re: Intrepid Beta: No Access to NAS samba share any more.

2008-11-02 Thread Robert Garshaw
Is anyone here willing to have a go at compiling samba with that smbclient patch (see the debian bug)? I might do it if I can't find a new deb with it in. -- Intrepid Beta: No Access to NAS samba share any more. https://bugs.launchpad.net/bugs/282298 You received this bug notification because

[Bug 594567] [NEW] Can't change desktop resolution when no monitors are connected.

2010-06-15 Thread Robert Garshaw
Public bug reported: Running up to date lucid: On a system with no monitor connected gnome-display-properties does not allow you to change the resolution. For example, when using the system remotely via vnc. ** Affects: control-center (Ubuntu) Importance: Undecided Status: New --

[Bug 594567] Re: Can't change desktop resolution when no monitors are connected.

2010-06-15 Thread Robert Garshaw
To reproduce: Unplug any monitors and connect to the computer via vnc (or similar) and try to change the desktop resolution. All inputs in gnome-display-properties are disabled. -- Can't change desktop resolution when no monitors are connected. https://bugs.launchpad.net/bugs/594567 You