Re: Digikam-users Digest, Vol 143, Issue 12
Locked
Re: Digikam-users Digest, Vol 143, Issue 12
 
|
Hy,
Slow start. How start in terminal. If write digikam, it seems starts a new configuration. antoni ------ Original Message ------ From: [hidden email] To: [hidden email] Sent: 3/4/2017 18:56:15 Subject: Digikam-users Digest, Vol 143, Issue 12 >Send Digikam-users mailing list submissions to > [hidden email] > >To subscribe or unsubscribe via the World Wide Web, visit > https://mail.kde.org/mailman/listinfo/digikam-users >or, via email, send a message with subject or body 'help' to > [hidden email] > >You can reach the person managing the list at > [hidden email] > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Digikam-users digest..." > > >Today's Topics: > > 1. Re: AW: Dgk 5.5 very slow start (Gilles Caulier) > 2. Re: Dgk 5.5 very slow start (Hella Breitkopf) > 3. Re: Dgk 5.5 very slow start (Gilles Caulier) > 4. Re: New digikam website source available from KDE's git > server (pbhj) > 5. Re: Content revision status update (Pat David) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 3 Apr 2017 16:12:55 +0200 >From: Gilles Caulier <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: AW: Dgk 5.5 very slow start >Message-ID: > <[hidden email]> >Content-Type: text/plain; charset="utf-8" > >This can be also something around similarity search. I'm not sure. The >debug trace on the console must be informative... > >Gilles Caulier > >2017-04-03 15:37 GMT+02:00 Andrey Goreev <[hidden email]>: > >> If you are on Linux please run digiKam in terminal and watch what is >> showing in it on startup. I suspect digiKam is still creating >>thumbnails. >> It takes long time for a large collection especially if you have many >>video >> files. >> >> Sent from my Samsung Galaxy smartphone. >> >> -------- Original message -------- >> From: "Dumelle, Timo (E+K)" <[hidden email]> >> Date: 2017-04-03 2:18 AM (GMT-07:00) >> To: digiKam - Home Manage your photographs as a professional with the >> power of open source <[hidden email]> >> Subject: AW: Dgk 5.5 very slow start >> >> Hi, >> >> >> >> i have the very same issue. >> >> >> >> DigiKam 5.5 with mysql external >> >> Pictures are on a NAS drive >> >> Picasa has no problems with this drive. >> >> There are ~ 220000 items >> >> >> >> Digikam startup takes ~ 15 to 30 minutes >> >> >> >> *Von:* Digikam-users [mailto:[hidden email]] *Im >>Auftrag >> von *Andrey Goreev >> *Gesendet:* Montag, 27. März 2017 16:07 >> *An:* antoni olivella <[hidden email]>; digiKam - Home >>Manage >> your photographs as a professional with the power of open source < >> [hidden email]> >> *Betreff:* Re: Dgk 5.5 very slow start >> >> >> >> Hello, >> >> >> >> I have never had such issue before. >> >> Was the process any faster on another system (what system?) ? >> >> Are you using mysql or sqlite? >> >> How many items are in the database? >> >> Where the database file is located (HDD?, its speed?, SSD ?) >> >> >> >> Sent from my Samsung Galaxy smartphone. >> >> >> >> -------- Original message -------- >> >> From: antoni olivella <[hidden email]> >> >> Date: 2017-03-27 7:58 AM (GMT-07:00) >> >> To: [hidden email] >> >> Subject: Dgk 5.5 very slow start >> >> >> >> Hello, >> >> >> >> Installed 5.5 in Kubuntu VM. >> >> >> >> Reading db in the start take now too long. More than 15 min. >> >> >> >> I can see only uses 1.7 gb of memory out of available 5.8 >> >> >> >> Any solution? >> >> >> >> antoni >> >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://mail.kde.org/pipermail/digikam-users/attachments/20170403/db11eba1/attachment-0001.html> > >------------------------------ > >Message: 2 >Date: Mon, 3 Apr 2017 16:46:22 +0200 >From: Hella Breitkopf <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: Dgk 5.5 very slow start >Message-ID: > <[hidden email]> >Content-Type: text/plain; charset=UTF-8 > >Hi, > >I've updated my digikam on Saturday to 5.5.0 >and the start is on my account @home suddenly very very slow, too. >Here @work I've got a very small database and don't see problems. > >I am using digikam on opensuse tumbleweed, plasma 5. > >~/Pictures/meta/digikam4.db (sqlite) is 162MB and located on SSD. > >Unluckily if I try to read my personalized function key settings >digikam crashes, so I've been waiting for digikam to start rather >a long time more than once, yesterday. CLI start or even >strace -e open -f didn't show anything special >in my eyes (but I am willing to upload any debugging information >wanted this evening). > >What type of startup options / strace options would be helpful >for debugging in this case? > >Best wishes, >Hella > >-- >[hidden email] >http://www.unixwitch.de > > >------------------------------ > >Message: 3 >Date: Mon, 3 Apr 2017 17:25:47 +0200 >From: Gilles Caulier <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: Dgk 5.5 very slow start >Message-ID: > <CAHFG6sHUO=[hidden email]> >Content-Type: text/plain; charset="utf-8" > >2017-04-03 16:46 GMT+02:00 Hella Breitkopf <[hidden email]>: > >> Hi, >> >> I've updated my digikam on Saturday to 5.5.0 >> and the start is on my account @home suddenly very very slow, too. >> Here @work I've got a very small database and don't see problems. >> >> I am using digikam on opensuse tumbleweed, plasma 5. >> >> ~/Pictures/meta/digikam4.db (sqlite) is 162MB and located on SSD. >> >> Unluckily if I try to read my personalized function key settings >> digikam crashes, so I've been waiting for digikam to start rather >> a long time more than once, yesterday. CLI start or even >> strace -e open -f didn't show anything special >> in my eyes (but I am willing to upload any debugging information >> wanted this evening). >> >> What type of startup options / strace options would be helpful >> for debugging in this case? >> > >Nothing. the text trace on the console must be enough to discover where >application hand. > >If not, running in to GDB can help. When it hand, just press CTRL+C and >enter "bt" to see where you stop the application. This can help. > >Gilles Caulier >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://mail.kde.org/pipermail/digikam-users/attachments/20170403/1330c4b4/attachment-0001.html> > >------------------------------ > >Message: 4 >Date: Mon, 3 Apr 2017 16:27:24 +0100 >From: pbhj <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: New digikam website source available from KDE's git > server >Message-ID: <[hidden email]> >Content-Type: text/plain; charset=utf-8; format=flowed > >FWIW as a long term KDE+digikam user I don't think much has changed in >what I do for several years. There's probably more value in slightly >out >of date generic videos than in not having videos at all. But I'd agree >that you need someone to own the video production and be prepared to >update them, maybe every year, if there are significant changes. > > >On 03/04/17 10:53, Dmitri Popov wrote: >>> since we have appimages, it should be much easier :-) >> Sure, but re-recording videos still requires time and effort. >> >> Best, >> Dmitri >> >> On Mon, Apr 3, 2017 at 10:51 AM, jdd <[hidden email]> wrote: >>> Le 03/04/2017 à 09:35, Dmitri Popov a écrit : >>>> It's a good idea only if someone will keep the videos updated. The >>>> pace of digiKam's development will make most videos outdated in a >>>> matter of months, and having obsolete videos on the website doesn't >>>> make a good impression. >>> >>> since we have appimages, it should be much easier :-) >>> >>> jdd >>> > > > >------------------------------ > >Message: 5 >Date: Mon, 03 Apr 2017 16:55:56 +0000 >From: Pat David <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: Content revision status update >Message-ID: > <[hidden email]> >Content-Type: text/plain; charset="utf-8" > >Awesome, thanks Dmitri! I wonder if we shouldn't use something other >than >email for this for better visibility? (Not sure about what's available >on >the KDE infrastructure for issue/enhancement tracking... > >On Mon, Apr 3, 2017 at 2:33 AM Dmitri Popov <[hidden email]> wrote: > >> Hello, >> >> I've finished revising the about.md and features.md pages. I >> integrated the content of the overview.md into about.md, as there is >> no reason to keep the content split in tiny chunks. Anyway, take a >> look and let me know what you think. >> >> Also, perhaps it's better to collaborate on the website via email, >> instead of clogging this list. Feel free to contact me at >> [hidden email], so I have your email addresses. >> >> Best, >> Dmitri >> >-- >https://patdavid.net >GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://mail.kde.org/pipermail/digikam-users/attachments/20170403/4bd7be51/attachment.html> > >------------------------------ > >Subject: Digest Footer > >_______________________________________________ >Digikam-users mailing list >[hidden email] >https://mail.kde.org/mailman/listinfo/digikam-users > > >------------------------------ > >End of Digikam-users Digest, Vol 143, Issue 12 >********************************************** |
Re: Digikam-users Digest, Vol 143, Issue 12
|
|
Normally you can right click on the launcher (desktop icons or main menu entry), check the box "Launch in terminal" and save. If you use appimage you can just drag and drop it to the terminal. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: antoni olivella <[hidden email]> Date: 2017-04-03 11:55 AM (GMT-07:00) To: [hidden email] Subject: Re: Digikam-users Digest, Vol 143, Issue 12 Slow start. How start in terminal. If write digikam, it seems starts a new configuration. antoni ------ Original Message ------ From: [hidden email] To: [hidden email] Sent: 3/4/2017 18:56:15 Subject: Digikam-users Digest, Vol 143, Issue 12 >Send Digikam-users mailing list submissions to > [hidden email] > >To subscribe or unsubscribe via the World Wide Web, visit > https://mail.kde.org/mailman/listinfo/digikam-users >or, via email, send a message with subject or body 'help' to > [hidden email] > >You can reach the person managing the list at > [hidden email] > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Digikam-users digest..." > > >Today's Topics: > > 1. Re: AW: Dgk 5.5 very slow start (Gilles Caulier) > 2. Re: Dgk 5.5 very slow start (Hella Breitkopf) > 3. Re: Dgk 5.5 very slow start (Gilles Caulier) > 4. Re: New digikam website source available from KDE's git > server (pbhj) > 5. Re: Content revision status update (Pat David) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 3 Apr 2017 16:12:55 +0200 >From: Gilles Caulier <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: AW: Dgk 5.5 very slow start >Message-ID: > <[hidden email]> >Content-Type: text/plain; charset="utf-8" > >This can be also something around similarity search. I'm not sure. The >debug trace on the console must be informative... > >Gilles Caulier > >2017-04-03 15:37 GMT+02:00 Andrey Goreev <[hidden email]>: > >> If you are on Linux please run digiKam in terminal and watch what is >> showing in it on startup. I suspect digiKam is still creating >>thumbnails. >> It takes long time for a large collection especially if you have many >>video >> files. >> >> Sent from my Samsung Galaxy smartphone. >> >> -------- Original message -------- >> From: "Dumelle, Timo (E+K)" <[hidden email]> >> Date: 2017-04-03 2:18 AM (GMT-07:00) >> To: digiKam - Home Manage your photographs as a professional with the >> power of open source <[hidden email]> >> Subject: AW: Dgk 5.5 very slow start >> >> Hi, >> >> >> >> i have the very same issue. >> >> >> >> DigiKam 5.5 with mysql external >> >> Pictures are on a NAS drive >> >> Picasa has no problems with this drive. >> >> There are ~ 220000 items >> >> >> >> Digikam startup takes ~ 15 to 30 minutes >> >> >> >> *Von:* Digikam-users [mailto:[hidden email]] *Im >>Auftrag >> von *Andrey Goreev >> *Gesendet:* Montag, 27. März 2017 16:07 >> *An:* antoni olivella <[hidden email]>; digiKam - Home >>Manage >> your photographs as a professional with the power of open source < >> [hidden email]> >> *Betreff:* Re: Dgk 5.5 very slow start >> >> >> >> Hello, >> >> >> >> I have never had such issue before. >> >> Was the process any faster on another system (what system?) ? >> >> Are you using mysql or sqlite? >> >> How many items are in the database? >> >> Where the database file is located (HDD?, its speed?, SSD ?) >> >> >> >> Sent from my Samsung Galaxy smartphone. >> >> >> >> -------- Original message -------- >> >> From: antoni olivella <[hidden email]> >> >> Date: 2017-03-27 7:58 AM (GMT-07:00) >> >> To: [hidden email] >> >> Subject: Dgk 5.5 very slow start >> >> >> >> Hello, >> >> >> >> Installed 5.5 in Kubuntu VM. >> >> >> >> Reading db in the start take now too long. More than 15 min. >> >> >> >> I can see only uses 1.7 gb of memory out of available 5.8 >> >> >> >> Any solution? >> >> >> >> antoni >> >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://mail.kde.org/pipermail/digikam-users/attachments/20170403/db11eba1/attachment-0001.html> > >------------------------------ > >Message: 2 >Date: Mon, 3 Apr 2017 16:46:22 +0200 >From: Hella Breitkopf <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: Dgk 5.5 very slow start >Message-ID: > <[hidden email]> >Content-Type: text/plain; charset=UTF-8 > >Hi, > >I've updated my digikam on Saturday to 5.5.0 >and the start is on my account @home suddenly very very slow, too. >Here @work I've got a very small database and don't see problems. > >I am using digikam on opensuse tumbleweed, plasma 5. > >~/Pictures/meta/digikam4.db (sqlite) is 162MB and located on SSD. > >Unluckily if I try to read my personalized function key settings >digikam crashes, so I've been waiting for digikam to start rather >a long time more than once, yesterday. CLI start or even >strace -e open -f didn't show anything special >in my eyes (but I am willing to upload any debugging information >wanted this evening). > >What type of startup options / strace options would be helpful >for debugging in this case? > >Best wishes, >Hella > >-- >[hidden email] >http://www.unixwitch.de > > >------------------------------ > >Message: 3 >Date: Mon, 3 Apr 2017 17:25:47 +0200 >From: Gilles Caulier <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: Dgk 5.5 very slow start >Message-ID: > <CAHFG6sHUO=[hidden email]> >Content-Type: text/plain; charset="utf-8" > >2017-04-03 16:46 GMT+02:00 Hella Breitkopf <[hidden email]>: > >> Hi, >> >> I've updated my digikam on Saturday to 5.5.0 >> and the start is on my account @home suddenly very very slow, too. >> Here @work I've got a very small database and don't see problems. >> >> I am using digikam on opensuse tumbleweed, plasma 5. >> >> ~/Pictures/meta/digikam4.db (sqlite) is 162MB and located on SSD. >> >> Unluckily if I try to read my personalized function key settings >> digikam crashes, so I've been waiting for digikam to start rather >> a long time more than once, yesterday. CLI start or even >> strace -e open -f didn't show anything special >> in my eyes (but I am willing to upload any debugging information >> wanted this evening). >> >> What type of startup options / strace options would be helpful >> for debugging in this case? >> > >Nothing. the text trace on the console must be enough to discover where >application hand. > >If not, running in to GDB can help. When it hand, just press CTRL+C and >enter "bt" to see where you stop the application. This can help. > >Gilles Caulier >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://mail.kde.org/pipermail/digikam-users/attachments/20170403/1330c4b4/attachment-0001.html> > >------------------------------ > >Message: 4 >Date: Mon, 3 Apr 2017 16:27:24 +0100 >From: pbhj <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: New digikam website source available from KDE's git > server >Message-ID: <[hidden email]> >Content-Type: text/plain; charset=utf-8; format=flowed > >FWIW as a long term KDE+digikam user I don't think much has changed in >what I do for several years. There's probably more value in slightly >out >of date generic videos than in not having videos at all. But I'd agree >that you need someone to own the video production and be prepared to >update them, maybe every year, if there are significant changes. > > >On 03/04/17 10:53, Dmitri Popov wrote: >>> since we have appimages, it should be much easier :-) >> Sure, but re-recording videos still requires time and effort. >> >> Best, >> Dmitri >> >> On Mon, Apr 3, 2017 at 10:51 AM, jdd <[hidden email]> wrote: >>> Le 03/04/2017 à 09:35, Dmitri Popov a écrit : >>>> It's a good idea only if someone will keep the videos updated. The >>>> pace of digiKam's development will make most videos outdated in a >>>> matter of months, and having obsolete videos on the website doesn't >>>> make a good impression. >>> >>> since we have appimages, it should be much easier :-) >>> >>> jdd >>> > > > >------------------------------ > >Message: 5 >Date: Mon, 03 Apr 2017 16:55:56 +0000 >From: Pat David <[hidden email]> >To: digiKam - Home Manage your photographs as a professional with the > power of open source <[hidden email]> >Subject: Re: Content revision status update >Message-ID: > <[hidden email]> >Content-Type: text/plain; charset="utf-8" > >Awesome, thanks Dmitri! I wonder if we shouldn't use something other >than >email for this for better visibility? (Not sure about what's available >on >the KDE infrastructure for issue/enhancement tracking... > >On Mon, Apr 3, 2017 at 2:33 AM Dmitri Popov <[hidden email]> wrote: > >> Hello, >> >> I've finished revising the about.md and features.md pages. I >> integrated the content of the overview.md into about.md, as there is >> no reason to keep the content split in tiny chunks. Anyway, take a >> look and let me know what you think. >> >> Also, perhaps it's better to collaborate on the website via email, >> instead of clogging this list. Feel free to contact me at >> [hidden email], so I have your email addresses. >> >> Best, >> Dmitri >> >-- >https://patdavid.net >GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://mail.kde.org/pipermail/digikam-users/attachments/20170403/4bd7be51/attachment.html> > >------------------------------ > >Subject: Digest Footer > >_______________________________________________ >Digikam-users mailing list >[hidden email] >https://mail.kde.org/mailman/listinfo/digikam-users > > >------------------------------ > >End of Digikam-users Digest, Vol 143, Issue 12 >********************************************** |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |