tde-devels

devels@trinitydesktop.org

10 participants
3780 discussions

by Darrell Anderson

Using recent GIT sources, does DrKonqi work correctly to create backtraces? When I run crashtest in 3.5.10, DrKonqi creates a backtrace. In TDE all I get is the following message: "This backtrace appears to be of no use. This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash." This worked some time in the past (I am the one who patched tdebase so crashtest would build). My build scripts all use --enable-debug=full for automake and -ggdb for cmake. The build logs show that the packages are compiling with those flags and the increased package sizes are further evidence. Yet I can't create a backtrace through DrKonqi. The crashtest binary should be sufficient to test DrKonqi. Would somebody running a recent GIT please confirm whether they can create a backtrace with DrKonqi? Thanks. Darrell

12 years, 11 months

Note about Qt3 in Debian

by Julius Schwartzenberg

I came across this through my G+ feed: http://ekaia.org/blog/2012/05/20/long-due-to-do-item-removal-of-qt3-from-de… I do not think this will affect Trinity much with its own (T)Qt3 packages, but it still seems relevant. I can imagine it may make it slightly harder to get Trinity into Debian in the future. Best regards, Julius

12 years, 11 months

Konqueror SIGABRT with latest GIT

by Darrell Anderson

Tim, Today I am receiving a SIGABRT crash when I try to start Konqueror. I don't have debugging symbols enabled with this build. My builds from May 14 late afternoon are okay. Therefore the possible candidates for the crash: d3a9d561 2012-05-15 [tdelibs] Add the ability to force read-only configuration file access in a TDE application Force tde-config to use read-only access b45b4bd7 2012-05-15[tdebase] Fix KHTML smooth scrolling control center option 9a948c1a 2012-05-15 [tdebase] Disable keyboard shortcuts for file location moving, as they did not work properly and have very little practical use b0fa10df 2012-05-15 [tdebase] Add drag and drop to kate file list in manual mode 46a657f7 2012-05-15 [tdebase] Add the ability to reorder documents in kate Intermixing tdelibs and tdebase packages between the two dates is inconclusive. The only combination that runs fine is using both packages from May 14. I'll have to debug by reverting patches one-by-one unless you have a hunch what happened. Darrell

12 years, 11 months

xsession error log

by Jay

I've noticed many errors in my .xsession-error.log. The main culprit is: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3600134 The opcode is usually 19 or 20. The errors are mainly caused from gtk applications written in gtkdialog with many other entries being from tdeinit. [tdeinit] Got EXT_EXEC 'kfmclient' from launcher. [tdeinit] PID 4739 terminated. At the moment i am softlinking .xsession-errors to /dev/null in my environment. An ugly fix. The log fills quite fast. Is this just bad coding of gtk apps? Kind Regards, Jay

12 years, 11 months

LibreOffice TDE integration

by Timothy Pearson

FYI: http://lists.freedesktop.org/archives/libreoffice/2012-May/031676.html Tim

12 years, 11 months

R14 idea

by Darrell Anderson

Just an idea, nothing more: ============================================ Trinity Community, Those of us involved with developing and supporting the Trinity Desktop Environment want the next release to be the best yet. With that goal we ask you to help us by participating in some simple polls. 1. Which bugs listed in the bug tracker are your favorites as paper cut candidates? A paper cut candidate is bug which in and of itself is insignificant and might be trivial to fix, but when combined with similar bugs creates an overall impression of an unfinished, buggy piece of software. 2. Which bugs listed in the bug tracker are your Most Hated Bugs? This is the type of bug that hampers productivity, causes data corruption or loss, or is something that doesn't work as expected or intended. 3. Which enhancement requests in the bug tracker do you want to see in the next Trinity release? We will strive to resolve the top 20 vote getters in each of the first two lists and the top five vote getters for the third list. No priorities are needed. Just provide us your list. Limit the first two lists to 20 items per list per person and the third list to five items per person. Note: Only bug reports and enhancement requests listed in the bug tracker are eligible for these polls. Note: Build issues are not candidates because we expect and intend to resolve those issues one way or another before the next release. Bug tracker: http://bugs.pearsoncomputing.net/ At the bottom of the page the bug tracker contains links for commonly used search criteria. To list all reports filed, use the ALL search criteria. Any list can be sorted by selecting the appropriate column heading link. Thank you for helping and thank you for supporting and using Trinity! ============================================ Post this or a similar request to all mail lists asking community members to vote. I believe we have work remaining before we can consider a soft freeze for R14 preparations. These three polls would help us considerably with that preparation. Not to mention providing a good way for community involvement. Get users involved in a nominal way. The resulting corresponding resolutions show users they that have a voice and matter to us. The bug tracker provides a priority mechanism, but these polls help us refine those priorities. We all are itching for the next official release. Tentatively that release is scheduled for May, this month. Let's ignore hard deadlines and do this right. A serious effort now to make R14 as bug free as practical means fewer bugs for the next cycle. Not to mention more time for us all just to use and enjoy Trinity. For many of us summer is around the corner and all of us look forward to a more leisurely pace. If we truly polish the next release then we all can do just that. :-) Again, just an idea. Darrell

12 years, 11 months

Build KDE3 on gcc 4.7 to test kwrite issue?

by David C. Rankin

Darrell, Do you have the capability to build Kde3 on gcc 4.7 to test the kwrite issue. I don't know if you have the same capabilities to build KDE as you do TDE, but since I don't and since I haven't gotten a confirmation from the SuSE folks, I'm curious if building 3.5.10 will show the same crash. If you have the sources and build scripts for it, it is probably worth doing just to see if we can eliminate the tqtinterface code as a possible source. If it is the same crash in KDE as it is in TDE, then tqtinterface should be able to be eliminated. Just a couple of stray thoughts that might add another piece of info to the puzzle. If it is tdelibs, then I'm not sure that it is even worth doing, but think about it. Also, Tim, have you been able to set up a gcc 4.7 build environment yet? I know you have another 26,539 things to do, but the more eyes we get on this thing, the sooner we will find the culprit. If anyone else has thought of another test they would like to see, then just let me know, happy to do it here -- as long as I know what to do. Thanks. -- David C. Rankin, J.D.,P.E.

12 years, 11 months

Re: [trinity-devel] kwrite crash - it is tdelibs! (tqt3-46, tdelibs-47, tdebase-46 => crash)

by Timothy Pearson

> Tim, Darrell, All, > tdelibs is the package that causes the kwrite/kate/etc.. crash when > built on > gcc 47. The backtrace is good this time and points to: > at (i=<optimized out>, this=<optimized out>) at > /opt/tqt3/include/ntqstring.h:641 > 641 { return i < d->len ? d->unicode[i] : TQChar::null; } That is valuable information! This is also not an issue of ignoring build warnings, as there are none which relate to the failing code. If you can, please try the attached patch. It will probably do nothing, but there is half a chance that gcc 4.7 did not inline the functions where gcc 4.6 did, *potentially* causing a crash due to misuse of parameters passed by reference. Tim

12 years, 11 months

Resizing kcontrol module windows launched from kcmshell

by Darrell Anderson

How are kcontrol module window sizes determined when launched from kcmshell? For example, 'kcmshell audiocd' opens to a window size of 765,778 and 'kcmshell media' opens to a window size of 765,512. I get the feeling the width of 765 is hard-coded somewhere but I can't find anything. I'd like to know how the width number is fixed, but at the moment I am more interested in how the height is determined for each window. Thanks. Darrell

12 years, 11 months

Fw: Re: Adding to Registered OnlyShowIn Environments

by Darrell Anderson

I'm forwarding the following message. Please follow either link and pay attention to the table. :-) Darrell --- On Fri, 5/11/12, Vincent Untz <vuntz(a)gnome.org> wrote: > From: Vincent Untz <vuntz(a)gnome.org> > Subject: Re: Adding to Registered OnlyShowIn Environments > To: xdg(a)lists.freedesktop.org > Date: Friday, May 11, 2012, 7:13 AM > Le lundi 23 avril 2012, à 09:14 > +0200, Vincent Untz a écrit : > > Le samedi 21 avril 2012, à 07:44 -0700, Darrell > Anderson a écrit : > > > Greetings, > > > > > > I am writing on behalf of the members of the > Trinity Desktop Environment (TDE) project. > > > > > > TDE is a continuation of the KDE 3.5 desktop. > > > > > > We want to add TDE to the list of Registered > OnlyShowIn Environments: > > > > > > http://standards.freedesktop.org/menu-spec/latest/apb.html > > > > > > Please let me know how to proceed further. > > > > Do you prefer "TDE" or "Trinity" to be registered? > > > > Any objection? If no, this will go in the spec next > week. > > I was away for a bit, so it took more than a week ;-) But > it's done now: > http://specifications.freedesktop.org/menu-spec/menu-spec-latest.html#onlys… > > I also updated desktop-file-utils. > > Vincent > > -- > Les gens heureux ne sont pas pressés. > _______________________________________________ > xdg mailing list > xdg(a)lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xdg >

12 years, 11 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels