Hi Whise,
Thanks for clarifying that this code needs to be run BEFORE importing gtkmozembed. I actually based this screenlet after your TheGamer screenlet. I had this initialization code there to begin with but it wasn't working because I was importing gtkmozembed beforehand. You'll see what led to my confusion if you look in TheGamerScreenlet.py where you have gtkmozembed imported twice :)
Thanks again! Without your screenlets to use as a model I never would have created this.
Ratings & Comments
6 Comments
change to screenlets section please
this is my favorite screenlet ever!!! Thank you!
Thanks! Glad I could make someone's day, you sure made mine :)
hi , here is a work arround for the ubuntu gtmozembed bug just add the code before importing it nice job :) Quote:
#########WORKARROUND FOR GTKOZEMBED BUG################
if sys.argv[0].endswith('SlackerScreenlet.py'):
if commands.getoutput("lsb_release -is") == 'Ubuntu':
mypath = sys.argv[0][:sys.argv[0].find('SlackerScreenlet.py')].strip()
if os.path.isfile(mypath + "running"):
os.system("rm -f " + mypath + "running")
else:
os.system ("export LD_LIBRARY_PATH=/usr/lib/firefox \n export MOZILLA_FIVE_HOME=/usr/lib/firefox \n python "+ sys.argv[0] + " &")
fileObj = open(mypath + "running","w") #// open for for write
fileObj.write('gtkmozembed bug workarround')
fileObj.close()
exit()
else:
pass
import gtkmozembed
Hi Whise, Thanks for clarifying that this code needs to be run BEFORE importing gtkmozembed. I actually based this screenlet after your TheGamer screenlet. I had this initialization code there to begin with but it wasn't working because I was importing gtkmozembed beforehand. You'll see what led to my confusion if you look in TheGamerScreenlet.py where you have gtkmozembed imported twice :) Thanks again! Without your screenlets to use as a model I never would have created this.
ohh didnt know i imported it twice , ill have to fix that , thanks