Help finding a reposotory that stops package kit fromupdateing

The error we get on my wife’s laptop is ‘malfunctioning repo opensuse leap 15.1 repo’ not identified.
It does not say which Leap 15.1 repo!

Problem is I can’t find any reference to Leap 15.1 in the repo list in YaST.
Just the standard opensuse things, packman, google, and saurland’s repo for the WiFi dongle in her machine

Where do I start looking for any reference left on my wife’s laptop relating Leap 15.1?

Hi Bill. I assume that you know that openSUSE 15.1 is now EOL…
https://en.opensuse.org/Lifetime

However, the repos should still be present. Can you share the following output please?

zypper lr -d

Yes i can. Tomorrow when I can use her machine.

It is odd, this started in just the past few days(maybe a week or so). Up to then package kit had no problems on her laptop.
And yes, I know 15.1 is EOL, but we updated all our machines to 15.2 when it became available.(15.3 when?)
That is why I am surprised there is a failure message for a Leap 15.1 repo.

BTW, I finally got the YaST Online Updates to open without error, and did the Security and Recommended updates(why are these not 2 separate categories?)
Package Kit functioned w/o error. We’ll see what happens tomorrow.

Thanks for the update Bill. Good to know PackageKit is functioning as expected now. (I never use it.)

Here it is for what it is worth. THe line in BOLD does not show up in YaST. (scratching head now!!)

zypper lr -d
#  | Alias                     | Name                               | Enabled | GPG Check | Refresh | Priority | Type   | URI           
                                                                                  | Service
---+---------------------------+------------------------------------+---------+-----------+---------+----------+--------+---------------
----------------------------------------------------------------------------------+--------
 1 | Google-Chrome             | Google-Chrome                      | No      | ----      | ----    |   99     | rpm-md | http://dl.goog
le.com/linux/chrome/rpm/stable/x86_64                                             |  
 **2 | openSUSE_Leap_15.1_Update | WiFi-dongle**                        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://downlo
ad.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Leap_15.2_Update/ |  
 3 | opensuse-guide.org-repo   | Libdvdcss Repository               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://opensus
e-guide.org/repo/openSUSE_Leap_15.2/                                              |  
 4 | packman-rwth              | packman-rwth                       | Yes     | (r ) Yes  | Yes     |   20     | rpm-md | https://ftp.ha
lifax.rwth-aachen.de/packman/suse/openSUSE_Leap_15.2/                             |  
 5 | packman.inode.at-suse     | Packman Repository                 | No      | ----      | ----    |   99     | rpm-md | http://packman
.inode.at/suse/openSUSE_Leap_15.2/                                                |  
 6 | repo-debug                | Debug Repository                   | No      | ----      | ----    |   99     | NONE   | http://downloa
d.opensuse.org/debug/distribution/leap/15.2/repo/oss/                             |  
 7 | repo-debug-non-oss        | Debug Repository (Non-OSS)         | No      | ----      | ----    |   99     | NONE   | http://downloa
d.opensuse.org/debug/distribution/leap/15.2/repo/non-oss/                         |  
 8 | repo-debug-update         | Update Repository (Debug)          | No      | ----      | ----    |   99     | NONE   | http://downloa
d.opensuse.org/debug/update/leap/15.2/oss/                                        |  
 9 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No      | ----      | ----    |   99     | NONE   | http://downloa
d.opensuse.org/debug/update/leap/15.2/non-oss/                                    |  
10 | repo-non-oss              | Non-OSS Repository                 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://downloa
d.opensuse.org/distribution/leap/15.2/repo/non-oss/                               |  
11 | repo-oss                  | Main Repository                    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://downloa
d.opensuse.org/distribution/leap/15.2/repo/oss/                                   |  
12 | repo-source               | Source Repository                  | No      | ----      | ----    |   99     | NONE   | http://downloa
d.opensuse.org/source/distribution/leap/15.2/repo/oss/                            |  
13 | repo-source-non-oss       | Source Repository (Non-OSS)        | No      | ----      | ----    |   99     | NONE   | http://downloa
d.opensuse.org/source/distribution/leap/15.2/repo/non-oss/                        |  
14 | repo-update               | Main Update Repository             | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://downloa
d.opensuse.org/update/leap/15.2/oss/                                              |  
15 | repo-update-non-oss       | Update Repository (Non-Oss)        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://downloa
d.opensuse.org/update/leap/15.2/non-oss/    

Ok, you’ve confused me. You mentioned openSUSE Leap 15.1 in your opening post, but your repos are for an openSUSE Leap 15.2 environment.

And 15.2 is in the prefix of the thread title. :question:

Look at the zipper output again. There is a line that I put in bold that states Leap 15.1 update and is part of the WiFi dongle repo.

Here is a repeat of that line:

**2 | openSUSE_Leap_15.1_Update | WiFi-dongle                        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://downlo
****ad.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Leap_15.2_Update/ |**

This repo only shows as 15.2 when I go to YaST and list out the repositories.

