Tag Info

New answers tagged

0

before upgrading to 4.0 while i was running kernal version 3.19 error was acpi probe failed.... starting version 219 and after updating to kernal 4.0 device descriptor read/64, error -32 and then : Starting version 219 please give me any solution it freeze my pc 1-2 mins before starting... thanks


0

It was fixed in an update :) , never mind


0

From the information you've given, your CPU is 64-bit. While I don't know why the extra RAM isn't currently showing under PAE, my recommendation is nevertheless to run a 64-bit build of Ubuntu on it. While PAE allows the system to make use of additional RAM, any given application is still limited to 3GB. Using 64-bit Ubuntu overcomes this. Software ...


0

This problem can happen in the case of Hyper-V virtualization (Happened to me today). In this case the answer is to disable OS-probbing in grub by opening the configuration file : sudo nano /etc/default/grub And adding the line : GRUB_DISABLE_OS_PROBER=true


1

"Clean install" is basically new installation. It's just informal way of saying "New installation". There's no user files, no user-specific settings. There are plenty of tutorials on how to do it on the web. Particularly, this one. To summarize, you need to download Ubuntu's image (a file with *.iso extension), and "burn" (or extract it ) to a USB or ...


0

Create a bootable usb drive of the Ubuntu 14.04.3 and install it on your system. Use dd: sudo dd if=/iso/file.iso of=/dev/sdb (Make sure you replace sdb with whatever node your usb drive is) or use Startup Disk Creator to create the bootable USB flash drive.


0

To use the latest available kernel releases for your Ubuntu release, install the package linux-generic sudo apt-get install linux-generic From apt-cache show linux-generic Description-en: Complete Generic Linux kernel and headers This package will always depend on the latest complete generic Linux kernel and headers.


0

The recommended way is to simply update your system. The current kernel in Ubuntu 14.04.3 and 15.04 is already 3.19.0-26. Run in terminal sudo apt-get update && sudo apt-get upgrade and you will get all routine updates.


0

I had the same problem, and all I had to do was: sudo apt-get install unity && unity and my desktop immediately fixed itself.


0

The hard way Write the names of the installed fglrx packages in the file fglrx_installed via the command below dpkg -l | awk '/^ii.+fglrx / || /^ii.+fglrx-updates / {print $2}' > fglrx_installed Check the content of fglrx_installed via cat fglrx_installed Sample content is fglrx Remove the file /etc/ati/atiapfxx sudo rm /etc/ati/atiapfxx ...


1

Unfortunately, if you wish to "upgrade" (Except between LTS versions), you must upgrade in sequence, so from 14.04, you need to upgrade to 14.10, and then 15.04. Once you are on 15.04, and you are fully patched (it will refuse to upgrade if you are not patched fully), you can open a shell and run sudo update-manager -d. The -d option allows it to give you a ...


0

Maybe you're not going to like this, but the best way to try out the daily build for 15.10 is by installing the testdrive application from the Ubuntu Software Center. Testdrive helps you download and run the daily Ubuntu development ISO in a virtual machine on your local hardware. I understand if you'd rather try out Ubuntu MATE 15.10 on bare metal.


1

First : cd /var/lib/dpkg/info/ then rm -rf mailman* then sudo apt-get clean all sudo apt-get update sudo apt-get upgrade Reference here


0

I experienced the same problem, there is also an expired bug report for it (https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1452968). I think it has been invoked by not first updating + upgrading + dist-upgrading to the latest version of 14.04 (.3 at the time of writing). Besides resetting the /etc/apt/sources.list file to trusty, as ...


0

After some try and error, I found the only solution to be to uninstall all maas related packages dpkg -r and re-install maas from scratch.


0

It is possible, but not recommended because it is not supported in current stable Ubuntu version (no security update etc...). Run the following commands : 64 bits : wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1.6-unstable/linux-headers-4.1.6-040106_4.1.6-040106.201508170230_all.deb wget ...


0

These errors often arise due to bad profile configuration. Rename the profile folder using the following cmd: cd ~/.config && mv libreoffice libreoffice.old New profile is generated automatically... Source: link


1

If your country's server is working fine at the moment then you should switch to that for it is effectively a mirror server to download your software packages from. As stated here this affects: spreading the load among multiple servers instead of just one generating less international network traffic which is expensive (not directly for you but for ...


0

