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 507562 - crash in Tasks: I was away from keyboard...
crash in Tasks: I was away from keyboard...
Status: RESOLVED DUPLICATE of bug 368272
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-05 23:33 UTC by uwe
Modified: 2008-02-07 06:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description uwe 2008-01-05 23:33:45 UTC 
Version: 2.12

What were you doing when the application crashed?
I was away from keyboard.


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.2 2007-11-27 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-0.123.rc6.fc9 #1 SMP Fri Dec 21 16:28:26 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 73588736 vsize: 73588736 resident: 16580608 share: 10084352 rss: 16580608 rss_rlim: 4294967295
CPU usage: start_time: 1199488278 rtime: 4100 utime: 2737 stime: 1363 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208166112 (LWP 20925)]
[New Thread -1211319408 (LWP 20927)]
0x00110402 in __kernel_vsyscall ()

+ Trace 184214

Thread 1 (Thread -1208166112 (LWP 20925))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 strrchr
    from /lib/libc.so.6
  • #10 process_flags
    at mail-stub-exchange.c line 1842
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at main.c line 238
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #18 _start
  • #0 __kernel_vsyscall 


----------- .xsession-errors (42466 sec old) ---------------------
report junk?? ailozzar
report junk?? WebSite Support
Internal error occurred
java.lang.InterruptedException
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:485)
	at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165)
	at org.rubypeople.rdt.internal.ui.text.ruby.hover.RiDocHoverProvider.execAndReadOutput(RiDocHoverProvider.java:140)
	at org.rubypeople.rdt.internal.ui.text.ruby.hover.RiDocHoverProvider.getRIResult(RiDocHoverProvider.java:161)
	at org.rubypeople.rdt.internal.ui.text.ruby.hover.RiDocHoverProvider.getHoverInfo(RiDocHoverProvider.java:75)
	at org.rubypeople.rdt.internal.ui.text.ruby.hover.BestMatchHover.getHoverInfo(BestMatchHover.java:99)
	at org.rubypeople.rdt.internal.ui.text.ruby.hover.RubyEditorTextHoverProxy.getHoverInfo(RubyEditorTextHoverProxy.java:67)
	at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:165)
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-07 06:00:59 UTC 
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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