Public bug reported:

Invoking `sudo system-config-samba` does nothing, except printing

    $ sudo system-config-samba
    (system-config-samba:27398): IBUS-WARNING **: The owner of 
/home/richter/.config/ibus/bus is not root!
    Traceback (most recent call last):
      File "/usr/sbin/system-config-samba", line 45, in <module>
        mainWindow.MainWindow(debug_flag)
      File "/usr/share/system-config-samba/mainWindow.py", line 121, in __init__
        self.basic_preferences_win = 
basicPreferencesWin.BasicPreferencesWin(self, self.xml, self.samba_data, 
self.samba_backend, self.main_window)
      File "/usr/share/system-config-samba/basicPreferencesWin.py", line 97, in 
__init__
        self.admin = libuser.admin()
    SystemError: could not open configuration file `/etc/libuser.conf': Datei 
oder Verzeichnis nicht gefunden

which makes it impossible to use the program.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: system-config-samba 1.2.63-0ubuntu6
Uname: Linux 4.1.4-040104-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 29 18:30:32 2015
InstallationDate: Installed on 2015-06-08 (82 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: system-config-samba
UpgradeStatus: Upgraded to vivid on 2015-06-09 (81 days ago)

** Affects: system-config-samba (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490216

Title:
  system-config-samba fails with "SystemError: could not open
  configuration file `/etc/libuser.conf': No such file or directory" at
  start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-samba/+bug/1490216/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to