I don't know how or why, sometimes, suddenly, for no apparent reason, key repetition is disabled.
If I run this command:
xset r on
or if I wait half an hour, the key repetition starts working again but after a few days the problem suddenly returns.
I think it's because xorg or another system program suddenly crashes, but that's just a guess.
I have no idea of the cause of the problem, so I ask whoever has the same problem, if they have been able to diagnose it.
I use Ubuntu 20.04 LTS Desktop 64-bit freshly installed.
There is a similar problem in Ubuntu 8.04 LTS, if it matches my problem, it would mean the bug hasn't been fixed for 12 years!:
https://bugs.launchpad.net/ubuntu/+bug/272293?comments=all
Reset keyboard settings to default
First do a dump of any keyboard settings that differ from default
dconf dump /org/gnome/desktop/peripherals/keyboard/
# => [org/gnome/desktop/peripherals/keyboard]
# => delay=uint32 188
# => numlock-state=true
# => repeat=true
# => repeat-interval=uint32 0
Then reset them back to defaults
dconf reset -f /org/gnome/desktop/peripherals/keyboard/
Danger proceed with care (you probably don't need to do anything beyond here)
Dump all changes
dconf dump /
Reset all settings back to default
dconf reset -f /
Related
Alright, just a disclaimer: I've been using some version of Unix or Linux for 30 years, I have good working knowledge, but when it comes to administration I'm enthusiastically dangerous :)
Every time I do the automated OS upgrade in Pop!_OS something bad happens. And I am not talking about apt update / apt dist-upgrade. I do mean going into the settings GUI and in the last item on the list clicking "Upgrade".
Last machine I did it on failed and I couldn't recover the system, not even from a bootable stick. That machine was on it's last leg, I just let it go and built a new box, it was time. Well here we are again, time for an upgrade to 20.10.
I hit "upgrade os" (maybe it's "update os" I don't remember exactly
It did some stuff, and said it needed to restart - Okay so now we're windows? Not thrilled
Restart and end up at a gray screen where it sat at 0% progress bar for the update
I let it sit a good long while, maybe 45 minutes, I was worried this mid-low range machine was just taking a while, nothing
Cringe.. hit the reset button, the system rebooted and did "something" and then came up seemingly okay
Now here's the problem list:
Did the upgrade happen fully, completely, and successfully? How can I tell? This feels like I'm running windows and just rolling in the blind mystery..
VMWare Workstation wont launch. Nothing happens with icon click, from command line I get this error:
/usr/bin/vmware: line 105: 159580 Segmentation fault (core dumped) "$BINDIR"/vmware-modconfig --appname="VMware Workstation" --icon="vmware-workstation"
Searching online a bunch there was a lot of talk that there may be permission problems after upgrade and running it as root would help. This did not work. I read that upgrading to VMWare 16.x will help. I'm open to it, but on principle WHY does this have to be the case?
I use another app that is installed from source, it's called MakeMKV. I've had no trouble with it until the Pop upgrade. Again, it doesn't launch from the icon. I rebuilt and reinstalled it. No go. Launching from command line returns:
/snap/makemkv/217/bin/desktop-launch: line 51: /home/ritchie/.config/user-dirs.dirs: Permission denied
qt.qpa.screen: QXcbConnection: Could not connect to display :1
Could not connect to any X display.
Launching from the command line with sudo worked though! So wtf?
This feels like a key piece of the puzzle, that bit about not being able to connect to the display.
Since this post is so long I wont list the hardware, but am happy to if it helps diagnose.
Any help is appreciated!
got the same with other snap packages...
tried to figure out what's wrong...
looks like some ENV variable is not set properly causing the error:
.config/user-dirs.dirs: Permission denied
but simply reinstalling the package resolves the issue:
sudo snap remove %package%
sudo snap install %package%
I am a linux noob trying to setup openbox on an arch linux base. I am trying to get it as lightweight as possible in terms of resources used.
My final plan is to use openbox, with tint1 and conky.
however I am having an issue getting openbox to start. I have followed numerous guides and am struggling to figure out the problem.
I have so far installed the following (and done this config)
openbox (installed default option with the extras asked for)
create ~/.conifg/openbox
copied, rc.xml, menu.xml, autostart, environment to the above location
pyxdg
xorg-xinit
xorg-server
this didn't work so I the installed the full
xorg
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
I have had a look at the attached log file, but I don't know enough to be able to interpret it properly.
log file: https://www.dropbox.com/s/r76fowkooi822y9/Xorg.log?dl=0
I would appreciate any assistance.
Thanks
Steve
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
what is it saying?
There is only one error: (EE) open /dev/fb0: Permission denied, try starting your environment with the same configuration as root - just to see if it works. Maybe its a problem related to rootless X.
Have you configured/checked your installation (xserver, graphics driver, xinit config) using the following guides?
https://wiki.archlinux.org/index.php/xorg
https://wiki.archlinux.org/index.php/xinitrc
Try to start a minimal X (As described in the xinitrc article) to see if your xserver and graphics driver is working correctly.
I know the purpose of "biosdevname" feature in Linux, but I'm not sure how
exactly it works.
I tested it with Ubuntu 14.04 and Ubuntu 14.10 (both 64-bit server editions)
and it looks like they enable it by default - right after system startup my
network interface has a name such as p4p1 instead of eth0, no customization
is needed. As I understood it, in order for biosdevname to be enabled, BOTH
of these two conditions must be met:
a boot option biosdevname=1 must be passed to a kernel
biosdevname package must be installed
As I already mentioned, both Ubuntu 14.04 and 14.10 seem to offer biosdevname
as a default feature: they come with biosdevname package already installed, I
didn't need to modify grub.cfg either - GRUB_CMDLINE_LINUX_DEFAULT has no
parameters and my network interface still has a BIOS name (p*p*) instead of a
kernel name (eth*.)
Later I wanted to restore the old style device naming and that's where the
interesting part begins. I decided to experiment a bit while trying to disable
the biosdevname feature. Since it requires biosdevname package to work (or
so I read here and there), I assumed removing it would be enough to disable the
feature, so I typed:
sudo apt-get purge biosdevname
To my surprise, after reboot my network interface was still p4p1, so
biosdevname clearly still worked even though biosdevname package had been
wiped out.
As a next step, I applied appropriate changes to /etc/network/interfaces in
order to restore the old name of my network interface (removed entry for p4p1
and added entry for eth0). As a result, after another reboot, ifconfig
reported neither eth0 nor p4p1 which was another proof that OS still
understood BIOS names instead of kernel names.
It turned out that I also had to explicitly change GRUB entry to
GRUB_CMDLINE_LINUX_DEFAULT=biosdevname=0 and update GRUB to get the expected
result (biosdevname disabled and old name of network interface restored).
My question is: how could biosdevname work without biosdevname package? Is
it not required after all? If so, what exactly provides the biosdevname
functionality and how does it work?
The reason biosdevname keeps annoying you even after you uninstall the package, is that it installed itself in the initrd 'initial ramdisk' file as well.
When uninstalling, the /usr/share/initramfs-tools/hooks/biosdevname is removed, but there is no postrm script in the package so update-initramfs is not executed and biosdevname is still present in the /boot/initrd... file used in the first stage of system startup.
You can fully get rid of it like this:
$ sudo update-initramfs -u
If I'm installing any program via ports, and my screensaver starts, or goes into sleep mode, gnome will suddenly stop functioning properly. If I move the mouse/press a key, the screen will flicker from black to wallpaper(no icons panels displaying). If I force a shutdown and restart gnome does not start, I can log into the system through terminal. I also get the following error saying Libpcre.so.0 can't be found. Anyone else have this problem / know how to fix it?
For the libpcre problem i suggest to use libchk (sysutils/libchk). It checks which programs link to unresolved libraries. Reinstall those ports.
I play to self-study 6.001 with the video lectures and lecture handouts. However, I have some problems setting up MIT Scheme in Ubuntu (intrepid).
I used package management and installed MIT-Scheme, but it's obviously the wrong version to use. It should be 7.5.1 instead of 7.7.90
I followed the instructions from this website (http://ocw.mit.edu/OcwWeb/Electrical-Engineering-and-Computer-Science/6-001Spring-2005/Tools/detail/linuxinstall.htm)
So far, I've downloaded the tar file, and extracted to /usr/local. I have no idea what step 3 means.
Then I entered command
scheme -large -band 6001.com -edit
and the error is
Not enough memory for this configuration.
I tried to run under sudo mode, and this time the error is different
Unable to allocate process table.
Inconsistency detected
I have close to 1GB of free memory, with ample HDD space. What should I do to successfully set this up?
Step 3 means that you should type export MITSCHEME_6001_DIRECTORY=${your_problems_path}. If you don't want to type it every time you launch Scheme, you should put it as a string in your ~/.bash_profile file(in case you use bash)
About the problem itself, Google instantly suggests a solution:
sudo sysctl -w vm.mmap_min_addr=0(taken from http://ubuntuforums.org/showthread.php?p=4868292)
Instead of the package manager, you may also want to compile the portable C sources for Unix. I am using it happily.