Describe the bug
The email with updates from the last 24 hours lists identifications, and mentions the name of the user having made the ID. The name is apparently supposed to be listed three times (!), but the middle occurrence is ”untranslated”, resulting in it being rendered as ”User S” for all identifications listed in the email.
Tooltip text for the ”User S” string says ”translation missing: fi.user_s_id”, as I’m using the fi locale, but
user_s_id is nowhere to be found in Crowdin, nor in current
en.yml, so I suspect this is independent of the locale. The reference to
user_s_id is in
I don’t know if this is doable, but after fixing this broken reference, I’d remove the first (header) mention of the identifier from the email altogether, since it’s followed by a listing of all the new identifiers anyway, so mentioning just the last identifier’s name in the header is redundant and confusing.
Also, rather than fixing/adding the currently broken ”User S” reference in the source, I’d remove it too, since the identifier’s name is already listed (for the third time!) right after the ID.
- Subscibe to email updates.
- Have your observations identified in the last 24 hours.
- View the email update listing the identifications.
(A mockup of how the simplified view I’d prefer to receive. Sorry I didn’t have the email in English to base this on.)
I’m using Gmail with Brave if that’s relevant.
There’s no gnome-shell-extension-dashtodock package for focal , but I did try with Dash to Dock from extensions.gnome.org, and could not reproduce the issue with it. I tried with the default settings, as well as after recreating the look & feel of Ubuntu Dock as much as possible.
Dash to Dock has customizable action for the scroll (to either switch workspaces or windows, or to do nothing), and all of those also worked just as expected.
I also noticed that using the two finger scroll function of the touchpad on my laptop does *not* trigger this (whereas using the mouse on it does).
*  https://packages.ubuntu.com/search?keywords=gnome-shell-extension-dashtodock
Do you want another log for that? Because (as I already mentioned above), this also reproduces when using a newly-created user, so that means no unsupported extensions.
I can reproduce the crash at will with the steps I listed above, so I don’t have to wait for it to happen. It also doesn’t forcibly log me out, so I can enter those commands by just having a terminal window present when I trigger the issue. But I logged out here (after triggering) anyway since you instructed me to log in, in case it matters.
Also, there’s lots of noise in these from Boinc, thanks to #1876313.
@FlexW I’ve now rebased and pushed the changes, hope this works for you. I don’t see a way for me to merge this myself here, ”Only those with write access to this repository can merge pull requests.”
1. There’s nothing in /var/crash
2. There are no reports on the page for this computer.
3. Done, still nothing in /var/crash.
I don’t know if this means it’s not a true crash, although visually all the indications are there.
I also verified that this reproduces when using a newly-created user (with the only change from defaults for it being switching to Wayland), and also on another computer (also running 20.04). I am limited to using the one mouse that I have, so that all testing so far has been with the same mouse.
# Steps to reproduce
0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll)
1. move mouse pointer over the dock
2. use the mouse scroller to scroll horizontally
# What I expect to happen
# What happens
Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock.
# Other info
Slightly similar to LP #1875106, but I’m not using imwheel.
I am using Wayland.
Syslog seems to always point to this one function: ”The offending callback was get_preferred_height(), a vfunc”. I’ll attach the relevant part from one crash.
I can add that to options.rst, but the terse explanation still seems pretty meaningless; at least for me there’s no visible difference when I run nextcloud with
--background compared to running without.
This could be due to #2333 though, if running without
--background is supposed to open the main dialog (which has never worked on Focal). If so, I’d mention this too, something like: ”Launch the application in the background (without opening the main dialog).”
@FlexW Not really, as I don’t know what the parameter does… due to it being undocumented :) Editing options.rst shouldn’t be an issue, I’d just need to know what it should say about