Well I guess Apple is copying some of Vista's features. Namly its lack of spit and shine out of the box. This is a list I would expect from a release canidate not a shipping product.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Seeds Mac OS X 10.5.1 9B13
- Thread starter MacRumors
- Start date
- Sort by reaction score
So it's only a real problem if you made a purchase based on info that wasn't final and could change? That wasn't very smart, was it?
So revert to your backup and report the issue to Apple. This is a beta release. If you're not willing to be a beta tester, don't be a beta tester.
It's called error correction, and it works, no "hoping" needed. I'm sure they'll add it sooner or later, they just need to make sure it's 100% reliable before they ship it.
Are you aware that without this sort of stuff macrumors would not even exist? Afaik, the admins have certain rules and they see they are not violated. So please take your law and morality campaign elsewhere.
The fact they didn't give the user tools to turn it off in Appearance makes it a bug, IMHO. I have a totally black desktop under the menu bar. So now my menu bar is about 50% gray and far too low contrast for my taste. When the cool factor gets in the way of getting work done, it's not a feature.
Keep those duplicate "transparent menu bar" bug reports coming at bugreporter.apple.com, folks!
I agree it should be an option. Having said that, I would be greatly disappointed if it were not an option to make it transparent.
and 2d dock should also be an option....I would also be greatly disappointed if apple releases 10.5.1 and the 2d work around gets blocked.
Please read the thread, this was a response to someone who said the whole notion of doing a backup over wifi was inherently shaky. The fact that you used a hack to try and make an unsupported feature work and it didn't doesn't support that claim.
There's a big difference between "wifi is shaky" and "my wifi is shaky".
It was the same with Tiger
And probably every major OS release on every platform.
Well look at it this way. a custom desktop scaled to exactly the size of the monitor resolution with a 22px white box behind the menu bar makes the menu bar a lot easier to read for me.
Basically, translucency is kind of a cool feature when you have interesting content that extends up that far, but it really and truly bothers me when the background is straight black behind it (and yes, I hated OS 8 and OS 9 too and used Kaleidoscope through that entire era). I'm glad it doesn't bother you; that doesn't make it a medical condition for those it does bother however.
I'm perfectly happy with the option of a translucent menu, just not with being forced to use it as is the current case.
One more reason to keep the updates small and frequent, Ubuntu does it fantastically, but this is not feasible for a popular commercial OS...
The fact they didn't give the user tools to turn it off in Appearance makes it a bug, IMHO. I have a totally black desktop under the menu bar. So now my menu bar is about 50% gray and far too low contrast for my taste. When the cool factor gets in the way of getting work done, it's not a feature.
Keep those duplicate "transparent menu bar" bug reports coming at bugreporter.apple.com, folks!
Well the fact that it does not serve my favorite beer is then also a bug, even when Apple never said it will serve beer of any kind. I guess I stand corrected.
If some people don't like Apple look and feel, it is a bug that must be corrected, regardless of Apple opinion and regardless of the opinion of other users, GOT IT!
hope they fix the finder glitches
1, the secure delete that hangs
2, the finder window disappearing when you unmount and drive or image
(#2) That is what the finder is supposed to do. When you unmount/eject a volume, its finder window disapears.
Anyway, about the only thing that I really would like is the ability to customize more aspects of front row. As it is, there is NO customization. This probably won't be until .2+, but whatever. I have noticed no significant glitches with Leopard since I installed it the day it came out...
I would bet you 99.9% of the users have had nothing but good impressions (and I'll bet even higher than that). So no there is not a lack of spit-and-shine, just some honest to goodness bugs that are often because of customizations and changes. The issues in Leopard have been no worse than your average point release upgrade.
Its so funny that people seem to have latched onto this file move bug as an "OMG, LEOPARD IS SO BUGGY AND AWFUL" thing when even the press release itself state that this has been confirmed as far back as Panther. What does it have to do with Leopard?
I have to admit I am more impressed as I use it -- this is my first full day working on a leopard system, and I am impressed by the speed and responsiveness relative to Tiger, and I may warm to Spaces yet -- its implementation is slick, and combined with the other OSX interface niceties (bouncing icons to tell you input is needed) it seems to really work well.
Sure there are bugs -- stacks, the embarrassing issue of Time Machine not working with Aperture, but as a point-oh release its pretty good.
Did you have a look at the release notes before installing?
They can't simulate everything in their test labs. That's why ADC members get early seeds (and to test their own software).
In the both cats ejecting a volume both closed the window or didn't at different times. I don't know what determines if it'll close or not, but it did had both behaviors for some reason. When it doesn't close it goes to the top computer window (viewing drives and network).
I have a separate problem in Leopard that forces me to eject volumes on all logged in accounts (by switching users first) when I mounted them in just one.
Nobody believed me on these forums when I said I thought that 10.5.0 was going to be buggy as hell because of the finagling around its release schedule and diversion of Apple's resources.
I'm so glad I've held off on upgrading to Leopard. Maybe even until 10.5.2 or 10.5.3 from what others seem to be saying...
I'm so glad I've held off on upgrading to Leopard. Maybe even until 10.5.2 or 10.5.3 from what others seem to be saying...
No, because sbpcat implied that he himself has updated the machine. He has also admitted that he is an ADC member. spbcat is under and NDA. That was the failure in your earlier statement. The first post of this thread is by Macrumors, who is a third party source of the information. spbcat addressing us makes him a first person source for information.
Admittedly, without seeing the original submission to this story, we don't know if the ADC member themselves emailed arn. It could be they were speaking through yet another proxy that was let in on the news over lunch or something. So even the tipster may not actually be under an NDA.
This has happened to me once or twice, but I never chalked it up to a bug per se... It just seemed logical that unplugging a hard drive that's being written to by the OS in mid-write would result in an unstable drive (usually this happened when something accidentally flipped off the power strip).
The only problem I have is, that some 3rd party vendors are not Leopard ready on time and you can't blame Apple for that. In general 10.5 runs fine.
LOL - I just might. There's no amazingly compelling reason to update to Leopard right now, not when developers are still compiling for compatibility with 10.3.9 (though I would expect this to very soon shift to 10.4.11). Sure, there's a lot of under the hood changes with Leopard, but so there was with Tiger and that really didn't stabilize until at least 10.4.3, and others would argue for even a later build.
Its something I've never done, except by accident for similar concerns. My biggest one being, even if it handles it perfectly, one move at a time, and gets interrupted I now have a tree that is split 1/2 on one drive and 1/2 on another -- how do I remerge them? Or maybe it copies the whole tree then deletes, but can I risk that was what really happened?
So I've always done a two-step copy and delete or if its larger most likely a 'tar cvf - * | (cd /Volumes/a; tar xf -)' if I really wanted to be careful.
That's probably why it has taken so long to notice this ... moving across partitions is just a bad idea in general...
While I agree that the alleged bugginess is probably overblown, the data loss bug supposedly has been fixed for a while and reappeared in Leopard.
And for the most part they were right.
That's not the problem - I'm sure we'd all expect a drive being written to may have problems with the file getting written being lost or corrupted in the case of an interruption. The problem is that the file is lost on the drive the file is coming FROM. There's no reason for this to happen, it's something apple needs to fix.
Based on what AI says in their article, this may be addressed in 10.5.1.