Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: There is no gdm.service, so where to add gdm session exec line?

  1. #11
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    30,513
    Blog Entries
    15

    Default Re: There is no gdm.service, so where to add gdm session exec line?

    Quote Originally Posted by 53Ri41 View Post
    This has become confusing and frustrating.
    I can't find any information on the exit-code "status=243", and the command works.
    The unit works as long as I manually start it prior to logging into a wayland session,
    but the unit errors when auto started.

    Any help is appreciated.

    -Cyril

    Code:
    cyril@ten:~> systemctl status tvRGBa.service 
    ● tvRGBa.service - Force tvRGB output
       Loaded: loaded (/etc/systemd/system/tvRGBa.service; enabled; vendor preset: disabled)
       Active: inactive (dead) since Mon 2019-10-21 16:50:04 EDT; 2min 23s ago
      Process: 1748 ExecStart=-/usr/bin/proptest -M i915 -D /dev/dri/card0 68 connector 70 2 (code=exited, status=243)
     Main PID: 1748 (code=exited, status=243)
    Hi
    For the service type have you tried simple or forking?
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  2. #12
    Join Date
    Jun 2008
    Location
    Belleville, Ontario, Canada
    Posts
    493

    Default Re: There is no gdm.service, so where to add gdm session exec line?

    Quote Originally Posted by 53Ri41 View Post
    This has become confusing and frustrating.
    I can't find any information on the exit-code "status=243", and the command works.
    The unit works as long as I manually start it prior to logging into a wayland session,
    but the unit errors when auto started.

    Any help is appreciated.

    -Cyril

    Code:
    cyril@ten:~> systemctl status tvRGBa.service 
    ● tvRGBa.service - Force tvRGB output
       Loaded: loaded (/etc/systemd/system/tvRGBa.service; enabled; vendor preset: disabled)
       Active: inactive (dead) since Mon 2019-10-21 16:50:04 EDT; 2min 23s ago
      Process: 1748 ExecStart=-/usr/bin/proptest -M i915 -D /dev/dri/card0 68 connector 70 2 (code=exited, status=243)
     Main PID: 1748 (code=exited, status=243)
    This, might be the reason:
    Code:
    ExecStart=-/usr/bin/proptest -M i915 -D /dev/dri/card0 68 connector 70 2 (code=exited, status=243)
    Notice the red "-"?
    Maybe try:
    Code:
    ExecStart=/usr/bin/proptest -M i915 -D /dev/dri/card0 68 connector 70 2 (code=exited, status=243)
    this instead. I could be wrong, though.
    "Making rich people richer doesn't make the rest of us richer." Ha-Joon Chang
    openSUSE 15.1 4.12.14-lp151.28.16-default x64

  3. #13
    Join Date
    Sep 2012
    Posts
    6,251

    Default Re: There is no gdm.service, so where to add gdm session exec line?

    Quote Originally Posted by 53Ri41 View Post
    The unit works as long as I manually start it prior to logging into a wayland session,
    but the unit errors when auto started.
    This and the fact that it works when you go via shell indirection suggests race condition. Unit is started too early before device /dev/dri/card0 becomes available. Unfortunately I do not see any easy way to delay unit initialization in this case. Could you provide full "journalctl -b" output after unit failed during system startup?

    Quote Originally Posted by kerijan2003 View Post
    Notice the red "-"? I could be wrong, though.
    You are, sorry. Read systemd.service manual for explanation of this red "-".

  4. #14

    Default Re: There is no gdm.service, so where to add gdm session exec line?

    Quote Originally Posted by malcolmlewis View Post
    For the service type have you tried simple or forking?
    Quote Originally Posted by kerijan2003 View Post
    This, [ dash ] might be the reason...
    Quote Originally Posted by arvidjaar View Post
    This and the fact that it works when you go via shell indirection suggests race condition....
    Regarding the dash in the command, it is designed for use in units with the ExecStartPre/Post= lines. In a single-command unit like the one(s) that I am attempting, it is neither problematic nor useful. Thanks for pointing it out though.

    plymouth-start.service (or whatever combination is called by 'splash=silent quiet' ) causes the command to fail. I was occasionally disabling it via grub edit to try and visually see where things were going wrong, not realizing that was having an effect on the success or failure of the command, and resulting in some frustrating inconsistencies and tail-chasing.

    I was initially thinking race-condition as well, specifically with udev, but found that the default dependencies force my unit to run after all relevant dependencies have been established (sysinit.target).

    There have been a few other tweaks that seem to have helped as well, although I am still testing. Ideally I will find a unit that will work with plymouth enabled, but I won't be bent on working that out.
    - Type matters. I am having the best results with Type=idle

    Thank you all for your help with this.
    -Cyril

  5. #15

    Default Re: There is no gdm.service, so where to add gdm session exec line?

    That wasn't the most clear post. I will reiterate.

    The main culprit seems to have been the boot splash, or whatever group of services that are called when the kernel boot parameter 'splash=silent quiet' is used.
    While the boot splash is running, any and all attempts to run that 'proptest' command fail.
    My manual unit-start successes were because the splash/boot animation wasn't running.
    I was occasionally disabling it via grub edit to try and visually see where things were going wrong, not realizing that it was having an effect on the success or failure of the command, and resulting in some frustrating inconsistencies and tail-chasing.

    Although early in testing, the service unit now seems to complete successfully more often than not, and the conditions where it fails are consistent and repeatable.

    -Cyril

  6. #16
    Join Date
    Sep 2012
    Posts
    6,251

    Default Re: There is no gdm.service, so where to add gdm session exec line?

    Quote Originally Posted by 53Ri41 View Post
    While the boot splash is running, any and all attempts to run that 'proptest' command fail.
    Makes sense. Plymouth is probably "master" of display and locks other consumers out.

    Try to order your service after plymouth-quit-wait.service.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •