[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored [patch]

2016-08-05 Thread Maik Qualmann via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

--- Comment #21 from Maik Qualmann  ---
Git commit af3309fe913933fcbc9fd05066ee56e0260e195f by Maik Qualmann.
Committed on 05/08/2016 at 18:41.
Pushed by mqualmann into branch 'master'.

apply patch #100439 from Simon to add information about configuration
transition to welcome screen

M  +20   -5utilities/assistants/firstrun/welcomepage.cpp

http://commits.kde.org/digikam/af3309fe913933fcbc9fd05066ee56e0260e195f

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored [patch]

2016-08-04 Thread Simon via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

--- Comment #20 from Simon  ---
Hi Gilles,

Do you plan to include this or something similar before the 5.1.0 release?
This is a major reason why digikam 5 is still in the experimental 
repository on debian. The "compatibility break" without any notice is 
considered a major issue for the user.

Cheers,
Simon

On 04/08/16 12:01, via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=364258
>
> caulier.gil...@gmail.com changed:
>
> What|Removed |Added
> 
>  Summary|Upgrade to 5.0  (beta6) |Upgrade to 5.0  (beta6)
> |:KDE4 application   |:KDE4 application
> |configuration rc files  |configuration rc files
> |ignored |ignored [patch]
>
> --- Comment #19 from caulier.gil...@gmail.com ---
> Thanks Simon for your patch.
>
> Gilles Caulier
>

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored [patch]

2016-08-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

caulier.gil...@gmail.com changed:

   What|Removed |Added

Summary|Upgrade to 5.0  (beta6) |Upgrade to 5.0  (beta6)
   |:KDE4 application   |:KDE4 application
   |configuration rc files  |configuration rc files
   |ignored |ignored [patch]

--- Comment #19 from caulier.gil...@gmail.com ---
Thanks Simon for your patch.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-08-03 Thread Simon via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

Simon  changed:

   What|Removed |Added

 CC||freisi...@gmail.com

--- Comment #18 from Simon  ---
Created attachment 100439
  --> https://bugs.kde.org/attachment.cgi?id=100439=edit
Add information about configuration transition to welcome screen.

I agree that this is a very important point for the user. Of course ideally the
transition problems would be removed, but as always: This is open-source, if
you want it done, do it.
I attached a patch that adds information about the (non-)migration of the
configuration to the welcome screen.

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-30 Thread Kristian via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

Kristian  changed:

   What|Removed |Added

 CC||kde-b...@kristiankoch.com

--- Comment #17 from Kristian  ---
I think as well that the current non-existing migration process from digikam 4
to 5 is pretty user unfriendly. I wondered also why I had to reconfigure
everything and my templates were gone. After some searching, I found this bug.
At least, my database wasn't fucked up. Since several bad experiences with
digikam breaking its db, I'm very cautious in this regard. 

I would have expected at least a piece of information somewhere that the config
paths changed. It shouldn't be so hard to implement a notice in the first-run
wizard. Alternatively, one could ask the user if he did use digikam 4 before
and if so, display some warnings. You could explain that the config path did
change and that the files can be copied by the user at own risk.
Furthermore, is there any reason why you do not make a copy of digikam4.db and
save it as digikam5.db (although the db didn't change)?

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-27 Thread Christian Trippe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

Christian Trippe  changed:

   What|Removed |Added

 CC||christiande...@web.de

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-12 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

ham...@laposte.net changed:

   What|Removed |Added

 CC||ham...@laposte.net

--- Comment #16 from ham...@laposte.net ---
(In reply to caulier.gilles from comment #8)
> Files to backport under Linux :
> 
> - ~/.kde4/share/config/digikamrc
> ...
> - ~/.kde4/share/apps/digikam/
> 
> New place under Linux :
> 
> - ~/.config/digikamrc
> ...

Here the migration was failed. It has removed all the databases entries :(
Here is a sample of messages when it scan the databases the 1st run :

digikam.database: Creating new Location  "/"  uuid 
"volumeid:?path=%2Fhome%2Fdomi%2FPhotos"
digikam.database: location for  "%2Fhome%2Fdomi%2FPhotos"  is available  true
KMemoryInfo: Platform identified :  "LINUX"
KMemoryInfo: TotalRam:  8376160256
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.database: Removed items: (1, 2, 3, 4, 5, 6) related items: ()
digikam.database: Removed items: (9) related items: ()
digikam.database: Removed items: (15747, 15945, 16033) related items: ()
digikam.database: Removed items: (2410, 2411, 2412, 2413, 2414, 2415, 2416,
2417, 2418, 2419, 2420, 2421, 2422, 2423, 2424, 2425, 2426, 2427, 2428, 2429,
2430, 2431, 2432, 2433, 2434, 2435, 2436, 2437, 2438, 2439, 2440, 2441, 2442,
2443, 2444, 2445, 2446, 2447, 2448, 2449, 2450, 2451, 2452, 2453, 2454, 2455,
2456) related items: ()
...
digikam.database: Removed items: (16304, 16305, 16306, 16307, 16308, 16309,
16310, 16311, 16312, 16313) related items: ()
digikam.database: Folder does not exist or is not readable: 
"%2Fhome%2Fdomi%2FPhotos"

Now, when it starts, I have this message :
digikam.database: Folder does not exist or is not readable: 
"%2Fhome%2Fdomi%2FPhotos"

Why %2F in place of slash ? it should be /home/domi/Photos" ??!!!
in digikamrc file, the path is correct :
Album Path=/home/domi/Photos
Database File Path=/home/domi/Photos

I have migrated another user successfully, and his folder appears correctly
with slash in path not %2F...

I think it's a clue.

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-08 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

--- Comment #15 from caulier.gil...@gmail.com ---
This one for ex : 

https://bugs.kde.org/show_bug.cgi?id=365079

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-08 Thread Jens B . Benecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

--- Comment #14 from Jens B. Benecke  ---
Also which bug report is about these crashes?

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-08 Thread Jens B . Benecke via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

--- Comment #13 from Jens B. Benecke  ---
Backups are a must anyway. (IMHO: Just install deja-dup and setup some remote
storage (a NAS or a cloud service) and stop thinking about it.)

Specifically, did you narrow down your search about 4.x settings digikam 5 so
that I can help doing some bisect testing?

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-08 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

--- Comment #12 from caulier.gil...@gmail.com ---
Alexey,

This is not implemented because we seen that old digikam 4.x settings from
digikamrc file crash violently the application and we haven't yet identified
which one exactly.

You must always make a backup of your database before a major update.

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-06 Thread Alexey Stukalov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

Alexey Stukalov  changed:

   What|Removed |Added

 CC||astuka...@gmail.com

--- Comment #11 from Alexey Stukalov  ---
That's amazing! The bug is there for a month and I guess the developers
understand its consequences and the fix is not very complex. Guess what? I've
just overwritten my old digikam4.db in the migration dialog without digikam
asking for any confirmation. Years of tags are lost. Well done digikam devs!

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 364258] Upgrade to 5.0 (beta6) :KDE4 application configuration rc files ignored

2016-07-06 Thread Simon Andric via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364258

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.