Ubuntu

Nautilus in Lucid Lynx Samba could not display network location dbus error gvfsd-smb-browse

Reported by Yfrwlf on 2010-04-11
82
This bug affects 15 people
Affects Status Importance Assigned to Milestone
libgnome-keyring (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: udisks

I'm not sure how to reproduce this bug, but try the following: mount a SMB share, unmount it, try to mount it again, try dragging it into the left pane or quick places section and then unmounting and remounting by clicking on it. I would run into the following error several times on different computers and different networks, and once it happens I'm not sure how to stop it, even rebooting did not work in one case so far.

The error:

Could not display "smb://the/server/and/share".
Error: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Please select another viewer and try again.

Yfrwlf (yfrwlf) wrote :

I also will sometimes get, "Sorry, the program gvfsd-smb-browse" closed unexpectedly, but it is not able to send the report. I get:

The problem cannot be reported:
The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes.

summary: Nautilus in Lucid Lynx Samba could not display network location dbus
- error
+ error gvfsd-smb-browse
Yfrwlf (yfrwlf) wrote :

I have now reproduced this bug.

Steps:
1) Mount a SMB share. In my case, the share required a password, and I told it to save until logged out.
2) Unmount that share.
3) Attempt to remount that share.

I then tried accessing other shares on the same and other computers on the same network and was unable to do so and got the following error:

Unable to mount location
DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

Yfrwlf (yfrwlf) wrote :

I tried logging out and back in, and could then remount the same share.

In the case mentioned above where I tried rebooting on a computer and that did not help, I had told it to save the password indefinitely.

This means that this issue is somehow related to whether or not the password for a share has been saved previously.

I'm really surprised if I'm the only one to have reported this yet if I am as this bug has been in Lucid for a while now and seems like quite a major bug given that SMB is the default method for file sharing via the Gnome GUI.

affects: udisks (Ubuntu) → gvfs (Ubuntu)
Changed in gvfs (Ubuntu):
importance: Undecided → Low
Yfrwlf (yfrwlf) wrote :

And what's your justification for it being of low importance? How can you determine that when this isn't even confirmed yet? Or are you just trying to be a jerk because I said I thought it was of high importance?

Yfrwlf (yfrwlf) on 2010-04-13
Changed in gvfs (Ubuntu):
status: New → Fix Released
Yfrwlf (yfrwlf) wrote :

I just tested this inside VirtualBox with the daily build 2010-04-13 and upon trying to access a network share, after putting in the credentials for it and selecting remember until I logout, I was presented the the errors once again.

Attaching a picture.

Is there anyone else out there who can confirm this?

Changed in gvfs (Ubuntu):
status: Fix Released → New
Yfrwlf (yfrwlf) wrote :

Strangely enough I'm not getting this on my main machine which was installed with an older build and then updated. Perhaps it's only effecting the fresh installs at the moment?

Sebastien Bacher (seb128) wrote :

the justification is that the bug is not at crasher or a security issue and that it has no duplicate or other affect users right now

Sebastien Bacher (seb128) wrote :

Could you try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem?

(the second comment indicates a crash, you might also want to get the stacktrace from the .crash file locally)

Sebastien Bacher (seb128) wrote :

you can read https://wiki.ubuntu.com/MozillaTeam/Bugs/Triage/Responses#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20%28using%20gdb%29 to get details on how to get the stacktrace, you need to adapt it to gvfs rather than firefox though

balait (balait) wrote :

I also got the same problem. This is new install of Lucid Lynx 64bit. updated to date.

When I save the password to remember, I got the DBUS error in the next time.

If I remove the password entry in the "Passwords and Encryption Keys", & try to open samba share it is asking for the password & work.

For the upgraded "Lucid Lynx", remember password work without any problem.

balait (balait) wrote :

For the new install of "Lucid Lynx" with remember password for samba share browsing, it is reproducible.

Changed in gvfs (Ubuntu):
status: New → Confirmed
Landon Cheek (lcheek) wrote :

