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 448616 - crash in Tasks: clicked on an email from...
crash in Tasks: clicked on an email from...
Status: RESOLVED DUPLICATE of bug 447591
Product: GtkHtml
Classification: Other
Component: Rendering
3.14.x
Other All
: High critical
: ---
Assigned To: gtkhtml-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-17 22:49 UTC by bkearns
Modified: 2007-12-10 01:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description bkearns 2007-06-17 22:49:28 UTC
What were you doing when the application crashed?
clicked on an email from monster.com


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 127188992 vsize: 127188992 resident: 37179392 share: 21905408 rss: 37179392 rss_rlim: 4294967295
CPU usage: start_time: 1182119698 rtime: 1077 utime: 986 stime: 91 cutime:37 cstime: 17 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 -1208514848 (LWP 3580)]
[New Thread -1273541744 (LWP 3822)]
[New Thread -1284031600 (LWP 3821)]
[New Thread -1315501168 (LWP 3684)]
[New Thread -1238934640 (LWP 3629)]
[New Thread -1325991024 (LWP 3621)]
(no debugging symbols found)
0x00a1d402 in __kernel_vsyscall ()

Thread 3 (Thread -1284031600 (LWP 3821))

  • #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 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #9 start_thread
    from /lib/libpthread.so.0
  • #10 clone
    from /lib/libc.so.6


----------- .xsession-errors (37 sec old) ---------------------
(evolution:3580): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9dbc258'
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3580): e-data-server-ui-WARNING **: Key file does not have key 'pop:__bkearns%40gni-us.com@mail.gni-us.com_'
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3580): e-data-server-ui-WARNING **: Key file does not have key 'pop:__b.kearns%40goodnewsinteractive.com@mail.goodnewsinteractive.com_'
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3580): e-data-server-ui-WARNING **: Key file does not have key 'pop:__info%40goodnewsinteractive.com@mail.goodnewsinteractive.com_'
(evolution:3580): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 André Klapper 2007-06-18 21:06:38 UTC
duplicate of bug 309560?
Comment 2 Tobias Mueller 2007-12-10 01:31:05 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 ***