tde-devels

devels@trinitydesktop.org

2 participants
3849 discussions

Re: [trinity-devel] suse 42.1 - crucial(?) trinity package(s) require an unavailable package
by François Andriot 15 May '16

15 May '16

Le 14/05/2016 11:58, Felix Miata a écrit : > > > The "trinity-libarts-akode" package requires the library > > "libakode.so.2", which is supposed to be provided by "trinity-akode" > > package. > > In your case, zypper found that it was provided by "libakode". > > > Notice that the Trinity's package for Akode is split in several smaller > > package, e.g. "trinity-akode" and several "libakode_xxx". > > > I do not even have any 'libakode' package available in my 42.1 > > installation, > > I didn't expect anyone would, since there is no such package in 42.1 > repos for zypper to find. > > > so where does it come from ? > > Maybe it is inherited from a previous opensuse release that you have > > upgraded , or it comes from another 3rd party repository... > > 42.1 in this case is an upgrade (zypper dup) from _Factory_ (before > the name change to Tumbleweed, from an installation last upgraded as > Factory in December 2014). What I don't understand is how to get rid > of the libakode package when the package manager claims other packages > depend on it. Will rpm -e --nodeps not break the TDE packages that > zypper claims depend on it? Why doesn't zypper recognize the trinity* > package(s) you mention as providing the required libs? Are the Trinity > packages broken WRT dependencies? Yes, you can forcibly remove the libakode package (rpm -e --nodeps) and then install trinity-akode , it won't break your system;. It is likely that 'libakode' was installed before Trinity on your computer, and the 'trinity-akode' does not obsolete 'libakode', so it was kept intact. François

2 1

Kontact and KNotes issue
by deloptes 14 May '16

14 May '16

Hi, I'm not sure which of both (Kontact or KNotes) is causing the problem, however when I add/change/delete a note in one of them, the other is not notified and does not update. Do you know how this works - I would guess via part? I think it is worth looking into, but perhaps you know more than me as I'm at level 0. regards

1 0

[trinity-devel] suse 42.1 - crucial(?) trinity package(s) require an unavailable package
by Felix Miata 14 May '16

14 May '16

# rpm -qa | grep kode libakode-2.0.2-419.1.x86_64 trinity-kode-14.0.3-1.oss421.x86_64 trinity-libarts-akode-14.0.3-1.oss421.x86_64 # zypper se -s libakode | libakode_jack_sink | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE | libakode_jack_sink-debuginfo | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE | libakode_mpeg_decoder | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE | libakode_mpeg_decoder-debuginfo | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE | libakode_pulse_sink | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE | libakode_pulse_sink-debuginfo | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE | libakode_src_resampler | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE | libakode_src_resampler-debuginfo | package | 2:2.0.2-14.0.3_1.oss421 | x86_64 | TDE i | libakode | package | 2.0.2-419.1 | x86_64 | (System Packages) # zypper rm libakode Loading repository data... Reading installed packages... Resolving package dependencies... The following 8 packages are going to be REMOVED: libakode trinity-desktop trinity-juk trinity-kttsd trinity-kttsd-contrib-plugins trinity-libarts-akode trinity-tdeaccessibility trinity-tdemultimedia 8 packages to remove. After the operation, 7.1 MiB will be freed. Continue? [y/n/? shows all options] (y): n Normally, packages listed as "System Packages" with no corresponding available package are those that have become obsolete. Why do these Trinity packages depend on a package that is not currently available? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

1 0

Addressbook next encoding issue
by deloptes 14 May '16

14 May '16

Hi again, it would have been too nice to be true, but there is the next issue in the chain. When I wrote yesterday "I tested", I meant I build and installed deb and restarted the virtual machine. I checked the address book and all the utf8 chars were still in place. Today however I pressed the reload button and got all the utf8 converted into ? signs (which is pointing to ascii conversion). Looking into the code there is vcardformat and vcardformatimpl. I finalized the vcardformat test which checks save and load, but all looks good. I am going to write a test for vcardformatimpl, but I am not even sure I'm looking into the right direction. Where and how do I find what is behind the reload button? thanks

1 2

DVD drive access trouble on Jessie
by Felix Miata 13 May '16

13 May '16

