Search options (Page 1 of 3)

Well....pulseaudio.  Start advertising Crunchbang on Ubuntu and Fedora forums as "One of the few that doesn't use pulseaudio" and the problem is, it will probably crash the server with folks trying to download it.

Pulse audio, as the developer complained--his complaint was that people were saying this---is a solution in search of a problem. Aside from breaking Skype for awhile, breaking sound for many, being a general nuisance, and showing no improvement over previous alsa sound, I can't think of a reason to ban it. 

Reasons against banning it---avoiding previously mentioned overload on servers.

Ok, I just tried this on CentOS, and this is what I found.  Using LC_CTYPE=en_US, I could not get it to work.  (I didn't even get anthy to open).

When I tried export LC_CTYPE=ja_JP.UTF8 , that worked.

So, in a terminal try.
echo $XMODIFIERS

It should come back @im=SCIM

If it doesn't then

export XMODIFIERS='@im=SCIM'

export LC_CTYPE=ja_JP.UTF-8

export GTK_IM_MODULE="scim"

after you've typed all that, in the same terminal, type something like uxterm, which will open up another terminal.  The reason we're doing this is to make sure that the values of these variables were properly exported.  In that second terminal, do a check

echo $XMODIFIERS $LC_CTYPE $GTK_IM_MODULE

If they come out correctly, we're good.

Now in that second terminal try typing

abiword

Abiword will open, and this may fix the issue.

@Tooolz--.bash_profile is read once, when you log in, .bashrc is read each time you open a shell.  Therefore, in theory, it saves resources to put things you *should* only need to be read once in .bash_profile, as in .bashrc, it has to be read and acted upon each time you open a terminal.

@Awebb, I'm not sure.  I would try, after logging in, running

source .bash_profile

and seeing if it fixes it.  As #! is Ubuntu based, and therefore has too many system thingies tied into the GUI, it's probably some kind of weirdness inherited from Gnome.  It's one reason I much prefer starting in runlevel 3--my main distro is Fedora (which I have to use at work) and I find that doing this helps me avoid many things that others find to be common problems.

And thank you for clarifying as well, I didn't realize what you meant.   

Sigh, I've really got to go to sleep (almost midnight here) so I hope my answer will be understandable. 

I think if you do, from a terminal

XMODIFIERS='@im=SCIM' LC_CTYPE=en_US.UTF-8 GTK_IM_MODULE="scim" firefox

that it will probably work. If that doesn't work, try changing en_US.UTF-8 (assuming that's your usual language, of course) to ja_JP.UTF-8

I'll give more of an explanation tomorrow (though probably not till the evening).  Just a really brief explanation---often all you need to do is set XMODIFIERS and LC_CTYPE.  I've found this to vary with distribution (and OS, e.g., the BSDs) and the application.  For example, Firefox is a GTK app so it will probably work with *either* ja_JP.UTF-8 OR GTK_IM_MODULE.  However, sometimes, it needs both.  I'm writing this from CentOS, so can't do a hands on test at this instant.

Ah thank you.  To be honest, I usually use fluxbox, so hadn't realized that.

The Locale warning sometimes has to do with using utf8 rather than UTF-8.  You might even want to do something like dpkg-reconfigure locales and make sure you have the necessary ones.  (I hope I have the command right, I'm in CentOS as I type this, so can't check.) 

Also do locale -a |grep ja_JP and see how they list it, if it's UTF-8, utf8 or whatever.  If the dpkg-reconfigure locales (locale?  Again, can't check at this instant) doesn't fix it, sometimes playing with the case and hypenation of utf-8 will fix it.

Also, it will sometimes work, even if you get that message.  (And sometimes, it won't).

It seems the only moderately active fluxbox based one is antiX, based on Mepis.  Not quite as convenient as #!, as for one, it doesn't easily boot from a USB drive, there's something in there complaining about no CD.

(It can be done, but I've forgotten the procedure.)

Even that isn't all that active.  There was a release in August and there's been another beta out since December 20th.

Though I prefer fluxbox to openbox,  #! is quicker to install and configure (for me) though I like the default antiX background.  (Trees and such, very nice.)  (That's not an effort to start a war over the two *boxes, they're both great window managers, it's simply my own personal taste, and no doubt, years of habit.) 

Fluxbuntu has seemed relatively inactive.  Fluxbox version of Mint also exists, but always seems a bit behind. 

No offense meant to any of them, just #! comes a bit closer to my personal tastes, plus it's quick to install.

@nik_doof, I know that some people have issues with ath5k.  (I haven't been one of them, however.)  I wasn't sure this version of #!Crunchbang would include it because the newer EEE's no longer use the AR5007EG.

Heh, well, to a dinosaur like myself, it was much better than alsa.   The BSDs still make use of it, and although I haven't followed it that closely, I believe that on both Ubuntu and Fedora forums, some folks have found it necessary for some things (but I don't remember the specifics and could easily be wrong on that.)

At any rate, it's what was there before someone decided alsa was a good solution.  From the coding/developer end, I have no idea, but along with the BSD crowd, I always considered alsa a regression.    Pulseaudio is even more of one. 

What I admire most about the fellow is that he went on IRC and took the abuse to get the information.  Their (the dwm people) whole thing about remaining elitest and keeping clueless newbies away, does make one wonder if the program was written by 12 year olds.   

Actually, I think it was Einstein who said something to the effect of, "If you can't explain it simply, you don't understand it well enough."

Here's one for ya.  In CentOS 5.2, with opera beta 10 and FF3. 
I go to the Linksys site.  If I go to choose the time, the drop down box won't work properly in opera.  I have to use firefox.

However, once I'm at the item, if, for example, I want to download firmware, *that* won't work in firefox.  Instead, I have to copy the url and open it in opera to download.

As has been said, some sites are better with one, others with the other. As FF is so popular, many developers make sure that their site works with it.

With opera, its more standards compliant, so I've heard.  (As in, "I saw it somewhere on the Internet, it MUST be true.")  Regardless, it seems to have trouble with more sites than does FF.

I think much of it is a matter of personal taste.