/home/pi/SysMaint/Dell64 session less than 10s.txt www.BillHowell.ca 09Apr2017 11:25 initial +-----+ 09Apr2017 11:25 https://forums.linuxmint.com/viewtopic.php?t=220578 Your session only lasted less than 10 seconds.. [solved] administrollaattori Re: You seesion only lasted less than 10 seconds PostSun Apr 17, 2016 4:44 am https://forums.linuxmint.com/viewtopic. ... 40#p805107 solved it by using: sudo services mdm stop startx rene Re: You seesion only lasted less than 10 seconds PostSun Apr 17, 2016 6:27 am It could help is we know how/when this started, but after you get that "Your session only lasted..." message it might be informative to switch to a virtual console (Ctrl-Alt-F4), log in on it and look at the X log with "sudo less /var/log/Xorg.0.log" and/or Xorg.0.log.old. At its end may be some indication of why things ended prematurely. Sometimes all there's to something like this is a typo in, if any such file, /etc/X11/xorg.conf, although the startx succeeding would seem to already refute that. But try and see. >>Howell - couldn't use the virtual consol - no login 09Apr2017 12:08 Just use the simple consol that I get cold boot -> Advanced options for LMDE2 -> recovery mode # services mdm stop No command 'serevices' found, did you mean: Command 'service' from package 'sysvinit-utils' (main) services: command not found # service mdm stop [ ok ] Stopping MDM Display Manager: mdm. # startx >> whole pile of output, last part I can see is : Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian Current Operating System: Linux dell64 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 ... xinit: connection to X server lost waiting for X server to shut down .error setting MTRR (base = 0xe9000000, size = 0x00e00000, type = 1) Invalid argument (22) (EE) Server terminated successfully (0). Closing log file. >> Error (EE) is a bit scary # sudo shutdown now >> It went to logon screen Same problem of "Your session only lasted less than 10 seconds."!!! >> Cold boot Your session only lasted less than 10 seconds. >> This doesn't solve the problem +-----+ 09Apr2017 11:25 https://forums.linuxmint.com/viewtopic.php?t=220578 Your session only lasted less than 10 seconds.. [solved] rene Re: You seesion only lasted less than 10 seconds PostSun Apr 17, 2016 6:27 am It could help is we know how/when this started, but after you get that "Your session only lasted..." message it might be informative to switch to a virtual console (Ctrl-Alt-F4), log in on it and look at the X log with "sudo less /var/log/Xorg.0.log" and/or Xorg.0.log.old. At its end may be some indication of why things ended prematurely. Sometimes all there's to something like this is a typo in, if any such file, /etc/X11/xorg.conf, although the startx succeeding would seem to already refute that. But try and see. >> cold boot -> Advanced options for LMDE2 -> recovery mode # sudo less /var/log/Xorg.0.log >> less didn't seem to work? # sudo more /var/log/Xorg.0.log >> nothing # sudo more /var/log/Xorg.0.log.old Markers : (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown >> Results (EE) extracted : [ 621.300] (EE) Failed to load module "nv" (module does not exist, 0) Howell note : nvidia loads seem OK [ 621.304] (EE) [drm] KMS not enabled [ 621.304] (EE) open /dev/dri/card0: No such file or directory [ 621.304] (WW) Falling back to old probe method for modesetting [ 621.304] (EE) open /dev/dri/card0: No such file or directory [ 621.304] (II) Module fbdevhw: vendor="X.Org Foundation" plusd teo more lines... [ 621.305] (EE) open /dev/fb0: No such file or directory >> Howell - tried twice in log [ 621.305] (EE) Screen 0 deleted because of no matching config section. [ 621.305] (II) UnloadModule: "fbdev" [ 621.305] (II) UnloadSubModule: "fbdevhw" [ 621.305] (II) Loading sub module "vbe" >> This seems to go OK [ 621.747] (EE) AIGLX: reverting to software rendering [ 621.305] [ 621.305] >> Check to see if I captured all errors (EE) # sudo more /var/log/Xorg.0.log.old | grep '(EE)' >> OK, I caught them all above NUTS!!! I did : $ apt-get install xterm >> Selected messages : Reading package lists... Done ... The following NEW packages will be installed: xterm ... The following packages were automatically installed and are no loger required: libdune-pdelab-2.0.0 libdune-typetree-2.3.1 libdune-typetree-dev libgmp-dev libgmpxx4ldbl >> Hovever, Dell64 couldn't connect with 'ftp.us.debian.org', >> so I don't think that anything happened +-----+ 09Apr2017 11:25 https://bugs.launchpad.net/ubuntu/+source/apt/+bug/180160 jz (jzhu4) wrote on 2008-01-04: #4 Hi- I found the solution http://www.linuxdiyf.com/bbs/archiver/tid-68799.htmlwhich is a Chinese forum. I did as follows: $ ldconfig -p |grep libstdc++ libstdc++.so.6 (libc6) => /usr/lib/libstdc++.so.6 libstdc++.so.6 (libc6) => /usr/local/lib/libstdc++.so.6 $ diff /usr/lib/libstdc++.so.6 /usr/local/lib/libstdc++.so.6 Binary files /usr/lib/libstdc++.so.6 and /usr/local/lib/libstdc++.so.6 differ The two files are different which means there are two different versions gcc in the system? I found a gcc directory under /usr/local Then : $ cat /etc/ld.so.conf.d/libc.conf # libc default configuration /usr/local/lib I added /usr/lib to the file and then run : $sudo ldconfig >> Howell 09Apr2017 11:25 $ ldconfig -p |grep libcrypto++ >> nothing $ ldconfig -p |grep libcrypto libcrypto.so.1.0.0 (libc6,x86-64) +> /usr/local/lib/libcrypto.so.1.0.0 libcrypto.so.1.0.0 (libc6,x86-64) +> /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 libcrypto.so (libc6,x86-64) +> /usr/local/lib/libcrypto.so libcrypto.so (libc6,x86-64) +> /usr/lib/x86_64-linux-gnu/libcrypto.so $ diff /usr/lib/libcrypto.so.1.0.0 /usr/local/lib/libcrypto.so.1.0.0 Binary files /usr/lib/libcrypto.so.1.0.0 /usr/local/lib/libcrypto.so.1.0.0 differ $ cat /etc/ld.so.conf.d/libc.conf >> same as example : >> I added /usr/lib to the file $ echo >>"/etc/ld.so.config.d/libc.conf" /usr/lib >> and then run : $sudo ldconfig /sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 is not a symbolic link /sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 is not a symbolic link >> Hmm, what do I do with that error? Ignore for now... $ sudo shutdown now 09Apr2017 12:04 cold boot >> This did not solve my problem! +-----+ 09Apr2017 15:05 http://askubuntu.com/questions/90915/troubleshooting-x-server-ee-failed-to-load-module-nv-module-does-not-exist troubleshooting X server. (EE) Failed to load module “nv” (module does not exist, 0) nv was an old open source driver for Nvidia cards, which is now deprecated. Make sure you don't have it in xorg.conf, or try blacklisting it with echo "blacklist nv" | sudo tee -a "/etc/modprobe.d/blacklist.conf". edited Apr 4 '12 at 21:29, fossfreedom answered Dec 28 '11 at 3:17, mikewhatever I ran the command above and there is zero change to my xinit output. – Paul Dec 29 '11 at 1:27 The command above add blacklists nv by adding it to blacklist.conf. Have you checked xorg.conf yet? – mikewhatever Dec 29 '11 at 1:43 xorg.conf was missing entirely. See update. – Paul Dec 29 '11 at 2:21 >> xorg.config - find can't find it anywhere, so this cannot be a problem >> IDIOT! it's xorg.conf >> still nothing +-----+ 09Apr2017 15:49 http://askubuntu.com/questions/704647/graphics-and-sleep-issues-on-dell-inspiron-15-uhd Graphics and sleep issues on Dell Inspiron 15 UHD [ 60.997] (EE) Failed to load module "nvidia" (module does not exist, 0) [ 60.998] (EE) Failed to load module "nvidia" (module does not exist, 0) [ 60.999] (EE) [drm] KMS not enabled [ 61.003] (EE) open /dev/fb0: No such file or directory [ 61.003] (EE) open /dev/fb0: No such file or directory [ 61.003] (EE) open /dev/fb0: No such file or directory [ 61.003] (EE) Screen 0 deleted because of no matching config section. [ 61.003] (II) UnloadModule: "modesetting" [ 61.003] (EE) Screen 0 deleted because of no matching config section. [ 61.003] (II) UnloadModule: "modesetting" [ 61.003] (EE) Screen 0 deleted because of no matching config section. [ 61.003] (II) UnloadModule: "fbdev" [ 61.003] (II) UnloadSubModule: "fbdevhw" [ 61.003] (EE) Screen 0 deleted because of no matching config section. [ 61.004] (EE) VESA(0): V_BIOS address 0xd00 out of range [ 61.004] (EE) Fatal server error: [ 61.004] (EE) no screens found(EE) [ 61.004] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 61.004] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 61.004] (EE) [ 61.004] (EE) Server terminated with error (1). Closing log file. /usr/share/X11.xorg.conf.d directory - 4 small files # Example xorg.conf.d snippet that assigns the touchpad driver # to all touchpads. See xorg.conf.d(5) for more information on # InputClass. # DO NOT EDIT THIS FILE, your distribution will likely overwrite # it when updating. Copy (and rename) this file into # /etc/X11/xorg.conf.d first. >> That directory doesn't exist on the Dell64 computer (nor on the raspberry pi ) ************************** 10Apr2017 10:45 Now that I've edited /etc/fstab and mounted a USB memory stick, I can use it for file transfers to my RaspberryPi to help error checking! On Dell64, using root primitive recovery "quasi-terminal" # cp -r "/home/bill/OOPM builds" /media/bill/Lexar # umount /media/bill/Lexar >> seems OK, pulled USB, put into RaspberryPi Now - transfer all of Qnial directory to look at possible "termcap" destruction of X11 # mount -t vfat UUID=7260-5B07 /media/bill/Lexar # cp -r /home/bill/Qnial /media/bill/Lexar # cp -r "/home/bill/OOPM builds old" /media/bill/Lexar # cp -r "/home/bill/System_maintenance/ # umount /media/bill/Lexar Should have used -p option (preserve ownership etc)!!! - dates all changed **************************** 10Apr2017 12:45 One last try before reformat-LMDE2 install Go back to : # startx >> whole pile of output, last part I can see is : Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian Current Operating System: Linux dell64 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 ... xinit: connection to X server lost waiting for X server to shut down .error setting MTRR (base = 0xe9000000, size = 0x00e00000, type = 1) Invalid argument (22) (EE) Server terminated successfully (0). Closing log file. >> Error (EE) is a bit scary Web search "Linux Mint and waiting for X server to shut down .error setting MTRR" https://bbs.archlinux.org/viewtopic.php?id=68093 error setting MTRR", can't get X to start markisthejob, From: Cork, Ireland, Registered: 2008-09-01 I had the same problem when I did a reinstall a while back.I Had no .xinitrc in my /home cp /etc/X11/xinit/xinitrc ~/.xinitrc That is what worked for me. Howell - look at Dell64 file # cat /etc/X11/xinit/.xinitrc >> OK - same as RaspberryPi version # cp /etc/X11/xinit/.xinitrc /home/bill/.xinitrc # find /home/pi -iname ".xinitrc" >> Nothing there? >> Nothing on Dell64 either # cp /etc/X11/xinit/.xinitrc /home/bill >> OK, now try reboot # shutdown now >> No workee! https://bbs.archlinux.org/viewtopic.php?id=68093 error setting MTRR", can't get X to start thoughtcrime, Registered: 2008-09-27 I got this error too and thought it caused X not to start. But creating a xinit.rc with: openbox-session did the job. - blog (about arch and other stuff): http://thoughtyblog.wordpress.com/ - x86_64 user +--+ Krytarik March 31st, 2011, 05:47 PM Ok, now we have a somewhat clearer picture. It maybe that when you did run startx with sudo, that changed the ownership of "/home/andy/.Xauthority" to those of root. Check that, and if so, revert it to yourself. As for the nouveau driver, it is still under development, and thus may cause issues at some systems or setups. So, would you like to install the proprietary driver instead? If you want to purge Xorg-Edgers' PPA and downgrade all concerning packages, you could use the tool "ppa-purge" for that: sudo apt-get install ppa-purge sudo ppa-purge ppa:xorg-edgers/ppaHowever, if you choose to use the proprietary driver, you shouldn't remove the PPA, since it also offers the most recent version of those. To install those, assuming that you don't have it already installed, you could run: sudo apt-get install nvidia-currentMake sure that a proper xorg.conf is present: sudo nvidia-xconfig --add-argb-glx-visuals --no-logo --force-generateBut if you are able to get to the desktop after possibly fixing the mentioned file permissions, you should install it via "System -> Administration -> Additional Drivers". +--+ >> I don't have a /home/bill/.Xauthority!! ************************** 10Apr2017 14:27 I give up!!! - re-install LMDE2 on Dell64 # enddoc