Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#47053 closed defect (fixed)

Settings Theme Configuration not working

Reported by: rv17070093@… Owned by: jgosmann (Jan Gosmann)
Priority: Normal Milestone:
Component: base Version:
Keywords: Cc: cgilles (HumanDynamo), mkae (Marko Käning), NicosPavlov, RJVB (René Bertin)
Port: digikam

Description

Just installed digiKam, Version 4.0.0 (beta) on Mac OS X 10.10.2

As per user guide:

'Color schemes are supplied like themes to personalize digiKam main interface for you pleasure. To access these settings select Settings → Themes from the menubar and select your preferred theme to use."

The default theme is available; when clicking on "Configuration" option, the system does not provide other themes to select from.

Thanks.

Attachments (5)

2.4 uninsall.tiff (32.2 KB) - added by rv17070093@… 5 years ago.
main.log (354.6 KB) - added by bugports@… 5 years ago.
Error log installing qtcurve
w_kdeartwork.jpg (33.6 KB) - added by bugports@… 5 years ago.
wo_kdeartwork.jpg (22.9 KB) - added by bugports@… 5 years ago.
Screen Shot 2015-03-14 at 22.04.17.png (112.2 KB) - added by RJVB (René Bertin) 5 years ago.

Download all attachments as: .zip

Change History (50)

comment:1 Changed 5 years ago by mf2k (Frank Schima)

Cc: caulier.gilles@… added
Owner: changed from macports-tickets@… to jan@…
Port: digikam added

In the future, please fill in the Port field and Cc the port maintainers (port info --maintainers digikam), if any.

comment:2 in reply to:  1 Changed 5 years ago by rv17070093@…

Replying to mf2k@…:

In the future, please fill in the Port field and Cc the port maintainers (port info --maintainers digikam), if any.

I'm sorry I failed to write in "port" information. I do not know anything on the matter of ports, their meaning and purpose and the way they are used. And I am not interested in learning and becoming and expert on these either.

You see, I'm just an old fellow that likes to tinker with camera stuff to play with the photos I've taken. I'm just an user, not a computer programmer.

After reading glowing reviews about DigiKam, I decided to download it but never imagined the complexity required in getting this app up and running.

And I thank you for your response; that gave me the opportunity to inform others like me, of my generation, not to bother with this app. It appears to be a good one but, at 75 years of age, I will not be able to keep up and maintain this software in good working order; it will be impossible for me to comply with all of the requirements needed to post a "some-one-please-help-me" with this issue and I do not want to leave my pictures and memories lost at the bottom of an application I can't manage.

So, I'm sorry I did not follow the rules. My last request is: could some one please assist me on how to remove all of that stuff I loaded onto my computer? And please forgive me for not entering the required port information.

  1. Valdes

comment:3 Changed 5 years ago by mkae (Marko Käning)

Cc: mk@… nicos@… rjvbertin@… added
Version: 2.3.3

Dear R.,

pleased don't feel offended by mf2k!!!

He is one of the very few who tries to keep this issue tracker clean and consistent. This job requires quite a lot of time which is why his standard phrase might drive you away from MacPorts.

But, let me tell you, that we take issues seriously here on MacPorts trac. It's just the sheer volume of tickets which needs very efficient handling by us volunteers who maintain ports, trac issues, the wiki or whatever needs to get done...

Anyway, you've got these options now:

1) uninstall digikam and all it's dependencies

2) uninstall MacPorts altogether

3) or don't give up (yet) and try installing digikam

How ever you decide, let us know, so that we can help you in your endeavour.

Best regards, Marko

comment:4 Changed 5 years ago by rv17070093@…

Dear Marko,

I'm sorry if my note insinuated in any way mf2k offended me with his reply regarding the need to use ports, and I apologize to all for this misunderstanding.

I know of the need you have to enforce rules in order to organize, manage and properly track the great volume of communications you receive daily.

The current path to install and manage this application is too complex and it demands a good understanding of the different processes required. At my age, if it is not possible for me now to do all of the leg work needed to overcome / troubleshoot technical issues, and knowing that future maintenance and upgrades would require more of this work, I do not want to commit to such endeavor.

Therefore, I will appreciate very much your help in performing options 1 and 2 you suggested.

Sincerely,

comment:5 in reply to:  4 Changed 5 years ago by mkae (Marko Käning)

Dear Ricardo,

Replying to rv17070093@…:

I'm sorry if my note insinuated in any way mf2k offended me with his reply regarding the need to use ports, and I apologize to all for this misunderstanding.

no worries, I don't think he felt offended, probably didn't even read this. I just wanted to explain a little...

