Zim

special characters not working when using neo2 under windows

Bug #1564457 reported by Jörn Dreyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zim
Won't Fix
Undecided
Unassigned

Bug Description

neo2 uses eg caps lock as a modifier. It used with the 'd' key to produce a colon. This might be a bug with python on windows or something in between it and zim.

Zim 0.65 on Windows 10 ... umm ... running 'zim -D' requires admin permissions to create the logfile in the app directoy and then fails with this:

INFO: Locale set to: de_DE.cp1252
INFO: This is zim 0.65
DEBUG: Python version is sys.version_info(major=2, minor=7, micro=11, releaselevel='final', serial=0)
DEBUG: Platform is nt
DEBUG: Zim revision is:
  branch: 065
  revision: 805 <email address hidden>
  date: 2015-11-01 15:42:45 +0100
DEBUG: Running from a source dir: C:\Program Files (x86)\Zim Desktop Wiki
DEBUG: Set XDG_DATA_HOME to C:\Users\jfd\AppData\Roaming\zim\data
DEBUG: Set XDG_DATA_DIRS to [<Dir: C:\Users\jfd\.local\share>]
DEBUG: Set XDG_CONFIG_HOME to C:\Users\jfd\AppData\Roaming\zim\config
DEBUG: Set XDG_CONFIG_DIRS to [<Dir: C:\Users\jfd\.config>]
DEBUG: Set XDG_CACHE_HOME to C:\Users\jfd\AppData\Local\Microsoft\Windows\INetCache\zim
DEBUG: Loading config from: <zim.notebook.VirtualFile object at 0x02CF5530>
DEBUG: Loading config from: C:\Users\jfd\Notebooks\Notes\notebook.zim
DEBUG: Wrote C:\Users\jfd\AppData\Roaming\zim\config\zim\notebooks.list
INFO: Using default notebook: file:///C:/Users/jfd/Notebooks/Notes
DEBUG: Wrote C:\Users\jfd\Notebooks\Notes\.zim\tmp
INFO: Remove file: C:\Users\jfd\Notebooks\Notes\.zim\tmp
DEBUG: Loading config from: C:\Users\jfd\Notebooks\Notes\notebook.zim
DEBUG: Cache dir: C:\Users\jfd\AppData\Local\Microsoft\Windows\INetCache\zim\zim\notebook-C_Users_jfd_Notebooks_Notes
DEBUG: Index database file: C:\Users\jfd\AppData\Local\Microsoft\Windows\INetCache\zim\zim\notebook-C_Users_jfd_Notebooks_Notes\index.db
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Starting server by spawning new process
INFO: Spawning: ['C:\\Program Files (x86)\\Zim Desktop Wiki\\zim', '--ipc-server-main', '\\\\.\\pipe\\zim-jfd-server', '10'] (cwd: None)
DEBUG: Process started with PID: 0
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
Traceback (most recent call last):
  File "zim.py", line 50, in <module>
  File "zim\ipc.pyo", line 124, in handle_argv
  File "zim\ipc.pyo", line 315, in servermain
AttributeError: 'Blackhole' object has no attribute 'isatty'
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Remote call from 10668: <RemoteMethodCall: 10668: zim.ipc.Server(None).ping((), {})>
DEBUG: Cannot connect to server 10668:
Traceback (most recent call last):
  File "zim\ipc.pyo", line 273, in start_server_if_not_running
  File "zim\ipc.pyo", line 763, in call
  File "multiprocessing\connection.pyo", line 167, in Client
  File "multiprocessing\connection.pyo", line 387, in PipeClient
WindowsError: [Error 2] Das System kann die angegebene Datei nicht finden

ERROR: Exception in main()
Traceback (most recent call last):
  File "zim\main.pyo", line 446, in main
  File "zim\main.pyo", line 211, in run
  File "zim\ipc.pyo", line 283, in start_server_if_not_running
AssertionError: Failed to start server (spawning)
DEBUG: Running ErrorDialog

Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

No idea what to do here

Changed in zim:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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