osdir.com
mailing list archive

Subject: Re: Picasa Web album export - msg#00020

List: gnome.apps.f-spot

Date: Prev Next Index Thread: Prev Next Index
I read of an earlier issue with picasaweb and gnome-keyring-daemon and
I'm having the same issue, but I'm not running gnome. However I did
manually start gnome-keyring-daemon before starting f-spot, the output
is at the end of this email. Is there a way to disable gnome-keyring
support when compiling f-spot? I really don't need or want any of it's
features.

sysrq@acnt:~ $ gnome-keyring-daemon
GNOME_KEYRING_SOCKET=/tmp/keyring-2RIQoI/socket
GNOME_KEYRING_PID=16572
sysrq@acnt:~ $ f-spot
Starting new FSpot server
open uri = file:///home/sysrq/media/images/pictures/rock steady/Heavy Trigger
02-18-06 024.jpg
read = 15061
approximate quality = 90
open uri = file:///home/sysrq/media/images/pictures/rock steady/Heavy Trigger
02-18-06 024.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00012.jpg
read = 99797
approximate quality = 89
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00012.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00011.jpg
read = 89431
approximate quality = 89
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00011.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00010.jpg
read = 140497
approximate quality = 89
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00010.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00009.jpg
read = 119586
approximate quality = 89
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00009.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00008.jpg
read = 161300
approximate quality = 89
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00008.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00006.jpg
read = 85176
approximate quality = 89
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00006.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00005.jpg
read = 128362
approximate quality = 89
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00005.jpg
open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 --
2006-03-26)/00006.jpg
read = 85176
approximate quality = 89
Gnome.Keyring.KeyringException: The keyring daemon is not available
at Gnome.Keyring.Ring.SendRequest (System.IO.MemoryStream stream) [0x00000]
at Gnome.Keyring.Ring.Find (ItemType type, System.Collections.Hashtable atts)
[0x00000]
Gnome.Keyring.KeyringException: The keyring daemon is not available
at Gnome.Keyring.Ring.SendRequest (System.IO.MemoryStream stream) [0x00000]
at Gnome.Keyring.Ring.GetDefaultKeyring () [0x00000]
at FSpot.GoogleAccountManager.WriteAccounts () [0x00000]
at FSpot.GoogleAccountManager.MarkChanged (Boolean write, FSpot.GoogleAccount
changed_account) [0x00000]
at FSpot.GoogleAccountManager.MarkChanged () [0x00000]
at FSpot.GoogleAccountManager.ReadAccounts () [0x00000]
at FSpot.GoogleAccountManager..ctor () [0x00000]
at FSpot.GoogleAccountManager.GetInstance () [0x00000]
at FSpot.GoogleExport..ctor (IBrowsableCollection selection) [0x00000]
at MainWindow.HandleExportToPicasa (System.Object sender, System.EventArgs
args) [0x00000]
at (wrapper delegate-invoke)
System.MulticastDelegate:invoke_void_object_EventArgs (object,System.EventArgs)
at GLib.Signal.voidObjectCallback (IntPtr handle, IntPtr gch) [0x00000]
at (wrapper native-to-managed) GLib.Signal:voidObjectCallback (intptr,intptr)
at <0x00000> <unknown method>
at (wrapper managed-to-native) Gtk.Application:gtk_main ()
at Gtk.Application.Run () [0x00000]
at Gnome.Program.Run () [0x00000]
at FSpot.Driver.Main (System.String[] args) [0x00000]

