Bug 1252037 - Horde bad shutdown Horde::Util
Horde bad shutdown Horde::Util
Product: Fedora
Classification: Fedora
Component: horde (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Jason Tibbitts
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-08-10 10:16 EDT by dev002
Modified: 2016-07-19 13:27 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 13:27:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description dev002 2015-08-10 10:16:06 EDT
Description of problem:
Horde::Util , public static function shutdown() tries to erase twice the same file.

Version-Release number of selected component (if applicable):

How reproducible:
Use horde libs

Steps to Reproduce:
1. Include horde libs
2. Call exit
3. Horde::Util is trying to erase twice tmp files

Actual results:

Expected results:
Clean exit

Additional info:

The code of function + temp solution.

  $ptr = &self::$_shutdowndata;

// $ptr contains files and dirs.
// Dirs and contains are erased in the first pass.
// But $ptr continues containing files already erased.
// In this case "is_file()" over non existent file return false, and tries to // iterate a non existent  dir. An error is printed.

        foreach (array_keys($ptr['paths']) as $val) {

 /* Temp Solution  */
if (!file_exists($val)) continue;
/* */

            if (@is_file($val)) {

            try {
                $it = new RecursiveIteratorIterator(
                    new RecursiveDirectoryIterator($val),
            } catch (UnexpectedValueException $e) {

            while ($it->valid()) {
                if (!$it->isDot()) {
                    if ($it->isDir()) {
                    } elseif ($it->isFile()) {
                    } else {

Comment 1 Fedora End Of Life 2016-07-19 13:27:32 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.