Bug 205007 - konqueror should not start loading pages before network is up on startup
Summary: konqueror should not start loading pages before network is up on startup
Status: CONFIRMED
Alias: None
Product: konqueror
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.3.0
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-24 21:43 UTC by m.wege
Modified: 2022-12-13 08:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2009-08-24 21:43:50 UTC 
Version:            (using KDE 4.3.0)
Installed from:    Ubuntu Packages

According to the maintainer of networkmanager it is not possible to let network manager start before applications are restored. This means quite often that a konqueror session is restored, before the network is up. Konqueror of course can not then load pages and presents error pages instead. So Konqueror should first test if network is up, before restoring session.
See also: https://bugs.kde.org/show_bug.cgi?id=204365
Comment 1 Andrew Crouthamel 2018-11-02 23:05:31 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 05:37:12 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-13 02:53:36 UTC 
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!