When (re)installing httpd today, I ran into the following error message:
(OS 10048)Only one usage of each socket address (protocol/network address/port) is normally permitted.
: make_sock: could not bind to address 0.0.0.0:80
I just finished upgrading Eclipse from Galileo to the new Helios release. I performed the upgrade by adding Helios to the software sources list and updating and all seemed to go well. However, when I restarted Eclipse, I got a splash image which indicated that the upgrade had gone through and then ran into the following error message:
Failed to create the Java Virtual Machine
When I attempted to make a commit using TortoiseSVN today, I was told that there was a problem and that I would have to run the
cleanup command to sort things out. Running the command, however, resulted in the following further error message:
Cleanup failed to process the following paths:
Here I was, earlier today, simply trying to swap the default gateway of the Ethernet card of my Windows 7 box, and ran into the following peculiarity. First off, as soon as I swapped the gateway, my Ethernet connection went down. To investigate this, I popped into the command-line and tried pinging the new gateway only to run into the error message below:
Windows 7: High CPU usage due to system interrupts (Deferred procedure calls and interrupt service routines)
Windows 7, much as I enjoy using it (although the shine has worn off a li'l bit), has a few niggles. One of these, which really annoyed me was the sudden seemingly random spike in CPU usage that, once it occurred, never went away until I rebooted the system. The task manager did not list any application as consuming any significant attention from the CPU. However, the resource monitor (which can be reached from the performance tab in the task manager) provided the answer as I found the innocuous sounding "system interrupts" process consuming a steady 40-45% CPU.
I made a mistake earlier today when looking for a GUI application to manage samba shares. I installed the wrong application - gadmin-samba (which is quite fugly and buggy) - instead of system-config-samba which is clean and has worked well for me in the past. gadmin-samba added all sorts of nonsense and in a bid to reset the samba configuration, I nuked the files in
/etc/samba to give system-config-samba something of a fresh slate.
During a fresh install of Windows XP SP3, upon reboot after the initial copying of files, I ran into an error message stating that there were CRC checksum issues with a file on my CD-ROM, namely D:\i386\asms.(sys?). Google divined that I very likely had a problem with the disc media... but considering the fact that I've installed XP using the same media very recently, I doubted this to be the case.
If you've run into the error message KDEInit could not launch '/usr/bin/ktorrent' on KDE 4, you are not alone. It appears that this is a KDE Bug that should be resolved in a bug-fix update in the near future. This also apparently affects other applications besides KTorrent.
In my case, when I clicked on a torrent file, the error message cropped up, but the file itself was open fine ...