Re: Session alrady running

Patrick Dupre via users Sat, 01 Mar 2025 09:00:54 -0800

Some information

1 - pdupre (1000)
Since: Sat 2025-03-01 17:39:04 CET; 5min ago
State: active
Leader: 2209 (vncsession)
Display: :9
Remote: 203.0.113.20
Service: tigervnc
Type: x11
Class: user
Idle: no
Unit: session-1.scope
├─2209 /usr/sbin/vncsession pdupre :9
├─2369 xinit /etc/X11/xinit/Xsession cinnamon-session-cinnamon -- /usr/bin/Xvnc :9 -auth /home/pdupre/.Xauthority -desktop "Sappho:9 (pdupre)" -fp catalogue:/etc/X11/fontpath.d -pn -rfbauth /home/pdupre/.vnc/passwd -rfbport 5909
├─2379 /usr/bin/Xvnc :9 -auth /home/pdupre/.Xauthority -desktop "Sappho:9 (pdupre)" -fp catalogue:/etc/X11/fontpath.d -pn -rfbauth /home/pdupre/.vnc/passwd -rfbport 5909
├─2406 /usr/libexec/cinnamon-session-binary --session cinnamon
├─2701 /usr/bin/ssh-agent /bin/sh -c "exec -l /bin/bash -c \"cinnamon-session-cinnamon\""
├─2753 /usr/bin/gnome-keyring-daemon --start --components=pkcs11
├─2776 /usr/bin/csd-color
├─2778 /usr/bin/csd-settings-remap
├─2779 /usr/bin/csd-clipboard
├─2780 /usr/bin/csd-background
├─2783 /usr/bin/csd-automount
├─2789 /usr/bin/csd-print-notifications
├─2793 /usr/bin/csd-xsettings
├─2794 /usr/bin/csd-a11y-settings
├─2802 /usr/bin/csd-housekeeping
├─2803 /usr/bin/csd-wacom
├─2804 /usr/bin/csd-keyboard
├─2805 /usr/bin/csd-media-keys
├─2806 /usr/bin/csd-screensaver-proxy
├─2807 /usr/bin/csd-power
├─3268 /usr/libexec/csd-printer
├─3330 cinnamon-launcher
├─3440 cinnamon --replace
├─3584 /usr/bin/zeitgeist-datahub
├─3585 /usr/libexec/geoclue-2.0/demos/agent
├─3586 /usr/bin/python3 -Es /usr/bin/seapplet
├─3587 /usr/bin/gnome-software --gapplication-service
├─3595 /usr/libexec/tracker-miner-fs-3
├─3596 /usr/bin/nemo-desktop
├─3601 /usr/bin/nm-applet
├─3604 cinnamon-killer-daemon
├─3606 /usr/libexec/evolution-data-server/evolution-alarm-notify
├─4184 blueberry-tray
├─4195 /usr/bin/sh /usr/lib/blueberry/safechild /usr/sbin/rfkill event
└─4196 /usr/sbin/rfkill event

Mar 01 17:39:05 Sappho vncsession[2209]: pam_unix(tigervnc:session): session opened for user pdupre(uid=1000) by pdupre(uid=0)
Mar 01 17:39:13 Sappho cinnamon-session-binary[2406]: WARNING: t+0.19925s: Could not read /home/pdupre/.config/autostart/Nextcloud.desktop: Could not parse desktop file Nextcloud.desktop or it references a not found TryExec binary
Mar 01 17:39:13 Sappho gnome-keyring-daemon[2753]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 01 17:39:13 Sappho gnome-keyring-daemon[2754]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 01 17:39:13 Sappho gnome-keyring-daemon[2752]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 01 17:39:13 Sappho gnome-keyring-daemon[2753]: discover_other_daemon: 0
Mar 01 17:39:13 Sappho gnome-keyring-daemon[2754]: discover_other_daemon: 0
Mar 01 17:39:13 Sappho gnome-keyring-daemon[2752]: discover_other_daemon: 0
Mar 01 17:39:15 Sappho spice-vdagent[3332]: vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 does not exist, exiting
Mar 01 17:39:17 Sappho cinnamon-killer-daemon[3604]: Bound Cinnamon restart to <Control><Alt>Escape.

There is still a tigervnc session

root 2229 0.0 0.0 13112 5524 ? S 17:49 0:00 /usr/sbin/vncsession pdupre :9
pdupre 2378 0.0 0.0 4040 2304 ? S 17:49 0:00 xinit /etc/X11/xinit/Xsession cinnamon-session-cinnamon -- /usr/bin/Xvnc :9 -auth /home/pdupre/.Xauthority -desktop Sappho:9 (pdupre) -fp catalogue:/etc/X11/fontpath.d -pn -rfbauth /home/pdupre/.vnc/passwd -rfbport 5909
pdupre 2398 0.8 0.3 571180 77940 ? Sl 17:49 0:00 /usr/bin/Xvnc :9 -auth /home/pdupre/.Xauthority -desktop Sappho:9 (pdupre) -fp catalogue:/etc/X11/fontpath.d -pn -rfbauth /home/pdupre/.vnc/passwd -rfbport 5909
pdupre 4735 0.0 0.0 227796 2112 tty3 S+ 17:50 0:00 grep --color=auto vnc

I can kill it, but it will reappear at next restart!

On 1 Mar 2025, at 13:57, Patrick Dupre via users <users@lists.fedoraproject.org> wrote:

On 1 Mar 2025, at 13:42, Patrick Dupre <pdu...@gmx.com> wrote:

Does this help or do it need to run loginctl when I cannot login ?

Login as root and run loginctl. What I suggst you do is look for differences.

I not sure what to look for myself.

The ans is teh same

SESSION UID USER SEAT TTY STATE IDLE SINCE
5 1000 pdupre seat0 tty3 online yes 5h 48min ago
6 1000 pdupre seat0 tty4 active no -

2 sessions listed.

I would run a controlled experiment, starting from a reboot.

Have root logged in on a console, avoid sudo from your user as that

will complicate what you see in loginctl.

Now, step by step, reproduce the problem and get loginctl output at each step, starting with before you first login as your user.

Barry

--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Session alrady running

Reply via email to