Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

plug fails to detect current user on fedora #91

Closed
decathorpe opened this issue Oct 30, 2018 · 1 comment · Fixed by #98
Closed

plug fails to detect current user on fedora #91

decathorpe opened this issue Oct 30, 2018 · 1 comment · Fixed by #98
Milestone

Comments

@decathorpe
Copy link
Contributor

decathorpe commented Oct 30, 2018

The current user is displayed as (null), and nothing else seems to work right either (adding new accounts doesn't work, etc.).

screenshot

These are the log messages I get from switchboard when opening the User Accounts plug:

Failed to open configuration directory /etc/xdg/lightdm/lightdm.conf.d: Error opening directory ?/etc/xdg/lightdm/lightdm.conf.d?: No such file or directory
Failed to open configuration directory /home/deca/.local/share/flatpak/exports/share/lightdm/lightdm.conf.d: Error opening directory ?/home/deca/.local/share/flatpak/exports/share/lightdm/lightdm.conf.d?: No such file or directory
Failed to open configuration directory /var/lib/flatpak/exports/share/lightdm/lightdm.conf.d: Error opening directory ?/var/lib/flatpak/exports/share/lightdm/lightdm.conf.d?: No such file or directory
Failed to open configuration directory /usr/local/share/lightdm/lightdm.conf.d: Error opening directory ?/usr/local/share/lightdm/lightdm.conf.d?: No such file or directory
Failed to open configuration directory /etc/xdg/lightdm/lightdm.conf.d: Error opening directory ?/etc/xdg/lightdm/lightdm.conf.d?: No such file or directory
Failed to open configuration directory /home/deca/.local/share/flatpak/exports/share/lightdm/lightdm.conf.d: Error opening directory ?/home/deca/.local/share/flatpak/exports/share/lightdm/lightdm.conf.d?: No such file or directory
Failed to open configuration directory /var/lib/flatpak/exports/share/lightdm/lightdm.conf.d: Error opening directory ?/var/lib/flatpak/exports/share/lightdm/lightdm.conf.d?: No such file or directory
Failed to open configuration directory /usr/local/share/lightdm/lightdm.conf.d: Error opening directory ?/usr/local/share/lightdm/lightdm.conf.d?: No such file or directory
'[Seat:*] autologin-guest' is not set anywhere assuming default 'false'

** (io.elementary.switchboard:1657): WARNING **: 17:00:05.584: Utils.vala:31: Failed to open file “/etc/X11/default-display-manager”: No such file or directory

(io.elementary.switchboard:1657): GdkPixbuf-CRITICAL **: 17:00:05.585: gdk_pixbuf_new_from_file_at_scale: assertion 'filename != NULL' failed

(io.elementary.switchboard:1657): GLib-CRITICAL **: 17:00:05.585: g_markup_escape_text: assertion 'text != NULL' failed

(io.elementary.switchboard:1657): Gtk-CRITICAL **: 17:00:05.589: gtk_list_box_insert: assertion 'GTK_IS_WIDGET (child)' failed

** (io.elementary.switchboard:1657): WARNING **: 17:00:05.590: Utils.vala:78: Failed to open file “/usr/share/language-tools/main-countries”: No such file or directory

(io.elementary.switchboard:1657): GLib-CRITICAL **: 17:00:05.590: g_strsplit: assertion 'string != NULL' failed

** (io.elementary.switchboard:1657): CRITICAL **: 17:00:05.597: Utils.vala:61: Failed to execute child process “/usr/share/language-tools/language-options” (No such file or directory)
@Dirli
Copy link

Dirli commented Nov 3, 2018

Gentoo +
I solved this problem:
public static unowned Act.User? get_current_user () {
if (current_user != null)
return current_user;
foreach (unowned Act.User temp_user in get_usermanager ().list_users ()) {
if (temp_user.get_user_name() == GLib.Environment.get_user_name ()) {
current_user = temp_user;
break;
}
}
return current_user;
}
P.S. adding new user not tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

3 participants