SEO

[I posted this in LQ on yesterday without much luck]

I recently upgraded to kde 3.3 and have since been unable to start
kontact. Although I can start the individual components with no problem
starting kontact itself results in a very quick crash. I am running
Slackware 10.0, 2.4.26 and upgraded to 3.3 via swaret. I tried
downloading and installing kde-pim 3.3.1 from source and still get the
same result.

$ kontact --version
gives me:
Qt 3.3.3, KDE 3.3.1 and kontact 1.0.1

Starting kontact from a console gives me:

$ kontact (core): Loading Plugin: Mail
kontact (core): LIBNAMEPART: libkmailpart
kontact (core): Loading Plugin: Feeds
kontact (core): LIBNAMEPART: libakregatorpart
kontact (core): Loading Plugin: Contacts
kontact (core): LIBNAMEPART: libkaddressbookpart
KCrash: Application 'kontact' crashing...

and the backtrace is:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 2711)]
[KCrash handler]
#5 0x00000000 in ?? ()
#6 0x0805b756 in Kontact::MainWindow::loadPlugins ()
#7 0x08059e1b in Kontact::MainWindow::initObject ()
#8 0x0805e716 in Kontact::MainWindow::qt_invoke ()
#9 0x40f0d18c in QObject::activate_signal ()
from /usr/lib/qt/lib/libqt-mt.so.3
#10 0x4122ebca in QSignal::signal () from /usr/lib/qt/lib/libqt-mt.so.3
#11 0x40f2736d in QSignal::activate ()
from /usr/lib/qt/lib/libqt-mt.so.3
#12 0x40f2eb53 in QSingleShotTimer::event ()
from /usr/lib/qt/lib/libqt-mt.so.3
#13 0x40eb084f in QApplication::internalNotify ()
from /usr/lib/qt/lib/libqt-mt.so.3
#14 0x40eafe4e in QApplication::notify ()
from /usr/lib/qt/lib/libqt-mt.so.3
#15 0x40a43873 in KApplication::notify ()
from /opt/kde/lib/libkdecore.so.4
#16 0x40ea0085 in QEventLoop::activateTimers ()
from /usr/lib/qt/lib/libqt-mt.so.3
#17 0x40e5a97b in QEventLoop:rocessEvents ()
from /usr/lib/qt/lib/libqt-mt.so.3
#18 0x40ec2ba8 in QEventLoop::enterLoop ()
from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x40ec2a58 in QEventLoop::exec () from /usr/lib/qt/lib/libqt-mt.so.3
#20 0x40eb0aa1 in QApplication::exec ()
from /usr/lib/qt/lib/libqt-mt.so.3
#21 0x080593c5 in main ()

none of which means too much to me. I have googled and tried
bugs.kde.org but I've not really come across anything to point me in
the right direction. I would be grateful for any pointers.

regards,
--
Robert
Slackware 10.0 - stable
2.4.26

On Tue, 14 Dec 2004 13:54:25 +0000, Robert wrote:

> I recently upgraded to kde 3.3 and have since been unable to start
> kontact. Although I can start the individual components with no problem
> starting kontact itself results in a very quick crash. I am running
> Slackware 10.0, 2.4.26 and upgraded to 3.3 via swaret. I tried
> downloading and installing kde-pim 3.3.1 from source and still get the
> same result.
> $ kontact --version
> gives me:
> Qt 3.3.3, KDE 3.3.1 and kontact 1.0.1

hmm, kde 3.3.2 is out, how 'bout trying to upgrade first?
something probably is not installed correct. well, try to upgrade to kde
3.3.2, or just remove kde package kontact, and recompile it using slackware
build script (i.e from current...). you must edit it, change to correct
version, and possibly even compile it optimized for your platform.
if upgrading to kde 3.3.2 is your choice, consider backing the settings up
and removing packages (kde*, qt, arts...) and installing new ones.
linuxpackages can provide some nice kde packages.

Robert wrote:

> [I posted this in LQ on yesterday without much luck]
>
> I recently upgraded to kde 3.3 and have since been unable to start
> kontact. Although I can start the individual components with no problem
> starting kontact itself results in a very quick crash. I am running
> Slackware 10.0, 2.4.26 and upgraded to 3.3 via swaret. I tried
> downloading and installing kde-pim 3.3.1 from source and still get the
> same result.

Have you tried backing up your .kde directory and then deleting it? This
will help you tell if it is having a problem with a previous
configuration setting. If this fixes the problem then try looking for
the kontact config files in your .kde directory and just delete the old
one or you could try converting the old data by hand in a newly created
config file.

Richard

richard wrote:

> Have you tried backing up your .kde directory and then deleting it?
[...]

Thanks I tried that but it still crashed, I'm now downloading the 3.3.2
packages as suggested by Mad-Eye Moody to give them a try.

regards,
--
Robert
Slackware 10.0
2.4.26

On Wed, 15 Dec 2004 13:58:50 +0000, Robert wrote:

>> Have you tried backing up your .kde directory and then deleting it?
> [...]
> Thanks I tried that but it still crashed, I'm now downloading the 3.3.2
> packages as suggested by Mad-Eye Moody to give them a try.

well, even if it doesn't work, it is always polite to upgrade first, to
avoid possibility of bitching about some bug that has meanwhile been
corrected in newer version.
btw. while i was quite dissapointed with kde 3 when it first came out, now
the things are falling into it's place. it is getting faster and less
buggy... except, in my case, artsd. good thing is, it seems we wont see
more of it soon... i am of course speaking about kde 4.

Mad-Eye Moody wrote:

> On Wed, 15 Dec 2004 13:58:50 +0000, Robert wrote:

> well, even if it doesn't work, it is always polite to upgrade first,
> to avoid possibility of bitching about some bug that has meanwhile
> been corrected in newer version.

I have now and no it didn't work (maybe the next version of kontact will
do it...I'll wait and see). Mind you I didn't know it was at 3.3.2
anyway, I went via swaret --upgrade to current and was left with 3.3.1.
I think I'll do it all by hand from now on, I'll learn more about
what's involved that way.

> btw. while i was quite dissapointed with kde 3 when it first came out,
> now the things are falling into it's place. it is getting faster and
> less buggy... except, in my case, artsd. good thing is, it seems we
> wont see more of it soon... i am of course speaking about kde 4.

I quite like it. The desktop icons shifting at every new login bugged me
at first but I can live with it. I'll do the 4 upgrade myself.

regards,
--
Robert
Slackware 10.0 - stable
2.4.26

On Wed, 15 Dec 2004 21:23:47 +0000, Robert wrote:

> Mad-Eye Moody wrote:
>
>> On Wed, 15 Dec 2004 13:58:50 +0000, Robert wrote:
>
>> well, even if it doesn't work, it is always polite to upgrade first,
>> to avoid possibility of bitching about some bug that has meanwhile
>> been corrected in newer version.
>
> I have now and no it didn't work (maybe the next version of kontact will
> do it...I'll wait and see). Mind you I didn't know it was at 3.3.2
> anyway, I went via swaret --upgrade to current and was left with 3.3.1.
> I think I'll do it all by hand from now on, I'll learn more about
> what's involved that way.

you shouldn't use current packages on 10. if you want to use current
packages, you should upgrade WHOLE distro to current. or download one of
those unofficial current isos and install them.
if your base system is still 10.0, try packages from
http://www.linuxpackages.net/

>> btw. while i was quite dissapointed with kde 3 when it first came out,
>> now the things are falling into it's place. it is getting faster and
>> less buggy... except, in my case, artsd. good thing is, it seems we
>> wont see more of it soon... i am of course speaking about kde 4.
> I quite like it. The desktop icons shifting at every new login bugged me
> at first but I can live with it. I'll do the 4 upgrade myself.

well, for example, i have an old pentium mmx 200@225, and k3b was slow as
hell until i recompiled it (using modified slackbuild script from current)
for i586. now it feels much nicer, and works without a glitch.