ubuntustudio-bugs team mailing list archive
-
ubuntustudio-bugs team
-
Mailing list archive
-
Message #00773
[Bug 967416] Re: inkscape crashed with SIGSEGV in file_save()
Do we have a plan for fixing this? Threading bugs can be so tricky...
Would it make sense to have the save routine set a lock when it starts,
and then have the exit thread check for existing locks and refuse or
delay exiting until they've cleared? Perhaps the lock could be
timestamped so that the lock is only honored for, say, 10 seconds (the
save routine could re-issue the lock if it expects the save operation to
take more time than that.
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to inkscape in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/967416
Title:
inkscape crashed with SIGSEGV in file_save()
Status in Inkscape: A Vector Drawing Tool:
Triaged
Status in “inkscape” package in Ubuntu:
Triaged
Bug description:
Occurred when I closed Inkscape.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: inkscape 0.48.3.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 28 15:01:15 2012
ExecutablePath: /usr/bin/inkscape
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: inkscape /home/username/MyKaryotes/graphics/cell.svg
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: inkscape
Title: inkscape crashed with SIGSEGV in sp_file_save_dialog()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/967416/+subscriptions