Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
03-13-2006, 02:08 PM
|
#1
|
Member
Registered: Aug 2005
Location: Bay
Distribution: Zenwalk, OpenBSD, Slackware
Posts: 167
Rep:
|
DEL key prints '~' after update
So I updated bash to the latest under Slack current. One obvious upgrade was the new colors that showed for certain files/dirs with special permissions. But another was a problem: the Delete key now prints a '~' character and does not DEL like it's supposed to.
Anyone know what's going on?
|
|
|
03-13-2006, 03:33 PM
|
#2
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
I don't have that problem in Slackware-current.
Did you just upgrade the bash package of Slackware-current on an older release of Slackware, or did you also install/upgrade all the rest of Slackware-current? The first is a definite road to disaster.
Eric
|
|
|
03-13-2006, 09:35 PM
|
#3
|
Member
Registered: Aug 2005
Location: Bay
Distribution: Zenwalk, OpenBSD, Slackware
Posts: 167
Original Poster
Rep:
|
I use slackpkg to upgrade the entire distribution (at least the packages I installed), originally 10.2 and I track current continuously.
Unless Pat added a package that isn't updated automatically from 10.2, or a config file is misconfigured ... anyone have any ideas?
|
|
|
03-13-2006, 09:52 PM
|
#4
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
Just one of many reasons why 'only upgrading what I have' is a road to this forum's favorite question "I upgraded foo, and faa stopped working"
You cannot.....REPEAT CANNOT 'upgrade' just one or two packages to 'current' without getting ALOT of errors. So many packages need so many other programs that you are asking for trouble.Your old Slackware system may not even HAVE the 'other programs' that a 'upgraded package' requires.
If I do a fresh install, then 'current' is fine.
Just do one thing before you allow another 'upgrade'....Do a search on this forum of the single word 'upgrade'....Then try it.
|
|
|
03-13-2006, 10:05 PM
|
#5
|
Member
Registered: Aug 2005
Location: Bay
Distribution: Zenwalk, OpenBSD, Slackware
Posts: 167
Original Poster
Rep:
|
Thanks for nothing.
Anyone else have any ideas as far as bash goes?
|
|
|
03-13-2006, 10:12 PM
|
#6
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
Quote:
Originally Posted by sweetnsourbkr
Thanks for nothing.
|
Nothing? If you would have done what I suggested BEFORE you 'upgraded' willy-nilly, you would not be in this situation. I was just trying to save you even more grief later.
The simple fix is to remap your keyboard. Search the forum for in-depth discussions on how to do so.
The harder way is to keep the attitude going.
Either way, my 'Del' works.
Last edited by cwwilson721; 03-13-2006 at 10:15 PM.
|
|
|
03-13-2006, 10:16 PM
|
#7
|
Member
Registered: Aug 2005
Location: Bay
Distribution: Zenwalk, OpenBSD, Slackware
Posts: 167
Original Poster
Rep:
|
Hey, all you had to say was that. No need for the flame. If you have nothing constructive to say initially, just don't say it bro. Stick to the topic, plz.
|
|
|
03-14-2006, 02:56 AM
|
#8
|
Senior Member
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247
Rep:
|
What installation do you have? If full, than take for example slapt-get and upgrade all the packages (not alsa, headers, etc..) with the current release of Slackware. If you prefer the manual way, go to ftp://ftp.slackware.com/pub/slackwar...t/PACKAGES.TXT, run pkgtool and check if you have the same packages installed, which are listed there. If not, try to think if it is required by bash. If yes, then download and install this package.
I also think that you could run setup and maybe remap keyboard.
Last edited by Alien_Hominid; 03-14-2006 at 02:59 AM.
|
|
|
03-14-2006, 03:55 AM
|
#9
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559
|
Quote:
Originally Posted by sweetnsourbkr
I use slackpkg to upgrade the entire distribution (at least the packages I installed), originally 10.2 and I track current continuously.
Unless Pat added a package that isn't updated automatically from 10.2, or a config file is misconfigured ... anyone have any ideas?
|
A few examples of packages that are new in Slackware current (so, upgrading is impossible for these)
openldap-client
cairo
db44
db42
Not installing these, will break many things.
Eric
|
|
|
03-14-2006, 08:49 PM
|
#10
|
Member
Registered: Aug 2005
Location: Bay
Distribution: Zenwalk, OpenBSD, Slackware
Posts: 167
Original Poster
Rep:
|
Interesting. I came across cairo and openldap-client, but I've been dubious about the other two until you mentioned them.
The quickest way I can tell if the system is missing dependencies is from error messages. Like cairo, it was pretty easy because everything was broken and it kept printing an error message about a missing cairo lib.
Let's see if installing those will fix the problem. I've already tried remapping the keybd, but no dice. It's a very old keybd ... IBM ca. 1985
I love the clickyness of the keys.  )
|
|
|
03-14-2006, 08:54 PM
|
#11
|
Member
Registered: Aug 2005
Location: Bay
Distribution: Zenwalk, OpenBSD, Slackware
Posts: 167
Original Poster
Rep:
|
Oh, and I forgot to mention. This problem only surfaces in X. I use KDE, so my preferred terminal app is Konsole.
|
|
|
03-15-2006, 03:45 AM
|
#12
|
Member
Registered: Jan 2004
Location: Trinidad & Tobago
Distribution: Slackware
Posts: 317
Rep:
|
hey how do you get the del to work? > for zsh or bash preferably the first.
|
|
|
03-19-2006, 12:56 PM
|
#13
|
LQ Newbie
Registered: Mar 2006
Location: France
Distribution: Slackware 13.1
Posts: 2
Rep:
|
Hello,
you must check your /etc/inputrc to see if you have the line :
"\e[3~": delete-char
or put it in your ~/.inputrc
|
|
|
03-20-2006, 11:07 PM
|
#14
|
Member
Registered: Aug 2005
Location: Bay
Distribution: Zenwalk, OpenBSD, Slackware
Posts: 167
Original Poster
Rep:
|
It does. I actually lost the use of 4 keys (now that I finally used it a little more and noticed): Insert, Delete, Page Up and Page Down all do the same thing: '~'
It does it in a console under X and also if I use Putty to ssh into my machine.
It gets weirder.....
|
|
|
03-21-2006, 04:29 AM
|
#15
|
LQ Newbie
Registered: Mar 2006
Location: France
Distribution: Slackware 13.1
Posts: 2
Rep:
|
I had this problem with my del key after I had edited my /etc/inputrc, in fact I had written "set bell-style none" at the end of the file instead of uncommenting the line at the beginning.
I had the same problem than you, only in console (or konsole), and not in X applications.
Have you tried to create a ~/.inputrc to override /etc/inputrc and see if the problem comes from this file ?
|
|
|
All times are GMT -5. The time now is 03:24 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|