Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 168092

Summary: app-emulation/dosemu-1.3.3 won't run with LDAP users and glibc-2.5
Product: Gentoo Linux Reporter: Robert Gill <rtgill82>
Component: Current packagesAssignee: Hanno Böck <hanno>
Status: VERIFIED TEST-REQUEST    
Severity: normal    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info

Description Robert Gill 2007-02-23 06:48:50 UTC
DOSEMU refuses to run from a user account that is specified in LDAP.

Reproducible: Always

Steps to Reproduce:
1.Run DOSEMU from an LDAP account.
Actual Results:  
If I try to run DOSEMU from a user account that's in LDAP I get the error:
In file included from built-in global.conf:145
Error in : (line 145) cannot open includefile /home/user/.dosemurc
1 error(s) detected while parsing the configuration-file

If I touch the file /home/user/.dosemurc it will continue on past that point, but then I get the error:
ERROR: can't boot from (null), using harddisk
ERROR: Sector not found in read_sector, error = Illegal seek!
ERROR: can't boot from hard disk



DOSEMU runs fine and neither error occurs when it is run from an account that is specified in /etc/passwd.

DOSEMU also runs fine on another machine running glibc-2.4.  Both machines are setup the same for LDAP and in fact, use the same database.

I was able to work around the problem using nscd, but that has some drawbacks.  I'd prefer to find another solution.
Comment 1 Robert Gill 2007-02-23 06:50:16 UTC
Created attachment 111024 [details]
emerge --info
Comment 2 Hanno Böck gentoo-dev 2007-04-03 19:05:35 UTC
I'm not familiar with ldap. Can you please try dosemu 1.3.4 and if that also fails, try to resolve that with upstream developers?
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2007-08-17 15:01:03 UTC
Get back to us, please.
Comment 4 Robert Gill 2007-08-20 20:55:59 UTC
Turned out to be a problem on my side.  Overlooked a configuration file in the chroot directory I was running things under.