Shotwell cannot publish to Facebook. Server redirect URL contained no session description

Bug #825401 reported by xlash911 on 2011-08-12
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Shotwell
New
Undecided
Unassigned
shotwell (Ubuntu)
Low
Unassigned

Bug Description

To reproduce :

Select a picture
Select Publish to Facebook
Log in to facebook via the publishing window
Name the computer for Facebook
display a brief success
Then display "Publishit to Facebook can't continue because an error occured: Server redirect URL contained no session description "

I updated from the default version in Ubuntu 11.04 to Shotwell 0.10.1, without success.

Changed in shotwell (Ubuntu):
status: New → Confirmed
Clint Rogers (clinton-yorba) wrote :

Hi,

Thank you for reporting this. We will try to reproduce it in-house as soon as possible. Is there anything else you can think of that might have made the session unusual? It seemed like Facebook publishing was working as recently as four days ago on our side.

Christopher Hill (ch6574) wrote :

> Is there anything else you can think of that might have made the session unusual?

Cannot speak on behalf of the original submitter, but for me the second Facebook authentication page (where you enter a name to remember the device by) is in Japanese, presumably due to my location being in Tokyo. I have no idea if this is relevant or not!

In addition to performing the same steps listed above under "To reproduce" I can see in Facebook's "Security settings", under "Active sessions" the following:

 Last accessed Today at 23:23 End activity
 Device name foo
 Location Tokyo, 13, JP (Approximate)
 Device type Mozilla/5.0 (X11; Linux x86_64)
      AppleWebKit/534.26+ (KHTML, like Gecko)
      Version/5.0 Safari/534.26+

And under the "Recognised devices" I see it also listed.

Hitting publish a second time in Shotwell tells me I have already "logged in and out" during this session, and that I need to restart the application to try again.

N.B. I'm using version 0.10.1

Same thing happens for me. I get to the second screen (in french I
believe), asking to name the device, I see a brief success, I get an
email from FB, but Shotwell doesn't like it.

I also try disabling Facebook forced-https security without success.

Guillaume

Le 2011-08-21 à 11:00, Chris <email address hidden> a écrit :

>> Is there anything else you can think of that might have made the
> session unusual?
>
> Cannot speak on behalf of the original submitter, but for me the second
> Facebook authentication page (where you enter a name to remember the
> device by) is in Japanese, presumably due to my location being in Tokyo.
> I have no idea if this is relevant or not!
>
> In addition to performing the same steps listed above under "To
> reproduce" I can see in Facebook's "Security settings", under "Active
> sessions" the following:
>
> Last accessed Today at 23:23 End activity
> Device name foo
> Location Tokyo, 13, JP (Approximate)
> Device type Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/534.26+ (KHTML, like Gecko)
> Version/5.0 Safari/534.26+
>
> And under the "Recognised devices" I see it also listed.
>
> Hitting publish a second time in Shotwell tells me I have already
> "logged in and out" during this session, and that I need to restart the
> application to try again.
>
> N.B. I'm using version 0.10.1
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/825401
>
> Title:
> Shotwell cannot publish to Facebook. Server redirect URL contained no
> session description
>
> Status in “shotwell” package in Ubuntu:
> Confirmed
>
> Bug description:
> To reproduce :
>
> Select a picture
> Select Publish to Facebook
> Log in to facebook via the publishing window
> Name the computer for Facebook
> display a brief success
> Then display "Publishit to Facebook can't continue because an error occured: Server redirect URL contained no session description "
>
>
> I updated from the default version in Ubuntu 11.04 to Shotwell 0.10.1, without success.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/825401/+subscriptions

Jennifer Sachs (jensachs) wrote :

I am in the US and receiving the same error. I've tried uploading my photos directly from my hard drive and not from Shotwell but the editing I've done is not saved there. I am new to using Linux and Shotwell but seems that I am not the only one with this problem. Is it best to not use Shotwell at all? I want to get my edited photos on Facebook. Thank you.

Jim Nelson (yorba-jim) wrote :

Chris and xlash911, we have an outstanding ticket for the problem you're describing (the Facebook page displaying in the wrong language): http://redmine.yorba.org/issues/3022

Jennifer, Shotwell is a non-destructive photo editor, which means it stores your changes internally rather than modifying the photo file on your hard drive. More information about that is here: http://www.yorba.org/shotwell/help/edit-nondestructive.html This means that, as you've discovered, uploading the files directly from your hard drive won't upload the changes you've made.

We've had problems in the past with Facebook because they change their protocol and its behavior with little to no warning to developers. It's possible that's the problem here.

I've ticketed this problem on our Redmine server. We'll take a look and see if we can figure out the problem: http://redmine.yorba.org/issues/4018

coco76 (giovanni-coriasco) wrote :

Hi,
I think I have found a WORKAROUND, at least for me...
If I temporarily disable both email & SMS Login Notifications in Account --> Account Settings --> Security --> Login Notifications inside Facebook settings, I can upload pictures again.
Please note that I have "Secure Browsing" and "Login Approvals" DISABLED too

I hope this may help.

@coco76 : Your workaround also works for me! Thanks

Once the workaround is set in Facebook, I no longer see the screen to name the new device, and it goes directly to the permissions screen for the shotwell app. Publishing works great now!

Changed in shotwell (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Low
Pieter (peterdeltafm) wrote :

@coco76, also here your workaround works on shotwell version 0.11.

I updated recently out of 0.10 to 0.11 but today i tried to upload with result the above mentioned problem.
I still use secure browsing setting, that seems not to be a problem here.

Matt Fischer (mfisch) wrote :

Can you guys retry again with 0.12 since the Facebook auth has been rewritten since 0.11.6 to use OAuth?

Changed in shotwell (Ubuntu):
status: Triaged → Incomplete
Jan Bongaerts (jbongaerts) wrote :

I started having these problems a few weeks ago, when trying to upload from abroad.
The connection bombed out after uploading the first photo, and I got an e-mail from facebook saying that someone tried to access my account and they weren't sure it was me.
Since then, I can't acces facebook from shotwell. It doesn't get through.
I haven't tried any of the abovementioned workarounds yet, but I'm not sure what will happen, since this thread is already quite old.

Jim Nelson (yorba-jim) wrote :

What version of Shotwell are you using? Have you tried logging out of Facebook from within Shotwell, then logging back in?

Lucas Beeler (lucas-yorba) wrote :

Hmm...it sounds like this may be more than just a login/logout issue. Facebook may have labeled the Shotwell Connect application untrusted in connection to your account (especially if you tried to login from a blacklisted IP). The way to correct this issue is to first log out of Facebook in Shotwell. Next, open your browser, navigate to Facebook and open up the "Apps" panel, then deauthorize the Shotwell Connect application. Finally, open Shotwell and try logging into Facebook again. This should trigger a "clean" login in which all new account/application bindings are established.

Kiren Pillay (kirenpillay1) wrote :

I tried this and it didn't work.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers