I tried out 3.8.0 but I’m still seeing the same behavior (on my laptop, my iMac is still fine with this version). I uploaded the output of gPodder -v here: http://pastebin.com/Y1UsHvRi At the point where I open the preferences pane, this occurs: 1407426553.761490 [gpodder.config] DEBUG: auto.update.enabled: False -> True 1407426553.761720 [gpodder.util] DEBUG: run_in_background: <bound method UIConfig.save_thread_proc of <gpodder.gtkui.config.UIConfig object at 0x10577a450>> (True) 1407426553.860766 [gpodder.gtkui.main] DEBUG: Setting up auto update timer with interval 20. This is happening with my old gPodder directory moved to a separate location, so it doesn’t seem to be related to my specific preferences. Tim On Aug 6, 2014, at 3:59 PM, Eric Le Lay <elelay@xxxxxxxxxxxx> wrote: > Hi Tim, > > first things first, can you try the latest (gPodder 3.8.0) version? > I released it yesterday so it's the freshest and greatest :-). > > to enable debug messages, you'll have to run it from a terminal. > To do so, open the terminal and > type /Applications/gPodder.app/Contents/MacOS/gPodder -v > > Good luck, > Eric > > Le Wed, 06 Aug 2014 15:49:38 -0400, > Tim Gilbert <timgilbert@xxxxxxxxx> a écrit : > >> Hi! I’m experiencing an odd problem on gPodder 1.7.0 on OS/X 1.9.4. >> The program seems to start up and run just fine, but when I try to >> open the preferences dialog box either from the menu or the keyboard >> shortcut, the preferences dialog box appears for a brief moment and >> then instantly closes as though I had pressed escape or something. I >> can’t make any changes to the preferences in this state. >> >> Frustratingly, this doesn’t happen on both of the machines I run >> gPodder on. The behavior above happens on my work laptop (Late-2011 >> MacBook Pro) but not my home machine (Mid-2010 iMac). They are both >> running OS/X 10.9.4 and are set up pretty similarly. >> >> I’ve tried wiping out my preferences and local settings (by moving >> ~/gPodder to ~/gPodder.BAK) and I still get the same behavior. >> Nothing that looks related shows up in the logs, though if someone >> can tell me how to enable debug messages I’ll try that. >> >> Any help appreciated! >> Tim >