tde-devels

devels@trinitydesktop.org

3 participants
3808 discussions

Re: [trinity-devel] Francois: tderadio presets
by Darrell Anderson 23 May '13

23 May '13

>> Hello, >> this command outputs nothing on my sources ... >> >> I'm using: trinity-tderadio-3.5.13.2~pre12+b7f6fa73 >> > >For me also nothing - tested on v3.5.13-sru branch and also on R14 >GIT before your updates today. > >Are you sure that you have correctly utf8 on your console? In your >patches today I see strange characters before the fix and also after fix. >They are just weird otherwise. I found part of the problem. For whatever reason, on my system konsole's encoding was set to ISO-8859-1. I set and saved the encoding to Default. I have LANG=en_US.UTF-8 in my environment. With that out of the way, now I no longer see the previous "ï¿½" character. Now I see an empty squares when I perform the same search. So please try this: Open tdelibs/tdeui/kled.cpp from the source tree. The following lines have funky characters: 2: Copyright (C) 1998 J�rg Habenicht (j.habenicht(a)europemail.com) 291: // painter routine taken from TDEUI�s KLed widget: 303: // Calculate the LED�s "light factor": 387: // painter routine taken from TDEUI�s KLed widget: 399: // Calculate the LED�s "light factor": 428: // drawing the shadow border at 45� (45*16 = 720). Ideas? Darrell

1 0

Updating Trinity for Debian Wheezy
by Darrell Anderson 23 May '13

23 May '13

Are there any online instructions for updating Trinity 3.5.13.x or GIT pre R14 for Wheezy? Darrell

2 1

Quick KOrganizer Test
by Darrell Anderson 23 May '13

23 May '13

Would somebody who uses KOrganzer please look at bug report 89 and tell me whether the bug report remains valid? Thanks. :-) Darrell

1 0

Re: [trinity-devel] Francois: tderadio presets
by Darrell Anderson 23 May '13

23 May '13

>For me also nothing - tested on v3.5.13-sru branch and also on R14 >GIT before your updates today. > >Are you sure that you have correctly utf8 on your console? Hmm. I tested LANG=en_US, LANG=en_US.UTF-8, and LANG=en_US.ISO8859- 1. I fully logged out of the system and not just exiting Trinity to ensure the variables were properly set. In each case changing the LANG environment variable made no difference and I see the same funky characters with each variable. >In your patches today I see strange characters before the fix >and also after fix. They are just weird otherwise. Are you saying the patches are bad? I'm confused! Darrell

1 0

Francois: tderadio presets
by Darrell Anderson 23 May '13

23 May '13

Francois, In bug report 1352 we updated the tderadio presets. I now believe the original patch was corrupted. Try the following search in the tderadio sources: grep -rn "ï¿½" . Thanks. Darrell

3 2

Updating generic documentation files (AUTHORS, COPYING, README, etc.)
by Darrell Anderson 22 May '13

22 May '13

I was looking into updating the README files with respect to non- historical branding references to KDE/KDE3. So as to not incorrectly update historical references, updating those files probably is a file-by-file project. There are 966 README files and that basically stopped my motivation for updating the files. Further, there are 287 AUTHORS files, 275 ChangeL|log, 298 COPYING*, 173 INSTALL, 116 NEWS, 7 PACKAGING, 11 RELEASE*, and 366 TODO. I suspect many --- possibly most --- of these text files provide little to no value anymore. The AUTHORS files are redundant of the Trinity About dialogs, likely all of the change log files have not been updated since several releases before 3.5.10 and certainly have not been updated in the Trinity era, the COPYING* files are redundant to almost all *.cpp files, the INSTALL files are irrelevant at best, the NEWS files all are outdated, PACKAGING files obsolete, RELEASE files obsolete. There might be a handful of useful ideas in some of the TODO files, but likely they could be consolidated into a wiki page or bugzilla enhancement requests --- not that we have the available personnel to accomodate most of those wish list items. Should we delete most of these text files? Comments? Darrell

1 0

3.5.13.2
by Darrell Anderson 22 May '13

22 May '13

What is the status of 3.5.13.2? Darrell

3 6

Notice before updating the common module 'admin'
by Slávek Banko 22 May '13

22 May '13

Hi all. To solve build with automake 1.13 (see bug 1520) I'm going to push the patch into common module 'admin'. This will subsequently lead to the updating of almost all other modules. And the resulting rebuild almost all packages. Tim, because it is fast approaching the conclusion of version 3.5.13.2, I will soon completely rebuild all packages for the final version => I'll also have a heavy burden for the build-farm. Slavek

1 0

Re: [trinity-devel] Window settings broken?
by Darrell Anderson 20 May '13

20 May '13

>I rebuilt a full package set on Sunday. Today I notice kpdf opens >in a tiny 470x285 window. Maximzing kpdf, then closing, then >reopening results in the same tiny window. Forced settings fail to > >override. Previously kpdf always opened maximum screen for me. >kpdf >now seems to ignore the kpdfrc [MainWindow] settings, which I >verified have not changed. I don't know whether this behavior is >limited to kpdf or affects all apps. > >I believe this is a very new bug. I'm asking for confirmation >before filing a report. I haven't yet tried to try to bisect when >this behavior began by reinstalling packages from older build >sets. The problem is caused by building tqt3 with the -glibmainloop configure option. Building without that option results in kpdf opening correctly. Darrell

1 0

Window settings broken?
by Darrell Anderson 20 May '13

20 May '13

I rebuilt a full package set on Sunday. Today I notice kpdf opens in a tiny 470x285 window. Maximzing kpdf, then closing, then reopening results in the same tiny window. Forced settings fail to override. Previously kpdf always opened maximum screen for me. kpdf now seems to ignore the kpdfrc [MainWindow] settings, which I verified have not changed. I don't know whether this behavior is limited to kpdf or affects all apps. I believe this is a very new bug. I'm asking for confirmation before filing a report. I haven't yet tried to try to bisect when this behavior began by reinstalling packages from older build sets. Thanks. :) Darrell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels