F-Spot crashes with SIGSEGV on open

Bug #194864 reported by Wilbur Harvey
16
Affects Status Importance Assigned to Milestone
f-spot (Ubuntu)
Invalid
Medium
Maia Everett

Bug Description

Binary package hint: f-spot

I cannot open F-Spot.
My system is Ubuntu Hardy-64, all updates as of 2008-Feb-23AM

If I right click on a picture, the wheel spins for a while and then nothing happens.

If I try to start it from the command line I get this.

Stacktrace:

  at FSpot.Global..cctor () <0xffffffff>
  at FSpot.Global..cctor () <0x0000d>
  at (wrapper runtime-invoke) FSpot.Defines.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0x00144>
  at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot [0x58df3e]
 f-spot [0x46a070]
 f-spot [0x56eb60]
 /lib/libpthread.so.0 [0x7f76ee5337d0]
 /lib/libc.so.6(memcpy+0x60) [0x7f76edfbece0]
 f-spot(mono_breakpoint_clean_code+0x2d) [0x46575c]
 f-spot [0x46a534]
 f-spot [0x46e040]
 [0x4037615b]

Debug info from gdb:

(no debugging symbols found)
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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f76ef20a7a0 (LWP 7370)]
[New Thread 0x4031d950 (LWP 7372)]
[New Thread 0x40e16950 (LWP 7371)]
(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)
0x00007f76ee5325cb in read () from /lib/libpthread.so.0
  3 Thread 0x40e16950 (LWP 7371) 0x00007f76ee532e81 in nanosleep ()
   from /lib/libpthread.so.0
  2 Thread 0x4031d950 (LWP 7372) 0x00007f76ee52fb99 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
  1 Thread 0x7f76ef20a7a0 (LWP 7370) 0x00007f76ee5325cb in read ()
   from /lib/libpthread.so.0

Thread 3 (Thread 0x40e16950 (LWP 7371)):
#0 0x00007f76ee532e81 in nanosleep () from /lib/libpthread.so.0
#1 0x000000000050d3b4 in ?? ()
#2 0x00007f76ee52b3f7 in start_thread () from /lib/libpthread.so.0
#3 0x00007f76ee01995d in clone () from /lib/libc.so.6
#4 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x4031d950 (LWP 7372)):
#0 0x00007f76ee52fb99 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#1 0x0000000000512582 in ?? ()
#2 0x00000000005128b0 in ?? ()
#3 0x0000000000512676 in ?? ()
#4 0x0000000000523dfc in ?? ()
#5 0x00000000004a91c0 in ?? ()
#6 0x00000000004c46da in ?? ()
#7 0x000000000052220c in ?? ()
#8 0x000000000053fc57 in ?? ()
#9 0x00007f76ee52b3f7 in start_thread () from /lib/libpthread.so.0
#10 0x00007f76ee01995d in clone () from /lib/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f76ef20a7a0 (LWP 7370)):
#0 0x00007f76ee5325cb in read () from /lib/libpthread.so.0
#1 0x00007f76ee9aef80 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x00007f76ee9af46e in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x00007f76ee9afdcf in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#4 0x00007f76ee9b0288 in g_spawn_command_line_sync ()
   from /usr/lib/libglib-2.0.so.0
#5 0x000000000058e007 in ?? ()
#6 0x000000000046a070 in ?? ()
#7 0x000000000056eb60 in ?? ()
#8 <signal handler called>
#9 0x00007f76edfbece0 in memcpy () from /lib/libc.so.6
#10 0x000000000046575c in mono_breakpoint_clean_code ()
#11 0x000000000046a534 in ?? ()
#12 0x000000000046e040 in ?? ()
#13 0x000000004037615b in ?? ()
#14 0x000000010096dcd0 in ?? ()
#15 0x000000000095da58 in ?? ()
#16 0x00007ffff722cc90 in ?? ()
#17 0x000000000050a6a7 in mono_class_get_method_from_name_flags ()
#18 0x000000004182600d in ?? ()
#19 0x0000000000000000 in ?? ()
#0 0x00007f76ee5325cb in read () from /lib/libpthread.so.0

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted (core dumped)

Revision history for this message
Maia Everett (linneris) wrote :

Can you please attach a crash dump file?

Changed in f-spot:
assignee: nobody → sikon
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Wilbur Harvey (wilbur-harvey-spirentcom) wrote :

It crashes immediately on startup.
I have all the latest updates as of 2008-Mar-02 PM

How do I create/find the crash dump file?

Revision history for this message
Wilbur Harvey (wilbur-harvey-spirentcom) wrote :
Download full text (3.7 KiB)

This is what I got from valgrind.

