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 87710 - Crash on checking inbox on start up.
Crash on checking inbox on start up.
Status: VERIFIED INCOMPLETE
Product: balsa
Classification: Other
Component: general
2.0.x
Other other
: High critical
: ---
Assigned To: Balsa Maintainers
Balsa Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-07-09 02:41 UTC by theraven
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description theraven 2002-07-09 02:42:54 UTC 
Package: balsa
Severity: normal
Version: 2.0.1
Synopsis: Crash on checking inbox on start up.
Bugzilla-Product: balsa
Bugzilla-Component: general

Description:
Description of Problem: When I check an option "check inbox on startup"
and quit from Balsa on next startup it crashes. But everything seems to
be OK when i do the same with root. 
Actual Results: Crash
Additional Info: I'm using Gnome2 2.0.0.




Debugging Information:

Backtrace was generated from '/usr/bin/balsa'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 5590)]
[New Thread 2049 (LWP 5591)]
[New Thread 2050 (LWP 5593)]
0x420292e5 in sigsuspend ()
   from /lib/i686/libc.so.6

+ Trace 24835

Thread 3 (Thread 2050 (LWP 5593))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 __pthread_alt_lock
    from /lib/i686/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/libpthread.so.0
  • #4 gdk_threads_enter
    at gdk.c line 442
  • #5 real_open_mbnode
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 1 (Thread 1024 (LWP 5590))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 __pthread_alt_lock
    from /lib/i686/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/libpthread.so.0
  • #4 gdk_event_prepare
    at gdkevents-x11.c line 1720
  • #5 g_main_context_prepare
    at gmain.c line 1929
  • #6 g_main_context_iterate
    at gmain.c line 2222
  • #7 g_main_loop_run
    at gmain.c line 2462
  • #8 gtk_main
    at gtkmain.c line 936
  • #9 main
  • #10 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 sigsuspend
    from /lib/i686/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-07-08 22:42 -------

The original reporter (theraven@xakep.ru) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, pawsa@theochem.kth.se.
Comment 1 Pawel Salek 2002-08-07 06:01:28 UTC 
Does it crash or lock up?
Comment 2 Constantine Evans 2003-07-18 04:24:14 UTC 
This seems to be a unique stack trace per simple-dup-finder. Changing
to high+critical and confirming.
Comment 3 Pawel Salek 2003-07-18 07:56:48 UTC 
No response for a year, closing the report.