tde-devels

devels@trinitydesktop.org

3 participants
3807 discussions

Error Message When Opening Panels Control Center
by Darrell Anderson 15 Nov '11

15 Nov '11

In 3.5.13, when I select Desktop/Panels in the Control Center or from the T-Menu, I receive the following error message: ================================================ Error - KDE Control Module ================================================ Error loading theme image file. /opt/trinity/apps/kicker/wallpapers/default.png /opt/trinity/apps/kicker/wallpapers/default.png OK ================================================ The message box title bar needs some branding attention. :) I have an /opt/trinity/share/apps/kicker/wallpapers/default.png. Is this error message a build error? I notice in the cmake files I might need to specify DATA_INSTALL_DIR (kde_datadir in autotools). If yes, then is that location $PREFIX/share? Or is this an error in the panel configuration sources? Thanks. Darrell

1 1

patch fails with qt 3.3.8d
by Robert Xu 14 Nov '11

14 Nov '11

Hi all, Usually I get the already applied message for patches, however I seem to have something different now: This patch fails completely. Can anyone make heads or tails out of it, or should this patch be significant enough to keep or throw away? Patch #28 (fix-key-release-event-with-imm.diff): --- src/kernel/qapplication_x11.cpp +++ src/kernel/qapplication_x11.cpp @@ -3294,11 +3294,7 @@ // filtering opportunity first to ensure all input methods work // properly regardless of application design. -#ifndef QT_NO_IM_EXTENSIONS if( keywidget && keywidget->isEnabled() && keywidget->isInputMethodEnabled() ) { -#else - if( keywidget && keywidget->isEnabled() ) { -#endif if( ( event->type==XKeyPress || event->type==XKeyRelease ) && sm_blockUserInput ) // block user interaction during session management return TRUE; @@ -5220,11 +5216,12 @@ } else { key = (int)(long)keyDict->find( keycode ); if ( key ) - if( !willRepeat ) // Take out key of dictionary only if this call. + if( !willRepeat && statefulTranslation ) // Take out key of dictionary only if this call. keyDict->take( keycode ); long s = (long)textDict->find( keycode ); if ( s ) { - textDict->take( keycode ); + if( statefulTranslation ) + textDict->take( keycode ); ascii = (char)(s-256); } } --- src/kernel/qwidget_x11.cpp +++ src/kernel/qwidget_x11.cpp @@ -2699,11 +2699,10 @@ { QInputContext *qic = 0; -#if !defined(QT_NO_IM_EXTENSIONS) if ( isInputMethodEnabled() ) { +#if !defined(QT_NO_IM_EXTENSIONS) qic = icHolderWidget()->ic; #else - { // icHolderWidget is always topLevelWidget QTLWExtra *topdata = icHolderWidget()->topData(); qic = (QInputContext *)topdata->xic; @@ -2754,10 +2753,8 @@ */ void QWidget::createInputContext() { -#if !defined(QT_NO_IM_EXTENSIONS) if( !isInputMethodEnabled() || QApplication::closingDown() ) return; -#endif QWidget *icWidget = icHolderWidget(); #ifndef QT_NO_IM -- later daze. :: Robert Xu :: rxu.lincomlinux.org :: protocol.by/rxu

1 0

Trinity 3.5.13 doesn't find login splash theme
by Darrell Anderson 14 Nov '11

14 Nov '11

I'm testing 3.5.13. I opened the Control Center to change the startup splash theme. The theme is installed in /usr/share/apps/ksplash/Themes. File permissions are the same as every other system around here. The theme does not appear in the pick list of themes. I tested this with both a migrated (and cleaned) KDE3 profile and a virgin Trinity profile. Same result. Logging in as root is the same, so more than likely this is not a permissions problem. Any ideas? Darrell

1 1

3.5.13 Usability -- KDE 4 Takes Over
by Darrell Anderson 14 Nov '11

14 Nov '11

I'm testing my 3.5.13 packages. I'm running Slackware 13.1 in a virtual machine. Full stock installation. KDE 4 is installed. All KDE 3.5.10 packages have been removed. Every time I started Trinity the Akonadi server dialog appeared, the desktop changed to KDE 4 Desktop View, and the KDE 4 file indexer started. Long story short: I traced the problem to the Trinity startkde script. The default 3.5.13 Trinity startkde script incorrectly sets the $KDEDIRS environment variable and includes the /usr directory. That means KDE 4 apps start when starting Trinity. The $KDEDIRS environment variable is intended to be a user defined variable and should not be set globally. Further review of startkde shows duplication of code and some code in the KDEHOME section that makes no sense. Even if somebody explains why $KDEDIRS should be set in startkde, somebody still needs to explain why /usr is in that path. I will file a bug report. Before I do that I would appreciate comments and observations from other people regarding startkde. Other people must be running into this same problem. :) Thanks! Darrell Darrell

