Startseite » Forum » Trisquel users
Verfasst von libre1412 am Mo, 11/09/2015 - 18:43

Laptop shuts down after waking up from suspend

9 Antworten [Letzter Beitrag]
Mo, 11/09/2015 - 18:43
libre1412
libre1412
Offline
Beigetreten: 10/15/2015

Hello,

I currently have a Libreboot T400 running Trisquel 7.0 Belenos, with the GNOME desktop environment. Starting just yesterday, I noticed that whenever I suspend my system, the laptop restarts after I try to wake it up. I've made sure that all of my packages are updated, and it wasn't doing that before, so I'm not sure why it started doing all of this so recently. Thank you guys for your help!

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Mo, 11/09/2015 - 20:43
#1
lembas
lembas
Offline
Beigetreten: 05/13/2010

Hi there! This is just a hunch (reminds me of something I experienced) but what is your output ofgsettings get org.gnome.settings-daemon.plugins.power use-time-for-policy

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Mo, 11/09/2015 - 21:05
#2
libre1412
libre1412
Offline
Beigetreten: 10/15/2015

*******@user1:~$ gsettings get org.gnome.settings-daemon.plugins.power use-time-for-policy
true
*******@user1:~$

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Mo, 11/09/2015 - 21:11
#3
lembas
lembas
Offline
Beigetreten: 05/13/2010

Ok, let's try toggling that.gsettings set org.gnome.settings-daemon.plugins.power use-time-for-policy false

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Mo, 11/09/2015 - 21:35
#4
libre1412
libre1412
Offline
Beigetreten: 10/15/2015

I did that, and after I hit space bar it briefly came back on, then it just shut off.

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Mo, 11/09/2015 - 22:20
#5
lembas
lembas
Offline
Beigetreten: 05/13/2010

Oh well... I guess you could check out which packages got updated lately in /var/log/dpkg.log

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Mo, 11/09/2015 - 22:40
#6
libre1412
libre1412
Offline
Beigetreten: 10/15/2015

What exactly am I supposed to be looking for in those logs?

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Di, 11/10/2015 - 06:51
#7
lembas
lembas
Offline
Beigetreten: 05/13/2010

The names of the packages installed between when it worked and when it didn't.

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Mi, 11/11/2015 - 00:26
#8
Magic Banana
Magic Banana

I am a member!

I am a translator!

Offline
Beigetreten: 07/24/2010

And if the kernel was updated, then it is worth booting the previous kernel to see if the problem still occurs. To boot the previous kernel, GRUB's password (in /etc/grub.d/01_PASSWORD) must be known or removed.

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines
Di, 11/10/2015 - 14:44
#9
SuperTramp83
SuperTramp83

I am a translator!

Offline
Beigetreten: 10/31/2014

Hmm, I briefly researched this and it appears to be mostly related to nvidia GPUs. That is not your case though as you have an integrated Intel one. I would try to contact the libreboot guys.

Also, first of all try upgrading to the latest jxself's kernel -> https://jxself.org/linux-libre/

Oben
  • +1
    0
    -1
    Please use the rating system to mark posts that go against the Community Guidelines