On Sun, Mar 15, 2015 at 19:03:41 +0100, Bernhard Übelacker wrote:
> Hello Philip,
> probably your case is more an example for the problem described in bugs
> #770130 and #776911.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770130
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
On Sun, 15 Mar 2015 at 19:48:07 +, Philip Hands wrote:
> I only posted to the bug because I saw no mention of the fact that one
> can get things working by avoiding gdm3 in any of these bugs, which
> seemed like it might be relevant. The fact that llvm-3.4 didn't help me
> is just an extra det
debian/changelog |6 ++
debian/control |4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
New commits:
commit 36e347779852ff821bb372d578ca02c09d2e5026
Author: Maarten Lankhorst
Date: Mon Mar 16 15:55:52 2015 +0100
Use conflicts/replaces on modesetting.
Irony,
Hi Simon,
Thanks for the detailed response.
Simon McVittie writes:
...
>> Hints about where gdm3 might be logging what happened would be useful.
>
> You seem to be running systemd as pid 1, so the catch-all answer is
> "in the journal" (available via either journalctl or the traditional
> syslo
4 matches
Mail list logo