I just undeliberately deleted my bin/tempfile, please don't ask why.
I experienced no issues, however, after a reboot, I wasn't able to login anymore. When I entered my password and pressed ENTER, I got a black screen, and 2 seconds later the login screen appeared again.
My system is Kubuntu 17.10 on 4.14.11 Kernel.
I did some research on it, but I still got no clue what this file does, or how I can restore it (it was deleted by rm).
Until now I did the following:
touch /bin/tempfile
chown root:root /bin/tempfile
chmod 755 /bin/tempfile
Finally I got back into KDE, and everything works fine this far, except an error, which I receive immediately after logging in: Xsession: Xsession: Warning: unable to write to ; X session may exit. The message is not in the style of my normal KDE desktop windows, it looks like a very old design, because the message probably comes from X itself. (I have no clue about this, sorry if it's rubbish)
In your case you can easily fix your issue by executing the following command:sudo apt-get --reinstall install debianutils.
Hope this helps.
Related
I am getting this error as:
apt-get: error while loading shared librarie: libz.so.1:cannot open shared object file: No such file or directory
When trying:
sudo apt-get zlib1g
I'm using a Ubuntu 16.04 os and i can't log into the graphic interface, after booting I can only see a blinking underscore on the top left corner of the screen, so i pressed "alt+f4" to open a terminal session.
In my commands historical I found the command:
rm -rf zlib-1.6.37
(That command was executed from the root directory of my user.) And i don't know if that is the cause.
I do need some solution to thia problem as soon as possible please.
If you need some more info just ask for it, I will reply with the answer as soon as I can.
Ok, I've figured it out, it was quite simple, but i just got desperate
The solution was just to recreate the symlink that was damaged (libz.so.1) and that fixed the problem, now I have another issue, it seems like I'm connected to network but i don't have internet at all anyway that's for another question.
Thanks if somebody tried helping me, even if the question just have like 2 hours from posted.
Alright, just a disclaimer: I've been using some version of Unix or Linux for 30 years, I have good working knowledge, but when it comes to administration I'm enthusiastically dangerous :)
Every time I do the automated OS upgrade in Pop!_OS something bad happens. And I am not talking about apt update / apt dist-upgrade. I do mean going into the settings GUI and in the last item on the list clicking "Upgrade".
Last machine I did it on failed and I couldn't recover the system, not even from a bootable stick. That machine was on it's last leg, I just let it go and built a new box, it was time. Well here we are again, time for an upgrade to 20.10.
I hit "upgrade os" (maybe it's "update os" I don't remember exactly
It did some stuff, and said it needed to restart - Okay so now we're windows? Not thrilled
Restart and end up at a gray screen where it sat at 0% progress bar for the update
I let it sit a good long while, maybe 45 minutes, I was worried this mid-low range machine was just taking a while, nothing
Cringe.. hit the reset button, the system rebooted and did "something" and then came up seemingly okay
Now here's the problem list:
Did the upgrade happen fully, completely, and successfully? How can I tell? This feels like I'm running windows and just rolling in the blind mystery..
VMWare Workstation wont launch. Nothing happens with icon click, from command line I get this error:
/usr/bin/vmware: line 105: 159580 Segmentation fault (core dumped) "$BINDIR"/vmware-modconfig --appname="VMware Workstation" --icon="vmware-workstation"
Searching online a bunch there was a lot of talk that there may be permission problems after upgrade and running it as root would help. This did not work. I read that upgrading to VMWare 16.x will help. I'm open to it, but on principle WHY does this have to be the case?
I use another app that is installed from source, it's called MakeMKV. I've had no trouble with it until the Pop upgrade. Again, it doesn't launch from the icon. I rebuilt and reinstalled it. No go. Launching from command line returns:
/snap/makemkv/217/bin/desktop-launch: line 51: /home/ritchie/.config/user-dirs.dirs: Permission denied
qt.qpa.screen: QXcbConnection: Could not connect to display :1
Could not connect to any X display.
Launching from the command line with sudo worked though! So wtf?
This feels like a key piece of the puzzle, that bit about not being able to connect to the display.
Since this post is so long I wont list the hardware, but am happy to if it helps diagnose.
Any help is appreciated!
got the same with other snap packages...
tried to figure out what's wrong...
looks like some ENV variable is not set properly causing the error:
.config/user-dirs.dirs: Permission denied
but simply reinstalling the package resolves the issue:
sudo snap remove %package%
sudo snap install %package%
After starting "anaconda-navigator" with a terminal, it ends up with dialogue box prompting that " it can't be run with root privileges.anaconda-navigator startup error as root.
For anaconda-3 run:
source ~/anaconda3/bin/activate root
anaconda-navigator
Hopefully this will solve everything.
I have exactly the same issue that you have and after trying the shocking solutions provided i ended up with more errors as you can find in some of my comments there.
How to Fix this:
The dialogue box as you and I see it, is a common dialogue in the Linux world, it has only one reason and that is your GUI is logged with a "normal user" but somehow you managed to install the anaconda with superuser(root).
so if possible, head to your login section and login with root user + with GUI activated(only saying this because there's a big Linux world out there)
if this didn't help, re-install it but be careful when uninstalling it as python can mess a lot of things up(its an OS bomb actually).
How to prevent this:
1- do not allow Anaconda installation to use any superuser areas like /root
2- try to install it with normal user and with sudo command
Good luck (the thing we all need with python installers)
The installation process should be done with the regular user but no root. In my case, the problem appears when I installed with superuser session. I follow these instructions, installing just with my username (without sudo privileges) and the problem was solved.
In /home/user/anaconda3/lib/python3.7/site-packages/anaconda_navigator/app/start.py:
if (MAC or LINUX) and os.environ.get('SUDO_UID', None) is not None:
Since last day I am getting issue(see link) with the Upwork. Many times I have reinstall the Upwork and restart the system but nothing goes happen.The network connection is also fine.I google but got nothing helpful. Anyone can suggested me how can I fix the issue. and make the Upwork run correctly.
As I remember the Upwork is running fine, I am getting the issue, since I run the command 'sudo restart lightdm' to display time on menu bar.
Please follow the below link and steps to fix up-work issue.
https://community.upwork.com/t5/Freelancers/Error-Message-THERE-WAS-A-PROBLEM-LOADING-UPWORK/td-p/83016/page/3
sudo dpkg -i libnss
wget http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3_3.19.2-1ubuntu1_i386.deb
sudo dpkg -i libnss3_3.19.2-1ubuntu1_i386.deb
Upwork fixed.
Note : These issues we are getting if we do not close the up-work properly while shutting down the operating system. Please remember this things.
I try to auto start a python script at startup, then reboot my Raspberry Pi to see if it works.
sudo nano /etc/xdg/lxsession/LXDE/autostart
Instead of a normal desktop display, I get a blank screen open box that can only open the menu by right click. So I tried to delete the code I have implemented on start up then reboot again, but the same thing happens. I uninstall open box hoping that it would solve the problem, but I still get the blank screen and the mouse cursor becomes an "X" icon. Has anybody encountered this problem before?
I had a similar problem with my Pi and, after checking the link provided by Matt (lxde wiki), I found what the problem was and the solution.
I had 2 autostart files:
Global commands:
/etc/xdg/lxsession//autostart
Local commands:
~/.config/lxsession/LXDE-pi/autostart
And, according to documentation "If both files are present, only the entries in the local file will be executed."
And my local file was empty.
After deleting the empty file, LXDE desktop was back and no more black screen.
The blank screen open box is the default openbox theme (for lack of a better word). Openbox is required for lxde so you should reinstall that first. To autostart something in LXDE you can create desktop files in your ~/.config/autostart directory (according to the lxde wiki) to avoid messing with the autostart file
Try reinstalling openbox and returning the /etc/xdg/lxsession/LXDE/autostart to the way you found it and see what happens. You might have accidentally messed up another autostart command
I went into ~/.config/autostart and found a file named lxde.desktop which I edited and commented out (using #) a line that began with something like OnlyShowIn or something similar. (After a reboot that line disappeared so I don't remember exactly what It was, It "could" have been NotShowIn but I thought it was something different)
After a reboot my desktop came back *fine!
*I had a bunch of GDBus.Error:org.freedesktop.PolicyKit1 errors which I cleared up by typing lxsession-edit in a terminal window and then unchecking LXDE and rebooting
If you figure out my "OnlyShowIn" confusion - please comment to clear it up for myself and others
I experienced same behavior, and found the following mistake I made:
I ran:
sudo dd bs=1m if=raspbian.img of=/dev/disk2 conv=sync
but I accidentally omitted the r before disk2
I Reran:
sudo dd bs=1m if=raspbian.img of=/dev/rdisk2 conv=sync
and it booted up properly.
The successful boot on Pi showed a blue square immediately saying "reformatting disk".
My solution was to format the SD card with the ZIP file directly instead of the IMG file found inside after extraction. I got the zip file from the Raspbian download page found here:
https://www.raspberrypi.org/downloads/raspbian/
With an SD card formatted from the ZIP rather than its contained IMG, my operating system is loading as expected.
This solution was applied in Mac OSX using Apple Pi Baker software and the above linked image.