Bug 153689 - Cryptographic loopback file don't show up in YaST Partitioning Tool
Summary: Cryptographic loopback file don't show up in YaST Partitioning Tool
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: i686 SuSE Linux 10.0
: P5 - None : Normal
Target Milestone: ---
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-27 14:59 UTC by Dennis Sieben
Modified: 2006-03-21 12:43 UTC (History)
0 users

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

Attachments
The required log file (119.75 KB, application/octet-stream)
2006-02-28 09:04 UTC, Dennis Sieben 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Sieben 2006-02-27 14:59:07 UTC 
On a SL 10.0 System the cryptographic loopback devices for whole partitions are displayed in the YaST Partitioning Tool, but the loopbacks which are stored in files not. The are only displayed when you create them, but if you restart the YaST Partitioning Tool they are lost. It seems like the cryptotab file isn't parsed.
It might be important to say that the devices are functioning right and they also appear in cryptotab but not in the YaST Tool.

The problem seems to occur only on updated systems. I have two which are updated from 9.3 to 10.0 and both show the same problem. The fresh install on my working machine doesn't show this problem.
Comment 1 Michael Gross 2006-02-27 15:04:59 UTC 
Dennis, please attach the YaST logfiles.
Comment 2 Dennis Sieben 2006-02-28 09:04:45 UTC 
Created attachment 70591 [details]
The required log file

Sorry for attaching the log file so late. The machine stands at home.

When I'm right the cryptographic files appear in the log file. But they aren't display. Please tell me if you need some kind of screenshot.
Comment 3 Michael Gross 2006-02-28 11:27:32 UTC 
I don't think a screenshot is neccessary. The problem is that the cryptotab is not parsed correctly. I'll reassign the bug.
Comment 5 Thomas Fehr 2006-03-21 12:43:37 UTC 
Such bug are not any more fixed in SL 10.0
If possible retest with SL 10.1 beta8 and reopen if problem still present.