0.9.3 18181 crashes directly after start on 10.6.2

[s0mebody]

Hi.

I just installed µTorrent 0.9.3 18181 (from "today") on my OS X Snow Leopard 10.6.2 system, but when I run it (after installed it in /Applications), I just get this:

Here's the complete text of what's shown in crash reporter:

Process:         uTorrent [5252]Path:            /Applications/uTorrent.app/Contents/MacOS/uTorrentIdentifier:      com.bittorrent.uTorrentVersion:         ??? (???)Code Type:       X86 (Native)Parent Process:  launchd [250]
Date/Time:       2010-03-03 18:19:49.528 +0100OS Version:      Mac OS X 10.6.2 (10C540)Report Version:  6
Interval Since Last Report:          198239 secCrashes Since Last Report:           7Per-App Crashes Since Last Report:   5Anonymous UUID:                      CCE7CFFB-36EB-4ECB-A84C-235B65DA7AD4
Exception Type:  EXC_BREAKPOINT (SIGTRAP)Exception Codes: 0x0000000000000002, 0x0000000000000000Crashed Thread:  0
Dyld Error Message:  Library not loaded: @loader_path/../Frameworks/Sparkle.framework/Versions/A/Sparkle  Referenced from: /Applications/uTorrent.app/Contents/MacOS/uTorrent  Reason: no suitable image found.  Did find:    /Applications/uTorrent.app/Contents/MacOS/../Frameworks/Sparkle.framework/Versions/A/Sparkle: stat() failed with errno=13    /Applications/uTorrent.app/Contents/MacOS/../Frameworks/Sparkle.framework/Versions/A/Sparkle: stat() failed with errno=13

An in /var/log/system.log, there's:

Mar  3 18:22:03 MacBook-Pro [0x0-0x1c81c8].com.bittorrent.uTorrent[5329]: dyld: Library not loaded: @loader_path/../Frameworks/Sparkle.framework/Versions/A/SparkleMar  3 18:22:03 MacBook-Pro [0x0-0x1c81c8].com.bittorrent.uTorrent[5329]:   Referenced from: /Applications/uTorrent.app/Contents/MacOS/uTorrentMar  3 18:22:03 MacBook-Pro [0x0-0x1c81c8].com.bittorrent.uTorrent[5329]:   Reason: no suitable image found.  Did find:Mar  3 18:22:03 MacBook-Pro [0x0-0x1c81c8].com.bittorrent.uTorrent[5329]:     /Applications/uTorrent.app/Contents/MacOS/../Frameworks/Sparkle.framework/Versions/A/Sparkle: stat() failed with errno=13Mar  3 18:22:03: --- last message repeated 1 time ---Mar  3 18:22:03 MacBook-Pro com.apple.launchd.peruser.502[250] ([0x0-0x1c81c8].com.bittorrent.uTorrent[5329]): Job appears to have crashed: Trace/BPT trapMar  3 18:22:03 MacBook-Pro ReportCrash[5330]: Saved crash report for uTorrent[5329] version ??? (???) to /Users/me/Library/Logs/DiagnosticReports/uTorrent_2010-03-03-182203_MacBook-Pro.crash

I tried deleting my settings - but couldn't find any *G* So I didn't delete anything there

Uhm - what can be done about this? 0.9.2 beta works just fine.

Regards,

s0mebody

[NoOneButMe]

Redownload the .app, its just not finding a framework it needs.

[s0mebody]

I'm confused - what should a REDOWNLOAD of the DMG file do? It's not like this is going to change what's IN the dmg, is it?

Anyway, the file I downloaded yesterday has this md5sum:

$ md5sum uTorrent-Mac-18181.dmg4d07c8073b2fb4280f2acee77f21c1fd  uTorrent-Mac-18181.dmg

Is this not correct?

Or did you mean that I should reinstall the .app from the DMG?

