Bug 268345 – Crash: Publishing of calendar

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 268345 - Crash: Publishing of calendar


Summary:	Crash: Publishing of calendar


Status:	RESOLVED DUPLICATE of bug 266631

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.0.x (obsolete)
Hardware:	Other All

Importance:	Normal major
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-10-14 15:44 UTC by tiganu
Modified:	2013-09-10 14:03 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description tiganu 2004-10-14 15:44:33 UTC

Distribution: Gentoo Base System version 1.5.3
Package: Evolution
Priority: Major
Version: GNOME2.8.0 2.0.0
Gnome-Distributor: Gentoo Linux
Synopsis: Publishing of calendar 
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.0.0
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
Adding publishing of calendar for local computer

Steps to reproduce the crash:
1. Settings
2. Clendars / FreeBusy Publishing
3. Add 'Local Computer / Presonal"

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(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)...[Thread debugging using libthread_db enabled]
[New Thread 1093159280 (LWP 669)]
[New Thread 1126378416 (LWP 750)]
[Thread debugging using libthread_db enabled]
[New Thread 1093159280 (LWP 669)]
[New Thread 1126378416 (LWP 750)]
[Thread debugging using libthread_db enabled]
[New Thread 1093159280 (LWP 669)]
[New Thread 1126378416 (LWP 750)]
[New Thread 1117985712 (LWP 698)]
[New Thread 1109593008 (LWP 679)]
0xffffe410 in ?? ()

+ Trace 51032

Thread 4 (Thread 1109593008 (LWP 679))

#0 ??
#1 ??
#2 ??
#3 ??
#4 poll
from /lib/libc.so.6
#5 g_main_context_acquire
from /usr/lib/libglib-2.0.so.0
#6 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#7 link_thread_io_context
from /usr/lib/libORBit-2.so.0
#8 ??
from /usr/lib/libglib-2.0.so.0
#9 ??
#10 g_static_private_free
from /usr/lib/libglib-2.0.so.0
#0 ??




Unknown reporter: tiganu@softhome.net, 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 Gerardo Marin 2004-10-25 23:36:20 UTC


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