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%
Related
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.
The Ubuntu 16.04 freeze by itself especially when 2-3 instance of Pycharm is actively running.I wanted to know the exact cause of the OS freeze and found linux-crashdump.
The linux-crashdump was installed using the link [kernel-crash-dump][1]
[1]: https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html "kernel-crash-dump"
It states that after installation and rebooting the system
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-17-server root=/dev/mapper/PreciseS-root ro
crashkernel=384M-2G:64M,2G-:128M
But cat /proc/cmdline is not showing the parameter crashkernel added to it.
I am not able to edit the /proc/cmdline in anyway.
If I add crashkernel=384M-2G:64M,2G-:128M then the error appears.
"/proc/cmdline" E667: Fsync failed
WARNING: Original file may be lost or damaged
don't quit the editor until the file is successfully written!
I am not able to move further, as per the documentation of kernel-crash-dump after the installation, I rebooted the system, but still the crashkernel parameter in the /proc/cmdline is not appearing.
I didn't get completely what the problem was but as far as I understood you had problems with crashkernel. I think that it would help if you just remove it completely and reinstall it again, because you have lost some of the files of crashkernel and that's why it's not responding. Hope it helps :)
I am a linux noob trying to setup openbox on an arch linux base. I am trying to get it as lightweight as possible in terms of resources used.
My final plan is to use openbox, with tint1 and conky.
however I am having an issue getting openbox to start. I have followed numerous guides and am struggling to figure out the problem.
I have so far installed the following (and done this config)
openbox (installed default option with the extras asked for)
create ~/.conifg/openbox
copied, rc.xml, menu.xml, autostart, environment to the above location
pyxdg
xorg-xinit
xorg-server
this didn't work so I the installed the full
xorg
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
I have had a look at the attached log file, but I don't know enough to be able to interpret it properly.
log file: https://www.dropbox.com/s/r76fowkooi822y9/Xorg.log?dl=0
I would appreciate any assistance.
Thanks
Steve
still nothing, although when I try to run startx the screen goes black for a second as though it is trying, but then goes back to text mode saying it has failed.
what is it saying?
There is only one error: (EE) open /dev/fb0: Permission denied, try starting your environment with the same configuration as root - just to see if it works. Maybe its a problem related to rootless X.
Have you configured/checked your installation (xserver, graphics driver, xinit config) using the following guides?
https://wiki.archlinux.org/index.php/xorg
https://wiki.archlinux.org/index.php/xinitrc
Try to start a minimal X (As described in the xinitrc article) to see if your xserver and graphics driver is working correctly.
I have been working with linux's version of XAMPP (named LAMPP) for about 3 months now and up until tonight XAMPP has worked fine, but suddenly when I tried to run the command
sudo xampp stop
it gave me this error message:
XAMPP is currently only availably as 32 bit application. Please use a 32 bit compatibility library for your system.
and since then any time I try to run any of the following commands:
sudo xampp start
sudo xampp stop
sudo xampp restart
I get the same message
I want to know why I got this message because xampp has been working flawlessly up until now and in fact, less than 30 minutes ago, I typed sudo xampp start and xampp started up normally and I was able to access localhost/phpmyadmin/
Here is some other info that may be useful:
-My OS is Arch Linux
-I am using the xfce desktop environment
-In the time between starting xampp successfully and trying to stop xampp when I got the error message above, I was trying to get the php mail() function to work by following the steps on this page http://www.absolutelytech.com/2010/07/18/howto-send-emailsusing-mail-function-from-localhost-in-php-through-msmtp-using-gmail-account-on-linux/ and I had just successfully finished step 1 and successfully sent the test email to myself.
-also, when I first got the aforementioned error message, I was still able to access pages via localhost (for instance I had a php file at /opt/lampp/htdocs/Brown/index.php that I could access successfully by typing localhost/Brown/index.php even after I was getting the error message) but then I tried to restart my computer to see if that might fix the issue and now I can't start xampp to begin with.
Please someone help me with this and feel free to ask any follow-up questions if that will help
I figured out my own issue. For anyone who sees this question, I had made a few changes to my php.ini file in attempts to get php's mail() function to work and I wanted to start fresh, so I moved php.ini to php_old.ini and copied a file named php.ini-pre1.7.2 to php.ini thinking that php.ini-pre1.7.2 was a file containing the default configuration of php.ini in case one might want to roll back to the defaults, but instead it is something entirely different. My issue was completely fixed when I moved php_old.ini back to php.ini
2021 and the same happened to me after trying to match php.ini seetings between a Windows environment and a Ubuntu 20.04 one. Everywhere I saw it told me to comment a section in the /opt/lampp/lampp file but it messed up my installation and I lost track of what was wrong. After re-installing LAMPP I matched the settings one by one restarting with sudo opt/lampp/lampp restart at each modification. The culprit was:
browscap="C:\xampp\php\extras\browscap.ini"
This line has to be stay commented (just put a semicolon at the start of the line), if you need it then this workaround may help you. Cheers!
Currently running: Arch linux 4.0.7-2
I've worked with X11 for a while without any trouble. Until recently after a reboot the following error came up: No screens found. I looked up similar questions but none of them had the answer required. I tried to remake my configuration file but that wasn't possible either due to Number of created screens does not match number of detected devices. Configuration failed.
I spend hours trying to find a fix but nothing worked, I tried re-installing every single package I had and removed everything to bare. Unfortunately no luck.
I then went and reinstalled entire Arch linux but to my surprise the first error to appear when trying to make a configuration file was No devices to configure. Running startx however gives me a set of floating terminals but freezes entirely.
lspci -vvv http://ix.io/juQ
/var/log/Xorg.0.log http://ix.io/juR
I'm kind of clueless right now. Any help would be much appreciated.
I think that the problem is located in that line of your log:
[ 355.070] (II) Loading /usr/lib/xorg/modules/drivers/i740_drv.so
[ 355.079] (EE) Failed to load /usr/lib/xorg/modules/drivers/i740_drv.so: /usr/lib/xorg/modules/drivers/i740_drv.so: undefined symbol: I740_Sync
It seems that this file is missing, googling a little i found that archlinux forum post, that probably will help you:
https://bbs.archlinux.org/viewtopic.php?id=176555
What you need to do, is simply run that command:
pacman -Sf `pacman -Qqet`
And maybe it solve the problem (there are no more answers to that post, so i'm not sure if it works)