Tag Info

Hot answers tagged

4

I had EXACTLY the same problem with NVIDIA drivers. Your problem probably is related to these bugs (they all have the same symptoms): https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310762 http://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314871 Unfortunately it is ...


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

Chrome 40.0.2214.93-1 was released and the problem seems to be gone much better now. Similar symptoms still occur some times but much less frequently. It seems that this problem only affected started with the 40.0.2214.91-1 release. So if you're running that version do sudo apt-get update && sudo apt-get upgrade to update to a more current version.


3

Got the same issue ever after the Chrome 40.0.2214.91 release, and though I haven't tried the .93, I can at least confirm the issue is 100% gone in Chrome 41 Beta. Strongly considering sticking to the beta until 41 becomes stable, or at least until it's 100% confirmed a point release fixed the issue.


2

According to your dmesg output there's a bug in the WiFi driver. Let's take a closer look: the most recent wakeup event is at [22500.127146] ACPI: Waking up from system sleep state S3 and the wakeup finishes ~5 s later: [22505.833530] PM: Finishing wakeup. The system then takes another ~5s to re-initiate the PS/2 interface (for keyboard and touch ...


2

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


2

As you're familiar with Ctrl+Alt+F1, I suppose you're more technical then the reputation 1 you have here would suggest... The standard Ubuntu NVidia drivers generate some problems on slightly older and slightly newer NVidia hardware. If you want more then the standard Ubuntu repository drivers, install the xorg.edgers PPA. As the xorg.edgers group ask not ...


2

Maybe light locker is installed on his system. Try uninstalling light locker if so: sudo apt-get remove light-locker And install xscreen saver instead of it: sudo apt-get install xscreensaver xscreensaver-gl-extra xscreensaver-data-extra See here for more info: Ubuntu forums


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

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

If the DE has frozen, switch to a different run-level by using ctrl-alt-f3 and login to the terminal presented. You can kill any offending processes by using kill or killall, if the DE has gone into hardlock it may be worthwhile to kill xorg by sudo killall Xorg to restart the DE (usually drops you back to the DM to login),switch back to the graphic ...


1

This is happening to my Lenovo T510 with Kubuntu 14.10 as well, several times every day. Ctrl+Alt+F1 followed by Ctrl+Alt+F7 "unfreezes" KDE, so no need to reboot for me. It's very annoying, though.


1

I've had the exact same problem about 2 years ago. Some background: I was always very careful about using the battery as little as possible: Always completely discharge the battery before charging again. Take it out of the machine whenever I was home and plugged in anyway Store it in a cool, dry place Stop charging when the charge reads 100% for more info ...


1

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


1

This is more of a "workaround" then a "solution"... As your user profile has some problem somewhere, it's just better to leave it behind! Do the following: sudo adduser newuser Add the user to the right groups (Below are the standard groups for an admin user. To get the user groups for the old user type: groups olduser) sudo adduser user2 adm sudo ...


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've seen cases like this where the problem was a bad RAM chip or a bad sector on the hard drive. Not enough to crash the system but enough to give the OS a hiccup. Run Memtest86 on the RAM, and if possible swap out the RAM for a friend's and see how it runs. Best to run the Memtest from a Live CD. Use a hard disk test utility from the HDD manufacturer ...


1

When you chroot into your system, regenerate your initial RAM-disk. It is likely that modules are missing causing this problem to occur. update-initramfs -k all -c Before chrooting, mount /dev, /proc and /sys inside chroot: mount -t proc /proc /mnt/proc mount -o bind /dev /mnt/dev mount -o bind /sys /mnt/sys I'm assuming here that you mounted your ...


1

So, I found a way to get things booted: downgrade the kernel. The kernel that came with 14.04.1 was 3.13.0-32-generic. The kernel that worked was 3.13.0-24-generic. It is available in the repositories. How to get it? Boot from a LiveCD/flash drive and open a terminal. Now, we need to load ourselves into the computer's new, non-functional OS: sudo mount ...


1

Try resetting Firefox... Try the links given below. Reset Firefox to its default state Firefox Slow/Hangs


1

Alright I figured it out and it brightness adjustments works better now then before my bios update Here's my fix for my NVIDIA NVS 5400m sudo nano /etc/default/grub edited GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" make sure to save and then run sudo update-grub afterwards. then do this ...


1

You can check whether you are hit by this bug. In my case it helped to inactivate the virtual keyboard "Onboard".


1

Deleting the .config/chromium folder and seems to have solved the issue.


1

It turned out to be a hardware problem - graphic card fan was packed with dust, and graphic-costly operations (like watching videos) caused it to overheat. I found that out when it was already too late and I needed to replace the graphic card. After replacing it the problem was gone.


1

This turned out to be a hard drive failure - I booted into a live CD and ran badblocks on the SSD whilst it was unmounted - there were lots of bad sectors. Bought a new SSD and it works fine now. Lesson learned: you can't properly check an SSD whilst it's mounted and in use.


1

I finally got this to work right by first switching to a terminal using CTRL + ALT +F2 and then running the following series of commands: sudo service lightdm stop rm ~/.config/dconf/user sudo service lightdm start The following article is where I found this answer and it goes into more details with a few other things folks could try, but it was this last ...


1

I had also this issue with my Dell E6520 with Nvidia NVS 4200M (Graphics issue). Search for "Additional Drivers" in unity and there changed from "nouveau" driver to "proprietary, tested".



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