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 303832 - F-Spot crashes
F-Spot crashes
Status: RESOLVED OBSOLETE
Product: f-spot
Classification: Other
Component: General
0.0.x
Other other
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
: 303616 303865 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-05-11 19:44 UTC by charles
Modified: 2009-07-27 13:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description charles 2005-05-11 19:44:50 UTC
Distribution: Debian 3.1
Package: f-spot
Severity: normal
Version: GNOME2.10.0 0.0.12
Gnome-Distributor: Ubuntu
Synopsis: F-Spot crashes
Bugzilla-Product: f-spot
Bugzilla-Component: General
Bugzilla-Version: 0.0.12
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. Start F-Stop
2. Import 198 photos into the program from the same directory.
3. Browse the imported photos.
4. a. Double-click on one of the photos and recieve a crash ("The
Application 'f-stop' has quit unexpectedly.").
4. b. Or select a picture and click "Full screen mode."
4. c. Or select a picture and select "Slideshow."

Expected Results:
What would normally be expected is that f-stop displays a larger version
of the image (4.a.), f-stop goes into fullscreen mode (4.b.), or that
f-stop begins a slide show (4.c.). 

What is occuring for me is that I recieve the same crash listed in 4.a.
for each of 4.a. 4.b. and 4.c..

How often does this happen?
This bug happens each time any of the actions listed in part 4 are
performed. Every time.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/f-spot'

Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 9449)]
[New Thread 32769 (LWP 9451)]
[New Thread 16386 (LWP 9452)]
[New Thread 32771 (LWP 9453)]
[New Thread 49156 (LWP 9456)]
[New Thread 65541 (LWP 9457)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x0f29f110 in waitpid () from /lib/libpthread.so.0
  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 waitpid
    from /lib/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-11 19:44 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was charles@chapsrelax.com.

Comment 1 Larry Ewing 2005-05-12 08:54:03 UTC
*** Bug 303668 has been marked as a duplicate of this bug. ***
Comment 2 Larry Ewing 2005-05-12 08:54:35 UTC
*** Bug 303865 has been marked as a duplicate of this bug. ***
Comment 3 Larry Ewing 2005-05-12 08:55:53 UTC
*** Bug 303616 has been marked as a duplicate of this bug. ***
Comment 4 Larry Ewing 2005-08-16 22:37:44 UTC
can anyone reproduce this in a recent version?  
Comment 5 Bengt Thuree 2006-02-17 07:37:15 UTC
Suggest we close this one since no-one have reported this problem for 6 months
Comment 6 Bengt Thuree 2006-05-17 04:27:09 UTC
I close this one, since no more information has been received.