Bug#765726: Peeling the Onion
vcheng at debian.org
Fri Oct 24 08:12:28 UTC 2014
On Sun, Oct 19, 2014 at 6:05 PM, Andreas Beckmann <anbe at debian.org> wrote:
> Control: tag -1 upstream
> On 2014-10-20 01:58, Martin Gallant wrote:
>> The reason it appeared I did not restart X after loading the updated
>> module is the Xorg.1.log was a stale console from an older unrelated
>> XDMCP client session.
>> I cannot get the system to create a new Xorg.*.log when X is invoked via gdm3.
>> I have no idea why that is - If I invoke X directly, the log file gets created.
> that's weird ...
That's expected as of gdm3 >= 3.12.x, because the X log is being
redirected to systemd-journald and accessible only via journalctl and
is root-only (by default); also see #765771. I'm not sure how to
handle systemd's journal logs through a reportbug script at this
More information about the pkg-nvidia-devel