GNOME Bugzilla – Bug 323499
Crash setting up a new recurrent appointment with mouse wheel
Last modified: 2006-07-31 08:55:47 UTC
Steps to reproduce: 1. Create a new appointement 2. Click on « Recurrence » tab, then active « This appointement recurs » 3. Change « for » to « until » with mouse wheel instead of mouse button 4. Change the number of « occurence » Expected Results: With buttons, you get new options : date for « until » and nothing for « forever ». With wheel, you get nothing : you stay on « occurences » number : this is wrong. Wheel and button should have the same behavior to avoid crashes. How often does this happen? Every times Stack trace: 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) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912600703216 (LWP 14514)] [New Thread 1115703648 (LWP 14541)] [New Thread 1149540704 (LWP 14537)] [New Thread 1141148000 (LWP 14534)] [New Thread 1124362592 (LWP 14522)] [New Thread 1098918240 (LWP 14518)] [New Thread 1090525536 (LWP 14517)] [New Thread 1082132832 (LWP 14516)] 0x00002aaaae25ceba in waitpid () from /lib/libpthread.so.0
+ Trace 64474
Thread 1 (Thread 46912600703216 (LWP 14514))
Other information: This bug also occurs with « All day event » and « Meetings ».
unique stacktrace according to simpledupfinder; shortening the summary a bit so reading search results gets easier. i can reproduce this running evolution-2.5.2 on suse9.3. there's a workaround to not use the mouse wheel, therefore lowering priority and severity.
Debug backtrace with 2.6.1 on Ubuntu dapper: Backtrace was generated from '/usr/bin/evolution-2.6' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231419168 (LWP 5464)] [New Thread -1322632272 (LWP 5515)] [New Thread -1324352592 (LWP 5514)] [New Thread -1311863888 (LWP 5506)] [New Thread -1303471184 (LWP 5505)] [New Thread -1295078480 (LWP 5478)] [New Thread -1270912080 (LWP 5477)] [New Thread -1261671504 (LWP 5475)] [New Thread -1253278800 (LWP 5473)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 68184
Created attachment 67240 [details] [review] Fixes the bug
Tested the patch, looks good ,can be committed.
Fix has been committed to cvs HEAD and gnome-2-14 branch.