Hot answers tagged

8

It seems like the problem reappeared with Chrome version 49. Below is a workaround that will solve the problem until Chrome fixes this bug. It works without disabling hardware acceleration in Chrome (and potentially causing other issues). If compizconfig-settings-manager is not installed, install it by sudo apt-get install compizconfig-settings-manager ...


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 ...


5

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.


4

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 ...


4

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 ...


4

An Atom processor? Running Ubuntu??? :O I'd start looking at Lubuntu and install that! Probably your system was just barely fitting until 14.04.4 when it started swapping like mad and that just looks like it's freezing: it's actually still working, but 1000 times slower then before... Sorry to be the harbinger of bad news... Alternatively, just get ...


3

Update of kernel to 4.4.8-wily will solve the problem. It works fine with Intel® HD Graphics 520, so I assume that it should help to all Skylake graphics cards. Instalation instructions here: http://linuxdaddy.com/blog/install-kernel-4-4-on-ubuntu/


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.


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 ...


2

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.


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

I have actually found an answer here as in fact the issue was due to having 16GB RAM installed. The writing buffer was actually too big. I have resolved by logging in as root: su root then setting the dirty bytes to a set number (I guess the default setting 0 actually doesn't give any cap to how much should the writing cache be large), by typing: echo ...


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 ran into the similar issue. Mine is 64 bit Ubuntu 14.04. So After a long struggle I found a answer which solves my issue. For easy use I added the commands below used in that above mentioned answer. Check the answer for detailed explanation. echo $((16*1024*1024)) > /proc/sys/vm/dirty_background_bytes echo $((48*1024*1024)) > ...


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

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


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.


1

I had the same thing. First using LibreOffice, which i uninstalled. Then after installing Openoffice. Selecting a piece of text in order to copy it everything froze. My problem was solved by turning off "Transparency" which can be found in "Tools-Options-View". Clearly a graphical issue indeed.


1

It's the noveau graphics driver, switch to the nvidia drivers and everything will be fine. I have a y50 myself and have been facing this issue for a while. To easily switch to the nvidia drivers, press the win key, type "drivers", enter, make sure you're on the additional drivers tab, then check nvidia binary driver and apply the changes. Then boom, ...


1

This is not because of Ubuntu or windows, it's because your HDD has some bad sectors, try to run a HDD test app like HDD Scan 3.3 to test it, then after you find the bad sectors use and app Like HDD Regenerator(free) to fix it. if the bad sector is unrepairable, you can try to cut the part of HDD that has it, Make it unallocated. If all the above doesn't ...


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

Had the same problem. It was GPU related but instead of disabling it, I went to Software & Updates -> Additional Drivers and switched from the (open source) drivers to the first choice which was the (proprietary, tested) one. Everything working flawlessly now.


1

This is caused by your touchpad, disable it and use a mouse as a test. Then you will need to blacklist the kernel mod. PS I have the exact same laptop ;-)


1

Passing a reboot= parameter to the kernel can solve this issue, no matter which shutdown command is used. See http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/ for more details. In my case, reboot=pci fixed the problem for a Dell Optiplex 790.


1

So after 1,5 years of testing it seems I've finally solved this problem. All it took was sheding some light into the issue. Literally. This is what I was only able to see after putting some bright, direct light into my PCIe slot: I'm guessing this happened when I first inserted my video card into that slot. The card may have pushed a couple of pins ...


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

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, ...



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