The current path to install and manage this application is too complex and it demands a good understanding of the different processes required.

I perfectly well understand.

Maintaing KDE applications on MacPorts is still a tricky business, although we've made great progress during the last year there are still many problems to be solved.

For digikam René has submitted already two suggestions on how to upgrade the application to newer versions 4.3.0 (#45107) and 4.6.0 (#46317), but not even I have tested them up to now, as I am swamped with other things.

Therefore, I will appreciate very much your help in performing options 1 and 2 you suggested.

Please follow the advice given in the section "2.4. Uninstall" of the MacPorts Guide for option 2 (which includes 1 of course).

Admittedly MacPorts is more a techie thing (for all those console-affine power-users who want to install all kinds of Open Source stuff) and not so much meant for normal users who are much more accustomed to the AppStore.

Best regards, Marko

Last edited 5 years ago by mkae (Marko Käning) (previous) (diff)

comment:6 Changed 5 years ago by RJVB (René Bertin)

This is not a defect in digiKam. It provides a shortcut to select from the colour schemes that are available through/for KDE; if only the standard scheme is installed that's the only choice you'll get.

I see Marko already pointed to the uninstall guide.

Last edited 5 years ago by RJVB (René Bertin) (previous) (diff)

Changed 5 years ago by rv17070093@…

Attachment: 2.4 uninsall.tiff added

comment:7 Changed 5 years ago by rv17070093@…

Hi all,

I am trying to follow instructions given in ​section "2.4. Uninstall" of the MacPorts Guide, and the 2.4 uninsall.tiff attachment I just included illustrates my predicament. I do not know where to go from there.

Would it be possible to have with any of you a 1-1 chat as I execute the instruction to help me with this process.

Thanks

If you cant access this attachment, this is a picture of the terminal window stating " sudo port command not found."

comment:8 Changed 5 years ago by mkae (Marko Käning)

Ricardo, yes, we can arrange a hands-on chat in order to support you in your task. I am Greenwhich+1, how about you?

You screenshot shows that port cannot be found on your system. This usually means on the console, that your paths aren't set correctly.

In 2.5. MacPorts and the Shell it is explained, that you need to set at least this:

$ export PATH=/opt/local/bin:/opt/local/sbin:$PATH

in order to allow your shell to find the 'port' executable.

May I ask you HOW did you install MacPorts in the first place and how did you install digikam in the next step. I am surprised to see that you were able to get as far as running digikam without having a properly set up MacPorts-ish shell environment.

comment:9 in reply to:  description Changed 5 years ago by bugports@…

The default theme is available; when clicking on "Configuration" option, the system does not provide other themes to select from.

The other themes for Digikam are provided by the kdeartwork package. Unless kdeartwork is not installed, you only have the default theme to choose. So if you install kdeartwork by typing 'sudo port install kdeartwork' into the terminal, you should be able to choose the alternative themes.

Best, Planet

comment:10 Changed 5 years ago by mkae (Marko Käning)

Thanks for reporting! :)

If someone independently could verify this and report back, we can close this issue as "invalid".

comment:11 Changed 5 years ago by mkae (Marko Käning)

I tested here

  • MacPorts' current (but outdated) digiKam 4.0.0
  • on Mavericks 10.9.5
  • with port:kde4-workspace and port:qtcurve installed - as recommended by MacPorts' KDE wiki page
  • without port:kdeartwork installed

and yet I saw various themes in the "Settings/Themes" menu as well as in the "Colors - KDE Control Module" when clicking "Settings/Themes/Configuration...".

Well, I consider the installation of kde4-workspace and qtcurve as a crucial step here. One should test how the application behaves without these ports installed!!!

Otherwise Yosemite itself may also have an issue here... Can someone test it, please?

A quick test of the program showed that it works nicely without problems, i.e. not only changing themes is possible without any issues, also importing photos, adding faces, clicking around in the GUI...

Changed 5 years ago by bugports@…

Attachment: main.log added

Error log installing qtcurve

comment:12 in reply to:  11 Changed 5 years ago by bugports@…

I'm on 10.6.8 with no qtcurve installed. Uninstalled kdeartwork just now and tried to install qtcurve instead, but the build did not succeed, see log. Without kdeartwork the themes are gone.

Last edited 5 years ago by bugports@… (previous) (diff)

comment:13 Changed 5 years ago by mkae (Marko Käning)

Yes, unfortunately it doesn't build on SL at the moment, see also #45625.

Try - as shown in that ticket - to build qtcurve with the gcc compiler.

Last edited 5 years ago by mkae (Marko Käning) (previous) (diff)

