Here’s the Quicktime video stream of this years WWDC 2011 keynote about Mac OS X Lion, iOS 5 and iCloud … and how it all works together. So, tune in to see Steve Jobs, Phil Schiller and Scott Forstall presenting the newest software developments.

This years WorldWideDeveloperConference WWDC 2011 sould out within 8 hours. So, bad luck if you’ve been on a transatlanic flight at that time. Today, the lucky ones of the iOS & Mac developer community, who managed to get a ticked this year, gather at the Moscone West Center in San Francisco. Probably, Apple will share the videos of all of the WWDC sessions for free with their registered iOS & Mac developers, like they did last year. And even if the Cupertino guys won’t stream Steve Jobs keynote live, we’ll get a video stream short after the event. For real live coverage we can rely on the all those people blogging from the keynote. The keynote begins at 10:00 AM PST (07:00 PM CET) and there are a lot of things to cover: The next version of Mac OS X called Lion, the next version of iOS for iPhones & iPads and Apples new cloud service iCould.
Here’s my link list for live coverage of the event:

• Tim Stevens & Darren Murphy for Engadget … Tim & Darren start their pre-keynote-roundup at 07:30 AM PST via UStream videostream and continue with the keynote coverage
  (Liveblog technology: UStream (not via iOS) & ? iOS-friendly engadget cms ?
• Ars Technica … live blog will start with the keynote
  (Liveblog technology: ScribbleLive, disabled for iOS).
• Greg Kumparak for TechCrunch … live blog will start at 08:45 AM PST – 17:45 CET
  (ScribbleLive, not iOS optimized).
• TheNextWeb … live blog will start at 09:30 AM PST – 18:30 CET
  (ScribbleLive, iOS friendly).
• Jason Snell & Dan Moren for Macworld… live blog will start with the keynote
  (Liveblog technology: CoverItLive, iOS-friendly)
• Technologizer … live blog will start with the keynote
  (CoverItLive, iOS-friendly).
• MacLife … live blog will start with the keynote
  (CoverItLive, iOS-friendly).
• Adrian Kingsley-Hughes for ZDNet … live blog will start with the keynote
  (CoverItLive, iOS-friendly).
• Arron Hirst for RazorianFly … live blog will start at 09:30 AM PST – 18:30 CET
  (CoverItLive, iOS-friendly).
• Gizmodo … live blog will start at 09:00 AM PST – 18:00 CET
  (Liveblog technology: unknown, iOS-friendly).

As soon as the keynote is available as a Quicktime stream, you’ll get an update here

I had a lot of trouble with some rubygem warnings after upgrading to Ruby 1.9.1 and Rails 3.0 on Mac OS x Snow Leopard. They always occurred when I started the server within the project with the command

rails server

At first, when running on bundler 0.9.3, I had two types of errors. The first NoMethodError populated the terminal with hundreds lines of code, like …

WARNING:  # NoMethodError: undefined method ` ' for nil:NilClass 
# -*- encoding: utf-8 -*-
...
WARNING:  Invalid .gemspec format in \
'.rvm/gems/ruby-1.9.1-p378/specifications/spec.gemspec'

The bundler-team around Carlhuda fixed that issue within bundler 0.9.4. So that problem will not occur any more.
The other problem was quite persistent. When starting the server via

rails server

or doing a test via

rake

within the rails-3-project resulted in a bunch of warnings:

/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:14: \
warning: already initialized constant VERSION
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:14: \
warning: already initialized constant RubyGemsVersion
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:194: \
warning: already initialized constant MUTEX
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:196: \
warning: already initialized constant RubyGemsPackageVersion
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:202: \
warning: already initialized constant WIN_PATTERNS
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:1079:\
 warning: already initialized constant MARSHAL_SPEC_DIR
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems.rb:1084: \
warning: already initialized constant YAML_SPEC_DIR
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/version.rb:72: \
warning: already initialized constant VERSION_PATTERN
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/requirement.rb:20: \
warning: already initialized constant OPS
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/requirement.rb:30: \
warning: already initialized constant OP_RE
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/version.rb:246: \
warning: already initialized constant Requirement
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:18: \
warning: already initialized constant TYPES
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/platform.rb:171: \
warning: already initialized constant RUBY
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/platform.rb:177: \
warning: already initialized constant CURRENT
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:39: \
warning: already initialized constant NONEXISTENT_SPECIFICATION_VERSION
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:50: \
warning: already initialized constant CURRENT_SPECIFICATION_VERSION
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:56: \
warning: already initialized constant SPECIFICATION_VERSION_HISTORY
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:72: \
warning: already initialized constant MARSHAL_FIELDS
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:75: \
warning: already initialized constant TODAY
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/source_index.rb:593: \
warning: already initialized constant Cache
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:14: \
warning: already initialized constant DEFAULT_BACKTRACE
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:15: \
warning: already initialized constant DEFAULT_BENCHMARK
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:16: \
warning: already initialized constant DEFAULT_BULK_THRESHOLD
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:17: \
warning: already initialized constant DEFAULT_VERBOSITY
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:18: \
warning: already initialized constant DEFAULT_UPDATE_SOURCES
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:24: \
warning: already initialized constant OPERATING_SYSTEM_DEFAULTS
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:30: \
warning: already initialized constant PLATFORM_DEFAULTS
/usr/local/lib/ruby/site_ruby/1.9.1/rubygems/config_file.rb:53: \
warning: already initialized constant SYSTEM_WIDE_CONFIG_FILE

Jeremy Kemper from the Rails core team pointed out that this is not a Rails problem, but a RubyGems issue. Ruby 1.9 ships with an outdated RubyGems … like 1.9.1p378 ships with RubyGems 1.3.1. I did update RubyGems to Version 1.3.5 by

sudo gem update --system

but this resulted in some duplicated rubygem files, which cause the error.

So how can the problem be solved? Deleting and reinstalling Ruby 1.9.1 does not have any effect … but the solution is quite simple:

If you already installed Ruby 1.9.1 and Rails 3.0 beta:

1. Be sure that you do NOT install RubyGems 1.3.5 separately after the installation of Ruby 1.9.1 – this would result in a double installation. So have that in mind when following the excellent instructions to installing Ruby, RubyGems, and Rails on Snow Leopard of Dan Benjamin.

2. If you already installed Ruby 1.9.1, updated to RubyGems 1.3.5 and bundler 0.9.4 and also installed Rails 3.0, the only thing you have to do is:

sudo gem uninstall rubygems-update

That’s it. No errors any more!

If you did not install Ruby 1.9.1 and Rails 3.0 yet …

1. You may start with Dan Benjamin’s recipe and modify it so you download, make and install the ruby-1.9.1-p378.tar.gz but NOT the rubygems-1.3.5.tgz.

2. Then update RubyGems with the command

sudo gem update --system

3. Ensure that the rake and the sqlite3-ruby gems are installed, too.

4. Now install the needed gems and rails –pre as described in the Rails 3.0 beta release notes

5. After the successful installation of Rails 3.0 beta, you now have to do the vitally important step:

sudo gem uninstall rubygems-update

6. Finally check, if any gem needs an update before diving into Rails 3.0 by

sudo gem update

Hope this helps … and saves some time. Thx Andy for the hint

Some days ago I published a first solution for reactivating printing on OKI-printers from Mac OS X 10.6 Snow Leopard … some of you managed it to reactivate the printer by following the instructions – others are still coping with that problem. Also I was disappointed to see that the solution broke again and I wasn’t able to print from Snow Leopard again. That was really annoying – so I spent some time again to find a proper solution. Here it is: Version 2 of how to solve the problem … and as always: no guarantee and on your own risk:

Problem: After updating from Mac OS X 10.5 Leopard to OSX 10.6 Snow Leopard the installed printer driver for the OKI-postscript driver does not work anymore. Here it’s an OKI MFP C5540 … but it should also work with other models, like the OKI C5450 or C8800. The printer diver was installed under Leopard and worked quite well. After finishing the update to 10.6 you are able to send a print job to the printer, but an error message shows up in the print queue.

Diagnosis: Two bugs may cause the problem: Some of the OKI-printer drivers just disregard case sensitivity in their path names – this wasn’t a problem in former Mac OS X versions – but it is a problem in Snow Leopard. The other bug – which even leads to a malfunction if the path names are right – is some wrong file permissions. And this causes Snow Leopard to hiccup when you try to print on an OKI-Printer.

Solution: The easiest way to solve the problems and get rid of the bugs is following three major steps:

1. Delete the old OKI printer drivers under the folder “/Library/Printers/” … if there are any.
2. Install a new OKI driver. This will also create the folder “/Library/Printers/OKIDATA”. Then install the specific printer driver for your OKI-printer (especially the PPD file).
3. Repair the file permissions.

You only need the OKI printer drivers and you have to put in some Terminal commands. But let’s do it step by step:

• Log into your Mac as an administrator.
• Step 1: Delete the old OKI files and folders:
• Don’t forget to backup your data before you start!
• Navigate to the following folder in the Finder and delete the folder “OKIDATA” or “Okidata” – if there is any.

  Macintosh HD/Library/Printers/

• Within the folder “PPDs” you may find also some OKI files – at my Mac it was “Oki C5540.ppd” – delete also these files.
• Step 2: Re-installation of the OKI printer driver. The installation program of older printer drivers may cause problems when creating the “OKIDATA” folder: They may name this folder “Okidata” and put in an old OKfilterA-file.
• Therefore you should download and install the printer driver for C5550n-MFP of OKI-USA specifically for Leopard users first. Just click on the “Mac OS X.5″ link on the printer driver page of OKIDATA-USA, download the installer.
• Then start the installer and put in your password. The installation program will create the folder “OKIDATA” as needed.
• If the C5550n MFP is not the OKI printer you have, you have to download install also the specific printer driver for your OKI-printer model. I had to choose the C5540n MFP. The installation will not overwrite the folder OKIDATA and only put’s the missing PPDs into the right folders.
• Step 3: Repair folder & file permissions. Open the program “Terminal” – you’ll find it under “Programs/Utilities”.
• Input the following command into the appearing command-line window and finish it with pressing the return-key:

  sudo chown -R root:admin /Library/Printers/OKIDATA

• Now, you’ll be prompted for your password … so put in your password of the admin account and finish the input by pressing the return key again
• Input a second command into the command-line window and finish it with pressing the return-key:

  sudo chmod 775 /Library/Printers/OKIDATA/Filters/OKfilterA

• A little complicated – but it works. Just exit the Terminal program and restart your Mac. Then you can setup your OKI-printer and select the specific OKI-printer driver manually.

Printer drivers under Mac OS 10.6 Snow Leopard are still sometimes causing trouble. After explaining how to reactivate an OKI-printer – here is the solution for an Kyocera-Mita-printer … and as always: no guarantee and on your own risk:

Problem: After updating from Mac OS X 10.5 Leopard to OSX 10.6 Snow Leopard the installed printer driver for the Kyocera-postscript driver does not work anymore. Here it’s an Kyocera Mita FS-2000D … but it should also work with other models. The printer diver was installed under Leopard and worked quite well. After finishing the update to 10.6 you are able to send a print job to the printer, but an error message shows up in the print queue.

Diagnosis:There are incorrect file permissions under Snow Leopard fort he Kyocera printer driver … and this causes some trouble. BTW a warm thank you to @kappuchino for his diagnosis and solution!

Solution:There is nothing like fixing the bug yourself You can easily fix the problem by one command in the Terminal:

1. Log into your Mac as an administrator.
2. Open the program “Terminal” – you’ll find it under “Programs/Utilities”.
3. Input the following command into the appearing command-line window and finish it with pressing the return-key:

   sudo chown root:wheel /usr/libexec/cups/filter/kyofilter

4. Now, you’ll be prompted for your password … so put in your password of the admin account and finish the input by pressing the return key again
5. That’s it. Just Close the Terminal program. Now printing on the Kyocera printer should be work like a charm.