Summary: | app-text/referencer: failed to run | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey Popov (RETIRED) <pinkbyte> |
Component: | Current packages | Assignee: | Dominik Kriegner <dominik.kriegner> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pacho, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey Popov (RETIRED)
![]() i am using referencer (1.2.1) extensively and did not experience this issue. what is the version of the dependencies of referencer on your system? to find if the mistake is really in referencer itself please remove all the installed plugins from the folder /usr/lib64/referencer and try to start referencer (also empty any local plugin directory ~/.referencer/plugins) also please check what is stored in gconf by executing 'gconftool-2 --recursive-list /apps/referencer' (In reply to Dominik Kriegner from comment #1) > i am using referencer (1.2.1) extensively and did not experience this issue. > what is the version of the dependencies of referencer on your system? > to find if the mistake is really in referencer itself please remove all the > installed plugins from the folder /usr/lib64/referencer and try to start > referencer (also empty any local plugin directory ~/.referencer/plugins) pinkbyte@phantom ~ $ ls -la .referencer ls: cannot access .referencer: No such file or directory pinkbyte@phantom ~ $ ls -la /usr/lib64/referencer ls: cannot access /usr/lib64/referencer: No such file or directory pinkbyte@phantom ~ $ referencer int main(int, char**): setting pythonPath to :./plugins:/home/pinkbyte/.referencer/plugins:/usr/lib64/referencer: terminate called after throwing an instance of 'Gnome::Conf::Error' Aborted As you see: just plugins info is gone, the error itself remains the same. > also please check what is stored in gconf by executing > 'gconftool-2 --recursive-list /apps/referencer' pinkbyte@phantom ~ $ gconftool-2 --recursive-list /apps/referencer pinkbyte@phantom ~ $ Nothing here. Should gconf settings appear after first successful run? Sorry, forgot to post dependency versions info: pinkbyte@phantom ~ $ emerge -Opv poppler gtkmm:2.4 libglademm gconfmm boost gtkmm-utils These are the packages that would be merged, in order: [ebuild R ] app-text/poppler-0.22.2-r2:0/35 USE="cairo cxx jpeg* lcms png utils -cjk -curl -debug -doc -introspection -jpeg2k -qt4 -tiff" 0 kB [ebuild R ] dev-cpp/gtkmm-2.24.2:2.4 USE="-doc -examples {-test}" 0 kB [ebuild R ] dev-cpp/libglademm-2.6.7:2.4 USE="-doc -examples" 0 kB [ebuild R ] dev-cpp/gconfmm-2.28.3 USE="-doc" 0 kB [ebuild R ~] dev-libs/boost-1.52.0-r6:0/1.52 USE="nls threads -debug -doc -icu -mpi -python -static-libs -tools" PYTHON_TARGETS="python2_7 -python2_5 -python2_6 -python3_1 -python3_2 -python3_3" 0 kB [ebuild R ~] dev-cpp/gtkmm-utils-0.4.1 USE="-doc" 0 kB Total: 6 packages (6 reinstalls), Size of downloads: 0 kB gtkmm-utils is here as i tried to use referencer-1.2.0 (In reply to Sergey Popov from comment #3) > Sorry, forgot to post dependency versions info: > > pinkbyte@phantom ~ $ emerge -Opv poppler gtkmm:2.4 libglademm gconfmm boost > gtkmm-utils > > These are the packages that would be merged, in order: > > [ebuild R ] app-text/poppler-0.22.2-r2:0/35 USE="cairo cxx jpeg* lcms > png utils -cjk -curl -debug -doc -introspection -jpeg2k -qt4 -tiff" 0 kB > [ebuild R ] dev-cpp/gtkmm-2.24.2:2.4 USE="-doc -examples {-test}" 0 kB > [ebuild R ] dev-cpp/libglademm-2.6.7:2.4 USE="-doc -examples" 0 kB > [ebuild R ] dev-cpp/gconfmm-2.28.3 USE="-doc" 0 kB > [ebuild R ~] dev-libs/boost-1.52.0-r6:0/1.52 USE="nls threads -debug > -doc -icu -mpi -python -static-libs -tools" PYTHON_TARGETS="python2_7 > -python2_5 -python2_6 -python3_1 -python3_2 -python3_3" 0 kB > [ebuild R ~] dev-cpp/gtkmm-utils-0.4.1 USE="-doc" 0 kB > > Total: 6 packages (6 reinstalls), Size of downloads: 0 kB > > gtkmm-utils is here as i tried to use referencer-1.2.0 I have the same versions of the dependencies except of poppler, which should not make any difference. I just tried with a new user and indeed the gconf entries are created after the first successful run of referencer. Could there be anything preventing an access to gconf? referencer is also dealing with some proxy settings in gconf: system/http_proxy and system/proxy. ( see http://bazaar.launchpad.net/~referencer-devs/referencer/trunk/view/head:/src/Preferences.C ) (In reply to Dominik Kriegner from comment #4) > I have the same versions of the dependencies except of poppler, which should > not make any difference. > > I just tried with a new user and indeed the gconf entries are created after > the first successful run of referencer. Could there be anything preventing > an access to gconf? referencer is also dealing with some proxy settings in > gconf: system/http_proxy and system/proxy. > ( see > http://bazaar.launchpad.net/~referencer-devs/referencer/trunk/view/head:/src/ > Preferences.C ) Well, i am trying to run referencer in chroot. Other gconf-related applications(for example, ccsm - compiz settings manager) runs fine, but not referencer itself :-( (In reply to Sergey Popov from comment #5) > (In reply to Dominik Kriegner from comment #4) > > I have the same versions of the dependencies except of poppler, which should > > not make any difference. > > > > I just tried with a new user and indeed the gconf entries are created after > > the first successful run of referencer. Could there be anything preventing > > an access to gconf? referencer is also dealing with some proxy settings in > > gconf: system/http_proxy and system/proxy. > > ( see > > http://bazaar.launchpad.net/~referencer-devs/referencer/trunk/view/head:/src/ > > Preferences.C ) > > Well, i am trying to run referencer in chroot. Other gconf-related > applications(for example, ccsm - compiz settings manager) runs fine, but not > referencer itself :-( I suggest you report the problem upstream. (https://bugs.launchpad.net/referencer or http://icculus.org/mailman/listinfo/referencer) From the build point of view there is not much one can change. Please re-test with version 1.2.1, Did you file an upstream bug report? (In reply to Michael Weber from comment #7) > Please re-test with version 1.2.1, As i said in first comment - i have already tried that - still no luck. > Did you file an upstream bug report? Nope, and i can not guarantee that i will do it soon cause my internet connection sucks now :-( Is this issue still unresolved? Possible retest with version 1.2.2 which is in the main tree and the newest upstream release! seems fixed now |