comment:14 Changed 5 years ago by mkae (Marko Käning)

Interesting, I have themes also without kdeartwork...

Do you have the ports kde4-runtime and kde4-baseapps installed?

Changed 5 years ago by bugports@…

Attachment: w_kdeartwork.jpg added

Changed 5 years ago by bugports@…

Attachment: wo_kdeartwork.jpg added

comment:15 in reply to:  14 ; Changed 5 years ago by bugports@…

Do you have the ports kde4-runtime and kde4-baseapps installed?

Yes, as they belong to the DigiKam port as far as I know. But I have some issues here - DigiKam 4 is not multilangual anymore, compared to 3.5 and I does not work with the Lisanet Mac Gimp, only with the Macports version. Maybe this is caused by the different way, Digikam is installed? Would you mind to explain, how to choose the gcc compiler? Thank you in advance!

comment:16 in reply to:  15 ; Changed 5 years ago by mkae (Marko Käning)

Replying to bugports@…:

Do you have the ports kde4-runtime and kde4-baseapps installed?

Yes, as they belong to the DigiKam port as far as I know. But I have some issues here - DigiKam 4 is not multilangual anymore,

it is not?

compared to 3.5 and I does not work with the Lisanet Mac Gimp, only with the Macports version. Maybe this is caused by the different way, Digikam is installed?

Could be.

Would you mind to explain, how to choose the gcc compiler? Thank you in advance!

Check out the comment:5 of said ticket!

port install QtCurve configure.compiler=macports-gcc-4.8

comment:17 in reply to:  16 Changed 5 years ago by bugports@…

Yes, as they belong to the DigiKam port as far as I know. But I have some issues here - DigiKam 4 is not multilangual anymore,

it is not?

Since Version 4.

Check out the comment:5 of said ticket!

Thanks, and sorry for not to simply mention, that I tried the hint w.o. success.

port install QtCurve configure.compiler=macports-gcc-4.8 }}}

Seems I have to install gcc first... :)

Hmm, libgcc @4.9.2_1 (active), but

port install QtCurve configure.compiler=macports-gcc-4.9

also failed:

Error: port lookup failed: too many nested evaluations (infinite loop?) Error: Unable to execute port: upgrade git failed

Last edited 5 years ago by bugports@… (previous) (diff)

comment:18 Changed 5 years ago by bugports@…

I partially succeed by

sudo port install kde4-workspace qtcurve
kbuildsycoca4

Now kdeartwork is not installed, but themes and different widget styles are available even though build of qtcurve still failed. Like before, Digikam is still monolingual despite of choosing my prefered language in systemsettings.app.

comment:19 Changed 5 years ago by mkae (Marko Käning)

Yes, I should have pointed out the need for kbuildsycoca in the first place.

Well, what concerns the languages - it rings a bell - I think this is due to the fact that the app-specific translations for other languages are not available as separate ports, if I am not completely mistaken.

comment:20 Changed 5 years ago by RJVB (René Bertin)

Digikams's language files are part of the source distribution; they should get installed. My copy has been talking proper European English to me since I first installed it...

comment:21 in reply to:  19 Changed 5 years ago by bugports@…

Replying to mk@…:

Cheers for your patience, seems I'm a little step further...

Well, what concerns the languages - it rings a bell - I think this is due to the fact that the app-specific translations for other languages are not available as separate ports, if I am not completely mistaken.

Oh I see, sometimes the solution is more easy, than expected :-) Many thanks!

comment:22 in reply to:  20 Changed 5 years ago by bugports@…

Replying to rjvbertin@…:

Digikams's language files are part of the source distribution; they should get installed. My copy has been talking proper European English to me since I first installed it...

Isn't English the default language of DigiKam? Are you able to choose another language by DigiKam/Help/Switch Application Language?

Last edited 5 years ago by bugports@… (previous) (diff)

comment:23 Changed 5 years ago by mkae (Marko Käning)

digiKam's default language seems to be "American English" and René has obviously successfully set "European English"... Wondering how he achieved that.

comment:24 in reply to:  23 Changed 5 years ago by bugports@…

Replying to mk@…:

digiKam's default language seems to be "American English" and René has obviously successfully set "European English"... Wondering how he achieved that.

You are right, American English seems the default here as well. In DigiKam 3.5 you were able to choose any additionally installed language. Seems, that feature went by. In any other KDE app I am still able to choose the language, and that was possible, even before I had systemsettings.app installed - via Help Menu.

Changed 5 years ago by RJVB (René Bertin)

comment:25 Changed 5 years ago by mkae (Marko Käning)

