Status Update
Comments
al...@gmail.com <al...@gmail.com> #2
Chrome Diagnostics Report of following results:
The DNS diagnostic test in Chrome Diagnostics Report is known to have some issues in some configuration. Internal bug id is
Here the diagnostic failure could indicate a real problem. Jason, Jie, what m126 bugs could this report be a duplicate of ?
ce...@gmail.com <ce...@gmail.com> #3
what m126 bugs could this report be a duplicate of ?
Not anything off the top of my head now (maybe Jason knows other). Since the device is not enterprise-enrolled according to the information in #1, I assume it should not hit the diagnostic DNS issue in
But I assume the reporter also encountered the issue of "no connection to gateway" in the diagnostic app, which is partially fixed on M128 in
Re #1,
Thanks for reporting the issue and sorry for the late reply here. A few questions to help us understanding the issue bettter:
- Are you still experiencing this issue? If so, could you file a feedback report (alt-shift-i, and put "
" in the textbox so that we can search for it easily) when you are seeing it again?b/360530624 - Does it only happen on a certain WiFi network? If it's the case, do you by chance have other devices (not Chromebook) to see if they work on the same network?
Thanks!
da...@gmail.com <da...@gmail.com> #4
This might be a dup of the internal bug of
As Jie mentioned, if this is still reproducible, a feedback report would help debug the issue further. Thank you!
an...@gmail.com <an...@gmail.com> #5
ju...@gmail.com <ju...@gmail.com> #6
Bugjuggler: wait 8w -> hugobenichi
af...@gmail.com <af...@gmail.com> #7
sh...@gmail.com <sh...@gmail.com> #8
It is still happening, so I will report the next instance with the requested text. It doesn't happen on a specific network, but all networks I am connecting to. It's not repeatable on other non ChromeOS devices in at least two of those, but is repeatable on the exact same device of another owner. I can ask them to also report with the reference number if that is helpful. Let me know if I can provide any additional information or troubleshooting.
I am out of the office for a few days this weekend, but should be able to repeat issue by eod Monday.
tc...@dogtowndev.com <tc...@dogtowndev.com> #9
be...@gmail.com <be...@gmail.com> #10
I looked at 2 reports, in both case we see that the WiFi network service state is eventually changed to "failure".
Rerouting to WiFi component to take an initial look if this is a WiFi issue.
ph...@gmail.com <ph...@gmail.com> #12
The client device disconnected from wifi_psk_6 due to "no remaining endpoints", and disconnected from wifi_psk_8 due to reconnect timeout. The connection to wifi_psk_36 was unstable, link monitor failure occurred and PREV_AUTH_NOT_VALID
error observed during reconnection.
da...@gmail.com <da...@gmail.com> #13
<tirage> Kevin to take a look, figure out if it is L2 or L3 issue.
ma...@gmail.com <ma...@gmail.com> #14
There are no issues seen on the firewall or with any other models of Chromebook at this same time. I also notice that instead of do53 query to DNS 9.9.9.9 its says Do53 query to (IPv4: 1) and (IPv4: 2) and fails.
Hope this is maybe related. Otherwise I can file my own report.
ka...@gmail.com <ka...@gmail.com> #15
mo...@brakestad.com <mo...@brakestad.com> #16
re...@gmail.com <re...@gmail.com> #17
I do not believe that this is an L2 layer issue. Indeed we see the Wi-Fi state reach "Failure" in all three feedback reports, but I believe that all three are explained by intended behavior. In
In the other two reports, we see a pattern where the device suspends, resumes, then fails to reconnect to the AP is was connected to prior to the resume. This could be explained by the user closing their device, traveling out of range of their AP, then re-opening their device. (
So, I believe the Wi-Fi failures are reflective of expected device behavior in response to user activity. I do believe there is some indication of L3 layer issues though. For example in
Handing this back to the networking team to take a look.
pa...@gmail.com <pa...@gmail.com> #18
I do believe there is some indication of L3 layer issues though. For example in
http://listnr/product/208/report/92051793504 where we see repeated dnsproxyd errors while we are in the "online" state.
As discussed many times internally, dns failures happen both because of link issues and L3 issues and therefore dns failures can't be used to rule out link issues. Actually dns health checks and dns queries are the first thing expected to fail when the link fails as a packet transport.
so...@caslco.com <so...@caslco.com> #19
hs...@gmail.com <hs...@gmail.com> #20
Thanks all for the investigation and #19 for providing more information.
I took a quick pass at the 3 reports in #11, the DNS failures always came together with the NUD_FAILED
logs, which means that the gateway was not reachable on L2. This usually means something went wrong on the network side (i.e., due to some reason the device did not get the ARP responses), but the weird thing is that, if I read the logs correctly, these 3 feedback reports are from 3 different networks, and the NUD_FAILED
is shown on all the 3 networks...
Questions to the user:
- Were you using the device at the same physical location to connect to these networks? (just want to rule out some random effect from the physical environment...)
- If it's possible, could you try connecting the device to the same router(s) with Ethernet cable to see if it works? (this could help us understand if the issue is at the network layer or the wifi layer).
Questions to the wifi team:
- In this case, will it be helpful to do some OTA packet capture?
Thanks!
kn...@gmail.com <kn...@gmail.com> #21
Thanks for all of y'all's help!
jn...@gmail.com <jn...@gmail.com> #22
Re #21,
Do you want me to submit feedback reports while I am connected? Or only if the issue arises?
Only if the issue arises is fine. Thanks!
Re #14 and #15,
Sorry for the late reply -- I checked the two logs and they showed the same pattern -- there were a lot of NUD_FAILED
in the logs. Not sure if the root cause is the same with #1 . Would you mind also filing a feedback report (alt-shift-i, and put "
kn...@gmail.com <kn...@gmail.com> #23
remotely through the admin console when I notice the behaviour through our
Meraki wifi system. It has these couple options I can select when
collecting logs. Can I do it this way? or another way remotely. Hopefully
this picture comes through.
[image: image.png]
On Tue, Nov 5, 2024 at 8:43 PM <buganizer-system@google.com> wrote:
--
Erik Jeffery
Brown Deer School District
--
Confidentiality Notice: This e-mail message, including any
attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies
of
the original message.
de...@gmail.com <de...@gmail.com> #24
Would you like me to only gather logs on devices already updated to 130 that have this issue or do you want logs from 129 devices as well?
ja...@gmail.com <ja...@gmail.com> #25
I think this issue seems to be mostly taken care of with 130, but still seems to occur sporadically.
All of our clients are remote, so the best I can do is collect system logs through the admin console.
Here is a netlog.txt from a OS130 client that has this issue occur at 2024-11-12R13:44:49. Also, you can see this issue occurring for a much longer duration at timestamp - 2024-11-1120:37:50 There is no indication on the firewall that this client had any issues through us.
I have the entire support bundle if uploading that would provide more information.
Please let me know what I can do to help.
bi...@gmail.com <bi...@gmail.com> #26
Re #23 ~ #25:
Thanks for the additional information (and sorry for the late reply).
Hopefully this picture comes through.
Unfortunately we can only see a [image: image.png]
:)
I'll defer to Kevin to check if there are any other logs we can collect for better debugging. (Logs in #25 still shows the NUD_FAILED issue)
gl...@gmail.com <gl...@gmail.com> #27
The computer was restarted at around 18:47 and you can see it connect right away.
Also, if you would rather have me create my own issue I can.
so...@gmail.com <so...@gmail.com> #28
I am going to upload one more netlog. This user is on Chrome OS 130 and is experiencing the issue multiple times of the day in multiple classrooms. It can be seen at timestamp 2024-11-18T17:40:58.026051Z
I have a log packet from the computer - Google Admin Console if needed/
Thanks
gr...@gmail.com <gr...@gmail.com> #29
Thank you for all of the logs, this is very helpful in working towards a diagnosis. Here's what I've got so far:
We see a repeated pattern of failed authentication attempts in all of your recent log submissions. We attempt to authenticate, and a couple seconds later the attempt times out, seemingly without any response from the AP:
2024-11-12T18:43:53.297881Z DEBUG wpa_supplicant[784]: nl80211: Authentication request send successfully
2024-11-12T18:43:53.298209Z DEBUG wpa_supplicant[784]: nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
2024-11-12T18:43:53.298233Z DEBUG wpa_supplicant[784]: nl80211: New station ea:9e:38:7f:e0:10
2024-11-12T18:43:53.311360Z INFO shill[1162]: INFO shill: [wifi.cc(2659)] WiFi wlan0 StateChanged inactive -> authenticating
2024-11-12T18:43:53.333510Z INFO patchpaneld[1974]: INFO patchpaneld: [shill_client.cc(262)] Service /service/1 was not connected
2024-11-12T18:43:53.338577Z INFO patchpaneld[1974]: INFO patchpaneld: [shill_client.cc(262)] Service /service/1 was not connected
2024-11-12T18:43:56.017781Z DEBUG wpa_supplicant[784]: nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
2024-11-12T18:43:56.017823Z DEBUG wpa_supplicant[784]: nl80211: Delete station ea:9e:38:7f:e0:10
2024-11-12T18:43:58.299255Z DEBUG wpa_supplicant[784]: wlan0: SME: Authentication timeout
One possibility is that the auth request was malformed in some way such that the AP didn't recognize it. Perhaps the device tried do authenticate using an unsupported method. Looking at the authentication request details, nothing stands out as erroneous. Another possibility is that the AP did send an authentication response, but that was somehow ignored by the device.
2024-11-19T14:02:00.401322Z DEBUG wpa_supplicant[800]: wlan0: Starting radio work 'sme-connect'@0x580617abf0 after 0.040791 second wait
2024-11-19T14:02:00.401402Z DEBUG wpa_supplicant[800]: wlan0: WPA: clearing own WPA/RSN IE
2024-11-19T14:02:00.401423Z DEBUG wpa_supplicant[800]: wlan0: RSN: clearing own RSNXE
2024-11-19T14:02:00.401481Z DEBUG wpa_supplicant[800]: wlan0: Automatic auth_alg selection: 0x1
2024-11-19T14:02:00.401510Z DEBUG wpa_supplicant[800]: wlan0: SAE enabled, but target BSS does not advertise SAE AKM for RSN
2024-11-19T14:02:00.401533Z DEBUG wpa_supplicant[800]: RSN: PMKSA cache search - network_ctx=0x5806180fb0 try_opportunistic=0 akmp=0x0
2024-11-19T14:02:00.401548Z DEBUG wpa_supplicant[800]: RSN: Search for BSSID (MAC OUI=ea:9e:38 IFACE=8)
2024-11-19T14:02:00.401563Z DEBUG wpa_supplicant[800]: RSN: No PMKSA cache entry found
2024-11-19T14:02:00.401583Z DEBUG wpa_supplicant[800]: wlan0: RSN: using IEEE 802.11i/D9.0
2024-11-19T14:02:00.401604Z DEBUG wpa_supplicant[800]: wlan0: WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2 proto 2
2024-11-19T14:02:00.401622Z DEBUG wpa_supplicant[800]: wlan0: WPA: Selected mgmt group cipher 32
2024-11-19T14:02:00.401642Z DEBUG wpa_supplicant[800]: wlan0: WPA: clearing AP WPA IE
2024-11-19T14:02:00.401670Z DEBUG wpa_supplicant[800]: WPA: set AP RSN IE - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 00 00
2024-11-19T14:02:00.401687Z DEBUG wpa_supplicant[800]: wlan0: WPA: clearing AP RSNXE
2024-11-19T14:02:00.401707Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP group 0x10 network profile group 0x358 driver supported ciphers 0x381e; available group 0x10
2024-11-19T14:02:00.401726Z DEBUG wpa_supplicant[800]: wlan0: WPA: using GTK CCMP
2024-11-19T14:02:00.401747Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP pairwise 0x10 network profile pairwise 0x358 driver supported ciphers 0x381e; available pairwise 0x10
2024-11-19T14:02:00.401766Z DEBUG wpa_supplicant[800]: wlan0: WPA: using PTK CCMP
2024-11-19T14:02:00.401786Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP key_mgmt 0x2 network profile key_mgmt 0xc000d42; available key_mgmt 0x2
2024-11-19T14:02:00.401804Z DEBUG wpa_supplicant[800]: wlan0: WPA: using KEY_MGMT WPA-PSK
2024-11-19T14:02:00.401825Z DEBUG wpa_supplicant[800]: wlan0: WPA: AP mgmt_group_cipher 0x20 network profile mgmt_group_cipher 0x0; available mgmt_group_cipher 0x0
2024-11-19T14:02:00.401844Z DEBUG wpa_supplicant[800]: wlan0: WPA: not using MGMT group cipher
2024-11-19T14:02:00.401874Z DEBUG wpa_supplicant[800]: WPA: Set own WPA IE default - hexdump(len=22): 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ac 02 8c 00
2024-11-19T14:02:00.401889Z DEBUG wpa_supplicant[800]: RSN: Set own RSNXE default - hexdump(len=0):
2024-11-19T14:02:00.401903Z DEBUG wpa_supplicant[800]: WPA: Set PMK based on external data - hexdump(len=32): [REMOVED]
2024-11-19T14:02:00.401951Z DEBUG wpa_supplicant[800]: RRM: Determining whether RRM can be used - device support: 0x30
2024-11-19T14:02:00.401966Z DEBUG wpa_supplicant[800]: RRM: Adding RRM IE to Association Request
2024-11-19T14:02:00.402027Z DEBUG wpa_supplicant[800]: Added supported operating classes IE - hexdump(len=24): 3b 16 79 51 53 54 73 74 75 76 77 78 79 7a 7b 7c 7d 7e 7f 80 81 00 82 80
2024-11-19T14:02:00.402050Z DEBUG wpa_supplicant[800]: EAPOL: External notification - EAP success=0
2024-11-19T14:02:00.402070Z DEBUG wpa_supplicant[800]: EAPOL: External notification - EAP fail=0
2024-11-19T14:02:00.402084Z DEBUG wpa_supplicant[800]: EAPOL: External notification - portControl=Auto
2024-11-19T14:02:00.402101Z DEBUG wpa_supplicant[800]: wlan0: Cancelling scan request
2024-11-19T14:02:00.402170Z NOTICE wpa_supplicant[800]: SME: Trying to authenticate with (MAC OUI=ea:9e:38 IFACE=8) (SSID='(SSID: 1)' freq=5680 MHz)
2024-11-19T14:02:00.402194Z DEBUG wpa_supplicant[800]: EAPOL: External notification - portValid=0
2024-11-19T14:02:00.402213Z DEBUG wpa_supplicant[800]: wlan0: State: SCANNING -> AUTHENTICATING
2024-11-19T14:02:00.402253Z DEBUG wpa_supplicant[800]: wlan0: Determining shared radio frequencies (max len 2)
2024-11-19T14:02:00.402276Z DEBUG wpa_supplicant[800]: wlan0: Shared frequencies (len=0): completed iteration
2024-11-19T14:02:00.402301Z DEBUG wpa_supplicant[800]: P2P: Add operating class 81
2024-11-19T14:02:00.402321Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=11): 01 02 03 04 05 06 07 08 09 0a 0b
2024-11-19T14:02:00.402335Z DEBUG wpa_supplicant[800]: P2P: Add operating class 115
2024-11-19T14:02:00.402350Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=4): 24 28 2c 30
2024-11-19T14:02:00.402363Z DEBUG wpa_supplicant[800]: P2P: Add operating class 116
2024-11-19T14:02:00.402378Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 24 2c
2024-11-19T14:02:00.402391Z DEBUG wpa_supplicant[800]: P2P: Add operating class 117
2024-11-19T14:02:00.402405Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 28 30
2024-11-19T14:02:00.402420Z DEBUG wpa_supplicant[800]: P2P: Add operating class 124
2024-11-19T14:02:00.402457Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=4): 95 99 9d a1
2024-11-19T14:02:00.402471Z DEBUG wpa_supplicant[800]: P2P: Add operating class 125
2024-11-19T14:02:00.402488Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=5): 95 99 9d a1 a5
2024-11-19T14:02:00.402502Z DEBUG wpa_supplicant[800]: P2P: Add operating class 126
2024-11-19T14:02:00.402516Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 95 9d
2024-11-19T14:02:00.402529Z DEBUG wpa_supplicant[800]: P2P: Add operating class 127
2024-11-19T14:02:00.402544Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=2): 99 a1
2024-11-19T14:02:00.402558Z DEBUG wpa_supplicant[800]: P2P: Add operating class 128
2024-11-19T14:02:00.402584Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=8): 24 28 2c 30 95 99 9d a1
2024-11-19T14:02:00.402611Z DEBUG wpa_supplicant[800]: P2P: Add operating class 130
2024-11-19T14:02:00.402632Z DEBUG wpa_supplicant[800]: P2P: Channels - hexdump(len=9): 24 28 2c 30 95 99 9d a1 a5
2024-11-19T14:02:00.402649Z DEBUG wpa_supplicant[800]: P2P: Update channel list
2024-11-19T14:02:00.402697Z DEBUG wpa_supplicant[800]: P2P: channels: 81:1,2,3,4,5,6,7,8,9,10,11 115:36,40,44,48 116:36,44 117:40,48 124:149,153,157,161 125:149,153,157,161,165 126:149,157 127:153,161 128:36,40,44,48,149,153,157,161 130:36,40,44,48,149,153,157,161,165
2024-11-19T14:02:00.402716Z DEBUG wpa_supplicant[800]: P2P: cli_channels:
2024-11-19T14:02:00.402749Z DEBUG wpa_supplicant[800]: nl80211: Authenticate (ifindex=2)
2024-11-19T14:02:00.402844Z DEBUG wpa_supplicant[800]: * bssid=(MAC OUI=ea:9e:38 IFACE=8)
2024-11-19T14:02:00.402859Z DEBUG wpa_supplicant[800]: * freq=5680
2024-11-19T14:02:00.402900Z DEBUG wpa_supplicant[800]: * SSID=649433bbcd6b
2024-11-19T14:02:00.402914Z DEBUG wpa_supplicant[800]: * IEs - hexdump(len=0): [NULL]
2024-11-19T14:02:00.402927Z DEBUG wpa_supplicant[800]: * Auth Type 0
Another possibility is that the AP did send an authentication response, but that was somehow ignored by the device. Unfortunately, none of these possibilities are observable in the limited logs that we have. Really, we're going to need additional information to actually make a diagnosis, since there isn't anything conclusive in the device logs.
ejeffery, if you're able to provide some additional diagnostics, it could go a long way to helping understand the behavior. Here are some things that would help me debug, listed in order of usefulness. I understand that you might not be able to complete some or all of these steps, but anything you can provide could be useful.
-
An OTA packet capture on the AP's operating frequency, showing a reproduction of the event. This is definitely an advanced step that requires additional hardware so no worries if this isn't viable, but it's certainly the most useful option.
-
Logs from the AP that you're trying to connect to. This could potentially inform me of misalignment between the Chromebook and AP.
-
A full feedback report from the Chromebook, gathered using Alt-Shift-I immediately after a failure. Feedback reports contain additional logs and information that isn't available in the net logs.
If you're able to complete items 1 or 2, it would still be really helpful if you could provide an accompanying feedback report that lines up with the packet capture or AP logs.
Let me know if you're able to provide any of this additional information. Thanks again for working with us to help diagnose this issue.
Best, Kevin
he...@gmail.com <he...@gmail.com> #30
1. I can try to do this. It would be like a monitor mode capture? I can try but most of the time it isn't necessarily happening when I am around. I just hear about it later with the time stamps.
2. One of the problems here is that we use Meraki APs. Don't have a lot in logging capabilities. I can attach some screenshots of dashboards here if you want.
3. Is there any specific logs you need. I usually do not get to see the user in person and must rely on log gathering from the admin console, but I can get a support bundle from there and upload any logs you may need if you want. That is where I got the netlog.txt from.
Thanks very much for helping me with this.
la...@gmail.com <la...@gmail.com> #31
Does this help at all?
al...@gmail.com <al...@gmail.com> #32
la...@gmail.com <la...@gmail.com> #33
vl...@gmail.com <vl...@gmail.com> #34
dd...@gmail.com <dd...@gmail.com> #35
ca...@gmail.com <ca...@gmail.com> #36
cr...@gmail.com <cr...@gmail.com> #37
re...@tothepenny.biz <re...@tothepenny.biz> #38
th...@gmail.com <th...@gmail.com> #39
jn...@gmail.com <jn...@gmail.com> #40
se...@gmail.com <se...@gmail.com> #41
pu...@gmail.com <pu...@gmail.com> #42
ct...@gmail.com <ct...@gmail.com> #43
ls...@gmail.com <ls...@gmail.com> #44
pr...@tcsne.org <pr...@tcsne.org> #45
ka...@gmail.com <ka...@gmail.com> #46
hy...@gmail.com <hy...@gmail.com> #47
ys...@gmail.com <ys...@gmail.com> #48
yi...@gmail.com <yi...@gmail.com> #49
la...@gmail.com <la...@gmail.com> #50
ma...@briody.net <ma...@briody.net> #51
te...@googlemail.com <te...@googlemail.com> #52
sl...@gmail.com <sl...@gmail.com> #53
rd...@gmail.com <rd...@gmail.com> #54
gg...@gmail.com <gg...@gmail.com> #55
Also keep finalized tasks in the task list until I remove them manually.
je...@gmail.com <je...@gmail.com> #56
Also, keep completed tasks in the list until removed manually.
Also, please allow full screen view of tasks (like Google Tasks Canvas allows)
Also, add functionality for repeating tasks daily, weekly, monthly, or yearly.
ca...@gmail.com <ca...@gmail.com> #57
Also, please add these other functionalities for tasks.
1. Reoccurring tasks monthy, yearly etc.
2. Alarm and reminder feature.
3. Able to view all tasks for the day so that we no longer need to switch from one category to the other
th...@gmail.com <th...@gmail.com> #58
si...@gmail.com <si...@gmail.com> #59
Thank you!
ja...@gmail.com <ja...@gmail.com> #60
jf...@gmail.com <jf...@gmail.com> #61
dm...@juno.com <dm...@juno.com> #62
mi...@gmail.com <mi...@gmail.com> #63
si...@gmail.com <si...@gmail.com> #64
si...@gmail.com <si...@gmail.com> #65
mc...@geek.net.ru <mc...@geek.net.ru> #66
vo...@gmail.com <vo...@gmail.com> #67
nothing like Google canvas, please pretty please don't turn it off :((((
you will break my tiny little heart..
On Thu, Feb 28, 2019, 16:56 <buganizer-system@google.com> wrote:
vh...@gmail.com <vh...@gmail.com> #68
th...@gmail.com <th...@gmail.com> #69
jo...@gmail.com <jo...@gmail.com> #70
Please work something out, gtasks is a small part of how I generate profit and you do as well.
Even your product, Google Tasks, can't compete or ....... have I just discovered something .....
hi...@gmail.com <hi...@gmail.com> #71
pe...@gmail.com <pe...@gmail.com> #72
vo...@gmail.com <vo...@gmail.com> #73
ka...@gmail.com <ka...@gmail.com> #74
"There is no actual substitute for Tasks Canvas for its simplicity, ease of use and product/market fit....I would not really shut it down just to teach newcomer product managers on how to make great products people really use and love."
Please continue to support the Tasks Canvas view. Thank you.
ho...@gmail.com <ho...@gmail.com> #75
li...@gmail.com <li...@gmail.com> #76
no...@gmail.com <no...@gmail.com> #77
Even simple shopping task lists like e.g.
Shopping
- Shop 1
-- Item 1
-- Item 2
-- Item 3
- Shop 2
-- Item 1
-- Item 2
already require two sub levels.
Without a certain number of sub levels, Google tasks is not really usable anymore.
Please keep the possibility to add sub levels!
ap...@gmail.com <ap...@gmail.com> #78
ol...@gmail.com <ol...@gmail.com> #79
Here are the actions I take:
1.
i. On the web: I use Gtaskd as an alternative interface to canvas:
ii.On android: Keep using Gtasks App:
2.DON'T Press the [Update List] button on the New Google Tasks. It will ruin all your subtasks hierarchy.
3.Backup all my current tasks as a CSV using:
bo...@gmail.com <bo...@gmail.com> #80
be...@bhague.com <be...@bhague.com> #81
na...@makhijani.org <na...@makhijani.org> #82
di...@gmail.com <di...@gmail.com> #83
gm...@gmail.com <gm...@gmail.com> #84
pb...@gmail.com <pb...@gmail.com> #85
Google, please re-insert the Print and Canvas features and find a solution to this issue.
My task list with a lot of important tasks is now more or less impossible to use.
/Patrik :-(
jo...@gmail.com <jo...@gmail.com> #86
sa...@gmail.com <sa...@gmail.com> #87
ma...@gmail.com <ma...@gmail.com> #88
ma...@gmail.com <ma...@gmail.com> #89
Why remove it when its upkeep must be a minute drop in your your massive ocean of cash?
pa...@gmail.com <pa...@gmail.com> #90
s....@alumni.ethz.ch <s....@alumni.ethz.ch> #91
ke...@gtaskd.com <ke...@gtaskd.com> #92
The new UIs launched by Google in 2018 work just fine without this change to the API. Aside from building the API in 2011, Google didn't make any in-house changes to Google Tasks until 2018, even after saying it was on their list in 2011:
The API allowed other developers to keep your product relevant in the era of smartphone with apps like the excellent GTasks for Android:
Canvas is gone, and I understand that your vision for Google Tasks if far different from mine, but there's no reason to break the API with this change when your new UIs already work with it.
Kevin
an...@schegg.org <an...@schegg.org> #93
gr...@gmail.com <gr...@gmail.com> #94
al...@gmail.com <al...@gmail.com> #95
rd...@gmail.com <rd...@gmail.com> #96
convert my stuff over or it will lose all meaning condensed to only two
task levels. Also, Gtasks will no longer synchronize, so I can't use that
iOS app any more, or the desktop version. After looking at about 10 other
programs I am switching to Quire. It supports infinite task levels and has
a lot of nice features. The migration is not too too bad either. Use the
backup function at
boxes for completed tasks, hidden tasks, etc., cuz they will clog up your
new lists in Quire. Export as a spaced text file. Then just open the file,
select the text for each project/task group (use ctrl click then shift
click to select), copy, and go to Quire. In Quire, you create a new project
(eg House Projects) to match your old one, add one task, then right click
the task, select More, then Paste. Do that for each project (I have about
20!) and you're done. Be careful when selecting text that you get all of
the spaces before the first task, or else it will become the parent and
everything else will be a subtask! They explain more about migration
here:
There are a few simple things to learn when you get started, such as
Ctl-arrow to collapse or expand each list, but it looks pretty good so far.
On Fri, Apr 5, 2019 at 4:35 AM <buganizer-system@google.com> wrote:
re...@gmail.com <re...@gmail.com> #97
ks...@gmail.com <ks...@gmail.com> #98
ga...@gmail.com <ga...@gmail.com> #99
et...@gmail.com <et...@gmail.com> #100
in...@gmail.com <in...@gmail.com> #101
[Deleted User] <[Deleted User]> #102
Thanks
ma...@gmail.com <ma...@gmail.com> #103
ni...@bubblevision.com <ni...@bubblevision.com> #104
th...@gmail.com <th...@gmail.com> #105
Also a Stylus (who still uses Stylish?) style here to make it look more like Canvas...
ko...@gmail.com <ko...@gmail.com> #106
an...@gmail.com <an...@gmail.com> #107
an...@gmail.com <an...@gmail.com> #108
tu...@gmail.com <tu...@gmail.com> #109
ek...@google.com <ek...@google.com> #110
th...@gmail.com <th...@gmail.com> #111
se...@gmail.com <se...@gmail.com> #112
se...@gmail.com <se...@gmail.com> #113
ek...@google.com <ek...@google.com> #114
Fundamentally this API is built to allow applications to integrate with Google Tasks. If Google Tasks no longer supports multiple levels of tasks then I think it's reasonable for the API to reflect that change. If your application doesn't care if a user can't access their tasks in the Google Tasks UI then it's probably better to implement your own backend for storing tasks instead of reusing the Tasks API for that purpose.
se...@gmail.com <se...@gmail.com> #115
By the way, in my option the best solution would be to keep the support of multiple level of sub tasks in both, the Task UI and the API cause I thing that there are a lot of people that like this feature and it is very hard to understand why you want to remove it at all.
ek...@google.com <ek...@google.com> #116
It's completely valid to have an opinion on whether or not the removal of multiple levels of tasks was good for the product, but as mentioned earlier that's outside the scope of this issue tracker.
vo...@gmail.com <vo...@gmail.com> #117
used by many people, required no updating (perfect the way it was) and make
it objectively worse, by reducing functionality. if you wanted a simple
tasks list why not just make one? why destroy a good thing that has been
working so well all along?
it's very disappointing :(
On Mon, Apr 15, 2019, 22:55 <buganizer-system@google.com> wrote:
jo...@buettgenwetekam.de <jo...@buettgenwetekam.de> #118
rd...@gmail.com <rd...@gmail.com> #119
vs. the old Google Tasks, and it does have some nicer features (and is
free). If you search for my earlier posting on this thread you'll see how
to transition. Also, to see the "notes" associated with each task, click
the double arrows at the right of the screen to open the detail panel.
On Fri, Apr 19, 2019 at 6:17 PM <buganizer-system@google.com> wrote:
li...@gmail.com <li...@gmail.com> #120
pi...@gmail.com <pi...@gmail.com> #121
BRING BACK CLASSIC TASKS. LEAVE SPACE FOR SIMPLE TOOLS. ...your current team isn't creating anything useful... only breaking things they don't understand.
wo...@gmail.com <wo...@gmail.com> #122
anyway.
From past experience, these public forums are totally ignored by the
development and support teams and all they usually just do their own things.
Remember, unless Google can monetarise a product, they wont continue it.
Remember Google+, Picasa, Gmail, Inbox etc?
Their replacements (or UI redesign) are not even vague useful to power
users.
I'm an educator with students now working with Google. They tell me the
people in charge only like shiny new things. Old boring stable isn't worth
it.
The simplicity of the Google search page is only kept because of the CEO's
nostalgia ...
On Mon, 22 Apr 2019 at 01:47, <buganizer-system@google.com> wrote:
rn...@gmail.com <rn...@gmail.com> #123
ja...@gmail.com <ja...@gmail.com> #124
Thanks
ra...@gmail.com <ra...@gmail.com> #125
kb...@gmail.com <kb...@gmail.com> #126
Finding Google Canvas was great. In an age of declining user interface functionality over edginess (including Google's!) it was actually useful and did what was necessary.
Cancvas and search are the only Google apps I care about.
Please bring Canvas back and don't cripple the tasks API by compromising use of subtasks.
It isn't useful if you can't complete documenting the thoughts/dependencies for a topic because you can't add a subtask.
Whoever is making your user interface decisions is certainly failing to deliver products that are useful to people who use computers to accomplish something rather than just for entertainment. Further they deprive users of the opportunity to learn what a good tool is or to be able to associate that with Google.
In summary, please continue to support Tasks Canvas view and multi level subtasks. Thank you.
cr...@noaa.gov <cr...@noaa.gov> #127
ma...@gmail.com <ma...@gmail.com> #128
ar...@gmail.com <ar...@gmail.com> #129
ma...@gmail.com <ma...@gmail.com> #130
jc...@gmail.com <jc...@gmail.com> #131
jcpease@gmail.com
ba...@gmail.com <ba...@gmail.com> #132
kr...@gmail.com <kr...@gmail.com> #133
ro...@gmail.com <ro...@gmail.com> #134
an...@gmail.com <an...@gmail.com> #135
essential to my tasks organization!
sw...@gmail.com <sw...@gmail.com> #136
pi...@gmail.com <pi...@gmail.com> #137
D-level tech support people from the subcontinent?
...because the Google experience now feels like I am talking to a
D-level tech support person who doesn't get paid enough to care.
On 4/22/19, buganizer-system@google.com <buganizer-system@google.com> wrote:
--
· · · —
We love because he first loved us.
--1 John 4:19
re...@gmail.com <re...@gmail.com> #138
by...@gmail.com <by...@gmail.com> #139
Please bring back multi-level sub tasks! (and list order).
sh...@gmail.com <sh...@gmail.com> #140
ca...@gmail.com <ca...@gmail.com> #141
ka...@gmail.com <ka...@gmail.com> #142
ri...@gmail.com <ri...@gmail.com> #143
Although simplicity is the goal of the new UI, do not let this impact the hidden API functionality, and impact the numerous third-party applications that rely on this API. Do not let this impact all the users who have already commented and countless more who currently use multiple sub-tasks and, to the best of my knowledge, will have all of this organization destroyed come August. Don't underestimate the power that comes with having hierarchy, as I'm sure your very large team at Google understands well. And while it is uncomfortable to have features that are absent from the main app, and requires detection of sub-sub-tasks so the "error" message can be displayed, I believe the level of productivity kept and gained by having nested sub-tasks far exceeds this inconsistency.
A suggestion for past and future commenters: Attach screenshots of your tasks, that you are willing to share, and how your nested sub-tasks help your organization and workflow. Pictures can help show the impact of this feature to you that your words cannot convey. The paperclip button is right next to the "Add Comment" one.
lu...@gmail.com <lu...@gmail.com> #144
de...@gmail.com <de...@gmail.com> #145
ra...@suchys.com <ra...@suchys.com> #146
an...@adeyko.com <an...@adeyko.com> #147
sa...@gmail.com <sa...@gmail.com> #148
ma...@gmail.com <ma...@gmail.com> #149
jo...@gmail.com <jo...@gmail.com> #150
91...@gmail.com <91...@gmail.com> #151
ro...@gmail.com <ro...@gmail.com> #152
su...@videogamerepairs.ca <su...@videogamerepairs.ca> #153
al...@gmail.com <al...@gmail.com> #154
cc...@gmail.com <cc...@gmail.com> #155
wr...@gmail.com <wr...@gmail.com> #156
jd...@gmail.com <jd...@gmail.com> #157
an...@schegg.org <an...@schegg.org> #158
Also, loss of canvas and it's UI was very disappointing. It affects my daily workflow. I am trying to find google tasks UI alternatives for desktop use. I'd prefer an offering from google.
sj...@gmail.com <sj...@gmail.com> #159
an...@gmail.com <an...@gmail.com> #160
Connected the App with my Google Tasks and changed the synchronisation method for all my Taskslists/Outlines to "TreelineDropbox".
I have Dropbox-synchronised multilevel tasklists on my phone now and a free desktop Outliner (Treeline Outliner).
There is a detailed tutorial for Android Outliner which describes the synchronisation setup for both, Google Tasks and Treeline Dropbox. And you need the PRO version because the free version lacks the synchronisation feature.
ro...@gmail.com <ro...@gmail.com> #161
ya...@gmail.com <ya...@gmail.com> #162
jp...@gmail.com <jp...@gmail.com> #163
ad...@gmail.com <ad...@gmail.com> #164
ad...@gmail.com <ad...@gmail.com> #165
se...@googlemail.com <se...@googlemail.com> #166
jb...@gmail.com <jb...@gmail.com> #167
bl...@gmail.com <bl...@gmail.com> #168
ra...@gmail.com <ra...@gmail.com> #169
ke...@gmail.com <ke...@gmail.com> #170
ad...@gmail.com <ad...@gmail.com> #171
ma...@gmail.com <ma...@gmail.com> #172
ml...@gmail.com <ml...@gmail.com> #173
my...@gmail.com <my...@gmail.com> #174
jf...@gmail.com <jf...@gmail.com> #175
am...@gmail.com <am...@gmail.com> #176
jl...@gmail.com <jl...@gmail.com> #177
As if removing the Canvas/full screen task view was bad enough...
I had such hopes they would eventually update the canvas view since it with gtasks was one of the only task apps that did what I wanted, only to have it discontinued and than dumbed down further.
la...@gmail.com <la...@gmail.com> #178
rd...@gmail.com <rd...@gmail.com> #179
er...@toplevelfunding.com <er...@toplevelfunding.com> #180
ne...@gmail.com <ne...@gmail.com> #181
pi...@gmail.com <pi...@gmail.com> #182
rd...@gmail.com <rd...@gmail.com> #183
a year now and it works great - similar to Google Tasks but more powerful.
You may be able to search my long ago post on how to transition your stuff
from Tasks to Quire.
No, I don't have any affiliation with Quire. But I had used Tasks for over
a decade and had thousands of entries sorted and organized on it. The
transition to Quire was not too bad, and I am very happy now.
On Wed, Dec 4, 2019 at 3:51 PM <buganizer-system@google.com> wrote:
re...@action-ed.com <re...@action-ed.com> #184
i....@univerpl.com.ua <i....@univerpl.com.ua> #185
without it difficult to us it and i should looking for something else
j....@gmail.com <j....@gmail.com> #186
Just sad that even as a Linux user, I can get better access to Microsoft online apps than I can Google ones.
sa...@gmail.com <sa...@gmail.com> #187
fo...@gmail.com <fo...@gmail.com> #188
no...@ensta.edu.dz <no...@ensta.edu.dz> #189
ah...@gmail.com <ah...@gmail.com> #190
kb...@gmail.com <kb...@gmail.com> #191
Frankly, I'm amazed this even needs to be up for debate.
Thanks!
gi...@gmail.com <gi...@gmail.com> #192
I think it's a must have for such a tool.
sa...@gmail.com <sa...@gmail.com> #193
le...@gmail.com <le...@gmail.com> #194
vl...@gmail.com <vl...@gmail.com> #195
multi-levels is a small technical feature that do a lot in task management
st...@elray.co <st...@elray.co> #196
wr...@gmail.com <wr...@gmail.com> #197
Wayne Greenhalgh
M: 0402313948
ᐧ
On Fri, 3 Jun 2022 at 03:15, <buganizer-system@google.com> wrote:
ma...@gmail.com <ma...@gmail.com> #198
bl...@gmail.com <bl...@gmail.com> #199
PLEASE RESTORE MULTILEVEL NESTING PLEASE
Description
Multiple level of sub tasks is a unique feature in Google Tasks. We know many people that using Google Tasks just because of this functionality. If Google drops the support of that feature then Google Tasks becomes just like any other task application.
-----------------------------------------------------------------------------------------------------------------------------
A short description of the request:
Keep the support of multiple level of sub tasks
What is the purpose of this new feature?
Keep the support of multiple level of sub tasks at least in the task API so that existing custom clients can continue to use that feature.
Ideally, enhance the existing application (e.g. the one that is integrated into GMail, the official Android app) to support multiple level of sub tasks as well.
What existing APIs would this affect?
Task API
What existing data does this use?
-
Please provide any additional information below.