When opening Okteta, it freezes for something like 30 seconds to a minute, then becomes usable. There is no info displayed on the console, I can't see what Okteta is doing. This bug happens at every startup of Okteta, should it get a file in its arguments or not. Reproducible: Always Steps to Reproduce: 1. Open Okteta 2. Wait for it to be ready 3. Start working Actual Results: Okteta froze as expected. Expected Results: Okteta should not have frozen upon its opening, or at least by giving some info in its status bar, or whatever. I have read there a bug that looks like similar: https://bugs.kde.org/show_bug.cgi?id=297214 . Yet, unlike this one (that is still unconfirmed), I do not have any output in the console from okteta, and the bug happens no matter which time zone I've chosen.
The version of Okteta I'm using is 0.15.2, with KDE Frameworks 5.6.0. This version is not yet listed.
Hi, In my case, if you press "Open" it stays in the dialogue, doing nothing and impossible to cancel it. All you can do is move it around, maximize, etc but no click or select a file or folder on it. Cancel and "X" button don’t work either. Your only escape is killing Okteta's process. Regards.
(In reply to Turbo from comment #2) > Hi, > > In my case, if you press "Open" it stays in the dialogue, doing nothing and > impossible to cancel it. All you can do is move it around, maximize, etc but > no click or select a file or folder on it. Cancel and "X" button don’t work > either. Your only escape is killing Okteta's process. > > Regards. I am experiencing the same bug since an update a month ago (I don't exactly remember when). Yet, I don't think these two bugs are linked: Okteta has always taken a long time to open on all of my computers since KDE 4, while the blocking "Open" dialog has only come up recently.
I'm also experiencing the frozen open dialog for Okteta. Here is what's in the konsole when I run it there: kasten.okteta.gui: Failed to open view profiles file "/home/lepore/.local/share/okteta/defaultviewprofile" kf5.kiconthemes: "Theme tree: (Oxygen)" codecForName: ucnv_open failed ISO-8859-16 U_FILE_ACCESS_ERROR kasten.okteta.controllers.checksum: ("random", "md5", "sha1", "keystorelist", "sasl", "pgpkey", "openpgp", "log", "sha0", "ripemd160", "md4", "sha224", "sha256", "sha384", "sha512", "hmac(md5)", "hmac(sha1)", "hmac(sha224)", "hmac(sha256)", "hmac(sha384)", "hmac(sha512)", "hmac(ripemd160)", "aes128-ecb", "aes128-cfb", "aes128-cbc", "aes128-cbc-pkcs7", "aes128-ofb", "aes128-ctr", "aes192-ecb", "aes192-cfb", "aes192-cbc", "aes192-cbc-pkcs7", "aes192-ofb", "aes192-ctr", "aes256-ecb", "aes256-cbc", "aes256-cbc-pkcs7", "aes256-cfb", "aes256-ofb", "aes256-ctr", "blowfish-ecb", "blowfish-cbc-pkcs7", "blowfish-cbc", "blowfish-cfb", "blowfish-ofb", "tripledes-ecb", "tripledes-cbc", "des-ecb", "des-ecb-pkcs7", "des-cbc", "des-cbc-pkcs7", "des-cfb", "des-ofb", "cast5-ecb", "cast5-cbc", "cast5-cbc-pkcs7", "cast5-cfb", "cast5-ofb", "pbkdf1(sha1)", "pbkdf2(sha1)", "pkey", "dlgroup", "rsa", "dsa", "dh", "cert", "csr", "crl", "certcollection", "pkcs12", "tls", "cms", "ca") kasten.okteta.controllers.structures: found structures: ("/usr/share/okteta/structures/elf/metadata.desktop", "/usr/share/okteta/structures/png/metadata.desktop") kasten.okteta.controllers.structures: found structures: ("/usr/share/okteta/structures/elf/metadata.desktop", "/usr/share/okteta/structures/png/metadata.desktop") kasten.okteta.controllers.structures: loadedStructs () kf5.kservice.sycoca: Trying to open ksycoca from "/home/lepore/.cache/ksycoca5" The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly. The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly. We got some errors while running 'net usershare info' "info_fn: file /var/lib/samba/usershares/chancery is not a well formed usershare file. info_fn: Error was Path is not a directory. info_fn: file /var/lib/samba/usershares/russellvets is not a well formed usershare file. info_fn: Error was Path is not a directory.
Hi, thanks for reporting this problem (and sorry for not having replied in all the time). I could see that problem as well on some machines, but never came around to dig into it. And on my current system there is no such issue. From the problem description it seems that the KF5 filedialog and filebrowser classes are blocked on some sync calls and that those return only after some timeout (or never). Not sure what is done wrong in Okteta code using those classes. To see debug output from KF5 classes, please start Okteta from the commandline with "QT_LOGGING_RULES="kf5.*=true okteta" Better would be to start it in the debugger and get a backtrace from the time when Okteta is blocked in the UI. But perhaps the respective bugs in KF5 classes got fixed meanwhile in newer releases? So do you still have these problems? https://bugs.kde.org/show_bug.cgi?id=349222 hints that at least the filedialog issue disappeared with Okteta 0.17 (or rather newer versions of KF5/Qt5).
On Okteta 0.17 I am not seeing the problems I was experiencing before. Thanks for getting back to this bug report.
Closing now, as luckily noone seems to be able to reproduce this problem anymore with recent KF5 (and Okteta) versions.