SEO

#1 (**permalink**) 02-20-2008, 12:05 PM

Hi folks.

I just upgraded the KDE packages in my Slackware 10.2 box. What happens
to me is that when KDE exits kicker crashes. On the console I can read:
[...]
kicker: sighandler called
KCrash: Application 'kicker' crashing...
kicker: sighandler called
Unable to start Dr. Konqi
[...]
I don't even see the usual kcrash window with a normal user.

I'm submitting a bug to KDE but I wanted to share this with you and know
if the problem is known or happened to you. My installation is pretty
"pure": I did some slackpkg upgrade-all and these are the first packages
I manually update.

Bye,
Enrico.

#2 (**permalink**) 02-20-2008, 12:05 PM

Enrico Maria Crisostomo wrote:

> I'm submitting a bug to KDE but I wanted to share this with you and know
> if the problem is known or happened to you. My installation is pretty
> "pure": I did some slackpkg upgrade-all and these are the first packages
> I manually update.

I would wait for Pat to include new kde in -current. It seems that every
time kde.org folks have those slack packages, they never work as good as
Pat's.

#3 (**permalink**) 02-20-2008, 12:05 PM

Dominik L. Borkowski wrote:
> Enrico Maria Crisostomo wrote:
>
>
>>I'm submitting a bug to KDE but I wanted to share this with you and know
>>if the problem is known or happened to you. My installation is pretty
>>"pure": I did some slackpkg upgrade-all and these are the first packages
>>I manually update.
>
>
> I would wait for Pat to include new kde in -current. It seems that every
> time kde.org folks have those slack packages, they never work as good as
> Pat's.
Yes, I should have waited Pat's packages but... the temptation was
strong. I think I'm waiting some days to understand if the issue is
known and if it'll be fixed. If not, I'll rollback.

#4 (**permalink**) 02-20-2008, 12:05 PM

Enrico Maria Crisostomo wrote:

> kicker: sighandler called
> KCrash: Application 'kicker' crashing...
> kicker: sighandler called
> Unable to start Dr. Konqi
> [...]

I have the same error with KDE 3.4.2 on Slackware 10.2.

Regards

Lothar Leidner

#5 (**permalink**) 02-20-2008, 12:06 PM

Enrico Maria Crisostomo wrote

> I'm submitting a bug to KDE but I wanted to share this with you an
kno
> if the problem is known or happened to you. My installation i
prett
> "pure": I did some slackpkg upgrade-all and these are the firs
package
> I manually update
>
I would wait for Pat to include new kde in -current. It seems tha
ever
time kde.org folks have those slack packages, they never work as goo
a
Pat's

#6 (**permalink**) 02-20-2008, 12:06 PM

no problems here, although i did remove the old kde packages first and
deleted the kde directory in /opt first and went to init 3 before
installing kde-3.5, try removing ~/.kde and try again.

kde-3.5 works perfect for me

#7 (**permalink**) 02-20-2008, 12:06 PM

TuxRaider wrote:
> no problems here, although i did remove the old kde packages first and
> deleted the kde directory in /opt first and went to init 3 before
> installing kde-3.5, try removing ~/.kde and try again.
>
> kde-3.5 works perfect for me
>

Enjoy your new KDE. Unfortunately I did the same. Well, the 1st time I
just upgraded the pkgs. Then I removed them all, installed the new ones
and removed the .kde dir (I backed it up, obviously ;-)). The problem
appeared in any case. I didn't know how to solve it because in kde bug
db I found many cases of kicker failure very similar to the one I was
experiencing. For the moment I rolled back and now I've got no problem.

Thanx.

#8 (**permalink**) 02-20-2008, 12:06 PM

Enrico Maria Crisostomo wrote:

> [...]
> kicker: sighandler called
> KCrash: Application 'kicker' crashing...
> kicker: sighandler called
> Unable to start Dr. Konqi
> [...]

Do you have KMix running in the tray? If so, just close it before shutting
down. Maybe that helps.

--
Cheerz Lars

#9 (**permalink**) 02-20-2008, 12:06 PM

On Tue, 29 Nov 2005 16:11:56 +0000, Enrico Maria Crisostomo wrote:

> Hi folks.
>
> I just upgraded the KDE packages in my Slackware 10.2 box. What happens
> to me is that when KDE exits kicker crashes. On the console I can read:
> [...]

You shouldn't upgrade kde (upgradepkg, slackpkg, etc). You should first
uninstall the existent version and then install the new version.

-----------------------------------------------------------
Linux - the last service pack you'll ever need.
Registered with The Linux Counter. http://counter.li.org/
Slackware 10.1 Kernel 2.4.29 i686 (GCC) 3.3.4

#10 (**permalink**) 02-20-2008, 12:06 PM

Carlos wrote:
> On Tue, 29 Nov 2005 16:11:56 +0000, Enrico Maria Crisostomo wrote:
>
>
>>Hi folks.
>>
>>I just upgraded the KDE packages in my Slackware 10.2 box. What happens
>>to me is that when KDE exits kicker crashes. On the console I can read:
>>[...]
>
>
> You shouldn't upgrade kde (upgradepkg, slackpkg, etc). You should first
> uninstall the existent version and then install the new version.
>
> -----------------------------------------------------------
> Linux - the last service pack you'll ever need.
> Registered with The Linux Counter. http://counter.li.org/
> Slackware 10.1 Kernel 2.4.29 i686 (GCC) 3.3.4
>
>
>
Yes, the second time I removed and installed "ex-novo". What I don't
understand is "why" I shouldn't upgrade. Should I backup every KDE-app
data (as KOrganizer) and import it again every time I change KDE?
The box which gave me the error is my laptop and is a pretty young
Slackware installation.
But I have another two boxes at home, one of which is a Slackware
installation of the early 1996 which I continued upgrading!!! And never
never gave me problems! The only difference is that that box always
has been upgraded with official Slack releases.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

KDE 3.5 crashing on exit