[SOLVED?]Virtual terminal weirdness

Hello
After re-installing Arch I was rather surprised to find that I was unable to change virtual terminal while running X.
What I am meaning is that once X starts, I am unable to change virtual terminal with Ctrl + Alt F1 etc. I can go from VT-1 to VT-7 (which is running X) normally but once in VT-7, Ctrl + Alt F1 does not work.
I googled around and found a workaround - running the command "chvt 1" as root changes me to VT-1 just fine.
However, I would rather not have to run this command every time I want to change virtual terminal - Ctrl + Alt F1 much less fuss.
Does anyone know why this is happening and/or how to fix it?
I would be happy to post config files if needed - just tell me what you want
[edit]
It appears that the issue may have been something to do with the open source ATI graphics drivers - I set up Catalyst and was able to shift virtual terminals with Ctrl + Alt + F1. Wierd.
Many thanks to everyone who posted
Caillin
Last edited by Darkwind (2008-06-19 22:59:27)

randomguy wrote:Are you loading the right keyboardlayout for X ? Some keyboards have weird layouts so ctrl would actually be mapped on meta when used with default xkb settings.
I think so - I mean when I use other keyboard shortcuts (eg Ctrl+space to play or pause in Rhythmbox) it works fine. I'm using the UK generic 105 key PC layout according to GNOME's 'keyboard' menu so I'd think that would be pretty normal.
C

Similar Messages

Xorg 6.8 + virtual terminal no go [solved]

upgrading to xorg 6.8 and can switch to virtual terminal (ctl-alt+f not working) when xsession is open .
solution :
the problem related to srvrkeys:none for some reason in the xorg 6.8 the effect of this option is changed in few aspects.

upgrading to xorg 6.8 and can switch to virtual terminal (ctl-alt+f not working) when xsession is open .
solution :
the problem related to srvrkeys:none for some reason in the xorg 6.8 the effect of this option is changed in few aspects.

GNOME | Desktop artifacts when switching from a virtual terminal

When switching from a virtual terminal to the graphical environment I observe artifacts on the desktop. When then I change wallpapers, the artifacts disappear. If I set the display mode for the desktop wallpapers (in the GNOME tweak tool) as “None” the artifacts don't show up at all.
How can I tackle the problem?
GNOME 3.14.2; nvidia 304.125

You answered my expectation en tu previous post.
BBM Channels PIN: C0007093A
Do not forget to give LIKE Those people who help you and advise you about your doubts. if the review has been SOLVED** # 4LL #ÉliteRoad Make a backup of your BlackBerry
BlackBerry Protect and BlackBerry Link constantly. #ichooseBlackBerry10 Gutijose14 Forums Veteran I

Virtual terminal problems (konsole, lxterminal)

Hi,
I did not find the solution for my particular problem, where the virtual terminal can't connect to the bash execution.
I'm using arch linux including all repos [testing, community-testing], and after a update, I'm unable to run konsole or lxterminal. However, xterm does work. I'm using kde 4 enviorment.
Whenever I run konsole from xterm I get:
$ konsole
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
konsole(3236)/kdecore (KPty/K3Process) KPty::open: Can't open a pseudo teletype
konsole(3236) Konsole::Pty::flowControlEnabled: Unable to get flow control status, terminal not connected.
An konsole window appears, but no prompt or anything. If I do an ps -A | grep bash it gives an bash execution not connected anywhere:
3288 ? 00:00:00 bash
if I kill it, then this message appears on the konsole terminal:
Warning: Program '/bin/bash' crashed.
I did search for it before, and found out the topic Terminal not running, but my devpts and shm are mounted correctly.
mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=4082808k,nr_inodes=1020702,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda2 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
tmpfs on /tmp type tmpfs (rw)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
none on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sda1 on /Fedora type ext4 (rw,relatime,data=ordered)
/dev/sdb1 on /windows type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sdb2 on /data type ext4 (rw,relatime,data=ordered)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
Any clues?
Regards
Diogo

