Bug 401627 - DELL Inspiron 1501 Freezes !! with openSUSE 11.0
Summary: DELL Inspiron 1501 Freezes !! with openSUSE 11.0
Status: RESOLVED DUPLICATE of bug 389656
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: 64bit openSUSE 11.0
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-19 08:48 UTC by Alex Rodriguez
Modified: 2008-06-19 15:03 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
LOGS (messages, boot) hwinfo_file, and some files with the gdm (97.85 KB, application/x-gzip)
2008-06-19 08:48 UTC, Alex Rodriguez
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Rodriguez 2008-06-19 08:48:22 UTC
Created attachment 223026 [details]
LOGS (messages, boot)  hwinfo_file, and some files with the gdm

My laptop is a DELL Inspiron 1501
AMD Thurion 64bits dual core

I have installed ir openSUSE 11.0 (final) 32bits
All the process was fine

But i can't do more than a few minutes of working with the system, it freezes
The cursor still can move, but it does not function
the CAPSLOCK light does not respond
I can't go to a command terminal :s
and the only thing i can do is shutdow by presing the Power-Button

What can i do ?
Comment 1 JP Rosevear 2008-06-19 13:40:45 UTC
Are you using reiserfs?
Comment 2 JP Rosevear 2008-06-19 13:49:40 UTC
If so, this is a dupe of bug 389656, you can try the kernel of the day, or probably go computer->control center->search settings and turn off beagle for now which is using the problematic xattr's (system wide indexing may still trigger a problem).
Comment 3 Alex Rodriguez 2008-06-19 14:16:28 UTC
Yes, I'm using reiserfs as the file system

I'm going to try the beagle solution that you wrote
Comment 4 JP Rosevear 2008-06-19 15:03:12 UTC

*** This bug has been marked as a duplicate of bug 389656 ***