With the recent renaming changes kfilereplace is renamed to
tdefilereplace. Yet the launcher menu still shows KFileReplace. A
quick look at tdefilereplace.desktop indicates why. :-)
I can update the desktop file, but there are 8 locales in the file
I can't update. Should I go ahead and push the English change?
A small problem that has bugged me for a while. On my HTPC I use
kdialog passive popups to remind me when a TV recording starts or
stops. This is helpful to me when I run XBMC because I run XBMC in
Originally when I built my HTPC I used KDE 3.5.10. The popups
always appeared in front of XBMC, which satisfied my intent.
Through the past many months I updated the HTPC: the operating
system from Slackware 12.2 to 14.0, KDE 3.5.10 to Trinity GIT,
Nvidia proprietary drivers, and XBMC from 9.01 to 10.1.
The popups no longer appear in front of XBMC. When I toggle XBMC
from full screen to windowed mode I can see the kdialog popups, but
not when XBMC is in full mode. The popups appear in front of other
This is not a killer problem. :-) I realize there are several
variables at play, but I don't know how the kdialog mechanism
works. I'd appreciate ideas for determining whether Trinity (twin?)
or kdialog is the culprit.
>I started with most pressing - that tdelibs and tdebase. Currently
>I focus on completing 22.214.171.124. I'll see if I find some next time
>explore and cleaning of other modules. Do you have a list of how
>modules are affected?
From the top of my local repo, I performed the following:
grep -rn "\\\n\\\r" . | grep printf | grep -v sprintf
The results are limited to a handful of modules:
I did not want to interfere with any additional work you were
doing, which is why I asked rather than start patching. :-)
I notice in the commits web page you pushed some patches to change
printf statements from \n\r to \n.
I performed a quick grep of the sources. There are more printf
statements that use \n\r.
Are you planning to update the entire source tree?
Hopefully there is a configuration cure to avoid a bug report.
Any file that is opened in kate or kwrite resulting in the infamous
warning dialog that the file is binary and editing will result in a
corrupt file, renders both text editors into a non-editing mode.
For example, create a diff file using "diff -urNa" where there are
file additions or removals in the target directory. Open the diff
file in kate or kwrite. The infamous warning dialog appears and
editing thereafter is impossible. Also disabled is searching and
Bug or configuration problem?
I want to close bug report 1344. I need to remove duplicate files
and directories. I know which files and directories to delete, but
I'm uncertain about the best GIT way to do this. (Doing this
outside of GIT is easy. :-) ) Fortunately there are only 9 modules
affected, but the number of files and directories to delete varies
in each module.
>Who upstream is making this problematic? Is this a Debian-only
>issue? Is this only a packaging issue? Please explain more. What
>exactly is needed to provide remedy?
>Trinity is recognized as an XDG desktop. Upstream, whoever they
>might be, need to get on board. I doubt "upstream" has failed to
>support other XDG recognized desktops. TDE != KDE. :)
>I created a tdelibs patch and am rebuilding now. I'll start
I updated the patch by adding a -DWITH_OLD_XDG_STD configure option
works great. No KDE4 apps autostart, no problems with desktop files
in ~/.local/share/applications or $TDEDIRS.
Should upstream problems continue then this patch seems like a fair
compromise until those problems disappear.
I have not tested by building tdelibs with -DWITH_OLD_XDG_STD,
which retains the current dual behavior.