All,
Is there anywhere in TDE, where default setting for xterm should be set to
prevent the black text on black background I currently see when I launch xterm?
Should we set a default term color and geometry in XDG somewhere?
--
David C. Rankin, J.D.,P.E.
Building from GIT.
fmt_codec_pnm.cpp: In member function 'virtual s32 fmt_codec::read_init(const std::string&)':
fmt_codec_pnm.cpp:959: error: 'exit' was not declared in this scope
fmt_codec_pnm.cpp:969: warning: suggest braces around empty body in an 'else' statement
make[2]: *** [fmt_codec_pnm.lo] Error 1
make[2]: Leaving directory `/dev/shm/libksquirrel/kernel/kls_pict'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/dev/shm/libksquirrel/kernel'
make: *** [all-recursive] Error 1
Any ideas how to fix?
Darrell
As of yesterday before syncing to the latest GIT, building against TQt3:
Fails to build:
avahi-tqt (bug report 920, FTBFS)
kstreamripper (bug report 946, FTBFS)
libksquirrel (FTBFS, fmt_codec_pnm.cpp:959: error: 'exit' was not declared in this scope)
mlt (FTBFS, has not been converted fully to tqt layer?)
Builds with patching or work-arounds:
tdelibs (bug report 627, Kspell Sym Link Incorrect)
tdebindings (bug report 597, tdebindings will not build without numerous patches)
tdemultimedia (bug report 788, Kaudiocreator won't build unless configure finds the cdda headers; 790, audiofile.h configure errors)
tdeadmin (bug report 871, FTBFS Against TQt3)
tdesdk (bug report 872, FTBFS Against TQt3)
tdenetwork (bug report 598, will not build on Slackware with wifi support)
amarok (bug report 347, Sym Links Incorrect)
kipi-plugins (bug report 613, Sym Links Incorrect)
konversation (bug report 626, Sym Links Incorrect )
kdiff3 (bug report 930, Sym Links Incorrect)
kmplayer (bug reports 931, Sym Links Incorrect; 943, Can't find the TQt version of the dbus-1.0 headers)
tellico (bug report 932, Sym Links Incorrect)
krusader (bug report 933, Sym Links Incorrect)
knights (bug report 939, Sym Links Incorrect)
kile (bug report 940, Sym Links Incorrect)
kpilot (bug report 945, FTBFS: Can't find tqt headers)
rosegarden (bug report 948, FTBFS when liblo is not installed )
Builds without error but incompletely:
tdeutils (bug report 877, X11/extensions/extutil.h: present but cannot be compiled)
k3b (bug report 942, Can't find the TQt version of the dbus-1.0 headers)
gwenview (bug report 873, will not build libmng support)
Package is missing:
tqca (bug report 817 --- I have a buildable package sources ready for the community)
Builds without patching or serious errors:
Dependencies/Core:
tqt3
tqtinterface
arts
dbus-tqt
dbus-1-tqt
tqca-tls
libart_lgpl
libcaldav
libcarddav
sip
python-tqt
tdebase
Libraries:
libkdcraw
libkexiv2
libkipi
libtqt-perl
python-trinity
pytdeextensions
Main suite:
tdeaccessibility
tdeartwork
tdegames
tdetoys
tdeedu
tdegraphics
tdevelop
tdeaddons
tdewebdev
tdepim
Applications:
k9copy
gtk-qt-engine
ksystemlog
kaffeine
digikam
knemo
ktorrent
koffice
kpowersave
basket
krename
kgtk-qt3
soundkonverter
kmyfirewall
kradio
kchmviewer
kbookreader
kiosktool
kmymoney
abakus
kbarcode
kima
katapult
Haven't tried to build:
Any application not listed here
Overall, not bad. Many of the referenced bug reports are paper cuts. None by itself breaks Trinity but all combined creates an uncomfortable feeling. :)
If somebody explains how to resolve the broken sym link bug reports, which breaks the HTML help files for non English languages, I am willing to work on resolving them.
Several of the other build related bugs are automake or cmake issues. I suspect most if not all can be resolved with nominal effort by experts.
I'll work with anybody who tackles any of the listed bug reports. I will patch, build, and test as fast as my dual core will allow me. :)
Darrell
Recently two significant usability bugs were fixed with simple one-liners in the code:
372 Storage media applet doesn't show usb stick at session startup
385 Unmounted removable device icons do not appear on the desktop
Both were resolved in GIT hash 43bb5b9.
Along with the patch for bug report 392, "Device Icon Placement," sanity has been restored to device icons.
Thank you everybody!
Darrell
Recently David shared some issues with starting Trinity. In his case the probable cause seemed to be stale profile cache file or profile cache files using the old prefix names.
Today I stumbled across a way to stall the session startup. I changed some settings in KControl.
What caught my eye with this bug is the xsession log error, which David saw as well:
ksmserver: '<wm>' missing.
ksmserver: Use --help to get a list of available command line options.
I traced the cause to these lines in my profile twinrc:
[ThirdPartyWM]
WMAdditionalArguments=
WMExecutable=twin
Those lines and group do not exist in a twinrc backup file and is the only difference between the files.
This is not a hard freeze. Trinity exits gracefully back to the command line, which is how I start X/Trinity.
The problem is with tdeinit_phase1. I commented out that command in starttde. I successfully substituted all of the following:
kwrapper ksmserver --windowmanager twin --windowmanageraddargs ""
kwrapper ksmserver --windowmanager twin
kwrapper ksmserver
Looking at the tdeinit_phase1 source code, I see that when WMExecutable is undefined/empty then tdeinit_phase1 defaults to "kwrapper ksmserver." As my previous twinrc contained no ThirdPartyWM group in twinrc, that is how tdeinit_phase1 always started.
When I changed some settings in KControl to cause twinrc to update with including the ThirdPartyWM group, tdeinit_phase1 instead starts with "kwrapper ksmserver --windowmanager %1 --windowmanageraddargs %2."
Changing the twinrc WMAdditionalArguments to WMAdditionalArguments=--lock allowed Trinity to start using tdeinit_phase1.
I think the solution then is to add the following condition test to tdeinit_phase1:
else if (wmArguments == "") {
return_code = system((TQString("kwrapper ksmserver --windowmanager %1").arg(wmToLaunch)).ascii());
Comments?
Darrell
All,
Upon k3b start, the only error received during startup check was:
<quote>
System locale charset is ANSI_X3.4-1968
Your system's locale charset (i.e. the charset used to encode filenames) is set
to ANSI_X3.4-1968. It is highly unlikely that this has been done intentionally.
Most likely the locale is not set at all. An invalid setting will result in
problems when creating data projects.
Solution: To properly set the locale charset make sure the LC_* environment
variables are set. Normally the distribution setup tools take care of this.
</quote>
I know about a year ago, there was considerable discussion about where these
variables should be set. Looking, it seems that some distros take care of this
with XDG config which can be set separately between gnome XDG and kde XDG. Does
TDE need to look at setting these? I don't know the answer. I do know SuSE sets
them and Arch doesn't. So there is a variation between the way this is handled
distro to distro. May not be a bad thing to do in the TDE config if these
setting matter.
--
David C. Rankin, J.D.,P.E.
All,
For those not familiar with applications/basket (Basket Notepads), it is
probably the finest 2nd brain invented for TDE. You can simply squirrel away all
types of information and notes in a simple manner. (text, graphics, audio,
colors, etc..) Think of it as an integrated sticky notes suite on steroids
providing full search of all the information you have in it. I have built up
hundreds of notes over the years and this is a must have app for me.
Builds and works fine:
http://www.3111skyline.com/dl/dt/trinity/ss/basket-1.0.3.jpg
Tip: set the following settings for improved ease of use:
(Basket tab)
[x] insert note when clicking to the right of the insertion line.
(General tab)
Show main windows when mouse hovers over system try icon for 7 tenths second
Crystal window decorations and basket notepads were the last 2 'must-haves'
before I could ditch 3.5.12 and move to 3.5.14 as my daily driver :)
--
David C. Rankin, J.D.,P.E.
All,
I have twin-style-crystal building on TDE. The version of crystal in GIT is
1.0.5. I want to get 1.0.7 building. I have both build directories and I will
work though them to see if I can figure out why. What I would like to get is
advise on what to start with to see if I can isolate the issue. Do I start with
the 'configure' files and go from there, or is it better to diff the raw sources
before trying to sort it out. Basically, the error with 1.0.7 is:
g++ -DHAVE_CONFIG_H -I. -I.. -I/opt/trinity/include -I/opt/tqt3/include -I.
-include tqt.h -I/usr/include/tqt -I/usr/include/tqt/Qt -DQT_THREAD_SUPPORT
-D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE
-Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -O2 -march=x86-64
-mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4
-D_FORTIFY_SOURCE=2 -Wformat-security -Wmissing-format-attribute
-Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common
-I/usr/include/tqt -MT embedtool.o -MD -MP -MF .deps/embedtool.Tpo -c -o
embedtool.o embedtool.cpp
In file included from embedtool.cpp:26:0:
/usr/include/tqt/Qt/qimage.h:45:30: fatal error: QtGui/qtransform.h: No such
file or directory
compilation terminated.
There is no QtGui/qtransform.h on my system even though it is included from
tqt/Qt/qimage.h. Should I look for a missing package or option not-enabled on
one of the packages that is already built? From searching, it looks like QtGui
is a plugin to Qt (or in this case TQt). Is there such a thing in TDE?
--
David C. Rankin, J.D.,P.E.