Accidentally while working on ubuntu 14.04 fired a command sudo rm -rf * and suddenly everything stopped working.
When I restarted then grub rescue started coming with above error in black screen while starting laptop..!!
Any clue wha happened and can be done ...?
Related
Recently I tried to run opera but nothing happened. So I tried to run it on terminal and got this error
cannot open /proc/self/cgroup: Permission denied
But I tried other snap apps such as code, it works fine,
and also recently saw a forum post that someone has the same problem with another browser.
Is it to do with the latest snap update on Manjaro? Or how do I fix it
I was also experiencing this issue yesterday. My Plex went down during the day and I wasn't sure why. I found the error you posted when running:
sudo snap logs plexmediaserver
Rebooting my whole server fixed the issue.
On Ubuntu sudo dpkg-reconfigure apparmor solved my problem.
From this askubuntu answer. Perhaps it's worth a try, even on manjaro.
I am new to Ubuntu 18.04. It has been a long time that I have not updated anything new on my current OS which is Loki (interestingly, besides Loki does not allow ppl to upgrade Juno).
For some reasons, I have to install another Linux OS on my machine, which is ubuntu 18.04 - the minimal installation. Although everything works perfectly to Ubuntu, it makes me cannot log in to my main OS.
Description of an issue: After selecting a boot of elementary, I log in my account on a log-in page of Elementary. It does not show anything else and move back to the log-in. Another try with a guest account (with no password), still the same problem.
Because most of my data and work in Elementary, I have to find a way to solve this problem. Is there anyone here giving me a hand? Thank you very much.
I ran into same problem once.
Login into tty mode by Ctrl+Shift+F1,and enter:
sudo dpkg --configure -a
sudo apt-get install ecryptfs-utils
sudo reboot
And I was able to login
Trying tty mode by Ctrl+Shift+F1, I was able to log-in in a terminal. Turn out that the Ubuntu has used almost the left memory to load an OS. By removing some files by the command rm -rf [filename] to release around 2GB, I was able to have everything back. It was freaking for a while. Phewww...
I keep getting this error when I start Android Studio (AS) (I am not running Eclipse). I am running Ubuntu; I did a fresh install of Ubuntu and AS and this happened upon start up:
ADB not responding. If you'd like to retry, then please manually kill
"adb" and click 'Restart'
I have tried this solution: ADB Not Responding - Wait More or Kill adb or Restart (Ubuntu 13) 64-bit
and this: Adb not responding with android studio on Ubuntu as well as the duplicate link that follows.
I tried making an AVD and it doesn't want to run on there. I double checked that ADB is added to my PATH.
Is there more information I can provide? Any response with information or questions is helpful.
In a terminal, type ps -u (your username), find the pid, and type kill -9 (pid). If that doesn't work, use a higher number, such as kill -15 (pid).
When this happens to me I usually do ps -ef to find out adb pid, and then kill -s 15 <adb_pid>. After that everything works fine.
On my Linux Mint 13, if I try to debug my Qt application, I see in the output:
&"warning: GDB: Failed to set controlling terminal: Invalid argument\n"
If I try to break execution, I see in the status line: Stop requested... , and after several seconds: Attempting to interrupt. That's it, nothing more.
I've seen some old questions related to similar issue, and I found the only answer here, but it doesn't work for me, unfortunately: I have created file /etc/ld.so.conf.d/Qt.conf with the following contents:
# Qt libraries
/opt/Qt5.2.1/5.2.1/gcc/lib
But nothing changed.
UPD: After Qt Creator restart, behavior changed a bit: now it stucks on the "Setting breakpoints..." stage, and after 40 seconds shows this message:
The gdb process has not responded to a command within 40 second(s).
This could mean it is stuck in an endless loop or taking longer than
expected to perform the operation. You can choose between waiting
longer or aborting debugging.
I also upgraded gdb to latest 7.7: I installed libncurses5-dev package: sudo apt-get install libncurses5-dev , which is needed to build gdb.
I downloaded latest gz archive from http://ftp.gnu.org/gnu/gdb to the temporary folder, and executed the following commands:
tar xvfz gdb-*.gz
cd gdb*
./configure
make
cp gdb/gdb /usr/local/bin
I also set up my Qt project to use gdb from /usr/local/bin . It is used now, but nothing is changed.
By the way, in Windows it works. How to solve it in Ubuntu 12.04 (Linux Mint 13)?
I have Ubuntu, version 12. I installed ATI driver and I'm getting an error running in low graphics mode.
I needed to install the driver because every time I update or upgrade Ubuntu, right after installing the packages the system runs in low graphics mode.
The answer here also couldn't help me.
Graphics card model: ATI Radeon HD 3600
Installing fglrx also didn't help. The ATI driver is still installed and it still runs in low graphics mode. What should I do?
First, you should understand that your graphics manager is messed up and that is what you want to fix. Now; here is a solution to your problem:
Here is a simple guide showing you how to do it step by step:
A step by step guide to fixing "your system is running on low graphics"
When you turn off your computer, reboot and hold these three keys:
CTRL + ALT + F1
This will open the terminal where you can enter commands that I am going to show you below:
sudo apt-get update
Next enter the following command:
sudo apt-get -d install --reinstall gdm
Next enter the following command:
sudo apt-get remove --purge gdm
Next enter the following:
sudo apt-get install gdm
Almost done; When asked to choose, please select GDM and then finally:
sudo reboot
That is all you need to solve this problem!
Ok. Let me try to help you :D
-Go to Recovery mode
-Enable network (so you have internet connection)
-Go to Root option (Recovery mode)
-When you are in terminal delete lightdm type without brackets {sudo apt-get remove --purge lightdm}
-Then type without brackets {sudo apt-get install lightdm} (wait to install it)
-Then type without brackets {sudo service lighdm start}
-When it's finished type exit (you will get back to Recovery console)
-Then go on third option dpkg (Repair broken packages)(confirm with Y)
-When it's finished with installing packages type without brackets {sudo reboot}
-After reboot you will have back your Ubuntu! :D
I solve this problem after 1 day... Im a new user :D
Almost forgot i have Ati Radeon HD6770 graphic card, if you have Nvidia try it... Hope this was helpful!
Another possible issue could be installing new programs in bin. I am not sure if that what is causing you the problem but I faced this issue because of the same issue. If I understand correctly, bin is supposed to contain only executables. By mistake I moved a whole big program to bin and when I restarted the system, I saw this error. A simple solution that I found is the following. Say you have moved the big folder ABC to bin.
Start terminal by typing Ctrl+Alt+F1 and login with your username and password.
Login to root by typing
sudo su
and providing password.
go to bin by typing
/usr/bin
type
ls -lrt
This last command will show all the files chronologically. See last few of them. One of those, say ABC, must be the one that moved by mistake to bin.
Remove that by typing
rm -r ABC
and then restart by
sudo reboot
And you get your graphics back!
You can try and turn off the switchable graphics in the BIOS:
after that, it will be possible to use the Intel video card only with proper drivers on Ubuntu.
Here is the source: http://thegeekyland.blogspot.com/2014/07/ubuntu-1404-lenovo-g510.html
In any ubuntu OS version 12.04,14.04 configured with the old graphic card ATI/RS690
change the setting as below
etc/default/grub/
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset "
sudo update-grub
Restart