Not possible to launch sbackup

Bug #1675965 reported by Lagoda on 2017-03-25

This bug report was converted into a question: question #590896: Not possible to launch sbackup.

This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

I have change place of logfile.
But after close sbackup i have delete my logfile folder.
After it is not psosible to launch sbackup (without re-create folder same as the start).
I send you this because it is write to send this information.

Traceback (most recent call last):
  File "/usr/bin/sbackup-config-gtk", line 45, in <module>
  File "/usr/share/sbackup/sbackup/ui/", line 2077, in main
    window = SBconfigGTK()
  File "/usr/share/sbackup/sbackup/ui/", line 90, in __init__
    self.configman = ConfigManager.ConfigManager(self.default_conffile)
  File "/usr/share/sbackup/sbackup/core/", line 248, in __init__
  File "/usr/share/sbackup/sbackup/core/", line 674, in __create_logger
    self.getint("log", "level"))
  File "/usr/share/sbackup/sbackup/util/", line 61, in getLogger
    return LogFactory.__createLogger(name, logfile, level)
  File "/usr/share/sbackup/sbackup/util/", line 97, in __createLogger
  File "/usr/lib/python2.7/", line 157, in makedirs
    mkdir(name, mode)
OSError: [Errno 13] Permission non accordée: '/var/log/sbackup'

Oumar Aziz OUATTARA (wattazoum) wrote :


You configured sbackup to write in a log directory in which you don't have the permission to write yourself. The previous log folder was writable to your user '/home/xxxxxxx/.local/share/sbackup/log/sbackup.log' .

To Fix the configuration

- Edit the file $HOME/.config/sbackup/sbackup.conf
- Change the log.file parameter back to a folder in which you can write.
- launch SBACKUP configuration gui

What you probably wanted to do

Launch sbackup in admin mode: gksudo sbackup-config-gtk

Then you have access to Scheduling option and have access rights to every directories.

Changed in sbackup:
assignee: nobody → Oumar Aziz OUATTARA (wattazoum)
Oumar Aziz OUATTARA (wattazoum) wrote :

This is due to a misconfiguration of the user.

Changed in sbackup:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions