closing as no further information was provided
** Changed in: shotwell (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741465
Title:
shotwell crashed
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I cannot provide that information, because I am running xubuntu now and
the error does not occur there.
On Sat, 2011-06-04 at 11:15 +, Omer Akram wrote:
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: shotwell
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741465
Title:
shotwell crashed with SIGABRT in __kernel_vsyscall()
--
ubuntu-bugs mailing list
Can you reproduce this crash? Does it occur every time you start
Shotwell, or did it only happen once?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741465
Title:
shotwell crashed with SIGABRT in
