Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#7194 - pacman sets wrong permission to /tmp

Attached to Project: Arch Linux
Opened by Pierre Schmitz (Pierre) - Thursday, 17 May 2007, 20:28 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 19 May 2007, 18:31 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Aaron Griffin (phrakture)
Architecture All
Severity Critical
Priority Immediate
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Pacman seems to ignore the file permissions of the /tmp directory (1777) and sets them to 0755. This breaks a lot of applications; eg. KDE, GNOME and perhaps all other X apps.

As a workaround this could be fixed by an updated install script for the filesystem package.

This bugs exists on the just released "Duke" ISOs.
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Saturday, 19 May 2007, 18:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  workaround was added to filesystem package. Pacman bug #7197 still needs to be fixed.

This workaround should be reverted in futture versions of filesystem when the pacman bug was fixed.
Comment by Roman Kyrylych (Romashka) - Thursday, 17 May 2007, 22:19 GMT
I've reported pacman bug here:
so let's keep this one as a request for workaround
Comment by Dale Blount (dale) - Thursday, 17 May 2007, 23:40 GMT
confirmed on a brand new x86_64 Duke install.
Comment by Pierre Schmitz (Pierre) - Thursday, 17 May 2007, 23:59 GMT
this breaks the local-gen script, too. I attached a workaround. (I remastered the isos (which will be on dvd, too.)
Comment by Aaron Griffin (phrakture) - Friday, 18 May 2007, 03:06 GMT
I'm not sure how this is caused, but I'm going to push a pacman fix for it ASAP. At least those that do an ftp install won't have an issue.
Comment by Aaron Griffin (phrakture) - Friday, 18 May 2007, 03:08 GMT
For completeness, here's the awesome bug fix
diff -u -r1.131 add.c
--- lib/libalpm/add.c 17 Apr 2007 02:31:04 -0000 1.131
+++ lib/libalpm/add.c 18 May 2007 03:07:13 -0000
@@ -704,6 +704,8 @@
_alpm_log(PM_LOG_ERROR, _("could not extract %s (%s)"), filename, strerror(errno));
alpm_logaction(_("error: could not extract %s (%s)"), filename, strerror(errno));
+ } else {
+ chmod(filename, archive_entry_mode(entry));

/* calculate an hash if this is in newpkg's backup */