I've compiled firefox normally always while running X.. and I noticed how it changed the title bar everytime it started doing something different. I'm redoing a system of mine and it's not configured yet.. I want to get all the programs installed.. then do a massive configuration of all programs (as the configs won't affect installation) so I'm in Text-Mode as you may call it.. it's 11:30PM.. and it's beeping so much I want to scream. because I'm a light sleeper and I have school tomarrow :) if possible I'm sure there is a way to detect if your running it in an xterm like program or not.. can we somehow get it to stop?.. or maybe bug the mozilla devs to add in a compile option to stop the titlebar that you don't have from updating? Reproducible: Always Steps to Reproduce: 1. compile mozilla-firefox without X running 2. 3. Actual Results: *BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP**BEEP* Expected Results: *silence*.... then we can sleep :D
I too am beeping away here. This is the first time I compiled firefox outside of an xterm window. It is running on the normal console and beeping like crazy.
Quick tip.. shut off beeping on the Linux console: echo -ne '\033[11;0]' Additionally I just disabled xterm updates in mozconfig.eclass which is used by mozilla-1.7.3-r2, mozilla-firefox-1.0-r2 and mozilla-thunderbird-0.9-r2 so you should be all set. Please re-open if it's still a problem. Sorry for the annoyance.
It's still a problem. I want to re-open it but there's no option - the only radio button is "Leave as RESOLVED FIXED" for some reason. It annoyed the heck out of me while I was trying to re-install everything from a console and there are probably other people who just don't know what's going on and don't know that trick to turn off beeping until after they've installed it. Or maybe this has been fixed? I was emerging 1.0 since ACCEPT_KEYWORDS=x86 but the latest if I set it to ~x86 is 1.0-r3. I can't really understand from comment #2 what was the problem or whether/how it was fixed.