This didn't change anything. I had nothing installed, then I installed the non functioning 18181 build then I installed the working beta 0.9.2 and then I installed 18181 again. So I installed 18181 (at least) twice.

Between the installs/runs of alpha, no settings were left in ~/Library. I removed them.

[s0meb0dy]

Found it.

There's a packaging error in the 18181.dmg file. Check this out:

MacBook-Pro:~ alex$ ls -al /Applications/uTorrent.app/Contents/total 16drwxr-xr-x   7 root  admin   238 12 Feb 05:29 .drwxr-xr-x   3 root  admin   102 22 Okt  2008 ..drwx------   3 root  admin   102 12 Feb 05:27 Frameworks-rw-------   1 alex  staff  1695 12 Feb 05:27 Info.plistdrwxr-xr-x   3 root  admin   102 12 Feb 05:29 MacOS-rw-------   1 alex  staff     8 12 Feb 05:27 PkgInfodrwxr-xr-x  68 root  admin  2312 12 Feb 05:29 Resources

Pay attention to the permissions of the Frameworks directory. Only root is allowed to read stuff from this directory.

Don't you guys install the app in /Applications or why is it, that this gets overlooked? My user is set to a restricted account. It's not an admin account, just like it should be *G*

Whatever When could we get a fixed version, please?

[NoOneButMe]

Problem's on your system, looks fine for me:

N:~ nobm$ ls -la /Applications/uTorrent.app/Contents/total 16drwxr-xr-x   7 nobm  staff   238 Feb 11 23:29 .drwxr-xr-x   3 nobm  staff   102 Oct 22  2008 ..drwx------   3 nobm  staff   102 Feb 11 23:27 Frameworks-rw-------   1 nobm  staff  1695 Feb 11 23:27 Info.plistdrwxr-xr-x   3 nobm  staff   102 Feb 26 02:57 MacOS-rw-------   1 nobm  staff     8 Feb 11 23:27 PkgInfodrwxr-xr-x  68 nobm  staff  2312 Feb 26 02:57 Resources

Or to look at the .dmg:

N:~ nobm$ ls -la /Volumes/uTorrent/uTorrent.app/Contents/total 16drwxr-xr-x   7 nobm  staff   238 Feb 11 23:29 .drwxr-xr-x   3 nobm  staff   102 Oct 22  2008 ..drwx------   3 nobm  staff   102 Feb 11 23:27 Frameworks-rw-------   1 nobm  staff  1695 Feb 11 23:27 Info.plistdrwxr-xr-x   3 nobm  staff   102 Feb 11 23:29 MacOS-rw-------   1 nobm  staff     8 Feb 11 23:27 PkgInfodrwxr-xr-x  68 nobm  staff  2312 Feb 11 23:29 Resources

Like i said, redownload the .app.

[s0meb0dy]

I did a redownload and this didn't change anything - why should it? Do you have a different md5 then the one I posted? If not, then I really do not see how a re-download really could change anything.

MacBook-Pro:~ alex$ md5 /Users/alex/Downloads/Internet/µTorrent/uTorrent-Mac-18181.dmg MD5 (/Users/alex/Downloads/Internet/µTorrent/uTorrent-Mac-18181.dmg) = 4d07c8073b2fb4280f2acee77f21c1fd

Since 0.9.2 works fine and 0.9.3 doesn't (and any other app also work fine), it's very unlikely that the prob is on my side. It's just the 18181 app which doesn't behave like all the other apps, so don't you think it's much more probably, that the problem is on your side? I use a "Standard" user account - do you also use such an account? Or do you have an Admin account?

Oh, just compare what's in 0.9.2 and 0.9.3 dmg:

