Opened 6 years ago
Closed 5 months ago
#61163 closed defect (fixed)
emacs @27.1_1 +x11: GLib-GIO-CRITICAL error/warning when running
| Reported by: | zalondek | Owned by: | drkp (Dan Ports) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.3 |
| Keywords: | Cc: | cooljeanius (Eric Gallager) | |
| Port: | emacs |
Description (last modified by jmroot (Joshua Root))
From an empty macports install on Mojave:
$ sudo port install emacs +x11 $ emacs (process:88042): GLib-GIO-CRITICAL **: 08:46:51.945: g_settings_schema_source_lookup: assertion 'source != NULL' failed $ ps -elf | grep 88042 750 88042 22860 4006 0 31 0 5088004 38284 - S 0 ttys001 0:00.30 emacs 1:38PM
Emacs still appears to run - I'm not sure of the implications of this error/warning.
Change History (8)
comment:1 Changed 6 years ago by jmroot (Joshua Root)
| Owner: | set to drkp |
|---|---|
| Port: | +x11 removed |
| Status: | new → assigned |
| Summary: | GLib-GIO-CRITICAL error/warning when running emacs installed with +x11 → emacs @27.1_1 +x11: GLib-GIO-CRITICAL error/warning when running |
comment:2 Changed 6 years ago by jmroot (Joshua Root)
| Description: | modified (diff) |
|---|
comment:3 Changed 6 years ago by kencu (Ken)
comment:4 Changed 6 years ago by kencu (Ken)
and that suggests adding this port may fix that error:
gsettings-desktop-schemas
comment:5 Changed 6 years ago by kencu (Ken)
and yes indeed that fixes the error (not sure if it does anything else, but the error disappears).
comment:6 Changed 6 years ago by drkp (Dan Ports)
Seems like emacs +x11 is building with gsettings support. That's unexpected (to me, at least), and I'm trying to decide what the right behavior is there. Only use gsettings with +gtk?
comment:7 Changed 4 years ago by cooljeanius (Eric Gallager)
| Cc: | cooljeanius added |
|---|
comment:8 Changed 5 months ago by drkp (Dan Ports)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.

Looks related to <https://github.com/NixOS/nixpkgs/issues/23845>