Problem mit der Timeline bzw. gespeicherter Filter-Einstellung

[pirat_helge@…]

Es geht um die Instanz der Piratenpartei Berlin auf lqpp.de ("1.3.1 mit Frontend Beta35"  https://twitter.com/acid23/status/230987540407132160).

Seit ich in meiner Timeline auf eine andere gespeicherte Filter-Einstellung wechseln wollte, erscheint folgende Fehlermeldung, wenn ich die Seite mit der Timeline öffnen möchte (abgesehen von der Timeline kann ich LiquidFeedback aber normal nutzen):

Database error of class InternalError occured:
could not find pathkey item to sort

Stack trace follows:
[C]: in function 'escalate'
../lib/mondelefant.lua:772: in function 'exec'
...opt/lqfb/frontend/beta35/app/main/timeline/_list.lua:22: in function 'content'
../env/ui/tag.lua:38: in function <../env/ui/tag.lua:15>
(tail call): ?
../env/ui/paginate.lua:77: in function 'content'
../env/ui/tag.lua:38: in function <../env/ui/tag.lua:15>
(tail call): ?
../env/ui/paginate.lua:70: in function 'paginate'
...opt/lqfb/frontend/beta35/app/main/timeline/_list.lua:17: in function 'func'
...
../env/execute/wrapped.lua:21: in function <../env/execute/wrapped.lua:11>
(tail call): ?
(tail call): ?
../env/execute/filtered_view.lua:28: in function 'filtered_view'
webmcp.lua:358: in function <webmcp.lua:235>
[C]: in function 'xpcall'
webmcp.lua:234: in main chunk
[C]: in function 'pcall'
/opt/lqfb/webmcp/1.1.2/cgi-bin/webmcp-wrapper.lua:7: in main chunk
[C]: ?

[jbe]

The "timeline system" has been replaced by the "event system" in LiquidFeedback 2.0. Please update to LiquidFeedback 2.0.

[jbe]

You might have also found a bug in PostgreSQL. A bug causing the same error message of class InternalError has been fixed in PostgreSQL version 9.1.2. See release notes of PostgreSQL 9.1.2:

 http://www.postgresql.org/docs/9.1/static/release-9-1-2.html

"Fix window functions that sort by expressions involving aggregates (Tom Lane)
Previously these could fail with 'could not find pathkey item to sort' planner errors."

However the installed version on your server seems to be 9.1.4. Anyway this doesn't seem to be a bug of LiquidFeedback.

[jbe]

Another idea is that your database cluster might be corrupted, as errors of class "InternalError" are not supposed to happen. Please inform your administrators, to check on this issue.