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 265391 - Evolution Crashed when testing Calendar/ also Calendar Bug
Evolution Crashed when testing Calendar/ also Calendar Bug
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
1.5.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks: 318200
 
 
Reported: 2004-09-06 15:19 UTC by nils.beckmann
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description nils.beckmann 2004-09-06 15:19:41 UTC
Distribution: SuSE Linux 9.1 (i586)
Package: Evolution
Priority: Normal
Version: GNOME2.4.1 1.5.93
Gnome-Distributor: GNOME.Org
Synopsis: Evolution Crashed when testing Calendar/ also Calendar Bug
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 1.5.93
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
I tested the Calendar by creating some new calendar items. First I
double-clicked at a time and became the dialog for a new appointments.
Funny enough theyy never appeared in the calendar after pressing OK
(only entered a subject like "test123").

Then cliked on a time and startet entering text directly w/o the extra
dialoge. Everytime I pressed <enter> the test I entered disappeared
although now there was a coloured marking apparently indicating an
Appointment. After two or three times Evolution crashed.

Steps to reproduce the crash:
Maybe one time issue after first start of Evolution 1.5


Expected Results:
Being able to enter appointments and see them and probably evolution not
crashing :)


How often does this happen?
Tried one time. Just started Evolution again and there are two
appointments now showing which I entered using the dialog (when
double-clicking a time in the calendar) and also one (still empty)
appointment from writing directly into the calendar. When I enter text
into the calendar now (directly or by dialoge it works).

Additional Information:
This was the first start of a freshly installed Evolution 1.5.93. At
first it converted my Evolution-1.4 data. Then I entered the free/busy
WebDAV URL for our SuSE Linux Open-Exchange Server (which I wanted to
play a bit w/). Then I wne tpleying w/ the calendar where the crash occurred.

Maybe relevant I upgraded to ulb (www.usr-local-bin..org) Gnome?


Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution-1.5'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1097262464 (LWP 17224)]
[New Thread 1122126768 (LWP 17282)]
[Thread debugging using libthread_db enabled]
[New Thread 1097262464 (LWP 17224)]
[New Thread 1122126768 (LWP 17282)]
[Thread debugging using libthread_db enabled]
[New Thread 1097262464 (LWP 17224)]
[New Thread 1122126768 (LWP 17282)]
[New Thread 1119472560 (LWP 17278)]
[New Thread 1117371312 (LWP 17276)]
[New Thread 1115270064 (LWP 17275)]
[New Thread 1113074608 (LWP 17274)]
[New Thread 1110973360 (LWP 17248)]
[New Thread 1108872112 (LWP 17247)]
0xffffe410 in ?? ()

Thread 8 (Thread 1108872112 (LWP 17247))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 poll
    from /lib/tls/libc.so.6
  • #5 g_main_context_iterate
    at gmain.c line 2875



Unknown reporter: nils.beckmann@li-consulting.de, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 André Klapper 2005-11-30 02:05:05 UTC
i pretty much assume this is fixed nowadays, do you still see this?
Comment 2 Chenthill P 2005-12-20 20:47:03 UTC
closing this as there is no response from the reporter. Please re-open the bug
if you find it happening.