=================================================================
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) GLib.Signal.g_signal_get_invocation_hint
(intptr) <0x00004>
at (wrapper managed-to-native) GLib.Signal.g_signal_get_invocation_hint
(intptr) <0xffffffff>
at GLib.Signal.get_Handler () <0x0001c>
at GLib.Signal.voidObjectCallback (intptr,intptr) <0x00060>
at (wrapper native-to-managed) GLib.Signal.voidObjectCallback (intptr,intptr)
<0xffffffff>
at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr)
<0x00004>
at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr)
<0xffffffff>
at Gtk.Object.Destroy () <0x0001a>
at Gtk.Widget.Destroy () <0x0000d>
at FSpot.Driver.Main (string[]) <0x008e2>
at (wrapper runtime-invoke) System.Object.runtime_invoke_void_string[]
(object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

f-spot(mono_handle_native_sigsegv+0xe7) [0x8154b97]
f-spot [0x8121ae8]
[0xb7ef1440]
[0xb4c68963]
[0xb4c688b5]
[0xb49d1131]
[0xb4db057b]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x4b)
[0xb659141b]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x13b) [0xb658407b]
/usr/lib/libgobject-2.0.so.0 [0xb65947b5]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x899) [0xb65959a9]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6595b59]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6941ecf]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6a39a63]
/usr/lib/libgtk-x11-2.0.so.0 [0xb6a45cf2]
/usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x51) [0xb6586721]
/usr/lib/libgtk-x11-2.0.so.0(gtk_object_destroy+0x7e) [0xb6941bde]
[0xb454f842]
[0xb454f7fb]
[0xb454f7d6]
[0xb77f2ffb]
[0xb77f1a73]
f-spot(mono_runtime_exec_main+0x60) [0x8099270]
f-spot(mono_runtime_run_main+0x1b3) [0x8099553]
f-spot(mono_main+0xe54) [0x805d424]
f-spot [0x805c0f2]
/lib/libc.so.6(__libc_start_main+0xd8) [0xb7ce2808]
f-spot [0x805c041]
Aborted


Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Re: 321770 - Filter on Last 20 Rolls

On Tue, 2006-10-03 at 14:51 +0200, Dotan Cohen wrote: > On 03/10/06, Alexandre Prokoudine <alexandre.prokoudine@xxxxxxxxx> wrote: > > > > I was rather referring to Preference dialog option vs. GConf key :) > > > > I don't see any reason that anything in GConf shouldn't be in > Preferences as well. Novice users know not to touch things in there > that they don't understand. That should read "Novice users SHOULD know not to touch things in there that they don't understand." But, the fact of the matter is, they don't, and for good reason - putting something in front of the user is the equivalent of saying "Play with Me". The beauty of GNOME is in it's simplicity - great strides have been taken to make GNOME more simple while retaining the power. Making a GConf key for this seems like the optimal solution - giving power while maintaining simplicity. For more information on this topic, you may want to check out Jeff Waugh's talk on freedom and design vs megapixel. He gave the talk as a keynote at FOSDEM and, more recently, at Ohio LinuxFest. You can find his FOSDEM talk at: http://free-electrons.com/pub/video/fosdem2006-jeff-waugh-keynote.ogg --Patrick

Next Message by Date: click to view message preview

Re: Picasa Web album export

