Bug 672227 - NameError: global name 'APPLY' is not defined
Summary: NameError: global name 'APPLY' is not defined
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sabayon
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Smetana
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-24 13:40 UTC by Milos Malik
Modified: 2016-09-14 12:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-14 12:12:56 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Milos Malik 2011-01-24 13:40:34 UTC
Description of problem:


Version-Release number of selected component (if applicable):
RHEL6.1-20110121.n.1
sabayon-apply-2.29.92-1.el6
xguest-1.0.9-2.el6

How reproducible:
always

Steps to Reproduce:
Run /CoreOS/xguest/Regression/bz639857-disallowed-apps-running test on RHEL-6.1 machine where firefox and gnome-python2-bonobo packages are not installed.
  
Actual results:
4 tracebacks

Expected results:
0 tracebacks

Additional info:
MainThread 2011/01/24 08:32:25.9036 (sabayon-apply): Applying profile '/etc/sabayon/profiles/xguest.zip' for user 'xguest'
Failed to import module 'paneldelegate' cmd="from sources import paneldelegate"
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/sabayon/userprofile.py", line 51, in __load_module
    exec (cmd)
  File "<string>", line 1, in <module>
  File "/usr/lib64/python2.6/site-packages/sabayon/sources/paneldelegate.py", line 23, in <module>
    import bonobo
ImportError: No module named bonobo
MainThread 2011/01/24 08:32:25.9569 (sabayon-apply): Fatal exception!  Exiting abnormally.
MainThread 2011/01/24 08:32:25.9582 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 165, in <module>
    profile.apply (is_sabayon_session)
  File "/usr/lib64/python2.6/site-packages/sabayon/userprofile.py", line 394, in apply
    delegate.apply (is_sabayon_session)
  File "/usr/lib64/python2.6/site-packages/sabayon/sources/mozillasource.py", line 433, in apply
    dprint (APPLY, "apply: Firefox not found in PATH.  Unable to create new profile.")
NameError: global name 'APPLY' is not defined

===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) =====
MainThread 2011/01/24 08:32:25.9036 (sabayon-apply): Applying profile '/etc/sabayon/profiles/xguest.zip' for user 'xguest'
MainThread 2011/01/24 08:32:25.9569 (sabayon-apply): Fatal exception!  Exiting abnormally.
MainThread 2011/01/24 08:32:25.9582 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 165, in <module>
    profile.apply (is_sabayon_session)
  File "/usr/lib64/python2.6/site-packages/sabayon/userprofile.py", line 394, in apply
    delegate.apply (is_sabayon_session)
  File "/usr/lib64/python2.6/site-packages/sabayon/sources/mozillasource.py", line 433, in apply
    dprint (APPLY, "apply: Firefox not found in PATH.  Unable to create new profile.")
NameError: global name 'APPLY' is not defined

===== END MILESTONES (/usr/sbin/sabayon-apply) =====
===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) =====
MainThread 2011/01/24 08:32:25.9036 (sabayon-apply): Applying profile '/etc/sabayon/profiles/xguest.zip' for user 'xguest'
MainThread 2011/01/24 08:32:25.9569 (sabayon-apply): Fatal exception!  Exiting abnormally.
MainThread 2011/01/24 08:32:25.9582 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 165, in <module>
    profile.apply (is_sabayon_session)
  File "/usr/lib64/python2.6/site-packages/sabayon/userprofile.py", line 394, in apply
    delegate.apply (is_sabayon_session)
  File "/usr/lib64/python2.6/site-packages/sabayon/sources/mozillasource.py", line 433, in apply
    dprint (APPLY, "apply: Firefox not found in PATH.  Unable to create new profile.")
NameError: global name 'APPLY' is not defined

===== END RING BUFFER (/usr/sbin/sabayon-apply) =====


This configuration for the debug log can be re-created
by putting the following in ~//etc/sabayon/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000

Comment 4 RHEL Program Management 2011-01-24 14:08:25 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 5 RHEL Program Management 2011-07-06 00:38:24 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 6 RHEL Program Management 2012-07-10 06:11:11 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2012-07-11 01:53:15 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 8 RHEL Program Management 2012-09-07 05:16:45 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 10 Tomas Smetana 2016-09-14 12:12:56 UTC
5.5 years having zero customer (or other) impact. Looks like a good candidate for the exceptional WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.