Quote:
Originally Posted by Nylex
If you add yourself to the "audio" group, you shouldn't get the message about /dev/dsp. Have you tried launching Firefox from a terminal to see if there are any error messages?
|
This issue has been covered many times in even recent threads in this forum. Just to reiterate, the issue is that in runlevel 3 you get added to "bonus" groups as set by /etc/login.defs
Quote:
Originally Posted by /etc/login.defs
# Note that users are added to these default groups only when
# logging into a shell with /bin/login, not when using a login
# manager such as kdm. In that case, users who should have
# hardware access must be added to the appropriate groups
# when the user is added with adduser or useradd, or by editing
# /etc/group directly.
#
CONSOLE_GROUPS floppy:audio:cdrom:video
|
As a result, your audio seems to work fine in runlevel 3, but not in runlevel 4 unless you user is a part of the audio group.
Code:
gpasswd -a user audio
should add your user to the audio group. Be sure to relogin that user and then run
groups to check if the group is there. While you are at it, make sure your user is at least part of the
plugdev group as well to make sure HAL works properly. Also, the
lp group is suggested for printing in 12.1 (see the CHANGES_AND_HINTS.TXT).
Quote:
Originally Posted by tommcd
Also, try creating a new profile for firefox. Try temporarily moving~/.mozilla to ~/.mozilla.old. Then relaunch Firefox. This will create a new ~/.moziila folder, and a new profile with it.
You can always [mv ~/.mozilla.old ~/.mozilla] to put it back if it doesn't fix it.
|
~/.mozilla/
firefox/ is the default location for Firefox profiles. If you mess with the entire .mozilla folder you are also messing with your seamonkey profiles as well. Running
firefox -P lets you create a new (and delete or rename) a profile anyways, so you should not have to clear anything out.
If allend's advice on SCIM isn't what you need I first recommend that you check for any lock files under your profile that may be preventing it from opening. It will be called something like
.parentlock. If firefox is not running then remove this file. If you have to kill any running instances of firefox first (
pkill firefox).
If you think it is a profile problem then by all means try a new profile. As I said earlier, you can simply create a new profile for testing by using the Profile Manager (
firefox -P).