[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2018-11-08 Thread Sebastien Bacher
the uoa support got removed in https://launchpad.net/ubuntu/+source/shotwell/0.26.1-0ubuntu1 ** Changed in: shotwell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2014-12-02 Thread Jim Nelson
The Flickr double-free crash is reported at bug #1382843 (and easily reproduced). I don't know that it's the same as the bug reported for this ticket, so I'm not marking as a duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2014-12-02 Thread Simon Lyall
On Tue, 2 Dec 2014, Jim Nelson wrote: The Flickr double-free crash is reported at bug #1382843 (and easily reproduced). I don't know that it's the same as the bug reported for this ticket, so I'm not marking as a duplicate. Looking at #1382843 this is almost certainly what I am seeing rather

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2014-11-29 Thread Simon Lyall
Forgot to post crash message. shotwell:21178): Gtk-DEBUG: Connecting to session manager *** Error in `shotwell': corrupted double-linked list: 0x0890d7d0 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2014-11-29 Thread Simon Lyall
I just had a crash. Happened the instant I tried to publish to flickr. I upgraded to 14.10 yesterday and have had several crashes since, uploads seem to work about 50% of the time. I ran with: export SHOTWELL_LOG=1 export G_MESSAGES_DEBUG=all shotwell attached shotwell.log but not all details

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2013-11-15 Thread Sebastien Bacher
Thank you for your bug report. Hey Mardy, do you think you could have a look? That seems an issue in uoa patch we carry for shotwell ** Information type changed from Private to Public ** Changed in: shotwell (Ubuntu) Importance: Medium = High ** Changed in: shotwell (Ubuntu) Assignee:

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2013-11-15 Thread Sebastien Bacher
There is a better stacktrace on the errors.ubuntu.com report: https://errors.ubuntu.com/problem/e678dd3bb4c4325a55d018bb42eccadaf32a5633 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1225629 Title:

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2013-11-15 Thread Alberto Mardegan
Unfortunately the most important part (the code from shotwell) is missing debugging information. I'll try to investigate anyway; it looks like Online Accounts is returning an error, and the code which I wrote in shotwell doesn't handle it well. -- You received this bug notification because you

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2013-11-15 Thread Alberto Mardegan
Hi! I tried to reproduce this bug, but with no luck. Philip (and others who can reproduce this), can you please give me some more information about when this precisely happens? Is it consistently reproducible? Does it happen when you click on Login, or before that? If you can reproduce it

[Bug 1225629] Re: shotwell crashed with SIGSEGV in publishing_accounts_uoa_publisher_authenticator_on_processed()

2013-11-15 Thread Philip Khor
Hi, Strangely I can't reproduce it even by publishing the same photos (though using a different FB account). Unfortunately I can't remember precisely how this happened. My apologies. I'll try again ASAP to see if I can reproduce this bug using other methods. -- You received this bug