Chromium starts up and opens my pinned tabs: Gmail, Gcalendar & Greader before gnome panel appears... Also network manager sometimes is slow to bring up WiFi even though my home network is set up to be used by all users, resulting in failed to load in chromium.
Achieving full disk encryption using FIPS, TCG OPAL and LUKS to encrypt UEFI ESP on bare-metal and in VMs Many security standards such as CIS and STIG require to protect information at rest. For example, NIST SP 800-53r5 SC-28 advocate to use cryptographic protection, offline storage and TPMs to enhance protection of information confidentiality and/or integrity. Traditionally to satisfy such controls on portable devices such as laptops one would utilize software based Full Disk Encryption - Mac OS X FileVault , Windows Bitlocker , Linux cryptsetup LUKS2 . In cases when FIPS cryptography is required, additional burden would be placed onto these systems to operate their kernels in FIPS mode. Trusted Computing Group works on establishing many industry standards and specifications, which are widely adopted to improve safety and security of computing whilst keeping it easy to use. One of their most famous specifications them is TCG TPM 2.0 (Trusted Platform Module). TPMs are now...
Browsers shouldn't announce that the page failed to load, they should say "Waiting for internet connection" or something. I hate how I have to go through all my tabs and hit F5 every time chrome loads starts faster than networkmanager gets on my wifi (100% of the time, Intel X-25M SSD).
ReplyDeleteWhat should the browser do if the network is really down? I don't think the bug is in the browser. I think the bug is in the system starting Apps before the system is up. I hate the same kind of behavior in windows. It's basic sequencing. Start network, then network apps.
ReplyDeleteThe network ought to start before the user's apps, since you don't know which ones will need the network. You wouldn't start running user apps before you've mounted everything in the fstab. You don't want every app to write it's own logic to guess if the system is still coming up or if the system is just broken. I've had to write software like that with timeout loops and multiple strategies for determining if it needs to wait a little more or if it needs to give up. Once you give up on the last failure you have to guess what kind of message to give the user to explain the error. The user experience is catastrophic in failure cases.
It sounds to me like Gnome needs to better organize startup dependencies.
I agree with Edward. If you have apps that needs a network connection, they should start up after the PC sees the network. Gnome should have enough smarts to realise what apps require the network, eg browsers, web apps, ultilities etc. Is that possible?
ReplyDeleteI came across the problem with CheckGmail on startup. CheckGmail would fail because wifi hadn't started yet, so not knowing anything about scripts I had to search the internet for someone who had written a simple time delay script. That's all it needed. The year is 2010, and this simple feature should of been designed in long ago.
This comment has been removed by a blog administrator.
ReplyDeleteThe point about desktop is to bring up web-browser as soon as possible in working state. In 15 seconds I can read an email and start replying. I wonder if upstart can be used to trigger web-browser as soon as network is up?
ReplyDeleteThe way I read it, systemd will also be for this.
ReplyDelete1. If you were to set your network credentials as system-wide, you would probably have network by the time you log in.
ReplyDelete2. gnome-session has no idea if an application needs the network when it starts it up, so you would have to have every application author update their .desktop files to flag requirements. Not pretty. Then wait for network to start applications that want 'network'. But what if you connect to a non-routable network? Or what if you have no network, but your application supports offline mode (think tomboy or gtg, both can 'sync' with the network, but that is not required).
3. NM already emits a dbus signal on connect. The correct method would be to update applications to listen for that signal and re-run their failed network-related functions when it is received (whether it be fetching a web page, syncing notes, etc). Fixing the issue in Chromium would solve network related issues at times that are not startup, as well.
I agree with Sequentious. That sounds like the right way to do it. I have Evolution start on system start up and it works almost exactly this way (it actually attempts a connection before it realises there is none and switches to offline mode). When NM connects, Evolution also connects and gets mail. Very neat.
ReplyDelete