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 455653 - crash in Tasks: editing mail account pro...
crash in Tasks: editing mail account pro...
Status: RESOLVED DUPLICATE of bug 430817
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-10 19:14 UTC by piotr
Modified: 2007-07-11 12:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description piotr 2007-07-10 19:14:34 UTC
Version: 2.10

What were you doing when the application crashed?
editing mail account properties (account made default account and OK pressed)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 159399936 vsize: 159399936 resident: 79429632 share: 41598976 rss: 79429632 rss_rlim: 4294967295
CPU usage: start_time: 1184090351 rtime: 16327 utime: 16252 stime: 75 cutime:27 cstime: 13 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 -1208510752 (LWP 5918)]
[New Thread -1267135600 (LWP 6208)]
[New Thread -1236849776 (LWP 5924)]
(no debugging symbols found)
0x00453402 in __kernel_vsyscall ()

Thread 1 (Thread -1208510752 (LWP 5918))

  • #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_str_hash
    from /lib/libglib-2.0.so.0
  • #6 g_hash_table_insert
    from /lib/libglib-2.0.so.0
  • #7 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #8 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (2901 sec old) ---------------------
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-07-11 12:43:23 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 430817 ***