FS#5322 - f-spot 0.1.11-2 hangs at launch

Attached to Project: Arch Linux
Opened by Benoit C (benoitc) - Thursday, 31 August 2006, 16:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When you lanch f-spot it hangs, maybe due to last release of mono. When you install last version it works (find attached the diff to the pkgbuild.

Here is the error log :
benoitc@marduk ~]$ f-spot
Starting new FSpot server
Glade.HandlerNotFoundException: The handler for the event ButtonPressEvent should take '(System.Object,Gtk.ButtonPressEventArgs)', but the signature of the provided handler ('HandleZoomOut') is '(System.Object,System.EventArgs)'

at SignalConnector.ConnectFunc (intptr,intptr,intptr,intptr,intptr,int,intptr) <0x0033f>
at (wrapper native-to-managed) SignalConnector.ConnectFunc (intptr,intptr,intptr,intptr,intptr,int,intptr) <0x00040>
in (unmanaged) 0xb61b296b
at (wrapper managed-to-native) SignalConnector.glade_xml_signal_autoconnect_full (intptr,Glade.XML/SignalConnector/RawXMLConnectFunc,intptr) <0x00004>
at SignalConnector.Autoconnect () <0x00059>
at Glade.XML.Autoconnect (object) <0x00042>
at MainWindow..ctor (Db) <0x0006c>
at FSpot.Core.get_MainWindow () <0x0002a>
at FSpot.Core.Organize () <0x0000f>
at FSpot.Driver.Main (string[]) <0x00547>




error in fspot dialog window:


An unhandled exception was thrown: The handler for the event ButtonPressEvent should take '(System.Object,Gtk.ButtonPressEventArgs)', but the signature of the provided handler ('HandleZoomOut') is '(System.Object,System.EventArgs)'


at SignalConnector.ConnectFunc (intptr,intptr,intptr,intptr,intptr,int,intptr) <0x0033f>
at (wrapper native-to-managed) SignalConnector.ConnectFunc (intptr,intptr,intptr,intptr,intptr,int,intptr) <0x00040>
in (unmanaged) 0xb61b296b
at (wrapper managed-to-native) SignalConnector.glade_xml_signal_autoconnect_full (intptr,Glade.XML/SignalConnector/RawXMLConnectFunc,intptr) <0x00004>
at SignalConnector.Autoconnect () <0x00059>
at Glade.XML.Autoconnect (object) <0x00042>
at MainWindow..ctor (Db) <0x0006c>
at FSpot.Core.get_MainWindow () <0x0002a>
at FSpot.Core.Organize () <0x0000f>
at FSpot.Driver.Main (string[]) <0x00547>

.NET Version: 1.1.4322.2032

Assembly Version Information:

gconf-sharp (2.8.0.0)
pango-sharp (2.8.0.0)
SemWeb (0.5.0.2)
glade-sharp (2.8.0.0)
gtkhtml-sharp (2.8.0.0)
System.Data (1.0.5000.0)
Mono.Data.SqliteClient (1.0.5000.0)
Mono.Posix (1.0.5000.0)
gdk-sharp (2.8.0.0)
gnome-vfs-sharp (2.8.0.0)
dbus-sharp (0.61.0.0)
System (1.0.5000.0)
atk-sharp (2.8.0.0)
gtk-sharp (2.8.0.0)
glib-sharp (2.8.0.0)
gnome-sharp (2.8.0.0)
f-spot (0.0.0.0)
mscorlib (1.0.5000.0)

Platform Information: Linux 2.6.17-ARCH i686 AuthenticAMD GNU/Linux

Disribution Information:

[/etc/arch-release]
Arch Linux 0.7.2 (Gimmick)

This task depends upon

