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 727839 - Warnings on startup due to DMAP server start
Warnings on startup due to DMAP server start
Status: RESOLVED FIXED
Product: libdmapsharing
Classification: Other
Component: DAAP Server
git master
Other All
: Normal normal
: ---
Assigned To: W. Michael Petullo
W. Michael Petullo
Depends on:
Blocks:
 
 
Reported: 2014-04-08 15:11 UTC by Bastien Nocera
Modified: 2016-03-02 12:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2014-04-08 15:11:45 UTC 
(rhythmbox:14490): GLib-GObject-CRITICAL **: object SoupServer 0xdd36e0 finalized while still in-construction

libsoup doesn't like that.

+ Trace 233450

  • #0 g_logv
    at gmessages.c line 1038
  • #1 g_log
    at gmessages.c line 1071
  • #2 g_object_finalize
    at gobject.c line 1026
  • #3 g_object_unref
    at gobject.c line 3112
  • #4 soup_server_constructor
    at soup-server.c line 250
  • #5 g_object_new_with_custom_constructor
    at gobject.c line 1645
  • #6 g_object_new_internal
    at gobject.c line 1722
  • #7 g_object_new_valist
    at gobject.c line 1980
  • #8 soup_server_new
    at soup-server.c line 758
  • #9 _dmap_share_server_start
    from /home/hadess/Projects/gnome-install/lib64/libdmapsharing-3.0.so.2
  • #10 daap_share_new
    from /home/hadess/Projects/gnome-install/lib64/libdmapsharing-3.0.so.2
  • #11 create_share
    at rb-daap-sharing.c line 111
  • #12 rb_daap_sharing_init
    at rb-daap-sharing.c line 170
  • #13 impl_activate
    at rb-daap-plugin.c line 206
  • #14 ffi_call_unix64
    from /lib64/libffi.so.6
  • #15 ffi_call
    from /lib64/libffi.so.6
  • #16 g_callable_info_invoke
    at girepository/gicallableinfo.c line 703
  • #17 g_function_info_invoke
    at girepository/gifunctioninfo.c line 281
  • #18 peas_gi_method_call
    at peas-introspection.c line 484
  • #19 peas_extension_callv
    at peas-extension.c line 288
  • #20 peas_extension_call_valist
    at peas-extension.c line 233
  • #21 peas_extension_call
    at peas-extension.c line 186
  • #22 g_closure_invoke
    at gclosure.c line 768
  • #23 signal_emit_unlocked_R
    at gsignal.c line 3551
  • #24 g_signal_emit_valist
    at gsignal.c line 3307
  • #25 g_signal_emit
    at gsignal.c line 3363
  • #26 g_closure_invoke
    at gclosure.c line 768
  • #27 signal_emit_unlocked_R
    at gsignal.c line 3621
  • #28 g_signal_emit_valist
    at gsignal.c line 3307
  • #29 g_signal_emit
    at gsignal.c line 3363
  • #30 peas_engine_set_loaded_plugins
    at peas-engine.c line 1242
  • #31 object_set_property
    at gobject.c line 1378
  • #32 g_object_set_property
    at gobject.c line 2306
  • #33 g_settings_binding_key_changed
    at gsettings.c line 2479
  • #34 g_settings_bind_with_mapping
    at gsettings.c line 2776
  • #35 g_settings_bind
    at gsettings.c line 2604
  • #36 construct_plugins
    at rb-shell.c line 891
  • #37 rb_shell_constructed
    at rb-shell.c line 1752
  • #38 g_object_new_internal
    at gobject.c line 1763
  • #39 g_object_new_valist
    at gobject.c line 1980
  • #40 g_object_new
    at gobject.c line 1571
  • #41 impl_startup
    at rb-application.c line 388
  • #42 _g_closure_invoke_va
    at gclosure.c line 831
  • #43 g_signal_emit_valist
    at gsignal.c line 3215
  • #44 g_signal_emit
    at gsignal.c line 3363
  • #45 g_application_register
    at gapplication.c line 1808
  • #46 impl_local_command_line
    at rb-application.c line 422
  • #47 g_application_run
    at gapplication.c line 2084
  • #48 rb_application_run
    at rb-application.c line 646
  • #49 main
    at main.c line 89 






Comment 1


Bastien Nocera





          2014-04-08 15:12:57 UTC
        



This is bug 719520 but even if not fatal, it should get fixed. Might be a libdmapsharing bug though.






Comment 2


Jonathan Matthew





          2014-04-08 22:27:12 UTC
        



There isn't anything we can do here, this is all happening inside libsoup.






Comment 3


Bastien Nocera





          2014-04-09 16:34:48 UTC
        



Should we reassign to libsoup then?






Comment 4


W. Michael Petullo





          2014-04-30 01:43:51 UTC
        



Well, libdmapsharing tries to call soup_server_new a few times as it tries to listen on IPv6 and IPv4 sockets and tries to use standard and random transport-layer ports. Some of these calls might result in soup_server_new returning NULL, depending on whether IPv6 or the standard ports are available. It looks like this warning is from the GObject infrastructure, and arises when libsoup's soup_server_constructor returns NULL.

Is libsoup's implementation wrong (that is, the way the constructor fails depending on the network conditions)? If so, I think this should be raised as a libsoup bug.






Comment 5


Jonathan Matthew





          2014-07-19 09:36:58 UTC
        




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






Comment 6


Dan Winship





          2014-07-19 09:48:31 UTC
        



In git master SoupServer has new APIs that let you construct first and then listen after so that it doesn't have to fail at construct time






Comment 7


Jonathan Matthew





          2014-07-19 10:10:05 UTC
        



oh, cool.  I'll reassign this to libdmapsharing then.






Comment 8


Sam Thursfield





          2016-02-07 23:19:14 UTC
        



This will be fixed by https://bugzilla.gnome.org/show_bug.cgi?id=761690






Comment 9


Bastien Nocera





          2016-03-02 12:53:01 UTC
        



Marking as fixed as per 761690