On Thu, 16.04.15 05:43, Felix Miata (mrma...@earthlink.net) wrote: > I asked the following on freedesktop list a month ago and got no response. As > there was quite some time between this showing up in Fedora and Tumbleweed, > and Tumbleweed only lately upgraded systemd from 210 to 219, it looks like > systemd could be playing at least some part in this. > > I first noticed this last May on rv200 and filed a Redhat bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1096487 > > Later it happened with Nouveau NV11 and I updated that bug. > > Still later I noticed it happen on Cauldron on rv200: > https://ml.mageia.org/l/arc/dev/2014-09/msg00218.html > > By last month it was happening in Tumbleweed on NV11. > > So this doesn't look like any problem specific to the distros, but I don't > see any existing bug on bugs.freedesktop.org either. Could this be a problem > in something else, systemd or pam maybe? I've not seen this on Intel as old > as 845G? Would it actually be two bugs, one against Nouveau and another > against Radeon? Has no one else here encountered this?
I do no see how this is related to systemd in any way. Please ask the X11/drivers people for help, or even better your distro maintainers. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel