Of Canaries
So, I missed the last Apple Bug Friday, or maybe I missed the last two, as it's all kind of blurring together at the moment, but I'm reasonably sure I missed the last one. This was kind of disappointing, as earlier in the week I'd done some thinking about the lamest bugs in Mac OS 10.4 Tiger.
For something to be considered The Lamest Tiger Bug™, it isn't enough for it to just be an obvious bug. It has to be a bug that so downright sickly sad that, like a dead canary in a coal mine, its state of being tells us something, somewhere, has gone horribly awry. This won't be exhaustive, but rather just what comes to mind...
I first mentioned this in The Downward Spiral, but the text wonkiness has always been there -- it's just gone crazy in Tiger.. and to quote Rentz, "NSTextView ain't right."
I primarily hear about it from developers with XCode, which I'm guessing is due to them having a higher likelihood of using larger blocks of text within a Cocoa app, instead of say, using Microsoft Word or such. Just including this bugginess in a launched product -- when people at Apple had to be aware it was around -- would have brought it to mind for this list.
However, it's going on six months since 10.4 has been released, and six years since Mac OS X has been released, yet Cocoa applications still can't deal correctly with non-trivial amounts of text, and it's getting worse.
To my knowledge, all Unix-a-like systems have some sort of way to run things periodically. An example might be scripts to roll over log files, or clean up caches, or anything you want your system to do. Big deal on servers, and on most systems, this takes the form of cron, which allows you to specify a script or app that you might want to run weekly, monthly, daily, hourly, every 5 minutes, etc.
For Tiger, Apple decided they wanted to do better than cron, and introduced something called launchd, which among other things took over the running of periodic tasks. Unfortunately:
- It only ran tasks once after every reboot. This meant that the daily maintenance scripts would run correctly the first day, but wouldn't run on the second day, let alone your own scripts you may need to run. The workaround was to bypass
launchdand put all the scripts back ascronjobs. - Apparently,
launchdwas reliant upon the kernel in order to tell time, yet apparently there was a bug in the kernel causing it to lose time while the computer was asleep. So if you had your computer asleep for 3 hours, and fired it up, a script that was supposed to run at 5pm would get run at 8pm. The computer knew what time it was in the menu bar, butlaunchddidn't.
That first one was a doozy, and about as embarrassing as a bug can get -- to be quiet honest I'm trying to think of corollaries on other platforms and coming up blank. It was just insanity.
What made it especially amusing is that cron is one of the most well-known technologies out there. Every system admin knows it and generally relies on it in some form, and "deprecating" it was already going to cause raised eyebrows -- but deprecating it with such a broken implementation is the stuff of legend.
I believe the first was finally fixed in 10.4.2, but lets just say it didn't help them get traction in the enterprise market -- it's akin to a practical joke on those tasked with trying to sell Apple solutions to larger institutions. We're not going to even go into lookupd, oh no, lookupd would take its own post and its state in Tiger is the least of its wonkiness.
This one had a special place in my heart. For iPhoto 5, Apple broke their modus operandi of including the previous version of iPhoto with the new OS, so if you upgraded to Tiger you were having to pick up iPhoto 5 as part of iLIfe '05. The big feature of the new version was its color adjustment panel, unfortunately if you actually cared about how your photos looked you couldn't do anything to them in iPhoto, as it would fuck with the color.
For reference:
- Mac OS X 10.4.2 Fails to Fix iPhoto 5 Color Profile Problem
- iPhoto 5.0.x and unwanted color shifting
Basically, images often have 'profiles' embedded in them to keep them looking as they should look on different devices. For whatever reason, if you touched the image with iPhoto 5 instead of just using it to store them, it would embed the Generic RGB profile instead of respecting what the file walked in with, which meant you had to use Photoshop or Adobe Elements or anything but iPhoto to adjust your image. This was finally fixed with iPhoto 5.0.3, which was released right after 10.4.2.
One could argue that enough stupid bugs would equal a canary in and of itself, but I'd say this qualifies as a major canary on its own, because it begs the questions:
- Did no one developing iPhoto even notice this?
- Did no one responsible for making sure iPhoto worked notice this?
- Did they notice it, but decided to ship it while knowing it was going to fuck up user's images?
Pick any, and the canary is dead, which is worrisome.
Take an image, and open it in Apple's Preview.app, like so...
Now, rotate it in Preview.app via one of the great big giant rotate buttons, like so below, and save it as a separate file...
If you open it in Preview.app, it's still rotated. If you view it within the Finder.app, you would be forgiven for thinking it was actually rotated...
However, if you open it in, say, Safari or anything else, including another image app, it's not rotated...
Right. Worked correctly before before 10.4, doesn't work as of 10.4.2, and justly deserves a WTF. Not because it's an end-of-the-world bug, but rather what one can infer from a bug like this making it into a public release, as well as it remaining unfixed.
If you want to edit text via the terminal, you have a few options. Some people gravitate towards emacs, some towards vi, and some towards pico. I use vi when I have no choice because the task demands it, but let's just say my brain and vi don't align as they should and I am constantly having to relearn commands. For just about everything else, I just fire up pico -w because it's fast and simple, and yes, I know a few will mock me, because Mac vs PC has nothing on emacs vs vi and I might as well be admitting to being partial to the Amiga.
Anywho, in 10.4 Apple made the decision to replace pico with an app called nano, by funneling all the commands and options that would normally go to pico towards nano. This was actually kinda cool, as nano is essentially an open-sourced clone of pico with correlations for all of its options. Since it's transparent, a normal user would never know his command to open pico was being mapped to nano, unless they happened to peek at the process list and see it running.
Unfortunately, there's a big fat bug which has been common knowledge since around April, that's very easy to reproduce:
- Open a terminal window.
- Type "nano" (without quotes), add a space after the word "nano", and then drag a .txt file from the Finder onto the terminal window, then hit return. You should see your text file opened within
nanofor editing. - Resize the window to be larger.
- The window should blank out and become unusable for any further commands, and if you open another terminal window and run
top, you should seenanousing 60-100% of your CPU. - The only people I'm aware of being unaffected are those who use
screento manage multiple sessions, and you could also type "pico" instead of "nano" above and you'll get the same thing.
The Nano-Pico bug completely wigs me out, and is one hell of a canary. Apple has to be aware of it, because it'd be just as scary if they weren't.
Like I said, the above isn't comprehensive, just examples coming to mind, and I'm sure you can come up with other canaries to compete for the title of The Lamest Tiger Bug™. There are others I have in mind I could jot down, but just banging out what I have was depressing enough, and to soldier on I'd need enough liquid courage lubricating my brain that I'd end up snoozing through the alarm.
Did I mention we're going on half a year into Tiger being out?
Posted by drunkenbatmanOctober 06, 2005, at 04:01 AM
Comments (47)
Posted by: Mac-arena the Bored Zo at October 6, 2005 04:09 AM
there's a bug reporter you can use for WebKit issues. I already searched (for 'rotation' and 'JPEG'), and found no existing bugs filed for this.
Posted by: drunkenbatman at October 6, 2005 04:16 AM
on the rotated-JPEG thing: that sounds like a WebKit bug, wherein it doesn't respect the rotation setting in the JPEG file. I don't know why it would work before and not work now, though.
I said "Safari, or anything else", which includes way more than webkit. Try, say, Camino or JView or, um, anything -- it's not limited to Safari, rather this is something Preview is doing now in 10.4. :)
Posted by: Diggory Laycock at October 6, 2005 04:37 AM
In the 'Oh launchd' section - you appear to have missed the 'd' from the end of a couple of daemons a couple of times.
'Apparently, launch was reliant...'
'..not going to even go into lookupd, oh no, lookup would take its own post..'
Posted by: drunkenbatman at October 6, 2005 04:42 AM
In the 'Oh launchd' section - you appear to have missed the 'd' from the end of a couple of daemons a couple of times.
Thanks, got the two you mentioned. Oh god, its now 4:30am...
Posted by: Carl at October 6, 2005 04:49 AM
My pet peeve bug of the day:
In an Open dialog, if a file's name doesn't fit into the column, it get's a *white* tooltip. Finder gives it a proper yellow one. Think about what this means:
For once Finder is the one not f'n' up the UI!!
It's a Bugsmas Day Miracle!!!
Posted by: nemo at October 6, 2005 05:13 AM
Those bugs were ok, but the worst apple bug EVER is right here:
char *envStr = nil;
envStr = getenv("USER");
//check for member of admin group
if ( (envStr != nil) && UserIsMemberOfGroup( inDSRef, inDSNodeRef, envStr, "admin" ) )
{
return true;
}
We reported this to apple before they removed the dsidentity suid.
For anyone who can't see the obvious bug, they test the user controlled environment variable "USER" to check if the user is a member of the admin group.
enjoy
- nemo
Posted by: at October 6, 2005 07:50 AM
now you are just being mean...
Posted by: slinkyfox at October 6, 2005 08:07 AM
who is the blonde? ;-)
Posted by: lazlo at October 6, 2005 09:06 AM
Hey db
Usually I appreciate your apple bug reports (though I should let you know today's definitely Thursday, not Friday -- but whatever), but I think your rant on launchd is undeserved. I applaud apple for taking on the vast inertia that is UNIX, and trying to sanitize the idiocy that it is. I should know -- I'm a linux sysadmin by training. You may be right that launchd doesn't work, it could be a bug. But the developer pages suggest that you might wrong, and that it may be that people who've tried to migrate from cron to launchd just did a poor job.
What I especially applaud about launchd is that you can specify in one place per program, exactly when it should be done: "every tuesday at 9am, once after each startup and whenever someone connects to TCP port 8000", say. That's the sort of flexibility that requires lots of messy config files or some sort of meta-config layer on a typical UNIX.
Posted by: Brian Webster at October 6, 2005 09:09 AM
I tried the JPG rotation thing with Preview, and indeed it opens up un-rotated in Safari and OmniWeb, but it opens up rotated using GraphicConverter. There's also a little note in the info panel in GC that says the picture is "rotation corrected". So it looks like this is a feature of the JPG format that's recognized by some programs, but not a lot. Quicktime Player opens it up un-rotated, so perhaps Quicktime is the root of a fair share of the bugginess in this respect, since all sorts of apps (plus Cocoa) use QT to read images.
Posted by: 2.STL-DX.B11 at October 6, 2005 09:14 AM
This was initially something I was really interested in, but I truly couldn't give a toss about any of these bugs now you've gone and included the picture. That was such a foolish move....I'm more interested in the photograph's content (the brunette actually). Anyway, now that I've probably made comments about your girfriend or something I should slope off to avoid getting a kicking.... At least if she IS your girlfriend you'll get the warm glow that comes with knowing how envious other fellows are.
But, you're right - That iPhoto bug was an utter disgrace. They go all out to prevent illegal copies of unreleased versions of the OS making it out to newsgroups/P2P networks etc. but frankly I reckon there's plenty of those who download those illegal versions that would be able to spot this sort of tripe before it ever blighted a final release.
Posted by: Jeff at October 6, 2005 09:14 AM
Case-sensitive search in Keychain Access. Do I have to memorize how the names are capitalized? Really incredibly lame.
Of course, there's the lamest OS X bug of all time: Safari STILL doesn't remember the last window position. Do we have to wait until OS X 10.7 for Apple to finally fix that stupid bug?
Posted by: bugluvr at October 6, 2005 09:32 AM
Does this one count?
Still can't reorder startup items in list since 10.4.0.
Posted by: Skorp at October 6, 2005 10:09 AM
I vote that the award should go to the Text Bug. Heck, it even appears in Mail.
Reading your posts is depressing. One wants to love Apple, and one does, but...
In the mean time: Mmmmm, hot bitches!...
Posted by: anon at October 6, 2005 10:12 AM
You are missing the point of launchd. launchd replaces init and is going to become the default way of launching processes. launchd is not replacing cron, at least not right now. Since there are so many ways to launch a unix process, I think it is great that Apple is trying to consolidate all that together into launchd. cron still works so there is no cause for alarm but some day you will probably be able to do everything from launchd that you can currently do from cron (and a lot more).
Posted by: James at October 6, 2005 10:16 AM
My favourite: in Finder, try renaming something with no difference other than a change of case - eg Index.html to index.html. Finder pops up an alert saying "The name 'index.html' is already taken, please choose another."
You can do it in the terminal, but this to me just shows how wrongbrained Finder is with its native filesystem.
Posted by: Ben at October 6, 2005 10:22 AM
My favorite weirdness was that under 10.3 something, screenshots were slightly red. So if I took a screenshot of a screenshot &c., the resulting image would have totally skewed coloring.
I assume it might have had something to do with color matching, but this was on an iBook with all default configuration in that regard. Maybe it had to do with trimming least important bits off the color with a poor, poor algorithm.
Posted by: ACSA at October 6, 2005 10:25 AM
DBM,
with all due respect, the launchd "bug" was fixed with 10.4.2 and even though there's a lanchdaemon that starts/stops the cron daemon, cron's not deprecated and certainly has been replaced by launchd. The actual relationship between launchd and cron is thus:
the /System/Library/LaunchDaemons/com.vix.cron.plist file monitors all crontab files on the system. If a crontab such as /etc/crontab is modifed, the launchdaemon will immediately start the cron process and as of 10.4.2, all tasks correctly specified in the crontab will run on schedule. The launchDaemon only decides whether cron should run or not. If you take a look at the /etc/crontab file, you'll see that the daily, weekly and monthly maintenance tasks are still in there. Launchd does just what its supposed to: launches the cron process when necessary. Launchd does have its own scheduling capabilities, but Apple isn't replacing cron, nor has it deprecated it in any way.
A little research here would have revealed this bug long squashed. I'm kind of suprised you even mentioned it. Sorry for the long post, my nstextview works, at least on your site. Rock on!
Posted by: Uli Kusterer at October 6, 2005 10:44 AM
DB, he's still called Rentzsch. Three letters more than you're giving him. Poor Wolf.
Posted by: Stern at October 6, 2005 12:04 PM
Preview seems to be storing the rotation in EXIF info embedded in the image. If I save a picture to a new file the "Orientation" tag is set to "Top left", if I rotate the picture left it is set to "Left bottom" and when rotated right it is set to "Right top".
My personal most annoying bug is that it seems to be impossible to set all four time formats to what you want. At least one seems to revert to the default setting every time you try!
Posted by: anonymoose at October 6, 2005 12:25 PM
I can't speak for everyone, but saving rotated images in preview and then opening them up in Safari works like a charm on 10.4.2 here.
Posted by: BP at October 6, 2005 12:42 PM
ACSA: re-read DB's post. He does mention that bug 1 was fixed. Bug 2 is definitely not fixed. Tiger 10.4.2 is running on completely up-to-date machines here and all have their scheduled tasks delayed by hours due to the machines having been in sleep mode (not being asleep during the time the task was supposed to run but just being asleep).
Posted by: thickslab at October 6, 2005 01:50 PM
James: filename case insensitivity is an intentional design feature, not a bug.
Posted by: Wes McGee at October 6, 2005 02:21 PM
The last bug report was a month ago (not counting the Preview bug report wtf response), so you actually missed about 3. Everybody misses this image.
Posted by: ACSA at October 6, 2005 02:36 PM
OK,
So DBM's possibly about the sleep/time issue with launchd. He's not right about Apple deprecating cron. It's amazing how launchd's become the stuff of urban legend so quickly. Launchd was never intended to replace cron, yet I've heard from many uninformed OS X users that "Cron's GONE" in Tiger. DBM isn't helping out with that.
Posted by: Twist at October 6, 2005 02:58 PM
The thing that is pissing me off about Mac OS X 10.4 these days is the fact that I have to keep reinstalling my fonts on a weekly basis. For some reason Times New Roman and a few other crucial fonts keep displaying with jacked up characters for me. I replace them and everything will be fine for about a week and then I will need to replace them again.
Posted by: drunkenbatman at October 6, 2005 03:12 PM
lazio said...
...but I think your rant on launchd is undeserved. I applaud apple for taking on the vast inertia that is UNIX
I don't have a problem that launchd exists, but rather that launchd was shipped broken -- especially since it was taking on "the vast inertia that is UNIX." If you're going to try to talk people into using something different than what they've used for a decade, it's a good idea to make sure it works.
But the developer pages suggest that you might wrong, and that it may be that people who've tried to migrate from cron to launchd just did a poor job.
Nope, check the fixes in the system updates. :)
Brian Webster said...
So it looks like this is a feature of the JPG format that's recognized by some programs, but not a lot.
I think we were here with attachments in Mail.app pre-10.3, where it was claimed that there wasn't a problem with how Mail.app handled them, it was just that most other clients weren't supporting how it handled them -- yet it changed with 10.3.
DB B11 said...
This was initially something I was really interested in, but I truly couldn't give a toss about any of these bugs now you've gone and included the picture. That was such a foolish move....I'm more interested in the photograph's content (the brunette actually).
Fair point -- didn't occur to me, just grabbed what was handy.
anon said...
You are missing the point of launchd. launchd replaces init and is going to become the default way of launching processes. launchd is not replacing cron, at least not right now.
Um, Apple didn't remove cron from the system, but is Apple saying launchd is what you should be using for periodic tasks? Yes. Did they move the periodic tasks from cron to launchd, so that when launchd wasn't working a bunch of people went and moved them back to cron? Yes. From Apple's developer page on launchd:
"The launchd daemon takes over many tasks from cron, xinetd, mach_init, and init, which are UNIX programs that traditionally have handled system initialization, called systems scripts, run startup items, and generally prepared the system for the user."
I mean hey, they still left Startup Items around too (which was a good thing, as there are situations where as of yet you need them instead of launchd) even though launchd also does the same stuff. launchd is meant to be sort of consildated umbrella for a bunch of services (including init, etc.)
ACSA said...
with all due respect, the launchd "bug" was fixed with 10.4.2 and even though there's a lanchdaemon that starts/stops the cron daemon, cron's not deprecated and certainly has been replaced by launchd. The actual relationship between launchd and cron is thus:
Deprecated may have been a poor choice of words (superseded?), but I don't think so. Apple didn't remove cron, but launchd has overtaken its role in the system -- see the quote above.
A little research here would have revealed this bug long squashed. I'm kind of suprised you even mentioned it.
I mentioned it was squashed, but ALSO mentioned it because the fact that it existed is scary as all hell, which is what makes it a canary.
Kusterer said...
DB, he's still called Rentzsch. Three letters more than you're giving him. Poor Wolf.
He'll get even.
Wes McGee said...
The last bug report was a month ago (not counting the Preview bug report wtf response), so you actually missed about 3. Everybody misses this image.
Inconceivable!
ACSA said...
So DBM's possibly about the sleep/time issue with launchd. He's not right about Apple deprecating cron.
I'm always right! Except when I'm not.
Posted by: John Faughnan at October 6, 2005 04:27 PM
The rotation bug is worse than you think.
If a camera supports the EXIF orientation tag, Image Capture will try to rotate it on import but it will create two EXIF rotation tags. It's done this since 10.3 at least, Thorsten (GraphicConverter) and I figured it out.
The extra tag confuses the heck out of graphics apps. Some crash, some do an extra rotation (iPhoto) so the image is incorrect, some get confused about the thumbnail, etc.
GraphicConverter checks for the duplicate tag and fixes it. (Gives a 'corrupt tag' warning.)
This bug is years old, but Apple ignores it.
Posted by: Anthony at October 6, 2005 05:57 PM
I don't have a problem that launchd exists, but rather that launchd was shipped broken -- especially since it was taking on "the vast inertia that is UNIX." If you're going to try to talk people into using something different than what they've used for a decade, it's a good idea to make sure it works.If you had to pick one word to describe UNIX it would be "pragmatism". A lot of things about other OSes are more elegant or perform better but it's the success that it is because you can hack stuff together very quickly.
When tools are supposed to be automatic fail in such a way that they require manual intervention (or worse, don't even tell you), it scares people off. If launchd gets a reputation for silently failing in weird ways, people will avoid it because even when it works find they've got to check up on it.
Posted by: vastheman at October 6, 2005 06:05 PM
One that still annoys me is that a terminal window will lock up if you paste a large amount of text into it (more than 100 lines or so). This appeared in Panther and is still there in Tiger.
Posted by: Kurt Moore at October 6, 2005 06:46 PM
Glad someone knows about the pico/nano issue, I reported it:
on sept 7, and no reply from apple yet.
Quick fix, scp pico off some older machine, or download it and compile it, then kill the symblink to nano.
I was quite surprised no one here had a official fix, this has bugged me since day one of 10.4
Posted by: James at October 6, 2005 07:28 PM
Add this to the list of annoying bugs in 10.4x...
In the Finder, when you are in list view you can't use "cut" to edit a file name. It works fine in icon and column view, but nothing happens in list view. This annoys the hell out of me.
It worked fine in 10.3. How the hell did they screw that one up?
Posted by: say it ain't so at October 6, 2005 11:00 PM
I used to think that your geek quotient was maximal. But now I'm just confused. How can a hard core geek know girls that good?
Something has to give, you can't have powers in both worlds.
Posted by: Matthias Lilke at October 7, 2005 04:36 AM
The picture rotation issue is a feature called lossless rotation. I believe it's primary use is to prevent distortion when rotatin pictures with non-square pixels (some video snapshots, for example). Therefore I believe it's an implementation issue in general. I'm not sure how 'new' this feature is but that could be an answer.
Posted by: Peter da Silva at October 7, 2005 03:01 PM
In my naivete, I thought that Launchd was at the very least a superset of SystemStarter. One of the things SystemStarter does that is really nice is to track dependencies:
Description = "PostgreSQL database server";
Provides = ("PostgreSQL");
Requires = ("Resolver");
Preference = "Late";
This means that Postgres won't be started until the resolver is working and it can look up the addresses of network hosts by names. This is a great leap forward from the traditional UNIX run levels and numbered scripts, where the system administrator has to guess what number to use and generally makes all new scripts start with "99".
Does launchd do this? Well, of co... wha... it doesn't? Whisky Tango Foxtrot, over?
That's not just a bug, it's a design flaw that must be addressed post haste. I haven't upgraded to Tiger yet, but if Apple hasn't fixed that one by the time I do I'm gonna be distributing an enhanced launchd of my own... since we HAVE the source...
In fact I'm downloading it right now...
Posted by: icedtrip at October 7, 2005 05:17 PM
ok, so i have tried replicating your preview rotating bug about a million times, but for the life of me i can't get the women in my pictures to look that good.
i try one angle, no luck. i try another angle, no luck. i open in safari, photoshop, or gimp...nothing. i had hopes for graphiconverter due to "convert" being in the name, but still, i don't have a fine looking blonde and brunette in my image.
db, how do you do it?
Posted by: James at October 8, 2005 04:31 AM
thickslab: please explain how I should tell my Unix webserver "well I made these files in OS X so it's case insensitive, so you should agree" and at that point I'll agree with you that it's a feature not a failing.
Posted by: drunkenbatman at October 8, 2005 04:50 AM
thickslab: please explain how I should tell my Unix webserver "well I made these files in OS X so it's case insensitive, so you should agree" and at that point I'll agree with you that it's a feature not a failing.
To be fair, HFS+ is case-insensitive but case-preserving, which means the info is there but is ignored. To be fairer, while Apple is dumping out support for UFS (I'm not super hot on UFS, but not exactly a great fan of HFS or HFS+ either) they have introduced a case-sensitive HFS+ option when formatting for Panther Server and now 10.4.
To be fairest of all, it isn't supported for boot volumes and isn't recommended for any volumes, and is a pretty sharp pain to many having to deal with compatibility issues -- especially when a Mac user says "Why would you have files like that anyhow."
Erm, it's past 4am again, and I'm talking about HFS+. Not good.
Posted by: christoph at October 10, 2005 10:59 AM
As for lamest bug in tiger i'm with Rui Carmo - logging key translation errors on every keypress to windowserver.log should've never made it through any decent QA process.
Posted by: Anthony at October 10, 2005 11:10 PM
It bugs me how iTunes continuously beachballs when it's doing anything hard (updating my iPod, importing songs, determining song volumes, etc). We're at version 5.
Posted by: dudewholikeschicks at October 11, 2005 10:14 AM
Can I just say "damn" in regards to the chicks in the picture?
Also, it's a little sad that I only saw one other comment along these lines. C'mon guys.
Posted by: Peter da Silva at October 12, 2005 07:19 PM
Anthony: we're at version 6 now.
Posted by: Peter da Silva at October 12, 2005 07:28 PM
I vote for putting /var/log in ramdisk. Except they don't seem to have mfs or equivalent in osx.
Hmmm... you can use the hard disk image tools to do it, but that's probably to late in the boot process to help.
Boogers.
Posted by: Anthony at October 13, 2005 01:06 AM
we're at version 6 now.That will make my criticism stronger if it's still there. Please note however that I will be waiting at least a week...
Posted by: Rob at December 5, 2005 12:56 AM
That issue in Preview is one of the oddest bugs I've seen in a while... It caught me very soon after I started using MacOS.
Posted by: caesurae at December 7, 2005 02:28 PM
I haven't upgraded to Tiger yet, but I'm all too familiar with the Preview bug. Although...the same thing happens to me when using the Crop function. Many apps will display the "cropped" version in it's original, unedited state.
Also, regarding James' reported bug. On my Panther system, I can use the Finder to rename "Index.html" to "index.html" just fine. Apparently, James cannot. That sounds like a bug to me.
on the rotated-JPEG thing: that sounds like a WebKit bug, wherein it doesn't respect the rotation setting in the JPEG file. I don't know why it would work before and not work now, though.