MacBook-Pro:~ alex$ ls -la /Volumes/uTorren*/uTorrent.app/Contents//Volumes/uTorrent 1/uTorrent.app/Contents/:total 16drwxr-xr-x   7 alex  staff   238 13 Nov 00:07 .drwxr-xr-x   3 alex  staff   102 22 Okt  2008 ..drwxr-xr-x   3 alex  staff   102 13 Nov 00:05 Frameworks-rw-r--r--   1 alex  staff  1687 13 Nov 00:05 Info.plistdrwxr-xr-x   3 alex  staff   102 13 Nov 00:07 MacOS-rw-r--r--   1 alex  staff     8 13 Nov 00:05 PkgInfodrwxr-xr-x  55 alex  staff  1870 13 Nov 00:07 Resources
/Volumes/uTorrent/uTorrent.app/Contents/:total 16drwxr-xr-x   7 alex  staff   238 12 Feb 05:29 .drwxr-xr-x   3 alex  staff   102 22 Okt  2008 ..drwx------   3 alex  staff   102 12 Feb 05:27 Frameworks-rw-------   1 alex  staff  1695 12 Feb 05:27 Info.plistdrwxr-xr-x   3 alex  staff   102 12 Feb 05:29 MacOS-rw-------   1 alex  staff     8 12 Feb 05:27 PkgInfodrwxr-xr-x  68 alex  staff  2312 12 Feb 05:29 Resources

In "uTorrent 1", there's 0.9.2, and in "uTorrent", there's 0.9.3. Have a look at the permissions of the Frameworks directory (0755 in 0.9.2 vs. 0700 0.9.3). 0.9.2 works fine, as it uses correct permissions.

Like I said, there is a packaging error in the 18181.dmg file. Reason why I say so: "all" other apps (incl. 0.9.2) work fine. Just 0.9.3 doesn't. And comparing 0.9.2 to 0.9.3 proves that.

> Whatever When could we get a fixed version, please?

[NoOneButMe]

I'm not seeing any problem in your second post. Permissions look fine. Just copy that µTorrent 0.9.3 into /Applications.

All your comparison proves is that you or something on your system changed the owner and group of the files. Not that the download is bad.

[s0meb0dy]

Please look closer, the problems are quite clear. Permissions of (eg.) Frameworks is 0700 but it should be 0755 (as it is in 0.9.2). Using 0700 is (close to) always wrong.

When I copy 0.9.3 to /Applications and run it, it crashes (see original post). Reason: The permissions in the source DMG are no good, and this causes, that the app can't find the framework libraries.

Yes, the download isn bad. The source DMG is bad. I have proven that. What else do you want to see?

When do we get a working version? As I have proven, the contents in the DMG are no good (because of bad permissions). Like I said: packaging error.

And no, I did not change the user / owner of the files in /Applications/uTorrent.app. It's completely normal that user is changed to root. Unless you use an Admin account, which you of course shouldn't do, for security reasons. What you've shown, is that you seem to use an admin account. To reproduce, use a "Standard" (ie. non-admin) account, install uTorrent 0.9.3 to /Applications and understand.

BTW: You told me to redownload. What should this have changed? Do you get a different MD5, then the one I've posted?

[NoOneButMe]

It's completely normal that user is changed to root.

No it isn't. Not on OS X.

Brush up on your unix permissions. owner, group, everyone else. 0700 means that the owner of the files has full read/write/execute access and no one else. That works fine.

So, look at the owner and group of the file. They're messed up in your local copy, but not on the volume. They should be alex:staff, not root:admin. And they are alex:staff on the volume. And the directory permissions have no bearing on executing a file within it, that can have different permissions.

I reiterate:

Just copy that µTorrent 0.9.3 into /Applications.

[s0mebody]

Boy, YOU don't need to tell ME to brush up my knowledge, when it's clearly YOU who doesn't know what he's talking about and proves this with every further post.

a) If you install something in /Applications, user/owner is changed to root. That is normal on OSX. Contrary to what you wrote, the permissions should of course not be so, that alex:staff is the owner:group. They should be so, that the owner is root. That's the normal way of setup. That's how "every" other application operates, even including uTorrent 0.9.2.

0700 is no good. You've even shown that yourself. Just create a test user on your system (eg. name it "john") and set it to "Standard" (ie. not Admin). Try to exec uTorrent from /Applications.