As I said, I wonder how he managed to get an "European English" into there... :-)

I am eager to learn how he managed that in dikiKam.

I know from KMyMoney that it also ships only with the default language and that one would have to create separate language ports if one wanted to support other translations. At least that's what I thought it was the case last time I discussed this with another KDE developer.

comment:26 Changed 5 years ago by RJVB (René Bertin)

You saw my screenshot, right?

comment:27 in reply to:  26 Changed 5 years ago by mkae (Marko Käning)

Replying to rjvbertin@…:

You saw my screenshot, right?

No, only now. :)

Well, how did you get "British English" offered?

My "Country/Region & Languages - System Setttings" dialog offers only American English as the sole KDE language...

comment:28 Changed 5 years ago by RJVB (René Bertin)

I don't know exactly how digiKam's language selection interacts with the systemsettings dialog. I presume that it will follow whatever you select there, unless you override it with an app-specific setting as shown in my screenshot.

What's certain is that the dialog under Help/Switch Application Language shows the translations installed for the application in question, while the "Country/Region & Language" KCM will only show the installed translation bundles (corresponding to the KDE Applications). For instance, I could switch digiKam to French, but that KCM doesn't provide French as an option. For that, I'd have to install port:kde-l10n-fr in addition to port:kde-l10n-en_GB that I have installed.

So, no, I didn't do anything special to get UK English, or Swahili or maybe even Klingon. DigiKam's translations are part of the port.

comment:29 Changed 5 years ago by mkae (Marko Käning)

OK, I see, if other languages are part of the digikam port then it is the question, why you get to select "British English" and we don't...

comment:30 Changed 5 years ago by mkae (Marko Käning)

BTW, thanks to René, all buildbots successfully built digikam 4.8.0 by now. This latest version should be made available by rsync very soon...

comment:31 in reply to:  29 Changed 5 years ago by RJVB (René Bertin)

Them buildbots are fast ...

Replying to mk@…:

OK, I see, if other languages are part of the digikam port then it is the question, why you get to select "British English" and we don't...

My bad. I thought I had checked, but I must have had a bit too much wine tonight...

# Option to compile GUI translations

variant translations description {Build digiKam GUI translations} {}

if {[variant_isset translations]} {
    configure.args-append -DDIGIKAMSC_COMPILE_PO=ON
} else {
    configure.args-append -DDIGIKAMSC_CHECKOUT_PO:BOOL=OFF -DDIGIKAMSC_COMPILE_PO=off
}

comment:32 Changed 5 years ago by mkae (Marko Käning)

Ahhh, there we are! ;-) That explains it, indeed.

comment:33 in reply to:  32 ; Changed 5 years ago by bugports@…

Replying to mk@…:

Thanks for the upgrade, which built successfully - except that all of the face- and image-tags are currently gone. Under Help/Components Information there seems to be no Sqlite2 support. Maybe that's the reason?

I tried via Tools/Maintainance to reread image metadata to the database, without success.

Last edited 5 years ago by bugports@… (previous) (diff)

comment:34 Changed 5 years ago by mkae (Marko Käning)

Hi, oh, I wasn't thinking about such issues for migration. Well the latest port uses SQLite3. Well, I could imagine that one may find hints how to migrate the old data to the new database...

I do not know whether compiling it with SqLite2 support would still allow to use it with version 3... Perhaps we should come up with a variant for it?!

I hope you have a backup of that db somewhere?!

BTW, I played with that feature also a little and found that it wouldn't automagically identify faces, as I expected it would...

comment:35 in reply to:  33 ; Changed 5 years ago by mkae (Marko Käning)

Replying to bugports@…:

I tried via Tools/Maintainance to reread image metadata to the database, without success.

port:qt4-mac-sqlite3-plugin is set as digikam's dependency and I don't know whether it would be wise to introduce a variant replacing this dependency by port:qt4-mac-sqlite2-plugin to avoid loosing the metadata...

This rather asks for a migration tool, although I could imagine that a simple backup dump of the old file and a (perhaps partial) reimport into the new one would solve the issue.

I have my current db file in ~/DigiKam over here. Can you locate where your old db file is? I hope it did not get overwritten at the first start of the application...

Last edited 5 years ago by mkae (Marko Käning) (previous) (diff)

comment:36 in reply to:  35 Changed 5 years ago by bugports@…

Replying to mk@…:

Replying to bugports@…:

port:qt4-mac-sqlite3-plugin is set as digikam's dependency and I don't know whether it would be wise to introduce a variant replacing this dependency by port:qt4-mac-sqlite2-plugin to avoid loosing the metadata...

