Bitmessage/PyBitmessage-2024-11-28
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 53 Actions Packages Projects Releases 5 Wiki Activity

ERROR - Could not find any typelib for MessagingMenu #706

New Issue
Closed
opened 2014-08-15 11:34:40 +02:00 by benpl · 4 comments
benpl commented 2014-08-15 11:34:40 +02:00 (Migrated from github.com)
Copy Link

pyBM will throw:
ERROR - Could not find any typelib for MessagingMenu
I have installed on my system all needed dependencies and I also run update PyBitmessage from source. Error under Ubuntu 14.04 and Elementary OS Luna.

[From terminal:]

benpl@benpl-comp:~$ cd PyBitmessage/ && python src/bitmessagemain.py
Loading existing config files from /home/benpl/.config/PyBitmessage/
2014-08-15 11:00:01,686 - DEBUG - Database file already exists.
Could not read the Namecoin config file probably because you don't have Namecoin installed. That's ok; we don't really need it. Detailed error message: [Errno 2] No such file or directory: '/home/benpl/.namecoin/namecoin.conf'
2014-08-15 11:00:01,883 - DEBUG - Loaded 0 objects from disk into the objectProcessorQueue.
2014-08-15 11:00:01,883 - DEBUG - reloading keys from keys.dat file
2014-08-15 11:00:02,008 - DEBUG - reloading subscriptions...
An Exception occurred within isOurOperatingSystemLimitedToHavingVeryFewHalfOpenConnections: invalid version number '#101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014'
2014-08-15 11:00:02,064 - ERROR - Could not find any typelib for MessagingMenu
Traceback (most recent call last):
  File "src/bitmessagemain.py", line 272, in <module>
    mainprogram.start()
  File "src/bitmessagemain.py", line 239, in start
    bitmessageqt.run()
  File "/home/benpl/PyBitmessage/src/bitmessageqt/__init__.py", line 3812, in run
    myapp = MyForm()
  File "/home/benpl/PyBitmessage/src/bitmessageqt/__init__.py", line 577, in __init__
    l10n.formatTimestamp()))
  File "/home/benpl/PyBitmessage/src/l10n.py", line 60, in formatTimestamp
    return unicode(timestring, encoding)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 2: ordinal not in range(128)
pyBM will throw: **ERROR - Could not find any typelib for MessagingMenu** I have installed on my system all needed dependencies and I also run update PyBitmessage from source. Error under Ubuntu 14.04 and Elementary OS Luna. [From terminal:] ``` benpl@benpl-comp:~$ cd PyBitmessage/ && python src/bitmessagemain.py Loading existing config files from /home/benpl/.config/PyBitmessage/ 2014-08-15 11:00:01,686 - DEBUG - Database file already exists. Could not read the Namecoin config file probably because you don't have Namecoin installed. That's ok; we don't really need it. Detailed error message: [Errno 2] No such file or directory: '/home/benpl/.namecoin/namecoin.conf' 2014-08-15 11:00:01,883 - DEBUG - Loaded 0 objects from disk into the objectProcessorQueue. 2014-08-15 11:00:01,883 - DEBUG - reloading keys from keys.dat file 2014-08-15 11:00:02,008 - DEBUG - reloading subscriptions... An Exception occurred within isOurOperatingSystemLimitedToHavingVeryFewHalfOpenConnections: invalid version number '#101-Ubuntu SMP Tue Jul 15 17:46:11 UTC 2014' 2014-08-15 11:00:02,064 - ERROR - Could not find any typelib for MessagingMenu Traceback (most recent call last): File "src/bitmessagemain.py", line 272, in <module> mainprogram.start() File "src/bitmessagemain.py", line 239, in start bitmessageqt.run() File "/home/benpl/PyBitmessage/src/bitmessageqt/__init__.py", line 3812, in run myapp = MyForm() File "/home/benpl/PyBitmessage/src/bitmessageqt/__init__.py", line 577, in __init__ l10n.formatTimestamp())) File "/home/benpl/PyBitmessage/src/l10n.py", line 60, in formatTimestamp return unicode(timestring, encoding) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 2: ordinal not in range(128) ```
bmng-dev commented 2014-08-16 05:03:11 +02:00 (Migrated from github.com)
Copy Link

This is actually 2 separate issues, although only 1 is a showstopper. It seems your system is indicating it will return ASCII encoded strings but is actually using some other encoding. I'm not sure how to deal with a system that lies like that other than doing a brute force check of unicode conversions of all month and day names/abbreviations at startup and falling back to a safe encoding and timeformat if something goes wrong.

I can't help with the MessaginMenu issue but it doesn't stop PyBitmessage from working. You just miss out on notifications or something.

