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 461840 - crash in Tasks: nothing at all, the wind...
crash in Tasks: nothing at all, the wind...
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-30 15:42 UTC by jeremy
Modified: 2007-08-23 06:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jeremy 2007-07-30 15:42:17 UTC
Version: 2.10

What were you doing when the application crashed?
nothing at all, the window just popped up



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-33.fc7 #1 SMP Mon Jul 23 17:33:07 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: 116936704 vsize: 116936704 resident: 45252608 share: 36360192 rss: 45252608 rss_rlim: 4294967295
CPU usage: start_time: 1185806804 rtime: 532 utime: 510 stime: 22 cutime:2 cstime: 5 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 -1208568096 (LWP 23762)]
[New Thread -1262892144 (LWP 24150)]
[New Thread -1293292656 (LWP 24149)]
[New Thread -1231029360 (LWP 23798)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208568096 (LWP 23762))

  • #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 (585 sec old) ---------------------
Mon Jul 30 11:31:25 2007
 CConnection: Server supports RFB protocol version 3.3
 CConnection: Using RFB protocol version 3.3
 CConnection: Authentication successful
 CConn:       Using pixel format depth 6 (8 bpp) rgb222
 CConn:       Using ZRLE encoding
Mon Jul 30 11:32:00 2007
 CConn:       Throughput 20227 kbit/s - changing to hextile encoding
 CConn:       Throughput 20227 kbit/s - changing to full colour
 CConn:       Using pixel format depth 24 (32 bpp) little-endian rgb888
 CConn:       Using hextile encoding
Mon Jul 30 11:32:06 2007
 CConn:       Closed: Window closed by user
--------------------------------------------------
Comment 1 André Klapper 2007-08-01 16:38:36 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 jeremy 2007-08-01 18:48:55 UTC
I was not able to duplicate this crash
Comment 3 Tobias Mueller 2007-08-23 06:26:42 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 431459 ***