Ubuntu
linux package

  1. Bug #1573231
  2. Comment #13

Comment 13 for bug 1573231

Revision history for this message
Rasmus Larsen (rla-2) wrote :

I get the same issue with the build, which seemed weird so I retested and it looks like I must have mislabeled one of my builds, because now when I build 31c2013e4ea2e594522980acc3d20e88664b19f1, I still get the issue, but if I go back to a6ebb4464659d35e0516900a8493f9720dd77d67 it works.
Somehow I must have swapped some builds...

a6ebb4464659d35e0516900a8493f9720dd77d67 Good
31c2013e4ea2e594522980acc3d20e88664b19f1 Bad
8ae10f463b7ae3455e9d0507176349c76580995f Bad

Really sorry about the detour Joseph.