Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[SOLVED] Login problem

alexjack
Forum Novice
Forum  Novice
Posts: 95
Joined: Wed May 02, 2018 3:11 pm

[SOLVED] Login problem

#1

Post by alexjack » Sun Apr 28, 2019 6:56 am

Hi all,
when booting, I get to the login screen and enter my pw. Then, the login doesn't complete (i.e. I don't get to the XFCE desktop) and I'm stuck on a screen with the login background image. I can press ctrl+alt+F1, login, then sudo lightdm, or startx. That then does take me to the desktop. Logging out, then back in (without reboot) doesn't cause the same problem. This started a week ago and I'm not sure what triggered the change. All was fine up to then with a fairly new installation.

Cheers

EDIT: logging in as root, does not give the same issue. Is the login to a user account getting hung up on something needing root privileges?
EDIT #2: If, after ctrl+alt+F1 and login as user, then "startx", at the XFCE desktop I get the message: "no removable device. Double click to remove."

Code: Select all

System:    Host: ryzen Kernel: 4.19.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum Apr 7  2019 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PRO GAMING v: Rev X.0x serial: <filter> 
           UEFI [Legacy]: American Megatrends v: 0312 date: 09/18/2018 
CPU:       Topology: 6-Core model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ rev: 2 
           L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 81438 
           Speed: 1401 MHz min/max: 1550/3400 MHz Core speeds (MHz): 1: 1401 2: 1412 3: 1557 
           4: 1447 5: 1461 6: 1420 7: 1547 8: 1547 9: 2294 10: 2336 11: 2141 12: 1556 
Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: ASUSTeK driver: nvidia v: 390.116 
           bus ID: 07:00.0 
           Display: x11 server: X.Org 1.19.2 driver: nvidia resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.116 
           direct render: Yes 
Audio:     Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 07:00.1 
           Device-2: AMD vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 09:00.3 
           Sound Server: ALSA v: k4.19.0-1-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 05:00.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 577.55 GiB used: 349.76 GiB (60.6%) 
           ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP300 size: 111.79 GiB 
           ID-2: /dev/sda vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB 
