Hi I just did a clean install of 12.3. The install went fine but I had a problem with Online Update to bring my system up to date. So there were a lot of updates to install, at least 225. It was about 53% complete, I can’t remember what was installing, but it appeared to have hung. I tried several attempts to abort, and it wouldn’t abort. Eventually, I rebooted. Now when I try to run Online Update, I get the message “Removing shim” and Package Installation Progress has stalled at 5% complete, Total Progress is 0%. It’s been nearly three hours stuck there. So how to recover from this?
Quit it
I always do
zypper patch
then reboot
then
zypper patch
then reboot
then
zypper up
On 10/10/2013 11:51 AM, caf4926 pecked at the keyboard and wrote:
> Quit it
>
> I always do
>
>
> Code:
> --------------------
> zypper patch
> --------------------
>
> then reboot
> then
>
> Code:
> --------------------
> zypper patch
> --------------------
>
> then reboot
> then
>
> Code:
> --------------------
> zypper up
> --------------------
>
>
WTF, there is no need for the reboots unless packages are updated that
require a reboot (hint, kernel update). People, this is NOT MS Windows.
Ken
I am pretty sure we know that. Programs will not always use new libraries unless they are restarted. On a personal workstation there isn’t much cost to doing so.
On 10/10/2013 01:16 PM, nightwishfan pecked at the keyboard and wrote:
> kensch;2590445 Wrote:
>> WTF, there is no need for the reboots unless packages are updated that
>> require a reboot (hint, kernel update). People, this is NOT MS Windows.
> I am pretty sure we know that. Programs will not always use new
> libraries unless they are restarted. On a personal workstation there
> isn’t much cost to doing so.
>
>
Which requires a restart of the program, not the computer. Again this is
/not/ MS, stop giving advice like it is.
Why am I arguing with someone upset over rebooting a machine? This isn’t drama class.
On 2013-10-10 19:34, Ken Schneider wrote:
> On 10/10/2013 01:16 PM, nightwishfan pecked at the keyboard and wrote:
> Which requires a restart of the program, not the computer. Again this is
> /not/ MS, stop giving advice like it is.
You have to run “zypper ps” to verify what needs to be restarted. In
many cases, it is just easier to reboot.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Logging out and back in is often enough for most things other then kernel updates and a small handful of others.But note that only restarts processes for the current user and may not for a multi-user machine that many people are using at the same time. In which case you must reboot or manually restart the processes. A user level process will not be updated for a given user if they are currently running it. ie an update changes the file on the disk but does not change a running process until it is restarted
@kensch: A reboot is much easier than a restart of a process. You can do both and the result is the same here.
Sometimes you need a lot of time to explain the difference for Linux newcomers.
You don’t know the knowledge of the TO.
On 10/11/2013 09:26 AM, AdaLovelace pecked at the keyboard and wrote:
> @kensch: A reboot is much easier than a restart of a process. You can do
> both and the result is the same here.
> Sometimes you need a lot of time to explain the difference for Linux
> newcomers.
> You don’t know the knowledge of the TO.
>
>
I have been a linux user since 1995, unix since 1989 so yes I think I
have a little knowledge of what requires a reboot and what doesn’t. It’s
better to teach the newcomers the “better” way of doing things rather
then just telling them to reboot. It may take a little more effort on
your part to teach the better way of doing things then taking the “easy
way out” that MS has dumb-ed everyone down to.
Oh, and restart of a program is /much/ faster then a computer restart.
Ken
The OP has just done a clean install of 12.3. There have been several kernel patches since this was released, and at least one reboot will be required.
On 2013-10-11 23:06, chief sealth wrote:
> The OP has just done a clean install of 12.3. There have been several
> kernel patches since this was released, and at least one reboot will be
> required.
And a glibc update, which also requires a reboot.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
In defence of my seeming lack of knowledge -
IMO, it’s just easier to suggest a reboot given the circumstances.
It was clear to me the OP wasn’t running a mission critical server… so a reboot was never going to be an issue. And in any case, it is a belt and braces approach to make sure all is correct.
No need to defend yourself Carl. As the majority hare have already noted, there is good justification for a reboot, and it does no harm. Experienced users will know how to restart any required processes for updates to take effect, while new users will find it easier to do what was recommended with no fuss. Common sense really.
On 2013-10-12 05:36, caf4926 wrote:
>
> In defence of my seeming lack of knowledge -
> IMO, it’s just easier to suggest a reboot given the circumstances.
> It was clear to me the OP wasn’t running a mission critical server…
> so a reboot was never going to be an issue. And in any case, it is a
> belt and braces approach to make sure all is correct.
Oh, I absolutely agree 
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
On 10/11/2013 11:36 PM, caf4926 pecked at the keyboard and wrote:
> In defence of my seeming lack of knowledge -
> IMO, it’s just easier to suggest a reboot given the circumstances.
> It was clear to me the OP wasn’t running a mission critical server…
> so a reboot was never going to be an issue. And in any case, it is a
> belt and braces approach to make sure all is correct.
>
>
I agree that with a personal PC, non-business critical system it may be
easier to just reboot. But we all need to keep in mind what is best use
practice.
On to the next problem.
Ken
Well being the newbie user, ( 4 months and counting), I appreciate being taught how to do things in the most efficient way. And it is my time where the efficiency matters, not the PC.
The end result is to bring the PC/process back to a usable state, if a bit of learning can be infused simultaneously, then more power to those that want it. But not if it gets so deep into the weeds so as to require too much learning time and gets in the way of getting things done.
With all due respect to all the Linux mavens, I always get a kick out of the comments from folks like Kensch. It seems like they feel sorry for the PC. I do agree that a bit of learning so as to be able to restart a process might be a good thing. I say might because in my newbie brain, starting a process could be wayyyyy more complicated and tedious than a reboot.
If I were to try it, the 1st things I would ask myself would be related to parent or child dependencies of the process that I am restarting. Are there any, and how do I go about figuring it out ?
I vote for a reboot.