https://bugzilla.novell.com/show_bug.cgi?id=383493 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383493#c1 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Target Milestone|--- |Beta 2 --- Comment #1 from Stefan Seyfried 2008-04-29 10:41:41 MST --- not really :-) s2ram segfaulted (139 == 128 + 11 => killed by sig11). I assume that s2ram -n shows you something about "Fixes: VBE_POST VBE_MODE" or similar. Reason is that the 2.6.25 kernel has a NX security fix which breaks libx86 and thus s2ram (the secupdate triggers a bug in libx86) Please update libx86 and suspend package from FACTORY, this will probably fix the problem. The libx86 package must contain this changelog entry: * Do Apr 17 2008 seife@suse.de - upstream fixes (from the ubuntu hardy package), among others: - Handle reading addresses that are outside the process range with the x86emu backend - Add xorg upstream fixes for cpuid, rdtsc, bsr, bsf opcodes - fix a problem that appears with NX fixes in 2.6.25 by mmap()ing video memory PROT_EXEC -- 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=383493 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383493#c3 --- Comment #3 from Stefan Seyfried 2008-04-30 09:09:14 MST --- It still segfaults (then it's a bug) or it still shows "VBE_POST VBE_MODE" (this is a feature)? The "could not unmount" message is either a KDE problem, or there is an external medium that cannot be unmounted? -- 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.