tde-devels

devels@trinitydesktop.org

2 participants
3855 discussions

Mystery Konqueror Icon
by Darrell Anderson 21 Sep '10

21 Sep '10

In the Trinity konqueror, lower right corner, is an icon that looks like a common electrical device receptacle plug. What is that icon for? I clicked and nothing happened. Darrell

2 4

kdebindings python support
by Darrell Anderson 21 Sep '10

21 Sep '10

I'm working my way toward building python support for kdebindings. I have sip and pyqt3 built and installed. I went searching for some build instructions for python-kde3 when I saw something in the svn tree called pykdeextensions. Do I need to install both packages or just python-kde3? If only python-kde3, then when and why would I want to build pykdeextensions? Darrell

1 0

FTBFS kdelibs + lua 5.1
by Serghei Amelian 20 Sep '10

20 Sep '10

Hello, Somebody tried to compile kdelibs against LUA 5.1? On my system fail with this error: kdelibs/kate/part/kateluaindentscript.cpp:249: error: 'luaL_newstate' was not declared in this scope [...] kdelibs/kate/part/kateluaindentscript.cpp:290: error: 'lua_version' was not declared in this scope Unfortunately, LUA 5.0 was removed from gentoo portage, so I cannot test with this version. Thanks -- Serghei

2 2

kdelibs config warning
by Darrell Anderson 20 Sep '10

20 Sep '10

I see the following warning in the kdelibs configure output: config.status: WARNING: 'kdecore/kde-config.cpp.in' seems to ignore the --datarootdir setting Probably harmless but should be fixed? Darrell

1 0

WARNING: DCOPReply
by Darrell Anderson 20 Sep '10

20 Sep '10

Updated to SVN 1177573. I now see these messages. Root and non-root users. WARNING: DCOPReply<QCString>: cast to 'TQCString' error WARNING: DCOPReply<QString>: cast to 'TQString' error WARNING: DCOPReply<>: cast to 'bool' error WARNING: DCOPReply<>: cast to 'bool' error WARNING: DCOPReply<QCString>: cast to 'TQCString' error WARNING: DCOPReply<QString>: cast to 'TQString' error Darrell

1 1

Quirks With New Trinity Profiles
by Darrell Anderson 20 Sep '10

20 Sep '10

Testing a new Trinity profile. I tested these quirks three ways: skipping kpersonalizer, configuring kpersonalizer for minimum effects, and accepting all defaults in kpersonalizer. ============================================ The panel height is preconfigured to Small. When the new Trinity profile opens, the height is indeed Small. Yet when I open the panel configuration box the size says Normal. ============================================ In /usr/share/config.kcfg/kickerSettings.kcfg I have panel set to 1) no mouseover effects, 2) no icon activation effects, and 3) no tooltips. I create those settings when I build the package and the kickerSettings.kcfg gets installed with my preferred settings. When I open the configuration box the first time all three settings are enabled, which I can confirm with straightforward usability tests of the desktop. ============================================ In /usr/share/config.kcfg/kdesktop.kcfg I have shadow text off and white text on. With a new profile the text is black with shadows. If I accept the defaults from kpersonalizer, then the text is white but shadows remain on. ============================================ Default icon theme is now Crystal SVG. Crystal SVG is the icon theme when I skip kpersonalizer or accept the defaults. When I select minimum desktop effects in kpersonalizer, the icon theme is KDE Classic. ============================================ With minimum desktop effects or defaults in kpersonalizer, the bouncing mouse cursor reappears, despite the default being non-busy. Seems the only way to get the default non-busy cursor is to skip kpersonalizer. Darrell

1 0

New Trinity Profile Messages
by Darrell Anderson 20 Sep '10

20 Sep '10

