Either yesterday or the day before, can’t remember which, I ran some updates with apper and, like richardstevenhack was unable to update after that…apper just sat there. Unlike him, however, I was unable to perform the four updates with either YaST or zypper on the command line. YaST shows the four updates for dbus, elfutils, sysconfig and libqt5-qtbase in the left column, but on the right side some of the packages for each patch are marked with the “keep” symbol while others are marked with the “autodelete” symbol. Well, no matter, I figure, YaST can sort it out and I try to run the updates. All four of them will fail with a message like
Subprocess failed. Error: RPM failed: error: package sysconfig-netconfig-0.83.7-1.1.x86_64 is not installed
but obviously different package names depending on which patch (note that version 0.83.7-1.1 of that package is the outdated one), with the option to “Ignore”, “Abort” or “Retry”. Retry comes back with the same result, ignore looks like it is working but after it’s done nothing is different, and abort just stops the process so nothing is changed. Zypper is even more confused: zypper lu says “No updates found”, zypper up says “Nothing to do” yet zypper pchk says “4 patches needed (2 security patches)”. Apper at this point fails with the same error as YaST, instead of just sitting there like it did before.
When I look at the “Software Management” portion of YaST, for the troubled packages under the version tabs I see multiple versions “installed” (e.g. for sysconfig-netconfig there is
0.83.8-5.1.x86_64 from vendor openSUSE (installed)
0.83.7-1.1.x86_64 from vendor openSUSE (installed)
I’ve tried to uninstall the packages using YaST and tell it to “break package X and ignore the dependencies” just to see if I can get the package off the system and re-install it fresh, but it comes up with the same error that the package isn’t installed, and given the three available options nothing will actually “uninstall” the offending packages. What is going on and what can I do? And yes, I’ve tried zypper clean, zypper refresh and rebooting, no change with those. Thanks for the help.
I allowed Apper to be installed. However, I prevented its automatic startup in KDE
“Configure Desktop” –> “Startup and Shutdown” –> “Service Manager”
and uncheck the box for “Apper”.
On some systems, I also opened “System Tray Settings” (right click on tray), and unchecked “Software Updater”. The plan was to only use Yast online update and zypper on those systems.
On a system where I did not uncheck “Software Updater”, I ran into the same problems you had. So I then unchecked “Software Updater”. (I think that is called "closing the barn door after the horses have escaped).
I am still using “Software Updater” on my only 13.1 system, where it has not run into the same problems.
Maybe the space in the name problem. I believe the solution is to force a zypper and rpm install. It is a chicken and egg problem an earlier update broke things and you can’t update until the break is fixed. There are several threads on it here
For what it’s worth (not much, I know), I couldn’t get anything to fix the problem so I figured out how to use snapper, rolled back to a snapshot prior to when any problems were happening, and then used YaST to update packages to current. No problem now, everything is current and I’m not seeing anything about multiple versions installed in the versions tab like I was before.
And yes, disabling apper after the problem is definitely “closing the barn door after the cows are loose” :). I’ve been using apper ever since it was first integrated (three versions now?) and it has never worked right. Thus far, however, my only problems have been that it won’t actually listen to how often you tell it to check for updates, seemingly always checking every hour unless there are actual updates, then it will not tell you about them, various UI problems and the near constant “unknown role” problem which prevents you from knowing any detailed information about a patch to be installed. Now I’ve actually had a system stability problem where something in the package management got screwy which I could not fix without going back in time essentially.
The problems with apper have been annoying enough so far, but this one will probably make me stop using it. It’s amazing that after three versions most of the forum here still recommends uninstalling it (as well as the wiki page). And yes, I know that I can’t say with surety that apper is definitely what broke my system in the first place here.
> The problems with apper have been annoying enough so far, but this one
> will probably make me stop using it. It’s amazing that after three
> versions most of the forum here still recommends uninstalling it (as
> well as the ‘wiki page’
This particular problem I don’t think you should blame apper that soon.
This my theory:
The problem fault is with certain packages. It triggers with apper
because apper, being automatic, finds the updates earlier than
YaST/Zypper, which have to be called manually.
There was a bad package, that had to be removed, modified, and then it
was reissued. If you chanced to update to the first version, your system
breaks, badly. So quickly aplying updates is what made the problem to
your system, not using apper. Or not exactly.
Experienced admins and users do not want apper because they, we, want to
be in control, and know how to do it.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
So have I, for at least four releases, and almost exclusively for all updates (where a vendor change is not required). It’s always worked here to install those updates. It also works on Tumbleweed (e.g used when packman updates alone appear), but otherwise there it is not the correct update method.
Thus far, however, my only problems have been that it won’t actually listen to how often you tell it to check for updates, seemingly always checking every hour unless there are actual updates, then it will not tell you about them, various UI problems and the near constant “unknown role” problem which prevents you from knowing any detailed information about a patch to be installed.
Mine is set to check daily, and AFAICT that is how it operates on 13.1 release (used for its longer term support). On 13.2 release, Apper has installed all its updates correctly, but it’s only run as a default version in a VM and not every day. It doesn’t appear to be checking hourly, but not a good example for that.
I agree the “unknown role” message [seen on 13.2] is totally unhelpful for any normal user. However on reviewing three openSUSE updates today, that message appeared once but clicking individual updates did produce details about the update. The behaviour is somewhat odd.
It’s amazing that after three versions most of the forum here still recommends uninstalling it (as well as the wiki page). And yes, I know that I can’t say with surety that apper is definitely what broke my system in the first place here.
Amazing and not true or at best an exaggeration. Some remove it, some of those recommend removal and some just post what they do to remove it, but overall only a few regulars take each opportunity to post about its removal.
It’s unlikely that Apper broke your system - the first patch did that.
On 2015-01-27 19:16, consused wrote:
>
> poorboywilly;2691442 Wrote:
> Amazing and not true or at best an exaggeration. Some remove it, some of
> those recommend removal and some just post what they do to remove it,
> but overall only a few regulars take each opportunity to post about its
> removal.
I should say that I don’t think it is broken, or a "bad thing"™. I
remove it simply because I don’t like it
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Upon attempting an update with zypper, it complains:
Installation of crystal-2.2.1-27.40 failed:
Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib64 /kde4/kwin3_crystal.so;5612d53f: cpio: open
error: crystal-2.2.1-27.40.x86_64: install failed
error: crystal-2.2.1-27.39.x86_64: erase skipped
I did “zypper clean”, “zypper refresh” attempted the update again; yet I still get the same error.
When I attempt to install a package manually I get:
TuxBox:~ # zypper install GimpResourcesThumbnailer
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
GimpResourcesThumbnailer
1 new package to install.
Overall download size: 28.8 KiB. Already cached: 0 B After the operation, additional 72.1 KiB will be used.
Continue? [y/n/? shows all options] (y):
Retrieving package GimpResourcesThumbnailer-2.1.2-1.39.x86_64 (1/1), 28.8 KiB ( 72.1 KiB unpacked)
Retrieving: GimpResourcesThumbnailer-2.1.2-1.39.x86_64.rpm .....................................................................................................[done (64.2 KiB/s)]
Checking for file conflicts: ................................................................................................................................................[done]
(1/1) Installing: GimpResourcesThumbnailer-2.1.2-1.39 ......................................................................................................................[error]
Installation of GimpResourcesThumbnailer-2.1.2-1.39 failed:
Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib64/kde4/gimpresourcesthumbnail.so;5612e9f4: cpio: open
error: GimpResourcesThumbnailer-2.1.2-1.39.x86_64: install failed
Regardless of what package I attempt to manually install, the attempt fails. The other type of error I get looks like:
TuxBox:~ # zypper install nano
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 2 NEW packages are going to be installed:
nano nano-lang
The following recommended package was automatically selected:
nano-lang
2 new packages to install.
Overall download size: 550.0 KiB. Already cached: 0 B After the operation, additional 2.2 MiB will be used.
Continue? [y/n/? shows all options] (y):
Retrieving package nano-2.3.6-1.1.x86_64 (1/2), 317.2 KiB (982.2 KiB unpacked)
Retrieving: nano-2.3.6-1.1.x86_64.rpm .........................................................................................................................[done (972.4 KiB/s)]
Retrieving package nano-lang-2.3.6-1.1.noarch (2/2), 232.8 KiB ( 1.2 MiB unpacked)
Retrieving: nano-lang-2.3.6-1.1.noarch.rpm ....................................................................................................................[done (765.3 KiB/s)]
Checking for file conflicts: ................................................................................................................................................[done]
(1/2) Installing: nano-2.3.6-1.1 ...........................................................................................................................................[error]
Installation of nano-2.3.6-1.1 failed:
Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/bin/nano;5612eb80: cpio: open failed - No such file or directory
error: nano-2.3.6-1.1.x86_64: install failed
I read gogalthorp’s post. I compared the executable /bin/rpm on the failing system to a known-good copy on a properly functioning system, and they are identical.
I am using openSUSE 13.2 on x86_64
I am quite baffled on this problem. Any help would be appreciated.
I attempted using YaST to disable all my repos that were not a “stock” part of a clean install, and YaST failed with the error “Unable to save changes to the repository configuration”. I’m starting to wonder if I will need to make a clean start with a whole new install of openSUSE 13.2.
Anyway, as requested, the Grand Repositry List on my system:
a couple of home:… repos active, which are the developpers’ repos, regarded as unstable.
It may very well be that your system seems stable, but before I pay any attention to the alledged Apper issue, you need to fix your repos / installed packages first. It may very well be that the inconsistency is not in Apper, but rather in your system.
I implemented your suggestion, and it falied as follows:
TuxBox:~ # zypper clean && sudo zypper ref
All repositories have been cleaned up.
Repository 'Jitsi - Stable Builds' is up to date.
Repository 'openSUSE 13.1 - OBS - GSmartControl - Home of enzokiel' is up to date.
Repository 'openSUSE 13.1 - OBS - CrossToolChain (AVR)' is up to date.
Repository 'openSUSE 13.2 - DVD Install ISO Image' is up to date.
Repository 'openSUSE 13.2 - Hardware Tools (fingerprint reader)' is up to date.
Repository 'openSUSE 13.2 - KDE Extra' is up to date.
Repository 'openSUSE 13.2 - KDE3 (Kyamo)' is up to date.
Repository 'openSUSE 13.2 - NVIDIA Proprietary, Accelerated Video Card Drivers' is up to date.
Repository 'openSUSE 13.2 - Network (qBittorrent)' is up to date.
Repository 'openSUSE 13.2 - Non-OSS' is up to date.
Repository 'openSUSE 13.2 - Non-OSS Updates' is up to date.
Repository 'openSUSE 13.2 - OBS - DeKorator for KDE4 - Home of cfeck' is up to date.
Repository 'openSUSE 13.2 - OBS - Plasmoid Quick Access - Home of ecsos' is up to date.
Repository 'openSUSE 13.2 - OSS' is up to date.
Repository 'openSUSE 13.2 - OSS Debug' is up to date.
Repository 'openSUSE 13.2 - OSS Debug Updates' is up to date.
Repository 'openSUSE 13.2 - OSS Source' is up to date.
Repository 'openSUSE 13.2 - OSS Updates' is up to date.
Repository 'openSUSE 13.2 - Packman - All Repositories' is up to date.
Repository 'openSUSE 13.2 - Science (GEDA, KiCad)' is up to date.
Repository 'openSUSE 13.2 - Utilities (BleachBit, Alien)' is up to date.
Repository 'openSUSE 13.2 - VLC - VideoLAN' is up to date.
Repository 'openSUSE 13.2 - VirtualBox' is up to date.
All repositories have been refreshed.
TuxBox:~ # zypper up
Loading repository data...
Reading installed packages...
The following 138 package updates will NOT be installed:
acpica amarok android-tools appmenu-qt bind-utils bluedevil bluedevil-lang btrfsprogs calibre calibre-icons-branding-upstream choqok cln cpupower crda cyrus-sasl
cyrus-sasl-crammd5 cyrus-sasl-digestmd5 cyrus-sasl-gssapi cyrus-sasl-plain digikam digikam-doc dnsmasq ed filezilla gegl-0_2 gstreamer-plugins-qt gtk2-engine-oxygen
gtk2-theme-oxygen hugin iscsiuio javapackages-tools kaffeine kde-gtk-config kim kio_iso kipi-plugins kipi-plugins-acquireimage kipi-plugins-geolocation kipi-plugins-lang
konversation konversation-lang krb5 krb5-32bit ksshaskpass ktorrent kvkbd lensfun-data libavutil52 libbabl-0_1-0 libbluedevil2 libbtrfs0 libchromaprint0 libcpupower0 libdca0
libepub0 libffmpeg-devel libftdi1 libgegl-0_2-0 libiw30 libjoschy0 libkgeomap-lang libkgeomap2 libkqoauth0 liblensfun0 libmad0 libmediainfo0 libmediawiki1 libmpeg2-0 libmtp9
libndp0 libnuma1 libodfgen-0_1-1 libopenal1 libopencv2_4 libpcre1 libpcre1-32bit libpcre16-0 libpython2_7-1_0 libpython2_7-1_0-32bit libqalculate5 libqca2 libqjson0
libqmi-glib1 libqmi-tools libraw10 libsasl2-3 libsasl2-3-32bit libspandsp2 libspeechd2 libssh4 libtag-extras1 libtelepathy-qt4-2 libvisual libvlc5 libvlccore8 libzen0
linuxconsoletools lsof mediainfo-gui moodbar numactl open-iscsi openal-soft openssh openssh-askpass openssh-helpers p7zip pm-utils prctl python python-Pygments python-base
python-dnspython python-numpy python-setuptools python-six python-xml python3-setuptools python3-speechd recorditnow rpcbind rsync skanlite skanlite-doc skanlite-lang
smartmontools snapper snapper-zypp-plugin speech-dispatcher speech-dispatcher-module-espeak synaptiks tnftp vokoscreen vpnc w3m wireless-regdb wireless-tools wpa_supplicant
The following application is going to be REMOVED:
"KDE Partition Manager"
The following 45 packages are going to be upgraded:
VirtualBox-5.0 amarok crystal ffmpeg gstreamer-plugins-base k4dirstat ktp-approver ktp-desktop-applets libavcodec56 libavdevice56 libavfilter5 libavformat56 libavresample2
libavutil54 libbluray1 libffmpeg-devel libgstallocators-1_0-0 libgstapp-1_0-0 libgstaudio-1_0-0 libgstfft-1_0-0 libgstpbutils-1_0-0 libgstriff-1_0-0 libgstrtp-1_0-0
libgstrtsp-1_0-0 libgstsdp-1_0-0 libgsttag-1_0-0 libgstvideo-1_0-0 libpostproc53 libqxt1 libstreamanalyzer0 libswresample1 libswscale3 libvlc5 libvlccore8 mpv partitionmanager
partitionmanager-lang smplayer smplayer-lang vlc vlc-codecs vlc-noX vlc-noX-lang vlc-qt xine-ui
45 packages to upgrade.
Overall download size: 95.2 MiB. Already cached: 0 B After the operation, additional 215.6 KiB will be used.
Continue? [y/n/? shows all options] (y):
Retrieving package crystal-2.2.1-27.40.x86_64 (1/45), 156.8 KiB (845.8 KiB unpacked)
Retrieving: crystal-2.2.1-27.40.x86_64.rpm ..................................................................................................................................[done]
.
.
.
.
Retrieving: vlc-codecs-2.2.1-291.1.x86_64.rpm ...............................................................................................................................[done]
Retrieving package VirtualBox-5.0-5.0.6_103037_openSUSE123-1.x86_64 (45/45), 63.1 MiB (163.5 MiB unpacked)
Retrieving: VirtualBox-5.0-5.0.6_103037_openSUSE123-1.x86_64.rpm ................................................................................................[done (1.5 MiB/s)]
Checking for file conflicts: ................................................................................................................................................[done]
( 1/45) Installing: crystal-2.2.1-27.40 ....................................................................................................................................[error]
Installation of crystal-2.2.1-27.40 failed:
Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib64/kde4/kwin3_crystal.so;5613743c: cpio: open
error: crystal-2.2.1-27.40.x86_64: install failed
error: crystal-2.2.1-27.39.x86_64: erase skipped
Abort, retry, ignore? [a/r/i] (a): a
Problem occured during or after installation or removal of packages:
Installation aborted by user
Please see the above error message for a hint.
TuxBox:~ #
I do not know if Apper has anything to do with my problem; I only said my problem was similar to the one at the beginning of this thread. I made no claim of any problem caused by Apper.
As for the repos labeld for openSUSE 13.1, I would love to disable them to see if it helps. Yet, as I previously stated, I attempted using YaST to disable all my repos that were not a “stock” part of a clean install, and YaST failed with the error “Unable to save changes to the repository configuration”.
I also can not disable any repos from the command line, as demonstrated below:
TuxBox:~ # zypper mr -d "openSUSE 13.1 - OBS - GSmartControl - Home of enzokiel"
Error while modifying the repository:
Can't open file '/etc/zypp/repos.d/openSUSE 13.1 - GSmartControl - OBS Home of enzokiel.repo' for writing.
Leaving repository openSUSE 13.1 - GSmartControl - OBS Home of enzokiel unchanged.
TuxBox:~ #
Why the configuration information for the repo could not be opened for writing is a mystery to me, as neither YaST nor Apper wwer running at the time I executed the command.
Any help would be appreciated.