RedNotebook fails to start

Bug #1074100 reported by Jendrik Seipp
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RedNotebook
Fix Released
Medium
Jendrik Seipp

Bug Description

RedNotebook produces an error on startup (Win7-32).
The content of <Rednotebook.exe.log> is:

Traceback (most recent call last):
  File "rednotebook", line 11, in <module>
  File "rednotebook\journal.pyc", line 60, in <module>
  File "rednotebook\util\filesystem.pyc", line 37, in get_utf8_path
UnicodeDecodeError: 'utf8' codec can't decode byte 0xf6 in position 10: invalid start byte
Traceback (most recent call last):
  File "rednotebook", line 11, in <module>
  File "rednotebook\journal.pyc", line 60, in <module>
  File "rednotebook\util\filesystem.pyc", line 37, in get_utf8_path
UnicodeDecodeError: 'utf8' codec can't decode byte 0xf6 in position 10: invalid start byte

Thanks for informations on that.

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

I assume you're using RedNotebook 1.5, the installed version (not the PortableApps one)?

Can you please provide the full path to the rednotebook.exe file (Maybe do a search for it)?

Changed in rednotebook:
status: New → Incomplete
Revision history for this message
artefaktenmuggel (abindietonne) wrote :

It is the 1.5.0 portable version. But I have good news: I moved the RedNotebook folder from the desktop to a more "regular" folder (c:\temp) and it works.

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

What is the full path to the desktop?

Can you check if the error still happens with version 1.6.1, please? If it does, it might affect many users with non-ASCII paths.

Revision history for this message
artefaktenmuggel (abindietonne) wrote :

Hi Jendrik,

here are the infos:

Path of the portable 1.5 EXE: <C:\Users\Jörg\Desktop\RedNotebookPortable>

I have also installed the 1.6.1 - twice:
1) in <C:\Program Files\RedNotebook>. Everything runs fine
2) in <C:\Program Files\Jörg>. RedNotebook failed to start and wasn't able to write the logfile also (see attachment).
But I think that is a credential problem, because the user "Jörg" is restricted and has not enough rights to write into the Program files folder.

I hope that helps.
Jörg (from Germany)

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote : Re: [Bug 1074100] Re: RedNotebook fails to start

Thanks for the info. I think the program fails to start because of the ö
in your name. Could you please try putting version 1.6.1 to
C:\Users\Jörg\Desktop\RedNotebookPortable1.6.1 and see if it fails as
well and with the same error message?

Revision history for this message
artefaktenmuggel (abindietonne) wrote :

Launching the 1.6.1 portable in <C:\Users\Jörg\Desktop\RedNotebookPortable> fails with the following error:

Traceback (most recent call last):
  File "rednotebook", line 11, in <module>
  File "rednotebook\journal.pyc", line 57, in <module>
  File "rednotebook\util\filesystem.pyc", line 37, in get_utf8_path
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 10: ordinal not in range(128)

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

Thanks, it seems RedNotebook 1.6.1 stilldoesn't like Umlauts... I'll
look into it.

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

The new beta https://dl.dropbox.com/u/4780737/rednotebook-1.6.5-beta1.exe should fix that problem. Can you confirm that?

Changed in rednotebook:
status: Incomplete → In Progress
importance: Undecided → Medium
assignee: nobody → Jendrik Seipp (jendrikseipp)
Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :
Changed in rednotebook:
status: In Progress → Fix Committed
Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

This has been fixed in version 1.6.6.

Changed in rednotebook:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.