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 484333 - crash in Tasks: program was just sitting...
crash in Tasks: program was just sitting...
Status: RESOLVED DUPLICATE of bug 455180
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-07 06:02 UTC by wipeout_630
Modified: 2007-10-07 15:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description wipeout_630 2007-10-07 06:02:31 UTC 
Version: 2.10

What were you doing when the application crashed?
program was just sitting open on my desktop


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 126681088 vsize: 126681088 resident: 46497792 share: 33333248 rss: 46497792 rss_rlim: 4294967295
CPU usage: start_time: 1191735748 rtime: 415 utime: 379 stime: 36 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 -1209047328 (LWP 8682)]
[New Thread -1230636144 (LWP 13381)]
[New Thread -1264878704 (LWP 13354)]
[New Thread -1243898992 (LWP 9632)]
[New Thread -1296348272 (LWP 9631)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 168484

Thread 1 (Thread -1209047328 (LWP 8682))

  • #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_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (88583 sec old) ---------------------
Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4)
==========================================================================
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 32000 Hz, 2 ch, s16le, 128.0 kbit/12.50% (ratio: 16000->128000)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
A:   0.1 V:   0.0 A-V:  0.056 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
VDec: vo config request - 352 x 284 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.24:1 - prescaling to correct movie aspect.
VO: [xv] 352x284 => 352x284 Planar YV12 
A:   0.1 V:   0.0 A-V:  0.072 ct:  0.000   2/  2 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.042 ct:  0.000   3/  3 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.005 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Suman Manjunath 2007-10-07 15:38:46 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 455180 ***