closing the bug then, thanks.
** Changed in: f-spot (Ubuntu)
Status: Incomplete => Invalid
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs maili
For me itś not an issue anymore. Don know why but I can use F-spot
0.4.3.1 now without problems. Thanks for your attention.
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assign
Still an issue? May someone try the same with the intrepid version of
f-spot? thanks.
** Changed in: f-spot (Ubuntu)
Status: Confirmed => Incomplete
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desk
I'm not sure. It was broken for a month. I believe it was fixed, but I
had left by that time. It may well be broken again.
As I said, though, I can't test it.
Best of luck.
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a mem
I believe I am referring to the patched version of f-spot:
f-spot 0.4.3.1-0ubuntu1_amd64.deb vs f-spot_0.4.2-1ubuntu2_amd64.deb
As far as I can see there is no further version of f-spot in the
'proposed repository' to fix this issue. It seems to me that f-spot is
broken again with an error very s
Well, you have five duplicates and three people in this thread
confirming it. You also had a patch with two people claiming it fixed
the problem. I would venture to say that the original bug was confirmed
long ago and fixed.
I would't know, though, because Ubuntu shipped a default app which
didn't
f-spot 0.4.3.1-0ubuntu1 aborts on AMD64:
Posted initially in the wrong thread:
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/230306/comments/13
Anyone may confirm the bug?
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you ar
works for me ... thanks :)
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
May someone else try to test the f-spot package from the proposed
repository and see if it solve this issue? thanks.
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Hello,
the latest patch for f-spot from the "proposed" repository fixed my issue of
f-spot not starting with the sigsevs on AMD 64
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
** Changed in: f-spot (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
Status: New => Confirmed
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubun
Same here
** Attachment added: "output.txt"
http://launchpadlibrarian.net/14559054/output.txt
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
des
After additional investigation, the problem only occurs in conjunction
with some GConf settings, though I'm not sure which ones yet. Deleting
ALL GConf keys for F-Spot results in the program launching and
performing as expected, but a second attempt to launch the program
(after the keys have been r
F-spot crashed also on my Hardy heron 64 LTS (fresh install) AMD
Athlon(tm) 64 X2 Dual Core Processor 5000+
Stacktrace:
at FSpot.Global..cctor () <0x>
at FSpot.Global..cctor () <0xd>
at (wrapper runtime-invoke) FSpot.Defines.runtime_invoke_void
(object,intptr,intptr,intptr) <0
I did a reinstall from the latest packages (netinst) this morning, moved
the old f-spot dir out of the way, and tested again. Still have the same
error. No one else is getting this?
--
f-spot sigsevs on AMD64
https://bugs.launchpad.net/bugs/214410
You received this bug notification because you ar
Can anyone else reproduce this? I have a pretty stock install. Purging
all mono-related packages and reinstalling doesn't help. It's sad that
we're only a few days away from an LTS release and a show-stopper bug in
Hardy's default photo manager on 64 bit platforms.
After search like hell, I found
16 matches
Mail list logo
