UbuntuThis forum is for the discussion of Ubuntu 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.
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.
Hi I'm keen to install Ubuntu on my old laptop
(HP ze4500 2.4GHz 1Gb Ram 120GbHDD) But during installation (I presume as soon as the screen capture function becomes available) A zillion screen capture screens appear and lock up the system.
It may be due to my prtscn button being missing. Actually its just the plastic part and the rubber button mechanism is still present. The button works without the plastic part completely fine in windows. That is to say I can press it when I want to use it and it works and it does nothing noticable otherwise.
Seems like a pretty trivial way to kill ubuntu, perhaps there's a trivial way to solve this problem on my laptop without replacing it?
I do get through to the desktop sometimes if i carefully dont touch the keyboard and shutdown the screencapture panels as they appear. It doesnt seem to matter which method i use to get into the desktop though livecd/install alongside windows/fresh install.
Thanks, yeh google is cool when you know what your looking for
So it would seem that xev and xmodmap are the key so to speak... However
I cant do anything by the time the desktop is visable so I needed to get to the terminal during boot. more googling and I see that ctrl-alt-f1 opens me up a terminal before my system starts and subsiquently gets thrown by my faulty key
unfortunately within the terminal that o open during boot xev and xmodmap result in "unable to open display '' "
more googling and it seems that both of these commands, which the vast majority of help on remapping keyboards are based on, seem to need the KDE to be up and running which is no good if your faulty key is killing the KDE. Maybe I should use xkb? unfortunanely instructions on its use look like instructions to build the space shuttle in greek to me.
I didnt think It'd be that difficult. Perhaps I'm missing something simple to get those commands or something equivilent which will work at the terminal in order to remap the keyboard before going to the desktop.
Anyone know of such a thing or what I've got wrong?
You will then probably have to find the correct file to modify. For gnome it looks to be /home/<username>/.gconf/desktop/gnome/peripherals/keyboard/host-<computer-hostname>/0/%gconf.xml. Sorry, I don't have KDE on this install, but I would imagine it is similar.
I havent had any luck locating the part of the X conf files to modify but I did finally get a long enough go on Gnome, before it hung out, to get into the terminal and run
Code:
xmodmap -pke
xmodmap -e 'keycode 107 = NoSymbol'
which solved my problem after a reboot. (xmodmap -pke indicated the 107 code for printscreen in my case).
So while it wasnt really the solution I was after I did get it sorted in the end.
Actually we're on the right track but I wouldnt call it solved.
In another forum I see that I should put the command in the System, Preferences, Sessions, Startup Programs folder, Add. In order to make it perminant.
That does work but if I could find a way to add the command from the terminal (preferably one not requiring the kde as xmodmap does) Then someone with a keyboard which kills their laptop would have a better shot at saving it.
I will have look myself. Quick googling gives many options . As soon as I have a working method I will post for others. Possibly based on /etc/rc.local
editing rc.local didnt work
and as it turns out when I finally got to the start up add part and added the xmodmap -e line and deleted the prtscn key perminantly (checked this with restarts)
Even with no prtscn key (checked with xmodmap -pke) My laptop is still being shut down by repeated screen captures.
After 10+ hours I'm officailly giving up on ubuntu for this laptop...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.