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 268923 - opening crash
opening crash
Status: RESOLVED DUPLICATE of bug 249624
Product: evolution
Classification: Applications
Component: general
pre-1.5 (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-10-29 07:14 UTC by jmreusch
Modified: 2004-10-29 20:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jmreusch 2004-10-29 07:14:28 UTC
Distribution: SuSE Linux 9.1 (i586)
Package: Evolution
Priority: Normal
Version: GNOME2.4.1 1.4
Gnome-Distributor: GNOME.Org
Synopsis: opening crash
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 1.4
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
Errors when accidental double clicking to open.

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:
normal start up process.

How often does this happen?
any time opening clicks are to close together.

Additional Information:



Debugging Information:

Backtrace was generated from
'/usr/local:/opt/gnome:/usr/libexec/evolution-alarm-notify'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread 1094831040 (LWP 3917)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0xffffe410 in ?? ()

Thread 1 (Thread 1094831040 (LWP 3917))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 raise
    from /lib/tls/libc.so.6
  • #12 abort
    from /lib/tls/libc.so.6
  • #13 g_logv
    from /opt/gnome/lib/libglib-2.0.so.0
  • #14 g_log
    from /opt/gnome/lib/libglib-2.0.so.0
  • #15 main
  • #0 ??



Unknown reporter: jmreusch@tds.net, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2004-10-29 20:50:10 UTC

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