tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

katapult: warning: comparison with string literal
by Darrell Anderson 01 Nov '12

01 Nov '12

I noticed the following warning when building katapult: documentcatalog.cpp:176:57: warning: comparison with string literal results in unspecified behaviour [-Waddress] From what I gather the problem is trying to compare incompatible data types, usually strings to pointers. Somebody please review the proposed patch: ====================================== diff -urN katapult/katapult/plugins/catalogs/documentcatalog/documentcatalog.cpp katapult.new/katapult/plugins/catalogs/documentcatalog/documentcatalog.cpp --- katapult/katapult/plugins/catalogs/documentcatalog/documentcatalog.cpp 2012-09-14 17:40:04.000000000 -0500 +++ katapult.new/katapult/plugins/catalogs/documentcatalog/documentcatalog.cpp 2012-11-01 11:27:44.000000000 -0500 @@ -173,7 +173,7 @@ if(files.count() > 0) { newStatus |= S_HasResults; - if(files.count() > 1 || files.at(0)->className() == "Directory") + if(files.count() > 1 || strcmp(files.at(0)->className(), "Directory")) newStatus |= S_Multiple; } else newStatus |= S_NoResults; ====================================== Thanks! Darrell

1 1

tdetoys and tdeutils cmake support
by Fat-Zer 30 Oct '12

30 Oct '12

Is there anybody who is already working on it?

3 7

Trinity composition manager
by Darrell Anderson 30 Oct '12

30 Oct '12

Please correct me, but to my knowledge there is no mechanism in place to warn users when the Trinity compositor will not work. There are two conditions that I am aware: * An existing xorg.conf contains the following: Section "Extensions" Option "Composite" "false" EndSection * A packager purposely disables compositor support such as proposed in enhancement request 1289: -DWITH_XCOMPOSITE=OFF. Currently with either condition, the user is allowed to enable the compositor, KControl->Desktop->Window Behavior->Translucency, and there is no feedback that this is an exercise in futility, which likely will confuse most users. What is the preferred method for informing users why their efforts will not succeed, or to inform them that the options are unavailable? Darrell

2 2

Latest GIT is broken
by Darrell Anderson 30 Oct '12

30 Oct '12

Updated late last night to the latest GIT. Fresh build of all packages. Build failures in tdegames, tdevelop, tdewebdev, koffice with: kgameprogress.moc:1: error: expected id-expression at end of input layout.moc.cpp:100: error: expected id-expression at end of input KDGanttMinimizeSplitter.cpp:56: error: expected id-expression before 'static' Darrell

3 11

Bugzilla
by Darrell Anderson 30 Oct '12

30 Oct '12

Tim, Calvin, Please enable the voting feature of bugzilla. :) Darrell

2 7

Bookmarks in kdialog and konqueror fail to function
by Darrell Anderson 26 Oct '12

26 Oct '12

I'm using the latest GIT sources from the past couple of days. This is a full package set rebuilt. I'm seeing may related error messages in the xsession log: KAction::property( "icon" ) failed: property invalid or does not exist KAction::setProperty( "icon", value ) failed: property invalid, read-only or does not exist KAction::property( "name" ) failed: property invalid or does not exist KAction::setProperty( "name", value ) failed: property invalid, read-only or does not exist KToolBarPopupAction::property( "shortcut" ) failed: property invalid or does not exist KToolBarPopupAction::setProperty( "shortcut", value ) failed: property invalid, read-only or does not exist KToolBarPopupAction::property( "name" ) failed: property invalid or does not exist KToolBarPopupAction::setProperty( "name", value ) failed: property invalid, read-only or does not exist KToggleFullScreenAction::property( "shortcut" ) failed: property invalid or does not exist KToggleFullScreenAction::setProperty( "shortcut", value ) failed: property invalid, read-only or does not exist KToggleFullScreenAction::property( "name" ) failed: property invalid or does not exist KToggleFullScreenAction::setProperty( "name", value ) failed: property invalid, read-only or does not exist KonqMainWindow::property( "currentProfile" ) failed: property invalid or does not exist KonqSidebarBrowserExtension::property( "urlDropHandling" ) failed: property invalid or does not exist ListViewBrowserExtension::property( "urlDropHandling" ) failed: property invalid or does not exist KBookmarkAction::setProperty( "url", value ) failed: property invalid, read-only or does not exist KBookmarkAction::setProperty( "address", value ) failed: property invalid, read-only or does not exist My previous full package set from Oct. 17 did not have this problem. So only a few patches qualify as the cause. Darrell

