After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 646290 - integrate with network manager to show a better loading error page
integrate with network manager to show a better loading error page
Status: RESOLVED OBSOLETE
Product: epiphany
Classification: Core
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on: 620932
Blocks:
 
 
Reported: 2011-03-31 00:48 UTC by William Jon McCann
Modified: 2018-03-30 16:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
current error page (42.86 KB, image/png)
2012-12-08 18:08 UTC, William Jon McCann
Details
mockup (23.99 KB, image/png)
2012-12-08 19:01 UTC, William Jon McCann
Details

Description William Jon McCann 2011-03-31 00:48:17 UTC
It would be really great if the page loading error screen was integrated with NetworkManager.  NetworkManager 0.9 has a new feature to be able to differentiate just connected to the gateway from actually connected to the internet.

If we are unable to connect we could provide an option to troubleshoot as well.
Comment 1 Matthias Clasen 2011-10-07 19:37:38 UTC
We'll likely have a nice and simple api for this in GIO in 2.32, see bug 620932
Comment 2 William Jon McCann 2012-12-08 18:08:34 UTC
Created attachment 231041 [details]
current error page
Comment 3 William Jon McCann 2012-12-08 19:01:21 UTC
Created attachment 231042 [details]
mockup

Perhaps something like this.

Clicking the link would open the Network Settings. If the network is reconnected out of band then the page should reload automatically (if the app is in the foreground).

Jimmac, what do you think?
Comment 4 Jakub Steiner 2012-12-10 19:06:36 UTC
Looks appropriate to me.
Comment 5 Michael Catanzaro 2018-03-25 17:48:21 UTC
This is a mass NEEDINFO of all Epiphany bugs with no activity in the past three years. I'm going to be automatically closing old bugs to help us focus on current problems. If you feel this bug is still relevant with Epiphany 3.26 or newer, then please leave any comment here so that I know not to close this one.
Comment 6 Michael Catanzaro 2018-03-30 16:27:45 UTC
This is a mass-close of old bugs currently in the NEEDINFO state.

If you think this bug is still relevant, please leave a comment.