Closed GoogleCodeExporter closed 9 years ago
由輸入內容消失的現象判斷,應該是輸入法崩潰了。
請打開 Console.app,在左邊欄展開 User Diagnostic Reports,找到
Squirrel_*.crash 傳上來看看吧。
Original comment by chen....@gmail.com
on 27 Jan 2013 at 7:08
log file
Original comment by FrankLu...@gmail.com
on 27 Jan 2013 at 8:18
Attachments:
.bin 文件可能是壞的。我這裏不能重現該錯誤。
*.bin 文件只在 *.dict.yaml 變化時重建,我猜測剛剛升級過?
刪除 /Library/Input Methods/Squirrel.app/Contents/SharedSupport/*.bin
重新部署看能否修正。
Original comment by chen....@gmail.com
on 27 Jan 2013 at 8:39
No lucky after remove all bin files from sharedsupport folder. Please find the
latest log file.
Original comment by FrankLu...@gmail.com
on 27 Jan 2013 at 11:54
Attachments:
should I re-install the program?
Original comment by FrankLu...@gmail.com
on 27 Jan 2013 at 11:57
I don't know... still unsure about the .bin files.
Can you give me the output of this command?
ls -lL ~/Library/Rime/luna_pinyin.*.bin
Original comment by chen....@gmail.com
on 27 Jan 2013 at 11:59
Uh oh. The suspect files producing the error are located in ~/Library/Rime/
instead of in SharedSupport directory,
and they were created 2 days ago? if your system clock isn't 2 days late.
Try:
rm ~/Library/Rime/*.bin
and Deploy.
Original comment by chen....@gmail.com
on 27 Jan 2013 at 12:13
执行过删除及重新部署之后可以正常使用了,谢谢!
另,我的时钟没问题哈。这次的版本是之前升级的,应该是ma
c掉电之后文件损坏造成的。
Original comment by FrankLu...@gmail.com
on 27 Jan 2013 at 12:20
Sorry for the inconvenience.
I believe this doesn't usually happen.
Could it be: while luna_pinyin.table.bin was in the midst of being created, the
power was down and left the file incomplete?
It was slightly smaller than mine (8165073 bytes) but I'm not sure since I edit
the dictionary files a lot.
Original comment by chen....@gmail.com
on 27 Jan 2013 at 12:26
是否可以使‘重新部署’强制修复类似问题?
Original comment by FrankLu...@gmail.com
on 27 Jan 2013 at 12:34
完整性檢查……這個沒有做,恐怕比較費時呀。
現在只檢查文件頭的信息是否正確。也許該最後寫文件頭纔��
�。
Original comment by chen....@gmail.com
on 27 Jan 2013 at 12:38
做了一些防范。CHECKSUM先不验吧。
Original comment by chen....@gmail.com
on 29 Jan 2013 at 11:33
Original issue reported on code.google.com by
FrankLu...@gmail.com
on 27 Jan 2013 at 7:01