[Bug 698814] New: after installing all security and recommended updates (2011-06-08) system has little problems
https://bugzilla.novell.com/show_bug.cgi?id=698814 https://bugzilla.novell.com/show_bug.cgi?id=698814#c0 Summary: after installing all security and recommended updates (2011-06-08) system has little problems Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bluedzins@wp.pl QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; U; en) Presto/2.8.131 Version/11.11 I installed all security (it is important, right) and recommended (it's the best to keep with recommended solutions) updates, all as for 2011-06-08. After installing all of them, I was asked to reboot the system. On positive side, the system was able to run again, but with such slight problems: * pretty many errors during boot (*) * the network is dead * the audio is dead * cannot mount any pendrive, because now vfat is not recognized (*) I would love to attach yast logs, but thanks to updates I am now disconnected from the world -- not net, no pendrives. Reproducible: Always Steps to Reproduce: 1. install updates for your computer 2. observe problems -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c1
--- Comment #1 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c2
--- Comment #2 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c3
--- Comment #3 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c4
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c5
Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c6
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c7
--- Comment #7 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c
Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c8
Michael Andres
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c
Jiri Srain
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c9
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c10
Maciej Pilichowski
Well, without /boot a kernel update obviously can't work.
But Yast shouldn't silently ignore that fact.
But in comment 7 you mention someone asked you to mount it. Which program was that?
It was Yast again. But note the difference -- when updating it was done via delta rpms, when restoring the system it was via full rpms ("update unconditionally") from OpenSUSE 11.4 release packages (copied from DVD). Yast->Software Management. Qt version (in both cases). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c11
Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c12
Ladislav Slezak
You see, normally I do NOT have boot partition mounted, and even it was mounted, it would be read-only.
Um, so how would you update the kernel if /boot is not mounted or mounted in read-only mode? And why do you have such setup? That's really unusual and strange... I quickly went through all yast sources and I could not find any "not mounted" error, and in the logs I also didn't find anything. Could you be more specific? When exactly was the warning displayed? A screenshot would be very helpful... (In reply to comment #10)
It was Yast again. But note the difference -- when updating it was done via delta rpms, when restoring the system it was via full rpms ("update unconditionally") from OpenSUSE 11.4 release packages (copied from DVD).
Deltas contain only the difference from the original package to the updated version and thus cannot be used for downgrade (they don't contain the needed data) so in this case full RPMs are used. That's expected behavior. (Decreasing the severity because of the unusual manual tweak...) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c13
Maciej Pilichowski
Um, so how would you update the kernel if /boot is not mounted or mounted in read-only mode?
"Dear user please mount /boot partition in read-write mode in order to update the kernel". Displaying messages is too hard?
And why do you have such setup?
Because it fit my needs.
That's really unusual and strange...
No, this is not strange. /boot partition for normal work is not needed at all. You can find a couple of reasons why it is wise to unmount it (and how to setup it) if you google for it.
I quickly went through all yast sources and I could not find any "not mounted" error, and in the logs I also didn't find anything. Could you be more specific? When exactly was the warning displayed? A screenshot would be very helpful...
a) I think there is problem with lack of the message, not with the message, so I would worry about the process which does NOT display it b) warning was displayed while restoring all selected rpms which I thought were causing the problems with the system c) screenshot would mean, repeating all the steps now -- which is pretty dangerous to my system, so sorry, but "no" for sure
Deltas contain only the difference from the original package to the updated version and thus cannot be used for downgrade (they don't contain the needed data) so in this case full RPMs are used. That's expected behavior.
I know, you asked what I did, so I explained.
(Decreasing the severity because of the unusual manual tweak...)
Setting it back, because of not statistically founded assumptions. Kernel is the core of the system, kernel update algorithm is lousy (every programmer will tell you that), incorrect update can cost user ALL the data and a lot of time. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c14
--- Comment #14 from Steffen Winterfeldt
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c15
--- Comment #15 from Maciej Pilichowski
I'd also say the setup is weird, at best.
http://www.linuxjournal.com/article/7743 (just an example) I have to write to LJ why they publish info about such weird setups then.
Anyway, if you say some program does already care about it, it would help if you narrowed down _which one_ that is. Maybe you could remember some more detail than just 'I downgraded somehow'.
Yeah, I remembered, and for the third time I write it -- Yast/Software Management. And I also remember and I WROTE IT (so please do not offend me) that I selected update unconditional in Yast/SM because I was downgrading packages.
Also, if you take this seriously, it's not about just /boot but any fs mounted somewhere that is touched by a new rpm.
I do take it VERY seriously and you are right, /boot partition is this case, but in general (and I wrote it just a few minutes before) there is /etc/mtab to check what partitions are mounted. Before file/partition operation program should always check if the target is available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c16
Ladislav Slezak
b) warning was displayed while restoring all selected rpms which I thought were causing the problems with the system
I see, so it should be displayed also during update.
c) screenshot would mean, repeating all the steps now -- which is pretty dangerous to my system, so sorry, but "no" for sure
Sorry, the same for me, I don't have time now for reproducing and debugging this unsupported scenario. For me it's low priority.
Yeah, I remembered, and for the third time I write it -- Yast/Software Management.
We need more _details_, if you cannot/do not want to provide them I'll close it as WONTFIX. Sorry, this but this doesn't help to solve the problem.
Before file/partition operation program should always check if the target is available.
That's complete nonsense - if there is no free space, network stops, no memory etc. programs simply report error, and _you_ have to solve the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=698814
https://bugzilla.novell.com/show_bug.cgi?id=698814#c17
Maciej Pilichowski
participants (1)
-
bugzilla_noreply@novell.com