Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rustdesk service not starting on gnome shell login screen #8106

Closed
NicKoehler opened this issue May 21, 2024 · 23 comments
Closed

Rustdesk service not starting on gnome shell login screen #8106

NicKoehler opened this issue May 21, 2024 · 23 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@NicKoehler
Copy link
Contributor

NicKoehler commented May 21, 2024

Bug Description

The service is not starting properly on boot using this specs:

Distro: Arch Linux
Kernel: Linux 6.9.1-arch1-1
DE: Gnome 46

this is what systemctl status rustdesk shows

● rustdesk.service - RustDesk
     Loaded: loaded (/etc/systemd/system/rustdesk.service; enabled; preset: disabled)
     Active: active (running) since Tue 2024-05-21 13:02:13 CEST; 23s ago
   Main PID: 675 (rustdesk)
      Tasks: 19 (limit: 38275)
     Memory: 43.0M (peak: 44.4M)
        CPU: 5.573s
     CGroup: /system.slice/rustdesk.service
             └─675 /usr/bin/rustdesk --service

mag 21 13:02:30 arch rustdesk[5031]: sudo: errore nell'inizializzare il plugin di audit sudoers_audit
mag 21 13:02:32 arch sudo[5882]:     root : unknown user listed. ; PWD=/ ; USER=listed. ;

It seems like the error comes from rustdesk parsing an user named "listed." instead of the actual username (maybe root?).

How to Reproduce

  1. install rustdesk
  2. enable rustdesk service
  3. reboot and don't login
  4. try to connect from another client

Expected Behavior

I should be able to connect

Operating system(s) on local side and remote side

All -> Linux

RustDesk Version(s) on local side and remote side

nightly -> nightly

@NicKoehler NicKoehler added the bug Something isn't working label May 21, 2024
@rustdesk
Copy link
Owner

@fufesou

@fufesou
Copy link
Collaborator

fufesou commented May 21, 2024

Thanks for your feedback.

Can you please run longinctl on the server side and paste the output here?
Please hide private info.

@NicKoehler
Copy link
Contributor Author

NicKoehler commented May 21, 2024

From what I can tell seems like the error is from this function:

fn _get_values_of_seat0(indices: &[usize], ignore_gdm_wayland: bool) -> Vec<String> {

Thanks for your feedback.

Can you please run longinctl on the server side and paste the output here? Please hide private info.

SESSION  UID USER SEAT  TTY   STATE  IDLE SINCE    
      2  120 gdm  seat0 tty1  active yes  13min ago
      4 1000 nic  -     pts/0 active no   -        
      5 1000 nic  -     pts/1 active no   -       

3 sessions listed.

In this output I think there is the "listed." word that the function is parsing.

@rustdesk
Copy link
Owner

rustdesk commented May 21, 2024

Is it currently wayland or x11? It is expected if it is wayland. Login Screen is not supported yet for wayland.

@NicKoehler
Copy link
Contributor Author

Same issue with both, the server doesn't show up as online too.

@rustdesk
Copy link
Owner

Both for x11 and wayland?

@NicKoehler
Copy link
Contributor Author

Yes, both X11 and Wayland

@rustdesk
Copy link
Owner

rustdesk commented May 21, 2024

Could confirm with below command?

loginctl show-session -p Type <session-id>

Login screen session type can only be modified via /etc/gdm/custom.conf.

@NicKoehler
Copy link
Contributor Author

I have

loginctl show-session -p Type 2
Type=wayland

But my /etc/gdm/custom.conf is like this:

t# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

@rustdesk
Copy link
Owner

So it is still Wayland.

@NicKoehler
Copy link
Contributor Author

I see, but previously the server would still appear online, and if I tried to connect, it would say that Wayland is not supported. Now it just appears completely off.

@rustdesk
Copy link
Owner

rustdesk commented May 21, 2024

Is this important for you? both not usable. And previously is it gnome 46?

@NicKoehler
Copy link
Contributor Author

No, I just reported it because I was using X11 all the time and suddenly it stopped working. Now I see that the problem is my session still being Wayland and ignoring my custom.conf.

@NicKoehler
Copy link
Contributor Author

Is this important for you? both not usable. And previously is it gnome 46?

No after I updated my nighly after a long time of no updates.

@rustdesk
Copy link
Owner

rustdesk commented May 21, 2024

Nevertheless, you are right, it should show Login screen using Wayland is not supported.
@fufesou follow it up.

@NicKoehler
Copy link
Contributor Author

I wouldn't have opened this issue if I had seen the Wayland message. I would have fixed my session, sorry for the misunderstanding.

@rustdesk
Copy link
Owner

This is a good report. Thanks.

@rustdesk rustdesk added the good first issue Good for newcomers label May 21, 2024
@NicKoehler
Copy link
Contributor Author

I fixed my gdm session now is properly using X and is working fine, so I confirm is only a wayland issue.

@rustdesk
Copy link
Owner

Thanks for your confirmation. How did you fix it to use X?

@NicKoehler
Copy link
Contributor Author

NicKoehler commented May 21, 2024

My custom.conf was not working, for some reason. I fixed it by changing my /usr/share/gdm/gdm.schemas:

<schema>
    <key>daemon/WaylandEnable</key>
    <signature>b</signature>
    <default>false</default>  # <- changed this from true to false and restarted my gdm session.
</schema>

Probably not a proper fix, but it worked.

@rustdesk
Copy link
Owner

Thanks

@rustdesk
Copy link
Owner

rustdesk commented May 22, 2024

@NicKoehler could you help test the latest nightly?

@NicKoehler
Copy link
Contributor Author

Tried both wayland and x with the expected results. Wayland not working but showing a message, x working fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants