Wed Mar 15, 2017 4:05 pm
This is what I did to install Tellico 3.0.1 on my Korora distro. I'll update this post until all errors are cleared.
NOTE: Any results are on proceeding posts to keep this one clean.
Download Tellico, extract tellico-3.0.1.tar.xz and change to new folder.
I looked at CMakeLists.txt in the tellico-3.0.1 folder to see what modules and packages were being looked for and installed the libraries:
NOTE: I noticed a difference between Fedora and Debian file naming conventions (i.e., -devel vs -dev and incl. of hyphenation):
Debian/Ubuntu: libexempi-dev kf5khtml-dev
Fedora/Korora: exempi-devel kf5-khtml-devel
Next, I used CMake to configure the compilation environment:
OPTIONS: -DCMAKE_BUILD_TYPE=debug -DENABLE_WEBCAM=TRUE -DBUILD_TESTS=TRUE -DBUILD_FETCHER_TESTS=TRUE
NOTE: If you want debugging use -DCMAKE_BUILD_TYPE=debug (I used all options to troubleshoot). Barcode scanner needs -DENABLE_WEBCAM=TRUE
If you see this:
Ignore missing library and use btparse included with Tellico, per developer's instruction. https://forum.kde.org/viewtopic.php?f=200&t=139255#p373149
I could not find or it's equivalent: libbtparse libbtparse-dev libtaglib-ocaml-dev in the Fedora repository.
Result: [100%] BLAH BLAH
Optionally, I tested my build by using:
Then I installed Tellico using:
Last edited by bitmizer on Wed Mar 15, 2017 6:04 pm, edited 2 times in total.
Wed Mar 15, 2017 4:39 pm
Because I'm missing a couple of libraries, I decided to compile with troubleshooting in mind. I used the following CMake command:
The results were copied from the terminal and edited to include only what I thought was important.
Make Test Results:
I went through the build process several times and fetchers 34 to 59 (listed above) failed consistently. I'm not sure if this was because there are no Tokens/API keys.
When I launch Tellico from the menu, I get a "tellico Closed Unexpectedly" alert. If I click "Restart App", Tellico seems to work fine. Of course, I'm only using Music and Video collections right now. Here's the debug info:
Application: tellico (tellico), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa2f8642980 (LWP 18438))]
Thread 3 (Thread 0x7fa2d10a5700 (LWP 18441)):
#6 0x00007fa2ef9e8f8d in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /lib64/libQt5Core.so.5
#7 0x00007fa2f878dfb0 in QDBusConnectionPrivate::closeConnection() () at /lib64/libQt5DBus.so.5
#8 0x00007fa2f877a852 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5
#9 0x00007fa2ef81e9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#10 0x00007fa2eba546ca in start_thread () at /lib64/libpthread.so.0
#11 0x00007fa2eec11f7f in clone () at /lib64/libc.so.6
Thread 2 (Thread 0x7fa2d23bc700 (LWP 18440)):
#0 0x00007fa2eec0601d in poll () at /lib64/libc.so.6
#1 0x00007fa2e84a9d10 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2 0x00007fa2e84abaa9 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3 0x00007fa2d5997d69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4 0x00007fa2ef81e9ca in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#5 0x00007fa2eba546ca in start_thread () at /lib64/libpthread.so.0
#6 0x00007fa2eec11f7f in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7fa2f8642980 (LWP 18438)):
#0 0x00007fa2eba5a460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1 0x00007fa2ef81f04a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5
#2 0x00007fa2ef81e5ce in QThread::wait(unsigned long) () at /lib64/libQt5Core.so.5
#3 0x00007fa2f877a5a6 in QDBusConnectionManager::~QDBusConnectionManager() () at /lib64/libQt5DBus.so.5
#4 0x00007fa2f877a639 in (anonymous namespace)::Q_QGS__q_manager::innerFunction()::Holder::~Holder() () at /lib64/libQt5DBus.so.5
#5 0x00007fa2eeb44410 in __run_exit_handlers () at /lib64/libc.so.6
#6 0x00007fa2eeb4446a in () at /lib64/libc.so.6
#7 0x00007fa2ef82c8be in QCommandLineParser::process(QStringList const&) () at /lib64/libQt5Core.so.5
#8 0x00007fa2ef82c92f in QCommandLineParser::process(QCoreApplication const&) () at /lib64/libQt5Core.so.5
#9 0x00000000004f7762 in main(int, char**) (argc=3, argv=0x7fff7bcf5b18) at /home/xxxx/tellico-3.0.1/src/main.cpp:147
Thu Mar 16, 2017 11:55 am
If you run the specific test directly, it might provide more info. But yes, some of them depend on API keys, and some of them are actually failing because of changes to different websites. That's why I separated all the fetcher tests from the regular unit tests with a different CMake build flag.
Unfortunately, the debug output doesn't appear to have anything related to Tellico in it. Have you compiled any other KDE-based applications? Do they exhibit any similar issues? I'm not exactly sure what to suggest there.
Thu Mar 16, 2017 8:58 pm
As I said in the other thread, I'm not a programmer and I am not too familiar with Linux, it's file structure or file extensions. This is the first time I have tried to compile anything. So, I'll apologize in advance for not getting the nomenclature correct while describing various interfaces and such.
On that note, I tried to find a couple of Tellico executables and desktop links and I noticed a difference in their properties. I made changes to the launcher link at All Applications --> Office and Tellico started without any errors.
I right-clicked the link and selected Properties and left-clicked Edit Application. Once the Properties dialogue appeared, I selected the Application tab and edited the Command field:
I repeated this for every link in the launcher. I don't understand why, but Tellico launches without any alerts. Essentially, it works fine. I did have have 2.3.12 (KDE4) installed previously. The link wasn't updated during my 3.0.1 installation?
Now about tests. I notice that one of my cpu cores was pegged at 100% after running make test. So I opened System Monitor and found a process name "python" and hovered my mouse over it. The tool tip showed the process fr.allocine.py which didn't terminate after the test. I had to manually end the process.
I took a closer look at the LastTest.log and found warnings in core modules and fetchers, as well as stack dumps for fetchers. One of the stack dumps was for allocinefetchertest. The file is pretty long and I'm not sure if you would like me to post or email it. What should I do with the log?
EDIT: Tellico closes fine through its menu, but I intermittently get the alert window (Restart App/Report Bug) when I click the close button on the upper-right of the window. I'm going to try to consistently replicate the fault. Doesn't KDE5/Plasma not like Tellico? How do I fix this?
Fri Mar 17, 2017 1:02 am
No worries. You've made a lot of progress, and I'm happy to try to help.
That qwindowtitle string is in the org.kde.tellico.desktop file that gets installed. If you had a previous version of Tellico installed for KDE4, I would uninstall it. Since the desktop file name changed, it's likely you were executing the old one.
The old version of the Allocine data source did use a python script, but the current version uses a direct API. I should just remove the tests for the old version. Don't bother worrying about that one.
If you can get a backtrace of that crash, it might be helpful.
Sat Mar 18, 2017 2:51 am
I'm not sure if this is a "backtrace" you're talking about, but this is what i get when I click Debug in the alert window:
Steps to duplicate crash:
Launch Telllico, close Tip of the Day, Settings-→Configure (Tellico or Toolbars or Shortcuts), click Cancel (or OK for changes), exit Tellico (either by close button on upper-right of window, or Tellico icon upper-left of window or Menu-->Exit). If I remember correctly, this didn't appear until I changed properties value to "-qwindowtitle" which solved my crash during launch.
Sometimes I'll get this:
I clicked a link in the Report window and I got this message:
The packages containing debug information for the following application and libraries are missing: