tde-devels

devels@trinitydesktop.org

3 participants
3812 discussions

Failed hard disk problem
by Kristopher Gamrat 27 Feb '11

27 Feb '11

Hi guys, My hard disk seems to have failed, it started making random loud noises and is now refusing to boot. I am currently booted off a Live CD and chatting with an HP tech. Hopefully we can get the new hardware in quickly so I can continue with TDE and my other Linux projects. -- Kris "Piki" Ark Linux Webmaster Trinity Desktop Environment Packager

4 9

Re: [trinity-devel] IMPORTANT: taskbar icons zooming proposal get back
by Calvin Morrison 26 Feb '11

26 Feb '11

Definitely, As far as I am concerned everything should have the option to turn off. Any other customizations for the animation would be cool. Calvin Morrison

5 4

Amarok - Constructor Needs Fixing - osd.h:40:78 redundant ‘::QImage’
by David C. Rankin 26 Feb '11

26 Feb '11

Tim, all, Working with the new Amarok port, I've found another constructor issue: [ 1%] Building CXX object amarok/src/amarokcore/CMakeFiles/amarokcore-static.dir/amarokdcophandler.cpp.o cd /home/david/tblds/trinity-app-amarok/src/amarok/amarok/src/amarokcore && /usr/bin/c++ -DHAVE_CONFIG_H -DUSE_QT3 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -march=i686 -mtune=generic -O2 -pipe -include tqt.h -I/home/david/tblds/trinity-app-amarok/src/amarok/amarok/src/amarokcore -I/home/david/tblds/trinity-app-amarok/src/amarok -I/home/david/tblds/trinity-app-amarok/src/amarok/amarok/src -I/home/david/tblds/trinity-app-amarok/src/amarok/amarok/src/statusbar -I/opt/trinity/include -I/opt/qt/include -I/opt/qt/include/tqt -I/usr/include/taglib -fPIC -o CMakeFiles/amarokcore-static.dir/amarokdcophandler.cpp.o -c /home/david/tblds/trinity-app-amarok/src/amarok/amarok/src/amarokcore/amarokdcophandler.cpp In file included from /home/david/tblds/trinity-app-amarok/src/amarok/amarok/src/amarokcore/amarokdcophandler.cpp:36:0: /home/david/tblds/trinity-app-amarok/src/amarok/amarok/src/osd.h:40:78: error: cannot call constructor ‘QImage::QImage’ directly /home/david/tblds/trinity-app-amarok/src/amarok/amarok/src/osd.h:40:78: error: for a function-style cast, remove the redundant ‘::QImage’ make[2]: *** [amarok/src/amarokcore/CMakeFiles/amarokcore-static.dir/amarokdcophandler.cpp.o] Error 1 make[2]: Leaving directory `/home/david/tblds/trinity-app-amarok/src/amarok' make[1]: *** [amarok/src/amarokcore/CMakeFiles/amarokcore-static.dir/all] Error 2 make[1]: Leaving directory `/home/david/tblds/trinity-app-amarok/src/amarok' make: *** [all] Error 2 Aborting... Thanks for getting the port done! -- David C. Rankin, J.D.,P.E.

1 1

IMPORTANT: taskbar icons zooming proposal get back
by PICCORO McKAY Lenz 26 Feb '11

26 Feb '11

In the current KDE 3.4 and 3.5 brand, icon taskbar focus efects are only a highlight over them, in kde 3.2 and 3.1 brand, icon effects are icon zooming, (like MAC bar style) any body have the code to get back these? can be ported to actual kde 3.5 Trinity desktop? pleae, at leas tell how any! -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; http://shutendouji.net creador de massenkoh linux.

7 10

trick for adding new 'specification' to the wiki?
by David C. Rankin 25 Feb '11

25 Feb '11

Tim How do I create a 'specification' in: http://trinity.pearsoncomputing.net/wiki/bin/view/Specifications/Developmen… So it shows up with the query: *This is a list of all specifications that have been added to the Wiki.* %SEARCH{ "parent.name='%TOPIC%'" type="query" nonoise="on" format="[[$topic]]" separator="<BR>" }% I don't know quite what is meant by the term. Is it just a new page that lists something as a parent? I wanted to add: http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/ProposedSystem… and DefaultConfigUpdateRequests I have a few notes I have taken on default setting that need updating. Eg.: kcontol -> KDE Components -> File Manger -> Preview & Meta-Data -> Maximum File Size: 1.0 MB -> 6.0 MB; kate syntax etc.. What's the trick for adding specifications. Looking at http://trinity.pearsoncomputing.net/wiki/bin/view/Specifications/Developmen… I'm still not sure which one to press. (It's probably simple, but before I mess something up, I thought I would ask :) -- David C. Rankin, J.D.,P.E.

1 1

Fwd: Kdelibs patch for kernels > 2.6.36
by Ilya Chernykh 25 Feb '11

25 Feb '11

re-posting

1 0

test
by Ilya Chernykh 25 Feb '11

25 Feb '11

seems spam-filter does not allow me to post

1 0

Re: [arch-general] [trinity-devel] x86_64 kdesktop.kcrash [SOLVED - it is glibc]
by David C. Rankin 24 Feb '11

24 Feb '11

On 02/23/2011 01:38 PM, David C. Rankin wrote: > On 02/22/2011 06:41 PM, Allan McRae wrote: >> That prelink patch is very, very unlikely to cause the issue. It was also the >> only change between 2.13-3 and 2.13-4... As I pointed out, there are other >> distros using that patch without reported issue and it is now in glibc mainline >> so nothing is obviously wrong with it. Also, I have had no other crash reports >> since this update... >> >> >> I just looked back through this thread and your backtraces are all over the >> place. First it was an issue with libxcb, and then on a different VM it is >> somewhere completely different. What is difference across your VMs that you >> get consistent crashes in one but not the other? >> >> Allan > > The basic x86_64 Arch VMs are the SAME VM, just moved from one box to the other > (one on my laptop copied from my backup server where it was originally > installed). The packages are identical on the VMs except on the first I had > rebuilt libxcb and glibc with options(!strip) and CFLAGS="$CFLAGS -g". > > I will rebuild Trinity and update both VMs and then give updated .kcrashes for > each. If 2.13-3 works fine and 2.13-4 causes the crash, it just points to some > unintended consequence in the update. I'll rebuild, update both and report back. > But if Baho is also seeing something -- the plot thickens. > I have rebuilt libxcb with !strip and CFLAGS="$CFLAGS -g". I have rebuild glibc with !strip and CFLAGS="$CFLAGS -g" ...and... removed all the 'manual strip' calls from the bottom of the package() function. The kdesktop crash happens just as before, but now all the ? marks are gone from the backtrace. The new backtrace with full information is: http://www.3111skyline.com/dl/dt/trinity/arch/err/x86_64-archangel/kdesktop… before removing the 'manual strip' info from package() it was: http://www.3111skyline.com/dl/dt/trinity/arch/err/x86_64-archangel/kdesktop… This is with Virtualbox 3.2.10. So I upgraded to 4.0.4 to see if there was any change... There wasn't anything I noticed. Same kdesktop crash: http://www.3111skyline.com/dl/dt/trinity/arch/err/x86_64-archangel/kdesktop… I have no idea what the error means, but it looks like malloc is complaining about corruption? #8 0x00007f3550d27b96 in malloc_printerr (action=3, str=0x7f3550dd6a2e "malloc(): memory corruption", ptr=<value optimized out>) at malloc.c:6283 #9 0x00007f3550d2a4ad in _int_malloc (av=0x7f3551012ea0, bytes=16) at malloc.c:4396 #10 0x00007f3550d2c460 in __libc_malloc (bytes=16) at malloc.c:3660 I'll also follow up with the Trinity folks because I have just tried downgrading to glibc 2.13-3 and I'm still getting the error on x86_64. No issues with i686 though?? Any help pointing me in the right direction would be greatly appreciated :) -- David C. Rankin, J.D.,P.E.

3 3

x86_64 kdesktop.kcrash
by David C. Rankin 23 Feb '11

23 Feb '11

Tim, all, I am experiencing a kdesktop crash on x86_64 that I don't experience on i686. I have rebuilt kdelibs and kdebase with -DCMAKE_CXX_FLAGS=-g to hopefully get meaningful debug information. What happens is Trinity starts and you have the little splash where the icons light up showing what part of the desktop is loaded, it gets 1/2 way (just before the folder) and the desktop crash occurs. Trinity finishes loading and there are no icons on the desktop and no rt-click context menu or desktop background. Otherwise all the apps work (konqueror, kwrite, etc...) I have attached the kdesktop.kcrash file. Let me know if you need anything else. The svn revs for the packages installed are: trinity-arts 1221325-1.1 trinity-kdebase 1221325-1.0 trinity-kdelibs 1221343-1.1 trinity-kdevelop 1221336-1.0 trinity-kdewebdev 1221338-1.0 trinity-pyqt3 3.18.1-9 trinity-qt3 3.3.8-20 trinity-tqtinterface 1221325-1.0 -- David C. Rankin, J.D.,P.E.

3 23

Trinity on Arch - Intel Atom (new thread)
by David C. Rankin 23 Feb '11

23 Feb '11

Calvin wrote: On an Intel Atom it takes much longer than 5 minutes :P It broke again D: Do you think it is related to the environmental variables? Hmmm.. (1.) The very first thing I want to do is confirm that you have the following built and installed in this order, so show us 'pacman -Q | grep trinity': 15:34 supersff:~> pacman -Q | grep trinity # then I manually sorted trinity-qt3 3.3.8-20 trinity-pyqt3 3.18.1-9 trinity-tqtinterface 1221148-1 trinity-arts 1214641-1 trinity-kdelibs 1222098-1 Your stuck at 37% on trinity-kdebase 1221588-1 (2.) Please post the error you received after rebuilding with 'make VERBOSE=1' in the build() function. (it will provide a little more info that will help) Your environment for the build is set within the PKGBUILD file so it shouldn't matter what your existing shell environment is: export CMAKE_PREFIX_PATH=/opt/qt:/opt/trinity CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt:/usr/include/dbus-1.0:/opt/trinity/include:/opt/trinity/include/libkrandr export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/qt/lib/pkgconfig The build environment will be influenced by /etc/ld.so.conf.d/trinity-kdelibs.conf. So if you have trinity-kdelibs installed: (3.) confirm you have cat /etc/ld.so.conf.d/trinity-kdelibs.conf /opt/trinity/lib (4.) As root, run ldconfig if the trinity-kdelibs.conf so the linker cache magic is updated. What I want to confirm is that you are NOT trying to build on a system with KDE4/Qt4 or kdemod3 installed. That will screw up your build because of the conflicting libraries that cmake has trouble ignoring. So: (5.) look at: pacman -Q | grep "qt\|kde" If you have: qt 4.7.1-3 kdemod3-<anything> 3.5.10-1 kde<xyz>-<anything> 4.6.0-2 The build will fail. I don't know how a build between a normal i686, x86_64 and an Intel Atom will differ, but I haven't heard anything that says building on an Intel Atom won't work -- or that it *will* work for that matter. So let's take it step by step. Change into trinity-qt3 do 'makepkg -sf --noextract' to do a quick rebuild of the existing package and install it with 'sudo pacman -U trinity-qt3-<version>.xz. do the same thing for trinity-pyqt3 Change into trinity-tqtinterface - a simple makepkg -sf and install with 'sudo pacman -U trinity-tqtinterface-<version>.xz. Do the same thing for 'trinity-arts' and 'trinity-kdelibs'. After 'trinity-kdelibs' is installed - and run (as root) ldconfig. (6.) Change into trinity-kdebase - and restart the build with 'make VERBOSE=1' and post the output if it fails again. I'm scratching my head on this one. I've literally built Trinity 5-6 times in the past 2 days using the build script and gotten no errors during the make. So the PKGBUILDs work. If there is something special we need to do for the Intel Atom, then that's something we will have to look into. But, to get started, we need the information requesting in (1.) - (6.) above :) -- David C. Rankin, J.D.,P.E.

2 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels