This is a large package and build failures do not occur until well into the build process. Painfully slow. :) So let's move one step at a time. I would like to ignore previous koffice FTBFS reports. Start clean, now that the core packages all build and we have a known foundation and baseline.
The first failure errors seem to be related to wv2, an MS Word import package.
I'm still building packages on Slackware 12.2. That release came with wv2 0.2.3. Release 13.0 uses 0.2.3. The wv2 package was updated to 0.4.2 in Slackware 13.1.
Unless there is no choice, I believe 12.2 and 13.0 users should not have to update the wv2 package to build or install koffice. Certainly that might be required, but I prefer to work from the thesis that Trinity KDE should build and install on previous KDE 3.5.10 distros without such tinkering.
Previously we thought the failure was caused by an old version of wv2. Yet Lenny uses the same 0.2.3 version. Trinity koffice builds for that operating system. Thus we should proceed with the presumption the problem is not wv2 directly but the build process. As we have discovered the past several weeks, what builds on Debian does not always build on Slackware without some modifications. We don't know why but that is not important right now. :)
When I build koffice on 12.2 with wv2 0.2.3 installed, the first fatal build errors I receive:
document.cpp:393: error: 'const struct wvWare::Word97::BRC' has no member named 'cv'
I'm no C++ programmer, but seems some constants are not being used correctly or as expected or are not being declared correctly.
Note: Koffice builds successfully with no errors when wv2 is not installed.
I suspect only a few people will be interested in that version. Most people want basic MS Word import functions.
Log attached!
Darrell
I'm using my existing 3.5.10 ~/.kde profile. I mentioned this quirk previously.
When I start KDE 3.5.10, my konsole has a black background with tabs on the top. That is what I want.
When I start Trinity KDE, my konsole has a white background with tabs on the bottom.
Pretty good way to irritate new users migrating to Trinity from 3.5.10. :)
I have seen this behavior before --- in Debian Lenny. I never traced the cause. I guess now I will.
As the Trinity KDE sources were started from Debian Lenny rather than from the stock 3.5.10, I suspect Trinity is carrying some weird baggage from Debian Lenny.
I do not believe any user configuration files are being changed. My reasoning is I can exit Trinity, log in two seconds later in 3.5.10, and konsole is black with tabs on top.
I presume some *.desktop file somewhere defines the default konsole in Debian/Trinity as white background and tabs on bottom. I don't care for that default selection, but my user configuration should prevail.
Why are the user configuration files being ignored for konsole?
If I understand correctly:
1. Color schemes are controlled by schema files in /usr/share/apps/konsole.
2. The preferred user scheme is defined in ~/.kde/share/apps/konsole/shell.desktop.
3. If ~/.kde/share/apps/konsole/shell.desktop does not exist then the system default Konsole is used.
4. The default Konsole schema is defined in /usr/share/apps/konsole/linux.desktop and shell.desktop.
5. In both 3.5.10 and Trinity, the default schema in linux.desktop is Linux.schema.
6. Linux.schema is the same in both 3.5.10 and Trinity.
7. shell.desktop is the same in both 3.5.10 and Trinity.
8. I'm unsure how to read the schema files, but I think the background color in Linux.schema is black.
At this point I'm lost as to why Trinity opens konsole with a white background and tabs on the bottom.
Darrell
> I temporarily renamed the ~/.kde directory so Trinity would create a new
profile directory.
> Beauty is always subjective, but I think Trinity should change some of
the
> old die-hard KDE defaults. As you mentioned previously, Trinity is now
the
> upstream source, not KDE. You now are the man. Be bold. Be different. :)
I agree for the most part, but we must be careful not to be bold and
different in the KDE4 style. ;-). Sometimes minor changes are OK in small
quantities between releases, but usually large, sweeping changes will
start alienating the types of users that are interested in this project.
> So here are some thoughts about the default Trinity desktop.
> 1. As you seem keen on changing references from KDE to Trinity, you
might
> want to consider a new splash image. Likewise for your side image in the
K-Menu.
Done. Thank goodness for the GIMP!
> 2. I always found the KDE-Classic Icon Theme somewhat unpleasant. The
Crystal SVG icon set is popular and cleaner.
Agree; it looks like the default is already set to crystalsvg in the code
though?
> 3. I never understood the blind acceptance of four virtual desktops.
Most
> new users will appreciate two.
Sorry; I don't agree here. I can't imagine life without four desktops
(and I have two 21" screens per desktop)! While this usage case may be a
bit extreme, this feature is still a major productivity enhancer compared
to Window$/Mac, therefore I think it should be emphasized as much as
possible. Also on a more practical note, IIRC other Linux DEs use four
desktops by default.
If you want to create a separate default for Slackware that could be done
quite easily; I do that for the stock "cartoon" version of Kubuntu each
release.
> 4. With only two virtual desktops, the Small panel can be used as a
default.
Same with four; changed.
> 5. Digital clocks are geeky. Just choose Plain as the default.
Agree; changed.
> 6. Change the default desktop icon text to non-shadowed, white.
Not sure on this one; the non-shadowed icons blend in to certain desktop
wallpapers and this may confuse users over time. Any thoughts from other
list members?
> 7. Get rid of the bouncing mouse cursor. :) Yeah, I mentioned that
already. I'm making a not-so-subtle point. The thing is obnoxious. Stupid,
> Dumb. Irritating. Annoying. Childish. Unprofessional. I greatly
appreciate
> any distro I test where the devs have changed the default mouse pointer
to
> Non Busy. And quite a few devs have done that too.
Fully agree; I thought I already got rid of it though?
> 8. None of the desktop device icons are enabled. You went through the
effort to create many new useful icons, so why not add them and set enable
> Device Icons as the default?
Agree; changed.
> 9. I don't understand the fetish and dumbing down with the default view
in
> Konqueror with icons. Set the default view to Tree View, and Show Hidden
Files. Treat users like adults and not kids. :)
Sorry, disagree. I like the intuitive icon view myself, and even by their
name, hidden files are supposed to be hidden! ;-) I can see too many
"oops, I just dragged and dropped my .<critical system file> who knows
where and now I can't use my computer" type complaints cropping up.
> 10. A bug: when I select the desktop Web Browser Device Icon, I receive
an
> error message: Unknown host default.browser. The message box has an OK
button but the message box disappears by itself in about 1.5 seconds.
Insufficient time to actually read without repeating the process a few
times.
Fixed.
> 11. A bug: Selecting the My Documents Device Icon results in an error
because the ~/Documents directory does not exist. I personally would get
upset if any software created such a directory on my system. On the other
> hand, I think when a person explicitly enables that device icon then
such
> a directory should get created. No, not quite. I think when a person
enables that directory a pop-up should appear asking for the path to that
> directory. The default would be ~/Documents, but the user can change the
text in the popup text box. I don't consider that a feature request
needing to be added after your feature freeze. I consider this behavior a
> bug.
Fixed; the shortcut now queries XDG for the documents directory path.
> 12. I'm glad you selected to display both software names and
descriptions
> in the K-Menu. I always empathize with new users and they need both.
Flip
> a coin, but I prefer Description (Name) rather than Name (Description).
My
> belief is that most people are looking to solve a task and a description
first helps toward that goal. Especially since so many developers have
given their apps names that provide no clue to the apps purpose.
The problem is that descriptions can change; e.g. become more descriptive.
Change the first letter in the description and the user has to hunt
through the entire list to find the same application again.
> 13. So you added the option to use a Kickoff style K-Menu. Nice
> programming touch. Really! You'll never see me use the Kickoff though.
I'm
> just too old to change some habits. :)
> 14. Place the Exit/Lockout applet buttons on the default kicker. Many
people use the buttons and they provide a familiar method to exit for new
> users.
Agree; changed.
> 15. Trinity did not create a new ~/.kde3 directory, but honored $KDEHOME
and created a new ~/.kde!
> I hope this helps!
Sure does!
Update kdelibs and kdebase to SVN revision 1176514 or above, recompile
both, and re-test everything. I believe I have repaired most of the bugs,
including the Klipper icon (thanks to your latest message regarding applet
mode, which allowed me to reproduce the bug here).
Let me know if anything fishy shows up in testing, or if I forgot to
address an issue!
Thanks,
Tim
At this point I believe the reason I don't see those HPLIP messages when I start 3.5.10 is 3.5.10 is not fully xdg compliant. If I'm wrong then I have no other explanation why I never see those messages in 3.5.10. That I was seeing the messages in Trinity and not in 3.5.10 was a red herring.
Yet Trinity is not fully compliant either. :(
Test Results:
In my 3.5.10 system, with my testing account, I removed the hplip.desktop file from ~/.config/autostart. I started 3.5.10 and there were no messages about HPLIP.
I have a second KDEDIR directory. I purposely assigned 700 permissions to that directory to prevent any *.desktop files there from overriding KDE defaults. Again no HPLIP messages.
Yet the service does not try to run in my 3.5.10 system. What did I do long ago in 3.5.10 to prevent HPLIP from starting?
Maybe nothing?
After much testing and web searching I started to wonder whether the original KDE 3.5.10 is broken with respect to xdg autostart requirements. Not a far stretch to believe since we have seen that 3.5.10 does not recognize or honor the ~/.config/autostart directory.
Trinity is almost fully xdg compliant but not quite. I see the HPLIP messages because Trinity is correctly reading the contents of /etc/xdg/autostart.
Is Trinity recognizing the ~/.config/autostart directory? Yes. In the past I used the ~/.config directory for non-KDE apps. Once in a while I run tests in Xfce. Xfce does honor the autostart directory. Trinity does too. I know this because when I start Trinity for the first time with no kde profile, a new profile gets created. My conky display starts. The only place Trinity can find that directive is the ~/.config/autostart directory.
I'm concluding that Trinity honors the ~/.config/autostart directory.
But does not recognize exceptions.
When I run Trinity and I have the ~/.config/autostart/hplip-systray.desktop file set to Hidden=True, I still see the HPLIP messages in the log. This seems to be a bug with respect to full xdg autostart compliance.
Initially I thought the Hidden=true directive in ~/.config/autostart/hplip.desktop only hides the tray icon and does not necessarily stop the service from trying to run. But that is not the effect I see in Xfce. When I set Hidden=False in the ~/.config/autostart/hplip-systray.desktop file, I see the same HPLIP messages in the log. When I set Hidden=True I no longer see the HPLIP messages. Thus the file in ~/.config/autostart fully controls whether the service in /etc/xdg/autostart actually starts.
As another test, in 3.5.10, I copied the /etc/xdg/autostart/hplip-systray.desktop file to ~/.config/autostart. No related messages found in the log. I exited KDE and moved the file to ~/.kde/Autostart. I then saw the same messages in the log.
SUMMARY: 3.5.10 is not fully xdg compliant and that is why I see no related messages. Trinity is mostly xdg compliant and that is why I see the messages in the log. Yet for some reason Trinity is not honoring the Hidden=True directive in the ~/.config/autostart/hplip-systray.desktop file and I still see the HPLIP messages when I should not.
Xfce does this as expected. Perhaps the Xfce code might help with getting Trinity fully xdg compliant. I have the source code here. Tell me what to look for and I can forward appropriate snippets.
As promised here comes some other compile errors probably caused by gcc-4.5:
In file included from /opt/qt/include/tqimage.h:32:0,
from /opt/trinity-3.5.12/include/kaboutdata.h:24,
from main.cpp:21,
from libkdeinit_ksmserver_la.all_cpp.cpp:2:
/opt/qt/include/qimage.h: In member function bool
QImageTextKeyLang::operator<(const QImageTextKeyLang&) const:
/opt/qt/include/qimage.h:61:61: warning: suggest parentheses around &&
within ||
In file included from libkdeinit_ksmserver_la.all_cpp.cpp:4:0:
shutdowndlg.cpp: In constructor
KSMShutdownFeedback::KSMShutdownFeedback():
shutdowndlg.cpp:78:36: error: cannot call constructor QImage::QImage
directly
shutdowndlg.cpp:78:36: error: for a function-style cast, remove the
redundant ::QImage
shutdowndlg.cpp:79:39: error: cannot call constructor QImage::QImage
directly
shutdowndlg.cpp:79:39: error: for a function-style cast, remove the
redundant ::QImage
make[3]: *** [libkdeinit_ksmserver_la.all_cpp.lo] Errore 1
make[3]: Leaving directory
`/usr/src/KDETrinity/20100918/kdebase-20100918/ksmserver'
In file included from /opt/qt/include/tqimage.h:32:0,
from /opt/trinity-3.5.12/include/kaboutdata.h:24,
from main.cpp:24,
from krandrtray.all_cpp.cpp:2:
/opt/qt/include/qimage.h: In member function bool
QImageTextKeyLang::operator<(const QImageTextKeyLang&) const:
/opt/qt/include/qimage.h:61:61: warning: suggest parentheses around &&
within ||
In file included from krandrtray.cpp:65:0,
from krandrtray.all_cpp.cpp:3:
krandrbindings.cpp: In constructor
KRandRSystemTray::KRandRSystemTray(QWidget*, const char*):
krandrbindings.cpp:31:2: error: cannot call constructor
KShortcut::KShortcut directly
krandrbindings.cpp:31:2: error: for a function-style cast, remove the
redundant ::KShortcut
krandrbindings.cpp:31:2: error: cannot call constructor
KShortcut::KShortcut directly
krandrbindings.cpp:31:2: error: for a function-style cast, remove the
redundant ::KShortcut
In file included from krandrtray.all_cpp.cpp:3:0:
krandrtray.cpp: In member function void
KRandRSystemTray::slotCycleDisplays():
krandrtray.cpp:508:6: warning: unused variable lastIndex
krandrtray.cpp:512:9: warning: unused variable s
krandrtray.cpp: In member function void
KRandRSystemTray::findPrimaryDisplay():
krandrtray.cpp:663:6: warning: unused variable lastIndex
krandrtray.cpp: In member function void
KRandRSystemTray::slotOutputChanged(int):
krandrtray.cpp:783:11: warning: unused variable output_id
krandrtray.cpp:785:9: warning: unused variable s
make[3]: *** [krandrtray.all_cpp.o] Errore 1
make[3]: Leaving directory
`/usr/src/KDETrinity/20100918/kdebase-20100918/kcontrol/randr'
In file included from kpackage.cpp:51:0,
from kpackage.all_cpp.cpp:2:
/opt/trinity-3.5.12/include/kedittoolbar.h:271:1: warning:
KEditToolbarWidget has a field KEditToolbarWidget::m_inactiveList whose
type uses the anonymous namespace
/opt/trinity-3.5.12/include/kedittoolbar.h:271:1: warning:
KEditToolbarWidget has a field KEditToolbarWidget::m_activeList whose
type uses the anonymous namespace
In file included from kpackage.cpp:52:0,
from kpackage.all_cpp.cpp:2:
/opt/trinity-3.5.12/include/kmimemagic.h:156:62: warning: KMimeMagicResult
is deprecated (declared at /opt/trinity-3.5.12/include/kmimemagic.h:47)
/opt/trinity-3.5.12/include/kmimemagic.h:170:58: warning: KMimeMagicResult
is deprecated (declared at /opt/trinity-3.5.12/include/kmimemagic.h:47)
/opt/trinity-3.5.12/include/kmimemagic.h:186:89: warning: KMimeMagicResult
is deprecated (declared at /opt/trinity-3.5.12/include/kmimemagic.h:47)
/opt/trinity-3.5.12/include/kmimemagic.h:191:27: warning: KMimeMagic is
deprecated (declared at /opt/trinity-3.5.12/include/kmimemagic.h:102)
/opt/trinity-3.5.12/include/kmimemagic.h:197:22: warning: KMimeMagicResult
is deprecated (declared at /opt/trinity-3.5.12/include/kmimemagic.h:47)
/opt/trinity-3.5.12/include/kmimemagic.h:200:22: warning: KMimeMagic is
deprecated (declared at /opt/trinity-3.5.12/include/kmimemagic.h:102)
In file included from /opt/qt/include/qdragobject.h:50:0,
from /opt/qt/include/tqdragobject.h:32,
from /opt/trinity-3.5.12/include/kurldrag.h:24,
from kpackage.cpp:53,
from kpackage.all_cpp.cpp:2:
/opt/qt/include/qimage.h: In member function bool
QImageTextKeyLang::operator<(const QImageTextKeyLang&) const:
/opt/qt/include/qimage.h:61:61: warning: suggest parentheses around &&
within ||
In file included from kpackage.all_cpp.cpp:4:0:
packageDisplay.cpp: In member function void
packageDisplayWidget::openBindingWith(QListViewItem*):
packageDisplay.cpp:392:56: error: cannot call constructor KURL::List::List
directly
packageDisplay.cpp:392:56: error: for a function-style cast, remove the
redundant ::List
In file included from kpackage.all_cpp.cpp:8:0:
options.cpp: In member function void Options::apply_slot():
options.cpp:322:85: warning: suggest parentheses around && within ||
In file included from kpackage.all_cpp.cpp:23:0:
kissInterface.cpp: In constructor KISS::KISS():
kissInterface.cpp:84:20: warning: unused variable paramsInst
kissInterface.cpp:88:22: warning: unused variable paramsUninst
make[3]: *** [kpackage.all_cpp.o] Errore 1
make[3]: Leaving directory
`/usr/src/KDETrinity/20100918/kdeadmin-20100918/kpackage'
I solved theese by following the compiler advice and successfully compiled
base packages plus kdeadmin. Again I'm not sure this is the right way to
deal with the errors, anyway hope it helps.
Regards,
Leandro
--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it: http://www.email.it/f
Sponsor:
Paghe e stipendi, consulenza e collocamento, tutto con Emailpaghe! Provalo
gratuitamente fino al 31/12/2010
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=10682&d=20100918
Hi,
first of all thanks to Timothy and all the people involved for keeping alive
my favourite desktop!
Now on to the business: I'm trying to build Trinity on a custom Linux From
Scratch system and experienced a few compiling errors, here are some caused
by the --enable-gcc-hidden-visibility switch:
In file included from /opt/qt/include/tqimage.h:32:0,
from kpixmap.cpp:26,
from libkdefx_la.all_cpp.cpp:2:
/opt/qt/include/qimage.h: In member function bool
QImageTextKeyLang::operator<(const QImageTextKeyLang&) const:
/opt/qt/include/qimage.h:61:61: warning: suggest parentheses around &&
within ||
In file included from libkdefx_la.all_cpp.cpp:5:0:
kimageeffect.cpp: At global scope:
kimageeffect.cpp:4739:13: warning: unused parameter bpp
kimageeffect.cpp:4739:13: warning: unused parameter has_alpha
In file included from libkdefx_la.all_cpp.cpp:7:0:
kstyle.cpp:155:1: warning: KStylePrivate has a field
KStylePrivate::menuHandler whose type uses the anonymous namespace
In file included from libkdefx_la.all_cpp.cpp:7:0:
kstyle.cpp: In member function virtual void
KStyle::drawComplexControl(QStyle::ComplexControl, QPainter*, const
QWidget*, const QRect&, const QColorGroup&, QStyle::SFlags, QStyle::SCFlags,
QStyle::SCFlags, const QStyleOption&) const:
kstyle.cpp:1134:7: warning: suggest explicit braces to avoid ambiguous
else
kstyle.cpp: At global scope:
kstyle.cpp:2267:19: error: expected unqualified-id before string constant
make[2]: *** [libkdefx_la.all_cpp.lo] Errore 1
make[2]: Leaving directory
`/usr/src/KDETrinity/20100918/kdelibs-20100918/kdefx'
solved by moving the KDE_EXPORT define in kdefx/kstyle.cpp as follows:
extern "C"
void KDE_EXPORT kde_kstyle_set_scrollbar_type_windows( void* style )
networkstatustestservice.all_cpp.o: In function
`ServiceIface_stub::registerNetwork(QString const&,
NetworkStatus::Properties)':
networkstatustestservice.all_cpp.cpp:(.text+0xff1): undefined reference to
`operator<<(QDataStream&, NetworkStatus::Properties)'
collect2: ld returned 1 exit status
make[2]: *** [networkstatustestservice] Errore 1
make[2]: Leaving directory
`/usr/src/KDETrinity/20100918/kdelibs-20100918/networkstatus'
solved by adding KDE_EXPORT to the << and >> operators in
networkstatus/networkstatuscommon.{h,cpp} and removing the const qualifier.
Not sure if this is the correct way.
./.libs/libkdeinit_konqueror.so: undefined reference to
`StatusBarNetworkStatusIndicator::StatusBarNetworkStatusIndicator(QWidget*,
char const*)'
./.libs/libkdeinit_konqueror.so: undefined reference to
`StatusBarNetworkStatusIndicator::init()'
collect2: ld returned 1 exit status
make[3]: *** [konqueror] Errore 1
make[3]: Leaving directory
`/usr/src/KDETrinity/20100918/kdebase-20100918/konqueror'
make[2]: *** [all-recursive] Errore 1
./.libs/libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_invoke(int, QUObject*)'
./.libs/libkdeinit_kicker.so: undefined reference to `typeinfo for
KickoffSearch::Plugin'
./.libs/libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_property(int, int, QVariant*)'
./.libs/libkdeinit_kicker.so: undefined reference to `typeinfo for
KickoffSearch::KickoffSearchInterface'
./.libs/libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::KickoffSearchInterface(QObject*,
char const*)'
./.libs/libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::staticMetaObject()'
./.libs/libkdeinit_kicker.so: undefined reference to
`KickoffSearch::Plugin::staticMetaObject()'
./.libs/libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_cast(char const*)'
./.libs/libkdeinit_kicker.so: undefined reference to `vtable for
KickoffSearch::KickoffSearchInterface'
./.libs/libkdeinit_kicker.so: undefined reference to
`KickoffSearch::KickoffSearchInterface::qt_emit(int, QUObject*)'
collect2: ld returned 1 exit status
make[4]: *** [kicker] Errore 1
make[4]: Leaving directory
`/usr/src/KDETrinity/20100918/kdebase-20100918/kicker/kicker'
solved by adding KDE_EXPORT to StatusBarNetworkStatusIndicator,
KickoffSearchInterface and KickoffSearch::Plugin.
There were some other undefined references regarding RandRScreen and
RandRDisplay classes but I deleted my logs...
Some more build errors will come in next mail.
Regards,
Leandro
--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it: http://www.email.it/f
Sponsor:
Prova subito Emailpaghe, e' in prova gratuita sino al 31 dicembre 2010
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=10679&d=20100918
Ouch.
No kicker/panel.
None.
Nada.
Root and non-root. Existing kde profile and new profile.
No off to the side. Just gone. Non-existent.
Desktop right-click works as does Alt-F2 and hotkeys.
========================================
startkde still needs a file test. Here is a snippet from the log:
/usr/bin/startkde: line 402: /usr/local/kde-mods/share/kgtk/preload: No such file or directory
I sent a patched version several messages ago. Probably got overlooked in the shuffle. :)
========================================
startkde line 110
echo "startkde: User ID is $UID. Setting KDEROOTHOME to $KDEHOME."
For consistency, you likely want to change
startkde:
To
[startkde]
========================================
You updated the splash. Might want to look at kpersonalizer too. Still uses the phrase KDE 3.5.12.
========================================
Whenever I start Trinity with a new profile, I always receive the following messages:
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateUzL0lc.tmp:1
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateFG2sia.tmp:1
Only with the very first log with a new profile. Yes, goes away with subsequent starts, but looks ugly.
========================================
I have seen this message a few times throughout the day but inconsistently. Shows up and sometimes doesn't.
QClipboard: Unknown SelectionClear event received.
========================================
Artifacts in konqueror toolbar grabbers still present.
Still trying to discover additonal info about the Klipper icon in the panel.
I removed the icon from the panel. I exited Trinity/X and restarted. Then I added the Klipper applet to the panel.
Same huge size.
I fiddled with the new system tray icon resizing. The krandr icon changes sizes but the klipper icon does not.
I tried the same thing with the panel icons. The other panel buttons changed size but the klipper icon did not.
I'll offer a wild guess there is a conflict of some sort with the klipper code and the system tray resizing code.
Again, this happens only with the root user. Perhaps there is something similar happening as with the KDEROOTHOME problem.
On a possible good note, I can't seem to replicate the "Klipper is already running!" message. I removed a file from ~/.kde/share/apps/klipper. Can't say for sure whether that file was corrupted in some way.
Darrell
Not a bug, but not a feature request either. Minor enhancement and a usability issue.
Right-click the panel and select Add applet.
The subsequent dialog box is squished. Peculiar looking.
Same behavior in 3.5.10. Thus, Trinity likely inherited the same behavior.
The old benchmark was being usable in 640x480, but I think 800x600 is acceptable nowadays. Regardless, the dialog box could be a bit longer to provide better readability.
Darrell
In the past, the desktop files in 3.5.x notoriously were poorly maintained. Starting a fresh KDE profile resulted in many error mesages in .xsession-errors about improperly configured desktop files. Usually errors about incorrect mimetypes and service types.
I have not done any conclusive tests yet with Trinity, but have those types of errors received attention during Trinity development?
Darrell
