RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 996885 - non-root users can't run tuna
Summary: non-root users can't run tuna
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuna
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: John Kacur
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On: 974027 996954
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-14 08:45 UTC by Jiri Kastner
Modified: 2014-06-18 07:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 974027
Environment:
Last Closed: 2014-06-13 11:12:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jiri Kastner 2013-08-14 08:45:07 UTC 
+++ This bug was initially created as a clone of Bug #974027 +++

Description of problem:
only root can successfully launch tuna 

Version-Release number of selected component (if applicable):
0.11

How reproducible:
always

Steps to Reproduce:
1. install tuna-0.11
2. run it as non-root
3. check output

Actual results:

[user@localhost ~]$ tuna                                                     |
Traceback (most recent call last):                                              |
  File "/usr/bin/tuna", line 647, in <module>                                   |
    main()                                                                      |
  File "/usr/bin/tuna", line 641, in main                                       |
    app = tuna_gui.main_gui(kthreads, uthreads, cpus_filtered)                  |
  File "/usr/lib/python2.7/site-packages/tuna/tuna_gui.py", line 52, in __init__|
    self.check_env()                                                            |
  File "/usr/lib/python2.7/site-packages/tuna/tuna_gui.py", line 156, in check_e|
nv                                                                              |
    os.mkdir("/root/.local/")                                                   |
OSError: [Errno 13] Permission denied: '/root/.local/' 

Expected results:
tuna executed with limited functionality

Additional info:

--- Additional comment from Fedora Update System on 2013-07-29 04:13:02 EDT ---

tuna-0.11.1-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/tuna-0.11.1-1.fc19

--- Additional comment from Fedora Update System on 2013-07-30 13:33:12 EDT ---

Package tuna-0.11.1-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tuna-0.11.1-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-13851/tuna-0.11.1-1.fc19
then log in and leave karma (feedback).

--- Additional comment from Fedora Update System on 2013-08-01 02:30:53 EDT ---

tuna-0.11.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/tuna-0.11.1-1.fc18

--- Additional comment from Fedora Update System on 2013-08-01 23:38:10 EDT ---

tuna-0.11.1-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

--- Additional comment from Fedora Update System on 2013-08-06 19:39:35 EDT ---

tuna-0.11.1-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 1 Jiri Kastner 2013-08-14 08:46:49 UTC 
this bug was resolved in upstream (0.11.1)
Comment 3 John Kacur 2013-11-07 14:33:02 UTC 
@Jiri - this should be fixed in RHEL too, since I have the latest from upstream, but it would help me to verify this if you had cited a commit. Thanks
Comment 4 Jiri Kastner 2013-11-07 14:42:37 UTC 
this commit https://git.kernel.org/cgit/utils/tuna/tuna.git/commit/?id=ef83898c745462832d88d6bcf5b706544436f32f is the fix
Comment 5 John Kacur 2013-11-07 23:08:14 UTC 
Is there any way you can keep the fedora bz numbers out of the commit name?
Comment 8 Ludek Smid 2014-06-13 11:12:46 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.