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 248092 - Crashes on window resize
Crashes on window resize
Status: RESOLVED DUPLICATE of bug 244444
Product: evolution
Classification: Applications
Component: Shell
pre-1.5 (obsolete)
Other All
: Normal blocker
: ---
Assigned To: Ettore Perazzoli
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-09-02 22:44 UTC by Matthew O'Haire
Modified: 2003-09-03 16:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthew O'Haire 2003-09-02 22:44:03 UTC 
Description of Problem:


Steps to reproduce the problem:
1. Display configured with shorcut hidden, folder
bar on left, message headers top of right and
message preview bottom of right.
2. Click in-box folder to view message headers.
3. Click on a message so it is shown in the
message preview.  My config has the grey box with
the sender and recipient infor shown at the top of
the message preview.
4. Now using either the TOP or BOTTOM window
rezise bars, resize the whole Evolution window.
5. As you do so, the message preview window is
resized.
6. As the resized window approaches the
splitter-bar between the message headers and
message preview the program crashes with a
"Floating Point" exception.
7. It only seems to happen if a message is shown
in the preview window.

Actual Results:
The program crashes with a Floating Point exception.

Expected Results:
The preview window would be "squashed" against the
slider bar and bumped along with the window border.

How often does this happen? 
Easily reproduced and predicatable (on my machine ;-)

Additional Information:
There doesn't appear to be a problem resizing
horizontally (width).  The problem can be produced
using the windows bottom-right resizing thingy.
Comment 1 Gerardo Marin 2003-09-02 23:08:10 UTC 
Can't reproduce this problem.
Please attach a backtrace, otherwise we can't pinpoint the problem
Comment 2 Gerardo Marin 2003-09-02 23:08:37 UTC 
Please reopen this report when you do so.
Comment 3 Matthew O'Haire 2003-09-03 04:38:49 UTC 
Starting program: /usr/bin/evolution
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 8041)]
[New Thread 32769 (LWP 8043)]
[New Thread 16386 (LWP 8044)]
[New Thread 32771 (LWP 8045)]
[New Thread 49156 (LWP 8046)]
[New Thread 65541 (LWP 8047)]

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 16384 (LWP 8041)]
0x4142a4c4 in _init () from /usr/lib/gtk-2.0/2.2.0/engines/libgalaxy.so
(gdb) thread apply all bt

+ Trace 39935

Thread 6 (Thread 65541 (LWP 8047))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 5 (Thread 49156 (LWP 8046))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 4 (Thread 32771 (LWP 8045))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0

Thread 3 (Thread 16386 (LWP 8044))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 e_msgport_wait
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #4 e_thread_busy
    from /usr/lib/evolution/1.4/libeutil.so.0
  • #5 pthread_start_thread
    from /lib/i686/libpthread.so.0
  • #6 pthread_start_thread_event
    from /lib/i686/libpthread.so.0 






Comment 4


Matthew O'Haire





          2003-09-03 05:15:21 UTC
        



I was running Evolution under KDE with only a partial Gnome install
(as installed by Mandrake 9.1 installer).

After installing the full Gnome desktop (using RPMDrake) the problem
has gone away.  Looks like I was missing a library or something.  I'll
close this bug.






Comment 5


Gerardo Marin





          2003-09-03 16:49:02 UTC
        



Matthew,
Thanks a lot. It seems to me that your crash is related to Galaxy
theme engine. Please try to change it to another theme and if you
still have the crash reopen this report.
This isn't a Evolution problem, but theme problem.






Comment 6


Gerardo Marin





          2003-09-03 16:49:54 UTC
        




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