Hot answers tagged

6

Perhaps X server may choose incorrect driver for your computer. If the current version of Xorg that you use supports your computer, you need to try manually change the driver via a file, /etc/X11/xorg.conf.d/xorg.conf. This file describes Xorg server configurations. Please create the xorg.conf file with following contents. Section "Device" Identifier ...


4

According to this bug report I solved it adding following lines vm.dirty_background_ratio = 5 vm.dirty_ratio = 10 into /etc/sysctl.conf and running sudo sysctl -p


4

I worked out a solution myself: Quick answer Assuming that your drive is /dev/sdX: Run dd if=/dev/zero | cmp - /dev/sdX to spot the first non-zero byte of the device: in my case it was byte 742300476649 Calculate to which block does the first non-zero byte belong to: ...


3

This happened for me in a new install of Ubuntu 14.04. In my case, it had nothing to do with sysctl issues mentioned. Instead, the problem was that the swap partition's UUID was different during installation than it was after installation. So my swap was never enabled, and my machine would lock up after a few hours use. The solution was to check the ...


3

Install the latest stable NVIDIA drivers supporting GTX670 from the Proprietary GPU drivers PPA. sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-352 sudo reboot Note 1 : If you ever had NVIDIA drivers installed - uninstall every NVIDIA related software before. Open a terminal and execute : sudo ...


3

Run Chrome from a terminal with the flag --disable-gpu google-chrome --disable-gpu Then select: Options - Settings - Show Advanced Settings Under the System heading, uncheck "Use hardware acceleration when available" and restart the browser.


3

Yes. Look at /var/log/kern.log, and check the lines before the reboot (lines with kernel: [ 0.000000] were logged 0.000000 seconds after the reboot, so look at the lines preceding that one.


2

If you start following random links around the web, it's a good thing if you make a system back-up (you're definitely user type 4) before trying random stuff that ends up freezing your computer. So unless you post an exact list of everything you tried to do, the answer to "Why?" is impossible to answer... Sorry to be the harbinger of bad news. :-(


2

Install the video driver by running sudo apt-get install nvidia-304 and reboot. I am suggesting 304, because I know that it works better that 340 on that card.


2

The blinking caps lock is probably caused by a kernel panic, more info here. Look for log files as instructed here to debug this. It seems like there should be something related in /var/log/syslog.


2

It's a confirmed bug, therefore use a newer version via the PPA ppa:wireshark-dev/stable sudo apt-add-repository ppa:wireshark-dev/stable sudo apt-get update sudo apt-get dist-upgrade


2

Press Alt+PrtSc and while holding on these two keys type REISUB. for more information you can found you answer here.


2

First check your laptop specification. Basically there is much trouble with some hardware for you kernel. and also the performance of your integrated graphic. In case someone else finds this, a kernel upgrade fixed a similar problem. I had Ubuntu 14.04.2 kernel version 3.16.0-30, and doing a "apt -y upgrade" ended me up at kernel 3.16.0-49, and that solved ...


2

Remove the currently installed NVIDIA drivers and the xorg-edgers PPA. Open a terminal and execute : sudo apt-get purge nvidia* sudo apt-get install ppa-purge sudo ppa-purge ppa:xorg-edgers/ppa sudo reboot Install the latest stable NVIDIA drivers that support GEFORCE GTX 660M. Open a terminal and execute : sudo apt-get update sudo apt-get ...


2

I've seen a lot of other people who have problems with Universal USB Installer. For some reason, it just doesn't seem to like Ubuntu. Instead, since you're on Windows, use Rufus. It's portable, it's free, it's small and, most importantly, it works really well.


2

I get it occasionally in 12.04 LTS. control+ALT+t will usually open a terminal window. modprobe -r psmouse followed by modprobe psmouse will usually fix it. Check RAM by booting into GRUB. Boot holding shift down, then test memory.


2

I suggest you remove all the instances you mention above. The correct way is: sudo -i echo "options forcedeth msi=0 msix=0" > /etc/modprobe.d/forcedeth.conf exit Upon reboot, the parameters will be applied. Whether they fix your exact issue is another question.


1

Your screenshot is displaying repeating patterns of video artifacts which are characteristic of video RAM artifacts. If the RAM in your graphics card is failing, sometimes just a small fraction of the RAM goes bad while the rest of the RAM continues to work properly. This can result in a screen that looks like a fraction of the screen has glitchy, repeating ...


1

After reporting my issue on the Xorg and the Linux kernel Bugzilla, I was invited to test a kernel patch (this is the patch, posted for this bug). After compiling and installing the patched kernel, the problem looks gone, and the dynamic turn on/off of the discrete graphic card is working again. I have to thanks kernel developers for pointing me to the ...


1

You are using an open source "radeon" driver for your video adapter. It may not perform well. I suggest installing a proprietary AMD driver. You can do it by running in terminal sudo apt-get install fglrx and reboot. Same task can be done in GUI. You can go to System Settings -> Software & Updates -> Additional Drivers and find there drivers for ...


1

Looks to me like you have a problem with your disk drive sda1. It's formatted as an ext4 file system and the file system is spitting out errors. Probably one way of fixing it would be by copying as much data as you can from the drive and then discarding the drive and putting the data on another one. Expensive and time-consuming. You can try other things, ...


1

I was able to at least find a workaround for my problem. Even though I did try this with 14.04, following this guide: https://wiki.ubuntu.com/DebuggingACPI I set the boot flag "acpi=off", which now seems to have solved my problem. I was able to install and use 15.04 for a couple of hours now without any problems.


1

DO NOT FOLLOW ANY ADVICE TO DELETE COMPIZ! I had the same problem after tweaking compiz. Unfortunately I followed someone's advice to delete compiz and destroyed my installation. The solution I found was to install Ubuntu again. When I chose LVM to look at the layout, it wiped my drive without warning. It is the only option that does not give a warning ...


1

freezing means you cant do anything in the desktop even a mouse pointer movement. this link may help you in such cases.


1

Could you please try to press Ctrl+Alt+F1 the next time it happens? If you are able to see a black screen with white font you are able to use the "screen" as a CLI. Login and then try to execute the command "kill -9 -1". Add the result to your question.


1

I think what you are facing is a very elusive bug. I had the same issue for a while. I thought it might be the nVidea graphics card, but when I got my new computer, it had the same problem with an Intel graphics card. I went back to 12.04 on my new computer and left 14.04 on my old desktop. I discovered that some time after I have been on the internet, ...


1

This is fairly old, but I thought I'd reopen this, with a possible but report in the making. I oversee a fairly large network on which we have many users who access a central LTSP server. Lately, we've noticed slowdowns and unintended log-offs when users take screenshots. Looking at top -0 %MEM, there are some xfce4-screenshooter processes taking fairly ...


1

GrUB will write code and data to some devices which will utterly confuse some BIOS USB code. The only thing I found which will make some of my systems not freeze is to format the first partition (e.g., /dev/sdb1) as VFAT (intending it to be used for GrUB boot. And that doesn't work for all of them, but it seems to help with some. I mean, if you don't do ...


1

I had the same problem. Upgrading to 15.04 fixed it for me.



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