The specified configuration cannot be used

[maeckha]

Bug description

Dont know if its a bug but when I am trying to translate text I get the following: "The specified configuration cannot be used."
Tried tweaking the settings, no results. Using Plasma on Manjaro Linux.

Steps to reproduce

1. Paste text from the clipboard into Crow Translate window.
2. Try to translate.
3. See error.

These are my settings:

Environment

Operating System: Manjaro Linux
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Kernel Version: 5.15.1-1-MANJARO (64-bit)
Graphics Platform: X11

Version: 2.9.1

[Shatur]

Can't reproduce the issue with your settings, main menu setup and the same text.

[maeckha]

I discovered that when I click on the "play" button on bottom left, I get the following:

The window says "unable to detect language".

[Shatur]

Still can't reproduce. Does this only happen with Google engine?

[maeckha]

No, still errors but other ones.

[Shatur]

No, still errors but other ones.

This engine doesn't not support TTS (should be obvious). And I meant translation.

[maeckha]

Translation does not work with any engine.

[Shatur]

That's interesting. Could you send me your configuration file? Located at ~/.config/Crow Translate/Crow Translate.conf.

[maeckha]

Sent it to your mail.

[Shatur]

Works for me with your configuration. Something wrong with your system then.

[Shatur]

The error message "The specified configuration cannot be used." is not from Crow Translate.

[Shatur]

Looks like a Qt issue: https://bugreports.qt.io/browse/QTBUG-46542

[maeckha]

Okay. Thanks for looking into it anyway.

[jeetsrs]

Same issue for me - Gnome 41, Manjaro

[VolkMilit]

@jeetsrs, what Qt version do you have (you can check it with: pacman -Qi qt5-base)? For example my Qt version is 5.15.2+kde+r254-1 and everything works on my Artix Linux (Arch Linux) setup.

This specific issue only affects very old Qt versions (5.3.1, 5.4.0 Beta) according to Qt bugreports.

[jeetsrs]

Name : qt5-base
Version : 5.15.2+kde+r256-1

[maeckha]

Got the exact same version as @jeetsrs .

[Gray47Maxx]

Looks like I've found a way to reproduce it:

1. Start Crow Translate.
2. Hibernate your PC / laptop.
3. Get your system from the hibernation.
4. Try to translate any text.

At least that's how I've reproduced that. Manjaro KDE, Qt 5.15.4+kde+r164-1, Dell G5 15 5587.

[VolkMilit]

@Gray47Maxx
Hibernation, hmm. NetworkManager can be an issue, in this case. Does your internet connection works fine after hibernation? Also, D-Bus (concretely it's demon) can be an issue.
As upstream Qt issue points out:

I see the same error when roaming between different access points in the same network (i.e. different BSSID, same SSID). See the original bug on how to reproduce.

Try restart networkmanager and dbus wia systemctl and check if issue still persists.

[Gray47Maxx]

@VolkMilit

Does your internet connection works fine after hibernation?

In most cases - yes. Sometimes it and audio fails to start, haven't researched why that happens yet.

Try restart networkmanager and dbus wia systemctl and check if issue still persists.

Yep, it works fine after restarting both services. Tried hibernating a few times now — seems to work as it should after awakening.

[VolkMilit]

In most cases - yes. Sometimes it and audio fails to start, haven't researched why that happens yet.
Yep, it works fine after restarting both services. Tried hibernating a few times now — seems to work as it should after awakening.

Seems like bug in systemd for me, then. Not a Qt or Crow-specific bug. Most likely, D-Bus or NetworkManager (it rely on D-Bus) problem.

[korongmambu]

Hibernation, hmm.

@VolkMilit I also reproduce this issue after sleep, workaround for me just restart crow-translate

[andruska]

Same problem here - "The specified configuration cannot be used". Yes, I'm using hibernation too. All other services and programs in the same computer i.e. bluetooth, audio, network, Qt and GTK programs works without any problems after resuming from hibernation. Except Crow Translate.

Archlinux 32-bit, Xfce

[ealeksejev]

For workaround, just remove bearer folder in a plugin:

$ lsb_release -r
Release:        22.04
$ sudo mv /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer/ /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer.mv

[korongmambu]

@ealeksejev It's a great way to break your qt5, thanks!

[ealeksejev]

@ealeksejev It's a great way to break your qt5, thanks!

It doesn't break anything. Bearer management has been removed in Qt 6.

[ValdikSS]

Same issue with Fedora 37, Qt5 5.15.9.

This is probably also the same issue as I reported in QuiteRSS back in 2022 and another person reported in QuteBrowser

QuiteRSS/quiterss#1517
qutebrowser/qutebrowser#129

[ValdikSS]

Nextcloud resets QNetworkAccessManager in case of issues.

https://github.com/nextcloud/desktop/blob/12177878e25a6e8ae350a117880be769d3b3db5/src/gui/accountstate.cpp#L298-L320

https://github.com/nextcloud/desktop/blob/12177878e25a6e8ae350a117880be769d3b3db5e/src/libsync/account.cpp#L363-L384

See nextcloud/desktop#4331

[ValdikSS]

Took some time to debug the issue.
https://bugreports.qt.io/browse/QTBUG-114666

Simpliest workaround: start the affected applications without the network, connect to the network later.