After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 362282 - Crashes when specifying wrong account.
Crashes when specifying wrong account.
Status: RESOLVED INCOMPLETE
Product: f-spot
Classification: Other
Component: General
0.2.2
Other Linux
: High critical
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-15 03:44 UTC by Marcos Rodriguez
Modified: 2006-11-02 20:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marcos Rodriguez 2006-10-15 03:44:20 UTC 
I am running Gentoo Linux, F-Spot crashed when I specified my Picasaweb account wrongly by accident. It gave me an  "Access Denied" window and closed by itself.
But later I specified the account properly and it worked, but it shouldn't crash when wrong account is specified, it should just warn about it and continue.
Comment 1 André Klapper 2006-10-15 09:25:48 UTC 
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it.
Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Stephane Delcroix 2006-10-15 10:20:24 UTC 
Actually, just running F-Spot from an xterm is enough to have a trace. but we need this trace, since it shouldn't happens.
Comment 3 Marcos Rodriguez 2006-10-15 14:15:26 UTC 
(In reply to comment #2)
> Actually, just running F-Spot from an xterm is enough to have a trace. but we
> need this trace, since it shouldn't happens.
> 

Its odd...its not showing up again, I will keep testing around to find more bugs, I'll keep gnome-term opened.
Comment 4 Stephane Delcroix 2006-10-16 07:43:20 UTC 
the crash you reported shouldn't happens. Exceptions during auth phase are catched. I close this bug, reopen (or open another one) if you can make it crash again (but don't forget the trace...)
Comment 5 Stef Walter 2006-11-02 20:27:39 UTC 
*** Bug 369183 has been marked as a duplicate of this bug. ***