This bug is fixed in git. It was a libart issue. Will be there in R14

I'll track down the patch and see how things go.

Even easier is to pull the fixed libart package from this link: https://quickbuild.pearsoncomputing.net/~trinity/+archive/trinity-nightly-b…

If I get reports that this truly fixes the problem, and does not introduce any other problems, then I will update the 3.5.13 PPA for Debian and Ubuntu with the new library.

I assume you have restarted your machine?

If it still crashes please grab a backtrace.

On 01/14/2012 10:38 AM, Calvin Morrison wrote: I have the same problem on 2 different machines -- the only 2 installs of 3.5.13 I've done so far -- and it's been reported on the list at least twice since then. So I think it must be a common problem that lots of folks run into. I haven't tried the patch yet, but am about to do so. But most who get to the website, install Trinity, and have this problem won't know there's a patch -- they'll just see a great big bug that's still there, and uninstall Trinity and never try it again. So I think it's a really bad idea to leave it unfixed until R14.

On Saturday 14 January 2012 10:22:22 am Dan Youngquist wrote: The OP was building from source on a Wheezy system, this IS different than a user visiting the TDE website & installing the binaries on a Wheezy system. AFAIK, TDE3.5.13 is compiled on a Squeeze box, for the Debian stuff, and I would not expect them to necessarily work 100% on Wheezy. The install instructions are for Lenny & Squeeze. I have tested TDE3..5..13 & Wheezy in a Vbox instance and would not want to use on my production boxes. Caveat, I don't think running a Wheezy guest on a Squeeze host is a valid test though. To many kernel & Xorg cahnges, to name a few, some stuff just won't work.

On 14/01/2012 21:41, Timothy Pearson wrote: I'm a little confused now so please bear with me, or just ignore me as you choose :) I'm not at all sure where libart comes into my equation. I have libart-2.0-2 & libart-2.0-dev installed on my system, as debs, but not libart-lgpl. Nor does libart-lgpl appear in the stable sources, except as an almost empty sub-folder of konstruct/libs or in apt on either Squeeze or Wheezy.

On Saturday 14 January 2012 22:09:28 Mike Howard wrote: 3.5.13 is not intended for Wheezy, so will not work on it. It is at least reasonably stable on Squeeze. (I haven't been running it long enough nor used it often enough to vouch for complete stability!)

On Saturday 14 January 2012 22:21:45 Mike Howard wrote: Whilst accusing TDE of not being stable: <quote> </quote>

Mike, join the club with respect to learning. :) I joined this project before 3.5.12 was released. I have learned much! Part of the learning has been a challenge. At times frustrating. Yet I am learning leaps and bounds. I'm teaching myself C++ right now. Of late I am learning a thing or two about how cmake works. Although I have only superficial knowledge of C++, I have submitted more than a few patches. I think I am actually having fun, but am too old and stubborn to admit as much. ;) I'll add some observations that help me. None of these thoughts are directed to you. I'm just rambling out loud. * Software is a moving target. Frustratingly so. Testing known stable software in a known untested or unstable environment, means shouldering the responsibility to find solutions. Ask questions like crazy but let others know that they are not the crazy one. :) * Always check the bugzilla before posting bug or build related questions. * Always check the web before posting bug or build related questions. * Ask, ask, ask. * There are only a few people working to keep Trinity going. That can be frustrating at times so I always "count to 10" before posting anything to the lists. We all have lives, families, responsibilities. We all need a large dose of patience to keep this project running. * If no solutions, then post a bug report or enhancement request. I do. Often. :) * Everybody involved is a creature of limited knowledge. That is a hard lesson I learned about life in general. We can't assume everybody knows, even subject matter experts don't know everything. When things arise like akode not being in the repository, just ask. Chances are that adding the package is as simple as asking. * Trinity is a continuation of the KDE3 desktop style. Packages that were not part of the original KDE3 package suite need to be added to the Trinity repository. * Many of us use different distros. That means each of us tests according to our limited perceptions of how our distro works. (See --- we all are creatures of limited knowledge. :) ) That means some features don't get built or tested by others. Recently Tim has been adding a WITH_ALL_OPTIONS to the cmake converted packages. That is good because everybody involved should use that option at least a few times to test the overall build process, even when they don't want to use all features for their distro. * Occasionally a build feature or two will slip through the proverbial cracks with an automake to cmake conversion. Just let everybody know. An example is the current discussion about FAM/GAMIN support missing in kdelibs. Remember that everybody is a creature of limited knowledge and these things will happen. Oh, I almost forgot --- with respect to some of the build errors you just shared, the bugs about kipi-plugins and kdevelop have patches in the bugzilla. :) I had better get off my soap box now. Darrell

libart-2.0-2 is what you want installed, but it should be installed from the link that I posted earlier in this thread. Older versions of this package can cause a SIGABRT (a crash in layman's terms) due to a bug in this library. None taken. I can only say that in my experience, Squeeze is rock solid (with TDE as well), whereas Wheezy won't even compile TDE completely on armel due to mysterious segfaults in (non-TDE) core libraries. Additionally, Wheezy has some other problems that manifest as a lockup of build chroots. I have had it with Wheezy for now and won't support TDE on Wheezy until Debian at least has the guts to mark it stable. :-) And I fully understand that Stable isn't always stable, but at least instability reports will be taken seriously after that moniker is applied. I have personally experienced the frustration of waiting for Debian releases (hence my usage of Ubuntu on most of my servers), so I can understand why people are trying to "jump the gun" and use Wheezy before it is ready. On the other hand TDE has enough problems (just due to its size and complexity) that I don't need to be fighting prerelease distribution-specific problems on top of the bugs in the TDE source.

Thanks Tim, for your reply & your efforts on this excellent project. I agree, TDE is rock solid on Squeeze and I'm happy to continue using it, I just wanted to try TDE on Wheezy.

On 14/01/2012 22:54, Timothy Pearson wrote: My system is no longer in the same state. I re-installed libart from the link you provided and rebooted but it didn't cure it so I decided to rebuild the packages, with the new libart in place. I'm just about to re-try now. If the problem persists is there anything specific you would like me to do prior to collecting a backtrace?

Ok, backtrace attached. Mike.

Interesting. Are you building with libart support enabled or disabled? If libart is disabled I can easily see a potential crash. The attached patch for kdelibs *should* fix the crash. Please let me know if it does so that I can commit it to GIT. Tim

On 01/16/2012 02:30 PM, Mike Howard wrote: Cool. How soon will it make it into the repo?

The fix is in GIT as of hash e6b6f2e. What I am more interested in is why libart support was disabled in the first place; even though this may have fixed the crash, kiconloader cannot read SVG icons without libart.