[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#549106: marked as done (libqt4 segfault during kde startup splashscreen)

Your message dated Sat, 10 Oct 2009 20:06:49 +0200
with message-id <20091010180649.GA5642@pryan.ekaia.org>
and subject line Re: Bug#549106: libqt4 segfault during kde startup splashscreen
has caused the Debian Bug report #549106,
regarding libqt4 segfault during kde startup splashscreen
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
549106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549106
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kde4
Version: 5
Severity: serious

After upgrading to latest kde4 libqtcore4 segfault during kde
startup in splashscreen.
KDE startup is very slow.
I get a window to report the kde bug but kde is on its knees and I
don't know how to save the trace.

If I install the -dbg package startup becomes faster and there is no
segfault.

I know the report is very poor but I don't know how to improve it.

I'm running amd64 on an Intel Core 2 Duo.

thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it

--- End Message ---
--- Begin Message --- 
Hi Ivan,

On Wed, Sep 30, 2009 at 09:30:49PM +0200, Ivan Sergio Borgonovo wrote:
> Package: kde4
> Version: 5
> Severity: serious
> 
> After upgrading to latest kde4 libqtcore4 segfault during kde
> startup in splashscreen.
> KDE startup is very slow.
> I get a window to report the kde bug but kde is on its knees and I
> don't know how to save the trace.
> 
> If I install the -dbg package startup becomes faster and there is no
> segfault.
> 
> I know the report is very poor but I don't know how to improve it.
> 
> I'm running amd64 on an Intel Core 2 Duo.
> 

First of all, you reported your bug against a meta package that does not exist 
since april, so your bug has been rotting in the BTS reported against not 
existant package until a few days ago somebody realized and re-asigned.

I am afraid with a bug report so poor there is not much that can be done.
Also you did not mention from what version to what version where you upgrading,
that would have been like the minimun information to give. Or if you upgraded
something else at the same time.
If you are still having issues, please try to track where the problem is
then report it.
When you are unsure about what is going on your system, you always can try 
first writing an email to the users mailing lists and seek for help there.

Ana

--- End Message ---
Reply to: