Bug 1401181 - Synapse doesn't run on my system
Summary: Synapse doesn't run on my system
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: synapse
Version: 25
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Tonet Jallo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-03 11:02 UTC by Bruno Antunes
Modified: 2017-04-04 13:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-24 14:38:15 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bruno Antunes 2016-12-03 11:02:33 UTC 
Description of problem:

I get this trying to run it:

[INFO 10:59:09.999198] [synapse-main:266] Starting up...
[INFO 10:59:10.108699] [synapse-main:208] Binding activation to <Control>space
fish: “synapse” terminated by signal SIGSEGV (Address boundary error)

Version-Release number of selected component (if applicable):

0.2.99.2-1.fc25

How reproducible:

Always

Steps to Reproduce:
1. Install
2. Run
3. Silently weep as it crashes on you

Actual results:

SIGSEGV

Expected results:

It actually running

Additional info:

I'm using the fish shell, on an AMD system running FC25. Just upgraded from FC24, and it ran fine.
Comment 1 Mamoru TASAKA 2016-12-31 04:17:18 UTC 
If you are using XWayland, try using X (reboot is needed)
Comment 2 Valent Turkovic 2017-01-16 20:00:21 UTC 
After logging into X instead of Wayland I got Synapse to start without Segmantation Fault.

Too bad that both Albert and Synapse fail with Wayland :(
Comment 3 Mamoru TASAKA 2017-04-04 12:49:19 UTC 
If the reporter is still watching this, would you try if 
$ GDK_BACKEND=x11 synapse
works on wayland session?
Comment 4 Bruno Antunes 2017-04-04 13:15:43 UTC 
Thanks for your comment, Mamoru TASAKA, but I don't use Synapse anymore.
Note You need to log in before you can comment on or make changes to this bug.