Closed by  arjan timmerman (blaasvis)
Sunday, 03 December 2006, 09:34 GMT
Reason for closing:  Works for me
Additional comments about closing:  customer is a gone
Comment by Hussam Al-Tayeb (hussam) - Saturday, 02 September 2006, 19:04 GMT
I just built f-spot 0.2.0 against sqlite3 and this bug seems to have been resolved.
Can we please upgrade arch's f-spot package to 0.2.0 as an official fix?
Comment by 甘露(Lu Gan) (ganlu) - Sunday, 03 September 2006, 04:19 GMT
I got the error too, doesn't test if recompile against sqlite3 will solve it though.
Comment by Tobias Kieslich (tobias) - Monday, 18 September 2006, 06:49 GMT
did anybody encounter errors with the f-spot 0.2.0 release? or can we just close this one?
Comment by 甘露(Lu Gan) (ganlu) - Sunday, 24 September 2006, 07:28 GMT
With newest mono package, I got this error:
[ganlu@myhost ~]$ f-spot
Starting new FSpot server
XXXXX
Mono.Data.SqliteClient.SqliteSyntaxException: file is encrypted or is not a database
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.ExecuteNonQuery () [0x00000]
at MetaStore.CreateTable () [0x00000]
at MetaStore..ctor (Mono.Data.SqliteClient.SqliteConnection connection, Boolean is_new) [0x00000]
at Db.Init (System.String path, Boolean create_if_missing) [0x00000]
at FSpot.Core..ctor () [0x00000]
at FSpot.Driver.Main (System.String[] args) [0x00000]
XXXXX
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server
Starting new FSpot server

=================================================================
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.
=================================================================

Stacktrace:

at (wrapper managed-to-native) System.Threading.Monitor.Monitor_try_enter (object,int) <0x00004>
at (wrapper managed-to-native) System.Threading.Monitor.Monitor_try_enter (object,int) <0xffffffff>
at System.Threading.Monitor.Enter (object) <0x00013>
at (wrapper synchronized) DBus.Service.remove_SignalCalled (DBus.Service/SignalCalledHandler) <0xffffffff>
at FSpot.Core.Proxy.Finalize () <0x00015>
at (wrapper runtime-invoke) System.Object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

f-spot(mono_handle_native_sigsegv+0xe7) [0x8154b97]
f-spot [0x8121ae8]
[0xffffe440]
f-spot [0x80c3283]
[0xb72f4bf7]
[0xb72f4b84]
[0xb4f3cbec]
[0xb4f3cbbe]
[0xb4f3cb39]
f-spot [0x80ae6e1]
f-spot [0x81145ae]
f-spot [0x80ae81f]
f-spot [0x80c5c12]
f-spot [0x81087f7]
f-spot [0x811e803]
/lib/libpthread.so.0 [0xb7e91274]
/lib/libc.so.6(__clone+0x5e) [0xb7e0347e]
Aborted

[root@myhost ganlu]# pacman -Qi f-spot
Name : f-spot
Version : 0.2.0-1

[root@myhost ganlu]# pacman -Qi mono
Name : mono
Version : 1.1.17.1-1

Comment by Tobias Kieslich (tobias) - Sunday, 24 September 2006, 18:17 GMT
gan-lu it seems you it can't convert a SQLite2 database to SQLite3. Others reported that it was working for them. I think you have deletes the SQlite2 package from your system so it can't convert the old database. But I'm not sure
Comment by 甘露(Lu Gan) (ganlu) - Monday, 25 September 2006, 12:02 GMT
Well, yes, install sqlite2 can solve the problem, but it seems f-spot still need sqlite2 even it reports having successfully updated database, since it works only when I have sqlite2 installed. Once I remove sqlite2, it complains and refuse to start (with old .gnome2/f-spot/).
Comment by Tobias Kieslich (tobias) - Monday, 25 September 2006, 15:09 GMT
oha, good to know, I'll change the PKGBUILD accordingly. But to me it seems that f-spot infact is still using sqlite2 but links to sqlite3. WEIRD!
Comment by 甘露(Lu Gan) (ganlu) - Tuesday, 26 September 2006, 13:18 GMT
It seems a F-spot own bug though.
Comment by Benoit C (benoitc) - Sunday, 15 October 2006, 10:51 GMT
seems to work well here.
Comment by 甘露(Lu Gan) (ganlu) - Sunday, 15 October 2006, 13:46 GMT
Benoit C (benoitc) :
Do you mean you can run F-spot without sqlite2 AND with old configuration (tabs etc)? I can run F-spot with sqlite3 only under new profiles/configuration.
Comment by Benoit C (benoitc) - Sunday, 15 October 2006, 13:51 GMT
yes it works sqlite3 only. But that isn't a bug, just an enhancement.
Comment by arjan timmerman (blaasvis) - Saturday, 21 October 2006, 09:16 GMT
isn't this fixed ?

Loading...