When enabling XDMCP in GDM in latest F22 ([xdmcp] Enable=true) in /etc/gdm/custom.conf and attaching to GDM, I immediately get the traceback below. It looks like g_object_new is indicating "cannot create instance of abstract (non-instantiatable) type" for GDM_TYPE_XDMCP_DISPLAY - surely that's not expected? (gdb) bt #0 0xb738e5f4 in _g_log_abort (breakpoint=1) at gmessages.c:315 #1 g_logv (log_domain=log_domain@entry=0xb74bcde4 "GLib-GObject", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0xb74c3508 "cannot create instance of abstract (non-instantiatable) type '%s'", args=args@entry=0xbff89ffc ",\344\017\200\344l)\267\a") at gmessages.c:1041 #2 0xb738e6d4 in g_log (log_domain=log_domain@entry=0xb74bcde4 "GLib-GObject", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0xb74c3508 "cannot create instance of abstract (non-instantiatable) type '%s'") at gmessages.c:1079 #3 0xb74b31d5 in g_type_create_instance (type=type@entry=2162303752) at gtype.c:1812 #4 0xb7493270 in g_object_constructor (type=2162303752, n_construct_properties=13, construct_params=0x80e22860) at gobject.c:2059 #7 g_object_new_internal (class=class@entry=0x80e1b7e0, params=params@entry=0xbff8a3cc, n_params=n_params@entry=6) at gobject.c:1772 #8 0xb7495b73 in g_object_new_valist (object_type=object_type@entry=2162303752, first_property_name=first_property_name@entry=0x800f7b18 "remote-hostname", var_args=0xbff8a4c8 "h\267", <incomplete sequence \341\200>, var_args@entry=0xbff8a498 "\360\310ဎy\017\200\001") at gobject.c:2033 #9 0xb7495bf0 in g_object_new (object_type=2162303752, first_property_name=first_property_name@entry=0x800f7b18 "remote-hostname") at gobject.c:1617 #10 0x800dbc48 in gdm_xdmcp_display_new (hostname=hostname@entry=0x80e1c8f0 "127.0.0.1", number=number@entry=1, address=address@entry=0x80e0d310, session_number=75345243) at gdm-xdmcp-display.c:276 #11 0x800d98e9 in gdm_xdmcp_display_create (displaynum=<optimized out>, address=<optimized out>, hostname=<optimized out>, factory=<optimized out>) at gdm-xdmcp-display-factory.c:2149 #12 gdm_xdmcp_handle_request (len=<optimized out>, address=0x80e0d310, factory=0x80dfa190) at gdm-xdmcp-display-factory.c:2390 #13 decode_packet (source=0x80e12f00, cond=G_IO_IN, factory=factory@entry=0x80dfa190) at gdm-xdmcp-display-factory.c:2995 #14 0xb73d25a6 in g_io_unix_dispatch (source=source@entry=0x80e12fd0, callback=0x800d7c20 <decode_packet>, user_data=0x80dfa190) at giounix.c:165 #15 0xb7386d43 in g_main_dispatch (context=0x80df9d50) at gmain.c:3122 #16 g_main_context_dispatch (context=context@entry=0x80df9d50) at gmain.c:3737 #17 0xb7387125 in g_main_context_iterate (context=0x80df9d50, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #18 0xb73874b1 in g_main_loop_run (loop=0x80dfff68) at gmain.c:4002 #19 0x800ba9ab in main (argc=1, argv=0xbff8a934) at main.c:404
Still happening in F23. (gdb) bt #0 0xb72f30b4 in _g_log_abort (breakpoint=1) at gmessages.c:324 #1 g_logv (log_domain=log_domain@entry=0xb7422624 "GLib-GObject", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0xb7428d48 "cannot create instance of abstract (non-instantiatable) type '%s'", args=args@entry=0xbf98aacc "L\027\020\200\200\247\032\267\200\247\032\267\300\345ցO\204\005\267") at gmessages.c:1081 #2 0xb72f3194 in g_log (log_domain=log_domain@entry=0xb7422624 "GLib-GObject", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0xb7428d48 "cannot create instance of abstract (non-instantiatable) type '%s'") at gmessages.c:1119 #3 0xb7418a15 in g_type_create_instance (type=type@entry=2178350640) at gtype.c:1816 #4 0xb73f81a0 in g_object_constructor (type=2178350640, n_construct_properties=13, construct_params=0x81d6f448) at gobject.c:2064 #5 0x800c3da6 in gdm_display_constructor (type=2178350640, n_construct_properties=13, construct_properties=0x81d6f448) at gdm-display.c:1110 #6 0xb73f8545 in g_object_new_with_custom_constructor (n_params=6, params=0xbf98ae9c, class=0x81d72468) at gobject.c:1697 #7 g_object_new_internal (class=class@entry=0x81d72468, params=params@entry=0xbf98ae9c, n_params=n_params@entry=6) at gobject.c:1777 #8 0xb73faaa3 in g_object_new_valist (object_type=object_type@entry=2178350640, first_property_name=first_property_name@entry=0x800faf38 "remote-hostname", var_args=0xbf98af98 "x\213Ձ", var_args@entry=0xbf98af68 "\230'ׁ\256\255\017\200\001") at gobject.c:2038 #9 0xb73fab20 in g_object_new (object_type=2178350640, first_property_name=first_property_name@entry=0x800faf38 "remote-hostname") at gobject.c:1622 #10 0x800df348 in gdm_xdmcp_display_new (hostname=hostname@entry=0x81d72798 "127.0.0.1", number=number@entry=1, address=address@entry=0x81d6e4c8, session_number=1759478523) at gdm-xdmcp-display.c:276 #11 0x800dcfe9 in gdm_xdmcp_display_create (displaynum=<optimized out>, address=<optimized out>, hostname=<optimized out>, factory=<optimized out>) at gdm-xdmcp-display-factory.c:2149 #12 gdm_xdmcp_handle_request (len=<optimized out>, address=0x81d6e4c8, factory=0x81d2d190) at gdm-xdmcp-display-factory.c:2390 #13 decode_packet (source=0x81d45ea0, cond=G_IO_IN, factory=factory@entry=0x81d2d190) at gdm-xdmcp-display-factory.c:2995 #14 0xb7336f16 in g_io_unix_dispatch (source=source@entry=0x81d45ee8, callback=0x800db320 <decode_packet>, user_data=0x81d2d190) at giounix.c:165 #15 0xb72ec0c3 in g_main_dispatch (context=0x81d2ce00) at gmain.c:3154 #16 g_main_context_dispatch (context=context@entry=0x81d2ce00) at gmain.c:3769 #17 0xb72ec4a5 in g_main_context_iterate (context=0x81d2ce00, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3840 #18 0xb72ec831 in g_main_loop_run (loop=0x81d338e0) at gmain.c:4034 #19 0x800be7cb in main (argc=1, argv=0xbf98b404) at main.c:404
I see this is https://bugzilla.gnome.org/show_bug.cgi?id=757714 upstream - would it be possible to bring this one-line patch into F23?
should be possible, but I'm not convinced xdmcp is functional, yet. I need to do some testing.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.