I see the bug (or similar) mentioned http://www.gamesas.com/topic/1317665-unofficial-buglist/ and http://www.uesp.net/wiki/Skyrim:Season_Unending#Bugs, but I don't see any solution.
My specific situation is as follows:
A while ago, I had started Joining the Stormcloaks and completed its initial quest to prove my worth, but I have not taken the oath from Ulfric. Yet I was still able to convince Ulfric to meet the Greybeards. It appeared as a different topic choice.
I had also started Joining the Legion a while ago and completed its initial quest to prove my worth, but I have not taken the oath from General Tulius either. Yet I am unable to discuss with General Tulius about meeting with the Greybeards. It doesn't even appear as a topic - I can only choose to take the oath or tell him that I need to think about it.
The only difference between the two factions is that before approaching Ulfric about the meeting, I had already discussed having completed his initial proof-of-worth quest and then denied taking the oath, before I had even started the Season Unending quest. However, when I first approached General Tulius to talk about the meeting I realized that I had completed his initial proof-of-worth quest but I had not yet informed him, so there was no conversation choices at all - he simply tells me to talk to Legate Rikke. As soon as I'm near Legate Rikke she initiates conversation with me and advances the quest by telling me to talk to General Tulius, and now I'm in the situation described above where I can only talk to him about the oath, not about meeting the Greybeards.
I'm not going to take the oath of either side, but apparently according to the bug reports it doesn't seem like it would help anyway.
So is there any way for me to get the option to talk to General Tulius about meeting the Greybeards?
Should I use the console to advance the quest? Is there any chance that I can break something important to the quest-line? Any suggestions as to what quest stage I should advance to?
Thanks.

Any ideas on how to properly fix this issue or do I just have to wait until it's patched (hopefully sometime in Jan.)?