| View previous topic :: View next topic |
| Author |
Message |
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
 Posted: Tue Oct 15, 2024 3:35 pm Post subject: [Solved] Sound/Pipewire/systemctl problem |
 |
|
[Administrator note: this post, and only this post, was originally attached to the solved topic [SOLVED] Sound/Pipewire/systemctl problem. -Hu]
I have all of those Problems as well, but the solution does not work for me. Anything else I can do? Thank you in advance.
PS: How did you manage to solve the shutdown and permission problems?
Last edited by GentooFan2024 on Mon Nov 04, 2024 6:48 pm; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22601
|
| Posted: Tue Oct 15, 2024 4:42 pm Post subject: |
|
|
Welcome to the forums. If you have the same problem as described in the referenced thread, then the solution described in that thread will work for you. If that solution did not work for you, then either you implemented it incorrectly or you have a different problem.
Generally, you should not reopen a solved thread if you need help with the problem it solved. Instead, you should open a new thread, using the old one as a guide for what information to share. You should describe what steps you have taken to try to solve the problem and what, if any, effect those steps had. |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Tue Oct 15, 2024 6:25 pm Post subject: |
|
|
Thank you! I was unsure if I should start a new topic. So I'm on a fresh Gentoo Install (Mate Desktop/systemd) and have all of the Problems that were described in the Other Thread. With my previous Gentoo installation I never had problems with user rights. Like the creator of the other thread, I have problems starting Pipewire for the user with systemctl. I get the error:
| Code: | | Failed to enable unit: Process org.freedesktop.systemd1 exited with status 1 |
When I check the status I get:
| Code: | | Failed to get properties: Process org.freedesktop.systemd1 exited with status 1 |
In the other Thread the Solution for this Problem was to downgrade to Polkit-123. I tried to do so but it didn't change anything.
I also can't shut down or restart the computer. If I try, I am thrown back into lightdm and have to do it from there.
I have one more problem: In my previous installation external drives could be mounted automatically. now I get an error message that I am not authorized to do so.
The only thing I did differently on this Installation was using Btrfs instead of ext4 and encrypting my drive.
I am Glad for any help. Many Thanks in advance.
Please Note: English is not my Native Language, so If there is anything unclear just ask.  |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Fri Oct 18, 2024 7:39 pm Post subject: |
|
|
| Since nobody has replied yet, I assume that nobody knows how to solve the problem. When I installed Gentoo I used this guide for the encryption setup & the Gentoo Handbook for everything else. If there is anything I might have overlooked that could be causing these problems, I would be very grateful for a suggestion. |
|
| Back to top |
|
|
NeglectedRudderPug
n00b
Joined: 04 Oct 2023
Posts: 26
|
| Posted: Sat Oct 19, 2024 3:55 pm Post subject: |
|
|
Interesting.
What user groups is your user in? From your regular user account try the groups command, you should get a similar (but probably not the same) output like this:
| Code: | username@host ~ % groups
wheel video libvirt plugdev username |
If you're using udisks and polkit for mounting devices, you'll want to be in the plugdev group, without it you'll get the error you described. For shutdown / reboots you may need wheel.
It sounds to me you might have missed the final steps?
https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Finalizing |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sat Oct 19, 2024 4:23 pm Post subject: |
|
|
Hey,
Thank you for your response!
My user is in the following groups:
| Code: | florian@floriangentoo ~ $ groups
wheel video usb users plugdev vboxusers pipewire florian |
I have installed acct-group/plugdev very early during the installation, because I wanted to install Network Manager.
I am also in group wheel, because I use sudo. |
|
| Back to top |
|
|
NeglectedRudderPug
n00b
Joined: 04 Oct 2023
Posts: 26
|
| Posted: Sat Oct 19, 2024 4:44 pm Post subject: |
|
|
Hmm. Starting with the basics:
Did you make any changes to the polkit or dbus configuration files? If yes, what did you change?
I assume dbus is running?
| Code: |
$ echo $DBUS_SESSION_BUS_ADDRESS
unix:[..]
|
As long as you get something from this, it's running. This should be setup automatically by your desktop environment.
Did you use a desktop profile? Desktop profiles automatically set the "policykit" use flag, but it's possible to not be set if not using a desktop profile.
Check with:
| Code: | | $ euse -I policykit |
You should get a list with installed packages matching the use flag.
If not, edit /etc/portage/make.conf and add "policykit" to your global use flags. And then run "emerge --ask --changed-use --deep @world". |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sat Oct 19, 2024 5:16 pm Post subject: |
|
|
No, I didn't change the configuration files.
dbus is running.
| Code: |
echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/tmp/dbus-11ioavDSkR,guid=6fb06832d6c4e5dd05539eff6713b119
|
I did chose the "default/linux/amd64/23.0/desktop/systemd (stable)" Profile.
Policykit is set & used.
Custom global USE FLAGS are: "xinerama networkmanager pipewire jack pulseaudio dist-kernel -bluetooth"
Thank you once again for your response |
|
| Back to top |
|
|
NeglectedRudderPug
n00b
Joined: 04 Oct 2023
Posts: 26
|
| Posted: Sat Oct 19, 2024 7:50 pm Post subject: |
|
|
| GentooFan2024 wrote: | No, I didn't change the configuration files.
dbus is running.
| Code: |
echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/tmp/dbus-11ioavDSkR,guid=6fb06832d6c4e5dd05539eff6713b119
|
I did chose the "default/linux/amd64/23.0/desktop/systemd (stable)" Profile.
Policykit is set & used.
Custom global USE FLAGS are: "xinerama networkmanager pipewire jack pulseaudio dist-kernel -bluetooth"
Thank you once again for your response |
That's odd. Why is your dbus path in /tmp? Shouldn't it be in /run/user? Can you use systemctl at all as user?
Try:
| Code: | | $ systemctl --user status |
Does this work?
Also check, as root:
| Code: | $ systemctl status user@1000.service
$ journalctl -xru user@1000.service |
Replace 1000 with your users id. Any significant errors showing?
Also:
| Code: | | $ ls -lav /run/user/ |
This should show a directory with your user id which is owned by your user. |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sat Oct 19, 2024 8:45 pm Post subject: |
|
|
Okay, I did all the things you suggested, with very interesting results:
| Code: | florian@floriangentoo ~ $ systemctl --user status
Failed to read server status: Process org.freedesktop.systemd1 exited with status 1
|
In my case the user id was exactly 1000 so I did:
| Code: |
floriangentoo ~ # systemctl status user@1000.service
○ user@1000.service - User Manager for UID 1000
Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
Drop-In: /usr/lib/systemd/system/user@.service.d
└─10-login-barrier.conf
Active: inactive (dead)
Docs: man:user@.service(5)
|
Out of Interest I tried restarting the server:
| Code: | floriangentoo ~ # systemctl restart user@1000.service
Job for user@1000.service failed because the control process exited with error code.
See "systemctl status user@1000.service" and "journalctl -xeu user@1000.service" for details.
|
I did what the error message suggested:
| Code: |
floriangentoo ~ # systemctl status user@1000.service
× user@1000.service - User Manager for UID 1000
Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
Drop-In: /usr/lib/systemd/system/user@.service.d
└─10-login-barrier.conf
Active: failed (Result: exit-code) since Sat 2024-10-19 22:14:37 CEST; 18s ago
Docs: man:user@.service(5)
Process: 31699 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=1/FAILURE)
Main PID: 31699 (code=exited, status=1/FAILURE)
Error: 49 (Das Protokoll ist nicht verfügbar)
CPU: 10ms
Okt 19 22:14:37 floriangentoo systemd[1]: Starting User Manager for UID 1000...
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_unix(systemd-user:session): session opened for user florian(uid=1000) by florian(uid=0)
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_systemd(systemd-user:session): Failed to get user record: Input/output error
Okt 19 22:14:37 floriangentoo systemd[31699]: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set.
Okt 19 22:14:37 floriangentoo (sd-pam)[31701]: pam_unix(systemd-user:session): session closed for user florian
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Failed with result 'exit-code'.
Okt 19 22:14:37 floriangentoo systemd[1]: Failed to start User Manager for UID 1000.
|
| Code: |
floriangentoo ~ # journalctl -xeu user@1000.service
Okt 19 22:14:37 floriangentoo systemd[1]: Starting User Manager for UID 1000...
░░ Subject: A start job for unit user@1000.service has begun execution
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit user@1000.service has begun execution.
░░
░░ The job identifier is 2662.
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_unix(systemd-user:session): session opened for user florian(uid=1000) by florian(uid=0)
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_systemd(systemd-user:session): Failed to get user record: Input/output error
Okt 19 22:14:37 floriangentoo systemd[31699]: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set.
Okt 19 22:14:37 floriangentoo (sd-pam)[31701]: pam_unix(systemd-user:session): session closed for user florian
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ An ExecStart= process belonging to unit user@1000.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ The unit user@1000.service has entered the 'failed' state with result 'exit-code'.
Okt 19 22:14:37 floriangentoo systemd[1]: Failed to start User Manager for UID 1000.
░░ Subject: A start job for unit user@1000.service has failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit user@1000.service has finished with a failure.
░░
░░ The job identifier is 2662 and the job result is failed.
|
Note: This is a shortened version of the Error message there were many lines with just the "~" character.
Next:
| Code: | floriangentoo ~ # journalctl -xru user@1000.service
Okt 19 22:14:37 floriangentoo systemd[1]: Failed to start User Manager for UID 1000.
░░ Subject: A start job for unit user@1000.service has failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit user@1000.service has finished with a failure.
░░
░░ The job identifier is 2662 and the job result is failed.
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ The unit user@1000.service has entered the 'failed' state with result 'exit-code'.
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ An ExecStart= process belonging to unit user@1000.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Okt 19 22:14:37 floriangentoo (sd-pam)[31701]: pam_unix(systemd-user:session): session closed for user florian
Okt 19 22:14:37 floriangentoo systemd[31699]: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set.
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_systemd(systemd-user:session): Failed to get user record: Input/output error
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_unix(systemd-user:session): session opened for user florian(uid=1000) by florian(uid=0)
Okt 19 22:14:37 floriangentoo systemd[1]: Starting User Manager for UID 1000...
░░ Subject: A start job for unit user@1000.service has begun execution
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit user@1000.service has begun execution.
░░
░░ The job identifier is 2662.
|
And lastly:
| Code: |
floriangentoo ~ # ls -lav /run/user/
insgesamt 0
drwxr-xr-x 2 root root 40 19. Okt 22:14 .
drwxr-xr-x 21 root root 480 19. Okt 15:16 ..
|
Something is very Odd here. It seems to complain about $XDG_RUNTIME_DIR. I have never heard of that. |
|
| Back to top |
|
|
NeglectedRudderPug
n00b
Joined: 04 Oct 2023
Posts: 26
|
| Posted: Sat Oct 19, 2024 9:54 pm Post subject: |
|
|
That result is expected, that is, you shouldn't ever need or want to manually start that service. It should be running automatically as soon as you login.
Does lightdm have the systemd USE flag activated?
Also, you could try this, but consider this an "untested, may or may not work and could cause a failure in login" kind of thing and is just a theory. I don't use lightdm so have no way of checking for myself at the moment.
According to:
https://wiki.gentoo.org/wiki/LightDM
Theoretically we may be able to:
| Code: |
root $ cp /etc/pam.d/lightdm /root/lightdm.bak
root $ cat /etc/pam.d/lightdm | grep pam_systemd.so
|
If that returned nothing:
| Code: |
root $ echo "session required pam_systemd.so" >> /etc/pam.d/lightdm
|
Reboot and try logging in as your user using lightdm. If you successfully get logged in go to your terminal and try "systemctl --user status" again.
If it still doesn't work or you get other login related issues:
| Code: |
root $ cp lightdm.bak /etc/pam.d/lightdm
|
I'd like to also mention, I am just a user like you, I too am prone to errors. Hence the backup.  |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sat Oct 19, 2024 10:21 pm Post subject: |
|
|
I did try that, but it resulted in Problems, so I restored the backup. Nevertheless, thank you very much for your help!
The systemd Use Flag is globally set by the Profile. |
|
| Back to top |
|
|
NeglectedRudderPug
n00b
Joined: 04 Oct 2023
Posts: 26
|
| Posted: Sun Oct 20, 2024 12:15 am Post subject: |
|
|
Hmm. It really should 'just work' to be honest. I took the liberty of noseying through the ebuild:
https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-misc/lightdm/lightdm-1.32.0-r2.ebuild
Which lead me to: https://bugs.gentoo.org/372229
So.. it should absolutely be loading pam_systemd already. A slightly deeper dive lead me to /etc/pam.d/system-login - you should find pam_systemd already in this file.
I'm not sure what's going on here. The other thread spoke about downgrading polkit, which you've already tried. Did you also try going up to 125, it's worth a shot I guess? |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sun Oct 20, 2024 2:10 pm Post subject: |
|
|
I actually did upgrade to Polkit-125 but that didn't work. I apologize, I should have mentioned that earlier.
I found something interesting in the file you mentioned:
| Code: | floriangentoo ~ # cat /etc/pam.d/system-login | grep pam_systemd.so
-session optional pam_systemd.so
|
"optional" instead of "required". Maybe I should change that? |
|
| Back to top |
|
|
NeglectedRudderPug
n00b
Joined: 04 Oct 2023
Posts: 26
|
| Posted: Sun Oct 20, 2024 2:37 pm Post subject: |
|
|
| GentooFan2024 wrote: | I actually did upgrade to Polkit-125 but that didn't work. I apologize, I should have mentioned that earlier.
I found something interesting in the file you mentioned:
| Code: | floriangentoo ~ # cat /etc/pam.d/system-login | grep pam_systemd.so
-session optional pam_systemd.so
|
"optional" instead of "required". Maybe I should change that? |
That appears to be set correctly, it matches perfectly with what is in the original stage3, and also what is on my system. So, it's probably best to leave that.
What does the system do when you try from tty? Login to your user account on tty (no gui, ctrl + alt + f6, for example) and run systemctl --user from there, does it output correctly then?
I guess another option you could try is using the stage3 to extract the /etc/pam.d/* files into your current /etc/pam.d/* directory - this would catch anything that may have gone amiss for some odd reason, though it will not include the files added by lightdm and other sources, so be sure that you do not to empty out additional files or that you have them reinstalled by the ebuilds that originally added them.
You could also check for other missing files, for example do you have /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop? Though admittedly I'm taking guesses at the moment.  |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sun Oct 20, 2024 3:58 pm Post subject: |
|
|
I tried everything:
When I run systemctl --user from tty I get a "Failed to connect to bus: Kein Medium gefunden." error. ("Kein Medium gefunden" is German for "No media found".)
I checked the /etc/pam.d/ directory and compared it with the latest stage3. The files had the Identical date. Two files were older, but their content was identical.
/etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop does exist.
On my search I have found this: https://bbs.archlinux.org/viewtopic.php?id=275801
I will try the solution out, maybe it helps. |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sun Oct 20, 2024 4:03 pm Post subject: |
|
|
| Update: Doesn't help: I get the same error as above. |
|
| Back to top |
|
|
NeglectedRudderPug
n00b
Joined: 04 Oct 2023
Posts: 26
|
| Posted: Mon Oct 21, 2024 10:59 pm Post subject: |
|
|
| GentooFan2024 wrote: | I tried everything:
When I run systemctl --user from tty I get a "Failed to connect to bus: Kein Medium gefunden." error. ("Kein Medium gefunden" is German for "No media found".)
I checked the /etc/pam.d/ directory and compared it with the latest stage3. The files had the Identical date. Two files were older, but their content was identical.
/etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop does exist.
On my search I have found this: https://bbs.archlinux.org/viewtopic.php?id=275801
I will try the solution out, maybe it helps. |
That rules out lightdm and any PAM configuration related to it being the cause. We're going to need to find more logs for this. Repeat the process and trigger the error again, but this time after that, switch to another tty (while leaving that one active) and log directly in as root.
Do you see your user session listed when you run?:
| Code: |
$ loginctl list-sessions
|
You should see your user here.
Also, try:
| Code: |
$ journalctl -xru user@1000.service
|
Don't try restarting the service first (or after). Is there anything at all listed here that might indicate the issue?
If there's nothing obvious there, just try general log checking (Use arrow keys to navigate, q to exit):
Note: These logs are in reverse, so most recent messages first.
There has to be some kind of error somewhere? |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Tue Oct 22, 2024 3:18 pm Post subject: |
|
|
I reproduced the error and then logged on to a new tty as root:
Output of loginctl list-sessions:
| Code: |
SESSION UID USER SEAT TTY STATE IDLE SINCE
1 0 root seat0 - online no -
4 0 root seat0 tty2 active no -
2 sessions listed.
|
My user seems to be invisible.
Output of journalctl -xru user@1000.service:
| Code: |
Okt 19 22:14:37 floriangentoo systemd[1]: Failed to start User Manager for UID 1000.
░░ Subject: A start job for unit user@1000.service has failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit user@1000.service has finished with a failure.
░░
░░ The job identifier is 2662 and the job result is failed.
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ The unit user@1000.service has entered the 'failed' state with result 'exit-code'.
Okt 19 22:14:37 floriangentoo systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ An ExecStart= process belonging to unit user@1000.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Okt 19 22:14:37 floriangentoo (sd-pam)[31701]: pam_unix(systemd-user:session): session closed for user florian
Okt 19 22:14:37 floriangentoo systemd[31699]: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set.
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_systemd(systemd-user:session): Failed to get user record: Input/output error
Okt 19 22:14:37 floriangentoo (systemd)[31699]: pam_unix(systemd-user:session): session opened for user florian(uid=1000) by florian(uid=0)
Okt 19 22:14:37 floriangentoo systemd[1]: Starting User Manager for UID 1000...
░░ Subject: A start job for unit user@1000.service has begun execution
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit user@1000.service has begun execution.
░░
░░ The job identifier is 2662.
|
Seems to be the same error as before.
Part of the output of journalctl -xr was:
| Code: |
Okt 22 16:12:32 floriangentoo login[1350]: ROOT LOGIN on '/dev/tty2'
Okt 22 16:12:32 floriangentoo systemd[1]: Started Session 4 of User root.
░░ Subject: A start job for unit session-4.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit session-4.scope has finished successfully.
░░
░░ The job identifier is 1253.
Okt 22 16:12:32 floriangentoo systemd-logind[1125]: New session 4 of user root.
░░ Subject: A new session 4 has been created for user root
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░ Documentation: sd-login(3)
░░
░░ A new session with the ID 4 has been created for the user root.
░░
░░ The leading process of the session is 1345.
Okt 22 16:12:32 floriangentoo login[1345]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Okt 22 16:12:13 floriangentoo systemd[1]: Started Getty on tty2.
░░ Subject: A start job for unit getty@tty2.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
░░ A start job for unit getty@tty2.service has finished successfully.
░░
░░ The job identifier is 1148.
Okt 22 16:11:53 floriangentoo login[1184]: pam_systemd(login:session): Failed to get user record: Input/output error
Okt 22 16:11:53 floriangentoo login[1184]: pam_unix(login:session): session opened for user florian(uid=1000) by florian(uid=0)
Okt 22 16:11:22 floriangentoo systemd[1]: systemd-hostnamed.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
|
I have a small additional question: Sometimes my user session just randomly crashes and I have to re-login. Do you know what could be causing this? (But I don't think it's related to this problem, as it was already the case on the previous installation).
Once again, thanks for your help! |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Fri Oct 25, 2024 9:33 pm Post subject: |
|
|
I am wondering if this Problem maybe could have something to do with the current stage3. Therefore I'm considering to do a Gentoo reinstall with an older version of the stage3.
Still I would prefer not to repeat the whole thing. |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sat Nov 02, 2024 12:06 am Post subject: |
|
|
I forgot to reply here: I did the re-installation (with the current stage3, as older ones weren't available anymore) but I still have the same Problems. However I seem to have fewer errors in the Logs:
| Code: |
florian@floriangentoo ~ $ systemctl --user enable --now pipewire.service
Failed to enable unit: Process org.freedesktop.systemd1 exited with status 1
florian@floriangentoo ~ $ systemctl --user status user@1000.service
Failed to get properties: Process org.freedesktop.systemd1 exited with status 1
florian@floriangentoo ~ $ sudo -i
floriangentoo ~ # journalctl -xru user@1000.service
-- No entries --
floriangentoo ~ # journalctl -xr
Nov 02 00:58:07 floriangentoo sudo[2165]: pam_unix(sudo-i:session): session opened for user root(uid=0) by florian(uid=1000)
Nov 02 00:58:07 floriangentoo sudo[2165]: florian : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/bash
Nov 02 00:57:59 floriangentoo dbus-daemon[1207]: [session uid=1000 pid=1205 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Nov 02 00:57:59 floriangentoo dbus-daemon[1207]: [session uid=1000 pid=1205 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.34' (uid=1000 pid=2159 comm="systemctl --user status user@1000.service")
Nov 02 00:57:46 floriangentoo dbus-daemon[1207]: [session uid=1000 pid=1205 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Nov 02 00:57:46 floriangentoo dbus-daemon[1207]: [session uid=1000 pid=1205 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.33' (uid=1000 pid=2154 comm="systemctl --user enable --now pipewire.service")
Nov 02 00:57:36 floriangentoo sudo[1650]: pam_unix(sudo-i:session): session closed for user root
Nov 02 00:56:44 floriangentoo systemd[1]: systemd-timedated.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://gentoo.org/support/
░░
|
I still appreciate any Help or Ideas. |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sat Nov 02, 2024 5:57 pm Post subject: |
|
|
I started wondering why my user session always seems to be seen as root.
I have found out:
/run/user/1000 does not exist. Only /run/user/0.
~/.local/share/systemd/ does not exist.
~/.config/systemd/ does not exist.
Is there anything I can do now? I have lost all hope in Solving this. |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 5063
Location: Bavaria
|
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sat Nov 02, 2024 6:39 pm Post subject: |
|
|
Hey pietinger, thanks for your reply!
My user is a normal user. The odd thing is: When I read the system logs it seems like my user (id 1000) starts a root session (id 0).
I have searched all over the web, yet I'm still not finding any solution. It's very frustrating.  |
|
| Back to top |
|
|
GentooFan2024
n00b
Joined: 15 Oct 2024
Posts: 20
|
| Posted: Sun Nov 03, 2024 3:32 pm Post subject: |
|
|
| I am wondering if switching to openrc might solve my Problem. Is there a guide for switching from an existing installation, or is it a better Idea to restart completely? |
|
| Back to top |
|
|
|
Installing Gentoo
