CentOS

Just found a solution that worked for me: renaming the .kde folder at the home directory, then logging in. That will bring the keyboard back to life, but all KDE configuration will be gone, which is quite a pain. Then copying back to the new .kde everything that was in the old one. That brought KDE ...

I've been trying to fix an issue with my nvidia card (still failed to do it, and I don't know if it's related to this but I thought it was worth mentioning), and ran into this weird problem: after logging in, the keyboard simply goes unresponsive. It's obviously working perfectly well because I need...

It seems it is now ok now. Since I was unable to do anything on the terminal (or using alt-f2 to run specific problems), and there was no way to edit limits.conf on KDE as well, the solution was to go to one of the text-only terminals (CTRL-ALT-F2), log as root (logging with my user wouldn't work), ...

I'm facing exactly the same problem, but it gets worse: it basically made my terminal (I use bash) completely unusable, as I can't even run any of the commands listed above: it returns just a series of five errors messages like this and then returns to the terminal - but without running the command ...

Would a bad cable or switch port cause a problem like this? What I find weird is that I always get networking back after the service restart without having to touch anything... This is what I get from the log: Oct 18 03:35:01 laue rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1973"...

In the last few days I keep facing a recurrent network problem - it goes down for no reason and the only way to get it back is doing a "sudo service network restart". Sometimes I don't need to do it for a full day, but sometimes I can't do anything because I have to restart the network every two min...

I've just I found a bug on kwrite and, after searching for people with the same issue, I only saw it mentioned for Kate (here, for example: https://bugs.kde.org/show_bug.cgi?id=253191 ). Interestingly, I've been using kwrite for many years in other distributions (mosly *buntu) and I don't remember h...

You're right - turns out the vendor had disabled the original CentOS-Base.repo... :/
After fixing that, everything seems to be ok now, thanks a lot.

Ok, I edited /etc/yum.repos.d/CentOS-Vault.repo and now the only two entries with enabled=1 are these: [C6.0-base] name=CentOS-6.0 - Base baseurl=http://vault.centos.org/6.0/os/$basearch/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6 enabled=1 [C6.0-updates] name=CentOS-6.0 - Update...

Ok, so I edited /etc/yum.repos.d/CentOS-Vault.repo, changed all C6.5-* entries to enabled=0 and enabled=1 for the C6.0* entries. I still get the same problem after a sudo yum update or a system reboot, though.