Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
--- Comment #65 from kevin martin <kevintm(a)ameritech.net> 2011-10-31 17:44:04 EDT ---
Interestingly enough, it appears that it *did*, in fact, write out a new
grub2/grub.cfg for the new kernel:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="1"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
true
}
set timeout=10
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (3.2.0-0.rc0.git1.0.fc17.x86_64.debug)' --class gnu-linux
--class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 5fa84efc-2093-49a8-a997-98bb79a345e3
echo 'Loading Fedora (3.2.0-0.rc0.git1.0.fc17.x86_64)'
linux /vmlinuz-3.2.0-0.rc0.git1.0.fc17.x86_64.debug
root=UUID=abf1eb35-0fe0-4e2c-8ee5-c6542ace2c85 ro nouveau.noaccel=1
nouveau.vram_pushbuf=1 nouveau.vram_notify=1 log_buf_len=16M
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.2.0-0.rc0.git1.0.fc17.x86_64.debug.img
}
menuentry 'Fedora (3.2.0-0.rc0.git1.0.fc17.x86_64)' --class gnu-linux --class
gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 5fa84efc-2093-49a8-a997-98bb79a345e3
echo 'Loading Fedora (3.2.0-0.rc0.git1.0.fc17.x86_64)'
linux /vmlinuz-3.2.0-0.rc0.git1.0.fc17.x86_64
root=UUID=abf1eb35-0fe0-4e2c-8ee5-c6542ace2c85 ro nouveau.noaccel=1
nouveau.vram_pushbuf=1 nouveau.vram_notify=1 log_buf_len=16M
SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.2.0-0.rc0.git1.0.fc17.x86_64.img
}
menuentry 'Linux, with Linux 3.1.0-0.rc9.git0.3.fc17.x86_64' --class gnu-linux
--class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 5fa84efc-2093-49a8-a997-98bb79a345e3
echo 'Loading Linux 3.1.0-0.rc9.git0.3.fc17.x86_64 ...'
linux /vmlinuz-3.1.0-0.rc9.git0.3.fc17.x86_64
root=UUID=abf1eb35-0fe0-4e2c-8ee5-c6542ace2c85 ro nouveau.noaccel=1
nouveau.vram_pushbuf=1 nouveau.vram_notify=1 log_buf_len=16M
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.1.0-0.rc9.git0.3.fc17.x86_64.img
}
menuentry 'Linux, with Linux 3.1.0-0.rc9.git0.3.fc17.x86_64 (recovery mode)'
--class gnu-linux --class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 5fa84efc-2093-49a8-a997-98bb79a345e3
echo 'Loading Linux 3.1.0-0.rc9.git0.3.fc17.x86_64 ...'
linux /vmlinuz-3.1.0-0.rc9.git0.3.fc17.x86_64
root=UUID=abf1eb35-0fe0-4e2c-8ee5-c6542ace2c85 ro single nouveau.noaccel=1
nouveau.vram_pushbuf=1 nouveau.vram_notify=1 log_buf_len=16M
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.1.0-0.rc9.git0.3.fc17.x86_64.img
}
menuentry 'Linux, with Linux 3.1.0-0.rc10.git0.1.fc17.x86_64' --class gnu-linux
--class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 5fa84efc-2093-49a8-a997-98bb79a345e3
echo 'Loading Linux 3.1.0-0.rc10.git0.1.fc17.x86_64 ...'
linux /vmlinuz-3.1.0-0.rc10.git0.1.fc17.x86_64
root=UUID=abf1eb35-0fe0-4e2c-8ee5-c6542ace2c85 ro nouveau.noaccel=1
nouveau.vram_pushbuf=1 nouveau.vram_notify=1 log_buf_len=16M
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.1.0-0.rc10.git0.1.fc17.x86_64.img
}
menuentry 'Linux, with Linux 3.1.0-0.rc10.git0.1.fc17.x86_64 (recovery mode)'
--class gnu-linux --class gnu --class os {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos5)'
search --no-floppy --fs-uuid --set=root 5fa84efc-2093-49a8-a997-98bb79a345e3
echo 'Loading Linux 3.1.0-0.rc10.git0.1.fc17.x86_64 ...'
linux /vmlinuz-3.1.0-0.rc10.git0.1.fc17.x86_64
root=UUID=abf1eb35-0fe0-4e2c-8ee5-c6542ace2c85 ro single nouveau.noaccel=1
nouveau.vram_pushbuf=1 nouveau.vram_notify=1 log_buf_len=16M
echo 'Loading initial ramdisk ...'
initrd /initramfs-3.1.0-0.rc10.git0.1.fc17.x86_64.img
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda1)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set=root 0A889E4D889E36E3
chainloader +1
}
menuentry "Windows 7 (loader) (on /dev/sda2)" --class windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy --fs-uuid --set=root B020C5A420C571C0
chainloader +1
}
menuentry "Windows Recovery Environment (loader) (on /dev/sda3)" --class
windows --class os {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root F43CED0D3CECCBA4
drivemap -s (hd0) ${root}
chainloader +1
}
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/90_persistent ###
### END /etc/grub.d/90_persistent ###
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
kevin martin <kevintm(a)ameritech.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kevintm(a)ameritech.net
--- Comment #64 from kevin martin <kevintm(a)ameritech.net> 2011-10-31 17:41:52 EDT ---
Still happens with latest rawhide and grub2:
Running Transaction
Updating : kernel-debuginfo-common-x86_64-3.2.0-0.rc0.git1.0.fc17.x86_64
1/19
Updating : kernel-tools-3.2.0-0.rc0.git1.0.fc17.x86_64
2/19
Updating : kernel-tools-devel-3.2.0-0.rc0.git1.0.fc17.x86_64
3/19
Updating : kernel-debuginfo-3.2.0-0.rc0.git1.0.fc17.x86_64
4/19
Installing : kernel-debug-debuginfo-3.2.0-0.rc0.git1.0.fc17.x86_64
5/19
Updating : kernel-tools-debuginfo-3.2.0-0.rc0.git1.0.fc17.x86_64
6/19
Installing : kernel-debug-devel-3.2.0-0.rc0.git1.0.fc17.x86_64
7/19
Updating : kernel-headers-3.2.0-0.rc0.git1.0.fc17.x86_64
8/19
Installing : kernel-devel-3.2.0-0.rc0.git1.0.fc17.x86_64
9/19
Installing : kernel-3.2.0-0.rc0.git1.0.fc17.x86_64
10/19
grubby fatal error: unable to find a suitable template
Installing : kernel-debug-3.2.0-0.rc0.git1.0.fc17.x86_64
11/19
grubby fatal error: unable to find a suitable template
Cleanup : kernel-tools-debuginfo-3.1.0-0.rc10.git0.1.fc17.x86_64
12/19
Cleanup : kernel-tools-devel-3.1.0-0.rc10.git0.1.fc17.x86_64
13/19
Cleanup : kernel-debuginfo-3.1.0-0.rc10.git0.1.fc17.x86_64
14/19
Cleanup : kernel-debuginfo-common-x86_64-3.1.0-0.rc10.git0.1.fc17.x86_64
15/19
Cleanup : kernel-3.1.0-0.rc9.git0.1.fc17.x86_64
16/19
grubby fatal error: unable to find a suitable template
grubby: doing this would leave no kernel entries. Not writing out new config.
Cleanup : kernel-headers-3.1.0-0.rc10.git0.1.fc17.x86_64
17/19
Cleanup : kernel-devel-3.1.0-0.rc9.git0.1.fc17.x86_64
18/19
Cleanup : kernel-tools-3.1.0-0.rc10.git0.1.fc17.x86_64
19/19
Verifying : kernel-tools-debuginfo-3.1.0-0.rc10.git0.1.fc17.x86_64
19/19
VerifyTransaction time: 2.557
Transaction time: 598.320
Removed:
kernel.x86_64 0:3.1.0-0.rc9.git0.1.fc17
kernel-devel.x86_64 0:3.1.0-0.rc9.git0.1.fc17
Installed:
kernel.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-debug.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-debug-debuginfo.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-debug-devel.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-devel.x86_64 0:3.2.0-0.rc0.git1.0.fc17
Updated:
kernel-debuginfo.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-debuginfo-common-x86_64.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-headers.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-tools.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-tools-debuginfo.x86_64 0:3.2.0-0.rc0.git1.0.fc17
kernel-tools-devel.x86_64 0:3.2.0-0.rc0.git1.0.fc17
This happens to be a home compiled kernel (to get rid of the debug code so I
could install akmod-nvidia driver (since there's an unresolved error with
nouveau) so this was a "yum localinstall kernel*rpm". This bug has been open
since 2004?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=246872
Harald Hoyer <harald(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |CURRENTRELEASE
Last Closed| |2011-10-20 04:47:24
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=246879
Paul Howarth <paul(a)city-fan.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |WONTFIX
Last Closed| |2011-10-20 04:37:22
--- Comment #3 from Paul Howarth <paul(a)city-fan.org> 2011-10-20 04:37:22 EDT ---
bittorrent has gone closed source and has been dropped from Fedora in F16, so
this isn't going to get done.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Product: Fedora
Version: rawhide
Component: perl-Archive-Zip
Marcela Mašláňová <mmaslano(a)redhat.com> has canceled Bug Zapper
<triage(a)lists.fedoraproject.org>'s request for needinfo:
Bug 543660: Perl Archive::Zip fails writing to an unseekable file handle after
calling desiredCompressionLevel()
https://bugzilla.redhat.com/show_bug.cgi?id=543660
------- Additional Comments from Marcela Mašláňová <mmaslano(a)redhat.com>
I keep this bug report for tracking progress in upstream.
Product: Fedora
Version: 12
Component: selinux-policy
Simon <simon(a)conditional-fee.co.uk> has canceled Bug Zapper
<triage(a)lists.fedoraproject.org>'s request for needinfo:
Bug 592089: SELinux is preventing /usr/lib/cups/backend/mfp "getattr" access to
device /dev/mfpports/probe.
https://bugzilla.redhat.com/show_bug.cgi?id=592089
------- Additional Comments from Simon <simon(a)conditional-fee.co.uk>
Hello again,
I bought a samsung CLX-6220FX which prints OK but each time I try to use the
smatpanel or unified driver configurater selinux block it:-
SELinux is preventing /opt/Samsung/mfp/bin/Configurator from using the
execstack access on a process.
***** Plugin allow_execstack (53.1 confidence) suggests ********************
If you believe that
None
should not require execstack
Then you should clear the execstack flag and see if
/opt/Samsung/mfp/bin/Configurator works correctly.
Report this as a bug on None.
You can clear the exestack flag by executing:
Do
execstack -c None
***** Plugin catchall_boolean (42.6 confidence) suggests *******************
If you want to allow unconfined executables to make their stack executable.
This should never, ever be necessary. Probably indicates a badly coded
executable, but could indicate an attack. This executable should be reported in
bugzilla
Then you must tell SELinux about this by enabling the 'allow_execstack'
boolean.
Do
setsebool -P allow_execstack 1
***** Plugin catchall (5.76 confidence) suggests ***************************
If you believe that Configurator should be allowed execstack access on
processes labeled unconfined_t by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep Configurator /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Additional Information:
Source Context
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1
023
Target Context
unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1
023
Target Objects Unknown [ process ]
Source Configurator
Source Path /opt/Samsung/mfp/bin/Configurator
Port <Unknown>
Host www.conditional-fee.co.uk
Source RPM Packages
Target RPM Packages
Policy RPM selinux-policy-3.9.7-44.fc14
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name www.conditional-fee.co.uk
Platform Linux www.conditional-fee.co.uk
2.6.35.14-97.fc14.i686.PAE #1 SMP Sat Sep 17
00:22:29 UTC 2011 i686 i686
Alert Count 1
First Seen Sat 15 Oct 2011 17:11:32 BST
Last Seen Sat 15 Oct 2011 17:11:32 BST
Local ID b1f3562c-ec3e-48c8-9798-73102216119f
Raw Audit Messages
type=AVC msg=audit(1318695092.132:2519): avc: denied { execstack } for
pid=14265 comm="Configurator"
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process
type=SYSCALL msg=audit(1318695092.132:2519): arch=i386 syscall=mprotect
success=no exit=EACCES a0=bfb02000 a1=1000 a2=1000007 a3=bfb020ec items=0
ppid=1 pid=14265 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500
sgid=500 fsgid=500 tty=(none) ses=268 comm=Configurator
exe=/opt/Samsung/mfp/bin/Configurator
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=(null)
Hash: Configurator,unconfined_t,unconfined_t,process,execstack
audit2allow
#============= unconfined_t ==============
#!!!! This avc can be allowed using the boolean 'allow_execstack'
allow unconfined_t self:process execstack;
audit2allow -R
#============= unconfined_t ==============
#!!!! This avc can be allowed using the boolean 'allow_execstack'
I want to use the scanning capability but not if the method involves any
security risk (I've got another scanner -not as good)
What are the implications of using execstack -c None
please?
Product: Fedora
Version: 15
Component: anaconda
Chris Murphy <bugzilla(a)colorremedies.com> has canceled Bug Zapper
<triage(a)lists.fedoraproject.org>'s request for needinfo:
Bug 503149: Add features to Anaconda to aid installation on Apple computers
https://bugzilla.redhat.com/show_bug.cgi?id=503149
------- Additional Comments from Chris Murphy <bugzilla(a)colorremedies.com>
This might need a separate bug report but I'll stick it in here for now.
Consistently I'm finding the partition type GUID is wrong in a number of cases:
The first ext4 partition listed in GPT (whether it's the 2nd partition entry or
the 5th) is thus far always the GUID for "EFI System Partition" GUID
C12A7328-F81F-11D2-BA4B-00A0C93EC93B. This is definitely incorrect, it should
be GUID 0FC63DAF-8483-4772-8E79-3D69D8477DE4 "Linux filesystem". The net result
of this bug is that there are two EFI System Partitions on a dual boot system,
one of which is the real EFI System partition, and the other is the partition
mounting as /boot. Probably not a good idea, should be fixed.
Subsequent partitions either ext4, btrfs, or xfs have partition type GUID
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 "Microsoft Windows basic data". This was
done for a long time under MBR, using the same partition type hex code as
Windows but linux filesystems have their own GUID which is
0FC63DAF-8483-4772-8E79-3D69D8477DE4. So it's a minor point, but ought to be
fixed.
"BIOS Boot" has the correct partition type GUID.
"Linux LVM" partitions also have the correct partition type GUID.
Last, all of my comments apply to F16 beta, so the version for this bug should
be changed to 16. Now that I've inundated everyone with multiple comments, I'll
remove the needinfo flag and await comments/questions on next steps.
Product: Fedora
Version: 15
Component: kernel
me(a)ibotty.net has canceled Bug Zapper <triage(a)lists.fedoraproject.org>'s
request for needinfo:
Bug 524458: Macbook Pro 5,5 video does not resume (with and without Nouveau
KMS)
https://bugzilla.redhat.com/show_bug.cgi?id=524458
------- Additional Comments from me(a)ibotty.net
as indicated last year, it did work with some not-so-magic kernel parameters.
in f15 it works out of the box (well: using a newer kernel because of other
bugs, which i can hardly reproduce (it's not my notebook) but which do not
happen with the 3.1rcs.)
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=253635
Jerry Amundson <jamundso(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|jamundso(a)gmail.com |
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
Slawomir Czarko <bugzilla.redhat.com(a)sklep.czarko.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla.redhat.com(a)sklep.c
| |zarko.net
--- Comment #63 from Slawomir Czarko <bugzilla.redhat.com(a)sklep.czarko.net> 2011-10-06 15:37:38 EDT ---
Got it on Fedora 15 when installing kernel-2.6.40.6-0.fc15.i686
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.