Session alrady running

[Patrick Dupre]

Hello,

Now, propabaly after a remmina session, I get

Session alrady running
Log is not possible because a remore session is already running for
To login, you must log out from the remote session or force stop it

The only option is to canczl.

Then I run

sudo pkill -KILL -u <username>

This let me login, but the issue reappears at the next time.

Would you have a solution?

Thank.

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
===========================================================================

[Patrick Dupre]

> Hello,
>
> Now, propabaly after a remmina session, I get
>
> Session alrady running
> Log is not possible because a remore session is already running for
> To login, you must log out from the remote session or force stop it
>
> The only option is to canczl.
>
> Then I run
>
> sudo pkill -KILL -u <username>
>
> This let me login, but the issue reappears at the next time.
>
> Would you have a solution?
>
> Thank.

Despite I do not use anymore remmina and that I run
sudo pkill -KILL -u  <user>
(this let me login and run an X session)
The issue reappears every time that I restart the PC.
> ===========================================================================
>  Patrick DUPRÉ                                 | | email: [e-mail]
> ===========================================================================
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Barry]

> On 28 Feb 2025, at 13:42, Patrick Dupre via users  wrote:
>
> Would you have a solution?

Have a look at loginctl reports to see if you can find a clue what is happening.
For example list sessions before and after the problem happens.

Barry

[Patrick Dupre]

> > On 28 Feb 2025, at 13:42, Patrick Dupre via users  wrote:
> >
> > Would you have a solution?
>
> Have a look at loginctl reports to see if you can find a clue what is happening.
> For example list sessions before and after the problem happens.
>
> Barry

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

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

2 sessions listed.

loginctl session-status 5
5 - pdupre (1000)
  Since: Sat 2025-03-01 09:05:13 CET; 5h 33min ago
  State: online
 Leader: 4538 (login)
   Seat: seat0; vc3
    TTY: tty3
 Remote: no
Service: login
   Type: tty
  Class: user
   Idle: yes since Sat 2025-03-01 09:06:46 CET (5h 31min ago)
   Unit: session-5.scope
         ├─4538 "login -- pdupre"
         └─4582 -bash

Mar 01 09:05:13 Sappho systemd[1]: Started session-5.scope - Session 5 of User pdupre.
Mar 01 09:05:13 Sappho login[4538]: LOGIN ON tty3 BY pdupre
Mar 01 09:06:46 Sappho sudo[4801]:   pdupre : TTY=tty3 ; PWD=/home/pdupre ; USER=root ; COMMAND=/usr/bin/pkill -u pdupre
Mar 01 09:06:46 Sappho sudo[4801]: Unable to get ecryptfs pam data : No module specific data is present
Mar 01 09:06:46 Sappho sudo[4801]: pam_unix(sudo:session): session opened for user root(uid=0) by pdupre(uid=1000)
Mar 01 09:06:46 Sappho sudo[4801]: pam_unix(sudo:session): session closed for user root

loginctl session-status 6
6 - pdupre (1000)
  Since: Sat 2025-03-01 09:07:24 CET; 5h 31min ago
  State: active
 Leader: 5142 (gdm-session-wor)
   Seat: seat0; vc4
    TTY: tty4
 Remote: no
Service: gdm-password
   Type: x11
  Class: user
   Idle: no
   Unit: session-6.scope
         ├─5142 "gdm-session-worker [pam/gdm-password]"
         ├─5194 /usr/bin/gnome-keyring-daemon --daemonize --login
         ├─5237 /usr/libexec/gdm-x-session --run-script /usr/bin/gnome-session
         ├─5241 /usr/libexec/Xorg vt4 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
         ├─5336 /usr/libexec/gnome-session-binary
         └─5597 /usr/bin/ssh-agent /bin/sh -c "exec -l /bin/bash -c "/usr/bin/gnome-session""

