I hope the fix will be available soon. The suggested bug report has already been marked as fixed, but the bug is still reproducible (11.2, x86_64)
esusnepoz wrote:
>
> I hope the fix will be available soon. The suggested bug report
> has already been marked as fixed, but the bug is still
> reproducible (11.2, x86_64)
>
>
yes I see the bug and I’ve seen no kernel update to fix it.
Russ
| openSUSE 11.2 (2.6.31.12-0.1-desktop) x86_64 | KDE 4.3.5 release 3
| Intel Core 2 Dual E7200 | 4 GB RAM | GeForce 8400 GS | 320GB Disc
(2) |
Same problem as others. Waiting for update to be available. Hope its soon.
Thanks to all who posted. At least I know it’s an official bug.
===========
openSuse 11.2 linux 2.6.31.12-0.1-desktop x86_64
I wonder how long must we wait for promised update? I thought bugs are resolved very quickly in linux world, it is one of the main advantages of linux over Windows - this statement is well known.
But in real world i can see that i use the same buggy kernel as several weeks before >:(
Just to point out that the patch must be tested. Perhaps there were side effects that broke something else.
itten wrote:
> I wonder how long must we wait for promised update? I thought bugs are
> resolved very quickly in linux world,
define “very quickly”…
that is, i believe there have been two kernel updates for openSUSE in
the last 50 days or so…
and, in that same time how many kernel updates, patches, etc have
flowed from Redmond for Win7/Vista/XP?
on the other hand, if things move too slowly here one can always get a
full refund of purchase price, with a smile–try that with Redmond or
Apple…
–
palladium
That is great anti-linux post.
First, you excuse linux by groundless and inappropriate humiliation of Windows.
Second, you offer me to give up linux if i have problems with it - yeah that is a way how to solve problems.
itten wrote:
> That is great anti-linux post.
> First, you excuse linux by groundless and inappropriate humiliation of
> Windows.
if Redmond is humiliated by its slowness in moving to patch their
products, that is their problem…not mine…
> Second, you offer me to give up linux if i have problems with it - yeah
> that is a way how to solve problems.
second, i didn’t say you should give up if you have problems with
Linux…instead i said (exactly) “if things move too slowly here one
can always get a full refund of purchase price”…
that does not mean you have to leave–since you paid nothing in the
first place…
i’d say instead of giving up you might consider switching from
complaining and and disrespecting the entire openSUSE community here
which has fixed many problems by providing you TWO kernel updates
in as many months, at no additional cost…and, instead say thank you…
–
palladium
Nevertheless, for several weeks I’m forced to shutdown computer manually - it is Stone Age!
I think fix of this kind of bug is as important as security updates and we need to get it asap.
itten wrote:
> I think fix of this kind of bug is as important as security updates and
> we need to get it asap.
i agree, and have no idea what the holdup is…
the bug <https://bugzilla.novell.com/show_bug.cgi?id=578222> is marked
RESOLVED and, if i read the recent posts correctly if you turn off
openSUSE online update it should be a workaround allowing you to shut
down normally, until the kernel update is distributed…
read through the bug report for yourself, then try it by right
clicking the online updater icon in the status bar and use the
resulting popup menu to find a way to turn it off (i can’t tell you
step by step because i stopped using the online updater a LONG time
ago and i don’t wanna have to figure out how to launch it, so i can
tell you how to turn it off!)
–
palladium
It is a pitty, but there is another reason for segfault.
There was a man in bugzilla who asked will it be ok if he installs **old ** kernel and doesn’t use online updater because it updates system to new buggy kernel. It doesn’t mean that online updater cause the bug, it means that online updater can update system to buggy kernel.
This is the bitter truth
then…patience…
–
palladium
i have been doing some testing and i have found that this error only occurs on computers with a GUI installed. i am currently running a server with a TTY only setup with kernel 2.6.31.12-0.1.1-default and i have no issues. how ever i have a system that i use on a regular basis and i have a GUI installed and have the segmentation fault during shutdown to temporarily fix the issue i downgraded to kernel 2.6.31.8 and works fine
Has it been determined whether this is a bug in this particular kernel, or KDE, or this particular Suse distribution?
Other forums are reporting the same error with kernel 2.6.31.12 so it doesn’t seem to be only related to opensuse eg. Segmentation fauld when shutting down with kernel 2.6.31.12 | Mandriva Forum
From this I conclude that it has to do with the kernel . So I think the solution for now is to install kernel 2.6.31.8 and wait for next kernel update .
I have here two MSI gx600 with this problem even if working under init 3. I can’t deliver them in this state!
This bug isn’t fixed yet. That’s what I really think… I cannot imagine the fix being tested for TWO weeks. New kernel with thousands of patches comes every 3-4 months out…
Everyday I need to switch off my computer manually… that’s awful. How long we are going to do this?!
I have the same problem on two systems running opensuse 11.2. The strange thing is that i have four other systems that are not affected.
When we expect a solution?
This is awfully annoying. Right now the only solution seems to be to update the kernel, which introduces a host of dependency problems I have no idea how to fix, and I’m not gonna waste my time dealing with that. How long will openSUSE be unable to shut itself down without trouble, a basic task that every other operating system I’ve used (Linux-based and not) has had no trouble doing?
It is a big shame on novell. Idlers!
Even Microsoft do updates frequently