On Mon, 28.04.14 21:34, Benjamin Podszun (d...@darklajid.de) wrote:
I merged Mantas' patch now, so I guess the thread can end, but...
> Frankly? No. I'm a fan of your work and I happily run systemd. But if you
> think that "Let's just make nvidia fix their drivers" is the right attitude,
> I thin
On Mon, Apr 28, 2014 at 6:10 PM, Lennart Poettering
wrote:
> On Mon, 28.04.14 00:44, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
>> With proprietary graphics drivers, there won't be any 'drm' devices in
>> sysfs, so logind will never suspend the system upon closing the lid,
>> even if only one (
Lennart Poettering poettering.net> writes:
>
> On Mon, 28.04.14 00:44, Mantas Mikulėnas (grawity gmail.com) wrote:
>
> > With proprietary graphics drivers, there won't be any 'drm' devices in
> > sysfs, so logind will never suspend the system upon closing the lid,
> > even if only one (interna
On Mon, 28.04.14 00:44, Mantas Mikulėnas (graw...@gmail.com) wrote:
> With proprietary graphics drivers, there won't be any 'drm' devices in
> sysfs, so logind will never suspend the system upon closing the lid,
> even if only one (internal) display is connected. This has been reported
> by multip
On Sun, Apr 27, 2014 at 11:44 PM, Mantas Mikulėnas wrote:
> With proprietary graphics drivers, there won't be any 'drm' devices in
> sysfs, so logind will never suspend the system upon closing the lid,
> even if only one (internal) display is connected. This has been reported
> by multiple users s
With proprietary graphics drivers, there won't be any 'drm' devices in
sysfs, so logind will never suspend the system upon closing the lid,
even if only one (internal) display is connected. This has been reported
by multiple users so far.
IMHO, it's better to suspend the system in this case for sa