[gpodder] Re: 'Uncaught exception' after migrating from 2 to 3

  • From: Dov Feldstern <dovdevel@xxxxxxxxx>
  • To: gpodder@xxxxxxxxxxxxx
  • Date: Thu, 30 Jan 2014 01:41:38 +0200

Actually, it seems like the patch *is* needed also for subsequent startups.

On Thu, Jan 30, 2014 at 1:31 AM, Dov Feldstern <dovdevel@xxxxxxxxx> wrote:
> Hi!
>
> I'm finally migrating from gpodder 2 to 3 (on my desktop, so no cuatro
> as far as I understand?), and when starting up gpodder3 after running
> the migration, I ran into the following uncaught exception (which
> aborted gpodder):
>
> 1391034956.956547 [gpodder.log] ERROR: Uncaught exception: Traceback
> (most recent call last):
>   File "proj/gpodder-new/bin/gpodder", line 174, in <module>
>     main()
>   File "proj/gpodder-new/bin/gpodder", line 169, in main
>     main.main(options)
>   File "/home/dov/proj/gpodder-new/src/gpodder/gtkui/main.py", line
> 3527, in main
>     gp = gPodder(bus_name, core.Core(UIConfig, model_class=Model))
>   File "/home/dov/proj/gpodder-new/src/gpodder/gtkui/main.py", line
> 122, in __init__
>     BuilderWidget.__init__(self, None)
>   File "/home/dov/proj/gpodder-new/src/gpodder/gtkui/interface/common.py",
> line 38, in __init__
>     GtkBuilderWidget.__init__(self, gpodder.ui_folders,
> gpodder.textdomain, **kwargs)
>   File "/home/dov/proj/gpodder-new/src/gpodder/gtkui/base.py", line
> 66, in __init__
>     self.new()
>   File "/home/dov/proj/gpodder-new/src/gpodder/gtkui/main.py", line 239, in 
> new
>     self.channels = self.model.get_podcasts()
>   File "/home/dov/proj/gpodder-new/src/gpodder/model.py", line 1346,
> in get_podcasts
>     podcast.check_download_folder()
>   File "/home/dov/proj/gpodder-new/src/gpodder/model.py", line 821, in
> check_download_folder
>     if not os.path.exists(filename):
>   File "/usr/lib/python2.7/genericpath.py", line 18, in exists
>     os.stat(path)
> TypeError: coercing to Unicode: need string or buffer, NoneType found
>
> The attached patch fixed it for me, but I'm not sure if it isn't
> covering up a deeper problem. (If anyone is interested in trying to
> understand the cause, I have the original version-2 database which is
> causing the problem.) Once gpodder 3 started up once with the patch,
> the patch is no longer even needed (i.e., the database has been
> cleaned up).
>
> So again, I'm not sure this is exactly right, and the wording of the
> message may also not be quite right, but probably some kind of
> solution should be applied here.
>
> Thanks!
> Dov

Other related posts: