On 4/19/20 12:57 AM, Sreyan Chakravarty wrote:
> Although I was testing with F32 beta, so maybe there has been an
update that fixed it in F31.
I thought Fedora 32 would contain all the fixes of Fedora 31 even if it
was in beta.
No, because there's a freeze at each stage where no updates are
> Although I was testing with F32 beta, so maybe there has been an update
that fixed it in F31.
I thought Fedora 32 would contain all the fixes of Fedora 31 even if it was
in beta.
On Sun, Apr 19, 2020 at 11:20 AM Samuel Sieb wrote:
> On 4/18/20 12:05 PM, Sreyan Chakravarty wrote:
> > > That'
On 4/18/20 12:05 PM, Sreyan Chakravarty wrote:
> That's because you already added the selinux changes to fix that.
I didn't though. It works automatically, the only difference between now
and then is that I am using the command systemctl hibernate to trigger
hibernation. Before, I had set "On
> That's because you already added the selinux changes to fix that.
I didn't though. It works automatically, the only difference between now
and then is that I am using the command systemctl hibernate to trigger
hibernation. Before, I had set "On Power Button Press: Hibernate" from
Gnome Power Opt
On 4/18/20 6:20 AM, Sreyan Chakravarty wrote:
On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
After a lot of experimentation, I did manage to get swap file
hibernation to work.
The dracut module for resuming is, for some reason, not enabled by
default. (At least on the minimal install that I trie
On 4/18/20 1:46 AM, Sreyan Chakravarty wrote:
Also could you tell me where did you get the list of dracut modules from ?
dracut --list-modules
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fe
On 4/18/20 2:33 AM, Sreyan Chakravarty wrote:
On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
After a lot of experimentation, I did manage to get swap file
hibernation to work.
The dracut module for resuming is, for some reason, not enabled by
default. (At least on the minimal install that I trie
On 4/18/20 1:51 AM, Patrick O'Callaghan wrote:
On Fri, 2020-04-17 at 15:57 -0700, Samuel Sieb wrote:
On 4/17/20 2:36 PM, Patrick O'Callaghan wrote:
On Fri, 2020-04-17 at 13:21 -0700, Samuel Sieb wrote:
From the header of that man page, it's an "introduction to boot time
parameters", not an
> On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
>
> After a lot of experimentation, I did manage to get swap file
> hibernation to work.
> The dracut module for resuming is, for some reason, not enabled by
> default. (At least on the minimal install that I tried. Maybe because
> I didn't crea
> On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
>
> After a lot of experimentation, I did manage to get swap file
> hibernation to work.
> The dracut module for resuming is, for some reason, not enabled by
> default. (At least on the minimal install that I tried. Maybe because
> I didn't crea
On Fri, 2020-04-17 at 15:57 -0700, Samuel Sieb wrote:
> On 4/17/20 2:36 PM, Patrick O'Callaghan wrote:
> > On Fri, 2020-04-17 at 13:21 -0700, Samuel Sieb wrote:
> > > From the header of that man page, it's an "introduction to boot time
> > > parameters", not an exhaustive summary. As far as I ca
> On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
>
> After a lot of experimentation, I did manage to get swap file
> hibernation to work.
> The dracut module for resuming is, for some reason, not enabled by
> default. (At least on the minimal install that I tried. Maybe because
> I didn't crea
On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
I have just configured a 8GB swap file on my Fedora 31 laptop. But it
seems that SELinux is blocking access to the swap file.
After a lot of experimentation, I did manage to get swap file
hibernation to work.
The dracut module for resuming is, for
On 4/17/20 2:36 PM, Patrick O'Callaghan wrote:
On Fri, 2020-04-17 at 13:21 -0700, Samuel Sieb wrote:
From the header of that man page, it's an "introduction to boot time
parameters", not an exhaustive summary. As far as I can tell, it is
valid to use a swap file for hibernation. That paramet
On Fri, 2020-04-17 at 13:21 -0700, Samuel Sieb wrote:
> On 4/17/20 9:13 AM, Patrick O'Callaghan wrote:
> > On Fri, 2020-04-17 at 15:37 +, Sreyan Chakravarty wrote:
> > > > On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
> > > >
> > > > It has to be a partition. A file can be on any kind
On 4/17/20 9:13 AM, Patrick O'Callaghan wrote:
On Fri, 2020-04-17 at 15:37 +, Sreyan Chakravarty wrote:
On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
It has to be a partition. A file can be on any kind of filesystem, so
how would the resume function know what to do?
From systemd-h
> There is no corresponding entry for resume_offset. I don't know if that's
> because
> Fedora doesn't support it.
>
> poc
Let me confirm this is some of the Arch distros. You may be right.
Give me some time.
___
users mailing list -- users@lists.fedo
On Fri, 2020-04-17 at 15:37 +, Sreyan Chakravarty wrote:
> > On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
> >
> > It has to be a partition. A file can be on any kind of filesystem, so
> > how would the resume function know what to do?
> >
> > From systemd-hibernate-resume(8):
> >
>
On Fri, 2020-04-17 at 15:37 +, Sreyan Chakravarty wrote:
> > On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
> >
> > It has to be a partition. A file can be on any kind of filesystem, so
> > how would the resume function know what to do?
> >
> > From systemd-hibernate-resume(8):
> >
>
On Fri, 17 Apr 2020 at 12:37, Sreyan Chakravarty wrote:
> > On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
> >
> > It has to be a partition. A file can be on any kind of filesystem, so
> > how would the resume function know what to do?
> >
> > From systemd-hibernate-resume(8):
> >
> > syst
> On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
>
> It has to be a partition. A file can be on any kind of filesystem, so
> how would the resume function know what to do?
>
> From systemd-hibernate-resume(8):
>
> systemd-hibernate-resume@.service initiates the resume from hibernation. It
I am really confused as to why you can't use a Hibernate file.
On Fri, Apr 17, 2020 at 5:43 AM Samuel Sieb wrote:
> On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
> > I have just configured a 8GB swap file on my Fedora 31 laptop. But it
> > seems that SELinux is blocking access to the swap file.
https://wiki.archlinux.org/index.php/Power_management/Suspend_and_hibernate#Hibernation_into_swap_file
The Arch Wiki clearly describes that you can Hibernate into a swap file by
giving the resume_offset.
Is there any reason that using a Swap file is illegal for Hibernation ?
On Fri, Apr 17, 202
On Fri, 2020-04-17 at 01:10 -0700, Samuel Sieb wrote:
> On 4/17/20 1:07 AM, Patrick O'Callaghan wrote:
> > On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
> > > On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
> > > > I have just configured a 8GB swap file on my Fedora 31 laptop. But it
> > > >
On 4/17/20 1:07 AM, Patrick O'Callaghan wrote:
On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
I have just configured a 8GB swap file on my Fedora 31 laptop. But it
seems that SELinux is blocking access to the swap file.
Can you hibernate to
On Thu, 2020-04-16 at 17:12 -0700, Samuel Sieb wrote:
> On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
> > I have just configured a 8GB swap file on my Fedora 31 laptop. But it
> > seems that SELinux is blocking access to the swap file.
>
> Can you hibernate to a swap *file*? I thought it had to
On 4/13/20 9:51 AM, Sreyan Chakravarty wrote:
I have just configured a 8GB swap file on my Fedora 31 laptop. But it
seems that SELinux is blocking access to the swap file.
Can you hibernate to a swap *file*? I thought it had to be a partition.
How would you set up the resume line for that?
On Thu, Apr 16, 2020 at 12:33 PM Sreyan Chakravarty
wrote:
> > On Mon, Apr 13, 2020 at 6:56 PM Sreyan Chakravarty >
> > wrote:
> >
> > Hi,
> >
> > There has already been reported a bugzilla:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1797543
> >
> > A new domain is needed to confine sys
> On Mon, Apr 13, 2020 at 6:56 PM Sreyan Chakravarty wrote:
>
> Hi,
>
> There has already been reported a bugzilla:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1797543
>
> A new domain is needed to confine systemd-sleep. As a temporary workaround,
> you can create a file with the following
On 14.04.20 12:49, Markus Schönhaber wrote:
...
sudo ausearch -c 'systemd-sleep' --raw | audit2allow -M my-systemdsleep
That way, ausearch will run with elevated privileges but audit2allow
will not. That's probably not what you intended.
yup, thanks for the hint.
--
sixpack13
_
13.04.20, 19:28 CEST sixpack13:
> and what happens if you perform the above two commands (everyone with
> "sudo" prefixed)
>
> sudo ausearch -c 'systemd-sleep' --raw | audit2allow -M my-systemdsleep
That way, ausearch will run with elevated privileges but audit2allow
will not. That's probably n
On Mon, Apr 13, 2020 at 8:23 PM Sreyan Chakravarty
wrote:
> Edit:
> > The message from the troubleshooter suggests that you run two commands
> > to get around the issue until it's fixed. Just follow them and you'll
> > be OK.
>
>
Can you please explain what they are doing, I don't know anything
On 04/13/2020 12:20 PM, Sreyan Chakravarty wrote:
Can you please explain what they are doing, I don't know anything about
SELinux.
Good question. The first command creates an exception for SELinux that
allows your system to work until the bug is fixed and the second one
installs it. I'm n
Edit:
> The message from the troubleshooter suggests that you run two commands
> to get around the issue until it's fixed. Just follow them and you'll
> be OK.
Can you please explain what they are doing, I don't know anything about
SELinux.
Also how do I reverse the commands once the bug is fixe
Can you please explain what they are doing, I don't know anything about
SELinux.
Also how do I reverse the commands once the bug is fixed in upstream ?
On Mon, Apr 13, 2020 at 11:39 PM Joe Zeff wrote:
> On 04/13/2020 11:57 AM, Zdenek Pytela wrote:
> > I don't know a whole lot about SELinux, do
Could you please explain what:
(allow init_t swapfile_t (file (getattr open read ioctl lock)))
is doing ?
Am I suppose to paste the above as is in the file ? is swapfile_t the name
of my swap file or is it a SELinux attribute ?
On Mon, Apr 13, 2020 at 11:29 PM Zdenek Pytela wrote:
>
>
> On Mon
I saw a pull request in the comments of the bug, did that solve the problem?
On Mon, Apr 13, 2020 at 11:29 PM Zdenek Pytela wrote:
>
>
> On Mon, Apr 13, 2020 at 6:56 PM Sreyan Chakravarty
> wrote:
>
>> I have just configured a 8GB swap file on my Fedora 31 laptop. But it
>> seems that SELinux i
On 04/13/2020 11:57 AM, Zdenek Pytela wrote:
I don't know a whole lot about SELinux, do I have to add a label or
something?
The message from the troubleshooter suggests that you run two commands
to get around the issue until it's fixed. Just follow them and you'll
be OK.
___
On Mon, Apr 13, 2020 at 6:56 PM Sreyan Chakravarty
wrote:
> I have just configured a 8GB swap file on my Fedora 31 laptop. But it
> seems that SELinux is blocking access to the swap file.
>
> SELinux is preventing systemd-sleep from read access on the file
> fedora.swap.
>
> * Plugin catchal
On 13.04.20 19:00, Sreyan Chakravarty wrote:
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'systemd-sleep' --raw | audit2allow -M my-systemdsleep
# semodule -X 300 -i my-systemdsleep.pp
...
and
Is there no way to hibernate using SELinux Enforcing ??
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-
Look like is an existing bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1797543
In SELinux are there any ways of adding domains ?
On Mon, Apr 13, 2020 at 10:21 PM Sreyan Chakravarty
wrote:
> I have just configured a 8GB swap file on my Fedora 31 laptop. But it
> seems that SELinux is blocking
I have just configured a 8GB swap file on my Fedora 31 laptop. But it seems
that SELinux is blocking access to the swap file.
SELinux is preventing systemd-sleep from read access on the file
fedora.swap.
* Plugin catchall (100. confidence) suggests
**
If you believe
43 matches
Mail list logo
