Summary: | xfce-base/xfce4-session Xfce screen does not lock | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | jorge <jorge.ramos> |
Component: | Current packages | Assignee: | XFCE Team <xfce> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | burcheri.massimo+bugs-gentoo, jstein, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
jorge
2020-04-29 12:50:17 UTC
What I found out, to the best of my abilities, I hope it helps: After some more testing, the error message only appears after the laptop is unlocked and when the unlocked state came from closing the lid. If the screen locks via the manual running of xflock4 or by "locking the screen" in the panel (as described before), the error message does not appear after the laptop gets unlocked. A curious behavior: the error message is not displayed immediately afterwards the unlocking, rather like 10 seconds after. From what I've investigated, the error comes from the program built from the file xfpm-manager.c a source file from the power manager app. The offending lines are (453-458): if (!xfce_screensaver_lock (manager->priv->screensaver)) { xfce_dialog_show_error (NULL, NULL, _("None of the screen lock tools ran " "successfully, the screen will not " "be locked.")); } as you can see, this is executed only if the xfce_screensaver_lock method returns FALSE. This method is found on the source file xfce-screensaver.c (also of the power manager app). The important lines (501-525): switch (saver->priv->screensaver_type) { case SCREENSAVER_TYPE_FREEDESKTOP: case SCREENSAVER_TYPE_MATE: case SCREENSAVER_TYPE_GNOME: case SCREENSAVER_TYPE_XFCE: { GVariant *response = NULL; response = g_dbus_proxy_call_sync (saver->priv->proxy, "Lock", g_variant_new ("()"), G_DBUS_CALL_FLAGS_NONE, -1, NULL, NULL); if (response != NULL) { g_variant_unref (response); return TRUE; } else { return FALSE; } break; } in my case I'm using the default xfce4-screensaver, so the case statement must have landed there. If this method is returning FALSE, it means that the response was NULL. This means that the call g_dbus_proxy_call_sync somehow always return NULL in my system. An odd thing is that the variable saver->priv->proxy is not declared in this method, so maybe the problem lies around there. Well that's the best of my current abilities. Hope it helps. Could you report your findings upstream (https://bugzilla.xfce.org)? Alternatively, I could proxy it for you but I think it'd be easier if you talked ot them directly ;-). Hi, I always get this message... https://github.com/xfce-mirror/xfce4-power-manager/blob/xfce4-power-manager-1.7.0/src/xfce-screensaver.c#L499 ...when going into Suspend-to-ram via the physical power button of my machine. Eventhough the messages says it is not locked, the xscreensaver lock screen is locking as usual when resuming from sleep. The message is just annoying when going to sleep. This ticket is about the same issue? Is there any news? Upstream bug says it's closed with some updates. But as for xfce4-screensaver, I'm not using this but xscreensaver: x11-misc/xscreensaver-6.02-r1 xfce-extra/xfce4-screensaver is not installed xfce-extra/xfce4-power-manager-4.16.0 |