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 448973 - crash in Tasks: just opened the plugin m...
crash in Tasks: just opened the plugin m...
Status: RESOLVED DUPLICATE of bug 465234
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
aklapper[fc7]
Depends on:
Blocks:
 
 
Reported: 2007-06-19 02:23 UTC by kirby_samydurai
Modified: 2007-08-23 07:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kirby_samydurai 2007-06-19 02:23:58 UTC 
What were you doing when the application crashed?
just opened the plugin manager and closed it.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 106905600 vsize: 106905600 resident: 29777920 share: 19128320 rss: 29777920 rss_rlim: 4294967295
CPU usage: start_time: 1182219700 rtime: 501 utime: 470 stime: 31 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208183072 (LWP 5312)]
[New Thread -1227818096 (LWP 5322)]
(no debugging symbols found)
0x00f5c402 in __kernel_vsyscall ()

+ Trace 142024

Thread 1 (Thread -1208183072 (LWP 5312))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/evolution/2.10/plugins/liborg-gnome-plugin-manager.so
  • #11 g_datalist_clear
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #17 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #19 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #22 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #23 main
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-06-19 09:18:34 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. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces







Comment 2


André Klapper





          2007-07-04 18:00:14 UTC
        



Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on certain distributions. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue.

Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.







Comment 3


Tobias Mueller





          2007-08-23 07:05:21 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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