Mar 01 09:34:27 Sappho /usr/libexec/gdm-x-session[5241]: (II) modeset(0): Modeline "1920x1080"x0.0  110.90  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
Mar 01 11:32:03 Sappho gdm-password][800866]: gkr-pam: unlocked login keyring
Mar 01 11:44:53 Sappho /usr/libexec/gdm-x-session[5241]: (II) modeset(0): EDID vendor "LGD", prod id 1135
Mar 01 11:44:53 Sappho /usr/libexec/gdm-x-session[5241]: (II) modeset(0): Printing DDC gathered Modelines:
Mar 01 11:44:53 Sappho /usr/libexec/gdm-x-session[5241]: (II) modeset(0): Modeline "1920x1080"x0.0  138.70  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
Mar 01 11:44:53 Sappho /usr/libexec/gdm-x-session[5241]: (II) modeset(0): Modeline "1920x1080"x0.0  110.90  1920 1968 2000 2080  1080 1083 1088 1111 +hsync -vsync (53.3 kHz e)
Mar 01 12:46:20 Sappho /usr/libexec/gdm-x-session[5241]: (II) Axis 0 value 1255 is outside expected range [1260, 5917]
Mar 01 12:46:20 Sappho /usr/libexec/gdm-x-session[5241]: See https://wayland.freedesktop.org/libinput/doc/1.26.2/absolute_coordinate_rang... for details
Mar 01 14:29:53 Sappho /usr/libexec/gdm-x-session[5241]: (II) Axis 0x1 value 1024 is outside expected range [1238, 4969]
Mar 01 14:29:53 Sappho /usr/libexec/gdm-x-session[5241]: See https://wayland.freedesktop.org/libinput/doc/1.26.2/absolute_coordinate_rang... for details

[Barry Scott]

> On 1 Mar 2025, at 13:42, Patrick Dupre  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.

Barry

[Barry]

> On 1 Mar 2025, at 13:57, Patrick Dupre via users  wrote:
>
> 
>
> On 1 Mar 2025, at 13:42, Patrick Dupre  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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Hi.

On Sat, 01 Mar 2025 17:59:58 +0100 Patrick Dupre via users wrote:
> Some information
>      ├─2209 /usr/sbin/vncsession pdupre :9
>      ├─2369 xinit /etc/X11/xinit/Xsession cinnamon-session-cinnamon --

You have enabled a VNC session on display :9 using cinnamon.

Disable it with: systemctl disable vncserver@:9.service

Stop it with: systemctl stop vncserver@:9.service`

Ref: /usr/lib/systemd/system/vncserver@.service

[Patrick Dupre]

Thanks.

What induced in error is that status said
 Active: inactive (dead) since Sat 2025-03-01 17:51:43 CET; 44min ago

Then I did not think that it could be enabled

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
===========================================================================
> Sent: Saturday, March 01, 2025 at 6:34 PM
> From: [e-mail]
> To: "Community support for Fedora users" 
> Cc: "Barry" , "Patrick Dupre" 
> Subject: Re: Session alrady running
>
> Hi.
>
> On Sat, 01 Mar 2025 17:59:58 +0100 Patrick Dupre via users wrote:
> > Some information
> >      ├─2209 /usr/sbin/vncsession pdupre :9
> >      ├─2369 xinit /etc/X11/xinit/Xsession cinnamon-session-cinnamon --
>
> You have enabled a VNC session on display :9 using cinnamon.
>
> Disable it with: systemctl disable vncserver@:9.service
>
> Stop it with: systemctl stop vncserver@:9.service`
>
> Ref: /usr/lib/systemd/system/vncserver@.service
>
> -- 
> francis

On Sat, 01 Mar 2025 19:01:50 +0100 Patrick Dupre wrote:
> What induced in error is that status said
>  Active: inactive (dead) since Sat 2025-03-01 17:51:43 CET; 44min ago
> Then I did not think that it could be enabled

enabled and active are distinct things.

In "systemctl status", look at the Loaded line: it indicates if the unit is
enabled or disabled.

Example for sshd:

systemctl -n 0 status sshd
  sshd.service - OpenSSH server daemon
       Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; preset: enabled)
      Drop-In: /usr/lib/systemd/system/service.d
               └─10-timeout-abort.conf
       Active: active (running) since Thu 2025-02-27 16:06:03 CET; 2 days ago
  <snip>