LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-17-2017, 04:03 PM   #1
Bourdieu
Member
 
Registered: Jan 2006
Location: Paris
Distribution: Slackware current
Posts: 38

Rep: Reputation: 11
Digikam segfault with current


Hi,

I do not use it very often, but when I tried to launch it recently on my slackware64 current box it immediately segfaulted.

I use SlackBuilds from slackbuilds.org with sbopkg.

I tried to recompile the whole queue but It didn't change anything.

I also tried with ponce slackbuilds for current, same result.

When I launch it in a terminal I only get "segmentation fault" and that's all.

Does anybody experiment the same result ? If no, do you have any idea to solve my problem ?

Packages version :
Code:
digikam-4.14.0-x86_64-3ponce
lensfun-0.3.2-x86_64-1ponce
libkface-15.08.3-x86_64-2ponce
libkgeomap4-15.08.3-x86_64-1ponce
libkvkontakte-4.12.0-x86_64-2ponce
liblqr-0.4.2-x86_64-1ponce
libpgf-7.15.32-x86_64-1ponce
opencv-3.1.0-x86_64-3ponce
ffmpeg-3.3.2-x86_64-1
Thanks for your help.
 
Old 07-17-2017, 04:18 PM   #2
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,040

Rep: Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031Reputation: 2031
Did you try uninstalling all those dependencies before recompiling the queue? Otherwise, the newer builds might've picked up older libraries.
 
Old 07-17-2017, 09:06 PM   #3
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,612

Rep: Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946
Hi Bourdieu,

the one in SBo is tested against -stable releases, not -current
I have digiKam 5.6.0 script already on my personal repository and that will become future digiKam script in the repository once KDE 5 goes into -current.

That will depends on framework5 and libkipi5 also available in my repository
 
Old 07-18-2017, 12:23 AM   #4
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 3,695

Rep: Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792Reputation: 1792
FWIW I just built digikam from SBo and all of its dependencies (with no additional patches) on a clean slackware64-current full install and it seems to work fine: you could try doing the same, it should work.

Last edited by ponce; 07-18-2017 at 12:40 AM.
 
Old 07-18-2017, 03:52 AM   #5
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,449
Blog Entries: 1

Rep: Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842
Quote:
Originally Posted by willysr View Post
......once KDE 5 goes into -current.....
That will be a sad day.


Speaking of digiKam, whatever happened to all the kipi-plugins used to extended the functionality of Gwenview?
I installed kde-5 yesterday, along with digiKam, and was quite surprised to see only a handful of plugins accessible from Gwenview.

Last edited by cwizardone; 07-18-2017 at 04:24 AM.
 
1 members found this post helpful.
Old 07-18-2017, 04:34 AM   #6
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 6,571

Rep: Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818
Quote:
Originally Posted by cwizardone View Post
That will be a sad day.
To the contrary. I can't wait for the old KDE4 to be brought to its death bed.

Your expectations of what Plasma5 should do for you are perhaps not matching with the direction its development is going, but you can always be vocal about your preferences - in the right places! Join the discussion in the KDE forums and Google+ groups, make a difference.
No KDE developer is going to read this Slackware forum for directions.
 
3 members found this post helpful.
Old 07-18-2017, 06:12 AM   #7
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,612

Rep: Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946Reputation: 946
Quote:
Originally Posted by cwizardone View Post
That will be a sad day.


Speaking of digiKam, whatever happened to all the kipi-plugins used to extended the functionality of Gwenview?
I installed kde-5 yesterday, along with digiKam, and was quite surprised to see only a handful of plugins accessible from Gwenview.
That's because i didn't build the extra package which contains the kipi-plugins in the current digiKam in SBo.
In my personal script, i have added that build and it's available in digiKam's menu.
 
Old 07-18-2017, 08:29 AM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 6,571

Rep: Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818
Quote:
Originally Posted by cwizardone View Post
Speaking of digiKam, whatever happened to all the kipi-plugins used to extended the functionality of Gwenview?
I installed kde-5 yesterday, along with digiKam, and was quite surprised to see only a handful of plugins accessible from Gwenview.
I checked Gwenview on Plasma5, and I see a lot of plugins that have their origin in the digikam package: http://imgur.com/a/QFP7n
You don't see those?
 
Old 07-18-2017, 10:11 AM   #9
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Posts: 1,375

Rep: Reputation: 1258Reputation: 1258Reputation: 1258Reputation: 1258Reputation: 1258Reputation: 1258Reputation: 1258Reputation: 1258Reputation: 1258
Several months ago I asked about Digikam no longer being a default app or even an "Extras" and was given an excellent explanation - for some reason Digikam is all-over-the-map with constantly changing dependencies so it is a moving target andf the cost of keeping up with it just isn't worth any benefit now that other apps more stable, do the same things. We all grow fond of certain apps and are reticent to just toss away hard won learning curves and smooth experience but I found I didn't miss Digikam more than about 5 minutes. YMMV but until such a time may come where Digikam settles down, it's just easier and of little adjustment to just wave bye bye.
 
Old 07-18-2017, 11:28 AM   #10
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,449
Blog Entries: 1

Rep: Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842
Quote:
Originally Posted by Alien Bob View Post
I checked Gwenview on Plasma5, and I see a lot of plugins that have their origin in the digikam package: http://imgur.com/a/QFP7n
You don't see those?
The export options? Yes, but I have no need for those. I'm looking for the image and tools plugins which have almost entirely disappeared.
Under "tools" there is one option to e-mail. Under "image" there are two options. What happened to the ability to edit or delete meta-data, the image manipulation tools, batch processing, etc., etc., etc.?

