Bug 169695

Summary:	Crashes with cancel in Export to Picasaweb...
Product:	[Applications] digikam	Reporter:	Kelosepas <kikelon>
Component:	Plugin-WebService-Google	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	andresbajotierra, caulier.gilles, lure
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	0.3.0
Sentry Crash Report:

Description Kelosepas 2008-08-24 02:00:31 UTC

Version:           0.10.0 beta2 (using KDE 4.1.0)
OS:                Linux
Installed from:    Mandriva RPMs

Whith the Kipi plugins, if you select Export to Picasaweb without configured account for Picasa Web Albums (I mean no credentials),   appears a window "Checking if previous token is still valid", well, if you cancel from this windows Digikam crashes whith message:
"The application digiKam (digikam) crashed and caused the signal 11 (SIGSEGV).
Please help us improve the software you use by filing a report at http://bugs.kde.org. Useful details include how to reproduce the error, documents that were loaded, etc.",  and whithout any trace.

Comment 1 Andi Clemens 2008-08-24 02:21:51 UTC

I just tested it and can't confirm it. Assigning the bugreport to kde-imaging...

Comment 2 Kelosepas 2008-08-25 10:23:20 UTC

In the window i mentioned if you hit Cancel very quick the problem does not occur, but if you wait a few seconds and hit cance, Digikam crashes.
Platform: KDE 4.1 under Mandriva 2009.0 beta 2 inside a virtual machine in VMware Server 1.0.5 (sorry, too much risky platform)

Comment 3 caulier.gilles 2008-12-07 21:12:44 UTC

Kelosepas,

This problem still exists using digiKam 0.10.0-beta6 and kipi-plugins 0.2.0-beta4?

Gilles Caulier

Comment 4 Dario Andres 2008-12-10 13:40:52 UTC

May be related to bug 160453 ?

Comment 5 Kelosepas 2008-12-11 15:44:09 UTC

I will try to reproduce the problem cause i tested it in a virtual machine under VMware Server 1.0.5 running 2009, but now i'm running 2009 Official natively and can install KDE4 to test the bug.

Comment 6 Luka Renko 2009-03-21 21:18:36 UTC

I cannot reproduce this with KDE 4 0.2.0 release. Feel free to reopen if you can reproduce this problem.