Yes and no. Computers will do what you ask them to, not what you want
them to.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1890998
Title:
Cant login in to system
To manage notific
Anyway it is stupid that setting custom umask blows gdm and prevent
logging in.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1890998
Title:
Cant login in to system
To manage notifi
** Changed in: gdm3 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1890998
Title:
Cant login in to system
To manage notifications about this bu
I found what causes this issue. I set up umask to 137 in .profile file.
After commenting out this line and restart I can log in to system.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/
I switched to sddm and log in to system to check permissions on ssh
agent socket.
$ ls -la /tmp/ssh-GLokEJp0ajlD/agent.4700
srw--- 1 mkukielka mkukielka 0 sie 18 12:26
/tmp/ssh-GLokEJp0ajlD/agent.4700=
I think the permissions are good.
--
You received this bug notification because you are a
Still nothing.
https://paste.ubuntu.com/p/q8NKNMh4KX/
I renamed ~/.ssh to ~/.ssh.bak, switched back to gdm3, reboot and it's same.
Still after confirming password I'm landing on gdm login screen.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subs
This looks like the exact point of failure:
sie 13 11:38:35 mkukielka-prs /usr/lib/gdm3/gdm-x-session[3413]: unix_listener:
cannot bind to path /tmp/ssh-eND2ca8O3cXt/agent.3413: Permission denied
sie 13 11:38:35 mkukielka-prs gdm-x-session[3385]: session exited with status 1
sie 13 11:38:35 mkuki
I didn't modify those files. Those files belongs to following packages:
xserver-xorg-video-amdgpu
xserver-xorg-core
xserver-xorg-video-radeon
xserver-xorg-input-libinput
xserver-xorg-input-wacom
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification b
Files from /usr/share/X11/xorg.conf.d in attachment. None of these files
contains 'Option "_source" "server/udev"' or 'Option "_source"
"_driver/libinput"'.
** Attachment added: "X11.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1890998/+attachment/5402142/+files/X11.tar.gz
--
Try looking in /usr/share/X11/xorg.conf.d/
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1890998
Title:
Cant login in
Thanks.
It sounds like there's an invalid Xorg config file on your system with
lots of:
Option "_source" "server/udev"
and
Option "_source" "_driver/libinput"
That may be why Xorg is exiting immediately. If you can find the config
file that contains those then please move it elsewhere, and
Debug mode enabled, steps repeated.
https://paste.ubuntu.com/p/f97M7NgWF4/
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1
These look like the problem:
sie 12 09:43:03 mkukielka-prs gdm-password][3167]: pam_unix(gdm-
password:session): session closed for user mkukielka
sie 12 09:43:03 mkukielka-prs systemd-logind[1446]: Session 2 logged out.
Waiting for processes to exit.
sie 12 09:43:04 mkukielka-prs systemd-logind
Here's log from previous boot like you wanted.
https://paste.ubuntu.com/p/T5bWDQXr76/
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad
I would like to see a clean log of the problem in action. Please reboot
fresh, reproduce the gdm login failure and then reboot _again_.
Now after the second reboot please hit Ctrl+Alt+F4 and log in to the
text console. In the text console please run:
journalctl -b-1 > prevboot.txt
and then att
1. I tried this before I made a bug report. It just hang on purple screen right
after confirming password. I needed to kill X session to return to login
screen. Doesn't work.
2. Doesn't work also. Symptoms are same but log is different.
https://paste.ubuntu.com/p/gjqXkFGyqP/
** Changed in: gdm3
Please:
1. Try selecting 'Ubuntu on Wayland' on the login screen, before
entering your password.
and if that didn't work then:
2. Try editing /etc/gdm3/custom.conf and uncommenting:
#WaylandEnable=false
to be:
WaylandEnable=false
and reboot.
** Changed in: gdm3 (Ubuntu)
S
17 matches
Mail list logo