Message: previous - next
Month: November 2011

Re: [trinity-devel] Unable to start TDE

From: "Timothy Pearson" <kb9vqf@...>
Date: Fri, 25 Nov 2011 19:34:50 -0600
>> > Looks like kded might be causing this. There is a
>> setting in KControl KDE
>> > Performance to disable system configuration startup
>> checks. Possibly that
>> > can be enabled to stop kconf_update.
>> >
>> I would suggest filing a bug report on this.  Mark the
>> priority to minor,
>> as this seems to only affect a small number of systems that
>> have a
>> third-party binary blob installed.
>> We will need a stack trace from gdb attached to the bug
>> report.  Best way
>> to do that is:
>> 1.) Wait for the process to hang
>> 2.) Switch to another console and find the PID of the hung
>> process
>> 3.) Start gdb with 'gdb'
>> 4.) Issue these commands to gdb:
>>  a.) attach <PID you found above>
>>  b.) bt
>> gdb should now spit out a backtrace that can be attached to
>> the bug
>> report.  You will of course need the debugging symbols
>> installed for the
>> backtrace to be of any use. ;-)
> I'm using the same packages I made available to everybody else: no
> debugging support. So I'll have to rebuild every package to get this. Well
> I guess at least kdelibs and kdebase.
> The DelayCheck feature had no effect.
> The only thing that works is configure X with vesa, start TDE, exit, and
> then restore Nvidia.
> Darrell

You should be fine with just the debugging symbols for kdelibs.