Never mind . . . I rebooted the phone and that solved the issue!
Same here. I didn't see any mention that a re-boot was needed, so Verizon might want to add this to their screen. This was due to a separate Verizon update that came in at the same time as the OS 6.0 update.
I only know because we have several devices and only the last one updated today to OS 6, and also updated by Verizon just after, had this problem.