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 485310 - crash in Evolution Mail: openning evo in offline ...
crash in Evolution Mail: openning evo in offline ...
Status: RESOLVED DUPLICATE of bug 485311
Product: evolution-data-server
Classification: Platform
Component: libical
1.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 485321 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-10 08:48 UTC by cs
Modified: 2008-07-03 16:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
stack trace (8.06 KB, text/plain)
2007-10-10 19:10 UTC, cs
Details

Description cs 2007-10-10 08:48:30 UTC
What were you doing when the application crashed?
openning evo in offline mode


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.11-1-k7 #1 Mon Jun 20 21:26:23 MDT 2005 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70000000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 27099136 vsize: 27099136 resident: 9338880 share: 7901184 rss: 9338880 rss_rlim: 4294967295
CPU usage: start_time: 1192006022 rtime: 10 utime: 9 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-alarm-notify'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb69956b0 (LWP 3164)]
[New Thread 0xb66e7b90 (LWP 3165)]
0xb780bbf1 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb69956b0 (LWP 3164))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.1/glib/gspawn.c line 364
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.1/glib/gspawn.c line 672
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 strlen
    from /lib/libc.so.6
  • #6 ??
    from /usr/lib/libecal-1.2.so.7
  • #7 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (88122 sec old) ---------------------
icewm-session: Warning: Closing file descriptor: 5
icewm-session: Warning: File still open: fd=7, target='pipe:[3864]' (missing FD_CLOEXEC?)
icewm-session: Warning: Closing file descriptor: 7
icewm-session: Warning: File still open: fd=5, target='pipe:[3860]' (missing FD_CLOEXEC?)
icewm-session: Warning: Closing file descriptor: 5
icewm-session: Warning: File still open: fd=7, target='pipe:[3864]' (missing FD_CLOEXEC?)
icewm-session: Warning: Closing file descriptor: 7
icewm-session: Warning: File still open: fd=5, target='pipe:[3860]' (missing FD_CLOEXEC?)
icewm-session: Warning: Closing file descriptor: 5
icewm-session: Warning: File still open: fd=7, target='pipe:[3864]' (missing FD_CLOEXEC?)
icewm-session: Warning: Closing file descriptor: 7
icewm-session: using /home/michael/.icewm for private configuration files
IceWM: using /home/michael/.icewm for private configuration files
icewmtray: using /home/michael/.icewm for private configuration files
icewmbg: using /home/michael/.icewm for private configuration files
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-10 11:20:56 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-10-10 11:21:43 UTC
*** Bug 485311 has been marked as a duplicate of this bug. ***
Comment 3 cs 2007-10-10 19:09:56 UTC
more complete stack trace attached. note that bugBuddy catches something (hence this report) but the evo app doesn't die (ie one can check some a/counts for email etc). sorry for misleading title! Michael
Comment 4 cs 2007-10-10 19:10:40 UTC
Created attachment 97019 [details]
stack trace
Comment 5 Tobias Mueller 2007-10-11 21:10:38 UTC
Thanks for that stacktrace :) If you could provide debug symbols for glibc and ORBit, it would be very awesome ;-)

  • #4 <signal handler called>
  • #5 strlen
    from /lib/libc.so.6
  • #6 icaltimezone_init_builtin_timezones
    at icaltimezone.c line 1610
  • #7 icaltimezone_get_builtin_timezone
    at icaltimezone.c line 1353
  • #8 config_data_get_timezone
    at config-data.c line 212
  • #9 queue_midnight_refresh
    at alarm-queue.c line 197
  • #10 alarm_queue_init
    at alarm-queue.c line 1873
  • #11 alarm_notify_init
    at alarm-notify.c line 248
  • #12 IA__g_type_create_instance
    at /tmp/buildd/glib2.0-2.14.1/gobject/gtype.c line 1569
  • #13 g_object_constructor
    at /tmp/buildd/glib2.0-2.14.1/gobject/gobject.c line 1046

This is quite similar to bug 485311, I think it's the same issue.
Comment 6 Tobias Mueller 2007-10-11 21:12:19 UTC
*** Bug 485321 has been marked as a duplicate of this bug. ***
Comment 7 cs 2007-10-11 21:53:10 UTC
a) I'm unsure how to get glibc and ORBit dbg symbols etc - apt-cache search on these doesn't give a -dbg version for unstable Debian...

b) a difference with 485311 is that this bug doesn't completely kill evolution whereas 485311 does but i agree there is a degree of similarity!

c) i'm happy to progress this by doing (a) [with your advice!] and once we've fixed this decide whether it fixed 485311 and if not we can look into that further.

Ta, Michael
Comment 8 Milan Crha 2008-07-03 16:35:22 UTC
Marking this as duplicate of the other mantined above, because the reason for this will be same. See the other bug for more information.

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