Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 2:57 PM, InvalidPath wrote: > > > On Thu, Jan 25, 2018 at 2:55 PM, InvalidPath > wrote: > >> >> >> On Thu, Jan 25, 2018 at 1:22 PM, InvalidPath >> wrote: >> >>> >>> >>> On Thu, Jan 25, 2018 at 1:18 PM, Ed Greshko >>> wrote: >>> On 01/26/18 03:57, InvalidPath wrote:

Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 2:55 PM, InvalidPath wrote: > > > On Thu, Jan 25, 2018 at 1:22 PM, InvalidPath > wrote: > >> >> >> On Thu, Jan 25, 2018 at 1:18 PM, Ed Greshko wrote: >> >>> On 01/26/18 03:57, InvalidPath wrote: >>> > So I think you are right.. I'd have to change this file to point >>> t

Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 1:22 PM, InvalidPath wrote: > > > On Thu, Jan 25, 2018 at 1:18 PM, Ed Greshko wrote: > >> On 01/26/18 03:57, InvalidPath wrote: >> > So I think you are right.. I'd have to change this file to point >> towards the PLasma >> > equivalent of GDM. >> >> >> Just do what I said

Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 1:18 PM, Ed Greshko wrote: > On 01/26/18 03:57, InvalidPath wrote: > > So I think you are right.. I'd have to change this file to point towards > the PLasma > > equivalent of GDM. > > > Just do what I said > > systemctl -f enable sddm.service > > Don't do anything manu

Re: Suspend to Ram Issues

On 01/26/18 03:57, InvalidPath wrote: > So I think you are right.. I'd have to change this file to point towards the > PLasma > equivalent of GDM. Just do what I said systemctl -f enable sddm.service Don't do anything manually.  Do proper system administration. -- A motto of mine is: Whe

Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 12:26 PM, Ed Greshko wrote: > On 01/26/18 01:00, InvalidPath wrote: > > I did a cursory google last night for wayland on Plasma... didnt have > much luck. I > > need to discover what part of Gnome borked me over this AM. > > > This thread has been rather long, and fragment

Re: Suspend to Ram Issues

On 01/26/18 01:00, InvalidPath wrote: > I did a cursory google last night for wayland on Plasma... didnt have much > luck. I > need to discover what part of Gnome borked me over this AM. This thread has been rather long, and fragmented.  So, just 2 observations which you need to think about. 1

Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 10:55 AM, Wolfgang Pfeiffer wrote: > On Thu, 25 Jan 2018 10:09:40 -0700 > InvalidPath wrote: > > > > > > Oh crap, my bad. I was confusing my two currently open issues. > Apologies. > > > > I did not run into the black screen after awaking today because last > night > > m

Re: Suspend to Ram Issues

On Thu, 25 Jan 2018 10:09:40 -0700 InvalidPath wrote: > > Oh crap, my bad. I was confusing my two currently open issues. Apologies. > > I did not run into the black screen after awaking today because last night > my battery was drained due to forgetting to plug it in. .. and you put it on

Re: Suspend to Ram Issues

Allegedly, on or about 25 January 2018, Frank Elsner sent: > I don't think that the display manager is of any significance as the > problem occures when using "pm-suspend" in a console window. Or even > on an alphanumireic display (ctrl+alt+f2). Probably not, but they asked what GDM was. Anyway,

Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 10:01 AM, Frank Elsner wrote: > On Fri, 26 Jan 2018 03:04:17 +1030 Tim wrote: > > [ ... ] > > > You can install more than one display manager, and choose which one you > > want to be run. > > > > A list of just a few others: > > > > KDM, KDE > > XDM, a bare-bones X displ

Re: Suspend to Ram Issues

On Thu, 25 Jan 2018 17:47:11 +0100 Wolfgang Pfeiffer wrote: > On Thu, 25 Jan 2018 07:09:42 -0700 > InvalidPath wrote: > > > On Jan 25, 2018 6:35 AM, "Wolfgang Pfeiffer" wrote: > > I hear you, but no I have not tried without X yet. If suspending worked > > without X then the forward option wou

Re: Suspend to Ram Issues

On Fri, 26 Jan 2018 03:04:17 +1030 Tim wrote: [ ... ] > You can install more than one display manager, and choose which one you > want to be run. > > A list of just a few others: > > KDM, KDE > XDM, a bare-bones X display manager > LXDM, for LXDE > SDDM I don't think that the display manager

