Bug 385715 - Beagle + Encrypted home == Hardlock of everything
Summary: Beagle + Encrypted home == Hardlock of everything
Status: RESOLVED DUPLICATE of bug 389656
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Factory
Hardware: Other openSUSE 11.0
: P2 - High : Critical (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 341832
  Show dependency treegraph
 
Reported: 2008-05-01 19:08 UTC by Bjørn Lie
Modified: 2008-11-10 14:34 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bjørn Lie 2008-05-01 19:08:13 UTC
If beagle is installed/running and you have a encrypted home, everything locks up hard.
Nothing works, drawing to screen dies, keyboard is unresponsive. 

Beagle runs just fine if I log in to my root account (that is on a unencrypted partition)

Setup: openSUSE 11 FACTORY - 2.6.25-24-pae (amd64cpu)
 hdd: lvm with /root and /home + swap (/boot is not on lvm but on same disk)

home and swap is encrypted (root and home is reiserfs)

--------

If I log in and switch to tty1 (logged in as root there) and look at top, beagled+beagle-helper goes to the top of list miliseconds before the lockup happens.

-----
lvm and partitions are freshly made for this install - ftpinstall of factory 30 of april, updatet 1.may to latest kernel++
Comment 1 JP Rosevear 2008-09-11 21:24:01 UTC
By any chance were you using reiser?
Comment 2 Bjørn Lie 2008-09-12 18:31:27 UTC
Yes, I wrote that in summary :)

Setup: openSUSE 11 FACTORY - 2.6.25-24-pae (amd64cpu)
 hdd: lvm with /root and /home + swap (/boot is not on lvm but on same disk)

home and swap is encrypted (root and home is reiserfs) <---- Look here :)

But as you can see, / was also on reiser at the time, so I'm not entirely sure that was the reason it broke.



Comment 3 JP Rosevear 2008-11-10 14:34:07 UTC

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