Bug#237213: SIGSEGV on start of konqueror after upgrade

To: Benjamin Mesing <bensmail@gmx.net>
Cc: 237213@bugs.debian.org
Subject: Bug#237213: SIGSEGV on start of konqueror after upgrade
From: Dominique Devriese <dominique.devriese@student.kuleuven.ac.be>
Date: Wed, 10 Mar 2004 17:05:47 +0100
Message-id: <[🔎] 87r7w0offo.fsf@student.kuleuven.ac.be>
Reply-to: Dominique Devriese <dominique.devriese@student.kuleuven.ac.be>, 237213@bugs.debian.org
In-reply-to: <[🔎] 1078917783.731.18.camel@benjamin> (Benjamin Mesing's message of "Wed, 10 Mar 2004 12:23:03 +0100")
References: <[🔎] 1078917783.731.18.camel@benjamin>

Benjamin Mesing writes:

> Package: konqueror Version: 4:3.2.1-1 Severity: important Tags: sid

> After the upgrade to KDE 3.2 (from 3.1.4) starting konqueror fails
> with the following output

Have you upgraded kde while a kde session was running ?  This is not a
good idea.  Do you still get the crash after restarting your kde
session ?

cheers
domi

Reply to:

Follow-Ups:
- Bug#237213: SIGSEGV on start of konqueror after upgrade
  - From: Benjamin Mesing <bensmail@gmx.net>

References:
- Bug#237213: SIGSEGV on start of konqueror after upgrade
  - From: Benjamin Mesing <bensmail@gmx.net>

Prev by Date: Bug#236750: known bug, fix is known too.
Next by Date: Processed: known bug, fix is known too.
Previous by thread: Bug#237213: SIGSEGV on start of konqueror after upgrade
Next by thread: Bug#237213: SIGSEGV on start of konqueror after upgrade
Index(es):
- Date
- Thread