# Segmentation fault core dump

**URL:** <https://forums.synfig.org/t/segmentation-fault-core-dump/4387>\
**Category:** Debugging\
**Created:** [March 5, 2018, 5:42pm UTC](https://forums.synfig.org/t/segmentation-fault-core-dump/4387 "2018-03-05T17:42:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![alfonso.nishikawa](https://forums.synfig.org/user_avatar/forums.synfig.org/alfonso.nishikawa/32/4141_2.png) [@alfonso.nishikawa](https://forums.synfig.org/u/alfonso.nishikawa)\
**Post date:** [March 5, 2018, 5:42pm UTC](https://forums.synfig.org/t/segmentation-fault-core-dump/4387/1 "2018-03-05T17:42:45Z")

</div>

Hi!

I am using Synfig 1.2.1 in Linux and I am getting segmentation fault core dump now and then each time I am using the application without doing any special action.

I attach my project, that comprises two animations.  
I suspect maybe could be related to this file:

`Thunar: Failed to open "/tmp/.mount_GiIvLf/usr/GoraExplorer web snapshot.png": Error when getting information for file '/tmp/.mount_GiIvLf/usr/GoraExplorer web snapshot.png': No such file or directory
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
synfig(17732) [15:56:18] error: synfig::save_canvas(): Unable to open file for write
synfig(17732) [15:56:18] info: Attempting to import /home/alfonso/Documentos/goraexplorer/Introduction to GoraExplorer alpha/Animations/GoraExplorer web snapshot.png
synfig(17732) [15:56:28] error: synfig::save_canvas(): Unable to open file for write`

But I assure /home/alfonso/Documentos/goraexplorer/Introduction to GoraExplorer alpha/Animations/GoraExplorer web snapshot.png exists.

I don’t know where to start looking and how to fix it, but if someone gives me a tip, I could try to fix it (if it is just a change in the file XML 🙂 At this moment with a segmentation fault I can’t do much ☹

Thank you!  
[segmentationfaultcoredump.zip](https://forums.synfig.org/uploads/default/original/2X/0/06f484c45f1546da0657d41bb111b63e8320a7b2.zip) (691 KB)

---

<div class="post-metadata">

**Author:** ![BobSynfig](https://forums.synfig.org/user_avatar/forums.synfig.org/bobsynfig/32/175_2.png) [@BobSynfig](https://forums.synfig.org/u/BobSynfig)\
**Post date:** [March 6, 2018, 8:17am UTC](https://forums.synfig.org/t/segmentation-fault-core-dump/4387/2 "2018-03-06T08:17:25Z")

</div>

Hi and welcome here,

please check if you have sufficient rights on /tmp directory ([github.com/synfig/synfig/issues/435](https://github.com/synfig/synfig/issues/435))  
But maybe you will need to apply the required permissions described here: [thegeekdiary.com/unix-linux … rectories/](https://www.thegeekdiary.com/unix-linux-what-is-the-correct-permission-of-tmp-and-vartmp-directories/)

> [@](#):
>
> What are the correct permissions required for the /tmp and /var/tmp directories?
> 
> Answer  
> The /tmp and /var/tmp directories requires special permissions.  
> This directory has Sticky Bit permissions.  
> Many applications will show errors or fail if they are not able to write to /tmp with the appropriate permissions.
> 
> `# ls -ld /tmp
> drwxrwxrwt 21 root root 12288 Apr 28 16:18 /tmp`  
> The ‘t’ at the end symbolizes that the sticky bit is set.  
> A file created in the /tmp directory can only be removed by its owner, or the root user.
> 
> Setting up the permissions  
> Change the permissions on the directory by running either the following commands:
> 
> [code]# chmod 1777 /tmp  
> or
> 
> # chmod a+trwx /tmp[/code]

Or you can try to use current dev builds 😉

---

<div class="post-metadata">

**Author:** ![alfonso.nishikawa](https://forums.synfig.org/user_avatar/forums.synfig.org/alfonso.nishikawa/32/4141_2.png) [@alfonso.nishikawa](https://forums.synfig.org/u/alfonso.nishikawa)\
**Post date:** [March 6, 2018, 11:06am UTC](https://forums.synfig.org/t/segmentation-fault-core-dump/4387/3 "2018-03-06T11:06:05Z")

</div>

Hi @BobSynfig. Thanks for the support! I will try with 1.3.6 testing.

The directory /tmp/.mount\_GiIvLf is created when launching the app. The permissions should be find since I did not touch them, but I will take a look if it keeps happenning 🙂