This is actually 2 separate issues, although only 1 is a showstopper. It seems your system is indicating it will return ASCII encoded strings but is actually using some other encoding. I'm not sure how to deal with a system that lies like that other than doing a brute force check of unicode conversions of all month and day names/abbreviations at startup and falling back to a safe encoding and timeformat if something goes wrong. I can't help with the MessaginMenu issue but it doesn't stop PyBitmessage from working. You just miss out on notifications or something.
benpl commented 2014-08-20 12:14:28 +02:00 (Migrated from github.com)
Copy Link

Error is caused by local settings in Language settings (under Ubuntu 14.04).
Number/date/currency format in my setings is set to "polski" (it means polish; I attach screen grab).
If I change it to "English (United States)" pyBM starts correctly.
So you can easy duplicate this error on your system.
polski-settings-20082014

Error is caused by local settings in Language settings (under Ubuntu 14.04). Number/date/currency format in my setings is set to "polski" (it means polish; I attach screen grab). If I change it to "English (United States)" pyBM starts correctly. So you can easy duplicate this error on your system. ![polski-settings-20082014](https://cloud.githubusercontent.com/assets/8445611/3979253/61116ce8-2852-11e4-9279-fbb749d8a193.png)
TheKysek commented 2014-08-24 16:14:14 +02:00 (Migrated from github.com)
Copy Link

Reproduced on Debian 7.6 Bitmessage works but GUI doesn't show up.

Traceback (most recent call last):
  File "/home/user/PyBitmessage/src/bitmessagemain.py", line 272, in <module>
    mainprogram.start()
  File "/home/user/PyBitmessage/src/bitmessagemain.py", line 239, in start
    bitmessageqt.run()
  File "/home/user/PyBitmessage/src/bitmessageqt/__init__.py", line 3812, in run
    myapp = MyForm()
  File "/home/user/PyBitmessage/src/bitmessageqt/__init__.py", line 534, in __init__
    self.loadInbox()
  File "/home/user/PyBitmessage/src/bitmessageqt/__init__.py", line 970, in loadInbox
    time_item = myTableWidgetItem(l10n.formatTimestamp(received))
  File "/home/user/PyBitmessage/src/l10n.py", line 81, in formatTimestamp
    return unicode(timestring, encoding)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 0: ordinal not in range(128)

This also happens for French: https://github.com/Bitmessage/PyBitmessage/issues/708

Reproduced on Debian 7.6 Bitmessage works but GUI doesn't show up. ``` Traceback (most recent call last): File "/home/user/PyBitmessage/src/bitmessagemain.py", line 272, in <module> mainprogram.start() File "/home/user/PyBitmessage/src/bitmessagemain.py", line 239, in start bitmessageqt.run() File "/home/user/PyBitmessage/src/bitmessageqt/__init__.py", line 3812, in run myapp = MyForm() File "/home/user/PyBitmessage/src/bitmessageqt/__init__.py", line 534, in __init__ self.loadInbox() File "/home/user/PyBitmessage/src/bitmessageqt/__init__.py", line 970, in loadInbox time_item = myTableWidgetItem(l10n.formatTimestamp(received)) File "/home/user/PyBitmessage/src/l10n.py", line 81, in formatTimestamp return unicode(timestring, encoding) UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 0: ordinal not in range(128) ``` This also happens for French: https://github.com/Bitmessage/PyBitmessage/issues/708
PeterSurda commented 2015-11-11 01:37:21 +01:00 (Migrated from github.com)
Copy Link

I cannot reproduce this on https://github.com/mailchuck/PyBitmessage, I think it was fixed in 111d60dde8. I tried German, French and Polish, both UTF-8 and ISO-8859-1/ISO-8859-2 and it works fine (there's no polish translation but it doesn't crash). When I revert the aforementioned commit, it crashes exactly as you describe. I have Ubuntu 14.04. Please reopen if you still experience this problem.

I cannot reproduce this on https://github.com/mailchuck/PyBitmessage, I think it was fixed in 111d60dde89f866e525684789884e69b3f944d91. I tried German, French and Polish, both UTF-8 and ISO-8859-1/ISO-8859-2 and it works fine (there's no polish translation but it doesn't crash). When I revert the aforementioned commit, it crashes exactly as you describe. I have Ubuntu 14.04. Please reopen if you still experience this problem.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something isn't working as it's supposed to

  
build

Related to building or build system

  
dependencies

Pull requests that update a dependency file

  
developers

The issue is relevant mainly for developers rather than users

  
documentation

   
duplicate

   
enhancement

New feature

  
formatting

Code or UI text formatting

  
invalid

   
legal

   
mobile

Frontend for mobile devices (kivy)

  
obsolete

   
packaging

   
performance

   
protocol

Protocol change

  
question

   
refactoring

   
regression

Some issue, fixed in the past, appears again

  
security

   
test

   
translation

   
usability

   
wontfix
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
Milestone
Clear milestone
No items
No Milestone
v0.6.0
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-11-28#706
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?