edit/create posts not possible (encoding)

Bug #458359 reported by dani
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
BloGTK
In Progress
High
JayReding

Bug Description

looks like a encoding problem, probably the same exception on #434635

-- New Post exception
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/bin/../share/blogtk2/lib/blogtk2/main.py", line 647, in createNewPost
    newEditor = editor.BloGTKEditor(self)
  File "/usr/bin/../share/blogtk2/lib/blogtk2/editor.py", line 118, in __init__
    spell = gtkspell.Spell (self.scvEditMain)
GError: enchant error for language: de_CH.UTF-8

-- Edit Post exception : (Blogtk statusline msg: An error occurred: enchant error for language: de_CH.UTF-8)
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "/usr/lib64/python2.6/threading.py", line 477, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/bin/../share/blogtk2/lib/blogtk2/main.py", line 559, in sendPostToEditor
    newEditor.destroy(None)
UnboundLocalError: local variable 'newEditor' referenced before assignment

Traceback (most recent call last):
  File "/usr/bin/../share/blogtk2/lib/blogtk2/main.py", line 356, in update_progress_bar
    gobject.source_remove(self.timeout_handler_id)
AttributeError: BloGTK instance has no attribute 'timeout_handler_id'

solution idee: set the default to UTF-8 and lang en with the ability to change in the Blogtk Settings Manager.

- gentoo linux system with python 2.6

FYI:
On start a deprecated modul information but it is not the reason for the post exception:

/usr/lib64/python2.6/site-packages/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha

Revision history for this message
dani (alienhunter) wrote :
JayReding (jayreding)
Changed in blogtk:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → JayReding (jayreding)
Revision history for this message
JayReding (jayreding) wrote :

The correct locale setting should probably be just de_CH, and the '.UTF-8' string should not be getting returned by locale.getlocale()[0]. Attempting to see if just stripping out that Unicode identifier will correct the bug.

JayReding (jayreding)
Changed in blogtk:
status: Confirmed → In Progress
Revision history for this message
Bosco Witch (boscowitch) wrote :

having the same problem with german de_DE.UTF-8 tryped setting it to de_DE still not working....

GError: Enchant-Fehler für Sprache: de_DE

Revision history for this message
Bosco Witch (boscowitch) wrote :

SLOVED under archlinux by installing aspell-de ... you should make a setting for systems without aspell in their languaage !

Revision history for this message
T Aubrey (pgarrett-homemail) wrote :

I think this might be the same bug I'm experiencing.

I'm a new user, using blogGTK 2.0 to post and edit to blogger and wordpress sites.

New posting is fine but editing existing posts gives erratic results:

1. the first edit on a new post usually works OK

2. Second edit on blogger does not go through (connection times out with no error message)

3. Second edit on Wordpress deletes the entire post!

Revision history for this message
Jim Tarvid (tarvid) wrote :

I installed BloGTK2 at home and created a new post on my Drupal site. I edited several times and published successfully.

I then installed at work and tried to edit the post I had published from home.

At first I got the error "An error occurred: categories". Later I got the error "An error occurred: 'mt_text_more'"

I am setting up a third box.

BloGTK is an import part of a migration strategy and would dearly love to have a work around.

http://ls.net/content/portable-blogging-tool-blogtk

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments