https://bugzilla.redhat.com/show_bug.cgi?id=984333
--- Comment #25 from Wolfgang Ulbrich <chat-to-me(a)raveit.de> ---
(In reply to Wolfgang Ulbrich from comment #23)
> Can confirm that uninstalling fprintd helps?
error......can you confirm please uninstalling fprintd helps?
Or using authcofig-gtk to disable it?
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=pyM8ZrObT5&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=984333
Wolfgang Ulbrich <chat-to-me(a)raveit.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(dgibson(a)redhat.co
| |m)
--- Comment #23 from Wolfgang Ulbrich <chat-to-me(a)raveit.de> ---
(In reply to David Gibson from comment #22)
> Ok, as noted above, I'm still seeing the problem with f22.
>
For some reasons xmonad-mate didn't start in my f22 VM.
> Another thought occurred to me: I also have workrave installed. I don't
> know if it is relevant, but it's possible. Often mate-screensaver activates
> when I am taking a workrave enforced rest break. I'm pretty sure I've had
> this problem occur other times as well, but I'm not certain.
After installing xmonad-mate on my notebook MSI FX600 with intel graphic i
could reproduce the issue after a long day of testing.
Late in evenning i couldn't unlock the session anymore.
Running 'journlctl -b 0 -f --no-tail' shows me that the fprintd.service was
running.
This is complete weird/bad because my notebook doesn't have a
fingerprint-reader.
After stoping the service i could unlock the session :)
fprintd.service is a static service wich will call by another service if
needed, so i tried to mask the service.
But today i run in the issue again, so masking the service isn't enough.
Dbus tried to load the mask service, which failed of course.
But the lookscreen was unselectable again.
Reason enough to uninstall unneeded fprintd.
Now the lookscreen works until yet.
So the question is why is fprintd.service running on a system w/o a hardware
for it, and which other service or appliction call it?
Looks for me more like a fprintd or maybe a systemd issue.
Can confirm that uninstalling fprintd helps?
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=wkSpT73pns&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=984333
David Gibson <dgibson(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(dgibson(a)redhat.co |
|m) |
--- Comment #22 from David Gibson <dgibson(a)redhat.com> ---
> Installing xmonad isn't user friendly.
> Why are the 2 needed yum/dnf groups in comps unvisible?
I can't answer that.
> Anyways, it runs in a f21 VM now.
Ok, as noted above, I'm still seeing the problem with f22.
> But i couldn't reproduce the issue until yet.
> So, some more questions:
> Does it only happens if the session is looked?
Sorry, I don't understand that question.
> Do i need to wait longer, ie 2 hours or 6 hours, before i try to unlock the session?
No, I've rarely left the session locked that long, and I've frequently hit the
problem when it has only been locked for seconds.
> Does it happens when the box boot from hibernate/suspend state?
When I resume from suspend-to-ram, I think the problem has sometimes happened,
but certainly not more frequently than any other time.
I'm not regularly using hibernate at the moment, so I don't know about that.
> I tested it also on bare metal several times, no luck.
> Which graphic are you using?
I'm using Intel Graphics on a Thinkpad T520.
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
I also encountered the problem on my previous laptop, which was a Thinkpad
X230, also with Intel graphics.
> I tested it with nvidia driver from rpmfusion.
I don't have any nvidia machines I could cross test with.
Another thought occurred to me: I also have workrave installed. I don't know
if it is relevant, but it's possible. Often mate-screensaver activates when I
am taking a workrave enforced rest break. I'm pretty sure I've had this
problem occur other times as well, but I'm not certain.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=uueeEBzhmU&a=cc_unsubscribe
https://bugzilla.redhat.com/show_bug.cgi?id=984333
Wolfgang Ulbrich <chat-to-me(a)raveit.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(dgibson(a)redhat.co
| |m)
--- Comment #21 from Wolfgang Ulbrich <chat-to-me(a)raveit.de> ---
Installing xmonad isn't user friendly.
Why are the 2 needed yum/dnf groups in comps unvisible?
Anyways, it runs in a f21 VM now.
But i couldn't reproduce the issue until yet.
So, some more questions:
Does it only happens if the session is looked?
Do i need to wait longer, ie 2 hours or 6 hours, before i try to unlock the
session?
Does it happens when the box boot from hibernate/suspend state?
I tested it also on bare metal several times, no luck.
Which graphic are you using?
I tested it with nvidia driver from rpmfusion.
But sorry, i can't use xmonad on my main box whole the day for testing more ;)
But it seems you're not alone, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785739
PS: you can try out latest mate-screensaver build which have improvements for
systemd-login.
https://bodhi.fedoraproject.org/updates/FEDORA-2015-5b345be5b9
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=4JtevhBwJw&a=cc_unsubscribe