Nasty Yast2 message, how to get rid of it?

Every time I start Software Management or Online Update in Yast2, I see this window:
http://abload.de/img/yast2d1um3.png

I choose solution 1 and nothing visually happens.

Okay, I tried zypper on the commandline:

zypper remove application:Firefox-.noarch
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following application is going to be REMOVED:
  Firefox 

No additional space will be used or freed after the operation.
Nothing to do.

How can I get rid of this message?

  1. What version of opensuse are you using?
  2. What are your repos? (Give the output from
# zypper lr -d

and put that output in code blocks.

  1. Where did you get Firefox-.noarch? I am not seeing anything “noarch” that matches “firefox” is a Yast search.?

Either you have an odd version of firefox, or you have been upgrading opensuse since forever and have a firefox component that is left over and not needed.

But I’m guessing. Provide what information you can on the above questions, and maybe this can be solved.

$ cat /etc/issue
Welcome to openSUSE 13.2 "Harlequin" - Kernel \r (\l).

13.2 just (on Thursday) upgraded from 12.3 – yes a maybe unsupported upgrade by skipping 13.1.

$ LANG=C zypper lr -d
# | Alias                    | Name                          | Enabled | Refresh | Priority | Type   | URI                                                          | Service
--+--------------------------+-------------------------------+---------+---------+----------+--------+--------------------------------------------------------------+--------
1 | nvidia                   | nvidia                        | Yes     | Yes     |   98     | rpm-md | ftp://download.nvidia.com/opensuse/13.2/                     |        
2 | packman-13.2             | packman                       | Yes     | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_13.2/                  |        
3 | repo-13.2-non-oss        | openSUSE-13.2 Non-OSS         | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/non-oss/ |        
4 | repo-13.2-oss            | openSUSE-13.2 OSS             | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/13.2/repo/oss/     |        
5 | repo-13.2-update-non-oss | openSUSE-13.2 Updates Non-OSS | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.2-non-oss/            |        
6 | repo-13.2-update-oss     | openSUSE-13.2 Updates OSS     | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.1/                    |

I have no idea where Firefox-.noarch comes from. Before 13.2 I had 12.3 installed, but I never ever installed firefox from any other repository then the equivalent ones from above for 12.3

Then it looks as if that Firefox-.noarch is a left over that is no longer needed.

If it were me, I would uninstall that. Then if there was a problem with firefox, I would do a forced reinstall of firefox.

Okay, I started Yast2, Software update, selected all 3 installed packages containing firefox in the name,

copy from the yast2 window:

  • Downloading MozillaFirefox-branding-openSUSE (download size 45.9 KiB)
  • Downloading MozillaFirefox (download size 36.71 MiB)
  • Downloading MozillaFirefox-translations-common (download size 8.55 MiB)
    Install messages are missing here, since the window vanished to fast :frowning: But reinstallation was done

Opened Software management again, same nasty message :frowning:

However, thanks for trying to help

Start YaST2 Software Management
Navigate to Options and uncheck System Verification Mode.
That will disable the pop up messages.

You must have enabled it as it is disabled by default.

Also, place a checkmark next to Cleanup when deleting packages.
Click on Accept button to exit YaST2.

That helps. Thanks!
BTW: In Online Update I have to uncheck the same menu entry …

However, there is a second issue. On the command line (yes, I love command lines, maybe because I use UNIX since 1987) I see the following message when starting Software management or Online Update:

Unknown config.

and a second line shows up after¹ I click on accept

Invalid snapshot ''.

¹) “after” because it seems that it shows up with a little delay…

I think both are related, did not mention since I hoped both go away with whatever fix.

On 2014-12-28 00:36, Wurgl1 wrote:

> 13.2 just (on Thursday) upgraded from 12.3 – yes a maybe unsupported
> upgrade by skipping 13.1.

How did you upgrade?


> --------------------
>     $ LANG=C zypper lr -d
>   # | Alias                    | Name                          | Enabled | Refresh | Priority | Type   | URI                                                          | Service
>   --+--------------------------+-------------------------------+---------+---------+----------+--------+--------------------------------------------------------------+--------
>   6 | repo-13.2-update-oss     | openSUSE-13.2 Updates OSS     | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/13.1/                    |
> --------------------

Your problem is repo number 6: you were pulling updates from 13.1, thus
the inconsistencies.

I have no idea where Firefox-.noarch comes from. Before 13.2 I had 12.3
installed, but I never ever installed firefox from any other repository
then the equivalent ones from above for 12.3

13.1:


Telcontar:~ # rpm -qa | grep -i firefox
MozillaFirefox-branding-openSUSE-21-2.1.2.x86_64
mhtml-firefox-0.5-21.1.1.noarch
MozillaFirefox-33.0-46.2.x86_64
Telcontar:~ #


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On 2014-12-28 01:56, Wurgl1 wrote:
> I see the following
> message when starting Software management or Online Update:

The are related to btrf snapshots, and happen when root is not btrfs.
ignore them.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Why not uninstall snapper then?

zypper ref
zypper up
zypper ar -n “openSUSE-13.2 OSS” http://download.opensuse.org/distribution/13.2/repo/oss/ repo-13.2-oss
zypper ar -n “openSUSE-13.2 Non-OSS” http://download.opensuse.org/distribution/13.2/repo/non-oss/ repo-13.2-non-oss
zypper ar -f -n “openSUSE-13.2 Updates OSS” http://download.opensuse.org/update/13.2/ repo-13.2-update-oss

in the line above I had that typo. Shame on me :frowning:

