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 271322 - Crash on Startup with No Network
Crash on Startup with No Network
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: API
2.2.x
Other All
: High critical
: ---
Assigned To: Dan Winship
Evolution QA team
: 271327 271912 274359 300150 300155 305321 311313 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-01-15 20:21 UTC by Ryan P Skadberg
Modified: 2005-10-27 16:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ryan P Skadberg 2005-01-15 20:21:37 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

Thread 1 (Thread -153340224 (LWP 2639))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libc.so.6
  • #2 do_system
    from /lib/tls/libc.so.6
  • #3 system
    from /lib/tls/libc.so.6
  • #4 system
    from /lib/tls/libpthread.so.0
  • #5 gnome_segv_handler
    at server.c line 109
  • #6 <signal handler called>
  • #7 send_request
    from /usr/lib/libsoup-2.2.so.7
  • #8 soup_dns_entry_get_hostent
    from /usr/lib/libsoup-2.2.so.7
  • #9 soup_address_get_port
    from /usr/lib/libsoup-2.2.so.7
  • #10 soup_address_get_port
    from /usr/lib/libsoup-2.2.so.7
  • #11 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at server.c line 347



Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Ryan P Skadberg 2005-01-29 18:27:08 UTC
*** bug 271327 has been marked as a duplicate of this bug. ***
Comment 2 Ryan P Skadberg 2005-01-29 18:27:47 UTC
*** bug 271912 has been marked as a duplicate of this bug. ***
Comment 3 Ryan P Skadberg 2005-02-21 21:10:23 UTC
This is still happening.
Comment 4 Sebastien Bacher 2005-03-15 14:15:38 UTC
There is a such bug open here: https://bugzilla.ubuntu.com/6614
Comment 5 Elijah Newren 2005-05-31 22:05:45 UTC
*** Bug 305321 has been marked as a duplicate of this bug. ***
Comment 6 Elijah Newren 2005-05-31 22:08:00 UTC
*** Bug 274359 has been marked as a duplicate of this bug. ***
Comment 7 Elijah Newren 2005-05-31 22:10:32 UTC
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...
Comment 8 Chenthill P 2005-08-05 09:17:34 UTC
Its a crash in libsoup. Changing the component.
Comment 9 Chenthill P 2005-08-09 08:18:58 UTC
*** Bug 300148 has been marked as a duplicate of this bug. ***
Comment 10 Chenthill P 2005-08-09 08:28:51 UTC
*** Bug 300155 has been marked as a duplicate of this bug. ***
Comment 11 Chenthill P 2005-08-22 22:22:54 UTC
*** Bug 300150 has been marked as a duplicate of this bug. ***
Comment 12 Dan Winship 2005-10-26 20:13:40 UTC
*** Bug 311313 has been marked as a duplicate of this bug. ***
Comment 13 Dan Winship 2005-10-27 16:43:46 UTC
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.