[gentoo-user] media-video/totem-2.20.3 Access violation

[gentoo-user] media-video/totem-2.20.3 Access violation

[Ivan Alden]

[-- Attachment #1: Type: text/plain, Size: 725 bytes --]

Hi,

When I run a revdep-rebuild or emerge totem I get an access violation
error when the system tries to compile totem.

Anyone knows what could be wrong?

Thanks

>>> Source compiled.
--------------------------- ACCESS VIOLATION SUMMARY
---------------------------
LOG FILE = "/var/log/sandbox/sandbox-16382.log"

unlink:    /usr/share/xml2po/docbook.pyc
unlink:    /usr/share/xml2po/docbook.pyc
unlink:    /usr/share/xml2po/docbook.pyc
unlink:    /usr/share/xml2po/docbook.pyc
unlink:    /usr/share/xml2po/docbook.pyc
unlink:    /usr/share/xml2po/docbook.pyc
unlink:    /usr/share/xml2po/docbook.pyc
unlink:    /usr/share/xml2po/docbook.pyc
--------------------------------------------------------------------------------

[-- Attachment #2: log.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 14441 bytes --]

Re: [gentoo-user] media-video/totem-2.20.3 Access violation

[Markus Schönhaber]

Ivan Alden wrote:

> When I run a revdep-rebuild or emerge totem I get an access violation
> error when the system tries to compile totem.

Try remerging app-text/gnome-doc-utils first.

Regards
  mks

Re: [gentoo-user] media-video/totem-2.20.3 Access violation

[Ivan Alden]

Thanks Markus for your help. I still get the error though =(
Cheers,
Ivan

On Mon, 2008-07-21 at 12:34 +0200, Markus Schönhaber wrote:
> Ivan Alden wrote:
> 
> > When I run a revdep-rebuild or emerge totem I get an access violation
> > error when the system tries to compile totem.
> 
> Try remerging app-text/gnome-doc-utils first.
> 
> Regards
>   mks
> 

Re: [gentoo-user] media-video/totem-2.20.3 Access violation

[Markus Schönhaber]

Ivan Alden wrote:

> Thanks Markus for your help. I still get the error though =(

Then I'm out of ideas. Re-emerging gnome-doc-utils solved the sandbox
violation wrt /usr/share/xml2po/docbook.pyc for me - it happened when
emerging epiphany, not totem, though.
Moreover: re-emerging gnome-doc-utils is what is suggested as a
workaround in the bug reports I've looked at (search for
/usr/share/xml2po/docbook.pyc in the comments field on BGO, for example).

Regards
  mks

Re: [gentoo-user] media-video/totem-2.20.3 Access violation

[Alex Schuster]

Ivan Alden wrote:

> When I run a revdep-rebuild or emerge totem I get an access violation
> error when the system tries to compile totem.
>
> Anyone knows what could be wrong?
>
> Thanks
>
> >>> Source compiled.
>
> --------------------------- ACCESS VIOLATION SUMMARY
> ---------------------------
> LOG FILE = "/var/log/sandbox/sandbox-16382.log"
>
> unlink:    /usr/share/xml2po/docbook.pyc
> unlink:    /usr/share/xml2po/docbook.pyc
> unlink:    /usr/share/xml2po/docbook.pyc
> unlink:    /usr/share/xml2po/docbook.pyc
> unlink:    /usr/share/xml2po/docbook.pyc
> unlink:    /usr/share/xml2po/docbook.pyc
> unlink:    /usr/share/xml2po/docbook.pyc
> unlink:    /usr/share/xml2po/docbook.pyc

Not sure about that, but I just got a similar error with some *.pyc files 
in /usr/share/pygtk/2.0/codegen/. I renamed those files, and could merge 
the package then.

If you try this, you do not need to compile totem, just do 
an "ebuild /usr/portage/media-video/totem-2.20.3.ebuild qmerge". 
Or "FEATURES=keepwork emerge -1 totem", which would take slightly longer 
due to unpacking and configuring again.

	Wonko

Re: [gentoo-user] media-video/totem-2.20.3 Access violation

[Zhu Sha Zang]

[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ivan Alden escreveu:
| Hi,
|
| When I run a revdep-rebuild or emerge totem I get an access violation
| error when the system tries to compile totem.
|
| Anyone knows what could be wrong?
|
| Thanks
|
|>>> Source compiled.
| --------------------------- ACCESS VIOLATION SUMMARY
| ---------------------------
| LOG FILE = "/var/log/sandbox/sandbox-16382.log"
|
| unlink:    /usr/share/xml2po/docbook.pyc
| unlink:    /usr/share/xml2po/docbook.pyc
| unlink:    /usr/share/xml2po/docbook.pyc
| unlink:    /usr/share/xml2po/docbook.pyc
| unlink:    /usr/share/xml2po/docbook.pyc
| unlink:    /usr/share/xml2po/docbook.pyc
| unlink:    /usr/share/xml2po/docbook.pyc
| unlink:    /usr/share/xml2po/docbook.pyc
| 
--------------------------------------------------------------------------------
I haved this problem when i'm trying to install ardour, but the problem 
was this:
unlink:    /usr/lib/scons-0.97/SCons/__init__.pyc
unlink:    /usr/lib/scons-0.97/SCons/Script/__init__.pyc
unlink:    /usr/lib/scons-0.97/SCons/Action.pyc
unlink:    /usr/lib/scons-0.97/SCons/Debug.pyc
unlink:    /usr/lib/scons-0.97/SCons/Errors.pyc
unlink:    /usr/lib/scons-0.97/SCons/Executor.pyc
unlink:    /usr/lib/scons-0.97/SCons/Memoize.pyc
unlink:    /usr/lib/scons-0.97/SCons/Util.pyc
unlink:    /usr/lib/scons-0.97/SCons/compat/__init__.pyc
unlink:    /usr/lib/scons-0.97/SCons/compat/builtins.pyc

The only solution for this, was deinstalling scons and reinstalling 
again. NOTE, i'm tried only reinstalling and won't worked. Only erasing 
scons have worked fine.

Bye.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiQC1cACgkQbLyL8mxGP9TOwQCghBKE1SNP3dD2q6GofOMPgWtd
WsgAoLENo52X5k4afm8dxvwGxk4qY5bi
=Te+L
-----END PGP SIGNATURE-----


[-- Attachment #2: Type: text/html, Size: 2649 bytes --]

Re: [gentoo-user] media-video/totem-2.20.3 Access violation

[Daniel Pielmeier]

All the problems above are related to python byte code, and the way it
is handled in gentoo. It would be to exhaustive to explain the
problems here but maybe this bug [1] helps to understand the problem.
Also if you want to learn more about python in gentoo you can read
this [2].

In the case of scons and docbook the problem is the same as mentoned
in the bug where python bytecode is installed into the wrong
filesystem location.

Other problems can occur when the python eclasses which handle the
python byte code are not used at all or improperly used with python
applications. For instance when python byte code is not handled by the
eclasses the py{c,o} files are created at runtime when using the
program as root. At deinstallation this files are not removed from the
filesystem because the package manager is not aware of them.

[1] http://bugs.gentoo.org/show_bug.cgi?id=194343
[2] http://www.gentoo.org/proj/en/Python/developersguide.xml