Show solver information not working - still a bug?

In the YaST2 Software Manager when choosing “Show solver information” from the context menu of a package a message is displayed telling that libqdialogsolver is required. I could not find any package with this name for OpenSUSE 13.2. It seems like there has been a bug in the past (https://bugzilla.novell.com/show_bug.cgi?id=785431), but the issue is marked as fixed. Is it still a bug or is a solution available?

Well that lib is brought in as part of another package. Try checking the box “provides” in search but in any case it still does not work. Wonderful tool hate to see it go away. I think there is no one to support it or perhaps move to ruby like the rest of yast.

Well, that looks like a bad habit to me to leave the context menu entry in a production ready software, if it is not going to be fixed soon or even not supported any more.:frowning:

I agree but the module is installed it just doesn’t seem to work

The problem here is that YaST got ported to Qt5, but libqdialogsolver is still using Qt4 (and unfortunately large parts use the Qt3 compatibility stuff that got removed in Qt5).
Porting work started, but hasn’t been completed in time.
Patches are welcome of course… :wink:
https://bugzilla.opensuse.org/show_bug.cgi?id=866622

I don’t know whether the menu option has been left in on purpose or was just forgotten to be removed.
But as it is now, you could just install that package when it is ported and get the functionality back. If the menu entry had been removed, this would not be possible.
So a ported libqtdialogsolver package could easily be released as online update for 13.2 even.

I doubt that.
The package libqdialogsolver1 (which contains that “module”) conflicts with YaST on a package level, so installing it would force you to remove YaST.
And this is done on purpose and for good reasons: it is still using Qt4, loading it into the Qt5 based YaST would cause an immediate crash. To be clear here: just having it installed would make YaST->Software Management crash on startup, not just when you call that function.

PS, regarding the bug report mentioned in the OP: yes, this has been fixed and an update has been released for 12.3 and 13.1 as you can see in the bug report. I myself pushed that update.
But as mentioned, for 13.2 YaST has been ported to Qt5, so the Qt4 based plugin would just crash it and a Qt5 based version is not available yet.

I checked a few days ago the package that is listed the contain the module is installed. Sop Yast Software management thinks it is there any way

And which package in particular are you talking about?

The package libqdialogsolver1 has been dropped in 13.2 (as it crashed YaST), and you cannot install the 13.1 version either because of the dependencies. There’s even an explicit conflict:

wolfi@amiga:~/Desktop> rpm -q --conflicts libyui-qt-pkg6
libqdialogsolver1 < 1.4.0

Note that this only applies to 13.2 (and Tumbleweed). You can install the package in 13.1 and earlier, and it should work fine. It isn’t installed by default though IIRC.

Asking Yast what provides libgtdialogsolve gets back openSUSE-release Which is installed. The lib is not in the file list though but since this is a meta I’d guess one of the packages thinks it is supplying it.

No.
Have you actually looked at the provides? (“Dependencies” tab in YaST)

openSUSE-release only provides “weakremover(libqdialogsolver1-devel)”, which tells zypper to uninstall the package libqdialogsolver1-devel when you do a distribution upgrade to 13.2.

As YaST’s search looks for substrings by default, it finds that package when searching for something that provides libqdialogsolver1.

That is my point to the casual user Yast says the thing is installed but if it is it does not run and gives info that you need to install libgldialogsolve. looking for that package brings up nothing unless you add provides check mark then it shows a package that is installed that says it provides said package but does not really???

You need to think like a user not a programmer :stuck_out_tongue:

Hm? You never tried to make a point.
You just wrote that you have the package installed but it doesn’t work.

But the package is not even included in 13.2.

looking for that package brings up nothing unless you add provides check mark then it shows a package that is installed that says it provides said package but does not really???

That package does not say it provides said package.

Search for “a” and you’ll get a lot of packages as a result. But I think I don’t have to tell you that not all of those packages do provide “a”…
Again, YaST searches for partial strings by default (search mode “Contains”), and that’s probably a good thing (IMHO at least).
Change the search mode to “Exact Match”, and you won’t get any result.

You need to think like a user not a programmer :stuck_out_tongue:

Why?
I just tried to explain to you that you cannot possibly have the package installed, although you said you have…

If you think that the menu option should be removed, then file a bug report. :stuck_out_tongue:
But then that feature will probably be gone forever…

No it just lead you in a circle unless you are aware of the history. If it is not there it should not show up in any search.

Again, file a bug report to remove that menu option if it bothers you. (or port libqdialogsolver1 to Qt5… :p)

And regarding the search, I already explained to you why it “shows up”.
If you search for the package name only (search for provides is deactivated by default anyway) it won’t show up.