[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 56733] Crash on starting juk
From:       Zack Rusin <zack () kde ! org>
Date:       2003-04-02 1:53:53
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=56733     




------- Additional Comments From zack@kde.org  2003-04-02 03:53 -------
Subject: Re:  Crash on starting juk

On Tuesday 01 April 2003 20:34, you wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=56733
>
>
>
>
> ------- Additional Comments From wheeler@kde.org  2003-04-02 03:34
> ------- Subject: Re: Crash on starting juk
>
> Ok, I just closed this because I'm pretty sure I spotted it and fixed
> it.  If you're running HEAD can you give it a try?  Otherwise I can
> send you a patch againt 1.1.

Sure you got the right bug there? I think you fixed 56687 and not this 
one. There's no way of testing qdatastream directly for validity but 
what could be done is creating an empty "invalid" file that would be 
deleted when cache would have been completely written to "cache" file. 
If JuK on startup would detect existence of that file it would 
regenerate the cache.
Anyway, here's the cache file you asked for :




Created an attachment (id=1288)
 --> (http://bugs.kde.org/attachment.cgi?id=1288&action=view)
cache
[prev in list] [next in list] [prev in thread] [next in thread]