You are not logged in.
Pages: 1
Hi,
I've just laid my hands on the new Dell XPS 13, I've installed Arch + i3 on it.
The problem is that when I try to suspend it does suspend but when I resume it and go back to i3 it looks something like this:
screenshot
I tried disabling LightDM and boot to tty, inside tty I suspended the system and resumed it and the tty was fine and I could keep working with it,
but if I start i3 via startx (after booting to tty -> suspending -> resuming -> startx) i3 is unusable from the beginning.
How can I debug this?
Offline
Well that's a very new notebook and last I heard Dell is still working on Linux support for it. What does the journal say? Have you tried xf86-video-intel-git from AUR?
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Other people I've asked (IRC) that have the same setup (xps 2015 + arch + i3) say that suspend works for them.
I didn't try intel-git, I'll check it out.
About the journal I will look to see if there is something odd there.
Offline
UPDATE:
When I change the acceleration method to 'uxa' instead of 'sna' suspending seems to work.
Offline
Hi,
I'm dealing with the same issue trying to run i3 on a 2015 XPS-13 on Ubuntu (so it's clearly not an Arch-specific problem), and like you, I can get it to work if I switch to UXA. Obviously I'd prefer SNA, so I'm trying to figure out what's going wrong.
What I've found so far is that the bug affects i3, fluxbox and openbox, but *not* Unity or GNOME. I can't seem to find any obviously interesting differences in the journal when suspending/resuming with the different desktops / WMs I've tried it with.
I thought that perhaps the difference was that Unity and GNOME use compositors, but having compton running with i3/flux/openbox changes nothing.
Offline
Pages: 1