My wife’s machine IS running Leap15.2, has been since a week after 15.2 was released.

But the ‘error’ that kept coming up in package kit said ‘cannot connect to Leap 15.1 update’, or something like that.

@hcvv 15.2 shows up in the title thread BECAUSE her machine is now & has been running 15.2!

PS, I may have to look at Sauerlands repos to see if he has an update to the WiFi dongle repository.

Just for kicks, here is an image of the repo’s on my wife’s laptop as a screen shot form the YaST repository output https://susepaste.org/31027225 .

NOTE>>> The 15.1 update line is not in the YaST repo output.
Why the reference to 15.1 update shows up in the zypper command on a 15.2 machine is beyond me.
I thought zypper and YaST were one and the same but graphic versus CLI?

Don’t worry about GUI deficiencies. What really matters is the URL:

**3400G:~ #** zypper lr -uEP 
#  | Alias                            | Name                                         | Enabled | GPG Check | Refresh | Priority | URI 
---+----------------------------------+----------------------------------------------+---------+-----------+---------+----------+------------------------------------------------------------------------ 
20 | packman                          | packman                                      | Yes     | (r ) Yes  | Yes     |   90     | http://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/ 
 7 | download.opensuse.org-non-oss    | Haupt-Repository (NON-OSS)                   | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/tumbleweed/repo/non-oss/ 
 8 | download.opensuse.org-oss        | Haupt-Repository (OSS)                       | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/tumbleweed/repo/oss/ 
 9 | download.opensuse.org-tumbleweed | Hauptaktualisierungs-Repository              | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/tumbleweed/ 
11 | google-chrome                    | google-chrome                                | Yes     | (r ) Yes  | Yes     |   99     | http://dl.google.com/linux/chrome/rpm/stable/x86_64 
17 | mozilla                          | Mozilla based projects (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | Yes     |   99     | https://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ 
 2 | BellSoft                         | BellSoft Repository                          | Yes     | (r ) Yes  | Yes     |  100     | https://yum.bell-sw.com/ 
15 | jalbum                           | jalbum                                       | Yes     | (  ) No   | Yes     |  100     | http://jalbum.net/download/software/yumrepo/ 
**3400G:~ #**

Alias and Name are helpful, but they don’t matter.

That string “15.1” is part of the Alias. The alias is only a short, comprehensive, not confusing, easy to use in commands, identification of a repository definition. Basically it does not matter what it is, it could be “blabla15.1or151.2oreverything” if you wanted that. But I admit that my idea of a short, comprehensive, not confusing, easy to use in commands, identification is different.

BTW, the Name of the repo is also not very revealing, at least to me.

Just rename it to match reality.

But the ‘error’ that kept coming up in package kit said ‘cannot connect to Leap 15.1 update’, or something like that.

Not sure why that is, although I don’t use PackageKit at all. Perhaps a bug report is required.

My, rather blunt I admit, advice would be to remove PackageKit as all. But it could be that you have a reason that you want to use it.

Uh, yeah, I really don’t want to give my wife root access. She is purely a computer novice & and prone to hitting wrong keys, etc.
Same for CLI zypper commands.
It is just easier on her machine to let package kit do the updates(when it works! and that is not often!)

She gets a lot of failures to update in package kit, and it doesn’t help when a strange message in package kit pop ups up that it FAILED to reach a Leap 15.1 repo WHEN THERE ARE NOT 15.1 REPOS ON HER MACHINE!
The only thing I can find relating to 15.1 is that line I referenced in the zipper output @deano ferrari asked for.

I have submitted new keys, after that my Laptop had also Problems with my repo and packagekit, so I have updated once with zypper to get the new key.
Now packagekit is working as before.

So the problem should be solved.

From whatever side you look at it, the system manager (probably you in that role and being the only one knowing the root password) must be the only one to do the updates (and whatever other tasks a system manager has to do on a system). The fact that PackageKit allows a normal user to do do updates is a severe break of security in my strong opinion.

Applying updates always requires some checking on what they are. E.g., it would be stupid to do a kernel update that requires a reboot asap at the moment that some real important work is done on a system. But apart from a kernel, even an update of Firefox could confront someone who has a lot of open FF windows/tabs with the result that all FF has to be stopped and started again. Wrong timing.

I have made out a maintenance window with my wife. Once a week at a moment she most of the time isn’t using her system. An SSH connection even makes it possible to do most of what is needed (YaST in NCurses, all of the command line) from my own system. but that is not really needed when the system is just in another room. It is the same sort of maintenance window you require from her during house cleaning: honey, please leave your working place every Saturday morning at 10:00, because then I hop in with cleaning utensils (the actual roles may differ at your’s, but the example still holds true).

Do her a favor and maintain her system. And stop offering her that nerving update applet, she should have nothing to do with it and thus should not see it at all.

As said earlier: my strong opinion. And IIRC I have posted likewise in another thread. Maybe I should copy this somewhere in a file to make it easy to post it again when need to be pedantic arises. rotfl!