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

List:       kde-bugs-dist
Subject:    [Bug 94238] New: Amarok database SEEMS broken after a crash
From:       Jean-Michel Fayard <jmfayard () gmail ! com>
Date:       2004-12-01 20:51:50
Message-ID: 20041201215148.94238.jmfayard () gmail ! com
[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=94238        
           Summary: Amarok database SEEMS broken after a crash
           Product: amarok
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: amarok-bugs-dist lists sourceforge net
        ReportedBy: jmfayard gmail com


Version:            (using KDE KDE 3.3.0)
Installed from:    SuSE RPMs
OS:                Linux

Amarok version 1.1 (SuSE RPMs)

Reproducible : always
  Start amarok
  xkill it
  Start amarok
  Look at the database, it is empty

What a dumb user (pleonasm) like me do then :
  Hu ? What īs going wrong ? Let īs rescan it
  [still empty]
  Hu ? Grr, let īs reconfigure it (try to add a folder)
  [still empty]
  [after sometimes] : go in ~/.kde and delete *amarok* files
  [now it works, but you have to reconfigure it]
If a second crash append after that, you maybe will have the chanc
  to figure out that actually the database was not broken/empty
  Only that it didn īt no what tags to display (ie : artists then albums)
  Do that and it works.

Bad points of the whole story : you loose your useful statistics and amarok
  can get unjustified reputation of a crashy app

Solution : after a crash, I don īt mind if this is not the thing I configure,
  just set "artis then albums" so that I understand the database still works.
[prev in list] [next in list] [prev in thread] [next in thread]