https://bugzilla.novell.com/show_bug.cgi?id=337657#c2 --- Comment #2 from Duncan Mac-Vicar 2007-11-08 05:42:05 MST --- This is a candidate for a bug worth to fix in 10.3. However the bug reports contain no useful information on how to reproduce. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=337657#c5 Miguel Angel Alvarez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #5 from Miguel Angel Alvarez 2007-11-08 08:45:16 MST --- The bug is not solved. To Duncan: I'm sorry. This is one of those bugs related to some unusual condition. I'll try to reproduce it somehow. To Bernhard: The problem is not loosing any information. The problem is the imposibility to solve "the problem" for anyone but an expert, and I mean really expert. Get it, yast segfaults and doesn't work anymore. Zypper doesn't work anymore. opensuseupdater doesn't work anymore and gives no error or indication it is not working, while it seems to be working. _Anything_ related to repository management doesn't work anymore. You _can't_ repair it and have no clue why it doesn't work, why it can't be repaired, and how to repair. The fix is easy: it's only a cache, if any error, make yast/zypper delete it and rebuild it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=337657#c7 --- Comment #7 from Miguel Angel Alvarez 2007-11-08 13:06:40 MST --- Don't forget to add a "rebuilddb" command to zypper/yast to be able to do it by hand too (sometimes it gets stuck and the exception would be not thrown) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=337657#c9 Fred Fox changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fredfox@weru.ksu.edu --- Comment #9 from Fred Fox 2007-11-28 14:47:32 MST --- This happened to me on a fresh install from a 10.3 CD that I downloaded yesterday. After this install, Launching Software Management would bring up a Bug Buddy screen saying it had collected information on the bug. When I renamed the /var/cache/zypp/zypp.db file, launching Software Management resulted in a rebuild of the /var/cache/zypp/zypp.db file and a working Software Management window. I had problems during the install since I enabled the firewall without opening a hole for HTTP traffic, resulting in some repeated steps when initially setting up the repositories. That might be a way to reproduce the problem. I saved the corrupted db file if that would be of any use. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=337657 User maacruz@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=337657#c11 --- Comment #11 from Miguel Angel Alvarez 2008-02-12 13:33:28 MST --- I have got a corrupt database again. This time I think it happened after the kernel-2.6.22.17-0.1 update, I updated using you and after reboot tryed running yast. Unfortunately there was no journal file when I noticed the corruption after running yast. So, I don't know if the sqlite3 engine directly corrupts the database, or a commit fails and when trying to rollback the database gets corrupted. I have saved the database file and raw directory, just in case you want to have a look at it or use it for testing. Trying to do a "vacuum" fails with "SQL error: database disk image is malformed" Running yast installer and selecting the Opensuse FTP repository gives the following warning at startup: Error en la inicialización del repositorio. Record not found in the cache Historial: - SQL logic error or missing database Selecting Repositories as filter and choosing openSUSE-10.3-FTP crashes yast with the following message: terminate called after throwing an instance of 'sqlite3x::database_error' what(): SQL logic error or missing database YaST got signal 6 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:45 /sbin/yast2: line 386: 16250 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS Running sqlite3_analyze on it: miguel@enol:/tmp> ./sqlite3_analyzer-3.5.4.bin zypp.db Analyzing table db_info... Analyzing table delta_packages... Analyzing table dir_names... Analyzing table file_capabilities... Analyzing table file_names... Analyzing table files... Analyzing table filesystem_capabilities... Analyzing table hal_capabilities... Analyzing table locks... Analyzing table modalias_capabilities... Analyzing table named_capabilities... Analyzing table names... Analyzing table numeric_attributes... Analyzing table other_capabilities... Analyzing table patch_packages... Analyzing table patch_packages_baseversions... Analyzing table repositories... Analyzing table resolvable_disk_usage... Analyzing table resolvable_files... Analyzing table resolvables... Analyzing table resolvables_repositories... Analyzing table split_capabilities... Analyzing table sqlite_master... Analyzing table sqlite_sequence... Analyzing table text_attributes... ERROR: SQLITE_CORRUPT SQLITE_CORRUPT while executing "btree_next $csr" ("foreach" body line 32) invoked from within "foreach {name rootpage} [db eval $sql] { puts stderr "Analyzing table $name..." # Code below traverses the table being analyzed (table name $name..." -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.