@Hydrox24: your stacktrace and issue seems different, you should open a
new bug
Closing that bug since it was happening during the unstable cycle only
once and got no new comment or duplicate since
** Changed in: shotwell (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug
This bug affects me also, if I run shotwell normally from the terminal
then I simply get the segfault message, see attached for more details.
** Attachment added: shotwell.gdb
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/947561/+attachment/3175599/+files/shotwell.gdb
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shotwell (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947561
Title:
What happens if you run Shotwell again? Does the crash occur every time
you try to start it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947561
Title:
shotwell crashed with SIGSEGV in size()
To
Unfortunately, it doesn't. I understand this is probably one of those
bugs that might be impossible to reproduce and fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947561
Title:
shotwell
