Tag Info

Hot answers tagged

11

Use nbd, the Network Block Device, and then rate limit access to it using say trickle. sudo apt-get install nbd-client nbd-server trickle


8

Switch to X (the graphical interface that is frozen) usually by typing Alt+7 and then type Alt+SysRq+k . This will kill X and it will restart. This is kind of a "nasty" solution but without additional details and debugging is the best I can offer. -- or -- logged in on a virtual console (or remotely) type sudo service gdm restart


7

Sometimes it's just the X server that is frozen. Try to get a console by hitting CTRL-ALT-F1. If that won't do, try logging it your machine using SSH (install openssh-server package first). If you can't get a shell, reboot. Once you have a shell, check the system logs (/var/log/syslog, /var/log/messages, /var/log/Xorg.0.log and ~/.xsession-errors). Scroll ...


6

Your best bet is to back up your files and re-install. I'm not sure what's causing the problem, but the 3 separate boot loaders sounds definately wrong to me. I would also advise doing a full dual boot instead of a wubi install because: What is the performance? The performance is identical to a standard installation, except for hard-disk access ...


6

Hmmm... Strange, maybe you'd installed it two times, one through USC and other through a downloaded .deb package, if so it's needed to find the other AWN you installed and uninstall it. But probably, you didn't do that, so what to do? Try typing in the terminal: sudo apt-get install aptitude sudo aptitude purge avant-window-navigator sudo apt-get -f ...


5

In 13.04, I found that /sys/class/backlight/toshiba breaks after suspend, but /sys/class/backlight/intel_backlight continues to function (echo $number > backlight after resume from suspend). Some great folks over at Arch have figured this one out. This does the trick: Source: ...


5

You might want to look into ~/.xsession-errors for relevant error messages.


4

Have a USB 1.1 hub? Or a slow SD card? They'll get you down to under 10mbps.


4

I know this might sound crazy, but go to the sound preferences, under input, and make sure the check mark for mute is unchecked, it is checked by default....


4

Add this line to your /etc/modprobe.d/alsa-base.conf file: options snd-hda-intel model=dell-vostro enable=1 index=0


4

You could probably extend the timeout in your system. Open the gconf-editor using sudo gconf-editor and navigate to desktop -> gnome -> session. There you find a key idle_delay. You can change that value by double-clicking on it. Depending from how long you are typically inactive you change it. So if you usually don't have FTP activity for half an hour ...


4

Ok, I manage to solve it. I just installed the libido package and now the indicator-sound package installed with no errors. Maybe the system needed a reboot with the package uninstalled or something. If someone's having this problem, you can try: sudo apt-get remove libido-0.1-0 sudo apt-get remove indicator-sound Restart your computer (this is the part ...


4

# echo 1 > /proc/sys/vm/drop_caches That'll slow you down :) It'll force you to read from disk, instead of taking advantage of the cached page. If you really wanted to get sophisticated you could do something like fake a read error every nth time using the scsi fault injection framework. http://scsifaultinjtst.sourceforge.net/


4

My ideas: Make sure you always keep at least one older and stable kernel version installed. That way, if a new kernel update causes the panic, you will still be able to restart your system with the old one. Write down as much information as you can regarding the error. Take a photo of the screen output with your mobile phone perhaps. Post these messages ...


4

Here is a good introductory video tutorial to Ubuntu. That youtube user has dozens of other tutorial videos as well. He's using an older version of Ubuntu, but most of the basics are the same, assuming you aren't using the newest version (11.04), which releases in a couple days (April 28, 2011). Version 11.04 uses the new Unity layout, which is pretty ...


4

There is a step-by-step troubleshooting guide on the wiki.


4

Try blacklisting the acer-wmi kernel module: sudo nano /etc/modprobe.d/blacklist.conf add blacklist acer_wmi as a new line at the bottom of this file. then reboot. edit: The acer-wmi kernel module enables you to control the following: the wireless LAN card radio inbuilt Bluetooth adapter inbuilt 3G card mail LED of your laptop brightness of the LCD ...


3

Is this "Prog." an abbreviation for the real directory name? If no: please try in a directory without a dot at the end. If yes: does the real directory name have spaces, like "My Programs"? Then you have to quote these spaces, i.e. use double quotes or apostrophes, like so: wine 'data/My Programs/Program/install.exe'


3

You need to specify the architecture when you remove i386 package. I.e. remove it by executing sudo dpkg -r qtikz:i386.


3

The unicode character entry keyboard sequence is Ctrl+Shift+U hex value Enter so the @ sign would be Ctrl+Shift+U 40 Enter. You might want to check the keyboard locale settings in the keyboard layout pane of the settings center to make sure you have the right layout. ◕‿◕


3

An interesting tool I hadn't seen from https://wiki.ubuntu.com/DebuggingSoundProblems : ubuntu-bug audio It attempts to do some interactive checks. If you haven 't, try running that when the issue occurs. But the checks are worth running any time. I believe the bug information generated will provide the information that the next links ask for. (For ...


3

The apache command you tried is clearly the problem, it's caused all sorts of files to now be owned by www-data instead of root, your user and a bunch of other system users that operate the machine. It would be very hard to try and recover the machine in it's current state and instead the best action to take is to reinstall. Make sure you back up all your ...


3

The most complete way to try and recover your system is with a reinstall. However you can try something to this affect which should produce some viable results. sudo chown -R root / for u in $(ls /home/); do sudo chown -R $u /home/$u; done This brings everything else on the system back into ownership of root, and home folders into ownership of themselves. ...


3

When i have a problem like that i normally do the following: In the grub menu select the RECOVERY MODE When the blue menu appears select to run as root in the terminal/shell When you login in the shell as root type dmesg to see any problem of devices when you were loading the system. To see a more specific summary type cat /var/log/syslog which will show ...


3

When this symptom occurs, please don't remove then reinstall sound packages. Instead, please file a bug using ubuntu-bug alsa-base immediately so that we can troubleshoot where in the audio stack the problem(s) is(are). Please go ahead and use ubuntu-bug alsa-base now via Applications > Accessories > Terminal. If necessary, we'll convert the report to a ...


3

The solution for me was to edit the /etc/X11/xorg.conf file. It's a problem with the graphics driver not the keymap. Open the file for editing and add the line Option "RegistryDwords" "EnableBrightnessControl=1" in the Section "Device" section as shown below. Section "Device" Identifier "Device0" Driver "nvidia" VendorName ...


3

Maybe your CMOS battery is getting empty (the battery on the motherboard itself). You can hit F1 (or DEL according to you motherboard) at the first seconds during pc starup to enter BIOS. in the BIOS you can check the hardware clock. Just let the computer run and check if the time stays correct (during this time you can't use your computer) If the ...


3

While I'm not sure what is causing your system clock to drift so badly, you can install ntpd to keep your clock in hand - it continuously adjusts the system clock based on the calculated drift. sudo apt-get install ntp By default it syncs to ntp.ubuntu.com but you can edit /etc/ntp.conf if you want to change the NTP server. For more details see the NTP ...


3

If I recall an article I read once on lwn.net Once the computer is booted it keeps track of time by the clock frequency of the system as this is more accurate than the quartz in the cmos and saves an expensive and (relatively) slow BIOS call. There was a problem with virtual machines having their CPU time sliced that caused the problem. This person has a ...



Only top voted, non community-wiki answers of a minimum length are eligible