Hi,
I have SparkyLinux 5 x86_64 "rolling" installed with the latest sparky kernel, and after the latest upgrade, I cant boot into GUI at all.
I just boots into CLI but after a longer wait than usual, if I was booting to my desktop.
I had the lxqt-desktop installed with openbox as my window manager.
I'm stuck at CLI and dont know how to get back to my desktop.
Here are some screenshots I took with my phone, so the quality is a bit blurry.
There seems to be a problem with openbox and/or Xserver
I also have Nvidia's proprietary driver installed.
Typing "echo $DISPLAY" doesn't print out anything.
I can provide you more info about my system/problem by replying to you.
This is really urgent because I cant use the machine for basic tasks currently at all.
Examples of the problem:
(https://i.imgur.com/ipXRWBx.jpg)
(https://i.imgur.com/Wy6NBem.jpg)
(https://i.imgur.com/eADABwq.jpg)
Pictures from .xsession-errors
(https://i.imgur.com/Hja1ENS.jpg)
(https://i.imgur.com/0SQTN6j.jpg)
First try Ctl-Alt-F7 to see if you get X back, probably not. Ctl-Alt F1 will get you back to vt1 (virtual terminal 1)
I had a stuck apt full-upgrade on an xorg - binary. Can't remember what it was.
If you do command line, "dpkg --configure -a" is pretty safe, if errors messages appear, please copy via Ctl-Shift-C from terminal and post errors (if possible).
There has been a change in "su" awhile back (sbin versus bin blah blah blah)
If you are in command line - then as root try "su - root" instead of "su root" That is what made my stuck upgrade progress. "dpkg --configure -a" did not solve my problem this time. relogging in as "su - root" worked for me. If not wait for someone else to post methods that use Aptus or synaptic.
There has been some writing about the su - root change, but it is hard to follow. One recent post of unstable debian users helped me a little in understanding it better, but I am still not sure about the "why's"
WHat happens if you start the desktop manager from the CLI? At the prompt type
sddm
or perhaps
lightdm
Do either of those invoke your GUI login manager?
Hi and thank you for your replies.
I tried the CTRL-ALT-F7 button combo but nothing happens.
I also tried doing "sudo dpkg --configure -a", but I don't think it did anything.
It finished the command as soon as I hit enter and nothing appeared on screen about the command actually being run, which is weird.
I've read that other people have had that same issue too, when they've gotten stuck at the CLI.
I still did a few test commands with dpkg to see if it was working with other commands, like reading the --version and --help.
It worked just fine.
I managed to get in as root by typing "su - root" and did the following commands:
sudo apt-get update
sudo apt-get upgrade
sudo dpkg --configure -a
lightdm
sddm
sudo lightdm
sudo sddm
It behaved exactly like it would have if I would have instead done "su root", and repeated those same commands.
Also now that I start thinking, I think that the last update freed like ~200mb of disk space, is that normal?
One possibility is that it might have deleted something but failed to bring back the updated version of it?
Like some random individual files that could cause a problem of this sorts?
Atleast the core system is stable and working, so I dont think any important system files are missing.
Typing in sddm or lightdm just says "unknown command".
Note: You should not need to use "sudo" when logged in as root. "sudo" is used when you are in a normal terminal and you want root permissions when logged in as a normal user.
When "dpkg --configure -a" gives no response, that means it could not find any partially configured packages. That is a good response.
"Other people had that same issue too." Where - what irc or forum? When, was it in the last few days? What OS if different than Debian (Sparky) What DE if different than lxqt?
Do you have any holds on packages? Either via pinning or apt-mark hold? (If you do not know you probably do not.)
My short glitch with xorg was in i386 Atom sparky been rolling for a couple of years in lxqt.
I just did apt full-upgrade in my Virtual amd64 sparky lxqt to try to replicate. No luck replicating.
Is your xorg-server version 2:1.20.3-1 or 2:1.20.2-1 ?
Is your xorg 1:7.7+19 ?
edit To investigate whether it is sddm or lightdm and if active I would use something like
systemctl status lightdm
and
systemctl status sddm. One or the other should come up during the boot process. My guess is that it is lightdm. A little green square and a green "active (running) will indicate if it is working.
I was browsing links from google search results when I was googling about my problem, before I posted on this forum.
They told the original poster to do "dpkg --configure -a", and for some it gave no response. (cant remember which site this was on and what configuration he had)
Then the original poster replied to someone and asked for a "fix" for why there was no response, so I thought it was a problem and I didn't do any more research on the reasons why he didn't get any reply.
Thanks for clearing that out, I thought there was a some kind of an "issue" with dpkg too.
Didn't know it was a good thing that it doesn't give any reply.
About the xorg-server and xorg, how can I check their versions?
I typed "xorg" and hit tab to see available commands and there were none.
I also tried some variations of it, like "Xorg", "X-org" and such.
I dont think that I have any packets on "hold", because I don't know what it even means or does.
I'm not super experienced user and this CLI stuff is still a bit new to me, as i'm used to doing most things through a GUI.
edit:
Here are the results from
systemctl status lightdm
systemctl status sddm
(https://i.imgur.com/e7lkfEO.jpg)
The little square is red.
After browsing Arch forums, I got the idea to try starting lightdm manually by using "sudo systemctl start lightdm", but with no success.
(https://i.imgur.com/MDsXpXg.jpg)
Contents of "sudo journalctl -xe":
(https://i.imgur.com/SjDOJqQ.jpg)
There doesn't seem to be much useful information.
Do you have active internet connetction at cli?
Test via:
sudo ping -c 1 google.com
If yes, try to install different login manager, I suggest slim:
sudo apt update
sudo apt install slim
Then choose slim as default and restart:
sudo reboot
I browsed the internet through lynx so I should have connection.
When I install slim, do I get to keep my lxqt desktop and my programs?
When slim is installed, how can I choose it as default?
If you have internet connection, simply install slim as I posted befor.
During installation proces, you will be asked what session manager you want to use as default, so choose slim, then reboot.
If everything ok, the system will display slim instead of lightdm, which lets you log in to your desktop.
Just try.
I got slim installed and set it as default login manager but unfortunately I still get booted to CLI.
The only difference is that now it says "A start job is running for Network manager Wait Online (seconds / no limit) when booting.
After that the CLI shows up.
Here's the output of "systemctl status slim"
(https://i.imgur.com/DjbFSq4.jpg)
It shows the same small red square on the top left of the screen, just like with lightdm when I ran that same command previously in this thread.
edit:
If I try to run slim manually by typing "sudo slim" It prints the following error:
/usr/bin/X11/xauth: file /var/run/slim.auth does not exist
I did "systemctl status slim" again and this time it has more text.
(https://i.imgur.com/LeqkWBi.jpg)
Also I checked if the file really was missing, but its not.
(https://i.imgur.com/al5xP8v.jpg)
The first screenshot says that it can not find /usr/bin/X so try to reinstall it:
sudo apt update
sudo apt install --reinstall xorg xserver-xorg xserver-xorg-core
or install it back if not installed:
sudo apt update
sudo apt install xorg xserver-xorg xserver-xorg-core
then reboot.
After doing
sudo apt update
sudo apt install --reinstall xorg
I rebooted but the CLI still shows up.
Here's what the CLI login looks like after it has finished booting.
(https://i.imgur.com/l4IdZoL.jpg)
You can see the login field at the top left between the letters.
I used neofetch to clear the screen the screen of text after logging in.
Using "clear" brings back the text and then I have to clear it again with some terminal program which outputs empty lines, like neofetch or just by typing "ls" a couple of times.
Using "sudo lightdm" brings me to an empty CLI but with a higher pixel density and with no input or output.
I can go back and return to it using CTRL+ALT+F7 - F1 buttons.
Here's what came up on the regular CLI when I returned to it.
(https://i.imgur.com/sd9B3zm.jpg)
Here's what shows up when I type "sudo slim"
I had to take multiple pictures so I'll post them in the same order as the text goes.
(1)
(https://i.imgur.com/L3gxPWf.jpg)
(2)
(https://i.imgur.com/dIZOQxn.jpg)
Contents of Xorg.0.log
(1)
(https://i.imgur.com/zClGn2w.jpg)
(2)
(https://i.imgur.com/VxMLBJL.jpg)
(3)
(https://i.imgur.com/zZ1WhY6.jpg)
I have edited my last post, there are 3 packages to be reinstalled.
I ran
sudo apt update
sudo apt install --reinstall xorg xserver-xorg xserver-xorg-core
sudo reboot
I had all of those installed and it finished reinstalling without problems.
Everything still seems to be the same as in my previous pictures but now there is an alert about "Network Manager Wait Online" failing to start when finishing booting.
It's highlighted in red.
(https://i.imgur.com/vj1WGT3.jpg)
Checked that I still have a working internet connection.
I tried running "sudo startx", "sudo slim" and "sudo lightdm" again but I ended up with the same results.
Copy/get the files:
/var/log/Xorg.0.log
/var/log/lightdm/lightdm.log
/home/you/.xsession-errors
and show their full output here (not screenshots).
The lightdm.log need root/sudo to be get it.
I used my USB stick and the "cp" command to get the files out of my PC and opened them on another machine.
Here are the contents of
lightdm.log
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=1506
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: posix_spawn avoided (fd close requested)
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.01s] DEBUG: XServer 0: Launching X Server
[+0.01s] DEBUG: Launching process 1511: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.01s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.01s] DEBUG: User irets added
[+0.25s] DEBUG: Process 1511 exited with return value 1
[+0.25s] DEBUG: XServer 0: X server stopped
[+0.25s] DEBUG: Releasing VT 7
[+0.25s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+0.25s] DEBUG: Seat seat0: Display server stopped
[+0.25s] DEBUG: Seat seat0: Stopping session
[+0.25s] DEBUG: Seat seat0: Session stopped
[+0.25s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+0.25s] DEBUG: Seat seat0: Stopping; greeter display server failed to start
[+0.25s] DEBUG: Seat seat0: Stopping
[+0.25s] DEBUG: Seat seat0: Stopped
[+0.25s] DEBUG: Required seat has stopped
[+0.25s] DEBUG: Stopping display manager
[+0.25s] DEBUG: Display manager stopped
[+0.25s] DEBUG: Stopping daemon
[+0.25s] DEBUG: Exiting with return value 1
Xorg.0.log
[ 36.904]
X.Org X Server 1.20.3
X Protocol Version 11, Revision 0
[ 36.904] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[ 36.904] Current Operating System: Linux Navi 4.19.0-sparky-amd64 #1 SMP Mon Oct 22 11:35:49 CEST 2018 x86_64
[ 36.904] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-sparky-amd64 root=UUID=e442a987-cf61-48f0-8ef9-767b316d37ce ro quiet
[ 36.904] Build Date: 25 October 2018 06:15:23PM
[ 36.904] xorg-server 2:1.20.3-1 (https://www.debian.org/support)
[ 36.904] Current version of pixman: 0.34.0
[ 36.904] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 36.904] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 36.904] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 6 19:51:22 2018
[ 36.904] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 36.904] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 36.904] (==) No Layout section. Using the first Screen section.
[ 36.904] (==) No screen section available. Using defaults.
[ 36.904] (**) |-->Screen "Default Screen Section" (0)
[ 36.904] (**) | |-->Monitor "<default monitor>"
[ 36.904] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 36.904] (==) Automatically adding devices
[ 36.904] (==) Automatically enabling devices
[ 36.904] (==) Automatically adding GPU devices
[ 36.904] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 36.904] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 36.904] Entry deleted from font path.
[ 36.904] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 36.904] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 36.904] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 36.904] (II) Loader magic: 0x5575671dce20
[ 36.904] (II) Module ABI versions:
[ 36.904] X.Org ANSI C Emulation: 0.4
[ 36.904] X.Org Video Driver: 24.0
[ 36.904] X.Org XInput driver : 24.1
[ 36.904] X.Org Server Extension : 10.0
[ 36.905] (--) using VT number 2
[ 36.905] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 36.905] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 36.906] (--) PCI:*(1@0:0:0) 10de:1b81:1462:3302 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[ 36.906] (II) LoadModule: "glx"
[ 36.906] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 36.906] (II) Module glx: vendor="X.Org Foundation"
[ 36.906] compiled for 1.20.3, module version = 1.0.0
[ 36.906] ABI class: X.Org Server Extension, version 10.0
[ 37.129] (==) Matched nouveau as autoconfigured driver 0
[ 37.129] (==) Matched nv as autoconfigured driver 1
[ 37.129] (==) Matched modesetting as autoconfigured driver 2
[ 37.129] (==) Matched fbdev as autoconfigured driver 3
[ 37.129] (==) Matched vesa as autoconfigured driver 4
[ 37.129] (==) Assigned the driver to the xf86ConfigLayout
[ 37.129] (II) LoadModule: "nouveau"
[ 37.129] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 37.129] (II) Module nouveau: vendor="X.Org Foundation"
[ 37.129] compiled for 1.20.0, module version = 1.0.15
[ 37.129] Module class: X.Org Video Driver
[ 37.129] ABI class: X.Org Video Driver, version 24.0
[ 37.129] (II) LoadModule: "nv"
[ 37.129] (WW) Warning, couldn't open module nv
[ 37.129] (EE) Failed to load module "nv" (module does not exist, 0)
[ 37.129] (II) LoadModule: "modesetting"
[ 37.129] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 37.129] (II) Module modesetting: vendor="X.Org Foundation"
[ 37.129] compiled for 1.20.3, module version = 1.20.3
[ 37.129] Module class: X.Org Video Driver
[ 37.129] ABI class: X.Org Video Driver, version 24.0
[ 37.129] (II) LoadModule: "fbdev"
[ 37.129] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 37.129] (II) Module fbdev: vendor="X.Org Foundation"
[ 37.129] compiled for 1.20.0, module version = 0.5.0
[ 37.129] Module class: X.Org Video Driver
[ 37.129] ABI class: X.Org Video Driver, version 24.0
[ 37.129] (II) LoadModule: "vesa"
[ 37.129] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 37.129] (II) Module vesa: vendor="X.Org Foundation"
[ 37.129] compiled for 1.20.1, module version = 2.4.0
[ 37.129] Module class: X.Org Video Driver
[ 37.129] ABI class: X.Org Video Driver, version 24.0
[ 37.129] (II) NOUVEAU driver Date: Fri Apr 21 14:41:17 2017 -0400
[ 37.129] (II) NOUVEAU driver for NVIDIA chipset families :
[ 37.129] RIVA TNT (NV04)
[ 37.129] RIVA TNT2 (NV05)
[ 37.129] GeForce 256 (NV10)
[ 37.129] GeForce 2 (NV11, NV15)
[ 37.129] GeForce 4MX (NV17, NV18)
[ 37.129] GeForce 3 (NV20)
[ 37.129] GeForce 4Ti (NV25, NV28)
[ 37.130] GeForce FX (NV3x)
[ 37.130] GeForce 6 (NV4x)
[ 37.130] GeForce 7 (G7x)
[ 37.130] GeForce 8 (G8x)
[ 37.130] GeForce GTX 200 (NVA0)
[ 37.130] GeForce GTX 400 (NVC0)
[ 37.130] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 37.130] (II) FBDEV: driver for framebuffer: fbdev
[ 37.130] (II) VESA: driver for VESA chipsets: vesa
[ 37.139] (EE) [drm] Failed to open DRM device for (null): -2
[ 37.139] (EE) [drm] Failed to open DRM device for pci:0000:01:00.0: -2
[ 37.139] (WW) Falling back to old probe method for modesetting
[ 37.139] (II) Loading sub module "fbdevhw"
[ 37.139] (II) LoadModule: "fbdevhw"
[ 37.139] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 37.139] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 37.139] compiled for 1.20.3, module version = 0.0.2
[ 37.139] ABI class: X.Org Video Driver, version 24.0
[ 37.139] (EE) Unable to find a valid framebuffer device
[ 37.139] (WW) Falling back to old probe method for fbdev
[ 37.139] (II) Loading sub module "fbdevhw"
[ 37.139] (II) LoadModule: "fbdevhw"
[ 37.139] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 37.139] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 37.139] compiled for 1.20.3, module version = 0.0.2
[ 37.139] ABI class: X.Org Video Driver, version 24.0
[ 37.139] (EE) open /dev/fb0: No such file or directory
[ 37.139] vesa: Ignoring device with a bound kernel driver
[ 37.139] (EE) [drm] Failed to open DRM device for (null): -2
[ 37.139] (EE) Screen 0 deleted because of no matching config section.
[ 37.139] (II) UnloadModule: "modesetting"
[ 37.139] (EE) Screen 0 deleted because of no matching config section.
[ 37.139] (II) UnloadModule: "fbdev"
[ 37.139] (II) UnloadSubModule: "fbdevhw"
[ 37.139] (EE) Screen 0 deleted because of no matching config section.
[ 37.139] (II) UnloadModule: "vesa"
[ 37.139] (EE) Device(s) detected, but none match those in the config file.
[ 37.139] (EE)
Fatal server error:
[ 37.139] (EE) no screens found(EE)
[ 37.139] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 37.139] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 37.139] (EE)
[ 37.145] (EE) Server terminated with error (1). Closing log file.
.xsession-errors
Xsession: X session started for irets at to 1.11.2018 12.37.47 +0200
localuser:irets being added to access control list
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
dbus-update-activation-environment: setting USER=irets
dbus-update-activation-environment: setting LC_TIME=fi_FI.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/irets
dbus-update-activation-environment: setting DESKTOP_SESSION=lxqt
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting LC_MONETARY=fi_FI.UTF-8
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-RV7168HWYF,guid=d50c67b93aefa708f4d672675bdad77b
dbus-update-activation-environment: setting LOGNAME=irets
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting GDM_LANG=en_US.utf8
dbus-update-activation-environment: setting LC_ADDRESS=fi_FI.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LC_TELEPHONE=fi_FI.UTF-8
dbus-update-activation-environment: setting LANG=en_US.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=lxqt
dbus-update-activation-environment: setting XAUTHORITY=/home/irets/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/irets
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting LC_NAME=fi_FI.UTF-8
dbus-update-activation-environment: setting GDMSESSION=lxqt
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting LC_MEASUREMENT=fi_FI.UTF-8
dbus-update-activation-environment: setting LC_IDENTIFICATION=fi_FI.UTF-8
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/irets
dbus-update-activation-environment: setting LC_NUMERIC=fi_FI.UTF-8
dbus-update-activation-environment: setting LC_PAPER=fi_FI.UTF-8
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
m: 1: m: Syntax error: Unterminated quoted string
dbus-daemon[1599]: Activating service name='org.a11y.atspi.Registry' requested by ':1.2' (uid=1000 pid=1637 comm="/usr/bin/nm-applet ")
Output: "DVI-D-0"
Output: "HDMI-0"
Output: "DP-0"
Output: "DP-1"
Output: "DP-2"
Output: "DP-3"
Output: "DP-4"
Output: "DP-5"
dbus-daemon[1599]: Successfully activated service 'org.a11y.atspi.Registry'
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
(0x7ffd7c66c760) Debug: systemd: "CanReboot" = "yes"
(0x7ffd7c66c760) Debug: systemd: "CanPowerOff" = "yes"
Translator is not loaded "qlipper_en_US" "/usr/share/qlipper/translations"
Get:1 http://security.debian.org testing/updates InRelease [38,3 kB]
Hit:2 http://repo.steampowered.com/steam precise InRelease
Get:3 http://ftp.debian.org/debian testing InRelease [150 kB]
Hit:4 http://sparkylinux.org/repo unstable InRelease
Get:5 http://ftp.debian.org/debian sid InRelease [233 kB]
Get:6 https://sparkylinux.org/repo testing InRelease [3 603 B]
Get:7 http://ftp.debian.org/debian testing/main Sources.diff/Index [27,9 kB]
Get:8 http://ftp.debian.org/debian testing/main i386 Packages.diff/Index [27,9 kB]
Get:9 http://ftp.debian.org/debian testing/main amd64 Packages.diff/Index [27,9 kB]
Get:10 http://ftp.debian.org/debian testing/main Translation-en.diff/Index [27,9 kB]
Get:11 https://sparkylinux.org/repo testing/main Sources [90,2 kB]
Get:12 http://ftp.debian.org/debian testing/main Sources 2018-10-31-0835.55.pdiff [790 B]
Get:13 http://ftp.debian.org/debian testing/main Sources 2018-10-31-1408.09.pdiff [3 964 B]
Get:14 http://ftp.debian.org/debian testing/main Sources 2018-10-31-2020.58.pdiff [1 755 B]
Get:15 http://ftp.debian.org/debian testing/main Sources 2018-11-01-0207.55.pdiff [20,9 kB]
Get:16 http://ftp.debian.org/debian testing/main i386 Packages 2018-10-31-0835.55.pdiff [850 B]
Get:17 http://ftp.debian.org/debian testing/main i386 Packages 2018-10-31-1408.09.pdiff [23,4 kB]
Get:18 http://ftp.debian.org/debian testing/main i386 Packages 2018-10-31-2020.58.pdiff [10,2 kB]
Get:19 http://ftp.debian.org/debian testing/main i386 Packages 2018-11-01-0207.55.pdiff [22,1 kB]
Get:20 http://ftp.debian.org/debian testing/main amd64 Packages 2018-10-31-0835.55.pdiff [849 B]
Get:21 http://ftp.debian.org/debian testing/main amd64 Packages 2018-10-31-1408.09.pdiff [24,2 kB]
Get:15 http://ftp.debian.org/debian testing/main Sources 2018-11-01-0207.55.pdiff [20,9 kB]
Get:19 http://ftp.debian.org/debian testing/main i386 Packages 2018-11-01-0207.55.pdiff [22,1 kB]
Hit:22 http://www.deb-multimedia.org testing InRelease
Get:23 http://ftp.debian.org/debian sid/non-free Sources.diff/Index [27,8 kB]
Get:24 http://ftp.debian.org/debian sid/contrib Sources.diff/Index [27,8 kB]
Get:25 http://ftp.debian.org/debian sid/main Sources.diff/Index [27,9 kB]
Get:26 http://ftp.debian.org/debian sid/main amd64 Packages.diff/Index [27,9 kB]
Get:27 http://ftp.debian.org/debian sid/main i386 Packages.diff/Index [27,9 kB]
Get:28 http://ftp.debian.org/debian sid/main Translation-en.diff/Index [27,9 kB]
Get:29 http://www.deb-multimedia.org sid InRelease [24,2 kB]
Get:30 http://ftp.debian.org/debian sid/contrib amd64 Packages.diff/Index [27,8 kB]
Get:31 http://ftp.debian.org/debian sid/contrib i386 Packages.diff/Index [27,8 kB]
Get:32 http://ftp.debian.org/debian sid/contrib Translation-en.diff/Index [27,8 kB]
Get:33 http://ftp.debian.org/debian sid/non-free amd64 Packages.diff/Index [27,8 kB]
Get:34 http://ftp.debian.org/debian sid/non-free i386 Packages.diff/Index [27,8 kB]
Get:35 http://ftp.debian.org/debian sid/non-free Translation-en.diff/Index [27,8 kB]
Get:36 http://ftp.debian.org/debian testing/main amd64 Packages 2018-10-31-2020.58.pdiff [10,1 kB]
Get:37 http://ftp.debian.org/debian testing/main amd64 Packages 2018-11-01-0207.55.pdiff [22,2 kB]
Get:38 http://ftp.debian.org/debian testing/main Translation-en 2018-10-31-0835.55.pdiff [368 B]
Get:39 http://ftp.debian.org/debian testing/main Translation-en 2018-10-31-1408.09.pdiff [2 185 B]
Get:40 http://ftp.debian.org/debian testing/main Translation-en 2018-10-31-2020.58.pdiff [719 B]
Get:41 http://ftp.debian.org/debian testing/main Translation-en 2018-11-01-0207.55.pdiff [33 B]
Get:42 http://ftp.debian.org/debian sid/non-free Sources 2018-10-31-0835.55.pdiff [29 B]
Get:43 http://ftp.debian.org/debian sid/non-free Sources 2018-11-01-0207.55.pdiff [685 B]
Get:44 http://ftp.debian.org/debian sid/contrib Sources 2018-10-31-0835.55.pdiff [31 B]
Get:45 http://ftp.debian.org/debian sid/contrib Sources 2018-10-31-2020.58.pdiff [1 002 B]
Get:46 https://sparkylinux.org/repo testing/main i386 Packages [102 kB]
Get:37 http://ftp.debian.org/debian testing/main amd64 Packages 2018-11-01-0207.55.pdiff [22,2 kB]
Get:43 http://ftp.debian.org/debian sid/non-free Sources 2018-11-01-0207.55.pdiff [685 B]
Get:41 http://ftp.debian.org/debian testing/main Translation-en 2018-11-01-0207.55.pdiff [33 B]
Get:47 http://www.deb-multimedia.org sid/main i386 Packages [156 kB]
Get:48 http://ftp.debian.org/debian sid/contrib Sources 2018-11-01-0207.55.pdiff [31 B]
Get:48 http://ftp.debian.org/debian sid/contrib Sources 2018-11-01-0207.55.pdiff [31 B]
Get:49 http://ftp.debian.org/debian sid/main Sources 2018-10-31-0835.55.pdiff [6 815 B]
Get:50 http://ftp.debian.org/debian sid/main Sources 2018-10-31-1408.09.pdiff [23,2 kB]
Get:51 http://ftp.debian.org/debian sid/main Sources 2018-10-31-2020.58.pdiff [16,5 kB]
Get:52 http://ftp.debian.org/debian sid/main Sources 2018-11-01-0207.55.pdiff [14,3 kB]
Get:53 http://ftp.debian.org/debian sid/main amd64 Packages 2018-10-31-0835.55.pdiff [3 912 B]
Get:52 http://ftp.debian.org/debian sid/main Sources 2018-11-01-0207.55.pdiff [14,3 kB]
Get:54 http://ftp.debian.org/debian sid/main amd64 Packages 2018-10-31-1408.09.pdiff [19,3 kB]
Get:55 http://ftp.debian.org/debian sid/main amd64 Packages 2018-10-31-2020.58.pdiff [71,0 kB]
Get:56 http://ftp.debian.org/debian sid/main amd64 Packages 2018-11-01-0207.55.pdiff [65,1 kB]
Get:57 https://sparkylinux.org/repo testing/main amd64 Packages [105 kB]
Get:58 http://ftp.debian.org/debian sid/main i386 Packages 2018-10-31-0835.55.pdiff [3 468 B]
Get:56 http://ftp.debian.org/debian sid/main amd64 Packages 2018-11-01-0207.55.pdiff [65,1 kB]
Get:59 http://ftp.debian.org/debian sid/main i386 Packages 2018-10-31-1408.09.pdiff [18,4 kB]
Get:60 http://ftp.debian.org/debian sid/main i386 Packages 2018-10-31-2020.58.pdiff [87,7 kB]
Get:61 http://ftp.debian.org/debian sid/main i386 Packages 2018-11-01-0207.55.pdiff [50,7 kB]
Get:62 http://www.deb-multimedia.org sid/main amd64 Packages [157 kB]
Get:63 http://ftp.debian.org/debian sid/main Translation-en 2018-10-31-0835.55.pdiff [381 B]
Get:64 http://ftp.debian.org/debian sid/main Translation-en 2018-10-31-1408.09.pdiff [1 138 B]
Get:65 http://ftp.debian.org/debian sid/main Translation-en 2018-10-31-2020.58.pdiff [5 301 B]
Get:66 http://ftp.debian.org/debian sid/main Translation-en 2018-11-01-0207.55.pdiff [1 632 B]
Get:67 http://ftp.debian.org/debian sid/contrib amd64 Packages 2018-10-31-0835.55.pdiff [31 B]
Get:68 http://ftp.debian.org/debian sid/contrib amd64 Packages 2018-10-31-2020.58.pdiff [1 286 B]
Get:69 http://ftp.debian.org/debian sid/contrib i386 Packages 2018-10-31-0835.55.pdiff [31 B]
Get:61 http://ftp.debian.org/debian sid/main i386 Packages 2018-11-01-0207.55.pdiff [50,7 kB]
Get:68 http://ftp.debian.org/debian sid/contrib amd64 Packages 2018-10-31-2020.58.pdiff [1 286 B]
Get:66 http://ftp.debian.org/debian sid/main Translation-en 2018-11-01-0207.55.pdiff [1 632 B]
Get:70 http://ftp.debian.org/debian sid/contrib i386 Packages 2018-10-31-2020.58.pdiff [474 B]
Get:70 http://ftp.debian.org/debian sid/contrib i386 Packages 2018-10-31-2020.58.pdiff [474 B]
Get:71 http://ftp.debian.org/debian sid/contrib Translation-en 2018-10-31-0835.55.pdiff [31 B]
Get:72 http://ftp.debian.org/debian sid/non-free amd64 Packages 2018-10-31-0835.55.pdiff [29 B]
Get:71 http://ftp.debian.org/debian sid/contrib Translation-en 2018-10-31-0835.55.pdiff [31 B]
Get:73 http://ftp.debian.org/debian sid/non-free i386 Packages 2018-10-31-0835.55.pdiff [29 B]
Get:74 http://ftp.debian.org/debian sid/non-free Translation-en 2018-10-31-0835.55.pdiff [29 B]
Get:72 http://ftp.debian.org/debian sid/non-free amd64 Packages 2018-10-31-0835.55.pdiff [29 B]
Get:73 http://ftp.debian.org/debian sid/non-free i386 Packages 2018-10-31-0835.55.pdiff [29 B]
Get:74 http://ftp.debian.org/debian sid/non-free Translation-en 2018-10-31-0835.55.pdiff [29 B]
Fetched 2 042 kB in 3s (790 kB/s)
Reading package lists...
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
(0x7ffd7c66c760) Debug: systemd: "CanPowerOff" = "yes"
(0x7ffd7c66c760) Debug: systemd: "CanPowerOff" = "yes"
Gdk-Message: 16:49:31.328: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
qlipper: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 39049 requests (39049 known processed) with 0 events remaining.
The first question:
Can you run your system with non Sparky kernel, just with default's Debian one?
The second:
Did you upgrade your system from Sid repos too?
Tried booting with Debian's kernel but with no success.
The unstable repos, yes.
I think so because I'm using the rolling edition of sparky and I haven't done any changes to repos and I have the unstable versions of programs installed as default.
The .xsession-errors says that you have sid repos active so if you made full upgrade from sid, it could destroy something, it happens, can't find what.
The good point is, if you have to install something from sid, just enable it, install what you need and then disable sid back.
So, is there an easy way to get out of this situation without reinstalling?
I guess this is what I get for running a rolling distro without any backups.
I'm completely clueless how to progress from here without wiping the partition and starting over.
Its kinda shame because the only problems i'm having are display related and reinstall seems like overkill but i'm prepared for it.
Could the Nvidia drivers be causing trouble now that i've reinstalled a couple of packages like Xorg?
Everything I write I am saying gently.
It is not so much that you are running a rolling distribution, it is that you are running Unstable - Sid (the child who destroys toys in Toy Story). All Debian releases are named after Toy Story characters. Making things even more difficult is that you have a mixed environment of Sid and Buster-Testing.
And for the 5% or less of your system that comes from Sparky sources, you might be the only one using Sid paxkages with Sparky packages that are based on Buster-Testing. One analogy is that you are driving down a gravel road at 160 km per hour (100 miles an hour). Things can happen fast.
I had basically eliminated lightdm as you problem and also the su - root (which does not seem to affect people who use aptus) and focus on xorg and I put in 28 hours at work in 2 days. But looking at it now, with network manager and also possible Nvidia problems, yeah, reinstall is my opinion. You can keep all of your /home/* I would recommend saving elsewhere your "dot" directories and files, but if you keep LXQT you probably would not have any problems. Yes, I really like LXQT and I do like Sparky.
You have learned a lot, you were debugging in a cli environment and started marking up your code in xml as requested. It will not take forever to reinstall.
My opinion is that I always comment out DebianMultimedia in my etc/apt'sourceslist And I have almost all of my /sourcelist.d repos commented out unless I really need them, I don't use wine, etc. Uncomment them out if you want to use specific items ,like the reps for wine, crosstalk, etc. And when you investigate a problem, and you see a solution in sid for that one program, then enable sid sources, get that one (or two) solution and comment it back out.
It has been awhile for bugs for me, but
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912900
just happened to me. I will wait, and then use dpkg to install the fixes.
The rolling portion of Debian testing and also Sparky 5 will be entering a smoother sailing - less bugs coming for 5-7 months in very soon. The "freeze" is entering and no more major transitions in preparation for the next Debian stable.
You have learned a lot. You should be good to go with the re-install. Arch linux has one fantastic wiki and is really useful for ideas. But Arch is not Debian. The Debian wikis (when updated) would have more appropriate content, and lurking in the debian-next irc is also helpful for problems.
peace out
I've been watching this intently to see what I could learn. Originally, I was thinking login manager or xorg, but when he installed SLIM and problems persisted, I was fairly certain xorg was the culprit. The nVidia comment was just another moment of confirmation, as nVidia is notoriously fickle. I thought for sure pavroo's suggestion to reinstall would fix his issue, until I saw where pavroo identified SID (Still In Development!) sources in repo...then realized iret was probably reinstalling same packages that broke his install.
I would probably re-install too, as that is probably the "cleanest" path of least resistance. But I'm also wondering if he couldn't comment out the SID repos, purge the xorg and xserver packages, as well as nVidia packages; then reinstall those packages from the Sparky rolling repos? Wouldn't that overwrite any SID packages that are broken? Or are the package versions show in his log files the same as Sparky's versions?
Just curious. Remember....9 year 'buntu boy here trying to learn more about Debian and rolling packages...asking for the sake of knowledge!