I am running 11.4 with KDE updated to 4.6.3 and suddenly I cant start Yast or Software Manager using kickoff. It doesn’t even open the dialogue to ask for root password. I see Yast appear in the panel for 15 seconds or so then it just disappears without opening a window.
If I open a terminal and su to root and run yast2 it work fine.
Strange I just rebooted the PC and it works fine now. I had tried logging out of KDE and back in again before but that didn’t fix it. Reboot did though.
On 06/01/2011 12:36 AM, pcolbeck wrote:
> That command just hangs. No output.
what about, in a user terminal
/sbin/yast2
any output in bash? and did a partially populated gui yast come?
–
dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255
On 06/01/2011 01:06 AM, pcolbeck wrote:
>
> Strange I just rebooted the PC and it works fine now. I had tried
> logging out of KDE and back in again before but that didn’t fix it.
> Reboot did though.
i see you have not many trips to this forum but i can’t see if you have
15 minutes or 15 years experience with *nix-like operating systems so i
feel compelled to say:
please don’t get the idea that (like Windows) a reboot is likely to
“fix” anything…
and, please don’t get in the old Redmond first team first idea to fix as
a reinstall, because usually a reinstall is never required unless the
operator somehow manages to murder the system though improper or
incorrect administrative procedures…
if you knew all of that, sorry to mention it…
–
dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255
On 2011-06-01 08:48, DenverD wrote:
> please don’t get the idea that (like Windows) a reboot is likely to “fix”
> anything…
Yes and no…
When you delete files that are still in use (something that happens when
doing updates) the old file is not really deleted, not till all the
applications using it exit. This is a characteristic of Linux filesystems.
Worse, an application can keep using the old library, and another one
started later will use the new version of that same library. This is
inconsistent.
This situation is detected by running “zypper ps”, and then corrected by
manually restarting those applications or services - which needs some
experience. It is easier to just reboot, no thinking necessary.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
> On 2011-06-01 08:48, DenverD wrote:
>> please don’t get the idea that (like Windows) a reboot is likely to “fix”
>> anything…
>
> Yes and no…
>
> When you delete files that are still in use (something that happens when
> doing updates) the old file is not really deleted, not till all the
> applications using it exit. This is a characteristic of Linux filesystems.
>
> Worse, an application can keep using the old library, and another one
> started later will use the new version of that same library. This is
> inconsistent.
>
> This situation is detected by running “zypper ps”, and then corrected by
> manually restarting those applications or services - which needs some
> experience. It is easier to just reboot, no thinking necessary.
But… Simply logging out (not rebooting) will accomplish what needs to be
done just as well 99 times out of 100. The only things that routinely
require a reboot are updates to the kernel itself. Note that if any users
remain logged on this may be ineffective.
It’s easy enough tell if the simple logout/login does the trick - just re-
run 'zypper ps".
Probably 15 years or more. Been running Linux since Before Redhat 4.0. Mainly been a Debian user though and Ubuntu on the desktop recently. I used to use SuSE a lot at home in the 7.x days but all this zypper stuff is new to me.
I was really surprised that rebooting fixed it, thought a logout and back in might have been necessary but not a reboot.
I bet there would have been a way of fixing it by restating some process or other but hey ho sometimes it’s just quicker to reboot if the machine is just a desktop not a critical server.
I appreciate the help though and even if someone has plenty of experience it does no harm to point out the obvious as sometime we all forget stuff and have “slap forehead” moments.
On 2011-06-02 00:26, Will Honea wrote:
> Carlos E. R. wrote:
>> This situation is detected by running “zypper ps”, and then corrected by
>> manually restarting those applications or services - which needs some
>> experience. It is easier to just reboot, no thinking necessary.
>
> But… Simply logging out (not rebooting) will accomplish what needs to be
> done just as well 99 times out of 100. The only things that routinely
> require a reboot are updates to the kernel itself. Note that if any users
> remain logged on this may be ineffective.
Yes, if what was updated belongs to the desktop. Sometimes that is not
enough, you need to do init 3, init 5.
> It’s easy enough tell if the simple logout/login does the trick - just re-
> run 'zypper ps".
Absolutely. I would log in text mode instead, to save time. As root, to be
able to change runlevel.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
On 06/02/2011 11:06 AM, pcolbeck wrote:
>
> Thanks guys
welcome…with that kind of experience you are MOST welcome to drop in
more often…we get plenty here that you could help, if you have the
patience…and time…
ps: zypper is just a variation of apt, yum or whatever…it is pretty
powerful though…and yast is just super for a whole host of things in
addition to ‘simple’ software management…
but, steer well clear of package kit, it is NOT ready for prime
time…instead use zypper or YaST Online Update…
–
dd CAVEAT: http://is.gd/bpoMD
[NNTP via openSUSE 11.4 [2.6.37.6-0.5] + KDE 4.6.0 + Thunderbird 3.1.10]
Dual booting with Sluggish Loser7 on Acer Aspire One D255