Re: Suspend to Ram Issues

On Thu, Jan 25, 2018 at 9:47 AM, Wolfgang Pfeiffer wrote: > On Thu, 25 Jan 2018 07:09:42 -0700 > InvalidPath wrote: > > > On Jan 25, 2018 6:35 AM, "Wolfgang Pfeiffer" wrote: > > > > > > > Plus: I'm running out of ideas: Did you try to start your machine > > without X? There's a link in my previ

Re: Suspend to Ram Issues

On Thu, 25 Jan 2018 07:09:42 -0700 InvalidPath wrote: > On Jan 25, 2018 6:35 AM, "Wolfgang Pfeiffer" wrote: > > > Plus: I'm running out of ideas: Did you try to start your machine > without X? There's a link in my previous message to a fedora page where > this is described in detail > Se

Re: Suspend to Ram Issues

Allegedly, on or about 24 January 2018, InvalidPath sent: > So correct me if Im wrong but *GDM*.. that stuff is all related to > Gnome yes? Related, but not essentially. Assuming that there's nothing else using the same initials, GDM is the Gnome Display Manager. In essence, it's the default log

Re: Suspend to Ram Issues

On Jan 25, 2018 6:35 AM, "Wolfgang Pfeiffer" wrote: On Thu, 25 Jan 2018 14:58:54 +0800 Ed Greshko wrote: > On 01/25/18 13:58, InvalidPath wrote: > > One thing of interest. I googled "Dell XPS 15 9550 sleep problem" and was > surprised by what was returned. So, maybe the problem isn't re

Re: Suspend to Ram Issues

On Thu, 25 Jan 2018 14:58:54 +0800 Ed Greshko wrote: > On 01/25/18 13:58, InvalidPath wrote: > > One thing of interest.   I googled "Dell XPS 15 9550 sleep problem" and > was > surprised by what was returned.  So, maybe the problem isn't related to Linux > at all? > @ed: It worked for t

Re: Suspend to Ram Issues

On Thu, 25 Jan 2018 03:20:48 +0800 Ed Greshko wrote: [ ... ] > Too early for me to attempt looking at the log   But what is the output > of > > systemctl status systemd-suspend.service Here is mine: # systemctl status systemd-suspend.service ● systemd-suspend.service - Suspend L

Re: Suspend to Ram Issues

On 01/25/18 13:58, InvalidPath wrote: > > Yeah I noticed the lack of entries myself... I have not looked but would > messages > nab anything? I wonder if teh suspend.service file itself could be setup to > log > elsewhere.. possibly a bit more verbosely? I doubt it.  It is doing shutting down H

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 10:43 PM, Ed Greshko wrote: > On 01/25/18 12:41, InvalidPath wrote: > > So since my log paste above I have suspended this guy two more times.. > for maybe 10 > > minutes then almost an hour respectively and both times the bloody thing > started up > > as a new boot. Each

Re: Suspend to Ram Issues

On 01/25/18 12:41, InvalidPath wrote: > So since my log paste above I have suspended this guy two more times.. for > maybe 10 > minutes then almost an hour respectively and both times the bloody thing > started up > as a new boot.  Each time I went to try sifting thru journalctl again but got > r

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 8:14 PM, InvalidPath wrote: > > > On Wed, Jan 24, 2018 at 7:55 PM, InvalidPath > wrote: > >> >> >> On Wed, Jan 24, 2018 at 7:54 PM, InvalidPath >> wrote: >> >>> >>> >>> On Wed, Jan 24, 2018 at 7:48 PM, InvalidPath >>> wrote: >>> Aaand this crap just happened again.

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 7:55 PM, InvalidPath wrote: > > > On Wed, Jan 24, 2018 at 7:54 PM, InvalidPath > wrote: > >> >> >> On Wed, Jan 24, 2018 at 7:48 PM, InvalidPath >> wrote: >> >>> Aaand this crap just happened again. Suspended for less than 4 hours and >>> the damned thing shutdown at some

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 7:54 PM, InvalidPath wrote: > > > On Wed, Jan 24, 2018 at 7:48 PM, InvalidPath > wrote: > >> Aaand this crap just happened again. Suspended for less than 4 hours and >> the damned thing shutdown at some point. Here's the related journalctl >> entries.. >> >> >> >> Jan 24

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 7:48 PM, InvalidPath wrote: > Aaand this crap just happened again. Suspended for less than 4 hours and > the damned thing shutdown at some point. Here's the related journalctl > entries.. > > > > Jan 24 14:24:40 Vostok NetworkManager[1354]: [1516829080.5343] > manager:

