Page MenuHomeSolus

Macbook Pro 8,3 not suspending when lid is closed.
Closed, ResolvedPublic

Description

When I close the lid of my MacBook Pro 8,3 at first the backlight of the screen goes off, maybe for about 3 or 4 seconds, then comes back on. Noticing this I open the screen and everything has crashed presenting me with lightdm to resign in. Oddly enough, selecting suspend from the power applet sometimes works but sometimes still crashes after I close the lid.

If it helps screen brightness also does not work and this laptop has a hybrid Intel / ATI graphics card :{. I assume there are a lot of mac switchers right now with their latest hardware and it would be truly great to get this all working out of the box. I want to say thank you for the amazing distro, even with these very frustrating problems, I feel as if this is the best distro I have ever used, and have signed up for the $25 a month patreon, I just wish I had the ability to do more.

Laptop: MacBook Pro 17
Model: 8,3
Graphis: Intel / ATI AMD Radeon HD 6600M Series ( both are running )
Kernal: 4.8.15
Applied all the updates in software center.

yeti@yeti ~ $ dmesg | grep -i lid
[ 7.023766] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
[ 7.023785] ACPI: Lid Switch [LID0]
[ 7.261899] radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x0000
[ 7.262041] radeon 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x0000

After it crashes this is the journalctl.

yeti@yeti ~ $ journalctl -f

  • Logs begin at Sun 2017-01-08 15:40:47 EST. --

Jan 16 15:43:58 yeti budgie-wm.desktop[2677]: (budgie-wm:2677): GLib-GObject-CRITICAL : g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Jan 16 15:43:59 yeti gnome-settings-daemon.desktop[2662]: (gnome-settings-daemon:2662): color-plugin-WARNING
: failed to get edid: unable to get EDID for output
Jan 16 15:43:59 yeti gnome-settings-daemon.desktop[2662]: (gnome-settings-daemon:2662): color-plugin-WARNING : unable to get EDID for xrandr-LVDS1: unable to get EDID for output
Jan 16 15:44:00 yeti tracker-store.desktop[2737]: (uint32 1,)
Jan 16 15:44:00 yeti gnome-session-binary[2610]: Entering running state
Jan 16 15:44:00 yeti org.gnome.OnlineAccounts[2623]: goa-daemon-Message: goa-daemon version 3.20.4 starting
Jan 16 15:44:00 yeti org.gtk.vfs.AfcVolumeMonitor[2623]: Volume monitor alive
Jan 16 15:44:02 yeti budgie-wm.desktop[2677]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1400007 (budgie-pan)
Jan 16 15:44:02 yeti budgie-wm.desktop[2677]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1400007 (budgie-pan)
Jan 16 15:44:02 yeti budgie-wm.desktop[2677]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1400007 (budgie-pan)
Jan 16 15:44:08 yeti org.gnome.Terminal[2623]: (gnome-terminal-server:2846): Gtk-WARNING
: Allocating size to GtkScrollbar 0xff61d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

I also ran this in a screen session so that I would keep going when it crashed as the lid closed. It registers the lid closing.

yeti@yeti ~ $ while true; do cat /proc/acpi/button/lid/LID0/state ; sleep 3; done
state: open
state: open
state: open
state: open
state: closed
state: closed
state: closed
state: closed
state: open
state: open
state: open
state: open

Event Timeline

tyler4 created this task.Jan 22 2017, 9:59 AM
tyler4 added a project: Hardware.
JoshStrobl moved this task from Backlog to Other on the Hardware board.Oct 26 2017, 2:43 AM
JoshStrobl added a subscriber: JoshStrobl.

Does this issue still persist under a fully upgraded Solus 3?

JoshStrobl closed this task as Resolved.Nov 19 2017, 1:11 AM
JoshStrobl claimed this task.

Closing due to lack of response.