abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: shotwell component: shotwell crash_function: FixedVMPoolAllocator executable: /usr/bin/shotwell kernel: 2.6.35.6-48.fc14.x86_64 package: shotwell-0.7.2-2.fc14 rating: 4 reason: Process /usr/bin/shotwell was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1289377686 uid: 500 How to reproduce ----- 1. Try to upload something to facebook 2. It will crash!
Created attachment 459365 [details] File: backtrace
I've just tried uploading 24 photos and it went without a hitch. Question: - how many photos were you uploading - what are their sizes - where during the uploading process does Shotwell crash? (I'm trying to estimate how many megabytes were transferred, and if the crash is when processing a particularly large picture) Thanks :)
To be sure I tried it once more! It does not even make it to uploading, I was trying to upload only one photo. It crashes while loading facebook login page. It is wired it may be a liboauth bug, I have a similar problem with gwibber, the only thing working with it is bti (the command line for twitter). Maybe you had your account setup before fc14? (For some other problems I have to clean all of config folders in my home directory)
No, shotwell does not link against oauth. Facebook uses a different scheme, AFAIK, though it does look like oAuth. (and I maintain bti, so thanks for the thumbs up :) ) I do indeed move my Shotwell settings from my previous F-13 install. On the other hand, I just checked ~/.shotwell and gconf-editor's /apps/shotwell/sharing/facebook and everything seems to be in order. Let me try it on another computer -- I don't want to risk messing up my photo library on this one, but I do have some photos I've not uploaded yet that I can use to set up a second Shotwell account. Since the problem appears to be JavaScript related, could you check which version of webkitgtk you have installed? I have 1.3.5, which was a test update that never got released : https://admin.fedoraproject.org/updates/webkitgtk-1.3.5-1.fc14 because it was superseded by 1.3.6 : https://admin.fedoraproject.org/updates/webkitgtk-1.3.6-1.fc14 Could you try either and see if they fix the problem?
oh, and please vote on the update if it indeed fixes the problem.
It is older than your webkitgtk-1.3.4-3.fc14.1.x86_64. I updated that from updates-testing it did not change much (maybe took 1 seconds later to crash)
Can you confirm which version you tried -- did you try 1.3.6 already? The webkitgtk maintainers are now Cc:ed on this bug report, so hopefully they can shed some light on this.
As you suggested I switched to webkitgtk-1.3.6-1.fc14.x86_64 And the problem is not solved with the update
This does look like a webkitgtk bug in the JIT compiler. ;( What was the last version that worked correctly for you? Michel is your machine 32bit? Trying to see any differences between your install and Amir's.
No my machine is 64bits, It has stopped working since FC14 it was fine on FC13 The version was webkitgtk-1.2.5-1.fc13.x86_64
My machine's 64-bit as well, and for me 1.3.5 works just fine. I do have 4GB of physical RAM + 6GB swap though.
See also bug 648319.
They might be duplicate bugs, I have problems with gwibber, gnome-calender and gnome-phone-manager in FC14. They all just crash! (Shotwell just crashesh on facebook, it works fine with picassa). Also gnome-session does not start fine, window-manager and nautilus are not started. I feel some basic package has a bug causing lots of trouble in FC14
So, please close as duplicate. I don't expect Peter doing anything about this bug, but we'are working on bug 648319.
I'm going to close this as a dup of 648319. My current theory over there is that this affects people with 64bit installs that have less than 4GB of physical memory. Lets continue over there. *** This bug has been marked as a duplicate of bug 648319 ***