Re: Suspend to Ram Issues

Aaand this crap just happened again. Suspended for less than 4 hours and the damned thing shutdown at some point. Here's the related journalctl entries.. Jan 24 14:24:40 Vostok NetworkManager[1354]: [1516829080.5343] manager: sleep requested (sleeping: no enabled: yes) Jan 24 14:24:40 Vostok

Re: Suspend to Ram Issues

On Wed, 24 Jan 2018 22:22:59 +0100 Wolfgang Pfeiffer wrote: > Even better: reboot with X disabled (no idea how to do it) appending this to a kernel boot line should work: systemd.unit=multi-user.target https://docs-old.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/s1-grub-targets.ht

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 2:22 PM, Wolfgang Pfeiffer wrote: > On Wed, 24 Jan 2018 08:40:55 -0700 > InvalidPath wrote: > > > On Wed, Jan 24, 2018 at 7:59 AM, InvalidPath > > wrote: > > > > > > > > > > > So last night I suspended using 'sudo systemctl suspend' At around > > 8pm. This morning when I

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 1:52 PM, Ed Greshko wrote: > On 01/25/18 04:39, InvalidPath wrote: > > > > $sudo systemctl status systemd-suspend.service > > [sudo] password for bhart: > > ● systemd-suspend.service - Suspend > > Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; > static;

Re: Suspend to Ram Issues

On Wed, 24 Jan 2018 08:40:55 -0700 InvalidPath wrote: > On Wed, Jan 24, 2018 at 7:59 AM, InvalidPath > wrote: > > > > > > So last night I suspended using 'sudo systemctl suspend' At around > 8pm. This morning when I opened the lid I was greeted with a black > screen but responsive keyboard l

Re: Suspend to Ram Issues

On 01/25/18 04:39, InvalidPath wrote: > > $sudo systemctl status systemd-suspend.service > [sudo] password for bhart:   > ● systemd-suspend.service - Suspend >   Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; static; > vendor > preset: disabled) >   Active: inactive (dead) >

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 12:20 PM, Ed Greshko wrote: > On 01/25/18 03:02, InvalidPath wrote: > > > > On Wed, Jan 24, 2018 at 9:48 AM, InvalidPath > > wrote: > > > > > > > > On Wed, Jan 24, 2018 at 9:26 AM, Patrick O'Callaghan < > pocallag...@gmail.com > >

Re: Suspend to Ram Issues

On 01/25/18 03:02, InvalidPath wrote: > > On Wed, Jan 24, 2018 at 9:48 AM, InvalidPath > wrote: > > > > On Wed, Jan 24, 2018 at 9:26 AM, Patrick O'Callaghan > > wrote: > > On Wed, 2018-01-24 at 17:00 +0100, Frank Elsner

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 9:48 AM, InvalidPath wrote: > > > On Wed, Jan 24, 2018 at 9:26 AM, Patrick O'Callaghan < > pocallag...@gmail.com> wrote: > >> On Wed, 2018-01-24 at 17:00 +0100, Frank Elsner wrote: >> > > So last night I suspended using 'sudo systemctl suspend' At around >> 8pm. >> > >> >

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 9:26 AM, Patrick O'Callaghan wrote: > On Wed, 2018-01-24 at 17:00 +0100, Frank Elsner wrote: > > > So last night I suspended using 'sudo systemctl suspend' At around 8pm. > > > > What's the diffenrece between "sudo systemctl suspend" and "pm-suspend" > > which I also tried

Re: Suspend to Ram Issues

On Wed, 24 Jan 2018 16:26:55 + Patrick O'Callaghan wrote: > On Wed, 2018-01-24 at 17:00 +0100, Frank Elsner wrote: > > > So last night I suspended using 'sudo systemctl suspend' At around 8pm. > > > > What's the diffenrece between "sudo systemctl suspend" and "pm-suspend" > > which I also trie

Re: Suspend to Ram Issues

On Wed, 2018-01-24 at 17:00 +0100, Frank Elsner wrote: > > So last night I suspended using 'sudo systemctl suspend' At around 8pm. > > What's the diffenrece between "sudo systemctl suspend" and "pm-suspend" > which I also tried without success. AFAIK pm-utils, which includes pm-suspend, is deprec