Last edited by cwizardone; 07-20-2017 at 11:33 AM. Reason: Typo.
 
Old 07-18-2017, 11:39 AM   #11
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,449
Blog Entries: 1

Rep: Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842
Quote:
Originally Posted by enorbet View Post
Several months ago I asked about Digikam no longer being a default app or even an "Extras" and was given an excellent explanation - for some reason Digikam is all-over-the-map with constantly changing dependencies so it is a moving target andf the cost of keeping up with it just isn't worth any benefit now that other apps more stable, do the same things. We all grow fond of certain apps and are reticent to just toss away hard won learning curves and smooth experience but I found I didn't miss Digikam more than about 5 minutes. YMMV but until such a time may come where Digikam settles down, it's just easier and of little adjustment to just wave bye bye.
I have tried digiKam several times over the years and have never cared for it.
At one time the digiKam developers made the kipi-plugins available as a separate package so you could install them if you needed them for Gwenview or other KDE applications. Most unfortunately, a few years ago (I've forgotten when) the developers, in their wisdom, HA!, decided to stop providing the plugins as standalone package and we are now required to install digiKam to get the plugins. Even if you never use digiKam, you have to install it to get the plugins.

Last edited by cwizardone; 07-20-2017 at 11:31 AM. Reason: Typo.
 
Old 07-18-2017, 11:51 AM   #12
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,449
Blog Entries: 1

Rep: Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842
Quote:
Originally Posted by Alien Bob View Post
To the contrary. I can't wait for the old KDE4 to be brought to its death bed.

Your expectations of what Plasma5 should do for you are perhaps not matching with the direction its development is going, but you can always be vocal about your preferences - in the right places! Join the discussion in the KDE forums and Google+ groups, make a difference.
No KDE developer is going to read this Slackware forum for directions.
I've been using KDE-5 since installing your packages, again, yesterday and my opinion hasn't changed a bit since the first time I tried it.
After KDE-4.13.3 was released, the first version of KDE-4 worth using, IMHO, I've been bouncing back and forth between Xfce and KDE-4. This most recent experience with KDE-5 has just cemented my plans to go completely to Xfce if and when KDE-5 is added to Slackware, and find replacements for what were my favorite KDE applications.
One thing I've noticed each time I've tried KDE-5, about 4 or 5 times, at this point, is it is just huge. The number of files and the space they require has to be far greater than KDE-4?

Last edited by cwizardone; 07-20-2017 at 11:29 AM. Reason: Typo.
 
Old 07-18-2017, 12:08 PM   #13
montagdude
Member
 
Registered: Apr 2016
Posts: 575

Rep: Reputation: 375Reputation: 375Reputation: 375Reputation: 375
What do you dislike so much about Plasma 5? It was a bit buggy in the beginning but has settled down nicely, IMO. To me, it's the same as KDE 4 but better looking and less cluttered.
 
Old 07-18-2017, 12:22 PM   #14
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 3,449
Blog Entries: 1

Rep: Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842Reputation: 842
Quote:
Originally Posted by montagdude View Post
What do you dislike so much about Plasma 5? It was a bit buggy in the beginning but has settled down nicely, IMO. To me, it's the same as KDE 4 but better looking and less cluttered.
My opinion is just the opposite. Worst looking desktop I've seen. Even after trying to "customize" it, it has that simplistic, almost childish appearance.
I'm guessing it is just impossible to keep the same method of changing settings from one version of qt to another?
I've been trying to move something I've added to the panel from one side to the other. Doesn't work the same way as KDE-4. Why does a user need to learn how to do this over and over.
If KDE were a car, every time a new version comes out, one would have to learn how to drive all over again. I can go rent a car, something that outwardly looks different from what I own, and yet I can get into it and drive away. No problem. The desktop developers need to learn people want to be able to do what they need to get done, without the controls changing with each and every new model.
 
Old 07-18-2017, 12:55 PM   #15
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 6,571

Rep: Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818Reputation: 3818
Quote:
Originally Posted by cwizardone View Post
One thing I've noticed each time I've tried KDE-5, about 4 or 5 times, at this point, is it is just huge. The number of files and the space they require has to be far greater than KDE-4?
Is that a gut feeling or did you really calculate the difference?

In Slackware 14.2:

Code:
652M    slackware64/slackware64/kde
386M    slackware64/slackware64/kdei
Plasma5 shows:
Code:
906M    ktown/current/latest/x86_64/kde
71M     ktown/current/latest/x86_64/kdei
I.e. most of what happened is a shift of the translations from separate source tarballs into the actual program sources.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
digikam 4.14 on -Current hoodlum7 Slackware 2 11-12-2016 07:02 AM
[SOLVED] Slack64-current and Digikam-5.2.0 3rensho Slackware 2 09-26-2016 05:55 AM
Segfault with E17 on Slackware --Current frankbell Slackware 5 03-26-2013 07:19 PM
[SOLVED] -current and Digikam smoooth103 Slackware 28 09-19-2012 04:27 AM
Xterminal + current GTK = segfault crxssi Linux - Software 3 01-28-2006 06:58 PM


All times are GMT -5. The time now is 04:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration