Not translated string

Bug #1600783 reported by Olivier Febwin on 2016-07-11
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Undecided
Unassigned
Ubuntu Translations
Medium
Ubuntu French Translators
deja-dup (Ubuntu)
Undecided
Unassigned
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in deja-dup (Ubuntu):
status: New → Confirmed
Changed in ubuntu-translations:
assignee: nobody → Ubuntu French Translators (ubuntu-l10n-fr)
importance: Undecided → Medium
status: New → Confirmed
Vej (vej) on 2016-12-23
Changed in deja-dup:
status: New → Confirmed
Anne017 (anneonyme017) wrote :

Deja-dup seems already 100% translated in French in the .po file, besides I have not found this particular string (although I have found a very similar string, "Another backup operation is already running", which is translated).

I though that is was an internationalization issue but have not found either any reference to "An operation is already pending" in the source code.

Olivier, could you tell us more about the Ubuntu and Deja-dup versions used when the snapshot has been taken?

Olivier Febwin (febcrash) wrote :

I had this issue on ubuntu 16.04 LTS

Naël (nathanael-naeri) wrote :

Could this be a message from duplicity instead?

Olivier Febwin (febcrash) wrote :

Same issue on my ubuntu 16.10 today

Anne017 (anneonyme017) wrote :

Olivier, could you tell us which Deja-dup version is it (search for example the deja-dup package in Synaptic)?
Also, could you verify if it is the stable release or a daily unstable release through PPA (https://launchpad.net/~deja-dup-team/+archive/testing)?

Olivier Febwin (febcrash) wrote :

version 34.2-0ubuntu

Naël (nathanael-naeri) wrote :

I can't find this message in Déjà-Dup's or duplicity's source code and .po files at the revisions corresponding to their versions in 16.10. No idea where it comes from.

Olivier, if you can identify and tell us how to trigger this error, this might give us a chance to find out where the message comes from.

Olivier Febwin (febcrash) wrote :

I have this issue when I plug my usb disk

Vej (vej) wrote :

This might be caused by this code (from ~deja-dup-hackers/deja-dup/34 : /libdeja/Network.vala lines 40 to 51 in revision 1580):

  public async bool can_reach(string url)
  {
    var mon = NetworkMonitor.get_default();
    try {
      var socket = NetworkAddress.parse_uri(url, 0);
      return yield mon.can_reach_async(socket);
    }
    catch (Error e) {
      warning("%s", e.message);
      return false;
    }
  }

Please see how the message from GLib.NetworkAddress or GLib.NetworkMonitor is passed to the user.
So lets try to find this string in the translation of GLib in vala.

Naël (nathanael-naeri) wrote :

@Olivier:

It's the disk you use as backup location I suppose? Does the error show up every time you plug it? Does it prevent automatic backups from happening or do they occur later? Does the error prevent you from running manual backups too? Does it also show up during manual backups?

@Vej:

Might be, but a network issue isn't very consistent with Olivier's report that the error occurs when he plugs in his USB disk.

There are several places in the code where a caught exception is printed out, grep warning("%s for a list. This one, in deja-dup/monitor/monitor.vala, is one of my top suspects (but I may be wrong):

static async void kickoff()
{
  [...]

  // Don't run right now if an instance is already running
  if (pid == (Pid)0 && !op_active) {
    try {
      debug("Running automatic backup.");
      [...]
      [calls to GLib.Process and GLib.ChildWatch functions]
      [...]
    }
    catch (Error e) {
      warning("%s\n", e.message);
    }
  }
  else
    debug("Not rerunning deja-dup, already doing so.");
}

Olivier Febwin (febcrash) wrote :

@nathanael-naeri : Yes it's my usb disk backup.
Yes this error show up everydays.
I must have to relaunch dejadup to begin backup.

Naël (nathanael-naeri) wrote :

Thanks for your feedback and the video. Never mind the untranslated string, this behavior is not normal at all. When I plug my external hard disk, backup starts and completes successfully.

I'm thinking we could add unique error IDs in the code to find out which particular error is triggered in your case. That would give us a lead to fix the translation and also hopefully the issue itself.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers