What's a faulty module?
I don't use fingerprints.
**Unmatched Entries**
lightdm: PAM adding faulty module: /lib/security/pam_fprintd.so:
1 Time(s) lightdm: PAM unable to
dlopen(/lib/security/pam_fprintd.so): /lib/security/pam_fprintd.so:
cannot open shared object file: No such file or
Hi folks! We're running a FUDCon NA workshop session today to try and
actually knock out some QA 'low-hanging fruit', and the one we tried to
deal with this morning is the blocker tracker bug names. We had some
grand ideas for making this even better in the glorious future, which
involve more good
On 01/20/2013 06:49 PM, Adam Williamson wrote:
This is an issue that's come up repeatedly in the past and was also came
up during the talk Tim gave on the blocker process on Friday: the
feedback from everyone at the meeting (QA people and non-QA people) was
that the current names were really bad
On Sun, 2013-01-20 at 19:05 +, Jóhann B. Guðmundsson wrote:
On 01/20/2013 06:49 PM, Adam Williamson wrote:
This is an issue that's come up repeatedly in the past and was also came
up during the talk Tim gave on the blocker process on Friday: the
feedback from everyone at the meeting (QA
On Sun, 2013-01-20 at 13:27 -0600, Adam Williamson wrote:
and can you point me
to any talk where this has come up?
There've been multiple threads and meeting discussions, I don't have
references handy, but I thought you'd remember that too...
On Sun, Jan 20, 2013 at 12:49 PM, Adam Williamson awill...@redhat.com wrote:
Hi folks! We're running a FUDCon NA workshop session today to try and
actually knock out some QA 'low-hanging fruit', and the one we tried to
deal with this morning is the blocker tracker bug names. We had some
grand
On Sun 20 Jan 2013 05:37:57 AM PST, Lawrence Graves wrote:
Why is it that the new installation system will not load the current
kernel out? It always loads the 3.6.10-4 kernel.
--
All things are workable but don't all things work. Prov. 3:5 6
How did you install the system? DVD or network