tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

Multiple xdg-script FAILURE dialogs displayed on login (permission or path failure)
by David C. Rankin 06 Mar '14

06 Mar '14

All, After rebuilding tdebase, I experienced a set of 'X-dialog' (not k-dialog) errors related to xdg-update-script failures on login. The x-dialog warned that this script would continue to run on each login -- not good. The error said there were permission or path failures involved. There was also a file placed in ~/.trinity named: r14-xdg-update-validation-test9.txt containing: <Filename>kde-kcpuload.desktop</Filename> <Filename>kde-knutclient.desktop</Filename> <Filename>kde-kcpuload.desktop</Filename> <Filename>kde-knutclient.desktop</Filename> <Filename>kde-k3bsetup2.desktop</Filename> <Filename>kde-k3bsetup2.desktop</Filename> <Filename>kde-kcpuload.desktop</Filename> <Filename>kde-knutclient.desktop</Filename> <Filename>kde-k3bsetup2.desktop</Filename> <Filename>kde-konqfilemgr.desktop</Filename> The failure warning about path and permission problems must have occurred before .xsession-error activation. Looking at the .xsession-error, here were some new messages that stood out: [r14-xdg-update] Performing a profile update for Trinity release R14 XDG compliance. [r14-xdg-update] [r14-xdg-update] To run this script against a different user directory, or automated [r14-xdg-update] from within another script, pass the directory path as a parameter. [r14-xdg-update] For example: r14-xdg-update /home/user_dir [r14-xdg-update] Use the user home directory and not the profile directory. [r14-xdg-update] User directory: /home/david [r14-xdg-update] Profile directory: /home/david/.trinity [r14-xdg-update] [r14-xdg-update] Renaming some configuration files and directories. [r14-xdg-update] dockdevtocpluginrc->doctdevtocpluginrc [r14-xdg-update] kdevgrepviewrc->tdevgrepviewrc [r14-xdg-update] kdevsnippetrc->tdevsnippetrc [r14-xdg-update] kdevfileselectorrc->tdevfileselectorrc [r14-xdg-update] kdevdesignerrc->tdevdesignerrc [r14-xdg-update] kdevdocumentation->tdevdocumentation [r14-xdg-update] kdevfileselector->tdevfileselector [r14-xdg-update] kdevabbrev->tdevabbrev WHY WAS RENAMING CONFIG FILES NECESSARY -- NONE OF THESE FILES CONFLICT WITH ANYTHING AT ALL?? Was the approach just a massive sed -e 's/k/tde/g' kdevelop/* and then patching whatever got caught up in the mix? That just seems like a bad idea... Additional messages were: [tdeinit] Got SETENV 'SESSION_MANAGER=local/valhalla:@/tmp/.ICE-unix/635,unix/valhalla:/tmp/.ICE-unix/635,inet6/valhalla:57874,inet/valhalla:36274' from tdelauncher. [tdeinit] Got SETENV 'XCURSOR_THEME=default' from tdelauncher. [tdeinit] Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/david/.gtkrc:/home/david/.trinity/share/config/gtkrc' from tdelauncher. [tdeinit] Got SETENV 'GTK2_RC_FILES=/home/david/.gtkrc-2.0-kde-kde4:/home/david/.trinity/share/config/gtkrc-2.0' from tdelauncher. Huh? Why is anything trying to set a directory on my system with "kde4" in its name?? If we are renaming things to make tde its own, then that is certainly the type of thing that would be OK to rename... -- David C. Rankin, J.D.,P.E.

1 1

TDevelop can not open existing projects
by Michele Calgaro 06 Mar '14

06 Mar '14

After the last round of renames, I can not open any existing project in TDevelop (see attachment for the error message). Can any one conrfirm this? Thanks Michele

3 5

BUG - gwenview Fails to Start - libgvimapart.la not found in path
by David C. Rankin 06 Mar '14

06 Mar '14

All, Gwenview fails to load when clicking an image in konqueror with the following error: Library files for "libgvimagepart.la" not found in paths http://www.3111skyline.com/dl/dt/trinity/ss/gwenview-lib-missing.jpg -- David C. Rankin, J.D.,P.E.

2 6

kdbg - will not execute or run program once loaded
by David C. Rankin 06 Mar '14

06 Mar '14

All, After a rebuild of tdepowersave with full debug enable, I decided to try kdbg. Opening the executable kdbg, reads the symbols and tells you it has completed reading symbol. The title shows tdepowersave and all looks ready, but there are NO active menu options at all to run or execute the program. It's like a connection is completely missing. http://www.3111skyline.com/dl/dt/trinity/ss/kdbg-no-execute.jpg The Execution menu has all items grayed out?? Can someone confirm this behavior in kdbg? -- David C. Rankin, J.D.,P.E.

2 2

Bug 1902 - tdeio_imap will exhaust available imap (anvil) if kmail open
by David C. Rankin 06 Mar '14

06 Mar '14

Slavek, One more issue with the tdeio_slaves failing to close is if kmail is left open, the automatic checks for new mails done every 10 minutes or so, will cause the mail server to begin rejecting connections after its anvil connection limit is reached (due to the imap connections never being closed): This was from my mail server after I began getting imap connection rejects: (all of those logins are from kmail that are stuck open) 953 ? Ss 0:29 /usr/sbin/dovecot 1087 ? S 0:05 \_ dovecot/anvil 1088 ? S 0:05 \_ dovecot/log 15680 ? S 0:09 \_ dovecot/config 31108 ? S 0:05 \_ dovecot/imap-login 31112 ? S 0:11 \_ dovecot/imap 1022 ? S 0:04 \_ dovecot/imap-login 1026 ? S 0:06 \_ dovecot/imap 20731 ? S 0:01 \_ dovecot/imap-login 20737 ? S 0:02 \_ dovecot/imap 21919 ? S 0:00 \_ dovecot/imap-login 21921 ? S 0:01 \_ dovecot/imap 23254 ? S 0:00 \_ dovecot/imap-login 23255 ? S 0:01 \_ dovecot/imap 25991 ? S 0:00 \_ dovecot/imap-login 25993 ? S 0:01 \_ dovecot/imap 32553 ? S 0:00 \_ dovecot/imap-login 32557 ? S 0:01 \_ dovecot/imap 15881 ? S 0:00 \_ dovecot/imap-login 15883 ? S 0:00 \_ dovecot/imap 16677 ? S 0:00 \_ dovecot/imap-login 16678 ? S 0:00 \_ dovecot/imap 19776 ? S 0:00 \_ dovecot/imap-login 19780 ? S 0:00 \_ dovecot/imap 23531 ? S 0:00 \_ dovecot/imap-login 23535 ? S 0:00 \_ dovecot/imap 23537 ? S 0:00 \_ dovecot/imap-login 23538 ? S 0:00 \_ dovecot/imap 1039 ? Ss 0:00 /usr/sbin/faxq -- David C. Rankin, J.D.,P.E.

2 15

Re: [trinity-devel] Good soft-freeze Report - 113/115 built without error on Arch
by Michele Calgaro 05 Mar '14

05 Mar '14

>I should try building kopete, but I've always preferred x-chat for some reason. >[FAILED] [00/00:00:36.144] "applications/kopete-otr" A known dependency problem for the last few months in Debian/testing. But since we are getting closer to release v14.0.0, it's time we do something about it. BTW I don't use neither kopete nor x-chat. >Kerry/Beagle -> the only good Beagle is a dead Beagle (software wise), leave it >dead, ashes-to-ashes dust-to-dust and all that jazz. >[FAILED] [00/00:00:34.221] "applications/kerry" Now builds OK! The report was slightly rearranged to mirror the new build order, but in reality libbeagle was not part of the full rebuild (I had forgotten to include it in the build list). After I saw that, I built libbeagle and after your email I rebuilt kerry. Now no problem :) [ OK ] [00/00:05:32.386] "applications/kerry" >[FAILED] [00/00:00:35.870] "applications/knetworkmanager8" Known issue, we need to add support for NM0.8 in tdehwlib >ksquirrel and libksquirrell are a few that would normally build. I believe they >provide additional graphics libs and extensions to some packages. I build >libksquirrel but not ksquirrel itself. >[FAILED] [00/00:00:36.914] "libraries/libksquirrel" >[FAILED] [00/00:00:36.301] "applications/ksquirrel" libksquirrel fails for a missing dependency and ksquirrel requires libksquirrel. I will have to check this as well. >What does smartcardauth do? I haven't built it before >[FAILED] [00/00:00:53.049] "applications/smartcardauth" As for Kerry, the problem was a missing dependency not previously built (pcsc-lite-nodbus). After recompiling, no problem! [ OK ] [00/00:03:54.424] "applications/smartcardauth" According to debian control file description: "This utility will allow you to set up your computer to accept a SmartCard as an authentication source for: - Your encrypted LUKS partition - TDE3.x, including automatic login, lock, and unlock features It is designed to work with any ISO 7816-1,2,3,4 compliant smartcard Examples of such cards are: - The Schlumberger MultiFlex - The ACS ACOS5 / ACOS6 series of cryptographic ISO 7816 cards If a card is chosen that has PKSC support, such as the ACOS cards, this utility can run simultaneously with the certificate reading program(s) to provide single sign on in addition to the PKCS certificate functionality" >Looks like a good build report as well. I like it when it works out that way. Once Slavek and I have time to merge our scripts, we will publish them. After our last conversation on the matter, we will probably do that after v14.0.0 is released, because we are trying to focus on that without introducing more delay (i.e. usability questions from user :-) ). To those who are waiting: please be patient a little more. Attached the new (manually reconstructed/reordered) build result log. Cheers Michele

2 1

Re: [trinity-devel] Good soft-freeze Report - 113/115 built without error on Arch
by Michele Calgaro 05 Mar '14

05 Mar '14

I have also done a full rebuilt after the soft freeze. Most of the modules build file (see attached report). Main exception is kopete-otr, which fails due to library dependency. I will have a go on it tomorrow probably. Cheers Michele

2 1

Good soft-freeze Report - 113/115 built without error on Arch
by David C. Rankin 05 Mar '14

05 Mar '14

All, It looks like all the hard work on the renaming and debugging payed off. After the soft freeze, end-to-end build on Arch built 112/115 packages (tdebase failed due to a reverted patch 'tdebase-kdesktop-systemd.diff' [so that didn't really count]). That leaves only 2 failures out of 115 packages. The failure were expected: makepkg --> FAILED for libtqt-perl at Mar 5 02:00:13 makepkg --> FAILED for tdebase at Mar 5 02:44:06 (patch removal) makepkg --> FAILED for kstreamripper at Mar 5 06:53:12 That means the only reason the keyboard was ever touched after starting the build was due to the tdebase failure (it being mandatory to the buildscript continuing). So except for the patch on tdebase, tde would have built end-to-end without any user interaction. That's refreshing. katesort appears to have built as part of tdeaddons, and kxmleditor was patched in from a local source. Testing can now begin. Good job Darrell, Slavek, Francios, all! -- David C. Rankin, J.D.,P.E.

1 1

Soft Freeze
by Slávek Banko 05 Mar '14

05 Mar '14

All, after a recent thorough review of the schedule and cancel freeze status, I would like to we stay on the schedule as is / will be in Etherpad - http://trinity.etherpad.trinitydesktop.org/39 In accordance with this I remind: Starting today, we went into a state Soft Freeze. This means that not to be pushed new features, major enhancements and renamings kde->tde. Depending on how quickly we will be successfully solved bug reports intended for the final release, I expect the announcement hard freeze after about two weeks. I want to thank you all for your efforts and I hope that we will soon reach a final release R14.0.0. Slavek --

3 3

R14.0.0 soft freeze
by Michele Calgaro 03 Mar '14

03 Mar '14

Dear all, this is to remind everybody that as of today, R14.0.0 has been declared feature-frozen (soft-freeze). No new apps, kde->tde renames, major enhancement will be included in R14.0.0 and they will have to wait for the next release. KXMLEditor and Katesort plugin will be included given the amount of work done on them in the last few days. I am working on a list of bugs that will have to be addressed in order to release R14.0.0. I should be able to complete the list within Wednesday and after that Tim, Slavek and Darrell will review it. When this is done, the list will be published for users/developers review and changes/additions to the list will be allowed as long as they are pertinent to R14.0.0. Once the list is fully completed and agreed upon, we should make it the official list and IMO we should declare R14.0.0 as hard-frozen. In the meantime, feel free to suggest what bugs you would like to see fixed in R14.0.0 and if you are willing to work on any of them. Please keep in mind that we want to keep the list as short as possible, in order to release R14.0.0 in a timely manner. Therefore bugs should fit in one of the next categories (in order of priority): - blockers - criticals - cause major loss of functionality to the system or to the user - results in loss of functionality that could affect R14 release reviews negatively (such as help buttons not working for example) Please do not suggest bugs that do not fit in one of these categories. Cheers Michele

5 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels