Another mediacenter crash, reassigning.

Odd. Debian 3.1 here as well but if I follow your steps it says "You need to 
enter a server name". No crash.

Have you updated your system recently?

Umm... probably I DID enter the server name, but left out the user name. Yes,
the system was an up-to-date Debian sarge, freshly installed only a few days
before. In the meantime, I have installed gnome 2.10 from Debian experimental
instead. There, I get a dialog box asking for username and password. It still
doesn't work, though. The best I have managed so far:
1. Enter server name and user name into dialog box, select "Secure WebDAV",
click connect
2. Enter password in the next dialog box, click ok.
3. I get an error message: "Couldn't find "davs://570614@mediacenter.gmx.net".
Please check the spelling and try again."
4. Still, a mediacenter mount icon is generated on the Desktop. I doubleclick it.
5. A window that displays the contents of my WebDAV share is openened. One of
the folders inside my share has a mangled name ("?" instead of umlaut) and there
is (Invalid Unicode) in brackets after the name.
6. After a second or two with no action on my part, "The Application "nautilus"
has quit unexpectedly." appears. Should I file another bug for that?

Sometimes, maybe if a share is already "mounted" on the desktop, it dies erlier,
e.g. during user/pass dialogs, or there was another error message "Cannot
display ..." once or twice. :-/

NB, this is now gnome 2.10 from Debian experimental, the version of the Debian
package libgnome-vfs0 is 1.0.5-5.2

Sebastian, thanks for your efforts but one problem at a time please.

Open a second report about your Gnome 2.10 problems. Please tell me the new bug 
number since i can confirm the issues partly.

>Umm... probably I DID enter the server name, but left out the user name.
Still no crash here. It would be very helpful if you can give us steps on how to 
reproduce the crash and/or it would be very helpful if you get get us a stack 
trace with debugging symbols. Please see 
http://bugzilla.gnome.org/getting-traces.cgi for more information about getting 
a useful stack trace.

any news on this bug?

I just tried to reproduce it another time with Gnome 2.10. I get a completely
different error. Probably something broke in my Debian setup in the meantime,
since it seems the davs://-URI no longer is handled correctly.

My steps in trying to reproduce the bug:

Click "Places/Connect To Server..."

Enter:
Service type: WebDAV (HTTP)
Server: mediacenter.gmx.net
User Name: 570614
Name to use for connection: mc

Click Connect.

Enter password in password dialog.

Result:
'Can't display location "dav://570614@mediacenter.gmx.net"

There is no default action associated with this location.'


If you can tell me what's wrong with the "default action", I can take a look
into the real bug :-/.

Thanks for caring about it.

Works fine here but I compiled Gome 2.10 on my own.

Lookslike your associated actions got borked up.

what happens if you create a new user and try these steps?

Also: if it is 2.10 it must be Debian unstable !? I'd claim that if this 
problems persists even with a pristine user account it is a packaging problem.

The problem with the action handler (where are they registered? Where can I
inspect or change them? There seems to be no UI for "default actions"...) went
away after a reboot. Maybe the problem was a Debian upgrade I had done in the
running session - I hadn't logged out for a few days. Yes, I'm running unstable,
which as of late has become rather tricky to maintain usable (shouldn't have
upgraded right now).

Anyway, in a regular gnome session, I still get the same error - a spontaneous
segfault a few seconds AFTER the window showing the contents of the webdav share
has been created. Maybe there is heap corruption and another thread stumbles
over it?

I tried running Nautilus with the valgrind memory checker tool, but it bailed
out very soon with multiple segfaults. valgrind also reports an unhandled
syscall, that might be the problem.

When I start Nautilus with the electric-fence malloc-debugging-library
LD_PRELOADED, there is a problem with corba and no Nautilus window appears.
Strange, I would have thought that libefence it should not influence a program's
behaviour at all; maybe it has problems with mmap or other means of VM
manipulation than malloc (new) / free (delete).

I tried to install debugging libraries, libc6-dbg and libgnomevfs2-0-dbg from
Debian. Adding /usr/lib/debug to my LD_LIBRARY_PATH correctly causes the
libc6-dbg libraries to be used (verified with ldd). For the libgnomevfs2-0-dbg
libraries, the path (maybe by mistake?) is /usr/lib/debug/usr/lib. There is no
libgnomevfs-2.so.0 link there (which, ldd shows me, is the file the dynamic
linker looks for), so I created one. After adding the link, when using
/usr/lib/debug:/usr/lib/debug/usr/lib as the LD_LIBRARY_PATH, I get the
following error:

nautilus: error while loading shared libraries: libgnomevfs-2.so.0: object file
has no dynamic section

The libgnomevfs2-0-dbg (2.10.1-5) package seems to be rather broken.

Another approach I took in order to narrow down the problem (and then maybe use
valgrind/libefence) was to run a standalone nautilus in a non-gnome (fluxbox)
environment with the following command:

nautilus --no-desktop --no-default-window davs://570614@mediacenter.gmx.net

This asks for my password (so it has a connection to the server), but then fails
with an error message titled "Can't Display Location", and the text 'Couldn't
find "davs://570614@mediacenter.gmx.net". Please check the spelling and try
again.'. Simulataneously, it opens a nautilus window showing $HOME.  Might this
be an unrelated bug?

So, what should I do next?

I believe I have misinterpreted how to use the debugging libraries - they seem
to be used automagically by gdb, even if only the normal libraries are
dynamically linked. I ran nautilus another time, got it to crash another time by
double-clicking on the icon labelled mc on my desktop and entering a password.
(I didn't even move the mouse in the period between the appearance of the webdav
share's window and the appearance of the crash window).

Then I got the following improved stack trace from bug buddy:
Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225255776 (LWP 6842)]
[New Thread -1237455952 (LWP 6856)]
[New Thread -1237111888 (LWP 6855)]
[New Thread -1236849744 (LWP 6854)]
[New Thread -1236370512 (LWP 6851)]
[New Thread -1227719760 (LWP 6843)]
(no debugging symbols found)
(no debugging symbols found)
0xb7bc8561 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 61850

Well, you are supposed to quit Gnome when updating anyway.
By the way, the last stack trace is *excellent* ! Is is Gnome 2.10
and you have upgraded meanwhile while the report is till tagged Nautilus 2.8.3

I will attach the trace to Bug 304736 which matches the stack trace you have  
just given.

We have to focus on _one problem at a time per report_ . So please stay talking 
about Gnome 2.8.3 here. Go to Bug 304736 for the problems you are currently 
facing. I am adding you to the CC: list there .

I'll mark this report INCOMPLETE. Feel free to install Gnome 2.8.3 and reopen 
this report so we can attempt to settle the issue concerning Gnome 2.8 . Thanks.

I'm afraid I cannot reproduce the Gnome 2.8 bugs any more, since I've upgraded
to Gnome 2.10, and a Debian downgrade isn't really that much fun.

Thanks for adding me to the cc.