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 460930 - crash in Tasks: khai kunni!
crash in Tasks: khai kunni!
Status: RESOLVED DUPLICATE of bug 467846
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
aklapper[fc7]
Depends on:
Blocks:
 
 
Reported: 2007-07-27 13:05 UTC by mm
Modified: 2007-09-04 19:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mm 2007-07-27 13:05:54 UTC
Version: 2.10

What were you doing when the application crashed?
khai kunni!


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 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: 103792640 vsize: 103792640 resident: 35594240 share: 28553216 rss: 35594240 rss_rlim: 4294967295
CPU usage: start_time: 1185541480 rtime: 54 utime: 49 stime: 5 cutime:3 cstime: 8 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 -1208174880 (LWP 3339)]
[New Thread -1261438064 (LWP 3387)]
[New Thread -1218352240 (LWP 3359)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208174880 (LWP 3339))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(evolution:2704): camel-pop3-provider-WARNING **: Bad server response: UQuTAk8LkgJNC5ECSguRAkgLkQJGwABAAAAPABTQAEAAAA
(evolution:2704): camel-pop3-provider-WARNING **: Bad server response: 8AFOAAQAAADwAU8ABAAAAPABUAAEAAAA8AFRAAQAAADwAVIABAAAAPABUwAEAAAA8AFUAAQAAADw
(evolution:2704): camel-pop3-provider-WARNING **: Bad server response: AVUABAAAAPABVgAEAAAA8AFXAAQAAADwAVgABAAAAPABWQAEAAAA8AFaAAQAAADwAVwABAAAAPAB
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:3339): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3339): DEBUG: mailto URL program: evolution
(evolution:3339): e-data-server-ui-WARNING **: Key file does not have group 'Passwords-Mail'
--------------------------------------------------
Comment 1 André Klapper 2007-08-01 16:51:47 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 Tobias Mueller 2007-09-04 19:02:59 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 467846 ***