tde-devels April 2013

devels@trinitydesktop.org

13 participants
66 discussions

Re: [trinity-devel] kicker and tdm issues with the current nightly builds
by Darrell Anderson 13 Apr '13

13 Apr '13

>I just tried the current "nightly" builds on a fresh Ubuntu >Quantal and >it seems there are still several major problems left. I'll >describe my >experience. > >When TDM started up, it gave the following error: >Cannot open theme file /opt/trinity/share/apps/kdm/themes/kubuntu- >trinity >There was also a process called tdm_greet using about 99,8% of my >CPU. >I then shut down tdm thought the init script. >I symlinked kdm to tdm in the above path and this problem went >away. I >got a nice login screen, but I was unable to type anything in it >at all! >I could click on things, but couldn't use my keyboard at all. > >I wanted to test a bit more, so I started another X11 server and >ran the >starttde script in it. This got me to the desktop, but with a >kicker >process using 100% of my CPU and I couldn't do anything till I did >a >kill -9 on it. > >Are these problems known or should I report them and try to get >more >information? How stable should the current nightly builds be >expected to be? > Yes, rings a bell. Look at some of these bug reports to see whether the problem looks the same: http://bugs.pearsoncomputing.net/buglist.cgi?quicksearch=ALL+100%25 Reopen one if applicable. :) Darrell

2 1

kicker and tdm issues with the current nightly builds
by Julius Schwartzenberg 12 Apr '13

12 Apr '13

Hi all, I just tried the current "nightly" builds on a fresh Ubuntu Quantal and it seems there are still several major problems left. I'll describe my experience. When TDM started up, it gave the following error: Cannot open theme file /opt/trinity/share/apps/kdm/themes/kubuntu-trinity There was also a process called tdm_greet using about 99,8% of my CPU. I then shut down tdm thought the init script. I symlinked kdm to tdm in the above path and this problem went away. I got a nice login screen, but I was unable to type anything in it at all! I could click on things, but couldn't use my keyboard at all. I wanted to test a bit more, so I started another X11 server and ran the starttde script in it. This got me to the desktop, but with a kicker process using 100% of my CPU and I couldn't do anything till I did a kill -9 on it. Are these problems known or should I report them and try to get more information? How stable should the current nightly builds be expected to be? Best regards, Julius

1 0

Re: [trinity-devel] Slavek Repository.
by Darrell Anderson 12 Apr '13

12 Apr '13

>Someone could say me how to have this repository on my own >repository ? (depot-trinity.dotriver.eu) > >Thanks for your help. Have you contacted Slavek? Darrell

1 0

Slavek Repository.
by Jean Milot 12 Apr '13

12 Apr '13

Hello, Someone could say me how to have this repository on my own repository ? (depot-trinity.dotriver.eu) Thanks for your help. Sincerely, Jean

1 0

Re: [trinity-devel] tdelibs FTBFS
by Darrell Anderson 09 Apr '13

09 Apr '13

On Tue, 09 Apr 2013 15:00:40 -0500 "Darrell Anderson" <darrella(a)hushmail.com> wrote: >tdelibs/tdecore/tdehardwaredevices.cpp:72:25: fatal error: >tqdbusdata.h: No such file or directory > >/opt/trinity/include/dbus-1-tqt/tqdbusdata.h exists. > >Changing -DBUILD_UPOWER=OFF resolves the failure but I want upower >support. I think the following patch solves the problem. I'm guessing by the tdehardwaredevices.cpp comments the upower includes should be used only when WITH_NETWORK_MANAGER_BACKEND=ON. Tim, please provide a sanity check. :) ==================================================== diff -urN tdelibs/tdecore/tdehardwaredevices.cpp tdelibs.new/tdecore/tdehardwaredevices.cpp --- tdelibs/tdecore/tdehardwaredevices.cpp 2013-04-05 22:37:52.000000000 -0500 +++ tdelibs.new/tdecore/tdehardwaredevices.cpp 2013-04-09 15:34:13.299824842 -0500 @@ -64,16 +64,17 @@ #include "config.h" #ifdef WITH_NETWORK_MANAGER_BACKEND - #include "networkbackends/network-manager/network-manager.h" -#endif // WITH_NETWORK_MANAGER_BACKEND +#include "networkbackends/network-manager/network-manager.h" -// uPower integration +// uPower integration for NETWORK_MANAGER_BACKEND #ifdef WITH_UPOWER - #include <tqdbusdata.h> - #include <tqdbusmessage.h> - #include <tqdbusproxy.h> - #include <tqdbusvariant.h> - #include <tqdbusconnection.h> +#include <tqdbusdata.h> +#include <tqdbusmessage.h> +#include <tqdbusproxy.h> +#include <tqdbusvariant.h> +#include <tqdbusconnection.h> +#endif // uPower integration + #endif // WITH_NETWORK_MANAGER_BACKEND // BEGIN BLOCK ==================================================== Darrell

1 0

tdelibs FTBFS
by Darrell Anderson 09 Apr '13

09 Apr '13

tdelibs/tdecore/tdehardwaredevices.cpp:72:25: fatal error: tqdbusdata.h: No such file or directory /opt/trinity/include/dbus-1-tqt/tqdbusdata.h exists. Changing -DBUILD_UPOWER=OFF resolves the failure but I want upower support. Darrell

1 0

Re: [trinity-devel] Panel colorize to match desktop color scheme
by Darrell Anderson 09 Apr '13

09 Apr '13

