GNOME Bugzilla – Bug 549963
Flooded with "User timeout caused connection failure"
Last modified: 2021-05-17 16:15:46 UTC
Don't know if I can blame my crappy internet connection or if this used to happen with my previous provider, but I get flooded by that warning dialog after opening postr. Definitively not a useful message at all.
This also happens to me whilst using Postr on Ubuntu 9.10. It used to happen on a different laptop whilst using 9.04 too.
I've had this problem on both Ubuntu 64-bit 9.04 and (currently) 9.10. There isn't anything actually wrong with my connection, but as soon as I add an image and go to add tags, title, etc. the warning message comes up. The couple times I didn't scramble to close the program immediately afterwards my whole system froze up.
I agree the message should be useful and not flood with the same warning dialog.
This is still happening with git master on Ubuntu 10.04
Created attachment 165526 [details] [review] patch This bug is produced due some widgets that couldn't load some information from Flickr, such as tags, groups, etc.. Each widget throws an error dialog. So far, the only thing the patch does is collect all the error messages in a single message dialog. So there isn't flood anymore, however the usability problem still exists, because if there was a connection problem, all the messages say the same. I'm not sure if the user would like to know what went wrong or why, for example, What is best?, say that it couldn't load the groups or there was a connection problem or it couldn't load the groups due the connection problem. On the other hand, there is 6 different widgets loading data from flickr (status bar, groups selector, set combo, license combo, the avatar image and the tag entry) some of them are really dispensable. Also I'm not sure if a dialogue message is the best way to communicate it.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/postr/-/issues/5.