Gnome suspend issue [NOT SOLVED - again]

[runningnak3d]

This is so strange that I am not sure if this is the proper place for this, and even if it is, I am not sure what logs to even post.

I am hoping that if I describe the problem, maybe someone out there can point me in the right direction to even start looking.

OK -- so I was running Dantrell's Gnome 3.30 and my laptop would suspend / resume just fine. I upgraded to his 3.32 repo and my laptop stopped suspending.

It suspends OK, and resumes OK except that I don't get a login screen -- I get a greyish / black (could just be the backlight) and can't switch between VTs.
However, if I ssh in, and restart gdm, I lose my session, but I get a login screen.

I figured let's just go with the obvious for now and downgrade back to 3.30. That didn't solve the problem -- it is identical. So I figured I would switch to the new official Gnome 3.30
profile to see if maybe some shared component that Dantrell had forked was the issue. Nope -- same issue.

So, I installed pm-utils to see if I could suspend and maybe get some better logging. Turns out that pm-suspend suspends the laptop just fine, but of course my laptop isn't locked when it is resumed.

That gave me an idea of where to start looking. Some interaction between elogind and gdm. What I found was it looks like elogind tries to delete the session and dbus segfaults.

If anyone has any clue where to start looking, it would be appreciated. I have an nVidia Optimus laptop, but I use bumblebee / nvidia-xrun so the nVidia driver isn't even loaded, and just to be safe, I disabled the bumblebee module as well, so the Intel driver is the only thing loaded.

Just to be clear, hitting the suspend button in Gnome, fails to resume. Closing the laptop lid, fails to resume. Running pm-suspend suspends and resumes, but no lockscreen (ofc).

-- Brian

[dantrell]

[runningnak3d]

[runningnak3d]

Now I am really confused. I upgraded elogind, and the suspend failure came back, so I downgraded it again, and that didn't solve it.

So, just for the heck of it, I did a full upgrade and then a downgrade, and that still didn't solve it.

So, I am running the exact versions of dbus and elogind that I posted above that solved the problem, but it is back.

With the downgraded versions I don't get the dbus segfault on resume.

So -- back to being REALLY stumped. How can downgrading solve the problem, and then just testing a few upgrades make it come back to the point that downgrading doesn't solve it now.

-- Brian

[dantrell]

[runningnak3d]

My procedure was:

Downgrade both elogind and dbus. I skipped upower because there was no older version in the official Gentoo repo (there is literally only one version right now), and I wasn't ready to add yours back yet -- so upower was never touched.

I rebooted since they are boot services -- I didn't want to even risk just restarting them.

When the laptop came back up, I logged in and then immediately suspended the laptop / woke the laptop up -- and viola, I had a login screen. I tested this several times. I rebooted several times. It was working as intended.

Next I did an emerge -1 elogind to upgrade elogind back to the latest version. Rebooted, did the test, and got no login screen.

I restarted gdm to get into my laptop, and then downgraded elogind again back to the version that worked. Rebooted, tested, and still nothing.

I thought maybe they had to be downgraded together (that makes NO sense, but I had to try), so I did an emerge -1 elogind dbus to get them both back to the latest, and rebooted. I doubted it would just magically work with those packages back at versions that hadn't been working, but I tested again just to be sure, but of course no login screen after suspend.

So I rebooted again, and then downgraded both elogind and dbus just like you suggested (and worked the first time) but again, using the oldest versions in the official repo (just as I had done the first time). Rebooted / tested / still no login screen.

I have repeated this several times just to be sure. Also want to be clear at no time were ANY other packages touched.

Lastly, I did remove elogind and dbus completely, disabled xdm(gdm) and rebooted. I then installed the versions of elogind and dbus that were working. I re-enabled xdm(gdm) and rebooted. Still doesn't work.

I am going to enable your repo and downgrade upower now. Even though it wasn't touched there are only a few packages that deal with suspend / resume and upower is one of them.

I am sure once I figure out what is causing this, I am going to kick myself.

Lastly, just because I don't feel like throwing more uncertainty, and don't feel like the long compile, I am going to stay on the official Gnome 3.30 for now. However, if you would like me to post the results to my tests in your thread, I will be happy to since whatever this problem is does affect you as well.

-- Brian

[runningnak3d]

Well, I got tired of fighting with it for now...

My solution for now was to create a shell script with:

[dantrell]

[PF4Public]

Did anyone solve this?