After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 608006 - perl-Pango sandbox violations while testing.
perl-Pango sandbox violations while testing.
Status: RESOLVED NOTABUG
Product: gnome-perl
Classification: Bindings
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk2-perl-bugs
gtk2-perl-bugs
Depends on:
Blocks:
 
 
Reported: 2010-01-25 08:18 UTC by Serdar Dalgic
Modified: 2010-01-27 09:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Serdar Dalgic 2010-01-25 08:18:18 UTC 
while testing perl-Pango 1.221 some sandbox violations occur:
                           
t/PangoContext.t ..... Sandbox violation: open (/root/.config/qtcurve/gtk-icons.5270 -> /root/.config/qtcurve/gtk-icons.5270)                                    

t/PangoFont.t ........ 1/57 Sandbox violation: open (/root/.config/qtcurve/gtk-icons.5275 -> /root/.config/qtcurve/gtk-icons.5275)                               

t/PangoFontMap.t ..... Sandbox violation: open (/root/.config/qtcurve/gtk-icons.5280 -> /root/.config/qtcurve/gtk-icons.5280)                                    

t/PangoFontset.t ..... Sandbox violation: open (/root/.config/qtcurve/gtk-icons.5285 -> /root/.config/qtcurve/gtk-icons.5285)                                    

t/PangoLayout.t ...... Sandbox violation: open (/root/.config/qtcurve/gtk-icons.5291 -> /root/.config/qtcurve/gtk-icons.5291)

t/PangoRenderer.t .... 1/7 Sandbox violation: open (/root/.config/qtcurve/gtk-icons.5297 -> /root/.config/qtcurve/gtk-icons.5297)

btw, couldn't find the pango component, so I've selected the general. My perl version is 5.10.1.
Comment 1 Torsten Schoenfeld 2010-01-26 18:53:27 UTC 
It looks like the error messages complain about the tests trying to access qtcurve's configuration directory.  If that's right, that sounds perfectly normal and legal to me (assuming that you use the qtcurve gtk+ theme).  I don't see what we should do differently.  Can you elaborate?
Comment 2 Serdar Dalgic 2010-01-27 07:39:55 UTC 
I'm packaging the program for my own distro, Pardus. We use gentoo-like sandbox system[1]. This is a special environment which prevents packages accidentally write outside of permitted locations. 

/root/.config/qtcurve is not among the locations that are permitted to be reached.

So, is there a way to run tests without violating sandbox? Or should I disable the test violating sandbox while packaging the program?

When sandbox is ignored, all tests are succesful.

I hope this clarifies the reason why I entered this bug :)

[1] http://devmanual.gentoo.org/general-concepts/sandbox/index.html
Comment 3 Emmanuele Bassi (:ebassi) 2010-01-27 09:09:13 UTC 
(In reply to comment #2)

there's nothing gtk+ (or pango) can do if you're running with a custom theme engine (like qtcurve) whenever you're packaging gtk+ related packages.

> /root/.config/qtcurve is not among the locations that are permitted to be
> reached.

you should disable your own gtk+ theme when packaging - see:

  http://library.gnome.org/devel/gtk/stable/gtk-Resource-Files.html

and:

  http://library.gnome.org/devel/gtk/stable/gtk-running.html