zypper ar -f -n “openSUSE-13.2 Updates Non-OSS” http://download.opensuse.org/update/13.2-non-oss/ repo-13.2-update-non-oss
zypper ar -f -n “packman” http://packman.inode.at/suse/openSUSE_13.2/ packman-13.2

and somewhen later, since I had problems with X11 the nVidia stuff

Fixed that 13.1, messages are still here.

@arvidjaar:
Deinstall snapper is not a good idea, it would uninstall grub2 which I am using and I think, I need grub2 since all my disk is RAID1, including the boot partition.

Just changing the repos doesn’t change the installed packages.
Run “sudo zypper dup” to switch your Firefox packages to the 13.2 ones, or do so manually in YaST via the “Versions” tab.

Deinstall snapper is not a good idea, it would uninstall grub2 which I am using and I think, I need grub2 since all my disk is RAID1, including the boot partition.

Hm? I can uninstall snapper perfectly fine here, without having to uninstall grub2.
Can you please post the output of “sudo zypper rm snapper”?

Only snapper-zypp-plugin requires snapper here. OTOH, those YaST/zypper messages probably come from snapper-zypp-plugin anyway, so try to uninstall that.

did zypper dup, could deinstall snapper. Messages on command line are gone.

The message with Firefox-.noarch still exists (but I can that turn of via unchecking system verification checkbox)

You’re right, that bug hasn’t been fixed yet. (it is a packaging error in the Firefox packages)

I just never see that error here, only when I run “zypper ve”. So I thought it is fixed already in the 13.2 update repo.

But it’s just a cosmetical issue. The problem is about the so-called “Appdata”, additional information about the package that is displayed in gnome-software (nothing else uses that yet at the moment AFAIK).

On 2014-12-28 09:06, arvidjaar wrote:
>
> robin_listas;2685490 Wrote:
>>
>> The are related to btrf snapshots, and happen when root is not btrfs.
>> ignore them.
>>
>
> Why not uninstall snapper then?

Yes, that’s a possibility. But it is not such a bother to ignore the
messages, and one never knows if btrfs will be used at some point here,
and then one will not remember to install snapper again.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On 2014-12-28 10:46, Wurgl1 wrote:
>
> robin_listas;2685488 Wrote:
>> On 2014-12-28 00:36, Wurgl1 wrote:
>>
>>> 13.2 just (on Thursday) upgraded from 12.3 – yes a maybe unsupported
>>> upgrade by skipping 13.1.
>>
>> How did you upgrade?

A comment: When pasting here computer commands and such, please use a
CODE BLOCK, so that the forum software doesn’t do silly things like
converting URLS to tiny urls, wrap lines, or otherwise hide or alter the
commands you entered. You get them by clicking on the ‘#’ button in the
forum editor. http://susepaste.org/images/15093674.jpg

I’ll edit your answer for better reading.


> zypper ref
> zypper up
> zypper ar -n "openSUSE-13.2 OSS" http://download.opensuse.org/distribution/13.2/repo/oss/repo-13.2-oss
> zypper ar -n "openSUSE-13.2 Non-OSS" http://download.opensuse.org/distribution/13.2/repo/non-oss/repo-13.2-non-oss
> zypper ar -f -n "openSUSE-13.2 Updates OSS" 'http://download.opensuse.org/update/13.2/'(http://download.opensuse.org/update/13.1/) repo-13.2-update-oss
> # in the line above I had that typo. Shame on me :-(
>
> zypper ar -f -n "openSUSE-13.2 Updates Non-OSS" http://download.opensuse.org/update/13.2-non-oss/repo-13.2-update-non-oss
> zypper ar -f -n "packman" http://packman.inode.at/suse/openSUSE_13.2/packman-13.2

And then I assume you did a zypper dup and perhaps something else,
because a zypper dup from 12.3 to 13.2 is supposed to fail.

> and somewhen later, since I had problems with X11 the nVidia stuff
>
> Fixed that 13.1, messages are still here.

Well, you have to replace all the packages that came from the wrong
repo, and that is not automatic.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Well, you can just as well use btrfs without snapper.
Snapper is only used/needed for creating and managing snapshots.

Uninstalling snapper is in fact one possible way to get rid of the automatically created snapshots…
(you can of course also just disable them in the config)

I had a menu entry “Snapper” in Yast to do whatever with this snapper. When I click on that, It tells me that I have to create some configuration file in a message box and the window vanished. I do not like such a behaviour. If there is a graphical interface, then this interface shall handle the situation just after install/upgrade well.

Those two lines on the command line are totally useless for people starting yast from the KDE-Menu (or any similar way in other Window managers). And it is nasty for for people starting yast from the command line. In addition these messages are confusing, because they do not tell the name of the program creating them. Yast is a magic black box and when fiddling around with installed software packages I expect a lot, but sure not a snapshot of my filesystem.

On 2014-12-28 17:26, Wurgl1 wrote:

> the name of the program creating them. Yast is a magic black box and
> when fiddling around with installed software packages I expect a lot,
> but sure not a snapshot of my filesystem.

It is an intentional feature.

The CLI messages could be more informative, yes, but messages on the CLI
from GUI programs are normally dubug messages intended for advanced
users and programmers, so complaining about them will usually be ignored.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Misunderstanding: The feature could be a good idea, I will not argue against the feature.

But when searching for the reason of that message I would never ever expect a snapshot-tool, I would rather expect some problem with one of the thousand of packages.

The CLI messages could be more informative, yes, but messages on the CLI

Agree!

from GUI programs are normally dubug messages intended for advanced
users and programmers, so complaining about them will usually be ignored.

My opinion: Use Option -d or similar for debugging. Add debug messages into a debug build only.