This is also an issue for me.

An additional note to make is that I get this error even after deleting the remembered credentials from the keyring.

Walter_Wittel (wittelw) wrote :
Download full text (4.0 KiB)

I'm on a fairly disk / resource constrained machine but installed apport-retrace and got the following stack trace (Lucid with an update just this evening) from _usr_lib_gvfs_gvfsd-smb.1000.crash:

--- stack trace ---
#0 0x00944422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x00712641 in raise () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x00715a72 in abort () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#3 0x00680dd3 in g_assertion_message () from /lib/libglib-2.0.so.0
No symbol table info available.
#4 0x0068142d in g_assertion_message_expr () from /lib/libglib-2.0.so.0
No symbol table info available.
#5 0x00a08802 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#6 0x00a07b55 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#7 0x00a088fc in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#8 0x00a095b1 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#9 0x00a11a16 in gnome_keyring_set_network_password_sync () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#10 0x080647cd in ?? ()
No symbol table info available.
#11 0x08052696 in ?? ()
No symbol table info available.
#12 0x08059b68 in ?? ()
No symbol table info available.
#13 0x080589fd in ?? ()
No symbol table info available.
#14 0x0805476e in ?? ()
No symbol table info available.
#15 0x00685cec in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#16 0x00683dcf in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#17 0x0060a96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#18 0x007b59de in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
--- source code stack trace ---
#0 0x00944422 in __kernel_vsyscall ()
#1 0x00712641 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0x00715a72 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0x00680dd3 in g_assertion_message () from /lib/libglib-2.0.so.0
#4 0x0068142d in g_assertion_message_expr () from /lib/libglib-2.0.so.0
#5 0x00a08802 in ?? () from /usr/lib/libgnome-keyring.so.0
#6 0x00a07b55 in ?? () from /usr/lib/libgnome-keyring.so.0
#7 0x00a088fc in ?? () from /usr/lib/libgnome-keyring.so.0
#8 0x00a095b1 in ?? () from /usr/lib/libgnome-keyring.so.0
#9 0x00a11a16 in gnome_keyring_set_network_password_sync () from /usr/lib/libgnome-keyring.so.0
#10 0x080647cd in ?? ()
#11 0x08052696 in ?? ()
#12 0x08059b68 in ?? ()
#13 0x080589fd in ?? ()
#14 0x0805476e in ?? ()
#15 0x00685cec in ?? () from /lib/libglib-2.0.so.0
#16 0x00683dcf in ?? () from /lib/libglib-2.0.so.0
#17 0x0060a96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#18 0x007b59de in clone () from /lib/tls/i686/cmov/libc.so.6

I have a feeling I didn't use the correct parameters to pull down the proper symbols, or maybe I don't have space, but it does show the shared objects on the stack which may help.

I also got the following trace from _usr_lib_gvfs_gvfsd-smb-browse.1000.crash:
--- source code stack trace ---
#0 0x00172422 in __kernel_vsyscall ()
#1 0x008a7641 in ...

Read more...

Sebastien Bacher (seb128) wrote :

could you install libgnome-keyring0-dbgsym and libglib2.0-0-dbg and get a new stracktrace? it seems a libgnome-keyring issue

affects: gvfs (Ubuntu) → libgnome-keyring (Ubuntu)
Walter_Wittel (wittelw) wrote :
Download full text (3.7 KiB)

Unfortunately I could not find libgnome-keyring0-dbgsym in the repository. I was able to install libglib2.0-0-dbg and it provided a bit more information (below). Also I noticed that my installed version of libgnome-keyring0 is 2.30.0-0ubuntu3 but the latest version is 2.30.0-0ubuntu4.

If you can point me to where I can get the 2.30.0-0ubuntu3 version debug symbols I can try the retrace again after work tomorrow. Otherwise I can try the newer version of libgnome-keyring0 and repro the crash (easy), but I didn't see debug symbols for that version either.

