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 467627 - crash in Tasks: Scrolled to the top of t...
crash in Tasks: Scrolled to the top of t...
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-08-17 11:40 UTC by david.roth
Modified: 2007-08-21 11:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description david.roth 2007-08-17 11:40:17 UTC
Version: 2.10

What were you doing when the application crashed?
Scrolled to the top of the inbox message list and clicked on the first message, which was new.


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-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 198447104 vsize: 198447104 resident: 66248704 share: 57151488 rss: 66248704 rss_rlim: 4294967295
CPU usage: start_time: 1187349202 rtime: 340 utime: 312 stime: 28 cutime:1 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 -1208428832 (LWP 3115)]
[New Thread -1363960944 (LWP 3587)]
[New Thread -1293104240 (LWP 3162)]
[New Thread -1210528880 (LWP 3159)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208428832 (LWP 3115))

  • #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 (144 sec old) ---------------------
err:toolbar:TOOLBAR_GetImageListForDrawing bitmap for ID 0, index 4 is not valid, number of bitmaps in imagelist: 4
Window manager warning: Window 0x4a00143 (DNCS Admin) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x4a00143 (DNCS Admin) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
err:toolbar:TOOLBAR_GetImageListForDrawing bitmap for ID 0, index 4 is not valid, number of bitmaps in imagelist: 4
err:toolbar:TOOLBAR_GetImageListForDrawing bitmap for ID 0, index 4 is not valid, number of bitmaps in imagelist: 4
fixme:imm:ImmReleaseContext (0x600b4, 0x159200): stub
fixme:imm:ImmReleaseContext (0x600b4, 0x159200): stub
fixme:imm:ImmReleaseContext (0x600f6, 0x159200): stub
fixme:imm:ImmReleaseContext (0x600b4, 0x159200): stub
fixme:imm:ImmReleaseContext (0x600f6, 0x159200): stub
fixme:imm:ImmReleaseContext (0x6016a, 0x159200): stub
fixme:imm:ImmReleaseContext (0x20094, 0x159200): stub
fixme:imm:ImmReleaseContext (0x20094, 0x159200): stub
Window manager warning: Window 0x3e000ef (Create Tas) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
Window manager warning: Window 0x3e000ef (Create Tas) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
--------------------------------------------------
Comment 1 palfrey 2007-08-17 12:40:03 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-08-21 11:53:14 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 ***