Ubuntu
libsoup package

crash on gnome session login with NetworkManager

Bug #12969 reported by Joe Barnett
8
Affects Status Importance Assigned to Milestone
libsoup (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

crashed immediately after logging into gnome

Backtrace was generated from '/usr/libexec/evolution-data-server-1.2'

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)
(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)
(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 -1222483840 (LWP 8410)]
[New Thread -1250370640 (LWP 8429)]
[New Thread -1225053264 (LWP 8415)]
(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)
0xffffe410 in ?? ()
#0 0xffffe410 in ?? ()
#1 0xbffff354 in ?? ()
#2 0x00000000 in ?? ()
#3 0xbffff210 in ?? ()
#4 0xb739a4bb in waitpid () from /lib/tls/i686/cmov/libc.so.6
#5 0xb73334c6 in system () from /lib/tls/i686/cmov/libc.so.6
#6 0xb7333257 in system () from /lib/tls/i686/cmov/libc.so.6
#7 0x0804b5cd in server_logging_register_domain ()
#8 <signal handler called>
#9 0xb707c4bb in send_request () from /usr/lib/libsoup-2.2.so.7
#10 0xb707d1c9 in soup_dns_entry_get_hostent () from /usr/lib/libsoup-2.2.so.7
#11 0xb70773d5 in soup_address_get_port () from /usr/lib/libsoup-2.2.so.7
#12 0xb7077525 in soup_address_get_port () from /usr/lib/libsoup-2.2.so.7
#13 0xb74851d8 in g_main_context_wakeup () from /usr/lib/libglib-2.0.so.0
#14 0xb7482ce7 in g_main_depth () from /usr/lib/libglib-2.0.so.0
#15 0xb7483c8d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0xb7483faf in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0xb74844f6 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#18 0xb75fc6f3 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#19 0x0804bc94 in main ()

Thread 3 (Thread -1225053264 (LWP 8415)):
#0 0xffffe410 in ?? ()
No symbol table info available.
#1 0xb6fb29d8 in ?? ()
No symbol table info available.
#2 0xffffffff in ?? ()
No symbol table info available.
#3 0x00000009 in ?? ()
No symbol table info available.
#4 0xb73bf589 in poll () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#5 0xb74848b6 in g_main_loop_get_context () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#6 0xb7483f2f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#7 0xb74844f6 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#8 0xb7577f28 in link_thread_io_context () from /usr/lib/libORBit-2.so.0
No symbol table info available.
#9 0xb74db398 in ?? () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#10 0xb6fb2ad8 in ?? ()
No symbol table info available.
#11 0xb749c2f2 in g_static_private_free () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#0 0xffffe410 in ?? ()

http://bugzilla.gnome.org/show_bug.cgi?id=271322: http://bugzilla.gnome.org/show_bug.cgi?id=271322

See original description
Revision history for this message
Sebastien Bacher (seb128) wrote :

the package installs /usr/lib/evolution/evolution-data-server-1.2, you have
probably installed /usr/libexec/evolution-data-server-1.2 by a different way,
I'm closing this bug. Feel free to reopen if you get the issue with the packages.

Revision history for this message
Joe Barnett (thejoe) wrote :

the evolution-data-server-1.2 executable is actually in /usr/lib/evolution, i'm
not sure why it's saying that it is in libexec, as i have nothing in
/usr/libexec.... this is running the latest hoary packages, btw, and is very
intermittent, but repeatable. re-opening.

Revision history for this message
Sebastien Bacher (seb128) wrote :

weird. Do you still get the crash with 2.1.6 ? Is your GNOME working fine out of
this ?

Revision history for this message
Joe Barnett (thejoe) wrote :

I'm still seeing all the same crashers in 2.1.6 that I've seen in 2.1.5.

the crash on login seems to be related to when my network connection comes up.
I'm using NetworkManager, which won't connect until hal has enumerated all its
devices, which takes about 1.5 minutes (there's a HAL bug open in ubuntu
bugzilla about this). Recently, I've been waiting until the connection is up
before logging into gnome, and haven't seen the crash on login with 2.1.5 or
2.1.6. Calendar related stuff is still very unstable, though (some bugs filed
in ubuntu bugzilla, others in upstream).

Except for Evolution (almost all related to exchange, I think), all of GNOME is
very stable.

Revision history for this message
Brett Johnson (brett-hp) wrote :
Download full text (7.2 KiB)

I'm getting the same kind of evolution-data-server crash on evolution startup.
Here is the bug-buddy report:

Oh, and it seems to be calendar related. If I remove
~/.evolution/calendar/local, the problem goes away.

################################ BugBuddy Report
#########################################
Subject: evolution-data-server crashes on startup

Distribution: Debian 3.1
Package: Evolution
Priority: Normal
Version: GNOME2.10.0 1.1.6
Gnome-Distributor: Ubuntu
Synopsis: evolution-data-server crashes on startup
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: 1.1.6
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:

evolution data server crashes when I start up evolution.

Steps to reproduce the crash:
1. Start Evolution
2. Profit!
3.

Expected Results:

Not crashing.

How often does this happen?

always.

Additional Information:

Seems to be calendar related. If I remove ~/.evolution/calendar/local
-- evolution starts up fine.

Debugging Information:

Backtrace was generated from '/usr/libexec/evolution-data-server-1.2'

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)
(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)
(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 -1221239904 (LWP 8817)]
[New Thread -1259344976 (LWP 8854)]
[New Thread -1294992464 (LWP 8853)]
[New Thread -1250952272 (LWP 8843)]
[New Thread -1240667216 (LWP 8841)]
[New Thread -1223787600 (LWP 8818)]
(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)
...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

The backtrace from #5 is a different bug.

This one is this upstream bug and seems to be due to NetworkManager:
http://bugzilla.ximian.com/show_bug.cgi?id=71322

Revision history for this message
Daniel Holbach (dholbach) wrote :

New upstream bug URL is: http://bugzilla.gnome.org/show_bug.cgi?id=271322

Revision history for this message
Daniel Robitaille (robitaille) wrote :

The upstream bug report marks this one as being fixed in the more recent libsoup.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Marking as fixed since dapper has a new version of that package

Changed in libsoup:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.