Ubuntu :: Can't Turn On Terminal Bell In Gnome-terminal Using Remote Screen Session With Irssi
Nov 6, 2010
I'm using 10.04, and gnome-terminal GNOME Terminal 2.30.2 . I have irssi running on screen session on remote host. And I've been struggling for quite many days to configure it to produce either visual feedback or ring terminal's bell when I receive a private message or one of those that are highlighted.
My compiz settings window in General tab has 'Audible bell' checked.
My GNOME terminal has 'Terminal bell' checked.
I also added 'set bell-style audible' to my ~/.inputrc
And I also tried to manually load pcspkr module into my kernel.
No of the above helped or at least I haven't been able to notice any difference.
I also used some commands for irssi to produce bell sign.
I've been trying to get this working for a while. On a remote server I'm running irssi in a screen session to keep my IRC client connected 24/7. I SSH to that server and reattach the screen session. irssi is able to send alerts when certain highlight words are mentioned (e.g. my nick). I would like gnome-terminal to flash in the taskbar when that happens. I was able to get this working with Putty on Windows, but I can't figure out how to get that working with gnome-terminal. Is it at all possible? The "Terminal bell" setting in the gnome-terminal profile doesn't seem to change anything.
I recently replaced (fresh install) Fedora 12 by 13. Surprisingly I noticed there is no log-in sound for Gnome and also when I use command line terminal there is no terminal bell in spite of the fact that I checked the "Terminal Bell" option in the EDIT --> Preferences menu! I checked the speakers are not mute, I can play music. Any idea how to fix it?
I'm running GNOME (gnome-session under xmonad). I want to turn off antialiasing (i.e. use monochrome mode) for fonts in gnome-terminal. But I want to retain antialiasing for other applications, like Firefox. Is this possible?
Antialiasing is great and almost necessary for using Firefox or Chrome. But it makes the fonts in gnome-terminal blurry at sizes around 12 or smaller.
Otherwise, I'll just have to use xterm, which seems not to anti-alias its fonts under any circumstances.
There are often times when the best way to launch an application is from the terminal, but it is a graphical application and after it is launched the terminal is useless.
Examples of places where a terminal is convenient are when a process starts lots of child processes and is also unstable; you can be sure to kill all of its children simply by using Ctrl-C at the terminal. Also it allows me to read program output and to set up the terminal environment to be optimal for the application (for example "unset LIBGL_ALWAYS_INDIRECT")
With GNU screen, I can get around the hassle of having a terminal window open by using something like the following in a terminal window:
Code: screen my_command Ctrl-A d
and then I can close the terminal and the program will keep running. Then I just type "screen -r <Tab>" (the tab will get me my screen session if there is only one such session) in any terminal window, even a tty, and I can get the screen session back and use Ctrl-c or something.
So my question is, is there a way to do this automatically so that a launcher or script will start a screen session, inside that screen session start a process, and then detach from that screen session without me having to manually open and close a terminal and type the commands?
I've recently installed Xubuntu Lucid Beta2 on my new laptop. But I'm unable to turn the bell back on. The 'pcspkr'-module is removed from the blacklist and is loaded. However, 'alsamixer' doesn't show me any volume-options for the beep. However, 'echo -e "a"' still doesn't make a sound. I've installed the 'beep'-package, and it works, thus I am assuming that the hardware-bell itself does WORK fine. It's just deactivated/muted somewhere, and I can't find the option to turn it back on.
I looked around for threads addressing this issue and some have come close to answering it, but I have yet to see a definitive yes or no. Anyway - Here's my issue:
Background: I can SSH into my home computer (Ubuntu 9.04 running Gnome) from work (Win XP Pro) using RealVNC via Putty tunnels. This has been working flawlessly for me for awhile now. I was messing around in the terminal window and accidentally rebooted the linux box (home computer) while I was at work. No big deal I thought. So I re-start the Putty connection, and it is back up in no time. Then I try to start the VNC connection, and no go, connection refused. I remember seeing that in order for the VNC connection to work, I had to be logged into the Gnome desktop already on the Ubuntu box.
Question: Is it possible to log in and start up a Gnome desktop session from the terminal command line in Putty so I can get the VNC connection back?
Is there one command that will let me record an entire terminal session (with any possible errors) to a text file while also seeing all output on screen too? I know it can be done for individual commands, but I'm looking to do this for an entire session where the individual commands will be normal (i.e., not piped into tee, etc.). It would be even better if the command prompt is captured too. The obvious utility of this makes me think someone surely has come up with a solution long ago (probably in the 60's).(I'm sure it goes without saying, but subsequent output in that session should be appended to the file. The file should contain the full history, with all output and errors, of the session.)
How do you change the volume of the terminal alert bell in F11? (the sound you hear when you press the tab button). I turned the sound all the way down and muted the "Alert volume" in System>Pref>Sound but I still get a deafening bell sound whenever I press the tab button.
how to get the terminal displayed on my serverbox to show up in a terminal on my laptop. I have a minecraft server running on ubuntu server edition 10.04 on a headless server. I also have a monitor, but it's a big bulky CRT and my girlfriend doesn't like having a huge amount of stuff tucked behind our chair where the router is (wifi wasn't working right, nor is it stable).
Essentially, when I ssh into the box, it creates a new terminal for me to input things on. That's nice when I need to edit stuff in the background, but when I want to input commands on the server directly, there's no real way to do that without blindly typing on my keyboard on the box itself. Not to mention, I can't see anything if something goes wrong. A friend of mine mentioned the 'screen' command, and that sort of works I guess, but it still doesn't show the minecraft server output, nor let me input.
tl:dr;
is there a way to get a physical terminal output to display on a remote ssh terminal screen?
Linux-goers. I did some research on this, but I am still fairly new to Linux. In Ubuntu 10.10 (Maverick), I accidentally overwrote my "/bin/bash" file. Dude, using "sudo" with a small typo can work disasters. Bash is now broken in the Terminal (gnome-terminal). Terminal itself still works fine, technically, but bash is still hosed/broken. Here is what I did to try to fix it: Booted from Ubuntu 10.10 live CD. Mounted my Ubuntu partition and manually copied the good/fresh "bash" file onto my hard drive. Verified copy was successful. Didn't help, as you see. Reinstalled "gnome-terminal" using synaptic package manager. Tried to reinstall bash via synaptic, it failed with error, "E: /var/cache/apt/archives/bash_4.1-2ubuntu4_i386.deb: subprocess new pre-removal script returned error exit status 2"
In Terminal, all basic commands work as far as I can tell. ("ls", "pwd", navigation, etc.) Here are some problems:My "username@computername" does not display in the prompt; only the $ sign. Bash keyboard shortcuts such as uparrow and tab do not work. Instead, each inserts a key code. I can't even move the cursor left/right. Aliases (a function of bash and .bashrc) are broken, of course. My sanity level decreases when I use Terminal now. For what it's worth, even with "sudo" I get a "permission denied" error when trying to run Google Chrome! I read something about a ".bashrc" file being a possible problem, but I don't know how to make it work, or the file's proper locations in Ubuntu 10.10. Is there something I can do with a "make" or "apt-get install" command or something?? Could this simply be a permissions problem? Is the link to "/bin/bash", "/bin/sh", or a ".bashrc" file broken? Guide me, oh Linux gurus.
P.S. I always wondered what exactly bash was and how it was different from the basic terminal. LoL, this is an excellent way to demonstrate the difference, and I WANT IT BACK!
gnome-terminal from the Debian squeeze does not use the 'default_size_columns' and 'default_size_rows' from the /apps/gnome-terminal/profiles/Default/ folder of gconf.
Is there a terminal emulator which works well in an Ubuntu desktop and provides the following features which Mac OS X's Terminal application has? Re-wrapping text when the window is resized.A Clear command which clears scrollback (as the shell clear does not) and does not clear the cursor's line (typically containing a prompt).
Are x-terminal-emulator and gnome-terminal different in any way? I noticed when I when I put those commands in my terminal they both opened the gnome-terminal.
I find xcompmgr more than adequate for making a desktop look pretty modern, and I don't like the more extravagentCompiz gimmicks - but there is one thing that irritates when using xcompmgr which someone here might have worked round.
Rounded window borders don't draw and redraw properly when using the Terminal (gnome-terminal and the LXDE and Xfce ones) or system monitor and moving them from their default place. You get this little white botch at the corners. I'm not massively technical and I'm ambivalent about how much more I want to learn as I have plenty of creative outlets already, but I would like to solve this. Somehow xcompmgr is treating these programs as a different class? It's capable of drawing the window borders properly as it is just these two programs that get botched. Possibly this doesn't get noticed as maybe people usually use xcompmgr with openbox and LXDE and their square window borders. I did do a search but there was nothing matching what I saw.
I have a favorite REXX program called fv2. When I was a Windows user I had an icon for fv2 on the Quick Launch bar. Click that icon, and the program ran. Now, as a Linux (Ubuntu) user it is necessary to go through several steps to run fv2.
1) Launch a terminal by clicking on the terminal icon at the top of the screen. What's that area called? The GNOME panel? 2) Enter: ~/Desktop/RexxScripts 3) Enter: regina fv2
I run fv2 several times per day and would really like to have the convenience of a clickable icon.
How can I make terminal applications immune to terminal emulator close, but still able to use all virtual terminal features?
egin{UPDATE}I want my terminal application remain alive and accessible if I accidentally close terminal emulator. This functionality is provided by screen and tmux, but they have issues with colors and they flush screen.Yes,I can run the shell inside screen, but I do not want the shell remain alive unless there is some other program running.
end{UPDATE}I see this must be something like screen, but without VT100 terminal emulation, something which will just apply whatever application does with "terminal proxy"'s terminal (like outputting something to stdout/stderr or using stty to set terminal options) to the terminal this proxy runs in.
// I know about screen and altscreen on, but it makes either this (screen with TERM=screen):
or this (screen with TERM=rxvt-unicode):
while I want this (rxvt-unicode without screen):
I have figured out that everything looks fine if I compile rxvt-unicode with USE=-xterm-color (in fact vim looks like on the second picture even without screen if I add this USE flag) and set TERM=screen-256color, but I do not like this workaround because it actually changes colors and I can't be sure that it will always change them only this way:
i have installed Ubuntu 10.10 and played around a bit and have got it booting into cli instead of the login screen. gnome is my default desktop environment but i wish to run kde along side to play around with. When i boot into kde using startx kde (usualy just using startx) all i get is a mouse, black background and a terminal screen.
When it launches, sometimes a few mins later, the upper left of the screen (where gnome-terminal sits) freezes and becomes unresponsive. The cursor always stays as the 'text entry' cursor when in the region. If I alt-drag the window and close, nothing changes.It only goes away when I right click the area (even if I have moved/closed the terminal window) I have terminal options so I select 'close' then the screen resumes.
I need to close my session but the exit button is no longer here. I can restart the computer (ctrl+alt_del), but not only the session. I opened a session with the gnome desktop but everytime is messed up and I want to come back to the UNE desktop. How can I do that from a terminal?
I'm running ubuntu 9.10 on a Dell XPS M1530. Sometimes i get a _VERY_ loud beep-sound, eg when i run out of battery or, the case that has me coming here when i'm working in a virtual terminal (tty1-6) and hit backspace once too often, that is, when the command line is actually empty.Not that big of a deal you might think, but, especially when you're wearing good (read: possibly loud) headphones the experience is that god damn unpleasant that i'd like to make sure it won't happen again.Oh and well, just hitting mute (in gnome, which doesn't have a lot to do with tty1 anyways) won't do the job.
I was tweakng the desktop effects in kubuntu and adjusted the stiffness slidder to max out wabbly windows so I could compare it to more stiffer option. It is only supposed to wobble when the window is moved but as soon as I hit the apply button the window started wobbling all over the place! So fast, that I can barely tell what window it is! It is impossible for me to open any windows without them flickering all over the place. I will not be able to fix this inside KDE.
Does anyone know of a command-line option to turn desktop effects off? Is there a desktop configuration file somewere I can edit w/ nano? I am having to write this on windows7 because I can't use any windows in linux.
I'm using a low spec machine and want to run it 'headless', so I don't need a GUI and want to conserve resources.How do I boot straight into a terminal session, rather than a GUI?
I have a server that has the mobile broadband connection "ppp0" is there a way to turn it on and off via terminal,Ifconfig shows connections for eth0 and l0 not ppp0 till it is connected.
This is for all of you who are having problems getting sound out of the PC Speaker, as far as getting the system beep or system bell. In Karmic (9.10), a change was made to get rid of the system beeps and disable the pc speaker. Unfortunately for people who liked (or more likely need) the beeps, the changes occurred in multiple places and are not that easy to find. The pc speaker and beeps were disabled in response to this bug. I believe there were other bugs dealt with here because not everything that was done seems to be covered, if that makes sense.
This bug was created in response, in hope of getting the beeps turned back on. This post by one of the developers has some pretty comprehensive instructions for getting the beep back on. I want to note right now, that I did not have to apply his patch to get the beeps back on where I wanted them. It may already have been included in an update, or was obviated by something else I did. I realize this is pretty fragmented, and you may or may not want or need to go as far as I did with this. When I get a chance to do a new clean install of Karmic (maybe in a vm or something) I intend to go back over these instructions and try to create a synthesis of them that should work for certain. If I can, I'll figure out a way to script it.
One other thing I should point out. I didn't get the bug where I had to reload the pcspkr module on every boot, so that must be fixed. (I did have to remove it from the blacklist so it would be loaded on boot, but I didn't have to kill and reload it or add it to rc.local like some people did in those descriptions). I also did not get the bug of an endless loop of beep sound or multiple beep sounds, but that only happened to people who followed the directions to change the system beep to another sound.
I'm trying to create a new gdm session in tty8, so I can switch between tty7 and tty8 running simultaneously.
How can I accomplish this? I found some website suggesting to run startx and also startx gnome-session -- :1 vt8 Both result in a black screen, blocking the overall system, not allowing me to go to tty1 nor any tty. I have to run REINSUB to restart the system.
# I don't know if tty is the exact term to refer to the CTRL+ALT+Fx virtual terminals.
I'm trying to turn on the system bell (pc speaker) in xterm. I have the bell working in console (text mode, not under X), and with X running, even firefox can use the pc speaker (it beeps, when I enter a search term which is not found). Only xterm doesn't seem to work.
Here is my xterm config, and the xset command I'm trying to use to turn the bell on: -------###-------- xterm*renderFont: true xterm*faceName: Terminus xterm*faceSize: 12
xterm*background: black xterm*foreground: white !xterm*highlightColor: red xterm*charClass: 46-47:48
xterm*visualBell: false -------###-------- xset b on xset bell 100 1000 1000 -------###--------
If I run xterm with the +vb option, it doesn't help either (I'm testing it with printf "a"). What am I missing? How can I make xterm use my pc speaker as bell?
when i did that, I turned it back on, and well I had this huge huge problem, i've made a few threads about it. So I had to go through a manual FSCK. I did all that and I do have the cd, although when I try to boot off of the live cd, it gives me a bunch of buffer errors, I have a thread or two about that problem too. So i can't boot off a live cd and fix it through that.
Now i've gotton to the point where I can get to the login screen, it looks normal and everything but when I log into a normal session it greets me with this Your session only lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of diskspace. Try logging in with one of the failsafe sessions to see if you can fix this problem. View details (~/.xsession-errors file)
Code: /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=en_US. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. mkdtemp: private socket dir: Permission denied
So i have no idea what that all means but i did understand failsafe terminal. So when I go to the failsafe terminal to try and fix things, I'm completely lost. I don't know what to type at all. I'm a windows user most of the time.
