Package Details: ring-kde 2.3.0.r424.gb1992bb-1

Git Clone URL: https://aur.archlinux.org/ring-kde.git (read-only)
Package Base: ring-kde
Description: KDE client for Ring (ring.cx)
Upstream URL: https://commits.kde.org/ring-kde
Licenses: GPL3
Groups: ring
Submitter: ArchangeGabriel
Maintainer: ArchangeGabriel
Last Packager: ArchangeGabriel
Votes: 18
Popularity: 1.262024
First Submitted: 2016-03-31 16:59
Last Updated: 2017-06-30 15:02

Latest Comments

Elv13 commented on 2017-08-22 18:07

3.0.0-alpha1 is out

https://www.youtube.com/watch?v=AYba9uepFzs

Please report *all* bugs to https://bugs.kde.org . I would really, really appreciate in depth testing before 3.0.0.

If you use Ring-KDE as a phone, use `--phone` on the command line to get the old GUI.

Another Arch user reported instabilities (https://bugs.kde.org/show_bug.cgi?id=383655) from an unknown source. I would also like to know if it's generalized or specific to him/her. I can't reproduce the issue on my system or my other test systems.

ArchangeGabriel commented on 2017-06-30 13:21

OK, QtQuickControls wasn’t a dependency before, and it was not detected as a runtime deps by Arch packaging tools. I’ll add it and keep you updated on freenode (#ring).

Elv13 commented on 2017-06-30 12:50

(I am on IRC, #ring, #kde-devel or #archlinux @freenode)

Elv13 commented on 2017-06-30 12:50


> qrc:/main.qml:19 module "QtQuick.Controls" version 2.0 is not installed

It doesn't find qt5-quickcontrols2, this is probably what prevented the wizard from starting. This is a packaging problem and none of the changes I did in the last 2 months could have effected this.

ArchangeGabriel commented on 2017-06-30 12:44

Hum… It doesn’t even start from the terminal now, here is the output:
History doesn't exist or is not readable
Loading vcf from: QDir( "/home/archange/.local/share/ring-kde/profiles" , nameFilters = { "*" }, QDir::SortFlags( Name | IgnoreCase ) , QDir::Filters( Dirs|Files|Drives|AllEntries ) )
Updating all accounts
Bookmarks doesn't exist or is not readable
QMetaType::registerTypedef: -- Type name 'Account*' previously registered as typedef of 'Account*' [1083], now registering as typedef of 'const Account*' [1085].
QQmlApplicationEngine failed to load component
qrc:/main.qml:19 module "QtQuick.Controls" version 2.0 is not installed

On previous attempts, there was even less output on the terminal.

Elv13 commented on 2017-06-30 12:35

> Starting from the terminal, then Settings → New account wizard does nothing.
> Did some more tests, clicking on New contact terminates the application.

Can you pastebin the terminal output. If it doesn't load, then a component is missing or a a fatal QML error happens and it will print an error. The same is true for the crash.

ArchangeGabriel commented on 2017-06-30 12:23

> For the accounts, they should be compatible as long as the Gnome client also see them. The very old accounts needs to be migrated to the new protocol. This can be done using the Gnome client. Given the current ring-kde is probably down to 3 digit users after the 18 months of brokeness and only 10% of them have the issue, I am not sure it's worth the week it would take to properly handle this. I think the answer for now is "use the Gnome client to press the migrate button, then the KDE client should work again".

OK, I now remember about this account migration thing. I’ll use the GNOME client to migrate then.

> Can you elaborate on that? Is there an error on the terminal? What happen if you starts it from the menu? I can at least confirm it seems reliable on 5 other distributions, including Gentoo (rolling) and Debian (old packages). Also, you can still create accounts from the setting page.

Lauching from the menu does not work (the StartupNotification happens, and then nothing, not sure if I can get some log of that somewhere).

Starting from the terminal, then Settings → New account wizard does nothing.

Did some more tests, clicking on New contact terminates the application.

I’ll try do to some more tests later, I’ll keep you updated.

Elv13 commented on 2017-06-29 22:58

> I’m pushing the new version anyway. :)

Lets consider this to be for early adopters ;). It's going to be a bit rough for a while. You can still start the old app using `ring-kde --phone`.

For the accounts, they should be compatible as long as the Gnome client also see them. The very old accounts needs to be migrated to the new protocol. This can be done using the Gnome client. Given the current ring-kde is probably down to 3 digit users after the 18 months of brokeness and only 10% of them have the issue, I am not sure it's worth the week it would take to properly handle this. I think the answer for now is "use the Gnome client to press the migrate button, then the KDE client should work again".

> the New account wizard doesn’t launch

Can you elaborate on that? Is there an error on the terminal? What happen if you starts it from the menu? I can at least confirm it seems reliable on 5 other distributions, including Gentoo (rolling) and Debian (old packages). Also, you can still create accounts from the setting page.

> I have an ugly UI that is not really working

Is it not working because of the account issue or something else? There is a known issue when the material QML theme is used where some widgets are invisible (upstream bug). Other than that, if you search a ring user from the left hand side search box then press call, it should work. If it doesn't I guess I will have install Arch to see why it doesn't. Can you try these steps to see if the features that works there also work for you?

https://www.youtube.com/watch?v=KJJmKov77HI&feature=youtu.be

ArchangeGabriel commented on 2017-06-28 22:40

So I did this.

But now launching from the menu does not work, though from the terminal it does work.

However, it does not seem to recognize my older account, and even after removing its file I have an ugly UI that is not really working (the New account wizard doesn’t launch). But I guess this is likely expected in the current state. ;)

I’m pushing the new version anyway. :)

ArchangeGabriel commented on 2017-06-28 22:26

And I agree with you on the use of static lib here. ;)

All comments