Trouble allocating fonts in a Tcl/Tk (Python 3.5) based snap

Bug #1709060 reported by Kushal Chauhan
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Snapcraft
New
Undecided
Unassigned

Bug Description

snapcraft version - 2.33
snap - https://github.com/kushalchauhan98/minimal-snip

I am trying to snap a single python3 script.
The code goes something like this: http://paste.ubuntu.com/25262415/

The python script (.py file) runs just fine when executed normally. But when I prime the snap and try it, I get this error on run: http://paste.ubuntu.com/25262438/

The font I am using in my app is the default one offered by tkinter. I haven't chosen any font explicitly to be used in my program.

Initially, I was getting a error which I solved by referring to this question on AskUbuntu (https://askubuntu.com/questions/815511/setting-a-tcl-tk-library-path-inside-a-snap-package).
But now, I am getting this error, which seems to be a snapcraft bug.

Revision history for this message
eike (eikekuehn42) wrote :

snapcraft version - 3.8
core18
python3

I'm trying to snap a python3 tkinter script which runs fine as a python package. I've broken it down to just opening a tk-window which results in a SEGFAULT. Seems to be the same or the evolution of the bug reported above. Will provide a minimal example of the crash this evening.

tags: added: python3 tkinter
Revision history for this message
eike (eikekuehn42) wrote :

I've created a minimal example to reproduce the bug:
https://github.com/randomchars42/snap_python_tkinter_skeleton

Produces:
initialising tk: window = Tk()
done
adding window title: window.title(TEXT)
done
creating a label: label = Label(window)
Segmentation fault (core dumped)

Not sure it's the same though, as it gives a SEGFAULT instead of: "_tkinter.TclError: failed to allocate font due to internal system font engine problem", so I opened a new bug (https://bugs.launchpad.net/snapcraft/+bug/1847321) which might eventually be merged if it proves to be the same.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.