Wait a little bit before firing off a window
Bug #1487896 reported by
Danielle Foré
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Captive Portal Assistant |
Fix Released
|
Medium
|
The Lemon Man |
Bug Description
Sometimes it seems like capnet checks for connectivity too early. It gets the signal it should check before the connection is fully established. We should make sure to wait just a little bit to avoid this.
Related branches
lp:~lemonboy/capnet-assist/bettercheck
- elementary Apps team: Pending requested
-
Diff: 11 lines (+1/-1)1 file modifiedsrc/CaptiveLogin.vala (+1/-1)
Changed in capnet-assist: | |
milestone: | none → loki-beta1 |
Changed in capnet-assist: | |
importance: | Undecided → Medium |
Changed in capnet-assist: | |
status: | Confirmed → In Progress |
assignee: | nobody → The Lemon Man (lemonboy) |
Changed in capnet-assist: | |
status: | In Progress → Fix Committed |
milestone: | loki-beta1 → loki-alpha1 |
Changed in capnet-assist: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Can confirm.
I noticed this issue after I installed google-chrome. But I don't think that has anything to do with it.
Most every time I boot into EoS, an instance of sensible-browser will attempt to open start.elementar yos.org, and I will simply get a 404. I have a wireless PCI-e wireless card installed, as well the onboard ethernet connection on the Mobo. I have a physical cable installed, and I'm also connected to the wireless network at the same time. (Same network most of the time... but I use the wireless card when I don't have an ethernet cable available)
$ lspci | grep -i net
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
04:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
$ # Running process yos.org 2>/dev/null yos.org 2>/dev/null
< root 1726 0.0 0.0 63776 3328 ? S 20:18 0:00 su [username] -s /bin/sh -c captive-login 2>/dev/null || sensible-browser start.elementar
< [username] 1727 0.0 0.0 4448 760 ? Ss 20:18 0:00 sh -c captive-login 2>/dev/null || sensible-browser start.elementar
< [username] 1728 0.9 0.6 2508212 105140 ? Sl 20:18 0:01 captive-login
Here's the syslog entry
$ grep CapNetAssist /var/log/syslog
Sep 3 20:18:38 [hostname] CapNetAssist: DetectCaptivePortal script triggered
Sep 3 20:18:38 [hostname] CapNetAssist: Display set
Sep 3 20:18:38 [hostname] CapNetAssist: Running browser as '[username]' to login in captive portal
Sep 3 20:18:39 [hostname] CapNetAssist: DetectCaptivePortal script triggered
Sep 3 20:18:39 [hostname] CapNetAssist: Display set
Sep 3 20:18:39 [hostname] CapNetAssist: Running browser as '[username]' to login in captive portal