2 4

Will Trinity and KDE 3.5.10 Coexist?
by Darrell Anderson 14 Nov '11

14 Nov '11

If both desktop environments are built to install to different locations, can the desktops coexist peacefully or will there be problems? I know Trinity is supposed to coexist peacefully with KDE 4 so why not KDE 3 too? Has anybody successfuly tried this? I ask because I need to test my packages on a real machine after testing in a virtual machine. My only candidates for this testing have KDE 3.5.10 installed. I want to know ahead of time what kind of problems I might or will experience. Thanks! Darrell

2 1

Branding issue
by Darrell Anderson 14 Nov '11

14 Nov '11

In 3.5.13 KPersonalizer, System Behavior (second screen) the option KDE (TM) should be TDE (TM). Let me know if this is easily fixed in SVN/GIT. If not I'll file a bug report. Darrell

4 6

Wiki Heading
by Darrell Anderson 14 Nov '11

14 Nov '11

The wiki heading says KDE3/Trinity Desktop Environment. We should change that to only Trinity Desktop Environment. Darrell

1 0

Improving the Web Site and Adding Documentation
by Darrell Anderson 14 Nov '11

14 Nov '11

Do we have access to the old KDE web site pages? The Trinity web site provides no package description pages like the old KDE web site. I think we could use such pages. I'm no HTML expert but if we have an archive of the old kde web site I am willing to help massage the old pages into Trinity pages. Second, I noticed when building the 3.5.13 packages from tarballs that some of the old /usr/doc files were not part of the binary packages. Fair enough, most of that was stale and useless. However, there is a readme file in every package and the file says nothing more than to visit the wiki to learn how to build each package. The wiki is lacking in specific package information. I can update the wiki but I don't know what is relevant. That is, I had to heavily patch a few 3.5.13 packages in Slackware, but I don't know whether that is true for other distros. I had to do some serious head scratching to get some packages to build and having specific information would have helped. Perhaps an improved approach is to create a wiki page for each package with instructions for building. That documentation should be duplicated in the package readme file. Many of the pages will be repetitive because they require nothing different or unique. Or create individual pages only for those packages that require different build options. Certainly any package that requires one or more patches needs that information. Lastly, long ago I mentioned the idea of a Trinity user's guide. Something that allows multiple output options, such as HTML, and PDF. Packagers could add a desktop icon to the generic user profile and first time users would see the icon right away. Several distro maintainers do this and I always liked the idea. The user's guide would be part of the Trinity web site too. I am willing to help. I'm not demanding anything :) --- just trying to start conversations. I welcome that GIT and bug quashing have priority for 3.5.14. I want that to succeed --- especially the bug quashing. :) I think documentation is something that can grow and mature on the side. Do we need a plan? Darrell

6 13

OpenBSD port proposition
by Vadim Zhukov 13 Nov '11

13 Nov '11

Hello all. I'm currently working on porting fresh KDE 4 to OpenBSD (there were attempts earlier but without that much success) and currently seeking for the ways to make KDE 3 (which OpenBSD already have in ports, and it's working well) and upcoming KDE 4 co-exist. Not so long (shame on me!) ago I was notified about the existence of Trinity Desktop. One of the main goals of Trinity, as I've seen, is the co-existence of KDE 3 and KDE 4 too. This way I became interested in porting Trinity to OpenBSD, replacing KDE 3. So the question is: will you accept patches for OpenBSD? Some "desktop" projects turn Linux-only nowadays, and nobody want to constantly maintain all the patches that obviously will be needed for porting on a different O/S with different kernel and specifics. From my own side, I can help in porting to Qt4 and, of course, in making Trinity and KDE 4 build and run simultaneously. Thanks in advance for your reply, and all the best to Trinity. :) -- WBR, Vadim Zhukov

7 12

Using KDM
by Darrell Anderson 13 Nov '11

13 Nov '11

I would appreciate comments/observations from people who have tested using Trinity KDM to run KDE 4 and KDE 4 KDM to run Trinity. Thanks. Darrell

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels