Your message dated Fri, 26 Sep 2014 16:05:26 +0200 with message-id <CAKNHny8bpDqUDA0dHmK1SXAz8_dcLLcUA1T6-KEpYoG=fo_...@mail.gmail.com> and subject line Re: Bug#761905: Database error in apper. has caused the Debian Bug report #761905, regarding apper Unable to open database read-only in current debian testing 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 [email protected] immediately.) -- 761905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761905 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apper Version: 0.9.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, lastest update to apper in debian testing resulted in the following error on startup: Unable to open database read-only: Database action 'prepare app insert statement' failed: SQL logic error or missing database (table applications has no column named unique_name) This renders apper unusable. Deleting the Listaller cache DB seemed to fix the problem for me. command used: rm -r /var/lib/listaller/db/ -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apper depends on: ii apper-data 0.9.1-1 ii kde-runtime 4:4.14.0-2 ii libappstream1 0.7.1-1 ii libc6 2.19-11 ii libdebconf-kde0 0.3-1 ii libgcc1 1:4.9.1-14 ii libgee-0.8-2 0.14.0-2 ii libglib2.0-0 2.40.0-5 ii libkcmutils4 4:4.14.1-1 ii libkdecore5 4:4.14.1-1 ii libkdeui5 4:4.14.1-1 ii libkemoticons4 4:4.14.1-1 ii libkidletime4 4:4.14.1-1 ii libkio5 4:4.14.1-1 ii libkprintutils4 4:4.14.1-1 ii libkutils4 4:4.14.1-1 ii libkworkspace4abi2 4:4.11.11-2 ii liblistaller-glib0 0.5.9-2 ii libpackagekitqt4-0 0.9.2-4 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-declarative 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-sql 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-xmlpatterns 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libsolid4 4:4.14.1-1 ii libstdc++6 4.9.1-14 ii packagekit 0.9.5-2 ii policykit-1-gnome 0.105-2 ii polkit-kde-1 0.99.1-1 ii software-properties-kde 0.92.25debian1 Versions of packages apper recommends: ii appstream-index 0.7.1-1 Versions of packages apper suggests: pn debconf-kde-helper <none> ii listaller 0.5.9-2 -- no debconf information
--- End Message ---
--- Begin Message ---Control: fixed 761905 0.5.9-3 This particular issue is fixed now as side-effect of dropping the PackageKit plugin in Listaller. I assume it was a very rare event where packages weren't upgraded to the latest version correctly. I fixed that as well, so hopefully nobody sees this issue anymore. To verify, execute $> lipa -l If you don't see an error, everything should be fine. Cheers, Matthias
--- End Message ---
