0 true 2009-08-25T02:40:07-05:00 58490 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-30T13:47:26-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 Here is the installer log. The installer was ran under a non-admin user, which explains why it failed to create the receipt. May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error 13 (Permission denied) trying to rename /private/tmp/ClickToFlash.pkg.1575MfyjnG/Receipts/ClickToFlash.pkg to /Library/Receipts/ClickToFlash.pkg May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error creating final receipt for package 'ClickToFlash.pkg' May 31 15:07:02 xxxx Installer[1575]: Install failed: The Installer could not write the receipt for “ClickToFlash”. May 31 15:07:02 xxxx Installer[1575]: Displaying 'Install Failed' UI. May 31 15:07:02 xxxx Installer[1575]: 'Install Failed' UI displayed message:'The Installer could not write the receipt for “ClickToFlash”.'. Here is the installer log. The installer was ran under a non-admin user, which explains why it failed to create the receipt. May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error 13 (Permission denied) trying to rename /private/tmp/ClickToFlash.pkg.1575MfyjnG/Receipts/ClickToFlash.pkg to /Library/Receipts/ClickToFlash.pkg May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error creating final receipt for package 'ClickToFlash.pkg' May 31 15:07:02 xxxx Installer[1575]: Install failed: The Installer could not write the receipt for “ClickToFlash”. May 31 15:07:02 xxxx Installer[1575]: Displaying 'Install Failed' UI. May 31 15:07:02 xxxx Installer[1575]: 'Install Failed' UI displayed message:'The Installer could not write the receipt for “ClickToFlash”.'. <div><p>Here is the installer log. The installer was ran under a non-admin user, which explains why it failed to create the receipt.</p> <p>May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error 13 (Permission denied) trying to rename /private/tmp/ClickToFlash.pkg.1575MfyjnG/Receipts/ClickToFlash.pkg to /Library/Receipts/ClickToFlash.pkg May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error creating final receipt for package 'ClickToFlash.pkg' May 31 15:07:02 xxxx Installer[1575]: Install failed: The Installer could not write the receipt for &#8220;ClickToFlash&#8221;. May 31 15:07:02 xxxx Installer[1575]: Displaying 'Install Failed' UI. May 31 15:07:02 xxxx Installer[1575]: 'Install Failed' UI displayed message:'The Installer could not write the receipt for &#8220;ClickToFlash&#8221;.'.</p></div> 0 Here is the installer log. The installer was ran under a non-admin user, which explains why it failed to create the receipt. @@@ May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error 13 (Permission denied) trying to rename /private/tmp/ClickToFlash.pkg.1575MfyjnG/Receipts/ClickToFlash.pkg to /Library/Receipts/ClickToFlash.pkg May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error creating final receipt for package 'ClickToFlash.pkg' May 31 15:07:02 xxxx Installer[1575]: Install failed: The Installer could not write the receipt for “ClickToFlash”. May 31 15:07:02 xxxx Installer[1575]: Displaying 'Install Failed' UI. May 31 15:07:02 xxxx Installer[1575]: 'Install Failed' UI displayed message:'The Installer could not write the receipt for “ClickToFlash”.'. @@@ <div><p>Here is the installer log. The installer was ran under a non-admin user, which explains why it failed to create the receipt.</p> <pre> <code>May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error 13 (Permission denied) trying to rename /private/tmp/ClickToFlash.pkg.1575MfyjnG/Receipts/ClickToFlash.pkg to /Library/Receipts/ClickToFlash.pkg May 31 15:07:02 xxxx pkgReceiptMaker[1584]: Error creating final receipt for package 'ClickToFlash.pkg' May 31 15:07:02 xxxx Installer[1575]: Install failed: The Installer could not write the receipt for &#8220;ClickToFlash&#8221;. May 31 15:07:02 xxxx Installer[1575]: Displaying 'Install Failed' UI. May 31 15:07:02 xxxx Installer[1575]: 'Install Failed' UI displayed message:'The Installer could not write the receipt for &#8220;ClickToFlash&#8221;.'.</code> </pre></div> false 2009-05-31T14:12:17-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 new 1.5b2 broken install installer non-admin permission pkg privilege receipt 2009-08-19T20:42:42-05:00 58490 someone someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 45213 0 false 2009-05-31T21:35:40-05:00 58490 --- :state: new :assigned_user: 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 open 1.5b2 broken install installer non-admin permission pkg privilege receipt 2009-05-31T21:35:42-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 What version of Mac OS X/Safari/ClickToFlash? I was able to correctly install for a nonadmin user on Mac OS X 10.5.7/Safari 3.2.3/ClickToFlash 1.5b3. <div><p>What version of Mac OS X/Safari/ClickToFlash? I was able to correctly install for a nonadmin user on Mac OS X 10.5.7/Safari 3.2.3/ClickToFlash 1.5b3.</p></div> true 2009-06-24T20:00:01-05:00 58490 --- :state: open 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b2 broken install installer non-admin permission pkg privilege receipt 2009-06-24T20:00:02-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 I've just witnessed this behaviour with 1.5b4 and Safari 4 on 10.5.7. I tried, on the offchance, asking pkgutil to forget the old package (my theory was that it was trying to replace and old receipt in /Library), but to no avail. pkgutil --pkgs lists no trace of CtF in either / nor $HOME. <div><p>I've just witnessed this behaviour with 1.5b4 and Safari 4 on 10.5.7.</p> <p>I tried, on the offchance, asking pkgutil to forget the old package (my theory was that it was trying to replace and old receipt in /Library), but to no avail.</p> <p>pkgutil --pkgs lists no trace of CtF in either / nor $HOME.</p></div> true 2009-06-29T02:20:05-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b2 broken install installer non-admin permission pkg privilege receipt 2009-06-29T02:20:11-05:00 33126 Mo someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 This bug still exists on ClickToFlash 1.5b4. I am running Safari 3.2.3 on Mac OS X 10.5.7 PPC. <div><p>This bug still exists on ClickToFlash 1.5b4. I am running Safari 3.2.3 on Mac OS X 10.5.7 PPC.</p></div> true 2009-06-30T23:04:12-05:00 58490 --- :tag: 1.5b2 broken install installer non-admin permission pkg privilege receipt 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b4 broken install installer non-admin permission pkg privilege receipt 2009-06-30T23:04:15-05:00 58490 someone someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 I don't see how you can write to the Receipts folder, since a non-admin user does not have permissions to write to that folder and the installer never asks for admin permission. In addition, would you consider abandoning the use of package installers and move to drop-and-drop based installation (provide symlinks in the dmg)? This method works well on both Tiger and Leopard, handles permission problems on its own and provides a more seemless Sparkle update experience). <div><p>I don't see how you can write to the Receipts folder, since a non-admin user does not have permissions to write to that folder and the installer never asks for admin permission.</p> <p>In addition, would you consider abandoning the use of package installers and move to drop-and-drop based installation (provide symlinks in the dmg)? This method works well on both Tiger and Leopard, handles permission problems on its own and provides a more seemless Sparkle update experience).</p></div> true 2009-06-30T23:09:33-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b4 broken install installer non-admin permission pkg privilege receipt 2009-06-30T23:09:40-05:00 58490 someone someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 I am just wondering if your /Library/Receipts has the standard permission set. <div><p>I am just wondering if your /Library/Receipts has the standard permission set.</p></div> true 2009-07-04T16:38:06-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b4 broken install installer non-admin permission pkg privilege receipt 2009-07-04T16:38:08-05:00 58490 someone someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 The installer package is still broken for *non-admin* users in version 1.5b5 under Safari 3.2.3 running on Mac OS X 10.5.7 PowerPC. Can you try to reproduce this bug again? I found it very surprising that you can write to /Library/Receipts when running the installer under a non-admin user without first obtaining admin privilege. <div><p>The installer package is still broken for <em>non-admin</em> users in version 1.5b5 under Safari 3.2.3 running on Mac OS X 10.5.7 PowerPC. Can you try to reproduce this bug again? I found it very surprising that you can write to /Library/Receipts when running the installer under a non-admin user without first obtaining admin privilege.</p></div> true 2009-08-11T01:09:05-05:00 58490 --- :tag: 1.5b4 broken install installer non-admin permission pkg privilege receipt 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-11T01:09:06-05:00 58490 someone someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 I just tested this, and installation under a non-admin user still works fine. It'd be stupid if Mac OS X required permissions to write a receipt to the /Library/ folder. That would mean that a non-admin user could not install *anything*. I think this is correct behavior on the part of the system; it's true that you don't have permissions to write to /Library/Receipts/ as a non-admin user, but I suspect that the Installer does. There's something about your user that isn't right. Have you tried creating a pristine non-admin user, and trying to install ClickToFlash using that account? <div><p>I just tested this, and installation under a non-admin user still works fine.</p> <p>It'd be stupid if Mac OS X required permissions to write a receipt to the /Library/ folder. That would mean that a non-admin user could not install <em>anything</em>. I think this is correct behavior on the part of the system; it's true that you don't have permissions to write to /Library/Receipts/ as a non-admin user, but I suspect that the Installer does.</p> <p>There's something about your user that isn't right. Have you tried creating a pristine non-admin user, and trying to install ClickToFlash using that account?</p></div> true 2009-08-11T01:20:56-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-11T01:21:00-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 Okay, I've now tried this on two machines, two running 10.5, one running [REDACTED]. On the first attempt, I tried installing 1.5b5 as me on my MacBook, and it failed as before. This was the only test with a Mobile account, the rest were local (were the results different for these, I would have tried a new mobile account, but it wasn't necessary). Next, I tried a fresh local non-admin account, which failed because the failed installation as me had left files lying around in /tmp (ClickToFlash.webplugin, specifically). I cleared those out and tried again, and it again failed because of an inability to write to /Library/Receipts. On [REDACTED], it succeeded, and didn't write one jot to /Library/Receipts or ~/Library/Receipts. On a different machine, also running 10.5 and on which I've never installed CtF on, I created another local non-admin account, and that also failed writing the package receipt. I note on my MacBook (but none of the others), I have a ~/Library/Receipts (which just contains growl.pkg). <div><p>Okay, I've now tried this on two machines, two running 10.5, one running <a href="/projects/24342/changesets/REDACTED" title= "Changeset [REDACTED]">[REDACTED]</a>.</p> <p>On the first attempt, I tried installing 1.5b5 as me on my MacBook, and it failed as before. This was the only test with a Mobile account, the rest were local (were the results different for these, I would have tried a new mobile account, but it wasn't necessary).</p> <p>Next, I tried a fresh local non-admin account, which failed because the failed installation as me had left files lying around in /tmp (ClickToFlash.webplugin, specifically). I cleared those out and tried again, and it again failed because of an inability to write to /Library/Receipts.</p> <p>On <a href="/projects/24342/changesets/REDACTED" title= "Changeset [REDACTED]">[REDACTED]</a>, it succeeded, and didn't write one jot to /Library/Receipts or ~/Library/Receipts.</p> <p>On a different machine, also running 10.5 and on which I've never installed CtF on, I created another local non-admin account, and that also failed writing the package receipt.</p> <p>I note on my MacBook (but none of the others), I have a ~/Library/Receipts (which just contains growl.pkg).</p></div> true 2009-08-11T04:18:55-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-11T04:18:58-05:00 33126 Mo someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 Out of curiosity, what's the rationale for --domain user not being passed to packagemaker in http://github.com/rentzsch/clicktoflash/blob/13b1e672adfe01b69f5b8f81c653eb2bd85ddae0/Installer/build_installer_pkg.command ? <div><p>Out of curiosity, what's the rationale for --domain user not being passed to packagemaker in <a href= "http://github.com/rentzsch/clicktoflash/blob/13b1e672adfe01b69f5b8f81c653eb2bd85ddae0/Installer/build_installer_pkg.command"> http://github.com/rentzsch/clicktoflash/blob/13b1e672adfe01b69f5b8f...</a> ?</p></div> true 2009-08-11T04:25:08-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-11T04:25:11-05:00 33126 Mo someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 I believe "--domain user" triggers the FileVault installer bug: http://rentzsch.lighthouseapp.com/projects/24342/tickets/96-continue-grayed-out-in-installer <div><p>I believe "--domain user" triggers the FileVault installer bug: <a href= "http://rentzsch.lighthouseapp.com/projects/24342/tickets/96-continue-grayed-out-in-installer"> http://rentzsch.lighthouseapp.com/projects/24342/tickets/96-continu...</a></p></div> true 2009-08-11T10:13:19-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-11T10:13:19-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 Okay, I figured this one out. If you've previously installed ClickToFlash as an admin user (i.e.: there is already a receipt for ClickToFlash in /Library/Receipts/), then installing as a non-admin user will succeed. But if you've never installed ClickToFlash as an admin and there is no existing receipt for it in /Library/Receipts/ (or you've deleted the receipt), then the install will fail. Argh. I guess we need yet another workaround. <div><p>Okay, I figured this one out. If you've previously installed ClickToFlash as an admin user (i.e.: there is already a receipt for ClickToFlash in /Library/Receipts/), then installing as a non-admin user will succeed.</p> <p>But if you've never installed ClickToFlash as an admin and there is no existing receipt for it in /Library/Receipts/ (or you've deleted the receipt), then the install will fail.</p> <p>Argh. I guess we need yet another workaround.</p></div> true 2009-08-11T10:30:44-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 cantreproduce 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-11T10:30:47-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 false 2009-08-11T10:31:54-05:00 58490 --- :state: cantreproduce 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 accepted 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-11T10:31:55-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 Sounds better than 'accepted' Simone, you have a bona-fide reproduction! ;-) <div><p>Sounds better than 'accepted' Simone, you have a bona-fide reproduction! ;-)</p></div> false 2009-08-12T03:07:38-05:00 58490 --- :state: accepted 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 reproduced 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-12T03:07:41-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 > When installing ClickToFlash, you may receive this error if > you've installed ClickToFlash before: > Installer could not install files in /tmp > This is a known problem with pre-release versions of 1.4 and 1.5. ____________ I can reproduce this bug in 1.4.2 It seems to happen if you have multiple user accounts The first install was ok, it was under a non-admin account The problem might occur only if you install under a user account first instead of the administrator account When the problem occurs, the package "forget" procedure must be repeated for each additional account you want to install on Generally speaking, to sudo-forget you must be administrator. This is the default behavior of MacOS (instructions on web site do not clarify this) If possible, ClickToFlash should have an option to "install for all users" and prompt for admin password where appropriate, instead of requiring admin logon _______ * FYI, I love the UI... this thing is just what I wanted - thanks! <div><blockquote> <p>When installing ClickToFlash, you may receive this error if you've installed ClickToFlash before:</p> <p>Installer could not install files in /tmp This is a known problem with pre-release versions of 1.4 and 1.5. ____________</p> </blockquote> <p>I can reproduce this bug in 1.4.2</p> <p>It seems to happen if you have multiple user accounts</p> <p>The first install was ok, it was under a non-admin account</p> <p>The problem might occur only if you install under a user account first instead of the administrator account</p> <p>When the problem occurs, the package "forget" procedure must be repeated for each additional account you want to install on</p> <p>Generally speaking, to sudo-forget you must be administrator. This is the default behavior of MacOS (instructions on web site do not clarify this)</p> <p>If possible, ClickToFlash should have an option to "install for all users" and prompt for admin password where appropriate, instead of requiring admin logon<br> _______</p> <ul> <li>FYI, I love the UI... this thing is just what I wanted - thanks!</li> </ul></div> false 2009-08-17T15:15:40-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 reproduced 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-17T15:15:44-05:00 66641 me someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 Blech, fixed this in my repo. Non-admin users are now asked for a password if there is no existing receipt. Unfortunately, due to the way this had to be constructed (two packages with the same content, one which requires admin privs and one not), if you're a non-admin user and there's no receipt, installing w/admin privs will not create the correct receipt, so you'll still have to put in a password the next time you install. But, yeah, this is an acceptable fix, since it should allow anybody to install as long as they have a username/password. <div><p>Blech, fixed this in my repo. Non-admin users are now asked for a password if there is no existing receipt. Unfortunately, due to the way this had to be constructed (two packages with the same content, one which requires admin privs and one not), if you're a non-admin user and there's no receipt, installing w/admin privs will not create the correct receipt, so you'll still have to put in a password the next time you install.</p> <p>But, yeah, this is an acceptable fix, since it should allow anybody to install as long as they have a username/password.</p></div> false 2009-08-22T19:59:50-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 reproduced 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-22T19:59:50-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 true 2009-08-23T14:41:07-05:00 58490 --- :state: reproduced 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 fixcommitted 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-23T14:41:07-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 This is broken for me circa <http://github.com/rentzsch/clicktoflash/commit/e84a62ad4ef5f4599d5b03b78fb21328944745ee> on Mac OS X 10.5.8. `8/25/09 2:31:19 AM [0x0-0x285285].com.apple.installer[18931] Notice There is a receipt, no admin privs required for installer pkg.` gets repeated around 200 times. First time through the installation also completely deadlocked. ClickToFlash is installed without correct permissions: @@@ wolf-mbp:~ wolf$ cd ~/Library/Internet\ Plug-Ins/ wolf-mbp:Internet Plug-Ins wolf$ ls -l total 0 drw-rw-r-- 3 wolf admin 102 Aug 25 02:30 ClickToFlash.webplugin drwxr-xr-x@ 3 wolf staff 102 Mar 10 23:37 XML View Plugin.webplugin @@@ Even though I'm the owner, the executable flag isn't set on the ClickToFlash.webplugin directory, denying enumeration of the bundle's contents. This disables the plugin from loading at all. <div><p>This is broken for me circa <a href= "http://github.com/rentzsch/clicktoflash/commit/e84a62ad4ef5f4599d5b03b78fb21328944745ee"> http://github.com/rentzsch/clicktoflash/commit/e84a62ad4ef5f4599d5b03b78fb21328944745ee</a> on Mac OS X 10.5.8.</p> <p><code>8/25/09 2:31:19 AM [0x0-0x285285].com.apple.installer[18931] Notice There is a receipt, no admin privs required for installer pkg.</code> gets repeated around 200 times. First time through the installation also completely deadlocked.</p> <p>ClickToFlash is installed without correct permissions:</p> <pre> <code>wolf-mbp:~ wolf$ cd ~/Library/Internet\ Plug-Ins/ wolf-mbp:Internet Plug-Ins wolf$ ls -l total 0 drw-rw-r-- 3 wolf admin 102 Aug 25 02:30 ClickToFlash.webplugin drwxr-xr-x@ 3 wolf staff 102 Mar 10 23:37 XML View Plugin.webplugin</code> </pre> <p>Even though I'm the owner, the executable flag isn't set on the ClickToFlash.webplugin directory, denying enumeration of the bundle's contents. This disables the plugin from loading at all.</p></div> true 2009-08-25T02:40:07-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 fixcommitted 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T02:41:02-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 Hrm. Kick out that commit, then. I thought I was fixing an issue where ClickToFlash was installed to /tmp with incorrect permissions, but maybe I'm just creating more problems? In any case, though, it works on my comp with ClickToFlash.webplugin having 664 privs. I specifically set the executable bit on the actual executable files in the postflight script. <div><p>Hrm. Kick out that commit, then. I thought I was fixing an issue where ClickToFlash was installed to /tmp with incorrect permissions, but maybe I'm just creating more problems?</p> <p>In any case, though, it works on my comp with ClickToFlash.webplugin having 664 privs. I specifically set the executable bit on the actual executable files in the postflight script.</p></div> true 2009-08-25T02:45:16-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 fixcommitted 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T02:45:18-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 lsbom tells me the permissions in the actual package are fine. Smells like the postflight script is doing something not quite right. <div><p>lsbom tells me the permissions in the actual package are fine. Smells like the postflight script is doing something not quite right.</p></div> true 2009-08-25T02:49:44-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 fixcommitted 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T02:49:48-05:00 33126 Mo someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 45213 0 true 2009-08-25T02:50:46-05:00 58490 --- :milestone: 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 fixcommitted 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T02:50:51-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 false 2009-08-25T02:51:03-05:00 58490 --- :state: fixcommitted 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 reproduced 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T02:51:07-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 Yeah, eliminating the postflight permissions changing (not the chowning, though) causes things to work right again. So we need to 775 the directory too? <div><p>Yeah, eliminating the postflight permissions changing (not the chowning, though) causes things to work right again. So we need to 775 the directory too?</p></div> false 2009-08-25T02:55:21-05:00 58490 --- {} 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 reproduced 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T02:55:24-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 Mo's latest commit <http://github.com/rentzsch/clicktoflash/commit/3c2b3ac31ef89c7b91702f5ee6f1a9e7038c5f6e> does indeed fix the wrong-permissions on my end. Still logging 92 'There is a receipt, no admin privs required for installer pkg.' messages, though. It that script being executed X times for each mounted disk or something? (I have 5 mounted volumes.) <div><p>Mo's latest commit <a href= "http://github.com/rentzsch/clicktoflash/commit/3c2b3ac31ef89c7b91702f5ee6f1a9e7038c5f6e"> http://github.com/rentzsch/clicktoflash/commit/3c2b3ac31ef89c7b91702f5ee6f1a9e7038c5f6e</a> does indeed fix the wrong-permissions on my end. Still logging 92 'There is a receipt, no admin privs required for installer pkg.' messages, though. It that script being executed X times for each mounted disk or something? (I have 5 mounted volumes.)</p></div> false 2009-08-25T03:11:31-05:00 58490 --- {} 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 reproduced 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T03:11:32-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 I dunno. I saw that message being duplicated, but honestly, I just ignored it. But maybe it's a symptom of the deadlock? I only have one mounted volume and it shows up about 16 times for me. Fucking fuck I hate Apple's installer technology. We can comment out the echo lines to suppress that, but if it truly is running that script ~16 times for each volume, then maybe something else is wrong? Sigh. <div><p>I dunno. I saw that message being duplicated, but honestly, I just ignored it. But maybe it's a symptom of the deadlock? I only have one mounted volume and it shows up about 16 times for me.</p> <p>Fucking fuck I hate Apple's installer technology.</p> <p>We can comment out the echo lines to suppress that, but if it truly is running that script ~16 times for each volume, then maybe something else is wrong? Sigh.</p></div> false 2009-08-25T03:15:33-05:00 58490 --- {} 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 reproduced 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-25T03:15:36-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 <http://github.com/rentzsch/clicktoflash/commit/96f78edb130f0b8d10149b9d0c053c9c6c9e5b43> <div><p><a href= "http://github.com/rentzsch/clicktoflash/commit/96f78edb130f0b8d10149b9d0c053c9c6c9e5b43"> http://github.com/rentzsch/clicktoflash/commit/96f78edb130f0b8d10149b9d0c053c9c6c9e5b43</a></p></div> true 2009-08-27T17:15:22-05:00 58490 --- :state: reproduced 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 fixcommitted 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T17:15:25-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 Fix released in 1.5fc1. <div><p>Fix released in 1.5fc1.</p></div> true 2009-08-27T18:19:08-05:00 58490 --- :state: fixcommitted 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 fixreleased 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T18:19:10-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 @simX has a repro on the installation deadlock I saw. It's nasty: can't even get a real stack trace with sample, Shark or gdb. I say back out this .mpkg fix, go back to less-broken .pkg, and simply document the 10.4+10.5 installer bug and that you have to issue some magic terminal command to install ClickToFlash on a nonadmin account after installing on to an admin account (10.6 seems to fix this bug). Maybe one day we'll figure out how to make an installer package that dodges all of Apple's bugs. But I don't want to hold up 1.5 for it. <div><p>@simX has a repro on the installation deadlock I saw. It's nasty: can't even get a real stack trace with sample, Shark or gdb.</p> <p>I say back out this .mpkg fix, go back to less-broken .pkg, and simply document the 10.4+10.5 installer bug and that you have to issue some magic terminal command to install ClickToFlash on a nonadmin account after installing on to an admin account (10.6 seems to fix this bug).</p> <p>Maybe one day we'll figure out how to make an installer package that dodges all of Apple's bugs. But I don't want to hold up 1.5 for it.</p></div> true 2009-08-27T19:23:31-05:00 58490 --- :state: fixreleased 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:23:36-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 @rentzsch: You've got it a bit backwards. You *can* install on a non-admin account after you've *already* installed it on an admin account. But if you *haven't* yet installed it on an admin account, you *cannot* install it on a non-admin account. So it's kind of worse, because it presents a bad install the first time a non-admin user tries to install it. And there's not really a magical Terminal incantation that'll fix it (unless creating a dummy 0 KB file named com.github.rentzsch.clicktoflash.pkg in the Receipts folder is enough). At this point, I think I would recommend requiring a password on all installs even though it's not necessary for admin users. I dunno, I'd prefer all users actually being able to install it. The other possibility is exploring whether using the legacy InstallationCheck files for .mpkg installers still works on 10.4 and 10.5 and whether that would avoid the deadlock issue... <div><p>@rentzsch: You've got it a bit backwards. You <em>can</em> install on a non-admin account after you've <em>already</em> installed it on an admin account. But if you <em>haven't</em> yet installed it on an admin account, you <em>cannot</em> install it on a non-admin account.</p> <p>So it's kind of worse, because it presents a bad install the first time a non-admin user tries to install it. And there's not really a magical Terminal incantation that'll fix it (unless creating a dummy 0 KB file named com.github.rentzsch.clicktoflash.pkg in the Receipts folder is enough).</p> <p>At this point, I think I would recommend requiring a password on all installs even though it's not necessary for admin users. I dunno, I'd prefer all users actually being able to install it.</p> <p>The other possibility is exploring whether using the legacy InstallationCheck files for .mpkg installers still works on 10.4 and 10.5 and whether that would avoid the deadlock issue...</p></div> true 2009-08-27T19:32:03-05:00 58490 --- {} 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:32:08-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 @simX: thanks for the correction. I say since it took us this long to discover this bug, most of our users are admin accounts or install first on an admin account. I'm against requiring a password because it makes ClickToFlash look like it's doing something insidious. I'm willing to sacrifice a seamless first-time-nonadmin experience on 10.4+10.5 to maintain our "harmless" appearance for the majority of our users. Besides, this is all fixed in 10.6, so this issue will eventually dissipate (or at least lessen) by itself. <div><p>@simX: thanks for the correction.</p> <p>I say since it took us this long to discover this bug, most of our users are admin accounts or install first on an admin account.</p> <p>I'm against requiring a password because it makes ClickToFlash look like it's doing something insidious.</p> <p>I'm willing to sacrifice a seamless first-time-nonadmin experience on 10.4+10.5 to maintain our "harmless" appearance for the majority of our users.</p> <p>Besides, this is all fixed in 10.6, so this issue will eventually dissipate (or at least lessen) by itself.</p></div> true 2009-08-27T19:37:14-05:00 58490 --- {} 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:39:33-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 Yeah, I agree, I don't like requiring a password. Lemme see if creating that dummy file is enough to satisfy our old installer. If so, then we'll go that route and have YET ANOTHER Terminal incantation for fixing the installer. <div><p>Yeah, I agree, I don't like requiring a password.</p> <p>Lemme see if creating that dummy file is enough to satisfy our old installer. If so, then we'll go that route and have YET ANOTHER Terminal incantation for fixing the installer.</p></div> true 2009-08-27T19:39:25-05:00 58490 --- {} 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:39:35-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 FWIW, this problem *won't* dissipate until we drop *10.5* support. :\ So it'll be quite a while. Unless we want separate packages for each OS version... <div><p>FWIW, this problem <em>won't</em> dissipate until we drop <em>10.5</em> support. :\ So it'll be quite a while.</p> <p>Unless we want separate packages for each OS version...</p></div> true 2009-08-27T19:41:37-05:00 58490 --- {} 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:41:39-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 1.5 45213 0 simX: it's funny how having our own custom installer is totally the actual way to solve this, however folks are more comfortable with an Apple-style .pkg. They think it's higher-quality and safer, when in fact both are incorrect. <div><p>simX: it's funny how having our own custom installer is totally the actual way to solve this, however folks are more comfortable with an Apple-style .pkg. They think it's higher-quality and safer, when in fact both are incorrect.</p></div> true 2009-08-27T19:42:03-05:00 58490 --- :milestone: 33492 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:42:05-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 rentzsch 0 true 2009-08-27T19:42:09-05:00 58490 --- :assigned_user: 45213 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:42:10-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 0 @rentzsch: Lol. How true. So, good news is, since the Installer is so bitchy, it thinks a 0 KB file named "ClickToFlash.pkg" in the receipts folder is good enough. So, yeah, revert to the old .pkg, and we have a magical Terminal incantation for non-admin users who haven't installed on an admin user before. <div><p>@rentzsch: Lol. How true.</p> <p>So, good news is, since the Installer is so bitchy, it thinks a 0 KB file named "ClickToFlash.pkg" in the receipts folder is good enough.</p> <p>So, yeah, revert to the old .pkg, and we have a magical Terminal incantation for non-admin users who haven't installed on an admin user before.</p></div> true 2009-08-27T19:46:54-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:46:58-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 0 (FWIW, the Terminal incantation is: @@@ su admin_user_name @@@ type in password, press return, then: @@@ sudo touch /Library/Receipts/ClickToFlash.pkg @@@ <div><p>(FWIW, the Terminal incantation is:</p> <pre> <code>su admin_user_name</code> </pre> <p>type in password, press return, then:</p> <pre> <code>sudo touch /Library/Receipts/ClickToFlash.pkg</code> </pre></div> true 2009-08-27T19:47:48-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-27T19:47:51-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 0 It appears that command can be reduced to @@@ su wolf -c 'touch /Library/Receipts/ClickToFlash.pkg' @@@ Replacing `wolf` with an admin user name, naturally. <div><p>It appears that command can be reduced to</p> <pre> <code>su wolf -c 'touch /Library/Receipts/ClickToFlash.pkg'</code> </pre> <p>Replacing <code>wolf</code> with an admin user name, naturally.</p></div> true 2009-08-28T00:28:34-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-28T00:28:36-05:00 45213 rentzsch someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 0 I found an application called SafariCookies which uses the PKG installer. Like ClickToFlash it extends Safari functionality but the install method is slightly different. I just thought it might be worth looking at for various reasons. http://sweetpproductions.com/safaricookies/index.htm _______________ The author sets a nice example here by detailing what the installer is going to do right inside the installer dialog: • Safari Cookies installs a folder into your Inputmanagers folder, located at /Library/InputManagers/ • Favorites are saved to the file ~/Library/Application Support/Favorites.plist • All of Safari Cookies preferences are stored in Safari's preference file ~/Library/Preferences/com.apple.Safari.plist (with the prefix "SC") • If logging is enabled, a log file will be created in the user folder ~/Library/Logs/ • An uninstaller is included in the Safari Cookies preference pane, which will delete all traces of Safari Cookies - should the need arise _______________ Under "Installation Type" in the installer dialog, it says: "Click Install to perform a standard installation of this software for all users of the computer." When this occurs under a non-admin account, the user is prompted for administrator name and password. When installation occurs under the admin account, it only prompts for the password. At this point it should be obvious that the password is required because you are installing for all users. But that seems like an acceptable solution to me. Maybe this method will not work the same way on 10.4 -- but maybe just fine on 10.5 or later. I wonder, is it really necessary to have a single installer that supports 10.4 through 10.6 ? It just seems like asking for a password is preferable to asking the user to do stuff in terminal, if possible. <div><p>I found an application called SafariCookies which uses the PKG installer. Like ClickToFlash it extends Safari functionality but the install method is slightly different. I just thought it might be worth looking at for various reasons.</p> <p><a href= "http://sweetpproductions.com/safaricookies/index.htm">http://sweetpproductions.com/safaricookies/index.htm</a><br> _______________</p> <p>The author sets a nice example here by detailing what the installer is going to do right inside the installer dialog:</p> <p>&#8226; Safari Cookies installs a folder into your Inputmanagers folder, located at /Library/InputManagers/</p> <p>&#8226; Favorites are saved to the file ~/Library/Application Support/Favorites.plist</p> <p>&#8226; All of Safari Cookies preferences are stored in Safari's preference file ~/Library/Preferences/com.apple.Safari.plist (with the prefix "SC")</p> <p>&#8226; If logging is enabled, a log file will be created in the user folder ~/Library/Logs/</p> <p>&#8226; An uninstaller is included in the Safari Cookies preference pane, which will delete all traces of Safari Cookies - should the need arise<br> _______________</p> <p>Under "Installation Type" in the installer dialog, it says:</p> <p>"Click Install to perform a standard installation of this software for all users of the computer."</p> <p>When this occurs under a non-admin account, the user is prompted for administrator name and password. When installation occurs under the admin account, it only prompts for the password. At this point it should be obvious that the password is required because you are installing for all users. But that seems like an acceptable solution to me.</p> <p>Maybe this method will not work the same way on 10.4 -- but maybe just fine on 10.5 or later. I wonder, is it really necessary to have a single installer that supports 10.4 through 10.6 ? It just seems like asking for a password is preferable to asking the user to do stuff in terminal, if possible.</p></div> true 2009-08-30T00:49:38-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-30T00:49:43-05:00 66641 me someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 0 Requiring a password for the majority of cases is a non-starter. We don't want ClickToFlash to look like it's mucking stuff up. <div><p>Requiring a password for the majority of cases is a non-starter. We don't want ClickToFlash to look like it's mucking stuff up.</p></div> true 2009-08-30T00:52:45-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-30T00:52:49-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 0 I dont think even the typical Mac user is going to be scared by a password request, especially if the installer dialog tells them why it happens. If they have chosen to install the app, they have already chosen to trust it. Most disk utility programs ask for a password too, even when they are launched under the admin account. I have never seen users complain about this. Just my opinion, but if you are concerned with appearances, it looks even worse when they have to use terminal to complete the install. No offense guys, but like Steve Jobs said, genius is next to insanity ;) <div><p>I dont think even the typical Mac user is going to be scared by a password request, especially if the installer dialog tells them why it happens. If they have chosen to install the app, they have already chosen to trust it. Most disk utility programs ask for a password too, even when they are launched under the admin account. I have never seen users complain about this. Just my opinion, but if you are concerned with appearances, it looks even worse when they have to use terminal to complete the install.</p> <p>No offense guys, but like Steve Jobs said, genius is next to insanity</p> <p>;)</p></div> true 2009-08-30T01:38:27-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-30T01:38:30-05:00 66641 me someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214 0 You're welcome to fork the project and create your own installer. :rolleyes: :P <div><p>You're welcome to fork the project and create your own installer. :rolleyes: :P</p></div> true 2009-08-30T02:18:09-05:00 58490 --- {} 214 installer-package-does-not-work-when-ran-under-non-admin-user 0 24342 bluesky 1.5b5 broken install installer non-admin permission pkg privilege receipt 2009-08-30T13:47:26-05:00 47272 simX someone http://rentzsch.lighthouseapp.com/projects/24342/tickets/214