Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 833131 - I can't log in as root by concole
Summary: I can't log in as root by concole
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-11 17:01 UTC by Mulgano
Modified: 2022-04-11 02:02 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
My system (emerge-info.txt,7.23 KB, text/plain)
2022-02-11 17:01 UTC, Mulgano
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mulgano 2022-02-11 17:01:58 UTC
Created attachment 764837 [details]
My system

I can't  log in as root by concole. I access with sudo

[  217.657330] login[4960]: segfault at 7f8dd3b4c087 ip 00007f8dd3a88f51 sp 00007ffeaf3715f8 error 4 in libc-2.33.so[7f8dd3953000+146000]
[  217.657470] Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 1f <c5> fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00 48 83 c7 20 83 e1
Comment 1 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2022-02-11 17:19:49 UTC
Can you get a backtrace using e.g. coredumpctl or minicoredumper? Or running 'login' from a root shell?

See https://wiki.gentoo.org/wiki/Debugging.
Comment 2 Mulgano 2022-02-19 17:52:30 UTC
slim systemd[1]: Started Getty on tty2.
feb 19 17:58:30 slim pam_blue[20490]: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0)
feb 19 17:58:30 slim systemd[1]: Created slice User Slice of UID 0.
feb 19 17:58:30 slim systemd[1]: Starting User Runtime Directory /run/user/0...
feb 19 17:58:30 slim systemd-logind[1413]: New session 6 of user root.
feb 19 17:58:30 slim systemd[1]: Finished User Runtime Directory /run/user/0.
feb 19 17:58:30 slim systemd[1]: Starting User Manager for UID 0...
feb 19 17:58:30 slim systemd[20509]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
feb 19 17:58:30 slim systemd[20509]: Queued start job for default target Main User Target.
feb 19 17:58:30 slim systemd[20509]: Created slice User Application Slice.
feb 19 17:58:30 slim systemd[20509]: Reached target Paths.
feb 19 17:58:30 slim systemd[20509]: Reached target Timers.
feb 19 17:58:30 slim systemd[20509]: Starting D-Bus User Message Bus Socket...
feb 19 17:58:31 slim systemd[20509]: Listening on D-Bus User Message Bus Socket.
feb 19 17:58:31 slim systemd[20509]: Reached target Sockets.
feb 19 17:58:31 slim systemd[20509]: Reached target Basic System.
feb 19 17:58:31 slim systemd[20509]: Reached target Main User Target.
feb 19 17:58:31 slim systemd[20509]: Startup finished in 117ms.
feb 19 17:58:31 slim systemd[1]: Started User Manager for UID 0.
feb 19 17:58:31 slim systemd[1]: Started Session 6 of User root.
feb 19 17:58:31 slim kernel: login[20519]: segfault at 7f2612bee087 ip 00007f2612b31f51 sp 00007ffc53a34d18 error 4 in libc-2.33.so[7f26129fc000+146000]
feb 19 17:58:31 slim kernel: Code: 84 00 00 00 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 1f <c5> fd 74 0f c5 fd d7 c1 85 c0 0f 85 df 00 00 00>
feb 19 17:58:31 slim systemd[1]: Started Process Core Dump (PID 20520/UID 0).
feb 19 17:58:31 slim systemd-coredump[20521]: [🡕] Process 20519 (login) of user 0 dumped core.
feb 19 17:58:31 slim pam_blue[20490]: pam_unix(login:session): session closed for user root
feb 19 17:58:31 slim systemd[1]: systemd-coredump@1-20520-0.service: Deactivated successfully.
feb 19 17:58:31 slim systemd[1]: getty@tty2.service: Deactivated successfully.
feb 19 17:58:31 slim systemd[1]: session-6.scope: Deactivated successfully.
feb 19 17:58:31 slim systemd[1]: getty@tty2.service: Scheduled restart job, restart counter is at 1.
feb 19 17:58:31 slim systemd-logind[1413]: Session 6 logged out. Waiting for processes to exit.
Comment 3 Mulgano 2022-04-11 02:02:15 UTC
Resolved. All you need to do is uninstall 'pam_bluez' and remove its configuration