MX Linux Forum

Posted: **Mon Feb 26, 2018 12:04 pm**

@all:

Just tried to install showfoto 4:5.7.0-1mx17+2, but I can't ("broken packages" problem). showfoto requires kipi-plugins-common, so maybe this issue is linked to the issue noticed in viewtopic.php?f=108&t=44229&p=437043.

Greetings, Joe

Posted: **Mon Feb 26, 2018 12:11 pm**

MX-16_fan wrote:@all:

Just tried to install showfoto 4:5.7.0-1mx17+2, but I can't ("broken packages" problem). showfoto requires kipi-plugins-common, so maybe this issue is linked to the issue noticed in viewtopic.php?f=108&t=44229&p=437043.

Greetings, Joe

my guess is you have something installed from the test repo that is conflicting. All the items you've posted on lately seem to be OK on my travel usb stick. I do have kdenlive installed as well.

So do you have a kde app installed from testrepo?

Posted: **Mon Feb 26, 2018 12:18 pm**

@dolphin_oracle:

dolphin_oracle wrote:(...) So do you have a kde app installed from testrepo?

Yes, Okular, for example, and probably others (I use a couple of KDE applications so frequently I don't even notice them to be KDE any more).

So what do I do?

Greetings, Joe

Posted: **Mon Feb 26, 2018 12:24 pm**

looks to me like several of the mxtest repo kde apps have a depend on the international files that are higher than the version in the standard repo (or at least support files)

So if you have one of those installed, that is likely your overall "kde" app issue.

You may well be able to simply enable the test repo in synaptic and install what you want.

Posted: **Mon Feb 26, 2018 12:26 pm**

@dolphin_oracle:

dolphin_oracle wrote:You may well be able to simply enable the test repo in synaptic and install what you want.

Same as here: viewtopic.php?p=437066#p437066: Already tried that, but there's no higher version of the kde-l10n-de available in the MX Test Repo.

Greetings, Joe

Posted: **Mon Feb 26, 2018 12:29 pm**

can you post output of

Code: Select all

sudo apt-get install kde-l10n-de

Posted: **Mon Feb 26, 2018 12:49 pm**

I think the problem is in the okular package from testrepo, or possibly one of the support files.

I suggest going with the okular from the regular repo.

Posted: **Mon Feb 26, 2018 1:31 pm**

@dolphin_oracle:

dolphin_oracle wrote:can you post output of
Code: Select all
sudo apt-get install kde-l10n-de

There you are:

Code: Select all

Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  kinit libbit-vector-perl libcarp-clan-perl libchm1 libconfig-general-perl libdate-calc-perl
  libexporter-tiny-perl libextutils-depends-perl libextutils-pkgconfig-perl libfilesys-df-perl
  libfont-ttf-perl libgoo-canvas-perl libgoocanvas-common libgoocanvas3 libgps22
  libgtk2-ex-simple-list-perl libgtk2-imageview-perl libgtkimageview0 libimage-magick-perl
  libimage-magick-q16-perl libio-string-perl libkf5activities5 libkf5calendarevents5 libkf5js5
  libkf5jsapi5 libkf5kexiv2-15.0.0 libkf5khtml-data libkf5khtml5 libkf5plasma5 libkf5plasmaquick5
  libkf5pty-data libkf5pty5 libkf5threadweaver5 liblist-moreutils-perl liblog-log4perl-perl
  libokular5core7 libossp-uuid-perl libossp-uuid16 libpdf-api2-perl libproc-processtable-perl
  libqca-qt5-2 libqmobipocket2 libqt5multimediawidgets5 libqt5positioning5 libqt5serialport5
  libreadonly-perl libsane-perl libset-intspan-perl libshp2 libtiff-tools libtry-tiny-perl
  libvisio-0.1-1 libvlccore8 libxcb-damage0 pkg-config plasma-framework
  qml-module-org-kde-kirigami qml-module-org-kde-kquickcontrols
  qml-module-org-kde-kquickcontrolsaddons qml-module-qt-labs-folderlistmodel
  qml-module-qtgraphicaleffects qml-module-qtquick-controls qml-module-qtquick-layouts
  qml-module-qtquick-window2 qml-module-qtquick2
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Vorgeschlagene Pakete:
  kde-standard
Die folgenden Pakete werden ENTFERNT:
  libastro1 libmarblewidget-qt5-28 marble marble-data marble-plugins marble-qt marble-qt-data
  okular okular-extra-backends
Die folgenden NEUEN Pakete werden installiert:
  kde-l10n-de
0 aktualisiert, 1 neu installiert, 9 zu entfernen und 29 nicht aktualisiert.
Es müssen 37,8 MB an Archiven heruntergeladen werden.
Nach dieser Operation werden 35,9 MB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n]

Greetings, Joe

Posted: **Thu Mar 01, 2018 12:09 pm**

