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 363330 - crash in Evolution: Switching from vertical ...
crash in Evolution: Switching from vertical ...
Status: RESOLVED DUPLICATE of bug 363839
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-10-19 05:47 UTC by Ted Gould
Modified: 2006-10-21 05:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Ted Gould 2006-10-19 05:47:12 UTC 
What were you doing when the application crashed?
Switching from vertical view to classic view.  I had just restarted Evolution to find that all of my views have gone missing.  Before restarting I was looking at the view editor.  In the view editor I selected to create a new view, hit cancel (I was surprised I couldn't copy from another view and didn't want to start from scratch) and closed the dialog.  I then closed Evolution.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 35409920 vsize: 0 resident: 130617344 share: 0 rss: 130617344 rss_rlim: 0
CPU usage: start_time: 37429 rtime: 0 utime: 1161236676 stime: 0 cutime:1160 cstime: 0 timeout: 1114 it_real_value: 0 frequency: 46

Backtrace was generated from '/usr/bin/evolution-2.8'

(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 805614976 (LWP 9922)]
[New Thread 877262064 (LWP 9955)]
[New Thread 876606704 (LWP 9950)]
[New Thread 868218096 (LWP 9949)]
[New Thread 840778992 (LWP 9944)]
[New Thread 849167600 (LWP 9940)]
[New Thread 831997168 (LWP 9938)]
[New Thread 823604464 (LWP 9936)]
(no debugging symbols found)
0x0ea20220 in waitpid () from /lib/libc.so.6

+ Trace 77108

Thread 8 (Thread 823604464 (LWP 9936))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 7 (Thread 831997168 (LWP 9938))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 6 (Thread 849167600 (LWP 9940))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 5 (Thread 840778992 (LWP 9944))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 4 (Thread 868218096 (LWP 9949))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0

Thread 3 (Thread 876606704 (LWP 9950))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 start_thread
    from /lib/libpthread.so.0 






Comment 1


Karsten Bräckelmann





          2006-10-19 07:42:38 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions







Comment 2


Ted Gould





          2006-10-21 05:36:18 UTC
        




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