GoldenDict can not import stardict dictionaries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
goldendict (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Dear Developers!
I use a large StarDict dictionaries collection. After upgrading to Ubuntu 13.04 goldendict could not recognize it usual way.
There are two folders in dictionaries configuration (F3): /usr/share/
I copied the collection to /home/user/
Running sudo goldendict did not help.
I copied the collection to /use/share/
Running sudo goldendict caused dictionary recognition process. But after a system restart rerunning sudo goldendict caused dictionary recognition process again.
With best regards.
Viktor.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: goldendict 1.0.2~git20120929-3
ProcVersionSign
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Mon Jul 8 16:38:45 2013
InstallationDate: Installed on 2013-05-25 (43 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no username)
XDG_RUNTIME_
LANG=uk_UA.UTF-8
SHELL=/bin/bash
SourcePackage: goldendict
UpgradeStatus: No upgrade log present (probably fresh install)
The workaround is (risky)
sudo apt-get install gksu
gksu-properties
Set identification mode as sudo and close a window
Use only:
gksu goldendict
It causes the dictionaries recognition process only once and works normally.
The main disadvantage is an invisibility of the resident icon in the top panel (but the program stays resident in the memory!). If You close a dictionary window You may run gksu goldendict (or sudo goldendict until next reboot/logoff) again. Until next reboot goldendict can not be run as a user with the following error in backtrace (the program stays in the memory as root):
The program 'goldendict' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
(Details: serial 395 error_code 10 request_code 33 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Also using Internet dictionaries as root possibly can be helpful for attackers.