Partition: ID-1: / size: 89.60 GiB used: 52.88 GiB (59.0%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 20.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 39.8 C mobo: N/A gpu: nvidia temp: 37 C 
           Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 27% 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/stretch stretch main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.uk.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.uk.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ stretch main non-free
           Active apt repos in: /etc/apt/sources.list.d/syncthing.list 
           1: deb https://apt.syncthing.net/ syncthing stable
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 276 Uptime: 14m Memory: 15.66 GiB used: 1.19 GiB (7.6%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.33 
Last edited by alexjack on Mon May 20, 2019 2:57 pm, edited 4 times in total.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 11805
Joined: Sun Dec 16, 2007 1:17 pm

Re: Login problem

#2

Post by dolphin_oracle » Sun Apr 28, 2019 12:32 pm

the nvidia drivers updated (from debian I think).

I suggest trying removing the xorg.conf file. That seems to help some folks who have this issue with Xfce.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-18
lenovo s21e - MX-18, antiX-17.3.1 (live-USB)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 8585
Joined: Wed Jul 12, 2006 2:10 am

Re: Login problem

#3

Post by Eadwine Rose » Sun Apr 28, 2019 12:38 pm

If you end up doing that you can put the line to counter screen tearing:

Code: Select all

nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
In sessions and startup, just give it a name, like "screen tearing fix" or something.
MX-18.3_x64 May 26 2019 * 4.19.0-5-amd64 ext4 Xfce 4.12.3 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 390.116 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 860EVO * Samsung S24D330 & P2250 * HP Envy5030

alexjack
Forum Novice
Forum  Novice
Posts: 95
Joined: Wed May 02, 2018 3:11 pm

Re: Login problem

#4

Post by alexjack » Sun Apr 28, 2019 12:44 pm

Thanks, but removing xorg.conf did not fix the issue.

Added to the original post at the top:
EDIT: logging in as root, does not give the same issue. Is the login to a user account getting hung up on something needing root privileges?

alexjack
Forum Novice
Forum  Novice
Posts: 95
Joined: Wed May 02, 2018 3:11 pm

Re: Login problem

#5

Post by alexjack » Sun Apr 28, 2019 1:11 pm

I had a look around in /var/log. In user.log, there are these lines corresponding to the time of a reboot and login attempt:

Apr 28 18:00:26 ryzen shutdown[6216]: shutting down for system reboot
Apr 28 18:01:02 ryzen colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
Apr 28 18:01:02 ryzen colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
Apr 28 18:01:02 ryzen colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
Apr 28 18:01:02 ryzen colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
Apr 28 18:01:02 ryzen colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
Apr 28 18:01:02 ryzen colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
Apr 28 18:01:02 ryzen colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
Apr 28 18:01:03 ryzen /hpfax: [3154]: error: Failed to create /var/spool/cups/tmp/.hplip
Apr 28 18:01:04 ryzen lightdm: pam_ecryptfs: Skipping automatic eCryptfs mount
Apr 28 18:01:06 ryzen pulseaudio[3759]: [pulseaudio] pid.c: Daemon already running.

Not sure if it's related.

alexjack
Forum Novice
Forum  Novice
Posts: 95
Joined: Wed May 02, 2018 3:11 pm

Re: Login problem

#6

Post by alexjack » Sun May 19, 2019 4:46 pm

Hi all,

I'm still having this issue where my user login doesn't take me to the XFCE desktop. I'm working around it at the moment. After any reboot, I first log in as root, log out, then log in as normal user. I can go several days then just using suspend and resume. I suspect that there is something trying to start that needs root permissions which gets sorted when I first log in as root.

I have been using Syncthing. A problem with the above workaround seems to be that Syncthing starts as root and stays as root, so my user sync folders that I have set up don't show when I open the Syncthing web UI.

Any ideas to troubleshoot this? I've searched around and can't find much.

User avatar
Richard
Posts: 2738
Joined: Fri Dec 12, 2008 10:31 am

Re: Login problem

#7

Post by Richard » Sun May 19, 2019 5:17 pm

Did you have this problem before installing Syncthing? Unusual, probably insecure to run a web app as root all the time?
LT: MX18.3: Thinkpad T430: DualCore, Intel i5-3320M, Ivy Bridge; 8GB RAM; 4.19.0-5-amd64; 119GB SSD 840PRO, Intel Graphics-Audio-Network
NB: MX18.1, antiX17.4: AsusTek EeePC 1005HA: Intel DualCore Atom N270, 1GB RAM, 4.19.0-1-686, 150GB HDD

alexjack
Forum Novice
Forum  Novice
Posts: 95
Joined: Wed May 02, 2018 3:11 pm

Re: Login problem

#8

Post by alexjack » Sun May 19, 2019 6:15 pm

Richard wrote:
Sun May 19, 2019 5:17 pm
Did you have this problem before installing Syncthing? Unusual, probably insecure to run a web app as root all the time?
I can't remember now, exactly if it coincided with starting to use Syncthing. I have just unchecked Syncthing from the auto startup list and rebooted. Didn't make a difference.

User avatar
Richard
Posts: 2738
Joined: Fri Dec 12, 2008 10:31 am

Re: Login problem

#9

Post by Richard » Sun May 19, 2019 7:48 pm

Well, since it's a fairly new install, I'd probably just backup data and reinstall. I know that's the whimpy way out but when this sort of problem starts it could be software, hardware, cables or cosmic rays. :)

Reinstalling gets me more acquainted with the installer which sometimes helps avoid problems.It will also help rule out some other possibilities.
LT: MX18.3: Thinkpad T430: DualCore, Intel i5-3320M, Ivy Bridge; 8GB RAM; 4.19.0-5-amd64; 119GB SSD 840PRO, Intel Graphics-Audio-Network
NB: MX18.1, antiX17.4: AsusTek EeePC 1005HA: Intel DualCore Atom N270, 1GB RAM, 4.19.0-1-686, 150GB HDD

alexjack
Forum Novice
Forum  Novice
Posts: 95
Joined: Wed May 02, 2018 3:11 pm

Re: Login problem

#10

Post by alexjack » Mon May 20, 2019 2:57 pm

Right, progress. I was using an entry in startup with:

[Desktop Entry]
Encoding=UTF-8
Version=0.9.4
Type=Application
Name=Nvidia pipeline
Comment=Force full pipeline
Exec=nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }"
OnlyShowIn=XFCE;
StartupNotify=false
Terminal=false
Hidden=false

Toggle this to off, and my login problem is fixed. Apply the same force pipeline thing once logged in, no problem. So I need to find a way to apply that force pipeline thing automatically, but after login to XFCE is complete.

Post Reply

Return to “Desktop Environment”