==31467== Memcheck, a memory error detector.
==31467== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==31467== Using LibVEX rev 1804, a library for dynamic binary translation.
==31467== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==31467== Using valgrind-3.3.0-Debian, a dynamic binary instrumentation framewor
k.
==31467== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==31467==
==31467== My PID = 31467, parent PID = 29327. Prog and args are:
==31467== f-spot
==31467==
--31467--
--31467-- Command line
--31467-- f-spot
--31467-- Startup, with flags:
--31467-- --suppressions=/usr/lib/valgrind/debian-libc6-dbg.supp
--31467-- -v
--31467-- --tool=memcheck
--31467-- --leak-check=full
--31467-- --num-callers=40
--31467-- --log-file=valgrind.log
--31467-- Contents of /proc/version:
--31467-- Linux version 2.6.24-12-generic (buildd@yellow) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu4)) #1 SMP Wed Mar 12 22:31:43 UTC 2008
--31467-- Arch and hwcaps: AMD64, amd64-sse2
--31467-- Page sizes: currently 4096, max supported 4096
--31467-- Valgrind library directory: /usr/lib/valgrind
--31467-- Reading syms from /bin/bash (0x400000)
--31467-- Reading debug info from /bin/bash...
--31467-- ... CRC mismatch (computed b0887cbf wanted 91d1b125)
--31467-- object doesn't have a symbol table
--31467-- Reading syms from /lib/ld-2.7.so (0x4000000)
--31467-- Reading debug info from /lib/ld-2.7.so...
--31467-- ... CRC mismatch (computed c9862f74 wanted 7aafc83d)
--31467-- Reading debug info from /usr/lib/debug/lib/ld-2.7.so...
--31467-- Reading syms from /usr/lib/valgrind/amd64-linux/memcheck (0x38000000)
--31467-- object doesn't have a dynamic symbol table
--31467-- Reading suppressions file: /usr/lib/valgrind/debian-libc6-dbg.supp
--31467-- Reading suppressions file: /usr/lib/valgrind/default.supp
--31467-- Reading syms from /usr/lib/valgrind/amd64-linux/vgpreload_core.so (0x4A1F000)
--31467-- Reading syms from /usr/lib/valgrind/amd64-linux/vgpreload_memcheck.so (0x4C20000)
--31467-- REDIR: 0x4015ca0 (index) redirected to 0x4c23e00 (index)
--31467-- REDIR: 0x4015e50 (strcmp) redirected to 0x4c24060 (strcmp)
--31467-- REDIR: 0x4015e80 (strlen) redirected to 0x4c23f90 (strlen)
--31467-- Reading syms from /lib/libncurses.so.5.6 (0x4E27000)
--31467-- Reading debug info from /lib/libncurses.so.5.6...
--31467-- ... CRC mismatch (computed 153c050c wanted 98bdd664)
--31467-- object doesn't have a symbol table
--31467-- Reading syms from /usr/lib/debug/libdl-2.7.so (0x5062000)
--31467-- Reading syms from /usr/lib/debug/libc-2.7.so (0x5266000)
--31467-- REDIR: 0x52e14b0 (rindex) redirected to 0x4c23cb0 (rindex)
--31467-- REDIR: 0x52e0b30 (strcmp) redirected to 0x4c24020 (strcmp)
--31467-- REDIR: 0x52e10a0 (strlen) redirected to 0x4c23f50 (strlen)
--31467-- REDIR: 0x52e1320 (strncmp) redirected to 0x4c23fb0 (strncmp)
--31467-- REDIR: 0x52e0980 (index) redirected to 0x4c23da0 (index)
--31467-- REDIR: 0x52e3ab0 (strchrnul) redirected to 0x4c242b0 (strchrnul)
--31467-- REDIR: 0x52e2430 (mempcpy) redirected to 0x4c24a20 (mempcpy)
--31467-- REDIR: 0x52e2d40 (memcpy) r...

Read more...

Revision history for this message
Wilbur Harvey (wilbur-harvey-spirentcom) wrote :
Download full text (4.1 KiB)

There was a new version of F-Spot this morning, but it still crashes.
There is no file in /var/crash generated.
This is an amd64 installation with all the updates as of an hour ago.
Here is the console output.

 f-spot
Stacktrace:

  at FSpot.Global..cctor () <0xffffffff>
  at FSpot.Global..cctor () <0x0000d>
  at (wrapper runtime-invoke) FSpot.Defines.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0xffffffff>
  at FSpot.Driver.Main (string[]) <0x00144>
  at (wrapper runtime-invoke) FSpot.Driver.runtime_invoke_int_string[] (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

 f-spot [0x51bb67]
 f-spot [0x43dacd]
 /lib/libpthread.so.0 [0x7f7ecfcbd7d0]
 /lib/libc.so.6(memcpy+0x60) [0x7f7ecf748da0]
 f-spot(mono_breakpoint_clean_code+0x1b) [0x42725b]
 f-spot [0x43f78d]
 f-spot [0x44005e]
 [0x41cae15b]

Debug info from gdb:

(no debugging symbols found)
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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f7ed098f7a0 (LWP 18421)]
[New Thread 0x407e3950 (LWP 18423)]
[New Thread 0x40f66950 (LWP 18422)]
(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)
0x00007f7ecf79cdf2 in select () from /lib/libc.so.6
  3 Thread 0x40f66950 (LWP 18422) 0x00007f7ecfcbce81 in nanosleep ()
   from /lib/libpthread.so.0
  2 Thread 0x407e3950 (LWP 18423) 0x00007f7ecfcb9b99 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
  1 Thread 0x7f7ed098f7a0 (LWP 18421) 0x00007f7ecf79cdf2 in select ()
   from /lib/libc.so.6

