Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Virtaal 0.7.1+git20191021+ds1-1/1.0.0-beta1 not working well in Linux Mint. #3323

Open
scootergrisen opened this issue Jan 24, 2021 · 5 comments

Comments

@scootergrisen
Copy link
Contributor

Not so good experience using Virtaal on Linux Mint 20.1.

With the application manager i search for Virtaal and it says version 0.7.1+git20191021+ds1-1.
After installation i run virtaal and it says version 1.0.0-beta1.
The Virtaal window is way to wide for the screen and i have a hard time making the window width smaller.
After editing some strings i see Virtaal changes some strings and does not remember all my changes.
I try to export but it does not create a mo file.

It would properly have been better to use the latest stable version instead of this beta version since it is not really working well.

@SaFi2266
Copy link

Exact same issue in ubuntu 20.04 with extra problems

  • 'Open' doesn't works neither in left interface nor in File menu
  • The Virtaal interface lists a 'recently po's files' that's I edited with Poedit app
  • When clicking on one of these files I get error says ImportError: cannot import name 'statsdb' from 'translate.storage' (/usr/local/lib/python3.8/dist-packages/translate/storage/__init__.py)
  • When run from terminal it generate some errors to load or find plugin like tm, gtkspell and migration

I was previously install translate-toolkit 3.3.0

@Burtan
Copy link

Burtan commented Jun 7, 2021

I'm getting the same error on debian bullseye.

@thierrybo
Copy link

same error Devuan unstable

@mikkorantalainen
Copy link

Broken with Ubuntu 22.04 LTS, too. Whoever packaged this for Debian/Ubuntu never bothered to try opening even a single .po file with it because it would have been obvious that the package is broken.

@llimeht
Copy link

llimeht commented Aug 31, 2023

Broken with Ubuntu 22.04 LTS, too. Whoever packaged this for Debian/Ubuntu never bothered to try opening even a single .po file with it because it would have been obvious that the package is broken.

Quite some assumptions you're making there @mikkorantalainen. Virtaal was in fact working fine when uploaded. I know, because I tested it. However, it was subsequently broken by incompatible pygtk changes that were not caught by the fairly limited test suite. That's why it's not in the current Debian release. You'd have to ask Ubuntu why they are still releasing it when Debian is not.

Oh, and when it comes to free software, patches are more welcome than uninformed ranting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants