On 05/17/2015 02:14 AM, Igor Gnatenko wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1221911
>
> On Sun, May 17, 2015 at 1:59 AM, Antonio Insuasti Recalde
> wrote:
>> Hi folks,
>>
>> I don't know if this is a bug, but when i start a container or execute
>> some command inside of container
restorecon -R -v /var/cache
Should fix the problem. There is a new release of selinux-policy that
hopefully will fix this label permanently.
On 12/21/2014 08:59 AM, Lawrence E Graves wrote:
> SELinux is preventing logrotate from read access on the directory
> /var/cache/dnf.
>
> * Plugin re
On 11/19/2014 12:38 PM, drago01 wrote:
> On Wed, Nov 19, 2014 at 6:19 PM, Daniel J Walsh wrote:
>> On 11/19/2014 09:16 AM, Paul Knox-Kennedy wrote:
>>> On a clean installation built from
>>> Fedora-Live-Workstation-x86_64-21_Beta-4.iso, I installed mongodb-server
>
On 11/19/2014 09:16 AM, Paul Knox-Kennedy wrote:
> On a clean installation built from
> Fedora-Live-Workstation-x86_64-21_Beta-4.iso, I installed mongodb-server
> but it failed to start due to selinux: "SELinux is preventing mongod
> from name_bind access on the tcp_socket port 27017."
>
> Followi
On 08/15/2014 03:34 PM, Robert Moskowitz wrote:
> My cubieboard2 does not have an rtc, so at boot time the clock is at
> the epoche start. Once the network is up, then NTP sets the clock.
>
> So I tried connecting to SSH after the install and got:
>
> Read from socket failed: Connection reset by
On 05/15/2014 11:26 PM, Chris Murphy wrote:
> On May 15, 2014, at 6:32 PM, Adam Williamson wrote:
>
>> On Thu, 2014-05-15 at 18:22 -0600, Chris Murphy wrote:
>>> This happens on both F20 and Rawhide with separately mounted /var.
>>>
>>> [2.839950] f20v.localdomain systemd[1]: Mounting /var...
firefox in Rawhide has become unusable for me also. It seems to have
runaway scripts and hangs all the time. It is asking me to force-kill
it all the time. I have had to switch to chrome, in order to have a
working browser.
On 03/29/2014 11:45 AM, Robert P. J. Day wrote:
> On Sat, 29 Mar 2014,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/27/2014 08:02 AM, Lawrence E Graves wrote:
>
> On 02/26/2014 04:39 PM, Lawrence E Graves wrote:
>> Is anyone aware of the fact that the apcupsd* packages have been in
>> update-testing for about 4 weeks and the fact that is does not work. I
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/16/2014 04:09 PM, Chris Murphy wrote:
>
> On Jan 16, 2014, at 11:57 AM, Michael Schwendt
> wrote:
>
Is this with SELinux enforcing/permissive/disabled? Do you get any
AVC denied messages in the logs?
>>>
>>> For me, yes and no.
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/16/2014 03:52 PM, Michael Schwendt wrote:
> On Thu, 16 Jan 2014 12:28:35 -0800, Adam Williamson wrote:
>
>>> selinux-policy-targeted-3.12.1-116
>
>> perhaps in light of this saga it might be wise to set the autopush
>> threshold for selinux-pol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Usually when you install some of these third party packages, you end up with
mislabeled content in /usr or /var
running restorecon -R -v /usr /var
May cleanup the problems you are seeing.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/2013 02:10 PM, Chuck Forsberg WA7KGX wrote:
> First TC5 attempt from netinst selecting Fedora-20-Beta-TC5-x86_64-DVD.iso
> disk image: Selected creative and dev workstation. No mingw option. No
> scientific-engineering option. Can not confi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/29/2013 03:09 AM, Adam Williamson wrote:
> On Sun, 2013-07-28 at 07:16 -0500, Bruno Wolff III wrote:
>> I've been having sound issues for over a week. The sound devices are not
>> visible to pulseaudio. At first they would be for a while and dis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/02/2013 05:30 AM, Peter Robinson wrote:
> On Tue, Jul 2, 2013 at 10:17 AM, Mateusz Marzantowicz
> wrote:
>> What can I do with this bugs? ABRT says it could not send bug report due
>> to insufficient data. I'm experiencing system freezes twice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/11/2013 08:09 AM, Tom Horsley wrote:
> On Mon, 10 Jun 2013 14:59:51 -0700 Samuel Sieb wrote:
>
>> Check the logs for selinux errors or boot with selinux in permissive
>> mode. You may need to relabel the filesystem.
>
> Yep, it was definitely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/06/2013 12:55 PM, Cristian Sava wrote:
>>> Anyways Crhitian, I have added the allow rules to the base policy to
>>> allow this. You can do this for now by executing
>>>
>>> # grep courier /var/log/audit/audit.log | audit2allow -M mycourier #
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/05/2013 01:59 AM, Cristian Sava wrote:
> On Tue, 2013-06-04 at 11:40 -0400, Daniel J Walsh wrote:
>> On 06/04/2013 05:06 AM, Cristian Sava wrote:
>>> I am trying to activate selinux for my mailserver. It is F19
>>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/2013 05:06 AM, Cristian Sava wrote:
> I am trying to activate selinux for my mailserver. It is F19
> postfix_courier_amavisd-new_clamav_squirrelmail install in a virtual
> environment. All needed is stock or was packaged on F19 (rpmbuild -ta .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/18/2013 10:11 AM, Sérgio Basto wrote:
> On Qui, 2013-04-18 at 09:43 -0400, Daniel J Walsh wrote:
>> On 04/18/2013 09:34 AM, Sérgio Basto wrote:
>>> On Qui, 2013-04-18 at 08:20 -0500, Michael Cronenworth wrote:
>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/18/2013 09:34 AM, Sérgio Basto wrote:
> On Qui, 2013-04-18 at 08:20 -0500, Michael Cronenworth wrote:
>> On 04/18/2013 08:07 AM, Sérgio Basto wrote:
>>> Are using vbox from rpmfusion ?
>>
>> Please see my previous email:
>> http://lists.fedorap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/22/2013 11:13 PM, Ankur Sinha wrote:
> Hi folks,
>
> I sent this mail to devel earlier, and got zilch. Any clues on what's
> wrong? Is the rawhide buildroot borked? Is it a mock bug? How do we test
> builds for rawhide?
>
> I've been having t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2013 03:26 PM, Bruno Wolff III wrote:
> On Thu, Jan 24, 2013 at 14:45:57 -0500, Daniel J Walsh
> wrote:
>>
>> Well we did test this but not on a reboot, actually found the problem
>> early in the morning and fixed it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2013 11:35 AM, Kevin Fenzi wrote:
> On Thu, 24 Jan 2013 10:32:06 -0500 Daniel J Walsh
> wrote:
>
>> Update libselinux. There was a new bug in libselinux that was causing
>> systemd to label stuff incorrectly, it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/24/2013 10:10 AM, Kevin Fenzi wrote:
> On Thu, 24 Jan 2013 00:11:31 -0600 Bruno Wolff III wrote:
>
>> To reboot I need to use the enforcing=0 kernel parameter. Switch to
>> enforcing after booting seems to work. This is filed as bug 903486
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/08/2013 12:17 PM, Ken Dreyer wrote:
> On Tue, Jan 8, 2013 at 10:11 AM, Frank Murphy wrote:
>> Updated selinux* from koji solved it for me:
>> http://koji.fedoraproject.org/koji/buildinfo?buildID=376537
>
> Thank you, you're absolutely right. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/07/2013 05:08 PM, nonamedotc wrote:
>
> On 01/07/2013 11:51 AM, Daniel J Walsh wrote: On 01/06/2013 06:55 PM,
> nonamedotc wrote:
>>>> Could anyone please shed some light on this selinux warning?
>>>>
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/08/2013 01:09 AM, William Morris wrote:
> Hello,
>
> Thank you for taking the time to read this, as I am sure that you get many
> requests from people that would like to join your the Bug Zappers group. I
> come from a varied Linux background s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/06/2013 06:55 PM, nonamedotc wrote:
> Could anyone please shed some light on this selinux warning?
>
> SELinux is preventing /usr/bin/python2.7 from using the execmem access on
> a process.
>
> Plugin: catchall you want to allow python2.7 to ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/2013 11:39 AM, M A Young wrote:
> On Thu, 3 Jan 2013, Daniel J Walsh wrote:
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 01/03/2013 11:05 AM, M A Young wrote:
>>> On Thu, 3 Jan 2013, Dan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/2013 11:05 AM, M A Young wrote:
> On Thu, 3 Jan 2013, Daniel J Walsh wrote:
>
>> What plugin is doing this and what directory is
>> "C:\nppdf32Log\debuglog.txt" being created in ? $HOME?
>
> I think you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/03/2013 07:43 AM, Lawrence Graves wrote:
> SELinux is preventing /usr/lib/nspluginwrapper/npviewer.bin from create
> access on the file C:\nppdf32Log\debuglog.txt.
>
> * Plugin catchall (100. confidence) suggests
> **
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/30/2012 04:17 PM, Ian Pilcher wrote:
> And getting a ton of SELinux AVCs?
>
> According to https://bugzilla.redhat.com/show_bug.cgi?id=872974#c2, the
> openvswitch policy should be in selinux-policy-targeted-
> 3.11.1-66.fc18.noarch, but I'm se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/19/2012 07:47 AM, Lawrence Graves wrote:
> SELinux is preventing systemd-readahe from 'read, open' accesses on the
> file /usr/sbin/consoletype.
>
> * Plugin catchall_labels (83.8 confidence) suggests
>
>
> If you want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/15/2012 06:13 AM, Richard W.M. Jones wrote:
> On Fri, Dec 14, 2012 at 01:17:02PM +, Fedora Rawhide Report wrote:
>> [libguestfs] 1:libguestfs-1.20.0-1.fc19.i686 requires selinux-policy >=
>> 0:3.11.1-63 1:libguestfs-1.20.0-1.fc19.x86_64 requi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2012 11:26 AM, john.flor...@dart.biz wrote:
> Daniel J Walsh wrote on 12/07/2012 10:46:11:
>>
>> On 12/07/2012 08:44 AM, Bruno Wolff III wrote:
>>> On Fri, Dec 07, 2012 at 08:22:10 -0500, john.flor...@dart.biz wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2012 08:44 AM, Bruno Wolff III wrote:
> On Fri, Dec 07, 2012 at 08:22:10 -0500, john.flor...@dart.biz wrote:
>>
>> Thinking selinux might be preventing the relabel from happening (?!?) I
>> rebooted with selinux=0 so that I could reconfig /e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2012 01:46 AM, Ankur Sinha wrote:
> On Mon, 2012-12-03 at 12:53 -0600, Bruno Wolff III wrote:
>> In bohdi, people have reported that -59 fixed the problem going forward.
>> But people already affected need to relabel.
>
> Looks like I got cau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/01/2012 12:58 PM, Adam Williamson wrote:
> Just a heads-up - several reporters (including me) have noticed that they
> can't access 'storage' drives in their systems (disks mounted at non-system
> locations - mine's at /media/Sea500 - to contain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/07/2012 07:27 PM, Ankur Sinha wrote:
> Hi folks,
>
> I upgraded my system from fedora 17 a few days ago. I forgot to change my
> selinux mode to permissive before the update and it took me a while to fix
> my files. I think they're all okay now.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/2012 10:06 AM, Joachim Backes wrote:
> On 10/10/2012 03:59 PM, Daniel J Walsh wrote:
>> On 10/10/2012 09:41 AM, Joachim Backes wrote:
>>> On 10/10/2012 02:38 PM, drago01 wrote:
>>>>> Hi drago01,
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/10/2012 09:41 AM, Joachim Backes wrote:
> On 10/10/2012 02:38 PM, drago01 wrote:
>>> Hi drago01,
>>
>> Hi,
>>
>>> thank you for your answer.
>>>
>>> 1. file ~/.cache/gdm/session.log does not exist
>>
>> If that does not exit than ~/.xsession-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/2012 03:17 PM, Adam Williamson wrote:
> On Tue, 2012-10-09 at 14:51 -0400, Daniel J Walsh wrote:
>> On 10/09/2012 12:46 PM, Adam Williamson wrote:
>>> On Sat, 2012-10-06 at 06:45 -0400, Daniel J Walsh wrote:
>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/09/2012 12:46 PM, Adam Williamson wrote:
> On Sat, 2012-10-06 at 06:45 -0400, Daniel J Walsh wrote:
>> On 10/04/2012 10:12 PM, Adam Williamson wrote:
>>> On Thu, 2012-10-04 at 16:32 -0400, john.flor...@dart.biz wrote:
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/2012 10:12 PM, Adam Williamson wrote:
> On Thu, 2012-10-04 at 16:32 -0400, john.flor...@dart.biz wrote:
>
>> I believe I've already found the problem. On the host running
>> livecd-creator, I'm seeing AVCs like:
>
> Yeah, it's selinux. I'v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/2012 09:49 PM, Tom London wrote:
> On Wed, Oct 3, 2012 at 2:05 PM, Daniel J Walsh wrote:
> On 10/03/2012 08:23 AM, Antonio Olivares wrote:
>>>>
>>>>
>>>>> -Original Message- From: awi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/2012 08:23 AM, Antonio Olivares wrote:
>
>
>> -Original Message- From: awill...@redhat.com Sent: Fri, 28 Sep
>> 2012 16:40:54 -0700 To: test@lists.fedoraproject.org Subject: Re:
>> Shutdown does not work (Gnome version of Alpha)
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/2012 08:39 PM, Ed Greshko wrote:
> On 10/03/2012 02:53 AM, Daniel J Walsh wrote:
>> On 10/01/2012 07:34 PM, Ed Greshko wrote:
>>> On 10/01/2012 10:04 PM, Stephen John Smoogen wrote:
>>>> On 30 September 2012
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/2012 11:54 AM, Kamil Paral wrote:
>>> Dear folks,
>>>
>>> Aside from newer kernels not appearing on Grub Menu, shutdown is not
>>> working. It just logs off and presents the gdm login screen.
>>>
>>> Running new Gnome from Alpha version fu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/01/2012 07:34 PM, Ed Greshko wrote:
> On 10/01/2012 10:04 PM, Stephen John Smoogen wrote:
>> On 30 September 2012 23:09, Ed Greshko wrote:
>>> I just started playing around with firewalld and I found something that
>>> doesn't seem right to me.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/28/2012 07:40 PM, Adam Williamson wrote:
> On Fri, 2012-09-28 at 14:39 -0800, Antonio Olivares wrote:
>> Dear folks,
>>
>> Aside from newer kernels not appearing on Grub Menu, shutdown is not
>> working. It just logs off and presents the gdm lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/25/2012 11:11 AM, john.flor...@dart.biz wrote:
>> From: "Jason L Tibbitts III" I'm something of an
>> idiot when it comes to selinux; I used to know just enough to get a
>> reasonable bug report out, but now I've even forgotten most of that. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/25/2012 08:42 AM, Matthew Miller wrote:
> On Tue, Sep 25, 2012 at 07:21:32AM -0500, Jason L Tibbitts III wrote:
>> You mean, besides the existing "disable dontaudit rules" switch? Just
>> run "semoduile -DB". It's pretty much mandatory to do t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/25/2012 08:42 AM, Matthew Miller wrote:
> On Tue, Sep 25, 2012 at 07:21:32AM -0500, Jason L Tibbitts III wrote:
>> You mean, besides the existing "disable dontaudit rules" switch? Just
>> run "semoduile -DB". It's pretty much mandatory to do t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/24/2012 04:23 PM, "Jóhann B. Guðmundsson" wrote:
> On 09/24/2012 08:16 PM, drago01 wrote:
>> On Mon, Sep 24, 2012 at 10:13 PM, "Jóhann B. Guðmundsson"
>> wrote:
>>> I hereby propose that we default selinux to permissive mode up to
>>> final whi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/2012 02:58 PM, john.flor...@dart.biz wrote:
> Daniel J Walsh wrote on 08/16/2012 14:34:01:
>
>> Fixed in selinux-policy-3.11.1-9.fc18.noarch
>
> Should I be able to grab that from bodhi? If not, where can I get these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/16/2012 01:49 PM, john.flor...@dart.biz wrote:
> My $HOME is (normally) mounted with autofs via NFS, but with F18 I am
> seeing this in my audit.log:
>
> type=AVC msg=audit(1345138563.576:2652): avc: denied { block_suspend }
> for pid=3708 com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/21/2012 09:19 AM, Jonathan Kamens wrote:
> On 05/21/2012 09:16 AM, Daniel J Walsh wrote:
>> It could be SELinux. You should look for its messages in
>> /var/log/audit/audit.log.
> # getenforce Disabled #
>
> jik
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/21/2012 07:22 AM, Jonathan Kamens wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=823485
>
> Anybody else seeing this?
>
> Details:
>
> I am running F17 x86_64 with all updates from updates-testing.
>
> I can't log in. When I click my na
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/2012 01:51 PM, Bruno Wolff III wrote:
> On Wed, May 09, 2012 at 13:31:42 -0400, Tom H wrote:
>> On Wed, May 9, 2012 at 1:08 PM, Bruno Wolff III wrote:
>>> On Wed, May 09, 2012 at 08:19:46 -0400, Tom H
>>> wrote:
Why do have both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/02/2012 06:44 PM, Adam Williamson wrote:
> On Wed, 2012-05-02 at 16:24 -0400, Daniel J Walsh wrote:
>> On 05/02/2012 04:22 PM, Adam Williamson wrote:
>>> On Sat, 2012-04-28 at 20:30 +0100, Frank Murphy wrote:
>>>&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/02/2012 05:08 PM, antonio montagnani wrote:
> Il 02/05/2012 22:54, Daniel J Walsh ha scritto: On 05/02/2012 04:35 PM,
> antonio montagnani wrote:
>>>> Il 02/05/2012 22:24, Daniel J Walsh ha scritto: On 05/02/2012 04:22
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/02/2012 04:35 PM, antonio montagnani wrote:
> Il 02/05/2012 22:24, Daniel J Walsh ha scritto: On 05/02/2012 04:22 PM,
> Adam Williamson wrote:
>>>> On Sat, 2012-04-28 at 20:30 +0100, Frank Murphy wrote:
>>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/02/2012 04:22 PM, Adam Williamson wrote:
> On Sat, 2012-04-28 at 20:30 +0100, Frank Murphy wrote:
>> On 28/04/12 20:26, antonio wrote:
>>> I upgraded from F-16 to F-17 Beta, then upgraded to find that I
>>> couldn't delete my own files!!! after d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/27/2012 12:10 PM, Adam Williamson wrote:
> On Thu, 2012-04-26 at 15:18 -0400, Daniel J Walsh wrote:
>
>>>>> selinux-policy needs a newer checkpolicy
>>> Thank you.
>> I believe the checkpolicy and libsepol h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/26/2012 01:50 PM, G.Wolfe Woodbury wrote:
> On 04/26/2012 01:45 PM, Dennis Gilmore wrote:
>>> Can someone provide an update on the build problems that are causing
>>> this?
>>>
>
>>> yum.Errors.YumRPMCheckError: [u'ERROR with transaction check
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/22/2012 08:42 PM, Fernando Cassia wrote:
> On Sun, Apr 22, 2012 at 18:34, Adam Williamson
> wrote:
>> That is not 'the usual procedure'. The usual procedure is 'setenforce
>> Permissive', boot with 'enforcing=0' or 'selinux=0' (but the last is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somehow /etc/ld.so.cache file got mislabeled? Was this an initial install?
Install from livecd? Running restorecon on /etc/ld.so.cache will fix the
label, as the setroubleshoot tells you. Does the file become mislabeled again?
If we could figure out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/19/2012 12:47 PM, Frank Murphy wrote:
> On 19/04/12 17:36, Fernando Cassia wrote:
>> Should I be worried about this?
>>
>> SELinux is preventing useradd from write access on the directory /run.
>
>
> https://admin.fedoraproject.org/mailman/lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/16/2012 07:22 AM, Pedro Francisco wrote:
> On Mon, Apr 16, 2012 at 2:28 AM, R P Herrold wrote:
>> On Sun, 15 Apr 2012, Pedro Francisco wrote:
>>
>>> wvdial is crashing when trying to start a connection. Modem =
>>> /dev/ttyACM0.
>>>
>>> $ sud
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/23/2012 04:03 PM, Joachim Backes wrote:
> On 02/23/2012 08:13 PM, Daniel J Walsh wrote:
>> On 02/23/2012 05:31 AM, Joachim Backes wrote:
>>> On 02/23/2012 08:32 AM, Joachim Backes wrote:
>>>> Hi,
>>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/23/2012 05:31 AM, Joachim Backes wrote:
> On 02/23/2012 08:32 AM, Joachim Backes wrote:
>> Hi,
>>
>> I made a fresh F17 desktop (gnome3) installation on my box to a
>> real partition with F17/Alpha/RC4: No problems during install,
>> the system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/2012 05:33 PM, Michel Alexandre Salim wrote:
> On 01/27/2012 04:08 PM, Daniel J Walsh wrote:
>> On 01/27/2012 08:10 AM, Harald Hoyer wrote:
>>> The packages, which are about to land in rawhide, are at this
>>> mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/27/2012 08:10 AM, Harald Hoyer wrote:
> Hello Testers and rawhide Users,
>
> Fedora 17 will locate the entire base operating system in /usr. The
> directories /bin, /sbin, /lib, /lib64 will only be symlinks: /bin →
> /usr/bin /sbin → /usr/sbin /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/31/2011 11:27 AM, Antonio Olivares wrote:
> Dear folks,
>
> I have installed Fedora 16 on an x86_64 machien and I can't install
> wine:
>
> [root@localhost ~]# yum install wine Loaded plugins: langpacks,
> presto, refresh-packagekit Setting up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/06/2011 03:08 AM, Adam Pribyl wrote:
> On Wed, 5 Oct 2011, Janina Sajka wrote:
>
>> Janina Sajka writes:
>>> I can't be the only one who's run into this?
>>>
>>>
>>> My procmail setup has not changed fundamentally in well over a
>>> decade. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/2011 07:19 PM, Antonio Olivares wrote:
>
>
> --- On Wed, 10/5/11, Daniel J Walsh wrote:
>
>> From: Daniel J Walsh
>> Subject: Re: oh no something has gone wrong ... :( f16 beta
>> To: "For testing and q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/04/2011 09:24 PM, Antonio Olivares wrote:
>
>
> --- On Tue, 10/4/11, Antonio Olivares
> wrote:
>
>> From: Antonio Olivares Subject: oh no
>> something has gone wrong ... :( f16 beta To: "fedora-test-list"
>> Date: Tuesday, October 4, 2011,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/09/2011 07:42 AM, Michael Schwendt wrote:
> On Fri, 09 Sep 2011 07:28:17 -0400, DJW (Daniel) wrote:
>
>>> 3) NFS file locking service fails to start. I haven't messed
>>> with it at all. The recent update (marked stable meanwhile with
>>> 0 karm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/09/2011 07:13 AM, Michael Schwendt wrote:
> The list of what today's Yum update installed is below.
>
> 1) "Removable devices" icon at the bottom in GNOME Shell. It lists
> my LUKS /home partition as removable. Left-clicking it obviously
> doesn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/24/2011 03:55 AM, Jurgen Kramer wrote:
> I've seen this with all alpha RC's and now with F16 alpha. At
> first bootup a selinux targeted policy label is required. Is this
> as designed?
>
> Jurgen
>
no. It is a bug.
-BEGIN PGP SIGNATURE---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2011 09:24 PM, Neal Becker wrote:
> I can't seem to get F15 setup as backuppc client. I'm using the same method
> I
> used under F14 (ssh from user backuppc on server to root on client). Copied
> backupc dsa key from server to authorized_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/13/2011 05:01 PM, James Laska wrote:
> On Fri, 2011-05-13 at 15:39 +0200, Gianluca Cecchi wrote:
>> On Fri, May 13, 2011 at 2:56 PM, Gianluca Cecchi
>> wrote:
>>> Here is a video booting with "S" instead of "rhgb quiet"
>>>
>>> https://docs.goog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/27/2011 11:51 AM, Per Bothner wrote:
> On 04/27/2011 05:22 AM, Daniel J Walsh wrote:
>> On 04/27/2011 02:45 AM, Per Bothner wrote:
>>> (I'm still having problems with symlinks from /var/www/html
>>> into /home.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/27/2011 08:51 AM, Manilal K M wrote:
> On 27 April 2011 17:52, Daniel J Walsh wrote:
>> You could try with permissive mode, by adding enforcing=0 to the kernel
>> boot line in grub, to see if this is an SELinux problem. A new SE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/27/2011 02:45 AM, Per Bothner wrote:
> On 04/26/2011 11:22 PM, Manilal K M wrote:
>> Hello all,
>>I have upgraded my desktop to Fedora 15 through YUM. The machine
>> boots fine, but after starting all the services it hangs with a blue
>> scre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/15/2011 10:04 AM, James Laska wrote:
> On Thu, 2011-04-14 at 18:30 -0600, Tim Flink wrote:
>> I just noticed this on a fresh install of F15 from the Beta RC2 media and
>> I'm not sure if there is a problem.
>>
>> I have separate LVs for home and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/14/2011 12:33 AM, Lawrence E Graves wrote:
> SELinux is preventing /sbin/iwconfig from using the sys_module capability.
> * Plugin sys_module (99.5 confidence) suggests *
> If you do not believe that /sbin/iwconfig s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2011 04:16 PM, Gregory Woodbury wrote:
>
>
> On Wed, Apr 13, 2011 at 3:58 PM, Daniel J Walsh <mailto:dwa...@redhat.com>> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2011 03:30 PM, Gregory Woodbury wrote:
> Test installs and updates in VBox guests are denied permission to
> shutdown or restart
> by the latest SELinux policy.
>
> setenforce permissive allows shutdown and restart to occur.
>
> --
> G.Wolf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/2011 02:34 PM, Adam Williamson wrote:
> On Tue, 2011-04-05 at 14:27 -0400, Daniel J Walsh wrote:
>
>> selinux-policy-3.9.16-12.fc15 and systemd-23-1.fc15 should allow the
>> system to boot in enforcing mode, althou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/2011 02:15 PM, James Laska wrote:
> On Tue, 2011-04-05 at 14:07 -0400, Kamil Paral wrote:
If you have a moment, and spare hardware/guest, please add karma
feedback to:
*
https://admin.fedoraproject.org/updates/a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2011 12:20 PM, Michał Piotrowski wrote:
> W dniu 31 marca 2011 18:18 użytkownik Daniel J Walsh
> napisał:
> [..]
>> Well if you don't have /etc/selinux/config then booting without
>> selinux=0 will cause the system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2011 12:14 PM, Michał Piotrowski wrote:
> W dniu 31 marca 2011 18:09 użytkownik Joachim Backes
> napisał:
>> On 03/31/2011 05:50 PM, Michał Piotrowski wrote:
>>>
>>> W dniu 31 marca 2011 17:39 użytkownik Joachim Backes
>>> napisał:
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/31/2011 10:15 AM, Joachim Backes wrote:
> Hi all,
> after having updated to the most recent packages (including update to
> systemd-21-2.fc15.x86_64), I got a lot of SElinux error messages during
> boot:
>
> Failed to load SElinux policy
> Faile
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2011 11:23 AM, Panu Matilainen wrote:
> On 03/14/2011 01:49 PM, Jon Stanley wrote:
>> On Mon, Mar 14, 2011 at 7:40 AM, Joachim Backes
>> wrote:
>>
>>> I saw that in F15 ping must be started with root rights, otherwhise I get:
>>>
>>> ping: i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/03/2010 06:57 PM, Antonio Olivares wrote:
> Dear fellow tests,
>
> I see several sealerts aside from dracut error:
>
> I tried to send in report via bugzilla, but forgot my password :(
>
> I got this:
>
> browser.py:277:row_activated:TypeErr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/01/2010 03:04 AM, cornel panceac wrote:
> 2010/11/1 cornel panceac
>
>>
>>
>> 2010/10/29 Daniel J Walsh
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>>
>>> Hash: SHA1
>>>
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/29/2010 02:48 AM, cornel panceac wrote:
> why is the selinux relabel required when the "Superblock last mount/write is
> in the future" error is fixed?
>
>
No clue. Who says it is? Do you have a bugzilla reference?
-BEGIN PGP SIGNATURE---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/18/2010 12:42 PM, Jurgen Kramer wrote:
> On Wed, 2010-08-18 at 09:29 -0400, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 08/17/2010 05:16 PM, Adam Williamson wrote:
>>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/17/2010 05:16 PM, Adam Williamson wrote:
> On Tue, 2010-08-17 at 19:56 +0200, Jurgen Kramer wrote:
>> I've just did a fresh install of F14alpha RC4 to see if I could
>> reproduce a bug. When checking /var/log/messages a see a ton of these:
>>
>>
100 matches
Mail list logo