Re: Suspend to Ram Issues

On Wed, 24 Jan 2018 08:40:55 -0700 InvalidPath wrote: [ ... ] > So last night I suspended using 'sudo systemctl suspend' At around 8pm. What's the diffenrece between "sudo systemctl suspend" and "pm-suspend" which I also tried without success. > This morning when I opened the lid I was greet

Re: Suspend to Ram Issues

On Wed, Jan 24, 2018 at 7:59 AM, InvalidPath wrote: > > > On Jan 24, 2018 6:53 AM, "Frank Elsner" > wrote: > > On Wed, 24 Jan 2018 14:42:09 +0100 Erik P. Olsen wrote: > > On 2018-01-24 at 14:29:49 Frank Elsner wrote: > > > > > On Tue, 23 Jan 2018 19:47:48 -0700 InvalidPath wrote: > > > > Fully u

Re: Suspend to Ram Issues

On Jan 24, 2018 6:53 AM, "Frank Elsner" wrote: On Wed, 24 Jan 2018 14:42:09 +0100 Erik P. Olsen wrote: > On 2018-01-24 at 14:29:49 Frank Elsner wrote: > > > On Tue, 23 Jan 2018 19:47:48 -0700 InvalidPath wrote: > > > Fully updated F27, Dell XPS 15 9550. > > > > Fully updated F27, Lenovo C200 > >

Re: Suspend to Ram Issues

On Wed, 24 Jan 2018 14:42:09 +0100 Erik P. Olsen wrote: > On 2018-01-24 at 14:29:49 Frank Elsner wrote: > > > On Tue, 23 Jan 2018 19:47:48 -0700 InvalidPath wrote: > > > Fully updated F27, Dell XPS 15 9550. > > > > Fully updated F27, Lenovo C200 > > > > > So last year on F26 I could safely an

Re: Suspend to Ram Issues

On 2018-01-24 at 14:29:49 Frank Elsner wrote: > On Tue, 23 Jan 2018 19:47:48 -0700 InvalidPath wrote: > > Fully updated F27, Dell XPS 15 9550. > > Fully updated F27, Lenovo C200 > > > So last year on F26 I could safely and reliably suspend to ram from the > > menu, then after the upgrade to F

Re: Suspend to Ram Issues

On Tue, 23 Jan 2018 19:47:48 -0700 InvalidPath wrote: > Fully updated F27, Dell XPS 15 9550. Fully updated F27, Lenovo C200 > So last year on F26 I could safely and reliably suspend to ram from the > menu, then after the upgrade to F27 all that stopped. I just dealt with it > until last night.

Re: Suspend to Ram Issues

Allegedly, on or about 24 January 2018, Ed Greshko sent: > I have a friend that experienced what I think your seeing. Her > laptop would go into suspension (her's also had a visual indicator) > but later she found it would at times be rebooting on opening the > lid. In her case it turned out to b

Re: Suspend to Ram Issues

On Tue, Jan 23, 2018 at 8:55 PM, Ed Greshko wrote: > On 01/24/18 10:47, InvalidPath wrote: > > Fully updated F27, Dell XPS 15 9550. > > > > So last year on F26 I could safely and reliably suspend to ram from the > menu, then > > after the upgrade to F27 all that stopped. I just dealt with it unti

Re: Suspend to Ram Issues

On 01/24/18 10:47, InvalidPath wrote: > Fully updated F27, Dell XPS 15 9550. > > So last year on F26 I could safely and reliably suspend to ram from the menu, > then > after the upgrade to F27 all that stopped. I just dealt with it until last > night. > So Google let em down again with the VAST m

Re: Suspend to Ram Issues

On 01/24/18 10:47, InvalidPath wrote: > Fully updated F27, Dell XPS 15 9550. > > So last year on F26 I could safely and reliably suspend to ram from the menu, > then > after the upgrade to F27 all that stopped. I just dealt with it until last > night. > So Google let em down again with the VAST m

Suspend to Ram Issues

Fully updated F27, Dell XPS 15 9550. So last year on F26 I could safely and reliably suspend to ram from the menu, then after the upgrade to F27 all that stopped. I just dealt with it until last night. So Google let em down again with the VAST majority.. if not damned near all of the results cente