c) Using an Admin account for normal work is wrong (eg. for security reasons). You're using an Admin account (else the files in /Application/uTorrent.app wouldn't be owned by your user). Stop that and use your system properly. And you tell me to brushup MY knowledge? Laughable.

d) I don't know unix perms? This from a kiddie who writes: "And the directory permissions have no bearing on executing a file within it, that can have different permissions.". *LOL*. Explain, how (a theoretical) user "john" with "Standard" (ie. non-Admin) permissions could execute anything, which is stored in /Applications/uTorrent.app/Contents/Framework, if any of the directories has permissions 0700 and is owned by nobm:staff. If permissions were at least 0711, then we could talk. But with 0700? Please SHOW! Or accept that you're talking rubbish and that there's an error.

Again: 18181.dmg is broken, it has permission errors - put differently, the permissions are set so, that only root or the user who installed it (ie. root, in properly setup systems) would be able to execute the installed application.

What's your problem with accepting that there's an error? To me, it seems that it's just because you necessary knowledge - but that, you fully make up with your attitude.

To your "reiteration": As I've wrote, I installed the app in /Applications. Else I wouldn't have posted the bug report here. You can keep on reiterating as long as you want, it won't change anything, because simply reiterating something just won't make the packaging error from the uTorrent Team go away.

[NoOneButMe]

a) If you install something in /Applications, user/owner is changed to root. That is normal on OSX.

That is not normal on OS X. There is nothing in OS X that changes permissions of .app's that are placed in in /Applications.

c) Using an Admin account for normal work is wrong (eg. for security reasons). You're using an Admin account (else the files in /Application/uTorrent.app wouldn't be owned by your user). Stop that and use your system properly. And you tell me to brushup MY knowledge? Laughable.

Look at your permissions. They are root:staff. µTorrent (and pretty much every 3rd party app out there) will ship with alex:staff, not root:admin. You changed the owner and group. Thats the bottom line here.

What's your problem with accepting that there's an error? To me, it seems that it's just because you necessary knowledge - but that, you fully make up with your attitude.

I'm saying that the default download will work. You're introducing the problem in your attempt to make things "right" by changing permissions around. And I'm saying to stop changing things around. At least while default permissions are off, because you're breaking whats letting it work.

[s0meb0dy]

It is normal behaviour in OS X, that file ownerships are changed to root (or to the admin user, who has write permissions to /Applications). Unless you use an account of type Admin, which any good user with some minor knowledge of course doesn't do. I don't use an Admin account for normal usage. Do you? Yes, you do, you've shown that. It's not *Best Practice" to do so.

You're right in so far, that the owner is root:staff. That is absolutely normal behaviour. "Every" is shipped that way. No app is installed with file owner set to alex:staff. I really wonder why you keep on denying the truth. By now, it's of course to be expected, that you setup a test user with NO Admin rights (ie. a Standard account) and installed some apps (eg. uTorrent 0.9.3.1). Having done so, you have seen that what you wrote was wrong and that I just described, what's totally normal behaviour on OS X (10.6.2 for certain, but also in 10.5, IIRC - but I'm not so sure about 10.5 anymore, too long ago).

Prove:

