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 439549 - crash in Evolution: starting evolution.
crash in Evolution: starting evolution.
Status: RESOLVED DUPLICATE of bug 435482
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-05-18 23:24 UTC by dan.mcdonald
Modified: 2007-05-19 17:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dan.mcdonald 2007-05-18 23:24:59 UTC
What were you doing when the application crashed?
starting evolution.


Distribution: Unknown
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 158003200 vsize: 158003200 resident: 31088640 share: 16318464 rss: 31088640 rss_rlim: 4294967295
CPU usage: start_time: 1179530668 rtime: 305 utime: 285 stime: 20 cutime:0 cstime: 0 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237076256 (LWP 15925)]
[New Thread -1345635424 (LWP 15984)]
[New Thread -1336587360 (LWP 15978)]
[New Thread -1328194656 (LWP 15977)]
[New Thread -1319801952 (LWP 15950)]
[New Thread -1311409248 (LWP 15948)]
[New Thread -1286607968 (LWP 15944)]
[New Thread -1278215264 (LWP 15943)]
[New Thread -1268356192 (LWP 15942)]
[New Thread -1259963488 (LWP 15940)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1237076256 (LWP 15925))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #5 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #7 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #8 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (32 sec old) ---------------------
Window manager warning: Property _NET_WM_ICON_NAME on window 0x2600030 contained invalid UTF-8
Window manager warning: Property _NET_WM_NAME on window 0x26031eb contained invalid UTF-8
Window manager warning: Property _NET_WM_ICON_NAME on window 0x26031eb contained invalid UTF-8
(gnome-panel:5405): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
(gnome-panel:5405): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
Window manager warning: Property _NET_WM_NAME on window 0x2603250 contained invalid UTF-8
Window manager warning: Property _NET_WM_ICON_NAME on window 0x2603250 contained invalid UTF-8
** Message: Found best visual for GL: 0x27
CalDAV Eplugin starting up ...
** (evolution:15925): DEBUG: mailto URL command: evolution %s
** (evolution:15925): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Susana 2007-05-19 17:53:55 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 435482 ***