Skip to main content
2 of 2
edited tags
Mokubai Mod
  • 94.8k
  • 1
  • 53
  • 78

The "set a bounty" dialog kept disappearing

I posted Can VMware Workstation Player be connected to my "Intel 4th Gen Core Processor Integrated Graphics Controller" card? and, as it got one "sanity check" comment but no other response, started a bounty. (I do not see the question as such to be interesting to discuss here; I gave a link so that moderators have a narrower field to investigate.)

What did happen that's relevant here is that the UI to set a bounty was inadvertently dismissed four or five times before posting; I ended up composing in vim and copying/pasting.

There were two things that might (or might not) be relevant:

First of all, I had a comment open to reply to the previous (sanity check) comment.

Second of all, I was switching screens on a single computer to manually type a copy of the guest OS warning from the hosts computer, and I eventually got all of what I intended:

Running in software rendering mode

Cinnamon is currently running without any video hardware acceleration and, a s a result, you may observe much higher than normal CPU usage.

This could be a problem with your drivers or some other issue. For best experiences, it is recommended that you only use this mode for troubleshooting purposes.

This message required several trips before I had copied the whole phrase, and I may have dragged my feet through more of the UI than someone just composing and writing without consulting external sources. None the less, whatever I did triggered the removal of the dialog quite a few times, and it is noteworthy to me that my partially entered text always vanished, every time.

I have the note and bounty message I intended to post (if I had to do it over again I would mark where the quotation began and ended), so I've got what I need. However, it might be worth investigating that it is apparently easy enough to accidentally dismiss the dialog, and unless there is strong enough reason to do otherwise, make the dialog stateful enough to remember what the user had entered in to it before.