"Shared folders" incorrect free()

Sorry, I wasn't more specific, with regards to error messages. Plum forgot! Here
goes.

When running
gskudo shares-admin

I get:
 (shares-admin:12821): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified
are supported and host-based authentication failed.
- using device duplex
- using device duplex
Audio device open for 44.1Khz, stereo, 16bit failed
Trying 44.1Khz, 8bit stereo.
Audio device open for 44.1Khz, stereo, 8bit failed
Trying 48Khz, 16bit stereo.
*** glibc detected *** double free or corruption (fasttop): 0x08289638 ***

This message is in reference to forum post
http://www.ubuntuforums.org/showthread.php?t=77086&highlight=shares-admin

Having the same problem here. I tried to set up a folder for sharing and then
when I tried to come back to the Shared Folders dialog box to edit the settings,
I got the round cursor problem. I tried to completely uninstall samba and NFS
from synaptic and reinstall them thinking that may have been part of the problem
but it didn't work. I then tried to launch shares-admin from the terminal using
"sudo shares-admin" and it gave me this error message:

*** glibc detected *** double free or corruption (fasttop): 0x08289638 ***

Please help,
Thank you.

Thanks for your bug report. Which version of Ubuntu and gnome-system-tools do
you use?

(In reply to comment #3)
> Thanks for your bug report. Which version of Ubuntu and gnome-system-tools do
> you use?

Breezy. (Hoary didn't have this feature, I think)
gnome-system-tools version 1.4.0-0ubuntu10.

- Ketil

(shares-admin:18590): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified
are supported and host-based authentication failed.
*** glibc detected *** double free or corruption (fasttop): 0x0822a020 ***

Is anyone actually looking at this?
Or should we expect to see the same bug in Dapper?
Some info would be cool!

Does anyone need more info to bugtrack this? I'm right here :)

I can't imagine that this can't be reset. I just want to set the whole thing to default values, and see what happens.

At <http://bugzilla.ubuntu.com/show_bug.cgi?id=20008> someone put in a new comment today.
1. Shouldn't this be posted here? How was this even possible to post?
2. Why doesn't the comment show up here?

- Ketil

I believe I've found a workaround. (More like a fix if you are experiencing this problem)
Open synaptic and mark gnome-system-tools and system-tools-backend for complete removal. While you're at it you could do the same to samba-packages (remember that this will remove your smb.conf).
Reboot your system (tried without reboot, which didn't work)
Do a fresh install of gnome-system-tools and system-tools-backend (and samba-packages too, if you removed them)
Close Synaptic.
Open shares-admin.
However, it still seems highly unstable, I am in the process of doing this whole thing once more right now.
I'm guessing package system-tools-backends is the culprit.

*Please* fix this before Dapper!

- Ketil

Now, this time, it didn't work.
What a useless app! This has got to be the most unstable set of packages yet.

- Ketil

I'd be very happy if somebody could double check with recent Dapper, because it works fo me.

And something about the tone: it doesn't really encourage to actually look at the bug. Remember everybody you want this to be looked at are people: the bug triagers, the package maintainers and the authors of the software.

Daniel Holbach: Are you using Dapper or Breezy?

About the tone:
I am not a rude person, and reading my posts, the only thing that might be not so polite was when I wrote "What a useless app!" And, to me, it is. It is supposed to do more or less 2 things: admin stuff for NFS and Samba. For me, it does neither.

If somebody was/is looking at it, it would be cool if he/she posted some info here, and someone else might have some clues. But there has been nothing, which dissapointed me. (Especially since I had to fight my way through smb.conf manually, in order to get Samba to work.)

However, if anyone was/is offended, I'm sorry.

Hope it works in Dapper - also for me!

- Ketil

We are sometime not happy with some software and bugs, but we ship the best alternative we find to do the job. Knowing that most upstream do that for free out of their job, and than the number of package maintained by people is not that low we are in a position where fixing some bugs takes time, especially if the bug depends on having some special configuration (there is quite some people working under linux and not having a smb configuration between different machines to play with that). Remark like "What a useless app! This has got to be the most unstable set of packages yet." might be true, they don't motivate people working on something for free to continue their work ... I know if kind be frustrating but better to work with people to make softwares better!

Bad news: The Shared Folder applet showed the same problems when I upgraded to Dapper (from Breezy of course).

I suspect this may be because you *upgraded*. Anyone with a clean Dapper install and the same problem?

- Ketil

I'm sure that upgrading is no problem at all.

The upgrade itself was not the problem (although it went with some problems...).
The problem was before and after the upgrade.

Upgrading may not show the full nature of this problem, because the configuation files to the affected packages may not be fully replaced.

So, I ask again, anyone with a clean install of Dapper, which displays this problem?

- Ketil

Could you get a valgrind log? Install the "valgrind" package and use "sudo valgrind shares-admin", it should make the application really slow to start but point some issues you may have, especially was is creating the "*** glibc detected *** double free or corruption (fasttop): 0x08289638 ***" you copied to your first comment

How do I output the result in a txt-file? It's too long, and the top is removed when it gets to the end.
Weird thing is, doing sudo valgrind shares-admin actually makes the app work right, at least it seems so.

- Ketil

you can use the valgrind --log-file= option for that

See comment in the end.

Here's the log:

==9561== Memcheck, a memory error detector.
==9561== Copyright (C) 2002-2005, and GNU GPL'd, by Julian Seward et al.
==9561== Using LibVEX rev 1367, a library for dynamic binary translation.
==9561== Copyright (C) 2004-2005, and GNU GPL'd, by OpenWorks LLP.
==9561== Using valgrind-3.0.1, a dynamic binary instrumentation framework.
==9561== Copyright (C) 2000-2005, and GNU GPL'd, by Julian Seward et al.
==9561==
==9561== My PID = 9561, parent PID = 9520. Prog and args are:
==9561== shares-admin
==9561== For more details, rerun with: -v
==9561==
==9561== Conditional jump or move depends on uninitialised value(s)
==9561== at 0x1B8F40FD: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E9DBA: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E484D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8EE875: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E491C: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E7421: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8F1A6D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E4D0E: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E47C6: (within /lib/ld-2.3.5.so)
==9561==
==9561== Conditional jump or move depends on uninitialised value(s)
==9561== at 0x1B8F410C: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E9DBA: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E484D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8EE875: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E491C: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E7421: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8F1A6D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E4D0E: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E47C6: (within /lib/ld-2.3.5.so)
==9561==
==9561== Conditional jump or move depends on uninitialised value(s)
==9561== at 0x1B8F411B: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E9DBA: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E484D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8EE875: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E491C: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E7421: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8F1A6D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E4D0E: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E47C6: (within /lib/ld-2.3.5.so)
==9561==
==9561== Conditional jump or move depends on uninitialised value(s)
==9561== at 0x1B8F4126: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E9DBA: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E484D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8EE875: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E491C: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E7421: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8F1A6D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E4D0E: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E47C6: (within /lib/ld-2.3.5.so)
==9561==
==9561== Conditional jump or move depends on uninitialised value(s)
==9561== at 0x1B8F4263: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E9DBA: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E484D: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8EE875: (within /lib/ld-2.3.5.so)
==9561== by 0x1B8E491C: (within /li...

Sorry for posting the log twice, can someone please delete half of it, if that's possible?

- Ketil

Thank you for the log, no we can't edit a commnet like that but don't worry that's not an issue. You log point an issue:

==9561== Invalid free() / delete / delete[]
==9561== at 0x1B8FF44F: free (vg_replace_malloc.c:235)
==9561== by 0x1C166053: g_free (in /usr/lib/libglib-2.0.so.0.800.3)
==9561== by 0x8050A88: gst_share_nfs_new_from_xml (in /usr/bin/shares-admin)
==9561== by 0x8051286: table_add_share_from_node (in /usr/bin/shares-admin)
==9561== by 0x80517A2: transfer_xml_to_gui (in /usr/bin/shares-admin)

Maybe you could do a debug build of gnome-system-tools package (https://wiki.ubuntu.com/DebuggingProgramCrash) to get the lines number to the log?

Itś been a while, but i found a good workaround. Use Synaptic to remove the package "nfs-kernel-server". Be sure you do a Complete removal including the config files.
After that, reinstall the same package and you're done. It worked in my case anyway.
As this worked, I suspect there is something wrong in a configuration file.

I hate to say this, but I have the same issue using Dapper. I am now doing a clean install of Dapper to see if it will repeat. The copy I'm using was not an upgrade from Breezy, but a new install. Results from 'sudo shares-admin':
*** glibc detected *** double free or corruption (fasttop): 0x082e5b40 ***

Will post whatever is needed to try to solve this, just let me know.

Confirmed by popular vote.

I've forwarded the issue upstream: http://bugzilla.gnome.org/show_bug.cgi?id=343200

Fixed for dapper:

 gnome-system-tools (2.14.0-0ubuntu10) dapper; urgency=low
 .
   * debian/patches/07_fix_share_incorrect_free.dpatch:
     - fix incorrect g_free call and a crasher due to it (Ubuntu: #26117)

So is it fixed for dapper? What is the fix? How do I get my hands on it because this site is of no use when it comews tp pointing what the fix is. I am using dapper and have this problem. A file to download? Terminal commands? What???????????????????????????????????

what version of gnome-system-tools is installed? just update the package using update-manager (or the "updates" systray icon). No need to use a zillion of "?" it will only bother people and they will not reply to your comment