Well I can fix the error by properly starting gnome-keyring-daemon but it would be nice if f-spot could fallback nicely if it can't find it or disable support for it alltogether at compile time. The fix way to properly start it is: sysrq@acnt:~ $ eval `gnome-keyring-daemon` sysrq@acnt:~ $ export GNOME_KEYRING_SOCKET sysrq@acnt:~ $ export GNOME_KEYRING_PID On Tue, Oct 03, 2006 at 10:55:19AM -0700, Eric Gillingham wrote: > I read of an earlier issue with picasaweb and gnome-keyring-daemon and > I'm having the same issue, but I'm not running gnome. However I did > manually start gnome-keyring-daemon before starting f-spot, the output > is at the end of this email. Is there a way to disable gnome-keyring > support when compiling f-spot? I really don't need or want any of it's > features. > > sysrq@acnt:~ $ gnome-keyring-daemon > GNOME_KEYRING_SOCKET=/tmp/keyring-2RIQoI/socket > GNOME_KEYRING_PID=16572 > sysrq@acnt:~ $ f-spot > Starting new FSpot server > open uri = file:///home/sysrq/media/images/pictures/rock steady/Heavy Trigger > 02-18-06 024.jpg > read = 15061 > approximate quality = 90 > open uri = file:///home/sysrq/media/images/pictures/rock steady/Heavy Trigger > 02-18-06 024.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00012.jpg > read = 99797 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00012.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00011.jpg > read = 89431 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00011.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00010.jpg > read = 140497 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00010.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00009.jpg > read = 119586 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00009.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00008.jpg > read = 161300 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00008.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00006.jpg > read = 85176 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00006.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00005.jpg > read = 128362 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00005.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00006.jpg > read = 85176 > approximate quality = 89 > Gnome.Keyring.KeyringException: The keyring daemon is not available > at Gnome.Keyring.Ring.SendRequest (System.IO.MemoryStream stream) [0x00000] > at Gnome.Keyring.Ring.Find (ItemType type, System.Collections.Hashtable > atts) [0x00000] > Gnome.Keyring.KeyringException: The keyring daemon is not available > at Gnome.Keyring.Ring.SendRequest (System.IO.MemoryStream stream) [0x00000] > at Gnome.Keyring.Ring.GetDefaultKeyring () [0x00000] > at FSpot.GoogleAccountManager.WriteAccounts () [0x00000] > at FSpot.GoogleAccountManager.MarkChanged (Boolean write, > FSpot.GoogleAccount changed_account) [0x00000] > at FSpot.GoogleAccountManager.MarkChanged () [0x00000] > at FSpot.GoogleAccountManager.ReadAccounts () [0x00000] > at FSpot.GoogleAccountManager..ctor () [0x00000] > at FSpot.GoogleAccountManager.GetInstance () [0x00000] > at FSpot.GoogleExport..ctor (IBrowsableCollection selection) [0x00000] > at MainWindow.HandleExportToPicasa (System.Object sender, System.EventArgs > args) [0x00000] > at (wrapper delegate-invoke) > System.MulticastDelegate:invoke_void_object_EventArgs > (object,System.EventArgs) > at GLib.Signal.voidObjectCallback (IntPtr handle, IntPtr gch) [0x00000] > at (wrapper native-to-managed) GLib.Signal:voidObjectCallback > (intptr,intptr) > at <0x00000> <unknown method> > at (wrapper managed-to-native) Gtk.Application:gtk_main () > at Gtk.Application.Run () [0x00000] > at Gnome.Program.Run () [0x00000] > at FSpot.Driver.Main (System.String[] args) [0x00000] > > ================================================================= > 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) GLib.Signal.g_signal_get_invocation_hint > (intptr) <0x00004> > at (wrapper managed-to-native) GLib.Signal.g_signal_get_invocation_hint > (intptr) <0xffffffff> > at GLib.Signal.get_Handler () <0x0001c> > at GLib.Signal.voidObjectCallback (intptr,intptr) <0x00060> > at (wrapper native-to-managed) GLib.Signal.voidObjectCallback > (intptr,intptr) <0xffffffff> > at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr) > <0x00004> > at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr) > <0xffffffff> > at Gtk.Object.Destroy () <0x0001a> > at Gtk.Widget.Destroy () <0x0000d> > at FSpot.Driver.Main (string[]) <0x008e2> > at (wrapper runtime-invoke) System.Object.runtime_invoke_void_string[] > (object,intptr,intptr,intptr) <0xffffffff> > > Native stacktrace: > > f-spot(mono_handle_native_sigsegv+0xe7) [0x8154b97] > f-spot [0x8121ae8] > [0xb7ef1440] > [0xb4c68963] > [0xb4c688b5] > [0xb49d1131] > [0xb4db057b] > /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x4b) > [0xb659141b] > /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x13b) [0xb658407b] > /usr/lib/libgobject-2.0.so.0 [0xb65947b5] > /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x899) [0xb65959a9] > /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6595b59] > /usr/lib/libgtk-x11-2.0.so.0 [0xb6941ecf] > /usr/lib/libgtk-x11-2.0.so.0 [0xb6a39a63] > /usr/lib/libgtk-x11-2.0.so.0 [0xb6a45cf2] > /usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x51) [0xb6586721] > /usr/lib/libgtk-x11-2.0.so.0(gtk_object_destroy+0x7e) [0xb6941bde] > [0xb454f842] > [0xb454f7fb] > [0xb454f7d6] > [0xb77f2ffb] > [0xb77f1a73] > f-spot(mono_runtime_exec_main+0x60) [0x8099270] > f-spot(mono_runtime_run_main+0x1b3) [0x8099553] > f-spot(mono_main+0xe54) [0x805d424] > f-spot [0x805c0f2] > /lib/libc.so.6(__libc_start_main+0xd8) [0xb7ce2808] > f-spot [0x805c041] > Aborted > _______________________________________________ > F-spot-list mailing list > F-spot-list@xxxxxxxxx > http://mail.gnome.org/mailman/listinfo/f-spot-list >