I updated the PPA list to the bare minimum as shown: Then ran the following commands: sudo apt-get update apt-cache showpkg linux-headers //select the latest kernel from the list sudo apt-get install linux-headers-4.1.0-3-generic linux-image-4.1.0-3-generic --fix-missing


-1

Windows 10 will overwrite your GRUB, but you can simply recover it with a live CD. Boot from live CD and open a terminal after upgrading and run "sudo fdisk -l" and remember the device your system is installed on. Not the partitions but the whole disk. It is usually /dev/sda or /dev/sdb. Then run "grub-install ".


0

It looks like my Broadcomm Wireless drivers do not play well with latest Ubuntu 14.04 updates. I just removed debian packages bcmwl-kernel-source and dkms. The packages might very well run fine, but apt-get upgrade hangs, and I don't want to to deal with contantly freezing updates. Now I can run 'sudo apt-get dist-upgrade' and smooth sailing.


0

This (the syntax error) is caused by a Python version mismatch, as the syntax has changed between Python 2 and Python 3. Another user with the same problem had manually installed a newer version of python (version 3.2; the version installed through packages is 2.7) and he redirected /usr/bin/python to python3.2 -- a bad idea. Restoring the original link of ...


0

I figured it out! It turns out my gnome-terminal was somehow outdated, even after running apt-get upgrade several times. I found this out by running apt search gnome-terminal, which gave me the following output: $ apt search gnome-terminal Sorting... Done Full Text Search... Done gnome-terminal/vivid 3.14.2-0ubuntu3 amd64 [upgradable from: 3.6.2-0ubuntu1] ...


-1

sudo dpkg -P unity-scope-gdrive sudo dpkg -P account-plugin-google sudo dpkg -P account-plugin-facebook sudo apt-get install -f


0

Like described in How to get to the GRUB menu at boot-time? you can access the GRUB Menue by pressing shift - there you should be able to select prior installed and not removed kernels...


0

Select Advanced options for Ubuntu from GRUB boot menu and choose kernel 3.19.0-25.


0

This is a pretty old question, but I recently ran into the same exact problem. Looking through the running processes I noticed /bin/sh /etc/init.d/lirc stop in the list. I killed that process (sudo kill <pid>) and the upgrade picked right back up.


2

I'd recommend sticking with 14.04 LTS. The LTS stands for Long Term Support, which means that issues with software and security vulnerabilities will be fixed and maintained for 5 years, so until April 2019. The next LTS release will be in April 2016, otherwise the standard support period is 9 months. So if you chose 15.04, you'd ideally want to move to ...


0

Ubuntu 14.04 is an LTS -- Long Term Support -- release. As such, it will be serviced at least until the next LTS verion is released (likely 16.04, based on past history). Given support expires much more quickly (one year from release, as I recall) for non-LTS versions, if you don't want to upgrade every few months, you may want to stick with 14.04 for the ...


2

This bug has been fixed in fglrx-updates_2:15.200-0ubuntu4.2 for Ubuntu 15.04 and fglrx-updates_2:15.200-0ubuntu0.5 for 14.04. It has been released already. Just wait till this version appears in updates. The package can be downloaded not from HERE This is the Bug report.


0

I came across the the exact same problem today and it is actually very trivial. Cause there are both python2.7 and python3.4 resided in my system, for some packages I had to install both versions for python2.7 and python3.4. Sometimes I explicitly edit ~/.profile to set the $PYTHONPATH. Yesterday I changed my $PYTHONPATH to point to 2.7/site-package to do ...


0

Upgrading may mess with your grub so be prepared to do a boot repair. Otherwise it wont mess with your pre-existing partitions as windows doesn't even recognize the ext4 format.


1

Before you start, try to delete unneeded packaged using : sudo apt-get autoremove Now, you have to install all dependencies packages using : sudo apt-get update sudo apt-get install -f After that, try to install updates using : sudo apt-get upgrade


1

Use the main server instead of http://in.archive.ubuntu.com/ubuntu/ sudo sed -i 's://in\.://:g' /etc/apt/sources.list sudo apt-get update or change the server via Software & Updates. Select Main server for Download from: Install the correct version of libuuid1:i386 sudo apt-get update sudo apt-get install libuuid1:i386=2.20.1-5.1ubuntu20.6 But ...


0

Determine why your pen and digitizer work now - what software supports them, and how that software is configured. Read the changelogs for your target Ubuntu version, and see if the supporting software is mentioned. If so, read very carefully.


