I’ve been running Gramps 5.2.2 since it was released, so thought it was time to move to v5.2.3
Gramps 5.2.3 seems to run fine, but the font is really ugly. So I installed the “Theme” add on in order to change font. But as soon as I try to select a font Gramps crashes. MacOS creates a crash report. To me it looks like a null pointer.
So now I’m back on version 5.2.2
Should note that v5.2.2 was installed by downloading the dmg file, while v5.2.3 was installed via Homebrew.
MacOS: Ventura 13.7 on Intel
Regards
Claus
Since you downloaded 5.2.2 as a dmg I suggest you continue and get the 5.2.3 dmg and not use Homebrew. Mixing install processes can get tricky. You should remove the gramps homebrew install completely before installing from dmg.
Instructions from Gramps – Free Genealogy Software » Download for downloading the dmg are:
Removed the Homebrew installed v5.2.3 and installed using dmg.
Same results - v5.2.3 font not very readable, and Theme crashes Gramps.
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Gramps [49135]
Path: /Applications/Gramps.app/Contents/MacOS/Gramps
Identifier: org.gramps-project.gramps
Version: Gramps-5.2.3-1 (Gramps-5.2.3-1)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2024-10-22 17:46:42.9346 +0200
OS Version: macOS 13.7 (22H123)
Report Version: 12
Anonymous UUID: 14595DAC-CA8E-D678-BE0F-00AD30E87243
Sleep/Wake UUID: 2A30BF55-23C3-44F9-98D8-8785F31EA750
Time Awake Since Boot: 210000 seconds
Time Since Wake: 20318 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [49135]
VM Region Info: 0 is not in any region. Bytes before following region: 4528857088
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 10df0e000-10df12000 [ 16K] r-x/r-x SM=COW .../MacOS/Gramps
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 CoreFoundation 0x7ff817c17396 CFNumberGetValue + 31
1 libpangocairo-1.0.0.dylib 0x112813a13 _pango_core_text_font_description_from_ct_font_descriptor + 211
2 libpangocairo-1.0.0.dylib 0x11281343f pango_core_text_font_describe + 31
3 libpango-1.0.0.dylib 0x11231e855 pango_itemize_post_process_items + 213
4 libpango-1.0.0.dylib 0x11232c360 pango_layout_check_lines + 960
5 libpango-1.0.0.dylib 0x1123322bb pango_layout_get_extents_internal + 43
6 libpango-1.0.0.dylib 0x1123326e8 pango_layout_get_pixel_extents + 120
7 libgtk-3.0.dylib 0x117a1cce1 get_size + 449
8 libgtk-3.0.dylib 0x117a1be11 gtk_cell_renderer_text_render + 113
9 libgtk-3.0.dylib 0x117a12384 gtk_cell_renderer_render + 292
10 libgtk-3.0.dylib 0x117a098a0 render_cell + 192
11 libgtk-3.0.dylib 0x117a0b441 gtk_cell_area_box_foreach_alloc + 1953
12 libgtk-3.0.dylib 0x117a0932f gtk_cell_area_real_render + 191
13 libgtk-3.0.dylib 0x117c73290 _gtk_tree_view_column_cell_render + 208
14 libgtk-3.0.dylib 0x117c6a4b5 draw_bin + 3909
15 libgtk-3.0.dylib 0x117b7e735 _gtk_pixel_cache_draw + 1845
16 libgtk-3.0.dylib 0x117c650a6 gtk_tree_view_draw + 246
17 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
18 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
19 libgtk-3.0.dylib 0x117a3ab03 gtk_container_draw + 211
20 libgtk-3.0.dylib 0x117bb23fd gtk_scrolled_window_render + 349
21 libgtk-3.0.dylib 0x117a42a55 gtk_css_custom_gadget_draw + 37
22 libgtk-3.0.dylib 0x117a484c2 gtk_css_gadget_draw + 1474
23 libgtk-3.0.dylib 0x117baeae1 gtk_scrolled_window_draw + 17
24 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
25 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
26 libgtk-3.0.dylib 0x117a3ab03 gtk_container_draw + 211
27 libgtk-3.0.dylib 0x117add445 gtk_grid_render + 37
28 libgtk-3.0.dylib 0x117a42a55 gtk_css_custom_gadget_draw + 37
29 libgtk-3.0.dylib 0x117a484c2 gtk_css_gadget_draw + 1474
30 libgtk-3.0.dylib 0x117adc8b1 gtk_grid_draw + 17
31 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
32 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
33 libgtk-3.0.dylib 0x117bd0fc2 gtk_stack_render + 1826
34 libgtk-3.0.dylib 0x117a42a55 gtk_css_custom_gadget_draw + 37
35 libgtk-3.0.dylib 0x117a484c2 gtk_css_gadget_draw + 1474
36 libgtk-3.0.dylib 0x117bcf505 gtk_stack_draw + 21
37 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
38 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
39 libgtk-3.0.dylib 0x117a3ab03 gtk_container_draw + 211
40 libgtk-3.0.dylib 0x117add445 gtk_grid_render + 37
41 libgtk-3.0.dylib 0x117a42a55 gtk_css_custom_gadget_draw + 37
42 libgtk-3.0.dylib 0x117a484c2 gtk_css_gadget_draw + 1474
43 libgtk-3.0.dylib 0x117adc8b1 gtk_grid_draw + 17
44 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
45 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
46 libgtk-3.0.dylib 0x117bd0fc2 gtk_stack_render + 1826
47 libgtk-3.0.dylib 0x117a42a55 gtk_css_custom_gadget_draw + 37
48 libgtk-3.0.dylib 0x117a484c2 gtk_css_gadget_draw + 1474
49 libgtk-3.0.dylib 0x117bcf505 gtk_stack_draw + 21
50 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
51 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
52 libgtk-3.0.dylib 0x117a3ab03 gtk_container_draw + 211
53 libgtk-3.0.dylib 0x1179ec265 gtk_box_draw_contents + 37
54 libgtk-3.0.dylib 0x117a42a55 gtk_css_custom_gadget_draw + 37
55 libgtk-3.0.dylib 0x117a484c2 gtk_css_gadget_draw + 1474
56 libgtk-3.0.dylib 0x1179eb5d1 gtk_box_draw + 17
57 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
58 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
59 libgtk-3.0.dylib 0x117a3ab03 gtk_container_draw + 211
60 libgtk-3.0.dylib 0x1179ec265 gtk_box_draw_contents + 37
61 libgtk-3.0.dylib 0x117a42a55 gtk_css_custom_gadget_draw + 37
62 libgtk-3.0.dylib 0x117a484c2 gtk_css_gadget_draw + 1474
63 libgtk-3.0.dylib 0x1179eb5d1 gtk_box_draw + 17
64 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
65 libgtk-3.0.dylib 0x117a3a41b gtk_container_propagate_draw + 475
66 libgtk-3.0.dylib 0x117a3ab03 gtk_container_draw + 211
67 libgtk-3.0.dylib 0x117ca083b gtk_window_draw + 747
68 libgtk-3.0.dylib 0x117c7f05c gtk_widget_draw_internal + 396
69 libgtk-3.0.dylib 0x117c802d0 gtk_widget_render + 288
70 libgtk-3.0.dylib 0x117b24cff gtk_main_do_event + 1919
71 libgdk-3.0.dylib 0x1128ef4e1 _gdk_event_emit + 49
72 libgdk-3.0.dylib 0x11290169e _gdk_window_process_updates_recurse_helper + 318
73 libgdk-3.0.dylib 0x11291190b -[GdkQuartzView updateLayer] + 203
74 AppKit 0x7ff81add81e1 _NSViewUpdateLayer + 98
75 AppKit 0x7ff81acff572 +[NSAppearance _performWithCurrentAppearance:usingBlock:] + 66
76 AppKit 0x7ff81af2ae34 __30-[_NSViewBackingLayer display]_block_invoke + 113
77 AppKit 0x7ff81ad39de1 -[NSFocusStack performWithFocusView:inWindow:usingBlock:] + 92
78 AppKit 0x7ff81add7b99 -[_NSViewBackingLayer display] + 383
79 QuartzCore 0x7ff81f541a64 CA::Layer::display_if_needed(CA::Transaction*) + 856
80 QuartzCore 0x7ff81f6c8d47 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 645
81 QuartzCore 0x7ff81f522b5f CA::Transaction::commit() + 713
82 AppKit 0x7ff81ae7079f __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285
83 AppKit 0x7ff81b683dac ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
84 CoreFoundation 0x7ff817c753c4 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
85 CoreFoundation 0x7ff817c752eb __CFRunLoopDoObservers + 482
86 CoreFoundation 0x7ff817c74876 __CFRunLoopRun + 859
87 CoreFoundation 0x7ff817c73eb1 CFRunLoopRunSpecific + 560
88 HIToolbox 0x7ff8216fef3d RunCurrentEventLoopInMode + 292
89 HIToolbox 0x7ff8216feb84 ReceiveNextEventCommon + 199
90 HIToolbox 0x7ff8216feaa8 _BlockUntilNextEventMatchingListInModeWithFilter + 64
91 AppKit 0x7ff81ad11d08 _DPSNextEvent + 858
92 AppKit 0x7ff81ad10bb2 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1214
93 libgdk-3.0.dylib 0x11291aa9a poll_func + 186
94 libglib-2.0.0.dylib 0x110b446fc g_main_context_iterate_unlocked + 508
95 libglib-2.0.0.dylib 0x110b447e8 g_main_context_iteration + 104
96 libgio-2.0.0.dylib 0x112a7fc9d g_application_run + 589
97 libffi.8.dylib 0x10e4b1cfa ffi_call_unix64 + 82
98 libffi.8.dylib 0x10e4b112c ffi_call_int + 828
99 libffi.8.dylib 0x10e4b0dbf ffi_call + 207
100 _gi.cpython-311-darwin.so 0x11093cf6f pygi_invoke_c_callable + 2255
101 _gi.cpython-311-darwin.so 0x11093df17 pygi_function_cache_invoke + 55
102 libpython3.11.dylib 0x10e53108d _PyObject_Call + 141
103 libpython3.11.dylib 0x10e625c1b _PyEval_EvalFrameDefault + 64891
104 libpython3.11.dylib 0x10e615c3f PyEval_EvalCode + 191
105 libpython3.11.dylib 0x10e66e47e _PyRun_SimpleFileObject + 1086
106 libpython3.11.dylib 0x10e66eeb5 PyRun_SimpleFileExFlags + 53
107 Gramps 0x10df11adf main + 1375
108 dyld 0x7ff81783f418 start + 1896
Thread 1:
0 libsystem_pthread.dylib 0x7ff817b95bb0 start_wqthread + 0
Thread 2:
0 libsystem_pthread.dylib 0x7ff817b95bb0 start_wqthread + 0
Thread 3:: pool-spawner
0 libsystem_kernel.dylib 0x7ff817b5e08e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x7ff817b9a758 _pthread_cond_wait + 1242
2 libglib-2.0.0.dylib 0x110ba2136 g_cond_wait + 38
3 libglib-2.0.0.dylib 0x110b0ca95 g_async_queue_pop_intern_unlocked + 133
4 libglib-2.0.0.dylib 0x110b73a88 g_thread_pool_spawn_thread + 72
5 libglib-2.0.0.dylib 0x110b73522 g_thread_proxy + 66
6 libsystem_pthread.dylib 0x7ff817b9a1d3 _pthread_start + 125
7 libsystem_pthread.dylib 0x7ff817b95bd3 thread_start + 15
Thread 4:: gmain
0 libsystem_kernel.dylib 0x7ff817b64222 __select + 10
1 libglib-2.0.0.dylib 0x110b5685a g_poll + 554
2 libglib-2.0.0.dylib 0x110b446fc g_main_context_iterate_unlocked + 508
3 libglib-2.0.0.dylib 0x110b447e8 g_main_context_iteration + 104
4 libglib-2.0.0.dylib 0x110b46270 glib_worker_main + 80
5 libglib-2.0.0.dylib 0x110b73522 g_thread_proxy + 66
6 libsystem_pthread.dylib 0x7ff817b9a1d3 _pthread_start + 125
7 libsystem_pthread.dylib 0x7ff817b95bd3 thread_start + 15
Thread 5:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x7ff817b5b552 mach_msg2_trap + 10
1 libsystem_kernel.dylib 0x7ff817b696cd mach_msg2_internal + 78
2 libsystem_kernel.dylib 0x7ff817b62584 mach_msg_overwrite + 692
3 libsystem_kernel.dylib 0x7ff817b5b83a mach_msg + 19
4 CoreFoundation 0x7ff817c75fef __CFRunLoopServiceMachPort + 145
5 CoreFoundation 0x7ff817c74a70 __CFRunLoopRun + 1365
6 CoreFoundation 0x7ff817c73eb1 CFRunLoopRunSpecific + 560
7 AppKit 0x7ff81ae71f55 _NSEventThread + 132
8 libsystem_pthread.dylib 0x7ff817b9a1d3 _pthread_start + 125
9 libsystem_pthread.dylib 0x7ff817b95bd3 thread_start + 15
Thread 6:
0 libsystem_kernel.dylib 0x7ff817b5e08e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x7ff817b9a758 _pthread_cond_wait + 1242
2 libgdk-3.0.dylib 0x11291bb33 select_thread_func + 67
3 libsystem_pthread.dylib 0x7ff817b9a1d3 _pthread_start + 125
4 libsystem_pthread.dylib 0x7ff817b95bd3 thread_start + 15
Thread 7:
0 libsystem_pthread.dylib 0x7ff817b95bb0 start_wqthread + 0
Thread 8:: CVDisplayLink
0 libsystem_kernel.dylib 0x7ff817b5e08e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x7ff817b9a78d _pthread_cond_wait + 1295
2 CoreVideo 0x7ff81fcc21c8 CVDisplayLink::waitUntil(unsigned long long) + 370
3 CoreVideo 0x7ff81fcc1148 CVDisplayLink::runIOThread() + 526
4 libsystem_pthread.dylib 0x7ff817b9a1d3 _pthread_start + 125
5 libsystem_pthread.dylib 0x7ff817b95bd3 thread_start + 15
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0xc5e76b50267f00ee rbx: 0x00006000007d9600 rcx: 0x00000000000007c8 rdx: 0x00007ff7b1feba28
rdi: 0x0000000000000000 rsi: 0x0000000000000004 rbp: 0x00007ff7b1feba00 rsp: 0x00007ff7b1feb970
r8: 0x0000000000000015 r9: 0x00007ff819af1c3f r10: 0x00007ff819af1c3e r11: 0x83dec1d2251f8926
r12: 0x0000600001e14390 r13: 0x0000000000000000 r14: 0x0000600003780420 r15: 0x00006000007d9bc0
rip: 0x00007ff817c17396 rfl: 0x0000000000010246 cr2: 0x0000000000000000
Logical CPU: 2
Error Code: 0x00000004 (no mapping for user data read)
Trap Number: 14
Thread 0 instruction stream:
42 48 23 17 48 39 f2 74-c3 48 8b 35 7a ad ed 42 BH#.H9.t.H.5z..B
48 89 c7 48 89 da ff 15-3e d6 ed 42 48 8b 0d df H..H....>..BH...
d4 ed 42 48 8b 09 48 3b-4d e8 75 10 0f b6 c0 48 ..BH..H;M.u....H
83 c4 30 5b 41 5e 5d c3-31 c0 eb e0 e8 c9 c2 1b ..0[A^].1.......
00 55 48 89 e5 48 81 ec-90 00 00 00 48 8b 05 af .UH..H......H...
d4 ed 42 48 8b 00 48 89-45 f8 40 f6 c7 01 75 33 ..BH..H.E.@...u3
[48]8b 07 48 85 c0 74 10-4c 8b 05 0b 95 8f 41 4c H..H..t.L.....AL <==
39 c0 0f 85 aa 00 00 00-48 85 d2 48 8d 85 70 ff 9.......H..H..p.
ff ff 48 0f 45 c2 48 89-c2 e8 10 2f 03 00 e9 09 ..H.E.H..../....
01 00 00 48 8b 05 b8 d5-ed 42 4c 8b 08 49 31 f9 ...H.....BL..I1.
44 89 c8 d1 e8 83 e0 07-44 89 c9 c1 e9 04 0f b6 D.......D.......
c9 48 83 c1 08 83 f8 07-48 0f 45 c8 83 f9 03 75 .H......H.E....u
Could you do some troubleshooting so a proper bug report can be filed for the 5.2.3 homebrew installation?
Start gramps from the terminal. The crash should write errors to the terminal. Then post the errors.
Google ai overview response to prompt : “start gramps from command line on macos”
To open Terminal, you can:
Click the Launchpad icon in the Dock, type Terminal in the search field, and then click Terminal
Open the /Applications/Utilities folder in the Finder, and then double-click TerminalYou can also open new Terminal windows by pressing Command-N or choosing Shell > New Window > New Window with Profile.
Unfortunately, on a Mac if it core dumps (like this case), there is no other information even from the console window.
I loaded the ARM version on my Apple Silicon running Sonoma 14.6.1 and it worked as expected - with and without the Theme addon. No issues.
So, can you tell me if you have an Apple Silicon machine or an older Intel-based system. The Code Type in the dump says you are running the version of gramps for the older Intel machines. What exactly is your hardware? If you loaded the Intel version on an Apple Silicon machine, the fonts will be weird. And a dump would not surprise me.
1 Like
My Mac is an older iMac Retina 5K, 27-inch with 3.4 GHz quad core Intel Core i5 with 40 GB RAM running macOS Ventura 13.7
It’s the Intel version of Gramps, that I have installed.
@GaryGriffin Did you try to change font in Theme? It’s when I try to select another font the crash happens.
I installed 5.2.3 on my Intel Mac running Mojave. It is older than your system.
I loaded the Theme plugin and ran it. I changed all of the options in the plugin and they worked fine. I could not crash it.
My suggestion - file a bug and attach the core dump. Assign to jralls as he built the dmg.
I cannot reproduce this.
Themes previously demonstrated problems building the Font menu on my Windows box when the OS had too many Font families installed.
This makes me dubious of that add-on’s ability to deal with a complex font ecology. But that suspicion is mitigated by the OS not changing between the 5.2.2 and 5.2.3 installers. But if there are any font installation cleaners, they are worth trying. (After a backup, of course.)
But maybe there’s a difference between the builds of the .dmg files. (We should ignore the Homebrew as a ‘distraction’ since the 5.2.3 .dmg presents with the same problem on Claus’ system.)
I prompted Perplexity:
are there tools for cleaning up font installations on a Ventura macOS
Based on the search results and the context provided, there are indeed tools and methods for cleaning up font installations on macOS Ventura. Here are some key approaches:
-
Terminal Commands:
- The most recommended method is using the Terminal command:
atsutil databases -removeUser - This command clears the user font cache without affecting system fonts.
- After running this command, it’s advised to restart the Mac to allow the system to rebuild the font cache.
- The most recommended method is using the Terminal command:
-
Font Book:
- macOS’s built-in Font Book application can be used to manage fonts.
- You can use it to validate fonts, remove duplicates, and manage font collections.
-
Third-Party Software:
- While not specifically mentioned for Ventura, some users might still use third-party font management tools. However, the native methods are generally preferred.
-
Safe Mode:
- Restarting the Mac in Safe Mode and then restarting normally can help clear font caches, especially if you don’t want to use Terminal commands.
-
Manual Removal:
- For specific font issues, manually removing font files from the user’s Library folder (~/Library/Fonts) can be effective.
-
Font Smoothing Adjuster:
- While not directly related to cleaning up installations, this tool can help adjust font rendering, which might resolve some font-related issues.
Important Notes:
- In Ventura (and since Monterey), the system font cache is in a read-only part of the drive and can’t be directly modified by users.
- The older command
sudo atsutil databases -removeis no longer effective or necessary for user-level font cache clearing. - After any font cache clearing operation, a system restart is recommended.
For your specific issue with installing third-party OTF fonts, if the above methods don’t help, you might want to check:
- Font file permissions
- Potential conflicts with existing fonts
- Any system-wide font restrictions that might be in place
Remember to always back up your fonts before making significant changes to your font system.
Citations:
[1] Clear Mac OS X Font Caches · GitHub
[2] Clear Font Cache/Ventura - Apple Community
[3] https://help.extensis.com/hc/en-us/articles/9491628439963-Finding-and-removing-Type-1-fonts-on-macOS
[4] Clean Font Cache (Ventura) - Scripting - Glyphs Forum
[5] https://www.fontsmoothingadjuster.com
[6] Reddit - Dive into anything
[7] Clearing the macOS font cache - Typeface App
[8] List of typefaces included with macOS - Wikipedia
For future reference, Homebrew does NOT build or package Gramps. They simply provide another way to install the .dmg prepared by the Gramps project. That’s why the OP experienced the same result with install methods that appear to be different (but aren’t).
Craig
Not all fonts are created equal. Do you have some third party fonts installed? When you select another font, did you select a basic, system-installed option?
Is your system set to English-US or something else?
Craig
In Grams v5.2.2 I can change font settings using Theme without any problems.
So the problem is only on v5.2.3
My Mac is running US-English, but with some settings changed, for example decimal point is comma and standard date format is dd/mm/yyyy.
Now, after changing font in v5.2.2 v5.2.3 starts up using the font setting from v5.2.2. That is actually fine, because now I have a much better look in v5.2.3
The crash still happens when trying to change font in v5.2.3. One thing I noticed is that the crash can happen just scrolling the drop down list of available fonts.
It sounds like you have a workaround - use 5.2.2 to select the font and do not change in 5.2.3 .
To actually solve this, I think the only option is to submit the bug with the SW info (OS) HW info (5K, Retina, Intel, …) and the core. jralls will know if a different gtk library was used in the dmg creation, for instance.
You might want to try on 5.2.2 to reset Themes to default and then seeing if it works in 5.2.3. Add to bug if it doesnt.
I dont see anything in the 5.2.3 relnotes other than Packaging for MacOS that might have impacted this. The Addon was not changed. The OS was not changed. But the dmg is a bundle with all of the gtk libraries.
This is when the addon is building a list of installed fonts. You might have a glitch in your system’s fonts. It might not be a critical failure but is still too much for the standard request for fonts.
Did you try using the OS Font Book application to revalidate your installed fonts?
The libraries for 5.2.3 might have been updated and have gained a weakness. But compensating for an invalid font is outside of Gramps’ responsibilities.
- Open Finder
- Go to Applications folder
- Locate and double-click on Font Book
- Trigger cleanup and revalidation:
- With Font Book open, click on “File” in the top menu bar
- Select “Validate Fonts” from the dropdown menu
- In the dialog box that appears, click “Validate”
Font Book will scan and check all installed fonts
1 Like
Running Font Book ‘Validate’ 17 font files was found “Serious errors - do not use”. Of the 17 files 13 was from Gimp, so I talked to Gimp people, and they said these files were some left overs, that are no longer being used. So I deleted these files. The last 4 files came from Apple’s iMovie !! which I have uninstalled.
The crash still happens in v5.2.3
Since the Theme add-on runs ok in v5.2.2, and I believe it’s the same Theme code being run in both v5.2.2 and v5.2.3, I think the problem must be somewhere in the v5.2.3 code.
Question: Is v5.2.2 and v5.2.3 using the same Python version?
The Mac bundle appears to be using python 3.11 since Gramps 5.1.
1 Like
@csam
Please try the Notes Editor to determine if it has any problem building a Font Family menu with your collection of Fonts.
@Nick-Hall
Based on subjective latency, the Themes add-on seems to be far less efficient at building a menu of installed Font Families than the Note Editor. Do you have any suggestion for improving it?
The Themes add-on uses a Gtk.FontButton widget which is a sensible choice.
The Note Editor gets the list from the pango context of a Gtk.TextView widget. This list is stored to overcome a long since fixed Gtk bug.
1 Like
This posting for another tool (from 6 year ago) notes an interesting similar behavior where using the Gtk.FontButton widget with different Themes has different failures.
In their report, an exit occurred with Adwaita theme. But when using Raleigh theme, a critical Gtk error is emitted.
@csam Can you try switching Themes and see if the error persists then selecting a font family?