← Back to issue list

FLTK applications cannot start

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1697473
Type
issue
State
open
Author
~msweet
Labels
—
Created
Updated
Closed
—

Current evaluation

FLTK launch failures were configuration-related; the reporter confirmed desktop-gtk3, an after dependency, and desktop-launch $SNAP/bin/<cmd> fixed both apps.

Suggested action: close not a bug

Reason: A maintainer diagnosed the errors as an unconfigured desktop runtime environment, and the reporter later confirmed that using desktop-launch with an absolute $SNAP command path resolved the launch failure. Current documentation also covers desktop-launch and desktop helper parts, so this was a snap recipe configuration issue rather than a Snapcraft defect.

Evaluated by: mr-cal-bot

Impact: 25 Quick Win: 18 Complexity: 20 Confidence: 96 Actionability: 90

Issue body

Hi, I'm trying to create snaps for two FLTK-based applications I maintain (rasterview and HTMLDOC) but when I run these applications I get two error messages: XOpenIM() failed Unable to find fonts. Check your FontConfig configuration. Both applications list the "x11" and "unity7" interfaces in the plugs: value in snapcraft.yaml, but neither will open a window. (HTMLDOC also has a command-line mode, and that works just fine...) The projects are hosted on Github: https://github.com/michaelrsweet/htmldoc https://github.com/michaelrsweet/rasterview

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 25
Quick Win: 18
Complexity: 20
Confidence: 96
Actionability: 90
close not a bug FLTK launch failures were configuration-related; the reporter confirmed desktop-gtk3, an after dependency, and desktop-launch $SNAP/bin/<cmd> fixed both apps.
stealth/space-bunny-alpha
Impact: 12
Quick Win: 8
Complexity: 8
Confidence: 84
Actionability: 72
close not a bug FLTK snaps failed with 'XOpenIM() failed' / 'Unable to find fonts' because the runtime environment wasn't set; resolved via desktop-gtk3 part + desktop-launch $SNAP/bin/<cmd>, now handled by the gnome extension
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 7
Complexity: 40
Confidence: 50
Actionability: 40
keep open FLTK applications fail to start in snaps due to XOpenIM and FontConfig errors; issue is 9+ years old with no maintainer response.
qwen/qwen3.8-27b
Impact: 15
Quick Win: 9
Staleness: 92
Complexity: 40
Confidence: 70
Support Request: 65
close stale 2017 report that FLTK apps (rasterview, HTMLDOC) fail to start in snaps with XOpenIM and fontconfig errors. Zero comments, no labels, no maintainer activity for ~8.6 years; references the since-removed unity7 interface.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 25
Confidence: 90
Support Request: 90
close stale User reports FLTK apps failing to start in snaps with X11 and FontConfig errors. Issue is 9 years old, has no comments, and lacks maintainer triage. Likely obsolete due to significant snapcraft ecosystem changes.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 85
close stale FLTK apps fail to start in snaps with XOpenIM and fontconfig errors. Issue is 9 years old, has no maintainer response, references deprecated unity7 interface, and remains unresolved.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 90
Support Request: 85
close stale User reports FLTK snap applications failing to start with X11 and FontConfig errors. Issue is over 9 years old, references the deprecated unity7 interface, and has no maintainer response.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.