0

Maybe grub is configured badly: Create a super grub2 disk (http://www.supergrubdisk.org/super-grub2-disk/) usb drive. Boot from the usb drive and try to start ubuntu. If it works, run update-grub and try booting without the usb drive.


1

Obviously the package's name and meta information both tell apt-get that it is a 32bit package, but this was set up falsely by the maintainers. Until they have fixed this and updated their repository with a real 32bit package, I use the following script to verify the package's true architecture: #! /bin/bash dir=$(mktemp -d) debfile="*_i386.deb" cd "$dir" ...


0

I solve it this way! because the apt-get * cannot do anything in my case, I use to remove myql-server and mysql-server-core by following commands. (Note that this way not mentioned in any of simillar questions!) dpkg -r mysql-server-core-5.5 dpkg -r mysql-server-5.5 then the mysql is gone without altering other packages that depend on them! now install ...


1

The do-release-upgrade script has a --sandbox option which performs the upgrade on an aufs overlay filesystem. This means that all changes are written to a separate filesystem overlaying the original files. Throw away the overlay and you are back with your original filesystem. Disclaimer: I don't have first hand experience with this feature. Regardless of ...


1

do-release-upgrade will carry out a release upgrade but do-release-upgrade doesn't have a dry run option. But, it does have a --sandbox option. From the point of running in --sandbox mode, any changes made to your system will actually be written to a ramdisk, and reset upon reboot via the magic os Aufs. This lets you test your machine thoroughly in a fully ...


0

I found that "broken" packages were causing problems with the upgrade. My packages (gnuplot) weren't explicitly broken (checked by looking in Synaptic package manager), but were marked to not be upgraded. This type of package will also cause the upgrade to crash; they can be found in the Synaptic package manager by filtering for "Installed (upgradeable)". ...


0

What you want can't be done. What you should be doing instead is installing your custom apps in a chroot stored in your userdata partition, and leave the root partition alone. Doing otherwise compromises in fact you receiving official updates on your phone.


0

FTR, running: dolphin camera:/ Lets me grab files off my camera, it just wont show up in dolphin without that command line.


0

At the start, press shift to enter the grub menu. Then press e to edit the grub commands. For the argument linux in the grub remove "quiet splash" and replace it with "text". For example: linux /boot/vmlinuz-3 ..... root=UUID=d1f1 .... ro quiet splash $vt_handoff Should be edited to: linux /boot/vmlinuz-3 ..... root=UUID=d1f1 .... ro text $vt_handoff ...


1

From what I could read from your paste it appears your Windows got hibernated at some point: 534: Metadata kept in Windows cache, refused to mount. and consequently os.prober could not detect your Windows installation (line 564). 564: 1 disks with OS, 1 OS : 1 Linux, 0 MacOS, 0 Windows, 0 unknown type OS. So in order to quickly get a running system ...


-4

Should not be a problem for Win-Home Users to always "dist-upgrade", but if you are running complex systems, you better "never (really) change a running system"... Even if there "should" be no problem, there "could" be probs - what'll cut you off! YOU should be the one who has the right 2 decide ;-)


0

You'll probably need install a version of a Ubuntu that supports 3.14 then (i.e. 15.04). Alternately, you could work your way through redoing versions of the relevant packages from source so they don't break 14.04 (probably very difficult), or redo the theme to work better with older versions Also, installing Gnome/gtk 3.14 in 14.10 (and probably 3.12 in ...


2

You should install the GNOME desktop again. ppa-purge removed the GNOME packages and if there is no equivalent packages in the repositories, it downgrades nothing. Therefore sudo apt-get update sudo apt-get install ubuntu-gnome-desktop


0

You have to reinstall GNOME to available version, sudo apt-get update sudo apt-get install gnome-shell sudo apt-get install ubuntu-gnome-desktop Remember to choose LightDM when prompted for it during the installation. Use Tab to move between the choices and Enter to confirm your selection. Once installed, log out of the system and click on the Ubuntu ...


3

There is no specific upgrade procedure from 14.04.1, 14.04.2 to 14.04.3. If you do routine upgrades, your version will be automatically switched to 14.04.3. There are new kernel and graphical stack introduced in 14.04.3. But they are mainly needed to support new installs on new hardware. Hardware Enablement Stack The old installations are fully ...



Top 50 recent answers are included