1 1

Which files in the user guides to be installed?
by Slávek Banko 24 Oct '12

24 Oct '12

Darrell, all, In the patch for tdenetworks (attachment 926 / 927 in bug 1262) I solved that with cmake are not installed some files into the 'doc' that were installed with autotools: + knewsticker: TODO + kppp: costsgraphs.fig, kppp.faq.question, ttyS-cua.txt + krdc: authentication.eps, krdc_window.eps, preferences_profilestab.eps, preferences_rdpdefaultstab.eps, preferences_vncdefaultstab.eps, snapshot.eps, snapshot_connectionspeed.eps, snapshot_nobrowse.eps, snapshot_vncentry.eps + krfb: configuration_access.eps, configuration_network.eps, configuration_session.eps, connection.eps, email_invitation.eps, invitation_management.eps, personal_invitation.eps, screenshot.eps For some files, I am not sure if this is considered a "source" and omission when installing is right - desirable? For example 'fig' and 'eps' files. Please, I need someone smarter to give me advice. Slavek --

2 2

Proposal change description for version numbers
by Slávek Banko 24 Oct '12

24 Oct '12

Hi all, in preparing the road map, I noticed that in tdelibs/tdecore/tdeversion.h are the instructions for the version numbers different from the way we intended. My proposal to change the description as follows: AS IS: ====== /* R <ABI VERSION> . <BUGFIX REVISION> . <SECURITY PATCHLEVEL> Security patchlevel is not present on initial release It is added on the first security release, starting with ".a" ".a" would correspond to a TDE_VERSION_RELEASE of 1, ".b" would be 2, etc. A new bugfix revision resets the security level A new ABI version resets both the bugfix revision and the security level */ CHANGE TO: ========== /* R <ABI VERSION> . <FEATURE REVISION> . <BUG AND SECURITY PATCH LEVEL> Initial release is always R<ABI VERSION>.0.0. BUG AND SECURITY PATCH LEVEL is always updated with a point release. FEATURE REVISION is updated when new features are introduced or existing features are significantly updated. A FEATURE REVISION release does NOT include ABI changes. A new FEATURE REVISION level always resets the BUG AND SECURITY PATCH LEVEL. A new ABI version resets both the FEATURE REVISION level and BUG AND SECURITY PATCH LEVEL. */ What is your opinion? Slavek --

1 0

Draft: R14.0.0 Road Map
by Slávek Banko 24 Oct '12

24 Oct '12

Hi all, some time ago I was in the users mailing-list announced that I wanted to write a proposal to work on new Trinity versions with GIT branches. To few initial paragraphs were added the some next sections. And result is the draft for plan to release R14.0.0 - road map. Because the proposal is longer, I placed it on the Etherpad: http://trinity.etherpad.trinitydesktop.org/39 As you all know, my English is not good - English is not my native language. So at this point I would like to thank Darrell for help with the correction of this proposal. Your ideas and comments are welcomed. Slavek --

1 0

kmail: The server certificate failed the authenticity test
by Darrell Anderson 23 Oct '12

23 Oct '12

I receive the following message when I send an email with one of my email addresses: The server certificate failed the authenticity test The certificate is good to 2016, but something else must trigger this dialog. I don't know how the code logic inspects certificates to send those dialogs. Perhaps I have something configured incorrectly. A second dialog prompts: Would you like to accept this certificate forever without being prompted? I select Forever but the next time I send an email I see the same dialogs, which implies kmail is not saving that option correctly. Can anybody confirm this behavior? I don't see anything obvious in the bug tracker. Darrell

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels