I have recently installed 12.3 32 bit with KDE desktop on my T42 laptop. All seemed well although I have had fairly regular notices that updates are available. These have been mainly gstreamer stuff as I recall and usually between 30 and 40 files. I have installed these without problem. Last night however the notice advised there were 1440 + files to be updated and included a reboot for one.
Since this process had been no trouble before, I went ahead and allowed the update. Big mistake. All the files downloaded but none were installed. I had a warning I was running out of disk space, probably true, but then everything stalled. Tried to restart and now cannot log into desktop. I can log into recovery console line but nothing else. Enter password and I just get the login screen back.
I should know this but how can I get my desktop back from the recovery console and is it credible that 1400+ files need updating or is this another apper error or have I been attacked by malware?
Nothing has been installed so far, since the “/” partition flooded before the system got to installing the packages.
Boot the system, enter the root password when prompted for, and run
Hi and thanks. That helped and now I have desktop back. Phew! I shall check hard drive capacity but 1440+ files would certainly have overfilled root directory.
Thanks again,
Budgie2
Yes, I took your advice with 12.2 and un-installed apper which was a disaster area then. Hadn’t thought about it when I installed 12.3 and when it appeared with notices of updates I assumed it had been improved. Clearly not, so will dump it once more. Also will check repos but I think they are OK.
You mean a disaster area for you on your 12.2 system, and now a disaster area for you on your 12.3 system. There seems to be a problem with your system(s).
Apper has been totally reliable updating my 12.2 and continues that way. It’s going ok on 12.3, just updated KDE to 10.2 using it, a lot of updates but not 1400.
If you get a different set of updates than would have been presented by zypper up, then there’s a serious bug in PackageKit-backend-zypp that must be investigated. The upgrades should always be exactly the same.
You might want to post your repo list - 1400 updates is ridiculous so something’s surely up with one of them. I can’t believe that could happen if you’ve stuck to the official repos.
I would like to know what authority you have to recommend Not using Apper? Do you have the current code in sync with git on your pc and have studied it to determine that people should not use it for some reason? If this is the case then maybe some bugs should be filed and you could provide us with some way to follow your appeal to stop using it. It seems a little circumstance to claim a program can not to be trusted or used when there is no proof that it is faulty.
> Yes, I took your advice with 12.2 and un-installed apper which was a
> disaster area then. Hadn’t thought about it when I installed 12.3 and
> when it appeared with notices of updates I assumed it had been improved.
> Clearly not, so will dump it once more. Also will check repos but I
> think they are OK.
Please post here your list of repos. Use:
su -
zypper lr --details
Before saying that apper is broken, we must see that list of repos.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 04/24/2013 06:06 AM, vazhavandan wrote:
> caf4926 has got authority of a mod <<_<<
no! being a moderator of these forums give caf4926 no magic extra authority to recommend or not recommend anything other than
following the terms and conditions of these fora…
on the other hand, his technical experience and capability is
sufficient that any recommendations based on his personal opinion and
experience is a recommendation which carries great weight with most
here who are experienced enough to know whats what.
on the third hand: if caf4926 recommended all openSUSE users should
run Apper, then i would exercise my personal authority to reject his
faulty opinion on this matter–no matter his experience.
Or indeed any evidence, rather than mere anecdote and unqualified opinion. Apper is after all a relatively simple user interface that doesn’t require any technical expertise from the operator. However the “system administrator” might have caused all sorts of back-room management problems.
In my own experience as an openSUSE user and not a developer, I like Apper a great deal. I was able to install it for a member of my family who was able to easily deal with all updates as they appeared.
HOWEVER, it all went wrong for me when I enabled the Packman repository and a couple of others for various useful pieces of software. The user soon came back to me and wondered why the same updates required installing every day. It seems Apper cannot determine the duplication of packages available in the regular openSUSE update repositories, and the Packman equivalents, and what the administrator had set as his/her preferences. In this case, I had enabled the Packman repository and selected the vendor switch so that this repo’s packages were preferred in YaST.
The upshot was a very sad removal of Apper to avoid confusion, and now updates are performed manually within YaST, which wasn’t an issue once I had shown them how. I was really sad about this though, as Apper is a terrific piece of software and really good idea for us everyday users. I hope it sees improvements for future releases. However if anyone could suggest a solution right now that is better than removing Apper in this situation I would be very grateful.
My Apper usage includes Packman, and a couple of other repos with far fewer updates. One difference is that I stopped using the YaST switcher on Packman a long time ago when I realized that Packman goes further than multimedia packaging within the multimedia-only repos e.g a couple of KDE packages (don’t recall names). Apper only performs the equivalent of zypper up (i.e. no vendor change by Apper). These days like on 12.2/3, I don’t mind mixing openSUSE and Packman multimedia packages even with gstreamer. It doesn’t seem to cause any issues.
Did your user provide you with actual details of duplicate package names and version levels for comparison? Even now, you should be able to find details in var/log/zypp/history. It would be interesting to look at some examples here.
