On 10/25/07, randd <[EMAIL PROTECTED]> wrote: > Hi, Dan > > > > ... What's the output of this command? > > > > $ gconftool-2 -g /desktop/gnome/sound/default_mixer_device > > Same here. I understand what you're saying, and thinking - initially, I was > thinking along the same lines. I was quite surprised to discover that some > of GNOME is still using oss. I'm looking back over my notes trying to > determine when it was I first saw "can't open /dev/dsp"; that was my first > tip-off; will resume the search tomorrow...
Any chance you can determine which app is causing that behavior? Look in ~/.xsession-errors. I've only had to enable OSS in a few rare occurrences with a very full GNOME desktop. > >> as a result of udev, or of anything else for that matter. Again, any ideas > >> or speculation would be welcome... > > > > Often the way this is done is to make the the snd-pcm module pull in > > the snd-pcm-oss module in modprobe.conf. This is explained in LFS: > > > > http://www.linuxfromscratch.org/lfs/view/development/chapter07/udev.html > > That makes sense; I'm not seeing any evidence of anything like that in > either Fedora 7 or Debian etch though and they're both loading snd_pcm_oss > et al. Given that they're both doing doing it I'm thinking something (an > app, probably some piece of GNOME) is causing them to be loaded (eg., > something is using a library that's causing snd_pcm_oss to be demand > loaded)... I doubt it's an app since that app would have to be suid or somehow gain root privileges to load a kernel module. Look in /etc/modules* or /etc/sysconfig/modules*. Every distro does it different. In LFS, you can add it to /etc/sysconfig/modules. > > You need more fonts. See the Xft section here: > > > > http://www.linuxfromscratch.org/blfs/view/svn/x/x-setup.html#fonts > > > > Installing FreeFont should give you (ugly) characters for nearly > > everything you find. > > Tried it; a scan of /var/log/Xorg.0.log shows no warnings r.e. missing or > corrupted fonts.alias / fonts.dir / fonts.scale - at first, I copied the > fonts over to /usr/lib/X11/fonts/default/TrueType & added that line to > /etc/X11/xorg.conf Sorry, wasn't specific enough there. Nothing in GNOME will care about Core X fonts, just Xft. So, anything with fonts.dir and xorg.conf doesn't matter. What does matter is if fontconfig is aware of newly installed fonts. Install the fonts to /usr/share/fonts/<whatever>, then run fc-cache. Run fc-list before and after to see if your new fonts are listed. > When I opened help in firefox it blew up: > *** glibc detected *** gnome-help: corrupted double-linked list: 0x0815c8a8 > *** > ======= Backtrace: ========= > /lib/libc.so.6[0xb6ebbfe0] <snip> Yikes. I've never seen that before. Incidentally, I think it's actually yelp using the Gecko engine, and not Firefox which is leading to this crash. I have no idea how to help you, though. > > It's a weak attempt at Gnome integration in Firefox. It tries to set > > the proper gconf key to make it the default browser, but it's setting > > the wrong key. Just turn that dialog off and set firefox as the > > default in the Preferences/Preferred Applications menu. ... > > So, the popup dialog isn't saving its result in the same place that the > preferences dialog is saving its? If I disable checking in Edit, > Preferences, "always check to see if mozilla is your default browser" then I > never see that popup. But, it doesn't matter how I answer the yes/no > question on that popup or whether the checkbox "always check ..." is cleared > or checked, firefox apparently ignores the result. It's handling the same > question differently in two different parts of the program, then? Hmm, I think they control the same setting in prefs.js. I turned the dialog off initially, and now "Always check..." is cleared in Preferences. I think the key is "browser.shell.checkDefaultBrowser". You can check it in about:config. > > It's actually a little worse, too, because saying Yes to that dialog > > makes firefox set itself as the default URL handler for nearly all URL > > types. So, now firefox is your preferred FTP handler, too. > > This is where it gets really wierd. My preferred application for a web > browser keeps (somehow) getting set back to "custom" whenever I run firefox. > Even if it was set to firefox before that... The actual executable for > firefox is in /usr/lib/firefox- ...; there's a symbolic link to it in > /usr/bin. I think that may be confusing GNOME; I'll play with that more > tomorrow too. Ah, now I remember correctly. The problem isn't that it sets the wrong key, it's that it gets set incorrectly. Firefox tries to determine the name of the firefox script from the name of the currently running binary, which is /usr/lib/firefox-*/firefox-bin. It settles on /usr/lib/firefox-*/firefox. If this was a standalone firefox install (the binary tarballs you can download from mozilla.com), that would be correct. But our firefox script is in /usr/bin. So, you lose. > What's even wierder though is that when I change my preferred application in > System / Preferences some of the keys in gconf get set as expected and some > don't. For example, /desktop/gnome/url-handlers/http is being set properly > but /desktop/gnome/url-handlers/ftp isn't; it stayed set to the app it was > set to initially). Maybe I wasn't remembering that part correctly and the only issue is the above one. But you are you seeing the same issue where the command that's being set is /usr/lib/firefox-*/firefox and not /usr/bin/firefox? -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
