|
Bugzilla – Full Text Bug Listing |
| Summary: | yast software manager , wine provider key , i must trust very often | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Episteme PROMENEUR <epistemepromeneur> |
| Component: | libzypp | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | dimstar, epistemepromeneur, forgotten_sM9JzehKpy |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast log
whole yast2 folder list of packages containing "gpg" word |
||
|
Description
Episteme PROMENEUR
2014-12-20 06:37:08 UTC
To see what is happening in YaST with the key and the repo we would need the YaST logs. Please attach. https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Attachments_-_y2logs.2C_hwinfo_etc. Created attachment 618106 [details]
yast log
Created attachment 618107 [details]
whole yast2 folder
I've looked through the YaST logs. I can see how YaST adds the key to the zypp Keyring and imports it every few days. 2014-12-20: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-16: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-17: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-18: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-19: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-13: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-13: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-12: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-11: User wants to trust key 8E5578B7233AB63D Emulators OBS Project But I see nothing removing or disabling it. I can be wrong, but my theory is that another software (and not YaST) is actually removing the key in the meantime. Since the main suspect would be the KDE systray application, I'm reassigning the bug to KDE workspace. Episteme, you did not by accident happen to update GPG to version 2.1? Created attachment 619981 [details]
list of packages containing "gpg" word
another hypothesis one on the file participating to the process is corrupted . is there any tool to sanitize , to recovery the software manger security data ? here is pk backend zyyp log it's not about wine repo but geo repo and it is the same pb .ee some error messages .
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] RepoFileReader.cc(repositories_in_stream):100 - priority : 99
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] RepoFileReader.cc(repositories_in_stream):100 - gpgcheck : 1
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] RepoFileReader.cc(repositories_in_stream):100 - keeppackages: 0
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] RepoFileReader.cc(repositories_in_stream):100
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] PathInfo.cc(dirForEach):563 readdir /var/cache/zypp/raw
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] PathInfo.cc(recursive_rmdir):430 recursive_rmdir /var/cache/zypp/raw/Application:GeoT5eZUp
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] PathInfo.cc(dirForEach):563 readdir /var/cache/zypp/solv
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] PathInfo.cc(dirForEach):563 readdir /var/cache/zypp/packages
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] RepoManager.cc(init_knownRepositories):674 end construct known repos
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] PathInfo.cc(unlink):666 unlink /var/tmp/zypp.BDcDeY/pubkey-CC7F07489591C39B-1yU3hG
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.BDcDeY/pubkey-CC7F07489591C39B-1yU3hG{- 0600 0/0 size 1012}
2015-09-18 06:50:47 <5> linux-b4lz.site(4912) [zypp] Exception.cc(log):137 Fetcher.cc(validate):419 THROW: Unknown error while validating /repodata/repomd.xml
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [Progress++] ProgressData.cc(report):86 {#38|}END
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp++] MediaSetAccess.cc(release):434 Releasing all media IDs held by this MediaSetAccess
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp++] MediaManager.cc(release):486 release(id=4)
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp++] MediaHandler.cc(release):734 Request to release attached media http<http://download.opensuse.org/repositories/Application:/Geo/openSUSE_13.1/>, use count=1
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp++] MediaHandler.cc(release):741 Releasing media http<http://download.opensuse.org/repositories/Application:/Geo/openSUSE_13.1/>
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] MediaHandler.cc(disconnect):713 Disconnected: http://download.opensuse.org/repositories/Application:/Geo/openSUSE_13.1/ attached; localRoot "/var/adm/mount/AP_0xQLIl0F"
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp++] MediaHandler.cc(removeAttachPoint):179 MediaHandler - checking if to remove attach point
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] PathInfo.cc(recursive_rmdir):430 recursive_rmdir /var/adm/mount/AP_0xQLIl0F
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] MediaHandler.cc(removeAttachPoint):191 Deleted default attach point /var/adm/mount/AP_0xQLIl0F
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] MediaHandler.cc(release):795 Released: http://download.opensuse.org/repositories/Application:/Geo/openSUSE_13.1/ not attached; localRoot ""
2015-09-18 06:50:47 <5> linux-b4lz.site(4912) [zypp] Exception.cc(log):137 RepoManager.cc(refreshMetadata):1045 CAUGHT: Unknown error while validating /repodata/repomd.xml
2015-09-18 06:50:47 <3> linux-b4lz.site(4912) [zypp] RepoManager.cc(refreshMetadata):1046 Trying another url...
2015-09-18 06:50:47 <3> linux-b4lz.site(4912) [zypp] RepoManager.cc(refreshMetadata):1055 No more urls...
2015-09-18 06:50:47 <5> linux-b4lz.site(4912) [zypp] Exception.cc(log):137 RepoManager.cc(refreshMetadata):1056 THROW: [|] Valid metadata not found at specified URL
2015-09-18 06:50:47 <5> linux-b4lz.site(4912) [zypp] Exception.cc(log):137 History:
2015-09-18 06:50:47 <5> linux-b4lz.site(4912) [zypp] Exception.cc(log):137 - Unknown error while validating /repodata/repomd.xml
2015-09-18 06:50:47 <5> linux-b4lz.site(4912) [zypp] Exception.cc(log):137
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] TargetImpl.cc(buildCache):797 Read cookie: /var/cache/zypp/solv/@System/cookie{- 0644 0/0 size 53}
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] TargetImpl.cc(buildCache):804 Read cookie: /var/cache/zypp/solv/@System/cookie says: uptodate
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] TargetImpl.cc(load):938 New cache built: false, force loading: true
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] TargetImpl.cc(load):944 adding /var/cache/zypp/solv/@System/solv to pool(@System)
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp::satpool] PoolImpl.cc(setDirty):215 _createRepo @System
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp::satpool] PoolImpl.cc(setDirty):215 setRepoInfo @System
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] Repository.cc(setInfo):216 sat::repo(@System){prio -99.0, size 0}
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp] TargetImpl.cc(load):968 adding /var/cache/zypp/solv/@System/solv to system
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [zypp::satpool] PoolImpl.cc(setDirty):215 _addSolv @System
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [libsolv++] PoolImpl.cc(logSat):99 repo_add_solv took 500 ms
2015-09-18 06:50:47 <1> linux-b4lz.site(4912) [libsolv++] PoolImpl.cc(logSat):99 repo size: 2653 solvables
The KDE Systray utility Apper is nothing more than just a frontend for PackageKit. So Apper can not be the faulty party here as that is just represents whatever PackageKit comes up with. However it can be easily tested by removing Apper. This is not an essential part of the KDE Desktop. @Episteme, could you remove the apper package and see if you still have the issue in a coupld of days. We have to keep in mind though that once Apper is removed, most likely PackageKit will not be started anymore either. However if the issue is no longer there, then it must be PackageKit that does something wrong for several days i already uninstalled "apper" . result : same pb sometime it is with Wine repo , sometime with Geo , sometime with Nvidia . then it is not packagekit . is it yast or zypper ? when apper is uninstalled and i use yast software online update there is a second pb : yast does not take care of many updates only a few ones . i must install again apper and apper takes care of all updates . As per above comment. Problem persist even on zypp/yast usage only. According to the log there've been 9 keys in the rpm-db; one was successfully added: > 2014-12-20 07:01:25 <1> linux-b4lz.site(6719) [liby2] genericfrontend.cc(main):575 Launched YaST2 component 'y2base' 'sw_single' 'qt' > ... > Found keys: { > [43387D4AA76AD8A1-53b54be4] [hardware OBS Project <hardware@build.opensuse.org>] [10B872E96E2184DCE4B18C1D43387D4AA76AD8A1] [TTL 630] > [E9CDFDD40AE6233B-53ba5c52] [home:rusjako OBS Project <home:rusjako@build.opensuse.org>] [8EE7330F326DA01265B1BAE8E9CDFDD40AE6233B] [TTL 634] > [45A1D0671ABD1AFB-54176598] [PackMan Project (signing key) <packman@links2linux.de>] [F8875B880D518B6B8C530D1345A1D0671ABD1AFB] [TTL 3554] > [B88B2FD43DBDC284-53674dd4] [openSUSE Project Signing Key <opensuse@opensuse.org>] [22C07BA534178CD02EFE22AAB88B2FD43DBDC284] [TTL 3421] > [27C070176F88BB2F-54032bd3] [KDE OBS Project <KDE@build.opensuse.org>] [4E8E6DE2961F3083EAC5008627C070176F88BB2F] [TTL 689] > [A040830F7FAC5991-4615767f] [Google, Inc. Linux Package Signing Key <linux-packages-keymaster@google.com>] [4CCA1EAF950CEE4AB83976DCA040830F7FAC5991] [TTL 2147483647] > [026B47F3766DA614-50755b61] [mozilla OBS Project <mozilla@build.opensuse.org>] [AAA531905D829BDCBE4D5169026B47F3766DA614] [TTL -1] > [CC7F07489591C39B-51971adb] [Application:Geo OBS Project <Application:Geo@build.opensuse.org>] [195E211106BC205D2A9C2222CC7F07489591C39B] [TTL 219] > [7CD94DEB9056621D-50f6ef88] [utilities OBS Project <utilities@build.opensuse.org>] [8B0079638DF609E2FD8B8CCE7CD94DEB9056621D] [TTL 97] > } > ... > User wants to trust key 8E5578B7233AB63D Emulators OBS Project <Emulators@build.opensuse.org> > User wants to import key 8E5578B7233AB63D Emulators OBS Project <Emulators@build.opensuse.org> > ... > Key [8E5578B7233AB63D-5486e781] [Emulators OBS Project <Emulators@build.opensuse.org>] [09E258099B678BCA07F848C58E5578B7233AB63D] [TTL 789] will be imported into the rpm trusted keyring. > Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '--import' '--' '/var/tmp/zypp.URUfkA/pubkey-8E5578B7233AB63D-iuI8Hy' > pid 6769 launched > Pid 6769 successfully completed > Key [8E5578B7233AB63D-5486e781] [Emulators OBS Project <Emulators@build.opensuse.org>] [09E258099B678BCA07F848C58E5578B7233AB63D] [TTL 789] imported in rpm trusted keyring. Two minutes later the next yast instance finds again just 9 keys in the rpm-db: > 2014-12-20 07:03:47 <1> linux-b4lz.site(7108) [liby2] genericfrontend.cc(main):575 Launched YaST2 component 'y2base' 'sw_single' 'qt' > ... > gpg-pubkey-0ae6233b-53ba5c52 R_ > gpg-pubkey-1abd1afb-54176598 R_ > gpg-pubkey-3dbdc284-53674dd4 R_ > gpg-pubkey-6f88bb2f-54032bd3 R_ > gpg-pubkey-766da614-50755b61 R_ > gpg-pubkey-7fac5991-4615767f R_ > gpg-pubkey-9056621d-50f6ef88 R_ > gpg-pubkey-9591c39b-51971adb R_ > gpg-pubkey-a76ad8a1-53b54be4 R_ > Rpm keys to export into zypp trusted keyring: 9 > Zypp trusted keys to import into rpm database: 0 > Exporting rpm keyring into zypp trusted keyring I doubt that someone removes the key that fast, looks more like a broken rpm-db to me. @Episteme PROMENEUR: You should run (as root) > # rpm --rebuilddb to make sure the rmp database is sane. After this the added key should either have become become visible or can be added without getting lost again. > # zypper ref -f download.opensuse.org-Wine This should now either succeed, or ask whether you want to trust the key. If you say 'a - trust always', the key should be added. If you repeat the command, refresh should not ask again for the key. i executed "rpm --rebuilddb" then no more problem it's a pity see my comment #7 2015/03/24 |