UPDATE:

Here's what I get when I try to install showfoto from the command line:

Code: Select all

$ sudo apt-get install showfoto
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:$ sudo apt-get install showfoto
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 showfoto : Depends: digikam-private-libs (= 4:5.7.0-1mx17+2) but it is not going to be installed
            Depends: kipi-plugins (= 4:5.7.0-1mx17+2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
 showfoto : Depends: digikam-private-libs (= 4:5.7.0-1mx17+2) but it is not going to be installed
            Depends: kipi-plugins (= 4:5.7.0-1mx17+2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

@Stevo: Is this of any help to resolve this?

Greetings, Joe

Posted: **Thu Mar 01, 2018 2:07 pm**

Showfoto is part of the Digikam set of packages, so you should be trying to install the test repo version to match the test repo Digikam.

Posted: **Thu Mar 01, 2018 2:12 pm**

@Stevo:

Stevo wrote:Showfoto is part of the Digikam set of packages, so you should be trying to install the test repo version to match the test repo Digikam.

1) You mean I can't install showfoto without installing digikam?

2) Can't install the Test Repo digikam either because that also gives me warning. Can you reproduce that?

Greetings, Joe

Posted: **Thu Mar 01, 2018 4:48 pm**

No, I just installed showfoto, digikam, and okular from the test repo without a hitch. Showfoto doesn't need digikam itself, but it uses some packages and libraries that come from the same build, such as kipi-plugins. I can see you already have those installed, which is why you can't install the stock Stretch version with

Code: Select all

apt install showfoto

with the test repo disabled.

Posted: **Fri Mar 02, 2018 5:15 am**

@Stevo:

Stevo wrote:No, I just installed showfoto, digikam, and okular from the test repo without a hitch. Showfoto doesn't need digikam itself, but it uses some packages and libraries that come from the same build, such as kipi-plugins. I can see you already have those installed, which is why you can't install the stock Stretch version with
Code: Select all
apt install showfoto
with the test repo disabled.

Sorry, I don't get what you mean. I always tried to install everything from the MX Test Repo.

What can I do to debug this?

Greetings, Joe

Posted: **Fri Mar 02, 2018 11:47 am**

@Stevo:

UPDATE: Just discovered that Synaptic provides some interesting "properties" information for each package, and there Synaptic precisely tells me that kipi-plugins-common as would be needed for showfoto is "damaged".

Greetings, Joe

Posted: **Fri Mar 02, 2018 1:26 pm**

MX-16_fan wrote:@Stevo:

UPDATE: Just discovered that Synaptic provides some interesting "properties" information for each package, and there Synaptic precisely tells me that kipi-plugins-common as would be needed for showfoto is "damaged".

Greetings, Joe

Hmmm...I believe in English it calls that a broken package...the result of

Code: Select all

apt policy kipi-plugins-commons

?

Posted: **Fri Mar 02, 2018 1:51 pm**

OK, I found the problem. Digikam (thus kipi-plugins) depends on a library from Marble that's specific to the version, so the stock Stretch version of that is libmarblewidget-qt5-25, but the version in the test repo is libmarblewidget-qt5-28. So basically, you currently can't have both the test repo Marble and Digikam installed at the same time. This was a decision I made when I built them each in isolated "vanilla" Stretch pbuilders, but I can also rebuild Digikam against the test repo Marble. That will just force users to also upgrade Marble at the same time, which I was trying to stay away from, but I think that is appropriate in this one case.

Using pbuilder is pretty neat, I can hook and unhook any repos to it at will in about 30 seconds, including one in a folder on my machine, so in this case I'll just hook the test repo to Stretch so it builds against the newer Marble. VLC 3.0.1 also needs a couple libraries in our test repo, so I was going to do that anyway for that build.

Edit: BTW, the way to track down an issue like this with something like kipi-plugins-common is to try and install it on the command line. If it says it can't install because of a problem with some other package, then you try and install that other package on the CLI. Repeat the procedure until you get down to the package that is causing the root issue.

Posted: **Fri Mar 02, 2018 2:55 pm**

@Stevo:

Stevo wrote:(...) ...the result of
Code: Select all
apt policy kipi-plugins-commons
?

Code: Select all

$ apt policy kipi-plugins-commons
N: Unable to locate package kipi-plugins-commons

(with kipi-plugins-common not installed right now.)

Greetings, Joe

Posted: **Fri Mar 02, 2018 3:04 pm**

@Stevo:

Stevo wrote:OK, I found the problem.

Cool!

Stevo wrote:Digikam (thus kipi-plugins) depends on a library from Marble that's specific to the version, so the stock Stretch version of that is libmarblewidget-qt5-25, but the version in the test repo is libmarblewidget-qt5-28. So basically, you currently can't have both the test repo Marble and Digikam installed at the same time. This was a decision I made when I built them each in isolated "vanilla" Stretch pbuilders, but I can also rebuild Digikam against the test repo Marble. That will just force users to also upgrade Marble at the same time, which I was trying to stay away from, but I think that is appropriate in this one case.

