Cannot back-up : "BackendException: Impossible d'initialiser le moteur : No module named repository"

Bug #1747982 reported by Joël Bourgault
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Undecided
Unassigned

Bug Description

# Description

Since update to xubuntu 17.10, I cannot make `deja-dup` to work, getting the error displayed in attachment.

I tried several solutions, including installing `python-gi`. Maybe it's not the correction version, however I cannot find anything else that would work.

# Computer configuration

Here are the output of the requested commands:

joel@babasse-jojo:~$ lsb_release -d
Description: Ubuntu 17.10
joel@babasse-jojo:~$ dpkg-query -W deja-dup duplicity
deja-dup 36.3-0ubuntu0.1
duplicity 0.7.12-1ubuntu1
joel@babasse-jojo:~$ gsettings list-recursively org.gnome.DejaDup
org.gnome.DejaDup last-restore '2016-01-02T17:11:32.732754Z'
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'drive'
org.gnome.DejaDup last-run '2017-11-10T19:57:29.435752Z'
org.gnome.DejaDup nag-check '2017-10-31T05:25:25.542589Z'
org.gnome.DejaDup prompt-check '2012-01-29T20:31:09.190326Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['/home/joel/Avatars', '/home/joel/Bureau', '/home/joel/créations', '/home/joel/Documents', '/home/joel/Dropbox', '/home/joel/Modèles']
org.gnome.DejaDup exclude-list ['/home/joel/créations/.metadata', '/home/joel/créations/eclipse/.metadata', '/home/joel/créations/android-sdk', '/home/joel/créations/AndroidStudioProjects', '/home/joel/Documents/programmation/.metadata', '/home/joel/Documents/z_archives']
org.gnome.DejaDup last-backup '2017-11-10T19:57:29.435752Z'
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'portable-joel'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'portable-joel'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'babasse-jojo'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'babasse-jojo'
org.gnome.DejaDup.Local folder 'babasse-jojo'
org.gnome.DejaDup.Remote uri ''
org.gnome.DejaDup.Remote folder 'babasse-jojo'
org.gnome.DejaDup.Drive uuid '63d178d6-8d15-4c02-af62-9f6f2590ba64'
org.gnome.DejaDup.Drive icon '. GThemedIcon drive-harddisk-usb drive-harddisk drive'
org.gnome.DejaDup.Drive folder 'deja-dup'
org.gnome.DejaDup.Drive name 'Joel - ext4'
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'babasse-jojo'
org.gnome.DejaDup.GOA type ''
org.gnome.DejaDup.File short-name 'Joel - ext4'
org.gnome.DejaDup.File type 'volume'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name 'SAMSUNG HM501II: Joel - ext4'
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File uuid '63d178d6-8d15-4c02-af62-9f6f2590ba64'
org.gnome.DejaDup.File icon '. GThemedIcon drive-harddisk-usb drive-harddisk drive'
org.gnome.DejaDup.File relpath b'deja-dup'

Revision history for this message
Joël Bourgault (joel-bourgault) wrote :
Revision history for this message
Michael Terry (mterry) wrote :

Your instinct to install python-gi seems correct. It should provide "gi.repository" which is what I assume the problem is from that error message.

I thought I had actually improved the dependency detection in 17.10 to help avoid problems like this. :(

I don't have an obvious recommendation for what to do to get around this right now. But I'll think about how to test what's wrong here.

Revision history for this message
Joël Bourgault (joel-bourgault) wrote : Re: [Bug 1747982] Re: Cannot back-up : "BackendException: Impossible d'initialiser le moteur : No module named repository"
Download full text (4.2 KiB)

Hello Mike,

Thanks for your feedback. I forgot to indicate that dejadup does not
provide anything about the bug in the command-line.

Any idea how I could investigate ? Running from python source code maybe ?

Best regards,
Joël

Le 11 févr. 2018 19:35, "Michael Terry" <email address hidden> a écrit :

> Your instinct to install python-gi seems correct. It should provide
> "gi.repository" which is what I assume the problem is from that error
> message.
>
> I thought I had actually improved the dependency detection in 17.10 to
> help avoid problems like this. :(
>
> I don't have an obvious recommendation for what to do to get around this
> right now. But I'll think about how to test what's wrong here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1747982
>
> Title:
> Cannot back-up : "BackendException: Impossible d'initialiser le moteur
> : No module named repository"
>
> Status in Déjà Dup:
> New
>
> Bug description:
> # Description
>
> Since update to xubuntu 17.10, I cannot make `deja-dup` to work,
> getting the error displayed in attachment.
>
> I tried several solutions, including installing `python-gi`. Maybe
> it's not the correction version, however I cannot find anything else
> that would work.
>
>
> # Computer configuration
>
> Here are the output of the requested commands:
>
> joel@babasse-jojo:~$ lsb_release -d
> Description: Ubuntu 17.10
> joel@babasse-jojo:~$ dpkg-query -W deja-dup duplicity
> deja-dup 36.3-0ubuntu0.1
> duplicity 0.7.12-1ubuntu1
> joel@babasse-jojo:~$ gsettings list-recursively org.gnome.DejaDup
> org.gnome.DejaDup last-restore '2016-01-02T17:11:32.732754Z'
> org.gnome.DejaDup periodic true
> org.gnome.DejaDup periodic-period 7
> org.gnome.DejaDup full-backup-period 90
> org.gnome.DejaDup backend 'drive'
> org.gnome.DejaDup last-run '2017-11-10T19:57:29.435752Z'
> org.gnome.DejaDup nag-check '2017-10-31T05:25:25.542589Z'
> org.gnome.DejaDup prompt-check '2012-01-29T20:31:09.190326Z'
> org.gnome.DejaDup root-prompt true
> org.gnome.DejaDup include-list ['/home/joel/Avatars',
> '/home/joel/Bureau', '/home/joel/créations', '/home/joel/Documents',
> '/home/joel/Dropbox', '/home/joel/Modèles']
> org.gnome.DejaDup exclude-list ['/home/joel/créations/.metadata',
> '/home/joel/créations/eclipse/.metadata', '/home/joel/créations/android-sdk',
> '/home/joel/créations/AndroidStudioProjects', '/home/joel/Documents/programmation/.metadata',
> '/home/joel/Documents/z_archives']
> org.gnome.DejaDup last-backup '2017-11-10T19:57:29.435752Z'
> org.gnome.DejaDup allow-metered false
> org.gnome.DejaDup delete-after 0
> org.gnome.DejaDup.Rackspace username ''
> org.gnome.DejaDup.Rackspace container 'portable-joel'
> org.gnome.DejaDup.S3 id ''
> org.gnome.DejaDup.S3 bucket ''
> org.gnome.DejaDup.S3 folder 'portable-joel'
> org.gnome.DejaDup.OpenStack authurl ''
> org.gnome.DejaDup.OpenStack tenant ''
> org.gnome.DejaDup.OpenStack username ''
> org.gnome.DejaDup.OpenStack container 'babasse-jojo'
> org.gnome.DejaDup.GCS id ''
> org.gnome.DejaDup.GCS bucket ''
> org...

Read more...

Revision history for this message
Michael Terry (mterry) wrote :

This was a packaging error that must be fixed in 19.10 at least. Certainly it is fixed in the snap version. Closing this ticket.

Changed in deja-dup:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.