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

List:       kde-bugs-dist
Subject:    [Bug 56733] Crash on starting juk
From:       Scott Wheeler <wheeler () kde ! org>
Date:       2003-04-02 1:22:18
[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 wheeler@kde.org  2003-04-02 03:22 -------
Subject: Re: Crash on starting juk

Well, somehow your cache got corrupted.  I can reproduce something similar if 
I intentionally corrupt my cache, but I've never had that hapen in real usage 
(this is the first report of such).

So, here's the question -- do you know of an easy way to check a QDataStream 
for validity before trying to read it?  

The only way that I know of corrupting it in real use is killing JuK while 
it's exiting.

For a quick fix you can rm your $KDEHOME/share/apps/juk/cache, but you might 
want to save a copy for later debugging.  Also, could you send me that file?  
I'd like to see how / where it's corrupted.
[prev in list] [next in list] [prev in thread] [next in thread]