Ask Your Question
0

I get a "segmentation fault" when starting synapse on fedora 25. What to do?

asked 2016-12-15 16:48:16 -0600

Andrei Cristian Petcu gravatar image

Hi,

I just updated to Fedora 25 and I get this error with Synapse.

synapse 
[INFO 00:43:19.635609] [synapse-main:266] Starting up...
[INFO 00:43:19.777342] [synapse-main:208] Binding activation to <Control>space
[1]    10803 segmentation fault (core dumped)  synapse

What can I do?

edit retag flag offensive close merge delete

3 Answers

Sort by » oldest newest most voted
0

answered 2017-01-10 11:34:24 -0600

It's solvable., I posted about it here:

https://iamthinkking.github.io/2017/0...

SOLUTION I figured it was synapse trying to access memory or a stream that doesn't exist. So I checked synapse -h to see what options are available. One of the options available to use --display. You can get synapse to successfully start by the following steps.

  1. check the location of the displays you have available: cd /tmp/.X11-unix && for x in X*; do echo ":${x#X}"; done
  2. then, from the locations listed, try using any as arguments to the --display option.

For me, synapse --display=:0 worked just fine.

NB: This allows you to manually launch synapse. However, you MAY want to ensure that:

  1. When you start synapse from the application menu it launches with the options you desire.

    append --display=:0 to the end of Exec=synapse in the file /usr/share/applications/synapse.desktop. You WILL need sudo access to do this. Be mindful of the space in the string you will be appending.

  2. If it's autostarted from your startup it is launched with the options you desire.

    ensure you have GNOME Tweak Tool installed. Install it using sudo dnf install gnome-tweak-tool or install it from the Software application. Then navigate: Tweak Tool>Startup Applications>➕. Search for Synapse then click "Add".

  3. Navigate Settings>Keyboard>➕. Enter Name: "Synapse", Command: "synapse --display=:0", Shortcut: [Whatever keyboard shortcut you desire].

This should suffice as a solution until a patch is made.

edit flag offensive delete link more

Comments

Is this with a Wayland gnome session, or X?

randomuser gravatar imagerandomuser ( 2017-01-10 14:55:25 -0600 )edit

Try it with either. It works for me on both.

iamthinkking gravatar imageiamthinkking ( 2017-01-11 22:04:42 -0600 )edit
0

answered 2016-12-16 07:04:26 -0600

hhlp gravatar image

you only options is open a ticket in bugzilla.redhat. an provide all the usefull information there

regards.,

edit flag offensive delete link more
0

answered 2016-12-16 09:02:36 -0600

CAI Qian gravatar image

Find out the location of the call. Normally, something like core.xxx in the root directory. Then you can use gdb to analyse the core with the debug symbols to get something useless lie backtrace, and starts from there.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2016-12-15 16:48:16 -0600

Seen: 452 times

Last updated: Jan 10 '17