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 587555 - Crash on disk full
Crash on disk full
Status: RESOLVED DUPLICATE of bug 322541
Product: f-spot
Classification: Other
Component: Import
0.5.x
Other All
: Normal critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
: 587556 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-01 20:16 UTC by mahfiaz
Modified: 2009-07-02 12:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mahfiaz 2009-07-01 20:16:37 UTC
Steps to reproduce:
f-spot gives no error on "no space left on device" but crashes instead, an error with resume option on import needed


Stack trace:

f-spot

** (/usr/lib/f-spot/f-spot.exe:3883): CRITICAL **: _wapi_shm_file_open: shared file [/home/mattias/.wapi/shared_data-ront-Linux-x86_64-328-12-0] write error: No space left on device

** (/usr/lib/f-spot/f-spot.exe:3883): CRITICAL **: _wapi_shm_attach: shared file [/home/mattias/.wapi/shared_data-ront-Linux-x86_64-328-12-0] open error
**
ERROR:shared.c:346:shm_semaphores_init: assertion failed: (tmp_shared != NULL)

** (/usr/lib/f-spot/f-spot.exe:3883): WARNING **: Thread (nil) may have been prematurely finalized
Stacktrace:


** (/usr/lib/f-spot/f-spot.exe:3883): WARNING **: Thread (nil) may have been prematurely finalized

Native stacktrace:

	f-spot [0x429e65]
	/lib/libpthread.so.0 [0x7f1a920ff080]
	/lib/libc.so.6(gsignal+0x35) [0x7f1a91b2bfb5]
	/lib/libc.so.6(abort+0x183) [0x7f1a91b2dbc3]
	/usr/lib/libglib-2.0.so.0(g_assertion_message+0x113) [0x7f1a927784f3]
	/usr/lib/libglib-2.0.so.0 [0x7f1a92778a82]
	f-spot [0x51a497]
	f-spot [0x5079dd]
	f-spot(mono_once+0x63) [0x515293]
	f-spot [0x507760]
	f-spot [0x519306]
	f-spot [0x4b8a87]
	f-spot(mono_runtime_init+0x25) [0x4c0485]
	f-spot [0x53cf3c]
	f-spot(mono_main+0x311) [0x417831]
	/lib/libc.so.6(__libc_start_main+0xe6) [0x7f1a91b175a6]
	f-spot [0x416ef9]

Debug info from gdb:

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f1a92dd9730 (LWP 3883)]
0x00007f1a920fdea0 in __read_nocancel () from /lib/libpthread.so.0
  1 Thread 0x7f1a92dd9730 (LWP 3883)  0x00007f1a920fdea0 in __read_nocancel ()
   from /lib/libpthread.so.0

Thread 1 (Thread 0x7f1a92dd9730 (LWP 3883))

  • #0 __read_nocancel
    from /lib/libpthread.so.0
  • #1 ??
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 IA__g_assertion_message
    at /build/buildd/glib2.0-2.20.1/glib/gtestutils.c line 1301
  • #6 IA__g_assertion_message_expr
    at /build/buildd/glib2.0-2.20.1/glib/gtestutils.c line 1312
  • #7 ??
  • #8 ??
  • #9 mono_once
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 mono_runtime_init
  • #14 ??
  • #15 mono_main
  • #16 __libc_start_main
    from /lib/libc.so.6
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #0 __read_nocancel
    from /lib/libpthread.so.0

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Aborted


Other information:
Comment 1 mahfiaz 2009-07-01 20:23:47 UTC
*** Bug 587556 has been marked as a duplicate of this bug. ***
Comment 2 Maxxer 2009-07-02 12:14:52 UTC

*** This bug has been marked as a duplicate of 322541 ***