As long as I'm able to sort and find the pictures according to their face tags via MacOS Finder... But a database migration tool would be rather helpful. Am I wrong, or hasn't such a tool been part of digiKam 3 to migrate SQL to sqlite2?

This rather asks for a migration tool, although I could imagine that a simple backup dump of the old file and a (perhaps partial) reimport into the new one would solve the issue.

Great hint! My first attempt: I downloaded the shell script from Sqlite.org and tried:

sqlite /Users/Me/Pictures/digikam4.db .dump | sqlite3 /Users/Me/Pictures/NEW.DB

but it did not succeed.

I have my current db file in ~/DigiKam over here. Can you locate where your old db file is?

Yes, it's in my home directory/pictures and seems untouched as far.

I hope it did not get overwritten at the first start of the application...

Don't worry :-)

comment:37 in reply to:  34 ; Changed 5 years ago by bugports@…

Replying to mk@…:

BTW, I played with that feature also a little and found that it wouldn't automagically identify faces, as I expected it would...

To be honest - face detection in digiKam is a real pain in the a... Most of the face tags I had to set manually until I decided to use Picasa only for that task. Once the face tags were embedded into the pictures, I uninstalled Picasa...

Last edited 5 years ago by bugports@… (previous) (diff)

comment:38 Changed 5 years ago by mkae (Marko Käning)

Replying to bugports@…:

As long as I'm able to sort and find the pictures according to their face tags via MacOS Finder... But a database migration tool would be rather helpful. Am I wrong, or hasn't such a tool been part of digiKam 3 to migrate SQL to sqlite2?

I have no clue, sorry.

Great hint! My first attempt: I downloaded the shell script from Sqlite.org and tried:

sqlite /Users/Me/Pictures/digikam4.db .dump | sqlite3 /Users/Me/Pictures/NEW.DB

but it did not succeed.

Hmm, I don't know whether sqlite3 reads from stdin like that auto-creating a new db... Have you tried ".save FILE" in sqlite and ".restore FILE" in sqlite3?

Could also be that they changed their db structure in the meantime!

Yes, it's in my home directory/pictures and seems untouched as far.

Yes, that's what I also saw here when I upgraded from 4.0.0 to 4.8.0. Yet I am not sure about the metadata stored in the db file.

I think you should contact digiKam's developers directly and come back to here with what you learnt. IRC or their ML might be faster than creating a ticket at b.k.o. though!

comment:39 in reply to:  37 Changed 5 years ago by mkae (Marko Käning)

Replying to bugports@…:

To be honest - face detection in digiKam is a real pain in the a... Most of the face tags I had to set manually until I decided to use Picasa only for that task. Once the face tags were embedded into the pictures, I uninstalled Picasa...

Including the face tags in the pictures themselves is possible? (I didn't know.)

Well, yes, I learnt that Picasa does quite a good job detecting faces.

I hadn't seen that for digiKam (yet) and thus I thought I just don't know how to get it done properly. Reading your opinion now makes me think that digiKam is still on its way to get there...

comment:40 Changed 5 years ago by mkae (Marko Käning)

comment:41 Changed 5 years ago by mkae (Marko Käning)

I think we should move this discussion perhaps to the MacPorts-dev or KDE-MAC mailing list, as this is all not really related to the upgrade to 4.8.0. =)

Also, shouldn't we also mark this issue as resolved?

Last edited 5 years ago by mkae (Marko Käning) (previous) (diff)

comment:42 in reply to:  40 Changed 5 years ago by bugports@…

Replying to mk@…:

Have a look at these two RRs regarding face recognition:

Thank you!

I think we should move this discussion perhaps to the MacPorts-dev or KDE-MAC mailing list, as this is all not really related to the upgrade to 4.8.0. =)

You are right. Just joined the macports-dev list.

Last edited 5 years ago by bugports@… (previous) (diff)

comment:43 Changed 5 years ago by mkae (Marko Käning)

Resolution: fixed
Status: newclosed

comment:44 in reply to:  40 ; Changed 5 years ago by mkae (Marko Käning)

Replying to mk@…:

Have a look at these two RRs regarding face recognition:

Only now I realise that these are 8 months old...

Have no clue whether they're already included in digiKam and the RRs simply not closed, or not.

comment:45 in reply to:  44 Changed 5 years ago by mkae (Marko Käning)

Replying to mk@…:

Have no clue whether they're already included in digiKam and the RRs simply not closed, or not.

They are incorporated (only the RRs are not marked as submitted), as I have just learnt on digiKam-devel.

Note: See TracTickets for help on using tickets.