--- stack trace ---
#0 0x00944422 in __kernel_vsyscall ()
No symbol table info available.
#1 0x00712641 in raise () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x00715a72 in abort () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#3 0x00680dd3 in IA__g_assertion_message (domain=0x0,
    file=0xa185f4 "gkr-operation.c", line=169,
    func=0xa18967 "gkr_operation_set_result",
    message=0x97f3590 "assertion failed: ((int) res != INCOMPLETE)")
    at /build/buildd/glib2.0-2.24.0/glib/gtestutils.c:1318
        lstr = "169\000\272\065\177\t+\245j\000\364\217\235\000\317\070\240\000\005\000\000\000\200_g\267\266\246\234"
        s = <value optimized out>
#4 0x0068142d in IA__g_assertion_message_expr (domain=0x0,
    file=0xa185f4 "gkr-operation.c", line=169,
    func=0xa18967 "gkr_operation_set_result",
    expr=0xa18633 "(int) res != INCOMPLETE")
    at /build/buildd/glib2.0-2.24.0/glib/gtestutils.c:1329
No locals.
#5 0x00a08802 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#6 0x00a07b55 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#7 0x00a088fc in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#8 0x00a095b1 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#9 0x00a11a16 in gnome_keyring_set_network_password_sync ()
   from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#10 0x080647cd in ?? ()
No symbol table info available.
#11 0x08052696 in ?? ()
No symbol table info available.
#12 0x08059b68 in ?? ()
No symbol table info available.
#13 0x080589fd in ?? ()
No symbol table info available.
#14 0x0805476e in ?? ()
No symbol table info available.
#15 0x00685cec in g_thread_pool_thread_proxy (data=0x97815f0)
    at /build/buildd/glib2.0-2.24.0/glib/gthreadpool.c:315
        task = 0x0
        pool = 0xffffffff
#16 0x00683dcf in g_thread_create_proxy (data=0x9789a50)
    at /build/buildd/glib2.0-2.24.0/glib/gthread.c:1893
        __PRETTY_FUNCTION__ = "g_thread_create_proxy"
#17 0x0060a96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#18 0x007b59de in clone () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
--- source code stack trace ---
#0 0x00944422 in __kernel_vsyscall ()
#1 0x00712641 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0x00715a72 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0x00680dd3 in IA__g_assertion_message (domain=0x0,
#4 0x0068142d in IA__g_assertion_message_expr (domain=0x0,
#5 0x00a08802 in ?? () from /usr/lib...

Read more...

Sebastien Bacher (seb128) wrote :

Did you add the ddeb source as indicated on http://wiki.ubuntu.com/DebuggingProgramCrash to get the debug binaries?

Walter_Wittel (wittelw) wrote :

Thanks Sebastien. I don't do this often enough to remember the details and that link provided the debug symbols. I've attached a much more informative trace. Hope it helps.

Stef Walter (stefw) wrote :

Sadly it looks like that last stack trace, the symbols or source somehow don't match the actual binary....

Likely update manager. Thought there would be a complaint on mismatch. I
should be able to repro and will verify versions match first.

On Apr 21, 2010 10:10 AM, "Stef Walter" <email address hidden> wrote:

Sadly it looks like that last stack trace, the symbols or source somehow
don't match the actual binary....

-- Nautilus in Lucid Lynx Samba could not display network location dbus
error gvfsd-smb-browse htt...

Walter_Wittel (wittelw) wrote :

I am unable to reproduce the crash (even with apport enabled) with the newer version:

libgnome-keyring0:
  Installed: 2.30.0-0ubuntu4
  Candidate: 2.30.0-0ubuntu4
  Version table:
 *** 2.30.0-0ubuntu4 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

