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 472906 - crash in Tasks:
crash in Tasks:
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
Depends on:
Blocks:
 
 
Reported: 2007-09-02 18:54 UTC by phubsm
Modified: 2007-09-04 18:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description phubsm 2007-09-02 18:54:12 UTC
Version: 2.10

What were you doing when the application crashed?



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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 147193856 vsize: 147193856 resident: 46350336 share: 37879808 rss: 46350336 rss_rlim: 4294967295
CPU usage: start_time: 1188759234 rtime: 181 utime: 164 stime: 17 cutime:2 cstime: 7 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 -1208912160 (LWP 17253)]
[New Thread -1282061424 (LWP 17292)]
[New Thread -1235010672 (LWP 17274)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208912160 (LWP 17253))

  • #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 (19992 sec old) ---------------------
// gg_watch_fd_connected() received a notify reply
KK <gadu-private.cpp:432>	virtual void GaduSocketNotifiers::socketEvent(): connected
KK <gadu.cpp:1909>	void GaduProtocol::userListReceived(const gg_event*)
KK <gadu.cpp:587>	void GaduProtocol::protocolUserDataChanged(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <powerkadu/infos.cpp:85>	void Infos::onUserStatusChangedSlot(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <gadu.cpp:587>	void GaduProtocol::protocolUserDataChanged(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <powerkadu/infos.cpp:85>	void Infos::onUserStatusChangedSlot(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <gadu.cpp:587>	void GaduProtocol::protocolUserDataChanged(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <powerkadu/infos.cpp:85>	void Infos::onUserStatusChangedSlot(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <gadu.cpp:587>	void GaduProtocol::protocolUserDataChanged(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <powerkadu/infos.cpp:85>	void Infos::onUserStatusChangedSlot(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <gadu.cpp:587>	void GaduProtocol::protocolUserDataChanged(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
KK <powerkadu/infos.cpp:85>	void Infos::onUserStatusChangedSlot(QString, UserListElement, QString, QVariant, QVariant, bool, bool)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2007-09-04 18:59:35 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 ***