Re: Picasa Web album export
- From: Ralph Wabel <rwabel gmx net>
- To: Stephane Delcroix <stephane delcroix org>
- Cc: f-spot <f-spot-list gnome org>
- Subject: Re: Picasa Web album export
- Date: Fri, 22 Sep 2006 18:51:53 +0200
So I finally could fix my gnome desktop. Picasa web album works perfect
under gnome. Dunno know why it didn't under KDE.
thanks anyway for the help. I really LOVE that new feature. thanks to all.
Cheers
Ralph
Stephane Delcroix wrote:
> hi,
>
> event though I'm able to reproduce that issue, I don't know how you can
> start and make the keyring-daemon available for applications :(
>
> I read that the kde session manager is able to start the
> gnome-keyring-daemon, look that way on google...
>
> best regards,
>
> s
>
> On Wed, 2006-09-20 at 22:51 +0200, Ralph Wabel wrote:
>
>> hi stephane,
>>
>> thanks for helping me here out. Here is the full log. the baddevice
>> error message is probably because of my gnome desktop problems. get that
>> with some other apps too.
>>
>> rwabel ubuntu:~$ gnome-keyring-daemon
>> GNOME_KEYRING_SOCKET=/tmp/keyring-qPCulN/socket
>> GNOME_KEYRING_PID=6481
>> rwabel ubuntu:~$ f-spot
>> Starting new FSpot server
>> X Error: BadDevice, invalid or uninitialized input device 169
>> Major opcode: 147
>> Minor opcode: 3
>> Resource id: 0x0
>> Failed to open device
>> X Error: BadDevice, invalid or uninitialized input device 169
>> Major opcode: 147
>> Minor opcode: 3
>> Resource id: 0x0
>> Failed to open device
>> open uri = file:///media/hda1/Photos/stockholm/cimg0051.jpg
>> read = 39307
>> approximate quality = 93
>> Gnome.Keyring.KeyringException: The keyring daemon is not available
>> in <0x00193> Gnome.Keyring.Ring:SendRequest (System.IO.MemoryStream stream)
>> in <0x00096> Gnome.Keyring.Ring:Find (ItemType type,
>> System.Collections.Hashtable atts)
>> Gnome.Keyring.KeyringException: The keyring daemon is not available
>> in <0x00193> Gnome.Keyring.Ring:SendRequest (System.IO.MemoryStream stream)
>> in <0x0003d> Gnome.Keyring.Ring:GetDefaultKeyring ()
>> in <0x00022> FSpot.GoogleAccountManager:WriteAccounts ()
>> in <0x00014> FSpot.GoogleAccountManager:MarkChanged (Boolean write,
>> FSpot.GoogleAccount changed_account)
>> in <0x0000e> FSpot.GoogleAccountManager:MarkChanged ()
>> in <0x0025d> FSpot.GoogleAccountManager:ReadAccounts ()
>> in <0x0002e> FSpot.GoogleAccountManager:.ctor ()
>> in <0x0001f> FSpot.GoogleAccountManager:GetInstance ()
>> in <0x0014d> FSpot.GoogleExport:.ctor (IBrowsableCollection selection)
>> in <0x0003b> MainWindow:HandleExportToPicasa (System.Object sender,
>> System.EventArgs args)
>> in (wrapper delegate-invoke)
>> System.MulticastDelegate:invoke_void_object_EventArgs
>> (object,System.EventArgs)
>> in <0x00093> GLib.Signal:voidObjectCallback (IntPtr handle, IntPtr gch)
>> in (wrapper native-to-managed) GLib.Signal:voidObjectCallback
>> (intptr,intptr)
>> in <0x00000> <unknown method>
>> in (wrapper managed-to-native) Gtk.Application:gtk_main ()
>> in <0x00007> Gtk.Application:Run ()
>> in <0x00007> Gnome.Program:Run ()
>> in <0x0063f> FSpot.Driver:Main (System.String[] args)
>>
>> =================================================================
>> 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:
>>
>> in (wrapper managed-to-native) GLib.Signal:g_signal_get_invocation_hint
>> (intptr) <0x4>
>> in (wrapper managed-to-native) GLib.Signal:g_signal_get_invocation_hint
>> (intptr) <0xffffff74>
>> in GLib.Signal:get_Handler () <0x1c>
>> in GLib.Signal:voidObjectCallback (intptr,intptr) <0x60>
>> in (wrapper native-to-managed) GLib.Signal:voidObjectCallback
>> (intptr,intptr) <0x48dd32>
>> in (wrapper managed-to-native) Gtk.Object:gtk_object_destroy (intptr) <0x4>
>> in (wrapper managed-to-native) Gtk.Object:gtk_object_destroy (intptr)
>> <0xffffffe7>
>> in Gtk.Object:Destroy () <0x17>
>> in Gtk.Widget:Destroy () <0xa>
>> in FSpot.Driver:Main (string[]) <0x6a9>
>> in (wrapper runtime-invoke) System.Object:runtime_invoke_void_string[]
>> (object,intptr,intptr,intptr) <0xbebc3f>
>>
>> Native stacktrace:
>>
>> /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0xe3) [0xb7dd843f]
>> /usr/lib/libmono.so.0 [0xb7d9a03e]
>> [0xffffe440]
>> [0xb33b2c95]
>> [0xb33b2bdd]
>> [0xb3137851]
>> [0xb5ff6726]
>> /usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__VOID+0x43)
>> [0xb6484423]
>> /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x11e) [0xb647879f]
>> /usr/lib/libgobject-2.0.so.0 [0xb64877ec]
>> /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x6b0) [0xb6488b19]
>> /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x29) [0xb6488e89]
>> /usr/lib/libgtk-x11-2.0.so.0 [0xb6949512]
>> /usr/lib/libgtk-x11-2.0.so.0 [0xb6a14c5f]
>> /usr/lib/libgtk-x11-2.0.so.0 [0xb6a1bae2]
>> /usr/lib/libgobject-2.0.so.0(g_object_run_dispose+0x50) [0xb647b9f4]
>> /usr/lib/libgtk-x11-2.0.so.0(gtk_object_destroy+0x76) [0xb69494ce]
>> [0xb30d3f54]
>> [0xb30d3f10]
>> [0xb30d3ef3]
>> [0xb71ccaba]
>> [0xb71cb823]
>> /usr/lib/libmono.so.0 [0xb7db7438]
>> /usr/lib/libmono.so.0(mono_runtime_invoke+0x33) [0xb7e19eed]
>> /usr/lib/libmono.so.0(mono_runtime_exec_main+0x67) [0xb7e1ca88]
>> /usr/lib/libmono.so.0(mono_runtime_run_main+0x188) [0xb7e1fbf0]
>> /usr/lib/libmono.so.0(mono_jit_exec+0x90) [0xb7dc9b5e]
>> /usr/lib/libmono.so.0(mono_main+0x962) [0xb7dca54f]
>> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7b66ea2]
>> f-spot [0x8048459]
>> X Error: BadDevice, invalid or uninitialized input device 169
>> Major opcode: 147
>> Minor opcode: 3
>> Resource id: 0x0
>> Failed to open device
>> X Error: BadDevice, invalid or uninitialized input device 169
>> Major opcode: 147
>> Minor opcode: 3
>> Resource id: 0x0
>> Failed to open device
>> rwabel ubuntu:~$
>>
>>
>>
>> Stephane Delcroix wrote:
>>
>>> ...
>>>
>>> hi,
>>>
>>> can you please send a full log of your session, i.e. opening a terminal,
>>> starting the keyring-daemon, starting f-spot, crashing it exporting to
>>> picasa.
>>>
>>> the important part here is to start the keyring and f-spot from the same
>>> terminal !
>>>
>>> regards,
>>>
>>> s
>>>
>>> On Wed, 2006-09-20 at 22:12 +0200, Ralph Wabel wrote:
>>>
>>>
>>>> I'm using KDE, that might be the problem. Can't test under gnome yet
>>>> as it's broken. :-(
>>>> tried your hint
>>>>
>>>> rwabel 14787 0.0 0.0 2336 732 pts/1 S 21:58 0:00
>>>> gnome-keyring-daemon
>>>> rwabel 15219 25.0 5.1 138644 52904 ? Sl 22:09
>>>> 0:23 /usr/lib/firefox/firefox-bin -a firefox
>>>> rwabel 15242 0.0 0.0 2392 1016 pts/2 R+ 22:11 0:00 ps
>>>> -aux
>>>>
>>>> but still get the same error message.
>>>>
>>>>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]