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 502379 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-07 20:41 UTC by jmerrifield
Modified: 2007-12-10 00:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jmerrifield 2007-12-07 20:41:06 UTC
Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 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: 164593664 vsize: 164593664 resident: 63234048 share: 46665728 rss: 63234048 rss_rlim: 4294967295
CPU usage: start_time: 1197039649 rtime: 1263 utime: 1082 stime: 181 cutime:0 cstime: 1 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 -1208449312 (LWP 3902)]
[New Thread -1361146992 (LWP 12071)]
[New Thread -1329677424 (LWP 12069)]
[New Thread -1319187568 (LWP 11108)]
[New Thread -1261446256 (LWP 4080)]
[New Thread -1240466544 (LWP 3923)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 3 (Thread -1329677424 (LWP 12069))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6


----------- .xsession-errors (297 sec old) ---------------------
	at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:502)
	at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:550)
	at org.eclipse.jst.jsp.core.internal.java.search.JSPSearchSupport$SearchJob.run(JSPSearchSupport.java:143)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
[INFO] XmlBeanDefinitionReader - Loading XML bean definitions from file [/home/fracmak/workspace/swift/swift-admin/src/main/webapp/WEB-INF/dispatcher-servlet.xml]
BBDB spinning up...
(evolution:3902): e-data-server-DEBUG: Loading categories from "/home/fracmak/.evolution/categories.xml"
(evolution:3902): e-data-server-DEBUG: Loaded 29 categories
(evolution:3902): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:3902): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa53c138'
(evolution:3902): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa53c258'
** Message: Response 1
--------------------------------------------------
Comment 1 Tobias Mueller 2007-12-10 00:30:33 UTC
Thanks for taking the time to report this bug.
It's most likely that this particular bug is the fedora specific bug 447591:
   GLib-GObject-WARNING **: gsignal.c:1669: signal
   `source_selected' is invalid for instance

but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.
As debug symbols are missing, it's just a guess anyway since we can't determine the issue without debug information. Feel free to install debug information and open a new bug. See http://live.gnome.org/GettingTraces for details

*** This bug has been marked as a duplicate of 447591 ***