Previous Message by Thread: click to view message preview

321770 - Filter on Last 20 Rolls

Hi Guys I uploaded a new version of my patch[1] for the Last Import Rolls[2] bug. This one keeps the roll id's permanently stored in the Photos database. The filter still works on the last 20 (configurable in gconf) import rolls. Import roll is not quite the same as in the old negative world. I just imported 300 photos from my camera, and that is one roll. Differences from previous patch, is that I renamed the imports table to rolls (did not rename the ImportStore.cs file nor its class though). I renamed the import_id to roll_id in photos. I have tested upgrade from cvs database, as well as from a non existing database. To test this one, I would recommend testing on a test user account, or at least use the --basedir option. This patch DO modify the sqlite database... Please test and comment... /Bengt [1] : http://bugzilla.gnome.org/attachment.cgi?id=73748&action=edit [2] : http://bugzilla.gnome.org/show_bug.cgi?id=321770 signature.asc Description: This is a digitally signed message part _______________________________________________ F-spot-list mailing list F-spot-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/f-spot-list

Next Message by Thread: click to view message preview

Re: Picasa Web album export

Well I can fix the error by properly starting gnome-keyring-daemon but it would be nice if f-spot could fallback nicely if it can't find it or disable support for it alltogether at compile time. The fix way to properly start it is: sysrq@acnt:~ $ eval `gnome-keyring-daemon` sysrq@acnt:~ $ export GNOME_KEYRING_SOCKET sysrq@acnt:~ $ export GNOME_KEYRING_PID On Tue, Oct 03, 2006 at 10:55:19AM -0700, Eric Gillingham wrote: > I read of an earlier issue with picasaweb and gnome-keyring-daemon and > I'm having the same issue, but I'm not running gnome. However I did > manually start gnome-keyring-daemon before starting f-spot, the output > is at the end of this email. Is there a way to disable gnome-keyring > support when compiling f-spot? I really don't need or want any of it's > features. > > sysrq@acnt:~ $ gnome-keyring-daemon > GNOME_KEYRING_SOCKET=/tmp/keyring-2RIQoI/socket > GNOME_KEYRING_PID=16572 > sysrq@acnt:~ $ f-spot > Starting new FSpot server > open uri = file:///home/sysrq/media/images/pictures/rock steady/Heavy Trigger > 02-18-06 024.jpg > read = 15061 > approximate quality = 90 > open uri = file:///home/sysrq/media/images/pictures/rock steady/Heavy Trigger > 02-18-06 024.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00012.jpg > read = 99797 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00012.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00011.jpg > read = 89431 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00011.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00010.jpg > read = 140497 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00010.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00009.jpg > read = 119586 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00009.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00008.jpg > read = 161300 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00008.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00006.jpg > read = 85176 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00006.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00005.jpg > read = 128362 > approximate quality = 89 > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00005.jpg > open uri = file:///home/sysrq/media/images/pictures/June Mtn. (2006-03-22 -- > 2006-03-26)/00006.jpg > read = 85176 > approximate quality = 89 > Gnome.Keyring.KeyringException: The keyring daemon is not available > at Gnome.Keyring.Ring.SendRequest (System.IO.MemoryStream stream) [0x00000] > at Gnome.Keyring.Ring.Find (ItemType type, System.Collections.Hashtable > atts) [0x00000] > Gnome.Keyring.KeyringException: The keyring daemon is not available > at Gnome.Keyring.Ring.SendRequest (System.IO.MemoryStream stream) [0x00000] > at Gnome.Keyring.Ring.GetDefaultKeyring () [0x00000] > at FSpot.GoogleAccountManager.WriteAccounts () [0x00000] > at FSpot.GoogleAccountManager.MarkChanged (Boolean write, > FSpot.GoogleAccount changed_account) [0x00000] > at FSpot.GoogleAccountManager.MarkChanged () [0x00000] > at FSpot.GoogleAccountManager.ReadAccounts () [0x00000] > at FSpot.GoogleAccountManager..ctor () [0x00000] > at FSpot.GoogleAccountManager.GetInstance () [0x00000] > at FSpot.GoogleExport..ctor (IBrowsableCollection selection) [0x00000] > at MainWindow.HandleExportToPicasa (System.Object sender, System.EventArgs > args) [0x00000] > at (wrapper delegate-invoke) > System.MulticastDelegate:invoke_void_object_EventArgs > (object,System.EventArgs) > at GLib.Signal.voidObjectCallback (IntPtr handle, IntPtr gch) [0x00000] > at (wrapper native-to-managed) GLib.Signal:voidObjectCallback > (intptr,intptr) > at <0x00000> <unknown method> > at (wrapper managed-to-native) Gtk.Application:gtk_main () > at Gtk.Application.Run () [0x00000] > at Gnome.Program.Run () [0x00000] > at FSpot.Driver.Main (System.String[] args) [0x00000] > > ================================================================= > 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) GLib.Signal.g_signal_get_invocation_hint > (intptr) <0x00004> > at (wrapper managed-to-native) GLib.Signal.g_signal_get_invocation_hint > (intptr) <0xffffffff> > at GLib.Signal.get_Handler () <0x0001c> > at GLib.Signal.voidObjectCallback (intptr,intptr) <0x00060> > at (wrapper native-to-managed) GLib.Signal.voidObjectCallback > (intptr,intptr) <0xffffffff> > at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr) > <0x00004> > at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr) > <0xffffffff> > at Gtk.Object.Destroy () <0x0001a> > at Gtk.Widget.Destroy () <0x0000d> > at FSpot.Driver.Main (string[]) <0x008e2> > at (wrapper runtime-invoke) System.Object.runtime_invoke_void_string[] > (object,intptr,intptr,intptr) <0xffffffff> > > Native stacktrace: > > f-spot(mono_handle_native_sigsegv+0xe7) [0x8154b97] > f-spot [0x8121ae8] > [0xb7ef1440] > [0xb4c68963] > [0xb4c688b5] > [0xb49d1131] > [0xb4db057b] > /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x4b) > [0xb659141b] > /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x13b) [0xb658407b] > /usr/lib/libgobject-2.0.so.0 [0xb65947b5] > /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x899) [0xb65959a9] > /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6595b59] > /usr/lib/libgtk-x11-2.0.so.0 [0xb6941ecf] > /usr/lib/libgtk-x11-2.0.so.0 [0xb6a39a63] > /usr/lib/libgtk-x11-2.0.so.0 [0xb6a45cf2] > /usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x51) [0xb6586721] > /usr/lib/libgtk-x11-2.0.so.0(gtk_object_destroy+0x7e) [0xb6941bde] > [0xb454f842] > [0xb454f7fb] > [0xb454f7d6] > [0xb77f2ffb] > [0xb77f1a73] > f-spot(mono_runtime_exec_main+0x60) [0x8099270] > f-spot(mono_runtime_run_main+0x1b3) [0x8099553] > f-spot(mono_main+0xe54) [0x805d424] > f-spot [0x805c0f2] > /lib/libc.so.6(__libc_start_main+0xd8) [0xb7ce2808] > f-spot [0x805c041] > Aborted > _______________________________________________ > F-spot-list mailing list > F-spot-list@xxxxxxxxx > http://mail.gnome.org/mailman/listinfo/f-spot-list >
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by