On 06/22/15 13:34, Bruno Wolff III wrote:
> On Mon, Jun 22, 2015 at 12:50:54 +0800,
> Ed Greshko wrote:
>> FWIW, also have a laptop running F22 and fully updated. Currently at
>> NetworkManager-1.0.2-1.fc22.x86_64 which I believe is the latest and I'm not
>> having any difficulties with my lo
On Mon, Jun 22, 2015 at 12:50:54 +0800,
Ed Greshko wrote:
FWIW, also have a laptop running F22 and fully updated. Currently at
NetworkManager-1.0.2-1.fc22.x86_64 which I believe is the latest and I'm not
having any difficulties with my lo interface.
I'm running NetworkManager-1.0.4-0.1.gi
Hi,
Thanks Sam, Tom and Ranjan!
Going further:
In /etc/selinux/config
I set
SELINUX=disabled
Which means that I do not use in fact SElinux, so it seems to me.
So will it be OK to run:
rpm -e selinux-policy-targeted
rpm -e selinux-policy
Regards,
Kevin
On Sat, Jun 20, 2015 at 3:26 AM, Ranjan
On 06/22/15 12:31, Bruno Wolff III wrote:
> I am still investigating this, but I have an f22 laptop that is only getting
> an IP6 address set up on the loopback interface. I noticed this because I run
> a local resolver on 127.0.0.1 and connections to it stopped working over
> night (after a reb
Allegedly, on or about 21 June 2015, Kevin Fenzi sent:
> It likely can, but even easier is to just use the 'fatrace'
> utility. ;)
>
> fatrace - Reports file access events from all running processes
LOL, do people go out of their way to name things with a pun (fat race),
or is just luck? ;-)
I am still investigating this, but I have an f22 laptop that is only
getting an IP6 address set up on the loopback interface. I noticed this
because I run a local resolver on 127.0.0.1 and connections to it stopped
working over night (after a reboot). The was a NetworkManager update before
the
OK, BZ review requests are in for pdf-stapler:
https://bugzilla.redhat.com/show_bug.cgi?id=1234210 and for PyPDF2:
https://bugzilla.redhat.com/show_bug.cgi?id=1234208
Currently, pdf-stapler is set to run using pyPdf which exists on Fedora, but I
am not comfortable with it, because the software
jd1008 writes:
On 06/21/2015 07:46 PM, Sam Varshavchik wrote:
jd1008 writes:
On 06/21/2015 06:13 PM, Sam Varshavchik wrote:
After updating to F22, after the system is up for some period of time, I
have not determine for how long, looks like something removes
/var/run/syslogd.pid
Con
On 06/21/2015 07:46 PM, Sam Varshavchik wrote:
jd1008 writes:
On 06/21/2015 06:13 PM, Sam Varshavchik wrote:
After updating to F22, after the system is up for some period of
time, I have not determine for how long, looks like something
removes /var/run/syslogd.pid
Consequently, logrotat
Ed Greshko writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/22/15 08:13, Sam Varshavchik wrote:
> After updating to F22, after the system is up for some period of time, I
have not determine for how long, looks like something removes
/var/run/syslogd.pid
First of all, I find th
jd1008 writes:
On 06/21/2015 06:13 PM, Sam Varshavchik wrote:
After updating to F22, after the system is up for some period of time, I
have not determine for how long, looks like something removes
/var/run/syslogd.pid
Consequently, logrotate eventually rotates /var/log/messages to
/var
On 06/21/2015 06:45 PM, Kevin Fenzi wrote:
On Sun, 21 Jun 2015 18:40:13 -0600
jd1008 wrote:
Some years ago, I wrote a subsystem in the BSD kernel (Not FreeBSD)
that actually did just that - every file access (even over nfs) was
audited and saved in an audit logfile, with an app that viewed o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/22/15 08:13, Sam Varshavchik wrote:
> After updating to F22, after the system is up for some period of time, I have
> not determine for how long, looks like something removes /var/run/syslogd.pid
First of all, I find this odd. The update to F
On Sun, 21 Jun 2015 18:40:13 -0600
jd1008 wrote:
> Some years ago, I wrote a subsystem in the BSD kernel (Not FreeBSD)
> that actually did just that - every file access (even over nfs) was
> audited and saved in an audit logfile, with an app that viewed or
> printed that log file.
> I do not know
On 06/21/2015 06:33 PM, Tom Horsley wrote:
On Sun, 21 Jun 2015 20:13:00 -0400
Sam Varshavchik wrote:
After updating to F22, after the system is up for some period of time, I
have not determine for how long, looks like something removes
/var/run/syslogd.pid
Someone was wondering what good aud
On Sun, 21 Jun 2015 20:13:00 -0400
Sam Varshavchik wrote:
> After updating to F22, after the system is up for some period of time, I
> have not determine for how long, looks like something removes
> /var/run/syslogd.pid
Someone was wondering what good auditd was the other day.
I believe I rea
On 06/21/2015 06:13 PM, Sam Varshavchik wrote:
After updating to F22, after the system is up for some period of time,
I have not determine for how long, looks like something removes
/var/run/syslogd.pid
Consequently, logrotate eventually rotates /var/log/messages to
/var/log/messages-mm
On 06/21/2015 06:13 PM, Sam Varshavchik wrote:
After updating to F22, after the system is up for some period of time,
I have not determine for how long, looks like something removes
/var/run/syslogd.pid
Consequently, logrotate eventually rotates /var/log/messages to
/var/log/messages-mm
After updating to F22, after the system is up for some period of time, I
have not determine for how long, looks like something removes
/var/run/syslogd.pid
Consequently, logrotate eventually rotates /var/log/messages to
/var/log/messages-mmdd (same for several other /var/log files), but
On Sun, 21 Jun 2015 14:18:21 -0500
Ranjan Maitra wrote:
> On Sun, 21 Jun 2015 08:18:09 -0600 Kevin Fenzi
> wrote:
>
> > On Sun, 21 Jun 2015 09:14:16 -0500
> > Ranjan Maitra wrote:
> >
> > > OK, does this mean that we have to wait for Philip Stark to bring
> > > out stapler under python3 (whic
On Sun, 21 Jun 2015 08:18:09 -0600 Kevin Fenzi wrote:
> On Sun, 21 Jun 2015 09:14:16 -0500
> Ranjan Maitra wrote:
>
> > OK, does this mean that we have to wait for Philip Stark to bring out
> > stapler under python3 (which he plans to do -- I can ask him about
> > progress)?
>
> No. It just me
Made the test.
If I try to install cockpit, it tries to pull lvm2 along the ride
If I try to install docker, it is ok, it does not try to pull lvm2 along
for the ride.
Already added a bug report to bugzilla about it.
Interestingly, cockpit also tries to bring docker along
JP
On Sat, Jun 20, 201
On Sun, 21 Jun 2015 09:14:16 -0500
Ranjan Maitra wrote:
> OK, does this mean that we have to wait for Philip Stark to bring out
> stapler under python3 (which he plans to do -- I can ask him about
> progress)?
No. It just means you should 'BuildRequires: python2-devel'
> But isn't it odd that
On Sun, 21 Jun 2015 08:03:47 -0600 Kevin Fenzi wrote:
> On Sun, 21 Jun 2015 15:29:13 +0200
> Suvayu Ali wrote:
>
> > On Sun, Jun 21, 2015 at 07:52:11AM -0500, Ranjan Maitra wrote:
> > > Any ideas on why pdf-stapler does not build for f22 and f23 but
> > > does for rawhide?
> >
> > [...chomp.
On Sun, 21 Jun 2015 15:29:13 +0200
Suvayu Ali wrote:
> On Sun, Jun 21, 2015 at 07:52:11AM -0500, Ranjan Maitra wrote:
> > Any ideas on why pdf-stapler does not build for f22 and f23 but
> > does for rawhide?
>
> [...chomp...chomp...chomp...]
>
> > > Where does one find the build.log? Here is
On Sun, Jun 21, 2015 at 07:52:11AM -0500, Ranjan Maitra wrote:
> Any ideas on why pdf-stapler does not build for f22 and f23 but does for
> rawhide?
[...chomp...chomp...chomp...]
> > Where does one find the build.log? Here is the URL for the failed build on
> > F22:
> >
> > http://koji.fedor
Any ideas on why pdf-stapler does not build for f22 and f23 but does for
rawhide?
On Sat, 20 Jun 2015 11:39:38 -0500 Ranjan Maitra
wrote:
> Kevin,
>
> Thanks!
>
> On Sat, 20 Jun 2015 09:49:39 -0600 Kevin Fenzi wrote:
>
> > On Fri, 19 Jun 2015 23:16:59 -0500
> > Ranjan Maitra wrote:
> >
On Sun, 2015-06-21 at 05:27 +0200, Ralf Corsepius wrote:
> On 06/20/2015 08:19 PM, Patrick O'Callaghan wrote:
> > On Sat, 2015-06-20 at 15:02 +0200, Ralf Corsepius wrote:
> > > C.f. the threat starting at
> >
> > Er, I think you mean thread. You had me worried for a minute :-)
>
> Yeah, sorry ...
Hi all,
anybody sees this too:
I'm running f22 (gnome3 desktop, nautilus as file manager). It happens
almost always that nautilus does not respond to a double click on icons
in some folder window. Trying to change the mouse behaviour by
gnome-control-center was unseccessful.
All updates are inst
29 matches
Mail list logo