Trying to understand that. Why can't different libmarblewidget-qt5 versions simply coexist on one system?

Stevo wrote:Edit: BTW, the way to track down an issue like this with something like kipi-plugins-common is to try and install it on the command line. If it says it can't install because of a problem with sofor youme other package, then you try and install that other package on the CLI. Repeat the procedure until you get down to the package that is causing the root issue.

I understand. Thanks for the hint.

1) So I'll uninstall Marble and install both the new showfoto and the new Marble from the MX Test Repo tomorrow. Correct?

2) As far as I remember, installing showfoto does not necessarily require installing digikam. Has digikam now become a showfoto dependency?

Greetings, wishing you a nice weekend, Joe

Posted: **Sat Mar 03, 2018 10:13 am**

@Stevo:

UPDATE: Your new showfoto 4:5.7.0-1mx17+3 installed o.k. (same goes for the new Marble), but it doesn't start:

Code: Select all

$ showfoto -qwindowtitle %c %U

(showfoto:4828): GLib-GObject-WARNING **: cannot register existing type 'GtkWidget'

(showfoto:4828): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(showfoto:4828): GLib-GObject-WARNING **: cannot register existing type 'GtkBuildable'

(showfoto:4828): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed

(showfoto:4828): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(showfoto:4828): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(showfoto:4828): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

Some problem with the graphics library?

Greetings, Joe

Posted: **Sat Mar 03, 2018 2:07 pm**

Since Showfoto is part of the Digikam project, it only makes sense that it uses some of the Digikam runtime framework. It does not require Digikam itself.

It runs OK on my working system, but I have my Qt apps decoupled from the GTK themes and use the Kvantum Qt themes instead. Like all KDE apps, it uses the Qt framework. I don't get any of those glib errors at all, but I'll have to test this on a generic install.

Posted: **Sat Mar 03, 2018 2:24 pm**

Confirmed. Does the same thing here. Definitely a theming issue, since it will start up with:

Code: Select all

QT_QPA_PLATFORMTHEME=gtk3 showfoto

or

Code: Select all

QT_QPA_PLATFORMTHEME=qt5 showfoto

or

Code: Select all

QT_QPA_PLATFORMTHEME=qt4 showfoto

Posted: **Sat Mar 03, 2018 2:31 pm**

@Stevo:

Stevo wrote:(...) I don't get any of those glib errors at all, but I'll have to test this on a generic install.

Thanks! Greetings, Joe

Posted: **Sat Mar 03, 2018 3:15 pm**

Confirmed on a generic install, and that Tim's fixes work. You could edit the menu entry to add one of those lines before the "showfoto".

Posted: **Sun Mar 04, 2018 7:55 am**

@Stevo:

Stevo wrote:Confirmed on a generic install, and that Tim's fixes work. (...)

Is it possible to implement the fix in a new version of the package? Greetings, and a nice Sunday, Joe

Posted: **Sun Mar 04, 2018 4:24 pm**

MX-16_fan wrote:@Stevo:

Stevo wrote:Confirmed on a generic install, and that Tim's fixes work. (...)
Is it possible to implement the fix in a new version of the package? Greetings, and a nice Sunday, Joe

Well, I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.

Posted: **Mon Mar 19, 2018 9:55 pm**

@Stevo:

Stevo wrote:(...) I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.

Just noticed that (unsurprisingly) this issue prevails in MX-17.1.

Trying to understand the nature of this problem. Why didn't it occur in MX-16?

Greetings, and thanks in advance for your answer, Joe

Posted: **Mon Mar 19, 2018 9:57 pm**

MX-16_fan wrote:@Stevo:

Stevo wrote:(...) I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.
Just noticed that (unsurprisingly) this issue prevails in MX-17.1.

Trying to understand the nature of this problem. Why didn't it occur in MX-16?

Greetings, and thanks in advance for your answer, Joe

Different qt and gtk versions. There were some.fairly major changes in both.

Posted: **Mon Mar 19, 2018 10:00 pm**

@dolphin_oracle:

dolphin_oracle wrote:
MX-16_fan wrote:@Stevo:

Stevo wrote:(...) I could modify the desktop launcher file to include one of those settings, but no matter what one of those I picked, it would cause problems on other desktops or themes.
Just noticed that (unsurprisingly) this issue prevails in MX-17.1.

Trying to understand the nature of this problem. Why didn't it occur in MX-16?

Greetings, and thanks in advance for your answer, Joe
Different qt and gtk versions. There were some.fairly major changes in both.

I see. And why is this dependent on the theme? Greetings, Joe

Posted: **Mon Mar 19, 2018 10:30 pm**