I turned off the firewall and was able to browse and open a share one of my Windows machines successfully (first time I've seen this on Lucid). I turned the firewall back on and got error dialogs trying to browse to the Windows network / machine but no crashes. After a reboot the particular Windows machine that has valid shares doesn't show up at all when I browse and if I try to browse a share I set up on the Ubuntu box I'm testing I get a password dialog but can never connect using the account credentials used to set up the share.

Very frustrating. If you have some ideas of what to look for or try please let me know.

Walter_Wittel (wittelw) wrote :

Wasn't clear on a couple of points (late night after a long day at work bad combo).

I'm using Firestarter (not Ubuntu officially supported) to control the firewall, but it has worked OK for me in the past with SMB (and have that enabled in the exceptions). Maybe there is some bad interaction in Lucid.

I can't browse to the machine in question (much less connect with any shares) with the firewall on or off, even after reboots. Was never able to get it into a working state.

Walter_Wittel (wittelw) wrote :

Status for this machine: Following the next two updates I am able to log onto workgroup shares on my Windows machine just fine (as long as the firewall is off). No crashes with the firewall on or off.

I can't open shares on this machine (shared from Nautilus) from either this machine or a Windows machine. I've tried all the possible sharing combinations. However that would be a separate bug. I'll try to look for it / dupes once Lucid releases. Thanks for your help on this.

fineconn (fineconn) wrote :

Maybe I found something! At least this works for me..!?

Select Applications|Accessories|Passwords and encryption keys. Then in the Passwords tab, delete the entry containing your smb share (in my case this was paul@uranium). Then close the Passwords and encryption keys application and open Nautilus. Delete any bookmarks that point to your share and close Nautilus. Reboot your PC (I'm not sure that this step is necessary). After the reboot, launch Nautilus again and hit Ctlr-L. Enter the path to your smb share following this format "smb://192.168.3.253/paul/" (192.168.3.253 is the IPaddress of my samba server uranium) and enter your smb password. Tell the system to save the password permanently and add a bookmark for your share. Following these steps you can also mount more shares. After a reboot I can simply click the bookmark and open the smb share. This is of course not the solution but only a workaround.

schuelaw (schuelaw) wrote :

fineconn, I have this bug on a clean 10.04 32-bit install, your workaround works for me too, thanks. I confirm that a reboot is required (or at least a logout and login).

schuelaw (schuelaw) wrote :

Doing this again on a second 32-bit install and now I can't get the above to work. I have no idea what's different, but it would be great to track this down. It seems to be a bug in the keyring manager, but that's only a guess.

schuelaw (schuelaw) wrote :

As a followup, I can mount the shares automatically on boot if I put an entry in fstab, but that's not desirable when the laptop is out of the network containing the samba shares. Better if I can get nautilus bookmarks for them and only mount them when I know they're available. Thanks,

PM (pm77) wrote :

I can confirm that problem persist on my computer, like reported earlier. This is an up-to-date Ubuntu Lucid.

On the other hand, I have another computer which has Lucid installed from the same CD, and does not have this problem. They are both in the same network, trying to connect to the same share.

I really hope that someone can make an effort to solve this problem. I can help with debugging, but need guidance.

Patrick (wushumasters) wrote :

The same problem to me with 10.04 32 bits & 64 bits

I think this bug should have a High importance, not low.

Changed in libgnome-keyring (Ubuntu):
assignee: nobody → Patrick (wushumasters)
Patrick (wushumasters) on 2010-06-22
Changed in libgnome-keyring (Ubuntu):
assignee: Patrick (wushumasters) → nobody
Yfrwlf (yfrwlf) wrote :

I'm no longer finding any of these problems with Ubuntu 10.10. I was able to unmount and remount SMB network shares in all the random ways I tried, with making shortcuts to subfolders on the share and clicking on those to mount the share and anything else I could think of doing, and can't reproduce this issue now.

Guess Ubuntu 10.04 will need a patch backported, or something will have to be upgraded to the version 10.10 is using?

This bug is still present in Ubuntu 10.04 LTS (Long Time Support), to which I stick for very good reasons and which makes me experience the bug at hand daily. Any hope of seeing a patch backported to LTS? Thanx in advance

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers