Bug 253279 - No sound for 'imported' users
Summary: No sound for 'imported' users
Status: RESOLVED DUPLICATE of bug 239688
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Installation (show other bugs)
Version: Final
Hardware: 32bit Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Jiří Suchomel
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-09 23:03 UTC by Christophe de Rivière
Modified: 2007-03-29 11:43 UTC (History)
0 users

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


Attachments
Last y2log as requested (4.92 MB, text/plain)
2007-03-20 08:43 UTC, Christophe de Rivière
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe de Rivière 2007-03-09 23:03:29 UTC
Opensuse 10.2 installed on a computer where there is also another linux distro already installed. During install, it proposes me to import the users of this other distro. 2 users whose uid are 501 and 502.
When rebooting after install, no sound for users but yast sound configurator can play sound. See : http://www.suseforums.net/index.php?showtopic=31907
Thanks to harryc, i realised that these users were not belonging to the 'users' group and then could not access to audio hardware. I had to modify this and then my users had sound. This seems to be a bug in the feature of the installer allowing installer to import user from other distro.
Comment 1 Cyril Hrubis 2007-03-13 10:39:05 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 2 Christophe de Rivière 2007-03-20 08:43:22 UTC
Created attachment 125369 [details]
Last y2log as requested

Last y2log as requested
Comment 3 Jiří Suchomel 2007-03-26 07:40:51 UTC
Could you please test again with openSUSE-10.3 Alpha2 or newer? I believe this is a duplicate of bug #239688
Comment 4 Jiří Suchomel 2007-03-29 11:43:53 UTC
I actually think it is already solved, please reopen if you find the problem again in 10.3

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