Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 823270

Summary: grubby --default-kernel segfault as user
Product: [Fedora] Fedora Reporter: Nicolas Chauvet (kwizart) <kwizart>
Component: grubbyAssignee: Peter Jones <pjones>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: andrew.elwell, bcl, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-31 14:51:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
grubby --default-kernel segault when run as user none

Description Nicolas Chauvet (kwizart) 2012-05-20 13:01:12 UTC
Created attachment 585639 [details]
grubby --default-kernel segault when run as user

Description of problem:
grubby --default-kernel segfault when run as non privileged users.
Even if it's not supposed to do so, the command should return insufficient privilege but not to segfault. 

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

How reproducible:
always from two different setup running f17 (i686 and x86_64).

Steps to Reproduce:
1.$ grubby --default-kernel

Actual results:
grubby recieved SIGSEGV!  Backtrace (6):

Expected results:
return an error code or the default kernel

Additional info:
When run as root (as probably expected) the right kernel is output in one of theses setup. (then there is another bug as #736188 for the other).
# grubby --default-kernel

Comment 1 Andrew Elwell 2012-08-31 14:51:55 UTC

*** This bug has been marked as a duplicate of bug 751608 ***