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 794809 - Crash in open file dialog
Crash in open file dialog
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Quartz
3.22.x
Other Mac OS
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
: 796045 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2018-03-29 12:57 UTC by Christoph Rohland
Modified: 2018-05-12 14:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Crash dump (86.42 KB, text/plain)
2018-03-29 12:57 UTC, Christoph Rohland 		Details
Trace file (500 bytes, text/plain)
2018-03-29 12:59 UTC, Christoph Rohland 		Details

Description Christoph Rohland 2018-03-29 12:57:42 UTC 
Created attachment 370295 [details]
Crash dump

Hitting any key in the Open File Dialog will crash Gnucash 2.7.8
Comment 1 Christoph Rohland 2018-03-29 12:59:02 UTC 
Created attachment 370296 [details]
Trace file
Comment 2 John Ralls 2018-03-29 20:10:14 UTC 
Seems to be Mac-only and a problem with the Gtk file chooser rather than with GnuCash.
Comment 3 Frank H. Ellenberger 2018-04-04 18:26:00 UTC 
Are all Mac versions affected? Above crash dump says: Mac OS X 10.13.3 (17D102)
Comment 4 John Ralls 2018-04-05 00:28:46 UTC 
I haven't tested on all (supported) Mac versions, but I can't think of any reason it would matter.
Comment 5 John Ralls 2018-04-28 18:47:33 UTC 
This is an implementation mismatch between submitHits in gncsearchenginequartz.c, which sends a char* of the path, and hits_added in gtksearchengine.c that expects a GtkSearchHit*. Trying to dereference a char* naturally crashes.
Comment 6 Christoph Reiter (lazka) 2018-04-28 19:07:16 UTC 
Could this be related? https://gitlab.gnome.org/GNOME/pygobject/issues/161
Comment 7 John Ralls 2018-04-28 19:33:54 UTC 
Only insofar as the crashes have the same user trigger. This crash is a segfault cause by trying to use the contents of a string as a pointer. 

The python crash is due to an uncaught transcoding exception. I don't know what is encoding 30 but I'd guess that it's not UTF8 (which is must be to interface with gtk and glib) and that there's a character in the file path that can't be represented in that encoding.
Comment 8 GNOME Infrastructure Team 2018-05-02 19:57:33 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/1043.
Comment 9 John Ralls 2018-05-12 14:08:50 UTC 
*** Bug 796045 has been marked as a duplicate of this bug. ***