On Sun, 07 Apr 2013 12:37:53 -0500 "Darrell Anderson" <darrella(a)hushmail.com> wrote: >In the taskbar Appearance configuration, there is a check box >option "Colorize to match the desktop color scheme" that has >effect when the "Enable background image" option is enabled. > >On my system, when I select the default.png background image and >then enable the colorize option, the color is always a "sky blue." > >Regardless of what I change in KControl, I can't use any color >other than that sky blue. > >I want to use the default.png background, which has a gradient >look, but I want a darker panel. > >From where is this color derived? I tried browsing the code but am >clueless. Anybody? Darrell

1 0

TDE Status Report
by Timothy Pearson 07 Apr '13

07 Apr '13

Hi all, After discussions with the core development team, I have realised that I owe everybody a long overdue update regarding Trinity. I apologise for the relatively long term silence on these mailing lists. Like most people, I have to work in order to keep the lights on and the servers humming, and these commitments have taken time away from TDE. In particular over the past several months I have not had any spare time to dedicate to TDE, which is why most development (other than Slavek's tireless patching) had appeared to grind to a halt. The good news is that the work which had been taking most of my time is now easing up. I am currently diving into the bugtracker and am currently focused on getting R14.0.0 stabilized and ready to ship. Thanks to several other dedicated individuals involved in the Trinity project, progress has continued while I was away. R14.0.0 is looking good overall, and the R14.0.0 road map and long term TDE road maps have been updated on the Etherpad to more accurately reflect our goals. Despite my absence I am encouraged that TDE will continue to move forward. After some discussions with the core developers of TDE, I have begun to realise that the project's top priority from now on needs to be resolving bug reports. Other work will continue, including enhancements and feature requests, but bug quashing will need to remain a top priority to ensure TDE's survival and success. Secondly, Trinity has much in common with other "secondary" desktop environments. We never will have the developer power or userbase of KDE, GNOME, or Unity, but like our cousin "secondary" desktops, TDE has a vtal role to play in the free/libre software world. We should strive for excellence within our particular software design model, and not worry so much about what the Big Three desktops are doing at any given instant. My motivation for using and developing Trinity is to create a desktop that functions the way I think it should function. How people believe a desktop should function varies widely and this is why so many exist, along with many window managers. The Trinity philosophy does not embrace certain popular elements now available in other desktops, and those elements are unlikely to ever become a part of Trinity. That kind of focus is neither "bad" nor "good." We live in a large, varied world and there is plenty of room for all of these varying opinions and designs. This is also part of the method why free/libre software will succeed in the long run: by encouraging choice and freedom of opinions. Continuing Trinity is not about "us" versus "them"; instead, we are simply exercising our freedom of choice by improving our software as we see fit. Nothing more, nothing less. Thank you so much for being patient the past several months. I know it was difficult for many of you, but rest assured that work on TDE will pick up again, especially with your continuing support! Timothy Pearson Trinity Desktop Project

3 3

Panel colorize to match desktop color scheme
by Darrell Anderson 07 Apr '13

07 Apr '13

In the taskbar Appearance configuration, there is a check box option "Colorize to match the desktop color scheme" that has effect when the "Enable background image" option is enabled. On my system, when I select the default.png background image and then enable the colorize option, the color is always a "sky blue." Regardless of what I change in KControl, I can't use any color other than that sky blue. I want to use the default.png background, which has a gradient look, but I want a darker panel. From where is this color derived? I tried browsing the code but am clueless. Thanks. :) Darrell

1 0

Re: [trinity-devel] TDE Status Report
by Darrell Anderson 06 Apr '13

06 Apr '13

>As a tireless advocate KDE-3 user, I really want TDE has a long >life and continue to develop and improve in the future (short, >medium and long term). >I look for a desktop that is configurable and complete (not >simplistic as LXDE,...) and with characteristics centered in its >useful for users and no a sample of technic virtuosity (tablet >sense GNOME3/Shell/Unity, plasmoids KDE4,...). KDE3/TDE and XFCE4 >are the closest to this ideal of desktop focused on what users >really need to take advantage of your desktop (MATE is too simple, >more inline with LXDE), and KDE3/TDE most than XFCE4 (KDE3/TDE is >more complete in features). (My apologize for those who feel >uncomfortable with this statements, nor do I have any interest in >entering into a discussion about desktop environments). I suspect we all share similar sentiments for wanting to use Trinity. :) >As a reporter of a lot of bugs, my biggest reservations about TDE >has been little attention paid to solve bugs reported. I have find >frustrating that TDE have a number of bugs significantly greater >than its predecessor KDE3 (comparing TDE with Debian Etch and >Lenny's KDE-3, I tested TDE in Lenny, Squeeze and Wheezy). Several >months ago I volunteered to help with what little I can to do for >the development of TDE (basically contribute with Spanish >translations and report bug), but that I continue locating bugs >back down me to invest time in translations and more. If you >really are going to invest a lot of effort in TDE now to resolve >outstanding bugs, for me is the best possible news! Yes, this is good news and if all goes well, as the days go by we'll see a dramatic change in this area. I'm looking forward to this as well. Bugs have a nasty way of eroding a person's enjoyment of any software. The old adage about "death by a thousand paper cuts" rings true with software bugs. :) The project road maps indicate this new emphasis as well. So let's all take a deep breath, start hacking, and start testing the patches! :D By the way, to help with translations, Slavek is the best person to contact about that kind of help. Darrell

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels April 2013