undeadb wrote:Mostly everything, was 4 months without a update. Got over 2GB of downloads. It did update kde.
Then I think the problem is related to the merging of all applications into "/usr/bin". "/bin/bash" kind of doesn't exist anymore.
Did you read the Arch Linux announcements before updating?
If you do think that's the problem, then I don't know what you can do to fix it. I'm not smart enough. I'd probably just reinstall the OS.

Why every virtual terminal always starts at root-dir, not ~

when i log in on a normal terminal ( ctrl-alt-f1 ~ ctrl-alt-f6), i'm in my home directory
but when i'm on a virtual terminal like gnome-terminal, i'm always in root directory, no matter it's a loggin shell or not
even including Gvim
thx
Last edited by treblih (2010-06-05 13:03:18)

You probably need to read http://www.catb.org/~esr/faqs/smart-questions.html
You need to describe in details what is you problem, how you start a terminal? You question dont make sense (where in the world is gvim a virtual terminal???)
Last edited by kazuo (2010-06-05 12:53:11)

[solved] connect to a virtual terminal

I want to start a console-based app (vim, ncmpc, irssi, etc.) in a new terminal (urxvt), how can I do this?
Here are some examples of things I'd like to be able to do:
- launch ncmpc in a new terminal at a given time every morning as an alarm clock
- launch irssi in a terminal every time I start X
If I summon an urxvt, is there a way of knowing which tty it's connected to (programmaticaly), and then is there a way of sending commands to that tty?
Last edited by peets (2007-11-25 15:44:53)

Moved to here.
urxvt -e <command> - it's in the man page.

[SOLVED] Cannot start a virtual terminal in KDE

Hi people,
I'm having an annoying issue with konsole : when started, the app starts, but it doesn't give me the prompt... All I have is a white cursor in the top left corner, and I can't type anything.
Switching to vc/1 using ctrl+alt+F1 works fine, and is fully usable.
I installed yakuake : same issue. I then installed gtkterm : same issue, but this time I get an error message :
Can not open /dev/ttyS0 : Permission not granted
Ain't ttyS0 the serial port ? Is there any chance that might be the problem ?
As suggested on the chakra forum, I checked permissions on :
* /bin/bash : root root 755
* /dev/tty1 : root root 777
On a maybe related note, I'm also having issues with kdesu : launching "kdesu kate" in krunner asks for root passwd, but then fails telling me "su" is not a recognized command. Similarly, I can only launch arxin, kuser, etc... as a regular user, giving the root passwd when required fails with that same error. I can use "su" when using vc/1, it works fine.
It looks like I've broken something bad, but I don't know what...Any idea, anyone ? I could go the easy way and reinstall, but I like to understand things...
Last edited by willy9 (2009-04-14 18:47:27)

Thanks for helping !
@jelly : yes, but I had the issue before. Can it be xorg related ?
@Chrysalis : yes but it is commented. Should I uncomment it ?
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
#none /dev/pts devpts defaults 0 0
#none /dev/shm tmpfs defaults 0 0
UUID=89336a04-983f-44ba-ba37-a869648b687f / ext3 defaults 0 0
UUID=6e5aca93-8b3f-4964-a7f2-47460e74d667 swap swap defaults 0 0
UUID=55daef78-db61-11dd-b2a0-2b699ceb5d02 /home ext3 defaults 0 0
/dev/sda1 /mnt/win ntfs users,umask=0,utf8 0 0

[SOLVED] TTY terminal font not displaying correctly

