firestarter crashed with SIGSEGV in __pthread_mutex_unlock_usercnt()

StacktraceTop:magazine_cache_push_magazine (ix=1, magazine_chunks=<value optimized out>, count=46) at /build/buildd/glib2.0-2.13.6/glib/gslice.c:593
private_thread_memory_cleanup (data=0x8656960) at /build/buildd/glib2.0-2.13.6/glib/gslice.c:691
?? ()
?? ()
?? ()

I'm getting the same problem. If I start from the terminal I see this warning, maybe it has nothing to do with the problem but maybe it will help.

gksu firestarter

***MEMORY-WARNING***: gksu[8552]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...
Firewall started

Firestarter then crashes after a few minutes

The same problem here. Firestarter works normally, then freezes and crashes (or just crashes).

I don't know if this is the same issue, but I've had two crashes (Gutsy, amd64)

kernel: [ 1335.716398] firestarter[3955]: segfault at 0000000000000160 rip 00002b4c75157d6c rsp 00007fff3c670370 error 4

I tried to attach data from /var/crash/_usr_sbin_firestarter.0.crash, but launchpad kept saying that I cannot upload an empty file. The file is not empty. I can email it to anyone that needs it.

later I also got:

kernel: [ 1624.699822] firestarter[5075]: segfault at 0000000000000598 rip 00002b7502285c2a rsp 0000000041001040 error 6

same bug.

firestarter version: 1.0.3-6ubuntu1
 on hardy heron alpha 3. (but is the same on gutsy)

Firestarter works normaly and after 1 or 2 minutes crashes every time.

Could you check if this is a duplicate of Bug #120445 ?

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Problem solved, no issue in Intrepid :-)

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!