tde-devels

devels@trinitydesktop.org

3753 discussions

Re: [trinity-devel] kicker and tdm issues with the current nightly builds

by Darrell Anderson

>I just reported the bugs. If there is anything else I can do, just >let me know! I added the reports to the etherpad road map. Those types of problems are over my head. Tim or Slavek likely will investigate and will need you to help test and debug of course. :) Darrell

11 years, 9 months

Re: [trinity-devel] kicker and tdm issues with the current nightly builds

by Darrell Anderson

>I just looked through them, but the only corresponding thing I can >find >is that one process uses a lot of CPU. Otherwise the problems do >not >seem similar. > >What would be the best way to provide more information? Am I >really the >only one who has these issues with the Ubuntu packages? If the problem is preventing normal usage, then file a Blocker bug report. If the system remains usable but abnormally intolerable, file the report as Critical. Either way I'll add the report to the R14.0.0 etherpad road map. Darrell

11 years, 9 months

Re: [trinity-devel] Kick-off Launcher

by Darrell Anderson

On Sat, 13 Apr 2013 12:16:12 -0500 "Calvin Morrison" <mutantturkey(a)gmail.com> wrote: >Hidey Ho Neighbors, > >Haven't been around much lately, but school is letting out soon >and it seems progress is picking up for R14. Welcome back. I hope school is going well. :) If you want to help with the R14.0.0 release, we have a road map in etherpad listing the specific bug reports we want to resolve for the release: http://trinity.etherpad.trinitydesktop.org/39 Please don't add anything to the etherpad list without a discussion. :) Don't delete anything either and instead use the strikeout format method to tag a bug report as resolved. I believe some of the bug reports in the etherpad are assigned to you and you might want to look at those. No related kickoff menu bug reports are part of the R14.0.0 road map. Scratch that itch if necessary, but help with the other bug reports is much appreciated. :) Darrell

11 years, 9 months

Re: [trinity-devel] Kick-off Launcher

by Darrell Anderson

>Haven't been around much lately, but school is letting out soon >and it >seems progress is picking up for R14. > >Kick-Off has been causing problems on and off for my desktops >since >inception. I did quite a bit of work last year to simplify it, but >now >the hard-drive parsing (the most ugly piece of code i've seen) has >caused problems again. This is due to a questionable amount of >parsing >doesn't seem to work correctly everwhere. > >I digress. > >A good solution would be to 1) remove kickoff since it's unlikely >that >it is used, and doesn't keep in the style of trinity and port the >cool >features of kickoff into the original kicker panel, if there are >any. >2) integrate tde's hw library with kickoff so isn't relying on a >bad >hack > >I'd be willing to do both, what do you guys think? I've used the kickoff style menu in both Trinity and KDE4. Personally I don't like the kickoff menu but my opinion counts as only one vote. Considering the bugginess of the Trinity version, and overall Trinity philosophy, I prefer dropping the feature. Posing the same question to the user's mail list probably is a good idea before deciding. If we decide to keep kickoff then I request we add a build option to tdebase/CMakeLists.txt so packagers can have the final say. Darrell

11 years, 9 months

Re: [trinity-devel] kicker and tdm issues with the current nightly builds

by Darrell Anderson

>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

11 years, 9 months

kicker and tdm issues with the current nightly builds

by Julius Schwartzenberg

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

11 years, 9 months

Re: [trinity-devel] Slavek Repository.

by Darrell Anderson

>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

11 years, 9 months

Slavek Repository.

by Jean Milot

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

11 years, 9 months

Re: [trinity-devel] tdelibs FTBFS

by Darrell Anderson

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

11 years, 10 months

tdelibs FTBFS

by Darrell Anderson

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

11 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels