Comment 6 for bug 1602712

I changed this to confirmed since the root cause was determined (user error) but the code could do something a little more intuitive then spit out a huge backtrace. At least we know how to guide people that run into this problem. This is actually the first time I've heard this reported...