I have 14.0.3 installed freshly on Jessie on an AMD Cedar machine 18 months old. When I try doing anything to access a CD in either of the two DVD drives, http://fm.no-ip.com/Tmp/Linux/Sound/xsession-errors-jessie-easyst.txt (includes dmesg tail) shows some sort of audio setup problem seems to be repeatedly trying and failing. When KsCD triggers this, it gets hung by the problem. Simply logging out of the session takes an excessive length of time, and so does attempting to reboot. Holding down CAD produces a long string of failed to store sound card state messages instead of rebooting, until well over a minute passes. On reboot, journal recovery occurs. /etc/group seems to have the required user permission assignments. Aplay works OK on a test .wav file, and so does normal startup and shutdown system sounds. How can I tell where the fault lies? Could there be a broken dependency? I don't see any open bug that seems related. Output from alsa-info.sh: http://fm.no-ip.com/Tmp/Linux/Sound/alsa-info-jessie-easyst.txt -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

3 7

testing: tdeabc/vcardparser$ more README.testing
by deloptes 10 May '16

10 May '16

Hi, I'm looking for a way to test the vcardparser. It looks like there is a small test utility in tdeabc and tdeac/vcardparser. tdeabc/vcardparser$ more README.testing For testing the vcardparser there are some test files and a small testsuite automatically checking for regressions. ... ... Now with cmake building in test dir ======== mkdir test && cd test && cmake .. cd tdeabc/vcardparser test/tdeabc/vcardparser$ make check make: *** No rule to make target 'check'. Stop. cd .. test/tdeabc$ make check make: *** No rule to make target 'check'. Stop. ======== but doing the old automake (it does not compile for various reasons) produces a Makefile in vcardparser that (almost) works ======== cd tdelibs-trinity-14.0.3/tdeabc/vcardparser make check make testread testwrite testread2 make[1]: Entering directory '/opt/software_x64/KDE/TDE/tdelibs-trinity-14.0.3/tdeabc/vcardparser' g++ -DHAVE_CONFIG_H -I. -I../.. -I../../dcop -I../../kjs -I../../tdecore -I../../tdeio/kssl -I../../tdeabc -I../../tdeabc -I../../dcop -I../../libltdl -I../../tdefx -I../../tdecore -I../../tdecore -I../../tdecore/network -I../../tdeui -I../../tdeio -I../../tdeio/tdeio -I../../tdeio/tdefile -I../.. -I/usr/share/tqt3/include -include tqt.h -I. -I/opt/trinity/include -DQT_THREAD_SUPPORT -D_REENTRANT -I/usr/include/tqt -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT testread.o -MD -MP -MF .deps/testread.Tpo -c -o testread.o testread.cpp In file included from testread.cpp:33:0: ../../tdeabc/vcardconverter.h:26:23: fatal error: addressee.h: No such file or directory #include "addressee.h" ^ compilation terminated. Makefile:710: recipe for target 'testread.o' failed make[1]: *** [testread.o] Error 1 make[1]: Leaving directory '/opt/software_x64/KDE/TDE/tdelibs-trinity-14.0.3/tdeabc/vcardparser' Makefile:840: recipe for target 'check-am' failed make: *** [check-am] Error 2 ======== Furthermore cmake refuses to use the src dir and does not produce usable Makefile for the test suite ======== tdelibs-trinity-14.0.3$ cmake . -- The C compiler identification is GNU 4.9.2 -- The CXX compiler identification is GNU 4.9.2 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found PkgConfig: /usr/bin/pkg-config (found version "0.28") CMake Error at cmake/modules/TDEMacros.cmake:24 (message): ################################################# Please use out-of-source building, like this: rm /opt/software/KDE/TDE/tdelibs-trinity-14.0.3/CMakeCache.txt mkdir /tmp/tdelibs.build cd /tmp/tdelibs.build cmake /opt/software/KDE/TDE/tdelibs-trinity-14.0.3 [arguments...] ################################################# Call Stack (most recent call first): cmake/modules/TDEMacros.cmake:1534 (tde_message_fatal) CMakeLists.txt:39 (include) -- Configuring incomplete, errors occurred! See also "/opt/software/KDE/TDE/tdelibs-trinity-14.0.3/CMakeFiles/CMakeOutput.log". ======== Let me know what you think about it and should we raise a bug to track and fix it. thanks in advance

5 17

CMake + tdelfeditor × versioned libraries
by Slávek Banko 19 Apr '16

19 Apr '16

