Mailinglist Archive: opensuse-bugs (6901 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=677444

https://bugzilla.novell.com/show_bug.cgi?id=677444#c0


           Summary: Every time I close the laptop, instead doing what-ever
                    it be done according to power saving rules (KDE) in
                    that case, the SO hangs.
    Classification: openSUSE
           Product: openSUSE 11.4
           Version: RC 2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Kernel
        AssignedTo: kernel-maintainers@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: publio.escipion.el.africano@xxxxxxxxx
         QAContact: qa@xxxxxxx
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.2.13)
Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13

Every time I close the laptop, instead of locking my session, or what-ever it
be done according to power saving rules (KDE) in that case, the SO hangs.
11.4 RC 2 complains at boot (the very first line, that is not collected into
/var/log/messages):
"FATAL: Module piix not found."
Are related?
I do not require, nor use any foreign module (for video, wireless, etc.), but
built in in kernel are enough. So, it is not a problem with proprietary drivers
I had installed.

Reproducible: Always

Steps to Reproduce:
1.Power adapter plugged-in (for instance), Run 11.4 RC2, KDE, log-in,
2.Close laptop
3.SO hangs.
4.Press Power button till power off (the SO is really hang, as it can not
capture the stimuli, so initiate a power-off sequence).
Actual Results:  
SO hangs.

Expected Results:  
Every time I close the laptop, be done what-ever it be according to power
saving rules (KDE) in that case, so if Power adapter were plugged-in, I expect
that my session were locked instead of hang.

-- 
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.