When I start Trinity for the first time, which creates a new profile, I see these messages: Invalid entry (missing '=') at /tmp/kde-root/kconf_updateDxWEba.tmp:1 Invalid entry (missing '=') at /tmp/kde-root/kconf_updateVC8cVa.tmp:1 Occurs for both root and non-root users. The messages seem to occur only with a new Trinity profile and only with the first run of Trinity. The messages likely are caused because the cache, socket, and tmp directories used by KDE/Trinity do not yet exist and the code is trying to create those directories. That part makes sense, but the error message indicates something like a typo similar in the code. Darrell

1 0

X Error: BadWindow
by Darrell Anderson 20 Sep '10

20 Sep '10

X Error: BadWindow (invalid Window parameter) X Error: BadAccess (attempt to access private resource denied) For as long as I can remember, anybody using KDE has seen these superfluous messages in their xsession log. The messages are annoying. FWIW, occasionally I start Xfce for some oddball testing and I don't see the messages. I'm guessing the problem is unique to legacy KDE code. Is there something specific in the KDE/Trinity code that causes X to respond with those messages? You have impressed me many times with your ability to patch the old sloppy KDE code. I think if you could solve this problem you would add one dandy looking feather to your cap! Darrell

1 0

First Trinity 3.5.12 Usability Test
by Darrell Anderson 20 Sep '10

20 Sep '10

My first usability test of Trinity was in a virtual machine. Trinity loaded just fine --- but ignored all of my previous ~/.kde profile settings. Hey! What? :) Not to mention the evil bouncing mouse cursor! Okay, I can solve that irritant when I build the package. What happened with my desktop? First clue: Trinity is using ~/.kde3 rather than ~/.kde. Yet my $KDEHOME environment variable is set to ~/.kde. Hmm. Where is this being ignored or overridden? Yes, I can rename ~/.kde to ~/.kde3. But I should not have to. Trinity should honor my $KDEHOME variable. First suspect: /usr/bin/startkde. I have some proposed patches for startkde, but that can wait for another thread. Nope. Not the culprit because I exited KDE, restored my ~/.kde profile, renamed the new startkde, and restored my old startkde. When I started X, Trinity again created ~/.kde3 and ignored my ~/.kde profile and $KDEHOME variable.. What is hard-coded to create and use ~/.kde3? A .desktop file somewhere? Been a looooong time since I wandered around with the KDE startup sequence. Second, there are folder icons on the desktop for every directory in the root level. They are not device icons and I don't know how to disable that effect. I also have lost my previous desktop icons. Third, something is starting the HP system tray. I remember that being an annoyance three or four years ago, but I don't remember how to stop that. There is a file in /etc/xdg/autostart, but there is one in my office system too and the tray does not start there. Fourth, There are messages in xsession-errors that seem to indicate something accessing samba, a service I don't have started in the virtual machine. Fifth, the Klipper tray icon is huge and does not display completely in the tray --- the top and bottom of the icon are missing. I don't seem to find anything in kcontrol/icons. Sixth, the color of my konsole changed from black to white. I realize some of the problems might be cause by using a 3.5.10 profile, but then again perhaps not. I'm suffering a bit from new culture shock. 3.5.12 is not 3.5.10. I did not expect so many configuration changes, however. :) If I have to start with a new profile and rebuild the profile I have been using for several years I am likely to become manic depressive. Suddenly I feel very tired!

3 19

libpng warnings
by Darrell Anderson 20 Sep '10

20 Sep '10

Open the Configure Panel dialog box. Select the Appearance option. The following (.xsession-errors) messages appear immediately. libpng warning: Ignoring gAMA chunk with gamma=0 libpng warning: Ignoring attempt to set negative chromaticity value libpng warning: Ignoring attempt to set cHRM RGB triangle with zero area Repeatable with an existing 3.5.10 or new Trinity profile. The messages probably are generated by libpng, but only happens when opening Appearances. I thought the problem was related to using button backgrounds, but selecting "Default" causes the messages too. I checked and see the error messages in 3.5.10 too. Thus, some legacy code is causing these messages in Trinity. Based on the context of the messages I suspect something in the Trinity/KDE code is not accessing the libpng libraries correctly. Darrell

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels