Bug 1291336 - No output when running a seinfo query
Summary: No output when running a seinfo query
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: setools
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1295879 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-14 15:22 UTC by Simon Sekidde
Modified: 2016-02-22 09:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-22 09:08:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
strace output (138.78 KB, text/plain)
2015-12-14 15:22 UTC, Simon Sekidde 		no flags Details
View All

Description Simon Sekidde 2015-12-14 15:22:15 UTC 
Created attachment 1105597 [details]
strace output

Description of problem:

No output from when running a seinfo query

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

setools-console-3.3.8-8.2.fc23.f1e5b20.x86_64

How reproducible:

100% 

Steps to Reproduce:
1. seinfo -thttpd_t -x 

Actual results:

No output

Expected results:

 httpd_t
      can_change_object_identity
      kernel_system_state_reader
      syslog_client_type
      corenet_unlabeled_type
      sepgsql_client_type
      netlabel_peer_type
      daemon
      nsswitch_domain
      domain
   Aliases
      phpfpm_t

Additional info:
Comment 1 Petr Lautrbach 2016-02-03 08:02:49 UTC 
Thank you for the report. This is not a bug in Fedora package as there's no setools-console-3.3.8-8.2.fc23.f1e5b20 build in koji. But it's an issue of my builds from http://copr.fedoraproject.org/coprs/plautrba/selinux  where all SELinux Project packages are rebased to the latest RC1 release and  are supposed to be pushed to Rawhide.
Comment 2 Petr Lautrbach 2016-02-19 10:44:46 UTC 
*** Bug 1295879 has been marked as a duplicate of this bug. ***
Comment 3 Petr Lautrbach 2016-02-22 09:08:30 UTC 
Fixed in setools-3.3.8-10.fc24
Note You need to log in before you can comment on or make changes to this bug.