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 328682 - Critical warning crash on launch
Critical warning crash on launch
Status: RESOLVED DUPLICATE of bug 333234
Product: evolution
Classification: Applications
Component: Memos
2.6.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 329377 331614 332505 (view as bug list)
Depends on:
Blocks: 327508
 
 
Reported: 2006-01-26 04:33 UTC by Elijah Newren
Modified: 2013-09-13 00:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Elijah Newren 2006-01-26 04:33:38 UTC
After launch I saw the little "this is an unstable version of Evolution
just for testing purposes; we suggest Evolution-2.4.2.1 for non-testers"
warning or whatever it said exactly, clicked on the "don't tell me
again" button, then clicked okay, and about a second later before any
other window came up I got this crash.  (This is cut & pasted from a "message denied" email received due to I'm guessing a bad sendmail setup but in any event generated it was originally created by bug-buddy; should hopefully still be intact...).

Debugging Information:

Backtrace was generated from '/opt/gnome2/bin/evolution-2.6'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -166537536 (LWP 24910)]
0x007927a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -166537536 (LWP 24910))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 792

Comment 1 Christian Kirbach 2006-01-26 19:13:21 UTC
unique stack trace
Comment 2 parthasarathi susarla 2006-01-27 09:05:36 UTC
Stack trace shows that the issue in loading up the Calendar & Memos component. Re-assigning to appropriate component
Comment 3 André Klapper 2006-02-01 13:48:49 UTC
*** Bug 329377 has been marked as a duplicate of this bug. ***
Comment 4 Luca Ferretti 2006-02-07 10:04:34 UTC
I suspect this is the same issue, isn't it?

Backtrace was generated from '/opt/gnome2/bin/evolution-2.6'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1232804160 (LWP 22488)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1232804160 (LWP 22488))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 792

Comment 5 André Klapper 2006-02-18 00:42:18 UTC
luca: yes, it's the same issue.
quoting vincent from bug 331614: "It seems it only happens if there's no evolution configuration."

targetting to 2.5.
Comment 6 André Klapper 2006-02-18 00:42:21 UTC
*** Bug 331614 has been marked as a duplicate of this bug. ***
Comment 7 Luca Ferretti 2006-02-20 14:33:44 UTC
(In reply to comment #5)
> quoting vincent from bug 331614: "It seems it only happens if there's no
> evolution configuration."
> 

It could be true. I experienced the crash using a newly created account for testing.
Comment 8 André Klapper 2006-02-25 14:11:50 UTC
*** Bug 332505 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2006-06-17 15:14:47 UTC
after reading the stacktrace i am pretty sure that this is a duplicate of bug 333234 which has been already fixed. see attached patch at bug 333234.

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