OAuth issues in 5.8

[Tac Tacelosky]

Sure -- but it's not doing that.

Is there a way to set the browser oAuth will use in digikam?  I can try
with both Firefox and Chrome, and post a video if that'll help.

By any chance, is there a command-line tool in digikam for setting the
oAuth token?

I've installed the appimage on a second computer, and it's behaving
better.  On my laptop, though, I upgraded from previous versions of
digikam, so maybe my config file is wrong.  Here's the output on startup --
maybe there's a problem with the plugins?  Where is the config file --
maybe I should delete that and restart digikam?

Shanghai, China Copyright (C) 2012-2016 Wang Bin (aka. Lucas Wang)
wbsecg1 at gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
capi::version: 0.6.0
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295,
skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295,
skipping unlock
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified
kf5.kservice.sycoca: Parse error in
"/home/tac/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" ,
line  1 , col  1 :  "unexpected end of file"
The desktop entry file "/usr/share/applications/unity-scope-gdrive.desktop"
has Type= "Application" but no Exec line
kf5.kservice.sycoca: Invalid Service :
"/usr/share/applications/unity-scope-gdrive.desktop"
The desktop entry file
"/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" has Type=
"Application" but no Exec line
kf5.kservice.sycoca: Invalid Service :
"/usr/share/applications/org.gnome.ChromeGnomeShell.desktop"
The desktop entry file "/usr/share/applications/unity-lens-photos.desktop"
has Type= "Application" but no Exec line
kf5.kservice.sycoca: Invalid Service :
"/usr/share/applications/unity-lens-photos.desktop"
org.kde.kcoreaddons: Error loading plugin "kipiplugin_remotestorage" "The
shared library was not found."
Plugin search paths are ("/tmp/.mount_digikaLtAdmz/usr/plugins",
"/tmp/.mount_digikaLtAdmz/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
kipi.library: Cannot create instance for plugin  "RemoteStorage"  (
"kipiplugin_remotestorage" )  with error:  "The shared library was not
found."
org.kde.kcoreaddons: Error loading plugin "kipiplugin_remotestorage" "The
shared library was not found."
Plugin search paths are ("/tmp/.mount_digikaLtAdmz/usr/plugins",
"/tmp/.mount_digikaLtAdmz/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
kipi.library: Cannot create instance for plugin  "RemoteStorage"  (
"kipiplugin_remotestorage" )  with error:  "The shared library was not
found."
org.kde.kcoreaddons: Error loading plugin "kipiplugin_remotestorage" "The
shared library was not found."
Plugin search paths are ("/tmp/.mount_digikaLtAdmz/usr/plugins",
"/tmp/.mount_digikaLtAdmz/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
kipi.library: Cannot create instance for plugin  "RemoteStorage"  (
"kipiplugin_remotestorage" )  with error:  "The shared library was not
found."
QFSFileEngine::open: No file name specified
QFSFileEngine::open: No file name specified


Thanks,

Tac

On Fri, Feb 2, 2018 at 6:34 AM, Maik Qualmann <metzpinguin at gmail.com> wrote:

> Also with OAuth it is necessary to log in with the browser and to confirm
> to
> the web service that the tool may access your account. After pressing on
> change account a browser window should open to log on. The difference now
> is
> that after login and confirmation the digiKam tool automatically receives
> the
> session token and is active. You should then see your username in the
> digiKam
> tool and you can use it.
>
> Maik
>
> Am Donnerstag, 1. Februar 2018, 16:32:44 CET schrieb Tac Tacelosky:
> > Hi, all.  First, kudos to the developers for such a great product.
> >
> > I saw that Digikam 5.8 refactored Flickr and Dropbox export to use oAuth2
> > rather than the problematic browser-basic login-with-hash-tag -- great!
> >
> > Alas, I can't seem to get it to work.  With dropbox, it looks like
> there's
> > a debug url, as it's going to http://127.0.0.1:8000/?code=
> QYjJ-r8n7etcetc...
> >
> > With Flickr, I can't seem to find where to put in the credentials,
> > shouldn't there be an "Add Account" here?
> >
> > [image: Inline image 1]
> >
> > Change Account | Add Account brings me back to this screen.
> >
> > Facebook still uses the browser-based authentication, but there's no auth
> > code anymore, but surely there's some way to upload to Facebook, yes?
> >
> > Thanks!  New to digikam (and indeed to Linux-based photography), but
> can't
> > wait to get more experience.
> >
> > Tac
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20180202/04bf20e9/attachment.html>