Tim,
What is involved to rename KDED to TDED?
I'm willing to explore and perform the grunt work and testing, but would appreciate guidance about covering all angles.
This is one of those cosmetic things that doesn't look right in Trinity. We've done so much good work with renaming and branding that to see "KDED" in kcontrol, dialogs, etc., just looks awkward.
Thanks.
Darrell
I'm updating various help guides.
The first section of the "TDE for Administrators" help guide, "Chapter 25. TDE Internals, Overview," is empty.
Note: To view this help guide, select the TDE User Guide and scroll to section VI.
I would be grateful for suggestions and ideas for what information should go in this section.
For R14 I would like at least to provide an outline of topics, even if we don't get around to actually providing detailed content.
Thanks!
Darrell
Tim,
Within the past two days or so I am experiencing occasional crashes when I log out of the Trinity session. I suspect commit 513ffc6e because of this backtrace:
[Thread debugging using libthread_db enabled]
[KCrash handler]
#5 0xb6139a67 in raise () from /lib/libc.so.6
#6 0xb613b2e2 in abort () from /lib/libc.so.6
#7 0xb617805d in __libc_message () from /lib/libc.so.6
#8 0xb617e5aa in malloc_printerr () from /lib/libc.so.6
#9 0xb6181503 in _int_free () from /lib/libc.so.6
#10 0xb61846b0 in free () from /lib/libc.so.6
#11 0xb636b191 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#12 0xb636b1ed in operator delete[](void*) () from /usr/lib/libstdc++.so.6
#13 0xb675f2f0 in ~TQObject (this=0x8180da8, __in_chrg=<value optimized out>)
at kernel/qobject.cpp:475
#14 0xb6794a39 in ~TQWidget (this=0x8180da8, __in_chrg=<value optimized out>)
at kernel/qwidget.cpp:1007
#15 0xb71cd059 in ~KLed (this=0x8180da8, __in_chrg=<value optimized out>)
at /dev/shm/tdelibs/tdeui/kled.cpp:106
#16 0xb5eb8195 in ~KLedButton (this=0x8180da8, __in_chrg=<value optimized out>)
at kledbutton.cpp:43
#17 0xb67949ad in ~TQWidget (this=0x8174e20, __in_chrg=<value optimized out>)
at kernel/qwidget.cpp:996
#18 0xb5ea1c11 in ~MixDeviceWidget (this=0x8174e20,
__in_chrg=<value optimized out>) at mixdevicewidget.cpp:67
#19 0xb5ea739f in ~MDWSlider (this=0x8174e20, __in_chrg=<value optimized out>)
at mdwslider.h:66
#20 0xb67949ad in ~TQWidget (this=0x8171c28, __in_chrg=<value optimized out>)
at kernel/qwidget.cpp:996
#21 0xb5e9bab3 in ~ViewBase (this=0x8171c28, __in_chrg=<value optimized out>)
at viewbase.cpp:68
#22 0xb5ea0331 in ~ViewSliders (this=0x8171c28,
__in_chrg=<value optimized out>) at viewsliders.cpp:59
#23 0xb5e9c7a5 in ~ViewOutput (this=0x8171c28, __in_chrg=<value optimized out>)
at viewoutput.cpp:35
#24 0xb67949ad in ~TQWidget (this=0x81700e8, __in_chrg=<value optimized out>)
at kernel/qwidget.cpp:996
#25 0xb689df81 in ~TQFrame (this=0x81700e8, __in_chrg=<value optimized out>)
at widgets/ntqframe.h:51
#26 ~TQWidgetStack (this=0x81700e8, __in_chrg=<value optimized out>)
at widgets/qwidgetstack.cpp:182
#27 0xb67949ad in ~TQWidget (this=0x816ff08, __in_chrg=<value optimized out>)
at kernel/qwidget.cpp:996
#28 0xb688b4e6 in ~TQTabWidget (this=0x816ff08,
__in_chrg=<value optimized out>) at widgets/qtabwidget.cpp:257
#29 0xb72e8119 in ~KTabWidget (this=0x816ff08, __in_chrg=<value optimized out>)
at /dev/shm/tdelibs/tdeui/ktabwidget.cpp:77
#30 0xb67949ad in ~TQWidget (this=0x816f578, __in_chrg=<value optimized out>)
at kernel/qwidget.cpp:996
#31 0xb5eab253 in ~KMixerWidget (this=0x816f578,
__in_chrg=<value optimized out>) at kmixerwidget.cpp:91
#32 0xb5e96cee in TQPtrList<KMixerWidget>::deleteItem (this=0x80b5710, d=0x0)
at /opt/trinity/include/ntqptrlist.h:153
#33 0xb6a22e81 in TQGList::clear (this=0x80b5710) at tools/qglist.cpp:704
#34 0xb5e96d1d in TQPtrList<KMixerWidget>::clear (this=0x80b5710)
at /opt/trinity/include/ntqptrlist.h:96
#35 0xb5e970bd in ~TQPtrList (this=0x80b5710, __in_chrg=<value optimized out>)
at /opt/trinity/include/ntqptrlist.h:73
#36 0xb5e9626f in ~KMixWindow (this=0x80b5620,
__in_chrg=<value optimized out>, __vtt_parm=<value optimized out>)
at kmix.cpp:103
#37 0xb5ebbc0b in ~KMixApp (this=0x80c2cb0, __in_chrg=<value optimized out>)
at KMixApp.cpp:36
#38 0xb5e93b3d in kdemain (argc=7, argv=0x80a8560) at main.cpp:67
#39 0xb787e474 in tdeinitmain (argc=7, argv=0x80a8560) at kmix_dummy.cpp:3
#40 0x0804e461 in launch (argc=<value optimized out>,
_name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=1,
envs=0x80a8a3d "DISPLAY=:0.0", reset_env=false, tty=0x0,
avoid_loops=false,
startup_id_str=0x80a8a4e "ovenbird;1341414944;536038;3110_TIME51073")
at /dev/shm/tdelibs/kinit/kinit.cpp:673
#41 0x0804f191 in handle_launcher_request (sock=9)
at /dev/shm/tdelibs/kinit/kinit.cpp:1240
#42 0x0804f89e in handle_requests (waitForPid=<value optimized out>)
at /dev/shm/tdelibs/kinit/kinit.cpp:1443
#43 0x08050db0 in main (argc=5, argv=0xbf934614, envp=0xbf93462c)
at /dev/shm/tdelibs/kinit/kinit.cpp:1909
Darrell
From the help handbook FAQ:
All TDE libraries are available under the LGPL making commercial software development for the TDE desktop possible, but all TDE applications are licensed under the GPL.
Is everything in TDE now fully GPL or do LGPL remnants remain?
Darrell
From the help handbook FAQ:
What kind of hardware do I need to run TDE?
To run TDE it is recommended that you have at least a pentium II processor, 64MB of memory and 500MB of free disk space for a basic installation. While TDE may run on slower configurations than this, performance can be severely impaired. Generally, if your computer runs an X-Server already with other desktop environments or window managers it's probably fast enough to run TDE.
I have tested Trinity on a PII with 448 MB of RAM. Barely usable and requires patience.
What are _realistic_ minimum hardware requirements?
I'm guessing Pentium III and 512 MB of RAM.
Thoughts? Experiences?
Darrell
A note to everybody interested: we have an etherpad checklist to track pre-release tasks. Please help with this preparation check list and missing items too.
http://trinity.etherpad.trinitydesktop.org/37
In the etherpad I attached a preliminary draft/template for a press release. Please add/edit as you see fit.
We need help to create a list of to whom we should send an email with the final press release. Please help populate that list.
Releasing R14.0.0 is a tad down the road yet, but if we peck away at these things then the final days won't be as hectic. :-)
I'm looking forward to the official release!
Darrell
All,
Also noted from the meeting, the current 3.5.13 will _not_ build on gcc 4.7.1.
There is _no_ reason not to port the patches to the 3.5.13 code base. All the
patches simply cleaned up the code from a syntax standpoint and will not impact
it building on earlier gcc releases. The closed bug 979 holds the collection of
gcc 4.7 patches that could easily be applied to 3.5.13 to make it gcc 4.7.1
compliant.
--
David C. Rankin, J.D.,P.E.
