After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 365405 - Crash when umounting an NFS share
Crash when umounting an NFS share
Status: RESOLVED FIXED
Product: gamin
Classification: Other
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Gamin Maintainer(s)
Gamin Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-10-26 19:27 UTC by Sebastien Bacher
Modified: 2006-10-27 12:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Sebastien Bacher 2006-10-26 19:27:32 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/gamin/+bug/63476

"I had an NFS share mounted. When I umounted it, I got the crash in question. An attachment is forthcoming.
...
Package: gamin 0.1.7-3ubuntu2
...
--- stack trace ---
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Core was generated by `/usr/lib/gamin/gam_server'.
Program terminated with signal 6, Aborted.
  • #0 __kernel_vsyscall
  • #0 __kernel_vsyscall
  • #1 __open_catalog
    from /lib/tls/i686/cmov/libc.so.6
  • #2 __sigpause
    from /lib/tls/i686/cmov/libc.so.6
  • #3 IA__g_assert_warning
    at gmessages.c line 552
  • #4 IA__g_assert_warning
    at gmessages.c line 561
  • #5 IA__g_log_remove_handler
    at gmessages.c line 352
  • #6 gam_inotify_remove_subscription
    at gam_inotify.c line 875
  • #7 gam_kernel_remove_subscription
    at gam_server.c line 445
  • #8 gam_remove_subscription
    at gam_server.c line 249
  • #9 gam_connection_request
    at gam_connection.c line 387
  • #10 gam_connection_data
    at gam_connection.c line 490
  • #11 gam_client_conn_read
    at gam_channel.c line 270

Comment 1 Daniel Holbach 2006-10-27 10:54:41 UTC
http://librarian.launchpad.net/4938120/_usr_lib_gamin_gam_server.1012.crash has another (quite similar) backtrace.
Comment 2 Daniel Veillard 2006-10-27 12:58:06 UTC
Can you try the CVS version if you have a reproduceable test case. The
inotify module got some serious fixes in the last couple of months. I
should actually do  a release, but if the problem is still present and
you think you can come up with a fix reasonably quickly then it makes 
sense to wait for the release.

Daniel