If I'm installing any program via ports, and my screensaver starts, or goes into sleep mode, gnome will suddenly stop functioning properly. If I move the mouse/press a key, the screen will flicker from black to wallpaper(no icons panels displaying). If I force a shutdown and restart gnome does not start, I can log into the system through terminal. I also get the following error saying Libpcre.so.0 can't be found. Anyone else have this problem / know how to fix it?
For the libpcre problem i suggest to use libchk (sysutils/libchk). It checks which programs link to unresolved libraries. Reinstall those ports.
Related
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%
I am having a problem using terminal in a Linux VirtualBox Terminal. This terminal is being used to compliment the StanfordOnline "Compilers" course on edX, the language for the class is called "cool".
Within this terminal I used the command "emacs 1.cl" in order to open the file "1.cl" with emacs. After I enter this command the file is successfully opened but the command prompt does not reappear, instead everything I type is just greyed text (see screenshot - Terminal is black window on left).
Why is this happening? I can start typing commands again if I close and then re-open terminal, but I think there must be a reason why this happens. Anyone have an idea?
Thanks in advance, let me know if I can provide any more helpful information regarding the course or the software. Running VirtualBox on MacOS Catalina 10.15.4 if it makes any difference.
-DR
Screenshot
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 a BeagleBone - no LCD/display. In the console when I try and use startx, it says /dev/fb0 doesn't exist. The xorg.conf file is using the fbdev driver. Apparently, if an LCD is detected, everything works.
How can I setup a virtual display so I can vnc to it?
Thought I better answer this for reference. Oh, I also got the 'Tumbleweed' badge... Great...
If no LCD/DVI cape is attached, then the boot doesn't load a frame buffer (/dev/fb0). As such, no X11 server starts up. x11vnc requires a real X11 server to be running for it to work. There is also the program xvnc which can create a virtual X11/frame buffer on your behalf, but I couldn't see it in the Angstrom packages.
So, I installed Xvfb - and created a virtual frame buffer. Install the package
xserver-xorg-xvfb
When starting, keep in mind (for the newbies like me coming from Windows), it is case-sensitive. To create a virtual X11 server;
Xvfb :1 -screen 0 1024x768x16 &
When you do this, you will probably get these errors;
(EE) AIGLX error: dlopen of /usr/X11/lib/dri/swrast_dri.so failed (dlopen(/usr/X11/lib/dri/swrast_dri.so, 5): image not found)
(EE) GLX: could not load software renderer
So, load the package;
mesa-dri-driver-swrast
OK, error gone. Now we can export our display (an environment variable so Firefox, or whatever X11 client you run, can attach to the display).
export DISPLAY=:1
Load up Firefox (something to see)
firefox &
And now we try and start the x11vnc;
x11vnc -display :1 -bg -nopw -xkb
At this point, with this distro, you'll see an error about XTEST not being found/not available when it was built. Here describes the issue.
I made sure that I had all the proper libraries installed, so I figured it must have been a bad build on Angstrom. So, now to build it myself. I ensured all required libraries were available; these are the ones ending with '-dev'; by default they all appeared to be available. I followed the instructions here.
Except the copy line didn't work too good for me, so do what you need to do to copy it to the /usr/bin folder.
Now it starts, and there are no errors about XTEST, and the input works!
I was trying to figure out how to run a program at boot, but after realizing this program is an infinite loop, I have no way of getting out, or back to the terminal. Right when I give the Pi power it just goes right to the program on a black background. I don't remember exactly what I did to make it run at boot, I believe I just added some code in a place right above something that said "exit 0" and below something that says "esac". I don't remember the command that even got me there. (I am new to the Pi and Python and have just been playing around..unsucessfully.)
If anyone could help me either delete this program or get me to be able to edit it so I can fix the infinite loop that would be great. I'd rather not have to completely over-write the sd card with a fresh raspbian. But like I said I can't do anything at boot, and Ctrl + C doesn't do anything nor Ctrl + Alt + Delete.
EDIT: When I put the SD card in my computer, I see a list of 11 files:
bootcode
cmdline
config
fixup
fixup_cd
issue
kernel
kernel_cutdown
kernel_emergency
start.elf
start_cd.elf
None of these mean anything to me...
Update: Looks like I failed to get that you want to interrupt the running bootprocess and stop the script.
The simplest idea would be to turn of the pi, unplug the sd card and plug it into your desktop, (re)move the script and boot again.
Processes spawned during boot are stored in scripts in /etc/init.d/.... These scripts are called by the init process, the first process on a Linux machine (PID:1)
But init starts not all scripts in /etc/init.d. This depends on the run level. On a debian system there are 7 run levels.
For every run level there is a folder called like:
/etc/rc0.d
...
/rc6.d
in which are softlinks to scripts from /etc/init.d are stored.
To remove a script from being executed on every boot you'll delete all links from that folders. Usually on debian systems this is done using the update-rc.d tool:
update-rc.d NAME_OF_INIT_SCRIPT remove
You should also have a look at the file /etc/rc.local
Alt + PrintScn + k to kill the process stuck running from rc.local
You can use the cmdline.txt.
First, add or modify the cmdline.txt file on your sd card. Add "init=/bin/sh", then restart your Pi, and you can see a command line prompt.
Type 'sudo nano /etc/rc.local' to edit the file, and comment or delete the line containing the error. After that restart.
I had exactly the same issue, couldn't quit the process using CTRL+C. I edited the cmdline.txt like stated above, but then the pi didn't load the necessary usb drivers for my keyboard.
So eventually I logged in over SSH to the pi, and modified my rc.local file that way.
In my case worked combination "Alt" + "F4", it stops the current session and opens the login screen
I had the same problem as explained at the beginning of this Post. My Python app was caught in an endless loop.
I tried the Ctrl+Alt+F2 Command as recommended in many posts found in Internet without any terminal window being open. Apparently, after many other trials and reboots I saw a glimpse of a Terminal window each time the loop of my application restarted. It was impossible to catch anything until I started recording the screen using the slow motion video of my mobile phone and, yes, a terminal window with the Linux prompt was active, and able to accept keyboard entries.
All I did was (almost blindly) editing the culprit file with the
sudo nano filename command
and entering some characters in order to actually corrupt such file, saving and closing it, a rebooting the Pi.
At the end of the boot, the file produced an error but the system kept ready to operate.
I was then able to fix the bug in a normal way.
It hope this may be useful to others. In my case it spared me of burning a new Raspbian and losing all my previous work.
I got myself stuck in exactly the same problem. Luckily I had the ssh enabled, apparently this is disabled by default on Raspbian Jessie, so this may not work for all.
The exit 0 is the line in /etc/rc.local where you would have added in the script that is now running in a continuous mode. If you can ssh into the Pi using Putty and the Pi's IP address then
sudo nano /etc/rc.local
Scroll down to the bottom of the file and remove the offending program, then sudo reboot
They way to prevent this issue from happening is to add an & (ampersand) to the end of the line to fork the process and run it as a separate process like so
python /home/pi/myscript.py &
as specified in https://www.raspberrypi.org/documentation/linux/usage/rc-local.md
The ampersand allows the command to run in a separate process and continue booting with the process running.