because the way the themes are applied varies by qt version, and what gtk/qt version the theme is written to.

under jessie, qt could be set to follow the gtk themes and it generally worked ok. In stretch, you can do something similar, but there are occasions when it doesn't work as well as before.

if you want, you can override the default qt theming in mx by modifing (or even deleting) /etc/X11/Xsession.d/98qtconfig , then loggin in/out.

Posted: **Tue Mar 20, 2018 12:21 pm**

@Stevo,
@timkb4cq:

dolphin_oracle wrote:because the way the themes are applied varies by qt version, and what gtk/qt version the theme is written to.

under jessie, qt could be set to follow the gtk themes and it generally worked ok. In stretch, you can do something similar, but there are occasions when it doesn't work as well as before.

So is this a "WON'T FIX" case then? Greetings, Joe

Posted: **Tue Mar 20, 2018 12:27 pm**

The packages aren't broke.

You can modify how we deal with qt theming in the /etc/X11/Xsession.d/98qtconfig file.

Posted: **Tue Mar 20, 2018 12:32 pm**

@dolphin_oracle:

dolphin_oracle wrote:The packages aren't broke.

You can modify how we deal with qt theming in the /etc/X11/Xsession.d/98qtconfig file.

Does that mean losing your carefully designed theming defaults? Greetings, Joe

Posted: **Tue Mar 20, 2018 12:39 pm**

MX-16_fan wrote:@dolphin_oracle:

dolphin_oracle wrote:The packages aren't broke.

You can modify how we deal with qt theming in the /etc/X11/Xsession.d/98qtconfig file.
Does that mean losing your carefully designed theming defaults? Greetings, Joe

Just for the Qt apps. That file does covery things systemwide.

Posted: **Tue Mar 20, 2018 12:48 pm**

@dolphin_oracle:

dolphin_oracle wrote:
MX-16_fan wrote:@dolphin_oracle:

dolphin_oracle wrote:The packages aren't broke.

You can modify how we deal with qt theming in the /etc/X11/Xsession.d/98qtconfig file.
Does that mean losing your carefully designed theming defaults? Greetings, Joe
Just for the Qt apps. That file does covery things systemwide.

Not nice. There's no other way whatsoever? Greetings, Joe

Posted: **Tue Mar 20, 2018 1:10 pm**

MX-16_fan wrote:@dolphin_oracle:

dolphin_oracle wrote:
MX-16_fan wrote:@dolphin_oracle:

Does that mean losing your carefully designed theming defaults? Greetings, Joe
Just for the Qt apps. That file does covery things systemwide.
Not nice. There's no other way whatsoever? Greetings, Joe

you can add the parameter tim suggested to just the desktop file for show photo. then only that app is different.

And yes, that's the current state of themeing between qt and gtk.

here's some info from the arch wiki. https://wiki.archlinux.org/index.php/qt ... KDE_Plasma

Posted: **Tue Mar 20, 2018 1:56 pm**

@dolphin_oracle:

dolphin_oracle wrote:
MX-16_fan wrote:@dolphin_oracle:

dolphin_oracle wrote:
Just for the Qt apps. That file does covery things systemwide.
Not nice. There's no other way whatsoever? Greetings, Joe
you can add the parameter tim suggested to just the desktop file for show photo. then only that app is different.

And yes, that's the current state of themeing between qt and gtk.

here's some info from the arch wiki. https://wiki.archlinux.org/index.php/qt ... KDE_Plasma

Thanks. So I'll mark this "SOLVED", as the package does indeed install, while the issue of it not running is another one.

Hopefully someone will fork showfoto and increase the compatibility of the fork.

Greetings, Joe

Posted: **Sat Sep 21, 2019 11:33 am**

Stevo wrote: Sat Mar 03, 2018 3:15 pm Confirmed on a generic install, and that Tim's fixes work. You could edit the menu entry to add one of those lines before the "showfoto".

Sorry Stevo, because is a thread of times ago ( today I tried to run ShowFoto...) and I made a search on forum.

You mean.....

QT_QPA_PLATFORMTHEME=gtk3 before showfoto -qwindowtitle %c %U in the command edit box ?

This gives me the follow error:

I can run ShowFoto from Terminal using this command

QT_QPA_PLATFORMTHEME=gtk3 showfoto

but I am not able to make a launcher for it.

Seems that producing
a bash file (saving as showFoto.sh or whatever name.sh )

Code: Select all

#!/bin/bash
QT_QPA_PLATFORMTHEME=gtk3 showfoto

and executing as bash showFoto.sh or sh showFoto.sh or simply changing permissions of this batch as executable makes the job.

MX Linux Forum

[SOLVED] MX-17: Can't install showfoto - dependencies' problem

[SOLVED] MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem

Re: MX-17: Can't install showfoto - dependencies' problem