Summary: | picasawebexport unable to create non listed album | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Philippe ROUBACH <philippe.roubach> |
Component: | Plugin-WebService-Google | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | vardhman |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.2.0 | |
Sentry Crash Report: |
Description
Philippe ROUBACH
2008-11-15 15:45:54 UTC
I'm not sure, but i think this point have been fixed by Jain (PicasaWebExport plugin maintainer) with KDE4 port. Gilles Caulier thanks but i watch kde 4 development since 2008 april and my conclusion is : i wait for kde 4.2.0 and perhaps 4.2.1 or 4.3.0 to change why ? according to my needs uncomplete buggy Philippe, you can easily install and use digikam 0.10 without running KDE 4.1. etc. on your desktop. I.e., if you have the required libs, you can use digkkam from anything you want, like Gnome, FVWM, .... Of course note, that 0.10 is under heavy development and the general recommendation is: "do not use in production" (yet....). (In reply to comment #3) > Philippe, you can easily install and use digikam 0.10 without running KDE 4.1. ok thanks i will try to compile 0.10 with my Mandriva 2008.1 when there will be a stable release Phillipe, Under Mandriva 2008.1, i don't recomend to try to compile digiKam, because kdelibs is an old version (KDE 4.0.3). Use Mandriva 2009.0 where KDE 4.1.2 is installed. It's really better. You can use a separate partition to install 2009.0, or another computer, or with VirtualBox In 2009.0, KDE3.5.x still available, but it's not the default desktop (KDE 4.1.2). You need to take a care to install other desktops during setup and login to KDE3 by default. Gilles Caulier there is a simple way if i upload this is because i work on picasaweb album thus i have an opened picasaweb session then i can create an unlisted album :) This is fixed in KDE4 version now (well tested at my end). ok thanks is it backported in digikam 0.9.5 ? |