Thread 3 (Thread 0x40f66950 (LWP 18422)):
#0 0x00007f7ecfcbce81 in nanosleep () from /lib/libpthread.so.0
#1 0x00000000004b8f4f in ?? ()
#2 0x00007f7ecfcb53f7 in start_thread () from /lib/libpthread.so.0
#3 0x00007f7ecf7a3b7d in clone () from /lib/libc.so.6
#4 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x407e3950 (LWP 18423)):
#0 0x00007f7ecfcb9b99 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0
#1 0x00000000004bb585 in ?? ()
#2 0x00000000004bdb37 in ?? ()
#3 0x00000000004cbc03 in ?? ()
#4 0x000000000046b3c1 in ?? ()
#5 0x00000000004855c3 in ?? ()
#6 0x00000000004cb287 in ?? ()
#7 0x00000000004e07d2 in ?? ()
#8 0x00007f7ecfcb53f7 in start_thread () from /lib/libpthread.so.0
#9 0x00007f7ecf7a3b7d in clone () from /lib/libc.so.6
#10 0x0000000000000000 in ...

Read more...

Revision history for this message
hardcorelinux (hardcorelinux) wrote :

Matvey,
   I'm facing the same problem as Wilbur. Attaching a core dump.

Revision history for this message
Jeff Cai (jeffcaiz) wrote :

Yep. I've upgrade to Hardy 64bit today. Encounter the same problem.
F-Spot works fine before upgrade.

Mono's problem?

Revision history for this message
Mark Duncan (eattheapple) wrote :

Up to date Hardy and F-spot still doesn't work properly on AMD64. If I go to a terminal and keep trying to run "f-spot" over and over again, it will work about 1 in 20 times (the other 19 times, I get the same error as the submitter). This is kind of embarrassing that a program that ships as part of the default install doesn't even run. It makes Ubuntu look like it was just kind of thrown together and not tested at all (I'm not saying that's the case, but someone new to Ubuntu might think that). Hopefully it gets fixed soon.

Revision history for this message
spitenmalice (atbakken) wrote :

I can confirm I have the very same problem with:

$lsb_release -rd
Description: Ubuntu 8.04
Release: 8.04

$apt-cache policy f-spot
f-spot:
  Installed: 0.4.2-1ubuntu3
  Candidate: 0.4.2-1ubuntu3
  Version table:
 *** 0.4.2-1ubuntu3 0

Seems that it will work intermittently but for the most part I get the same debug info from gdb resulting in:

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Revision history for this message
llevering (l-levering) wrote :

I have this same problem. I see that the bugreport is still on incomplete, is there any data I can provide to get the bugreport complete and confirmed?

Revision history for this message
Rajeev Nair (rajeev) wrote :

look at my terminal output

rajeev@rajeev-desktop:~$ f-spot
Stacktrace:

Segmentation fault
rajeev@rajeev-desktop:~$

thats all it says.

but i have filed another bug report when hardy was in testing caught by apport bug no 202771.

Revision history for this message
hardcorelinux (hardcorelinux) wrote :

Folks,
 I got a latest patch/update which seems to have solved this:
Package: f-spot
Versions:
0.4.3.1-0ubuntu1 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_hardy-proposed_main_binary-amd64_Packages) (/var/lib/dpkg/status)
 Description Language:
                 File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_hardy-proposed_main_binary-amd64_Packages
                  MD5: da892ff83cc63d9e6a405171ea181c44

0.4.2-1ubuntu3 (/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_hardy_main_binary-amd64_Packages)
 Description Language:
                 File: /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_hardy_main_binary-amd64_Packages
                  MD5: da892ff83cc63d9e6a405171ea181c44

Revision history for this message
Maia Everett (linneris) wrote :

Wilbur, can you confirm whether it fixes the bug for you?

Revision history for this message
Robert McKee (bertmanphx) wrote :

Matvey,
This patch fixed the mono related crash I was having.

bertman

Revision history for this message
phill.wall@gmail.com (phill-wall) wrote :

64 bit hardy
up to date as of 29th May 2008

I get the following when run in terminal

phillw@QUAD1:~$ f-spot
Starting new FSpot server
XXXXX
Mono.Data.SqliteClient.SqliteSyntaxException: no such table: tags
  at Mono.Data.SqliteClient.SqliteCommand.GetNextStatement (IntPtr pzStart, System.IntPtr& pzTail, System.IntPtr& pStmt) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32& rows_affected) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader (CommandBehavior behavior) [0x00000]
  at Mono.Data.SqliteClient.SqliteCommand.ExecuteReader () [0x00000]
  at (wrapper remoting-invoke-with-check) Mono.Data.SqliteClient.SqliteCommand:ExecuteReader ()
  at Banshee.Database.QueuedSqliteCommand.Execute () [0x00000]
XXXXX
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Starting new FSpot server
Can't get a connection to the dbus. Trying again...
Sorry, couldn't start F-Spot
phillw@QUAD1:~$

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Intrepid Ibex. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in f-spot:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.