I use lxde on Gentoo.
Versions of software:
lxappearance 0.5.2
lxde-common 0.5.5
lxde-icon-theme 0.5.0
lxinput 0.3.2
lxmenu-data 0.1.2
lxpanel 0.5.12
lxrandr 0.1.2
lxsession 0.4.6.1
lxsession-edit 0.2.0
lxshortcut 0.1.2
menu-cache 0.4.1
Time to time lxde exits from session to the session manager (I use slim-1.3.5). After it items reboot and halt disappear from the Logout menu and ck-list-sessions shows two sessions: one active and one not active.
System log near the problem: http://vpaste.net/zOZFl
The question is where can I try to look for the reason of this problem? Where does lxde store logs?
Check /var/log/Xorg.0.log.old for errors. It may be the X server that is restarting. Failing that, try starting X from the console using startx. You'll need to stop /etc/init.d/xdm first. If it still boots you out, you'll probably see some useful output. As a side note, I found slim to be a little unreliable but it's been a while since I tried it. I use lightdm now instead.
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%
Perhaps this problem is specific to upgrading an Ubuntu 12.04 that is using tftp-hpa as part of a standard LTSP installation. After upgrading to 14.04 using do-release-upgrade the tftp-hpa daemon failed to start in a confusing way.
Using either systemV or the upstart method it pretended to start (it would complain if I tried to start it again without first "stopping" it) but no daemon appeared in the ps listing AND any attempt to download something via
tftp localhost generated a time out.
(Posted as an answer on behalf of the OP).
I traced the problem to the --address flag by attempting to start the daemon by hand. It worked if I left out the --address flag altogether but refused to start with any of the standard "0:0:0:0:69" like constructions.
Since "--address TFTP_ADDRESS" is baked into the the upstart script,
it did not work to remove TFTP_ADDRESS entirely from /etc/default/tftp-hpa. However setting
TFTP_ADDRESS :69
in /etc/default/tftp-hpa seems to have solved the problem.
Also, the upgrade from 12.04 to 14.04 left /var/lib/tftpboot owned by root, which generated the complaint
in.tftpd[3084]: cannot set groups for user nobody
in syslog.
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!
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.