/Applications/Skitch.app/Contents/:total 24drwxr-xr-x    7 root  admin   238 12 Jan 15:27 .drwxr-xr-x    3 root  admin   102 12 Jan 15:27 ..drwxr-xr-x    9 root  admin   306 12 Jan 15:27 Frameworks-rw-r--r--    1 root  admin  5297 12 Jan 15:27 Info.plistdrwxr-xr-x    3 root  admin   102 12 Jan 15:27 MacOS-rw-r--r--    1 root  admin     8 12 Jan 15:24 PkgInfodrwxr-xr-x  241 root  admin  8194 12 Jan 15:27 Resources
/Applications/Transmission.app/Contents:total 24drwxr-xr-x@  9 root  admin   306 22 Feb 03:45 .drwxr-xr-x@  3 root  admin   102 22 Feb 03:45 ..lrwxr-xr-x   1 root  admin    28 22 Feb 03:46 CodeResources -> _CodeSignature/CodeResourcesdrwxr-xr-x@  4 root  admin   136 22 Feb 03:45 Frameworks-rw-r--r--@  1 sv    501    3309 22 Feb 03:45 Info.plistdrwxr-xr-x@  3 root  admin   102 22 Feb 03:45 MacOS-rw-r--r--@  1 sv    501       8 22 Feb 03:45 PkgInfodrwxr-xr-x@ 93 root  admin  3162 22 Feb 03:45 Resourcesdrwxr-xr-x@  3 root  admin   102 22 Feb 03:45 _CodeSignature

"sv" is my admin user.

Any particular reason, why you deny this truth?

And no, I'm not changing any permissions around (at least not by doing something like chown/chmod manually, which you seem to have implied). Why do you try to blame ME for an error, that's introduced by the way uTorrent 18181.dmg is distributed?

So, now that we've got all that through, when do we get a fixed distribution of 0.9.3.1, since the 18181.dmg is broken (ie. is shipped with a packaging error, in so far, as it has bad permissions)? Or don't you care about uTorrent and its users? Distributing broken files for much longer than absolutely required doesn't seem like the right thing to do.

I find it quite confusing, that you make so much fuss about it. Everyone with a slight bit of knowledge about Unix permissions will easily understand, that 0700 permissions of a directory and ownership of eg. nobm:staff, will make it impossible for a user "john" to read/exec anything which is in that dir.

By now, you of course have created a test user "john", haven't you? And you have seen, that what I wrote was true. Just admit the tiny error in the DMG, release a fixed version and be done with it. What's the problem in doing so?

Lastly, really stop blaming me. I didn't do anything wrong. It's the DMG which is wrong, that's all.

[Firon]

sure, it's technically broken, but to be honest, the dmg works for everyone I know. my machine works and so does every other mac we used it on here. you've done something special on your system that breaks it. so here's a thought: don't fuck with OSX's permissions?

still, just to make you happy, we've changed the build script to correct the permissions on the DMG. next one will have it

[s0meb0dy]

Firon, once again: I AM NOT DOING ANYTHING SPECIAL! I AM NOT CHANGING PERMISSIONS!

Gosh. Is it really that hard?

The root cause of the problem is, that the permissions in the DMG are "sub-optimal". If they were properly set (like they were eg. in 0.9.2), then there would be no problem. This shows, that it's not my system which is causing problems, but your DMG is causing problems. That can also be seen by the fact, that every other app out there works just fine; it's just the 18181.dmg which doesn't and that in turn shows, that you've done something special there (and this "special" is, that the permissions for eg. the Frameworks directory is set to 0700).

Do NOT blame me for YOUR mistakes, okay?

And I doubt that it's working on every other system you've got. Heck, even NoOneButMe has shown that the app doesn't work on his system! If he'd create a test user "john" with Standard permissions, then this user CANNOT execute uTorrent from the 18181.dmg. This shows, that what you're writing is plainly wrong.

Should we assume, that you just don't know better? How could that be? Don't you test? Or do you lack knowledge? Both are bad choices, but you clearly write, that it's one of those.

Alexander

PS: Yes, I'm pissed off. Which is no wonder, if you have a look at the junk that NoOneButMe wrote (eg. "redownload app" - WTF should that change. Or "brush up Unix knowledge" - yeah, right, that from someone who's shown that he doesn't have Unix knowledge). And it's also pissing me off, that you, Firon, blow in the same horn. It's your DMG which is special.

[NoOneButMe]

Heck, even NoOneButMe has shown that the app doesn't work on his system!

No I didn't. Please don't put words into my mouth.

Since, according to Firon, the problem is solved, I'm closing the thread.