[Bug 294107] x11/xedit fails to launch

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294107

            Bug ID: 294107
           Summary: x11/xedit fails to launch
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
          Assignee: [email protected]
             Flags: maintainer-feedback?([email protected])

xed 3.8.5 fails to launch with the following errors:

/usr/local/lib/python3.11/site-packages/gi/module.py:50: Warning: cannot
register existing type 'GIRepository'
repository = Repository.get_default()
/usr/local/lib/python3.11/site-packages/gi/module.py:50: Warning:
g_once_init_leave_pointer: assertion 'result != 0' failed
repository = Repository.get_default()
/usr/local/lib/python3.11/site-packages/gi/module.py:50: Warning:
g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT
(object_type)' failed
repository = Repository.get_default()

No window appears. Process exits with code 1.

When launched via D-Bus with an existing stale registration, the error is:
"Failed to register: Timeout was reached"

After killing the stale instance, the GIRepository errors appear.

Affected packages (same versions in quarterly, latest, and ports):
* xed-3.8.5
* py311-pygobject-3.54.5_1
* gobject-introspection-1.84.0,1

Workarounds attempted (none successful):
* pkg install -f xed py311-pygobject gobject-introspection
* Rebuilding from ports
* XED_PLUGINS_PATH=/dev/null xed
* GI_TYPELIB_PATH="" xed --standalone
* PYTHONPATH="" GI_TYPELIB_PATH="" xed

System: FreeBSD 14.4-RELEASE-p1, amd64

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.