Solved, see Edit 2 for solution.
Begin original post:
Hi everyone,
When I login to any TTY console on my system (i.e. by pressing Ctrl+Alt+F2 and loging with my user name and password), the [user@hostname ~]$ is all gibberish; it looks something like this:
┌─[\[\e[31;1m\]\u@\[\e[32;1m\]\H\[\033[1;37m\]] \n\[\033[1;37m\]└─[\[\033[0;36m\]\w\[\033[1;37m\]]> \[\e[0m\]
Note: The user name and password prompts display correctly, as well as any commands that I enter (such as pacman -Syu), just the text preceding where I enter commands in messed up. Also, graphical terminal emulators such as xfce4-terminal do not have this issue.
I have researched this for a while, and I found a Post that outlines the same issue I am having. Unfortunately, the solution is for init.d and rc scripts, so it obviously will not work with Systemd.
Also, no other distro has this problem on my system, even a clean install of Arch works properly. This leads me to believe that a config file is messed up somewhere.
Does anybody know how to translate the above fix to a Systemd solution so I do not have to deal with wonky virtual consoles?
Thanks
-venividivici24
Edit: I just tried logging in as root, and it worked fine, everything was normal, so maybe it is some configuration file for my user specifically.
Edit 2: I fixed it. The problem happened to be in my ~/.profile config file. A while ago, I had bashish installed, but have since removed it. It left some settings in .profile that caused the console to act the way described above.
All I did to fix this was to change this:
# Termcap is outdated, old, and crusty, kill it.
unset TERMCAP
# Man is much better than us at figuring this out
unset MANPATH
BASHISHDIR="/usr/local/share/bashish" ## line added by bashish
TTY=`tty 2>/dev/null` && if test "x$BASHISHDIR" != x;then ## line added by bashish
test "$BASHISH_OLDPATH"||BASHISH_OLDPATH="$PATH" ## line added by bashish
PATH="$HOME/.bashish/launcher:$BASHISHDIR/lib:$BASHISH_OLDPATH" ## line added by bashish
BASHSISH_CP=437 ## line added by bashish
EST_TERM="$TERM" _bashish_utfcheck && BASHISH_CP=utf8 ## line added by bashish
ENV="$HOME/.profile" ## line added by bashish
export BASHISH_CP BASHISH_OLDPATH TTY ENV ## line added by bashish
. "$BASHISHDIR/main/prompt/sh/init" ## line added by bashish
fi ## line added by bashish
to this (I commented out the commands):
# Termcap is outdated, old, and crusty, kill it.
#unset TERMCAP
# Man is much better than us at figuring this out
#unset MANPATH
#BASHISHDIR="/usr/local/share/bashish" ## line added by bashish
#TTY=`tty 2>/dev/null` && if test "x$BASHISHDIR" != x;then ## line added by bashish
#test "$BASHISH_OLDPATH"||BASHISH_OLDPATH="$PATH" ## line added by bashish
#PATH="$HOME/.bashish/launcher:$BASHISHDIR/lib:$BASHISH_OLDPATH" ## line added by bashish
#BASHSISH_CP=437 ## line added by bashish
#EST_TERM="$TERM" _bashish_utfcheck && BASHISH_CP=utf8 ## line added by bashish
#ENV="$HOME/.profile" ## line added by bashish
#export BASHISH_CP BASHISH_OLDPATH TTY ENV ## line added by bashish
#. "$BASHISHDIR/main/prompt/sh/init" ## line added by bashish
#fi ## line added by bashish
I hope that this helps anyone who has this issue
Last edited by venividivici24 (2014-12-01 00:41:23)

It says:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
This is my bashrc, but I do not see anything in here that would warrant such odd behavior.
alias aurup='yaourt -Sua'
alias pacup='sudo pacman -Syu'
alias update='sudo pacman -Syu && yaourt -Sua'
export EDITOR="nano"
complete -cf sudo
Last edited by venividivici24 (2014-12-01 00:32:05)

[Solved] Virtual terminals/agetty overhanging screen.

I've got a strange problem on my Asus A6Jc lappy with nVidia 7300 Go card and 1280x800 screen. X/Gnome/KDE/Openbox/Whatever is fine and acts normally, but the virtual terminals (Ctrl-Alt-F[1-6]) are bigger than my physical screen (vertically). Not a problem to start with, and even if the terminal is used for more than a few commands, a 'clear' gets it usable again, but opening nano/vi/links chops off the last 4 or 5 lines of text.
I don't think I've done anything particularly strange in the config files, and I've not got the problem in other distros. vbeinfo and hwinfo --framebuffer both give the same results (aside from the +-512 to convert between linux and vesa modes) but these only include 320x240, 640x480, 800x600, and 1024x768 at various bit depths, with no mention of 1280x800. I've searched the forum and google, although, to be fair, I'm not sure of the best things to search for. My /etc/inittab looks sane, and agetty takes no size arguments anyway that I can see. The other thing I've noticed is that the grub terminal works correctly - ie, doesn't overhang, its only the linux virtual terminals. I'm not sure if the boot messages fall off the edge, since they go past too quick for me.
Any ideas where to look?
Last edited by mjc506 (2010-04-09 01:06:54)

On several laptops the kernel option vga=864 or vga=865 will select the widescreen resolution for the framebuffer. However 1280x800 is not an official VESA mode so these codes may or may not work depending on your laptop's manufacturer.
If you use grub to boot other distros that work correctly you might want to take a look at the config file and see what they use as kernel options.

[SOLVED] Arch terminal issues

Having some trouble with my terminal in Arch. I currently have Arch running with i3 and using Terminator emulating xterm. Everything is fine except something is causing the terminal instance to wrap the cursor way too earlier (before the end of the columns) and it wraps back to the start of the line rather than the beginning of a new line. I'm not sure how this would have happened or if there is some option to fix this. It works fine when I have no seperate tiles, adding vertical tiles causes the weird word wrap but horizontal tiling doesn't affect it. It's almost like its trying to programmatically figure out the word wrap point but gets halved with you add vertical tiles
Thanks for any help!
Last edited by mihok (2013-01-29 14:27:04)

Thanks for the direction.
PS1="\[\e[00;31m\][- \[\e[107;34m\]\u@\h\[\e[00;31m\]- ]
|-\[\e[107;31m\] in [* \W * ]\[\e[00;31m\]-|-->\[\e[00m\]"
[- joe@Tux-Box- ]
|- in [* Tunes * ]-|-->

[SOLVED] Virtual Box Kernel Bug?

I'm using virtualbox_bin 3.2.8-5 from the AUR & kernel26 2.6.35.6-1.
I boot the machine clean. It starts the bare essentials. I open a terminal, /etc/rc.d/vboxdrv setup && modprobe vboxdrv. It is not vboxdrv that is the issue, but I'll recompile it anyway to make sure.
I start VirtualBox and it either:
A) Locks up the entire system
B) Gives me some error that says Component: ProgressProxy, Interface: IProgress
C) Force reboots my PC
Only other things in in the /var/log/errors.log besides this:
Sep 29 15:54:51 localhost kernel: BUG: scheduling while atomic: VBoxXPCOMIPCD/5464/0x00000003
Sep 29 15:54:52 localhost kernel: BUG: scheduling while atomic: VirtualBox/5541/0x00000002
Sep 29 15:54:52 localhost kernel: BUG: scheduling while atomic: pidgin/5808/0x00000002
Sep 29 15:55:08 localhost kernel: BUG: scheduling while atomic: bash/5566/0x00000002
Sep 29 15:55:21 localhost kernel: BUG: scheduling while atomic: X/4067/0x00000002
is "Assuming drive cache: write through" warnings.
Not sure if this should be in the kernel section or not.
Last edited by Jimi (2010-09-29 22:11:11)

Thanks for the very quick response.
I didn't realize I wasn't running the latest. Internet's been going in and out frequently. Once I've confirmed this is it (after yaourt finished upgrading everything), I'll change the title to solved.
Last edited by Jimi (2010-09-29 20:43:13)

[Solved] Firefox looks weird after Upgrade

Hello (sorry for my poor english)
After update, firefox looks weird and like a "root-application" without gtk integration:
Gtk-WARNING **: libpng14.so.14: cannot open shared object file: No such file or directory
And...
[***@***** ~]$ pacman -Qm
adobe-air 2.1-1
adobe-air-sdk 2.6-1
aironux 1.7-1
arch-artwork 0.2.1-6
beclock 0.16-1
befaded 0.4a-1
bug-buddy 2.32.0-1
chakra-gtk-config 1.7-1
chromium-libpdf LATEST-5
clipgrab 3.1.3.0-2
dee 1.0.0-1
droid-plasmatheme 0.1-1
emesene-supported-themes 20111008-1
evolution-webcal 2.32.0-1
exaile 0.3.2.2-3
faelementary-icon-theme 0.10-1
faenza-icon-theme 1.2-2
faience-icon-theme 0.3-1
flashplugin-beta 11.2.202.197-1
gen-init-cpio 2.6.36-1
gimp-fourier 0.4.1-1
gimp-paint-studio 1.5_final-1
gimp-photoshop-pattern 1.0-1
gimp-plugin-layerfx 0.1-1
gimp-resynth-heal-selection 0.16-4
gimp-ultimate-web-gradients 1-1
gimpfx-foundry 2.6_1-2
gnome-mag 0.16.3-1
gnome-shell-theme-elementary 3.2-1
gnome-shell-theme-fainece 1-1
gnome-shell-theme-gaia 20111026-1
gnome-shell-theme-google 1.5.1-3
gnome-shell-theme-nord 20111101-3
gnome-shell-theme-sugar 1.0-1
gnome-theme-vizard 20110919-1
gok 2.30.1-1
gradiator 12.01.5-1
gsharkdown 0.5.9-1
gtk-engine-murrine-git 20110711-1
gtk-engine-unico 1.0.1-2
gtk-theme-hope 20120109-2
gtkspell3 2.0.16-4
gwget 1.0.4-3
gwibber 3.2.1-4
hal 0.5.14-7
hal-info 0.20091130-1
isotostick 0.1-3
jclic 0.2.1.0-1
jdk 7-3
jogl 1.1.1-7
jre 7-3
kcm-qt-graphicssystem 1.3-1
kdepim-wizards 4.7.4-1
kdevplatform-git 20110830-1
kdm-theme-caledonia 0.9-1
kfaenza-icon-theme 0.8.9-1
kmozillahelper 0.6.3-2
ksplash-caledonia 0.9-1
lib32-nspr 4.8.9-1
lib32-nss 3.12.11-1
libreoffice-faenza-mod 0.4-4
lyrics-plasmoid 0.5-1
minitube 1.7-1
mint-z-theme 1.1.4-1
mozplugger 1.14.4-1
oxygen-gtk-git 20111112-1
oxygen-gtk3-git 20111015-1
oxygen-molecule-theme 3.2-1
oxygenrefit2-icon-theme 2.5.0-2
packer 20111022-1
partitionmanager-svn 1257912-1
pinta 1.1-1
plasma-icontasks 0.9.2-1
plasma-theme-caledonia 0.9.8-1
plasma-theme-fragile 1.4-1
plasma-theme-fushigi 0.4.2-1
plasma-theme-kneda 0.6.4-2
pmidi 1.6.0-3
pylast 0.5.4-2
quanta-git 20110830-1
quickaccess-plasmoid 0.8.2-2
rar 4.1.0-1
rmlint 1.0.8-1
runescape-client-bin 2:1.2-1
silc-toolkit 1.1.10-1
supertuxkart-addons 0.7-6
tcp_wrappers 7.6-15
ttf-ms-fonts 2.0-9
ultimate-gnome-icon-theme 0.5.1-1
unetbootin-git 20111229-1
usb-creator 0.2.34-2
x-get 0.3-3
xampp 1.7.7-1
What is the package in conflict?
Last edited by Mistery159 (2012-02-06 05:29:20)

jasonwryan wrote:
What about these?
gtk-engine-murrine-git 20110711-1
gtk-engine-unico 1.0.1-2
gtk-theme-hope 20120109-2
I upgrade again gtk-engine-unico and that solved the problem. Thanks.

[solved] xfce4-terminal spam after update to util-linux 2.25-3

I use the setterm command inside a file in /etc/profile.d so that I can prevent the screen from blanking when using a console, along with a couple of other things.
After the latest update to util-linux (2.25-3), whenever I open xfce4-terminal these lines show up:
setterm: terminal xterm does not support --blength
setterm: terminal xterm does not support --bfreq
setterm: terminal xterm does not support --blank
[gilmoreja@JamesPC ~]$
Is there a better way to handle making sure setterm runs when a console is used, but not necessarily when a terminal is opened? Or is there some other way to solve this issue? There doesn't seem to be a switch for setterm for any kind of "quiet mode."
Last edited by gilmoreja (2014-08-06 18:36:28)

I think that the shell started in a console is a login shell, and it is not the case in a graphical terminal.
A login shell has a '-' at the start of $0; so you can test that and condition the execution of the setterm commands:
if [[ $0 == '-bash' ]]; then
setterm ...
setterm ...
fi

[Solved] My terminal environment is messed up

I have several terminal / virtual console related problems bugging me.
1) I cannot delete certain characters/typos and be sure they are gone. For example, if I have a variable VAR and I accidentally type
$ echo $äVAR
$äVAR
Then I delete the accidental character "ä" (move the cursor on it and press delete and enter). I get:
$ echo $VAR
$ÃVAR
When I press up to see the previous commands these remaining wrong characters are displayed, but not so whenever I'm correcting my typos.
This happens specifically with umlauts. Common characters get deleted properly.
2) I'm trying to build LFS. The manual (http://www.linuxfromscratch.org/lfs/vie … nment.html) says that the line
"exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash" in ~/.bash_profile
replaces the running shell with a new one with a completely empty environment, except for the HOME, TERM, and PS1 variables.
I can't get this to happen, no matter which way I try to login. Not even executing the line manually changes a thing. My PS1 is still what is set in /etc/profile, not what the exec env line says. And several other variables are still present, like PS{2,3,4}.
I guess I don't understand something very critical about this. The way I see it, the quote above says PS2 should not be set. What am I doing wrong / what am I not getting?
3) Bash (in a terminal window under X) doesn't wrap long lines properly. If I press up to see lines in ~/.bash_history, sufficiently long lines get garbled up. For example the configure command here spans several lines. The last two are okay, but when moving to the beginning of the command, the words begin to overlap and I can't make any sense out of them.
This happens both in xterm and urxvt. In urxvt $TERM is "rxvt", in xterm just "xterm".
To my knowledge I have no funny configs in any related places. I haven't touched /etc/profile or /etc/bash.bashrc.
My LFS-building user has its environment set up exactly as in here:
http://www.linuxfromscratch.org/lfs/vie … nment.html
But these problems still occur.
Last edited by SternGerlachExperiment (2012-04-15 20:49:16)

I'll have to see how rebooting affects the behaviour in Konsole.
cfr wrote:
$ printenv | grep LC
LC_ALL=C
Should I set it to something else? LOCALE seems not to be set in my environment at all, although it is set in /etc/rc.conf:
LOCALE="en_GB.UTF-8"
DAEMON_LOCALE="no"
but:
$ printenv | grep LOC
returns nothing.
I would by preference set LOCALE (and LC_ALL?) to cy_GB.UTF-8 but I'm worried about doing that...
I think that LC_ALL is set as it is because I had problems running python programmes with it set to something local. (Hence the worry.)
Do you have locale settings in ~/.bashrc or .bash_profile or .profile?
LC_ALL=POSIX is the same thing as LC_ALL=C, so you could try setting
LOCALE="cy_GB.UTF-8" in rc.conf and then have
export LC_MESSAGES = C
in .bashrc and .profile, and see what effect this has on your Python programs. Or you could just set LOCALE in rc.conf and start the problematic Python programs with
$ LANG=C NameOfThePythonProgram
I wonder why it doesn't work for you in konsole, either.
EDIT: I have the problem in both LilyTerm and xterm as well. I don't usually use these and they are not really configured but bash is bash is bash... right?
How about urxvt?
Last edited by SternGerlachExperiment (2012-04-15 12:55:24)

[SOLVED] virtual box (vboxdrv: not loaded)

I have installed virtualbox
pacman -S virtualbox_bin
and installed virtualbox_bin 3.0.0-2
/etc/rc.d/vboxdrv not found
When I run virtual box, it says vboxdrv is not loaded
what to do
Last edited by sant527 (2009-07-10 06:33:36)

For reference..
pacman -Ql packageName shows what files a package contains.
You might add | grep bin or something of the sort after it to find the binaries quickly (sometimes.. some files contain 'bin' in the title or a folder name, obviously)
that question has been asked many times before. please learn to use Pacman, the Forum (and corresponding Search functions), and the Wiki before asking questions, and edit your first post to append [SOLVED] to the title when you find an appropriate answer to your questions.. it will save those of us looking to help time and frustration if you do all of that. thanks.
Last edited by FrozenFox (2009-07-06 09:26:17)

[SOLVED?]Virtual terminal weirdness

Similar Messages

Maybe you are looking for