Bug 740579

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

I can confirm that this behaviour still persists with RHEL 6.2 and acrobat reader 9.4.7-1. It is very annoying...

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

I can confirm this behaviour on RHEL6.4 even with latest updates (as of July 22nd 2013). The acroread process appears to be stuck into an 'inotify' loop when exited..

# rpm -q acroread
acroread-9.5.5-1.el6_4.i686
# uname -a
Linux rh6x64 2.6.32-358.14.1.el6.x86_64 #1 SMP Mon Jun 17 15:54:20 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)

[raistlin@rh6x64 ~]$ rm -rf .adobe 
[raistlin@rh6x64 ~]$ acroread &
[1] 7214
[raistlin@rh6x64 ~]$ 
[raistlin@rh6x64 ~]$ sudo strace -f -p 7214
[sudo] password for raistlin: 
Process 7214 attached with 2 threads - interrupt to quit
[ Process PID=7445 runs in 32 bit mode. ]
[pid  7445] restart_syscall(<... resuming interrupted call ...>) = 0
[pid  7445] poll([{fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 1000) = 0 (Timeout)
[pid  7445] poll([{fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 1000) = 0 (Timeout)
[pid  7445] poll([{fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 1000) = 0 (Timeout)
[pid  7445] poll([{fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 1000) = 0 (Timeout)
[pid  7445] poll([{fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 1000) = 0 (Timeout)
[pid  7445] poll([{fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 1000) = 0 (Timeout)
[pid  7445] poll([{fd=9, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=10, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}], 2, 1000^C <unfinished ...>
Process 7214 detached
Process 7445 detached

[raistlin@rh6x64 ~]$ ls -la /proc/7445/fd/9
lr-x------ 1 raistlin users 64 Jul 22 17:21 /proc/7445/fd/9 -> inotify
[raistlin@rh6x64 ~]$ ls -la /proc/7445/fd/10
lrwx------ 1 raistlin users 64 Jul 22 17:21 /proc/7445/fd/10 -> socket:[23519]

[root@rh6x64 ~]# netstat -an|grep 23519
unix  3      [ ]         STREAM     CONNECTED     23519

[root@rh6x64 ~]# lsof |grep 23519
acroread   7214  raistlin   10u     unix 0xffff88010a3b8980       0t0      23519 socket

Seems the issue isn't exactly new:
https://bugzilla.novell.com/show_bug.cgi?id=618207

Hi,

I'm closing this bug because we can not fix it. We do not have access to Adobe Reader's internals.

Regards

Marek

Could this be reported to Adobe, at least?

(In reply to Vincent S. Cojot from comment #16)
> Could this be reported to Adobe, at least?

Unfortunately not. Adobe's Bugbase doesn't contain Adobe Reader.