Bug 1217061

Created attachment 1020151 [details]
File: backtrace

Created attachment 1020152 [details]
File: environ

I removed  database
rm .config/gpodder/database.sqlite  .config/gpodder/mygpo.queue.sqlite

Started with a clean gpodder-downloads 
rm -rf gpodder-downloads

Added a new RSS feed

Downloaded the a episode.

quit gpodder

Started gpodder
Trace ended in
File "/usr/lib/python2.7/site-packages/gpodder/dbsqlite.py", line 708, in upgrade_table
    for pos, idx_name, idx_is_unique in current_indices:
ValueError: too many values to unpack

It just startet recently, so I suspect this:
    Updated sqlite-3.8.8.3-1.fc20.i686                                 @updates
    Updated sqlite-3.8.8.3-1.fc20.x86_64                               @updates
    Update         3.8.9-1.fc20.i686                                   @updates
    Update         3.8.9-1.fc20.x86_64                                 @updates
    Updated sqlite-devel-3.8.8.3-1.fc20.x86_64                         @updates
    Update               3.8.9-1.fc20.x86_64                           @updates

Another user experienced a similar problem:

Works for me since many years. Thanks for that. But, since now crashes the program already at the start :(

reporter:       libreport-2.2.3
cmdline:        /usr/bin/python /usr/bin/gpo update
executable:     /usr/bin/gpo
kernel:         3.18.9-100.fc20.x86_64
package:        gpodder-2.20.3-2.fc20
reason:         dbsqlite.py:708:upgrade_table:ValueError: too many values to unpack
runlevel:       N 5
type:           Python
uid:            666

Created attachment 1021560 [details]
Quick and dirty fix

I did a quick and dirty patch that seems to fix it for me.
Maybe there is a better solution to prevent breaking next time sqlite extends a set/array

Comment on attachment 1021560 [details]
Quick and dirty fix

Yes, really great. Changing line 708, works for me. thank you Mark

dbsqlite.py
        # Search for a unique index on the "guid" column in
        # the episodes table and drop it if it exists. It will
        # be recreated without the unique flag. (Maemo bug 12094)
        cur.execute('PRAGMA index_list(%s)' % self.TABLE_EPISODES)
        current_indices = cur.fetchall()
Line 708
        for pos, idx_name, idx_is_unique in current_indices:
fix:
        for pos, idx_name, idx_is_unique, ignore1, ignore2 in current_indices:

https://www.sqlite.org/pragma.html#pragma_index_list
Specific pragma statements may be removed and others added in future releases of SQLite. There is no guarantee of backwards compatibility. 

PRAGMA database.index_list(table-name);

This pragma returns one row for each index associated with the given table.

Output columns from the index_list pragma are as follows:

    A sequence number assigned to each index for internal tracking purposes.
    The name of the index.
    "1" if the index is UNIQUE and "0" if not.
    "c" if the index was created by a CREATE INDEX statement, "u" if the index was created by a UNIQUE constraint, or "pk" if the index was created by a PRIMARY KEY constraint.
    "1" if the index is a partial index and "0" if not. 


Why does line 708 for .... choke ?

gpodder-2.20.3-3.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gpodder-2.20.3-3.fc20

Package gpodder-2.20.3-3.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gpodder-2.20.3-3.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-7745/gpodder-2.20.3-3.fc20
then log in and leave karma (feedback).

There is a better fix upstream now:

https://github.com/gpodder/gpodder/commit/e02b028

gpodder-2.20.3-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.