Deluge
Opened 3 years ago
Last modified 18 months ago
#3412 new bug
Trying to open US locale with wrong path
| Reported by: | petersasi | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.0.6 |
| Component: | Unknown | Version: | 2.0.3 |
| Keywords: | Cc: |
Description
While profiling deluge 2.04dev38 on windows for filesystem activities I have spotted these obviously messed up paths:
"pythonw.exe","IRP_MJ_CREATE","C:\Program Files\Deluge\lib\gtk-builduildd eleasegettextuildwin32 s16\..............gtkdRelease\share\locale\en_US\LC_MESSAGES\atk10.mo","NAME INVALID","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode?: Read, Write, AllocationSize?: n/a" "pythonw.exe","IRP_MJ_CREATE","C:\Program Files\Deluge\lib\gtk-builduildd eleasegettextuildwin32 s16\..............gtkdRelease\share\locale\en\LC_MESSAGES\atk10.mo","NAME INVALID","Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode?: Read, Write, AllocationSize?: n/a"
The correct file is in data\share\locale\en\LC_MESSAGES\atk10.mo but deluge never tried that.
Change History (3)
comment:1 Changed 3 years ago by petersasi
comment:2 Changed 18 months ago by Cas
- Milestone changed from 2.0.4 to 2.0.5
Ticket retargeted after milestone closed
comment:3 Changed 18 months ago by Cas
- Milestone changed from 2.0.5 to 2.0.6
Ticket retargeted after milestone closed
Same garbled path is attempted for: eleasegettextuildwin32 s16\..............gtkdRelease\share\locale\en\LC_MESSAGES\atk10.mo" eleasegettextuildwin32 s16\..............gtkdRelease\share\locale\en\LC_MESSAGES\glib20.mo" eleasegettextuildwin32 s16\..............gtkdRelease\share\locale\en\LC_MESSAGES\gtk30-properties.mo" eleasegettextuildwin32 s16\..............gtkdRelease\share\locale\en\LC_MESSAGES\messages.mo"
I have noticed that these 'en' locale files are indeed missing in my GTK build why the same exist for the other locales including 'en@shaw', 'en_CA' and 'en_GB'. Will have to investigate, why, still the garbled paths above are probably due to some error.