Hi all, I noticed one problem regarding the cmake build of libraries with versioning and tdelfeditor. Tdelfeditor is used not only on file with the appropriate version, but also on base 'so' file without a version number. However, this is a symlink to the file with the appropriate version. Use tdelfeditor causes that instead of this symlink is created a regular file. Results are then two full 'so' files, which is incorrect. For example, in tdebase (current stable R14.0.3 Wheezy@amd64): libkonq.so - size 809232 (package libkonq4-trinity-dev) libkonq.so.4.2.0 - size 809240 (package libkonq4-trinity) Solutions should be simple: in the common cmake module run tdelfeditor only on libraries with the appropriate version and on base files only if the library is not versioned. In some cases tdelfeditor is used, although library is not shared == tdelfeditor is started without valid arguments. See proposed patch. I believe that there is no reason against to push the patch. There will be only one consequence - the patch causes rebuild almost all packages. -- Slávek

3 13

Testing TDE on the latest ubuntu
by Diego M. Vadell 17 Apr '16

17 Apr '16

Hi everybody, I was thinking about helping by testing TDE on the upcoming Ubuntu release (16.04). Do you think is useful? Should I test git, the nightly snapshot or 14.0.3? Or all of them? Cheers, -- Diego.

5 6

TDEPIM TDEABC backup or cache files
by deloptes 16 Apr '16

16 Apr '16

I start new thread here to track this phenomenon. I'm really p*ss*d off, because something is really wrong with that. Luckily I make backup before playing around and based on my experience from the past. So here are my findings - no deeper code analyses yet. When syncing 220 contacts to empty address book it ended up with only 72 in the address book (vcf) configured. This magic number 20 seem to be hardcoded undo steps. So what tdeabc was doing, is saving couple of contacts and making backup and again and again. Why the last copy of the vcf file had only 72 is still a mystery, but I already had some headache with this phenomenon. I think I'll have a closer look and play with it a bit. Perhaps I'll come up with some improvement. I hope I'll be able to reproduce this with the filesync or some test code. Oh and BTW if one does copy-paste of contact from one address book into another the encoding/conversion issue gets visible. I'll test the Fat-Zer patch and get back reporting to the bug we opened. I now understand what was wrong with opensync as well (haha - obviously nothing) ... it took me just another 10y to come to the rootcause. (to be continued) regards

2 1

TDEPIM with SyncEvolution
by deloptes 10 Apr '16

10 Apr '16

Hi all, I now have one version that I would consider working and of preproduction state. Next steps Is someone willing to test it, or how would you proceed in this case? I do not have cal/carddav accounts or any of the other supported peers. I have only two phones I could test with - Nokia 5530 and Nokia N9. It would be interesting to test with other phones, devices, systems etc. - at least the contacts and the calendar ( which I believe work fine now). Contacts and Calendar I tested address book (contacts) and calendar (events) extensively on both phones. Todos and Memos (journal) The 5530 has some strange calendar type, so todo and memo worked only from phone to TDE, but not v.v. for obvious reason. I am waiting now for some hints on how to configure (perhaps virtual calendar or special settings). On the N9 I did not test those extensively. I tested briefly todos and it works fine. Memos in N9 are TDE/Knotes (see below). Notes I also did not implement the classical KDE/TDE notes - but I will soon do so as this will be helpful for the N9 (and perhaps other phones/systems/peers too). I have the basic structure and functions, but this goes into a separate plugin and was not a prio. Build As SyncEvolution is using the automake system, the code is integrated into it. (Not sure if this is of any interest) Packaging SyncEvolution is provided by debian main line. Should the code be pushed there or we could provide a deb package with the tdepim part from within trinity? I am not sure if the debian main line will work with it. I had to explicitly disable some configure options to have it working. What does one do in such a case? Provide the full package? I would need some help here and brainstorming as well. Code availability Where would you upload the code for testing in this case? What is the "standard" procedure. I dislike google but have account @sourceforge Is the latter good to go? Optimization There were some good advises from Fat-Zer regarding string encoding, but I couldn't follow (as my time window is closing now), so I still convert the TQString into std::string and then assign the content. (One could save some memory here and there). valgrind does not complain about the code - it looks clean. Fun I had some issue yesterday on the test env (2G mem) where it crashed, because of memory exhausted. It turned out that opening the log file in konqueror consumed 1,7G :D ... I was thinking for a moment - come one, you were just syncing fine until last start of the virutal machine ... WTF happened, but it was the konqueror and the log file :D I also didn't follow up with the parseVCard - I'm not sure if it needs to be handled as a bug - it seems to be left over from the babylonian times, but someone has to retest and work it out properly and I do not think that I could spend the time now and take the responsibility. thanks in advance for your patience and support regards

2 5

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels