Document Viewer 2.28.2 wrote:
The file could not be saved as “file:///home/hennebry/...
Failed to create file “/tmp/evince-8622/saveacopy-4.ECDEYW”: No such file or
directory
I get that rather a lot. Can workaround with mkdir /tmp/evince-8622 , but would rather not need to. Any idea what is going on and how I stop it?
I'm running xfce 4 on centos 6.2 . [hennebry@96-18-56-186 t2]$ uname -a Linux 96-18-56-186.cpe.cableone.net 2.6.32-279.22.1.el6.i686 #1 SMP Wed Feb 6 00:31:03 UTC 2013 i686 i686 i386 GNU/Linux [hennebry@96-18-56-186 t2]$
Michael Hennebry wrote:
Document Viewer 2.28.2 wrote:
The file could not be saved as “file:///home/hennebry/...
Failed to create file “/tmp/evince-8622/saveacopy-4.ECDEYW”: No such file or
directory
I get that rather a lot. Can workaround with mkdir /tmp/evince-8622 , but would rather not need to. Any idea what is going on and how I stop it?
Doesn't file->save a copy->menu to save offer you a way to name/put in a directory?
mark
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
Document Viewer 2.28.2 wrote:
The file could not be saved as “file:///home/hennebry/...
Failed to create file “/tmp/evince-8622/saveacopy-4.ECDEYW”: No such file or
directory
I get that rather a lot. Can workaround with mkdir /tmp/evince-8622 , but would rather not need to. Any idea what is going on and how I stop it?
Doesn't file->save a copy->menu to save offer you a way to name/put in a directory?
Yes. That is what gives me the message.
On Mon, 10 Jun 2013, Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
That is what gives me the message.
Do you have write permission in the directory where you are trying to save the file?
Yes. The workaround is successful. Its necessity is annoying.
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
That is what gives me the message.
Do you have write permission in the directory where you are trying to save the file?
And I trust the filesystem isn't full? Or is selinux enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
That is what gives me the message.
Do you have write permission in the directory where you are trying to save the file?
And I trust the filesystem isn't full? Or is selinux enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before? Also, do you have any idea why it was trying to save it in a non-existent directory?
mark
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
That is what gives me the message.
Do you have write permission in the directory where you are trying to save the file?
And I trust the filesystem isn't full? Or is selinux enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before?
I have not rebooted since the last evince problem, so the selinux initialized message from dmesg in another post should be from the most recent boot and before the evince message. No AVCs.
Also, do you have any idea why it was trying to save it in a non-existent directory?
Just that it appears to be intended as a temporay location. The one I made is empty.
On Mon, 10 Jun 2013, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
That is what gives me the message.
Do you have write permission in the directory where you are trying to save the file?
And I trust the filesystem isn't full? Or is selinux enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before?
I have not rebooted since the last evince problem, so the selinux initialized message from dmesg in another post should be from the most recent boot and before the evince message. No AVCs.
Also, do you have any idea why it was trying to save it in a non-existent directory?
Just that it appears to be intended as a temporay location. The one I made is empty.
[root@96-18-56-186 ~]# grep AVC /var/log/audit/audit.log [root@96-18-56-186 ~]# grep type= /var/log/audit/audit.log | wc 3571 52375 814962
Michael Hennebry wrote:
On Mon, 10 Jun 2013, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
<snip>
And I trust the filesystem isn't full? Or is selinux enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before?
<snip>
[root@96-18-56-186 ~]# grep AVC /var/log/audit/audit.log [root@96-18-56-186 ~]# grep type= /var/log/audit/audit.log | wc 3571 52375 814962
ARGH!!! 3571 AVC's.... You need to find out what they're telling you, and fix that, a combination of setsebool, semanage -P <whatever>/restorecon -v <whatever>, and/or grep -i avc | tail 100 | audit2allow to show you what it would do, and check the manpage for audit2allow to get the flags right to create a module that you can then load, as per the examples in the manpage.
mark "hates selinux, is slowly learning more than he wants to know"
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote: > On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) > Michael Hennebry wrote:
<snip>
And I trust the filesystem isn't full? Or is selinux enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before?
<snip> > [root@96-18-56-186 ~]# grep AVC /var/log/audit/audit.log > [root@96-18-56-186 ~]# grep type= /var/log/audit/audit.log | wc > 3571 52375 814962
ARGH!!! 3571 AVC's.... You need to find out what they're telling you, and
No AVC's at all. The first grep came up empty. I just put in type= to demonstrate that I was getting selinux messages.
fix that, a combination of setsebool, semanage -P <whatever>/restorecon -v <whatever>, and/or grep -i avc | tail 100 | audit2allow to show you what it would do, and check the manpage for audit2allow to get the flags right to create a module that you can then load, as per the examples in the manpage.
mark "hates selinux, is slowly learning more than he wants to know"
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/10/2013 03:31 PM, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote: > Frank Cox wrote: >> On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry >> wrote:
<snip>
> And I trust the filesystem isn't full? Or is selinux > enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before?
<snip> > [root@96-18-56-186 ~]# grep AVC /var/log/audit/audit.log > [root@96-18-56-186 ~]# grep type= /var/log/audit/audit.log | wc 3571 > 52375 814962
ARGH!!! 3571 AVC's.... You need to find out what they're telling you, and
No AVC's at all. The first grep came up empty. I just put in type= to demonstrate that I was getting selinux messages.
fix that, a combination of setsebool, semanage -P <whatever>/restorecon -v <whatever>, and/or grep -i avc | tail 100 | audit2allow to show you what it would do, and check the manpage for audit2allow to get the flags right to create a module that you can then load, as per the examples in the manpage.
mark "hates selinux, is slowly learning more than he wants to know"
_______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
There are lots of messages in the audit.log that are not related to SELinux error messages that have type=.
ausearch -m avc,user_avc
WIll show you all AVC messages.
On Tue, 11 Jun 2013, Daniel J Walsh wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/10/2013 03:31 PM, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote: > On Mon, 10 Jun 2013, m.roth@5-cent.us wrote: >> Frank Cox wrote: >>> On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry >>> wrote:
<snip>
>> And I trust the filesystem isn't full? Or is selinux >> enforcing? > > The filesystem is not full the workaround works. selinux is set > for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp > drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp > > I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before?
<snip> > [root@96-18-56-186 ~]# grep AVC /var/log/audit/audit.log > [root@96-18-56-186 ~]# grep type= /var/log/audit/audit.log | wc 3571 > 52375 814962
ARGH!!! 3571 AVC's.... You need to find out what they're telling you, and
No AVC's at all. The first grep came up empty. I just put in type= to demonstrate that I was getting selinux messages.
fix that, a combination of setsebool, semanage -P <whatever>/restorecon -v <whatever>, and/or grep -i avc | tail 100 | audit2allow to show you what it would do, and check the manpage for audit2allow to get the flags right to create a module that you can then load, as per the examples in the manpage.
There are lots of messages in the audit.log that are not related to SELinux error messages that have type=.
ausearch -m avc,user_avc
WIll show you all AVC messages.
From ausearch, I have AVC messages now,
but they are all from May or from after I posted about evince.
I do not understand why I did not find the May ones with grep. grep still only gives me 7, the ones from June, and does ont give me times, even when I use -e time in the command line.
From gview, .../audit.log does not contain an explicit time.
Is it encoded somehow?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/11/2013 03:28 PM, Michael Hennebry wrote:
On Tue, 11 Jun 2013, Daniel J Walsh wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 06/10/2013 03:31 PM, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote: > Michael Hennebry wrote: >> On Mon, 10 Jun 2013, m.roth@5-cent.us wrote: >>> Frank Cox wrote: >>>> On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael >>>> Hennebry wrote:
<snip>
>>> And I trust the filesystem isn't full? Or is selinux >>> enforcing? >> >> The filesystem is not full the workaround works. selinux is >> set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp >> drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp >> >> I had no trouble making the absent directory. > > Ahhhh... were there any selinux AVCs from when you tried to > save before?
<snip> > [root@96-18-56-186 ~]# grep AVC /var/log/audit/audit.log > [root@96-18-56-186 ~]# grep type= /var/log/audit/audit.log | wc > 3571 52375 814962
ARGH!!! 3571 AVC's.... You need to find out what they're telling you, and
No AVC's at all. The first grep came up empty. I just put in type= to demonstrate that I was getting selinux messages.
fix that, a combination of setsebool, semanage -P <whatever>/restorecon -v <whatever>, and/or grep -i avc | tail 100 | audit2allow to show you what it would do, and check the manpage for audit2allow to get the flags right to create a module that you can then load, as per the examples in the manpage.
There are lots of messages in the audit.log that are not related to SELinux error messages that have type=.
ausearch -m avc,user_avc
WIll show you all AVC messages.
From ausearch, I have AVC messages now, but they are all from May or from after I posted about evince.
I do not understand why I did not find the May ones with grep. grep still only gives me 7, the ones from June, and does ont give me times, even when I use -e time in the command line. From gview, .../audit.log does not contain an explicit time. Is it encoded somehow?
Audit.log is being rolled, did you look at /var/log/audit/audit.log*
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Michael Hennebry wrote:
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
<snip>
And I trust the filesystem isn't full? Or is selinux enforcing?
The filesystem is not full the workaround works. selinux is set for enforcing. [hennebry@96-18-56-186 t2]$ ls -Zd /tmp drwxrwxrwt. root root system_u:object_r:tmp_t:s0 /tmp
I had no trouble making the absent directory.
Ahhhh... were there any selinux AVCs from when you tried to save before?
I have not rebooted since the last evince problem, so the selinux initialized message from dmesg in another post should be from the most recent boot and before the evince message. No AVCs.
What you posted isn't where it would be. a) is setroubleshoot-server installed? b) is auditd running? c) if yes to both, above, are there any sealert messages in /var/log/messages? d) alternatively, grep -i avc /var/log/audit/audit.log
mark
On Mon, 10 Jun 2013, m.roth@5-cent.us wrote:
Frank Cox wrote:
On Mon, 10 Jun 2013 12:15:15 -0500 (CDT) Michael Hennebry wrote:
That is what gives me the message.
Do you have write permission in the directory where you are trying to save the file?
And I trust the filesystem isn't full? Or is selinux enforcing?
[hennebry@96-18-56-186 t2]$ dmesg | grep inux SELinux: initialized (dev fuse, type fuse), uses genfs_contexts SELinux: 2048 avtab hash slots, 277596 rules. SELinux: 2048 avtab hash slots, 277596 rules. SELinux: 9 users, 12 roles, 3898 types, 205 bools, 1 sens, 1024 cats SELinux: 81 classes, 277596 rules SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialized (dev proc, type proc), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs SELinux: initialized (dev proc, type proc), uses genfs_contexts SELinux: initialized (dev sdd1, type vfat), uses genfs_contexts [hennebry@96-18-56-186 t2]$
-
Daniel J Walsh -
Frank Cox -
m.roth＠5-cent.us -
Michael Hennebry