GNOME Bugzilla – Bug 271322
Crash on Startup with No Network
Last modified: 2005-10-27 16:43:46 UTC
Distribution: Fedora Core release Rawhide (Rawhide) Package: Evolution-Data-Server Priority: Major Version: GNOME2.8.0 1.1 Gnome-Distributor: Red Hat, Inc Synopsis: Crash on Startup with No Network Bugzilla-Product: Evolution-Data-Server Bugzilla-Component: Calendar Bugzilla-Version: 1.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Seems like this happens when I don't have my network up yet and EDS tries to start. I use NetworkManager, which doesn't actually get a network until I chose one of the Wireless networks available, so a network isn't up right away when I log in. CVS as of 2005/01/15 02:37 America/New_York of: Evolution EDS Gal GTKHtml Debugging Information: Backtrace was generated from '/usr/libexec/evolution-data-server-1.2' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -153340224 (LWP 2639)] [New Thread -219591760 (LWP 2862)] [New Thread -156619856 (LWP 2689)] 0x009fd7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 54547
Thread 1 (Thread -153340224 (LWP 2639))
Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** bug 271327 has been marked as a duplicate of this bug. ***
*** bug 271912 has been marked as a duplicate of this bug. ***
This is still happening.
There is a such bug open here: https://bugzilla.ubuntu.com/6614
*** Bug 305321 has been marked as a duplicate of this bug. ***
*** Bug 274359 has been marked as a duplicate of this bug. ***
Bug 274359 has a valgrind run attached as attachment 45057 [details]. Marking priority up (it's a crasher), and updating the version number due to the duplicates...
Its a crash in libsoup. Changing the component.
*** Bug 300148 has been marked as a duplicate of this bug. ***
*** Bug 300155 has been marked as a duplicate of this bug. ***
*** Bug 300150 has been marked as a duplicate of this bug. ***
*** Bug 311313 has been marked as a duplicate of this bug. ***
Not reproducible with the current libsoup (2.2.6.1), and all of the traces predate the dns rewrite earlier this year, so this is presumably fixed. Reopen with a new stack trace if this is still a problem for you with current libsoup.