When trying without root:
$ dd if=/dev/zero bs=16M count=1 of=test.img
1+0 records in
1+0 records out
16777216 bytes (17 MB, 16 MiB) copied, 0.0326881 s, 513 MB/s
$ echo foo | cryptsetup luksFormat test.img –
Not compatible PBKDF options.
Whereas for root it still works:
# dd if=/dev/zero bs=16M count=1 of=test.img
Please touch the device.
1+0 records in
1+0 records out
16777216 bytes (17 MB, 16 MiB) copied, 0.0183403 s, 915 MB/s
# echo foo | sudo cryptsetup luksFormat test.img –
#
For a workaround (from upstream report) with non-root, specify –type luks1:
$ dd if=/dev/zero bs=16M count=1 of=test.img
1+0 records in
1+0 records out
16777216 bytes (17 MB, 16 MiB) copied, 0.0138972 s, 1.2 GB/s
$ echo foo | cryptsetup luksFormat –type luks1 test.img –
$
Oh and I’m using Wayland, in case it matters here. Haven’t yet tried whether Xorg is similarly affected.
When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says:
Boxes wants to inhibit shortcuts
You can restore shortcuts by pressing Super+Escape.
In my locale (Finnish), it says
Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.
Voit palauttaa pikanäppäinten toiminnan painamalla Super…
(sic; see attached photo)
So the actual key combination is truncated, defeating the point of that part of the text.
This isn’t a localization error (AFAICT; see [2]). It’s caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed.
(I’m reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.)
* [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
* [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10&show=all&search=pikan%C3%A4pp%C3%A4inten
* [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036
Comments can no longer be updated, as pressing the Edit button just reverts the comment back to what it was prior to editing. Both rich and non-rich editor are affected.
Server Setup Information:
- Wekan version: 3.89
- Operating System: Ubuntu 16.04
- Deployment Method: snap
- Http frontend if any: Apache
- Web browser: both Chrome and Firefox affected
Steps to reproduce
- Add a comment to a card.
- Click the
edit
link to start editing the comment, make some changes.
- Click the
Edit
button.
What I expect to happen
For the comment to reflect the changes made when editing.
What happens instead
The comment content reverts back to what it was prior to editing.
Logs
Nothing in browser console log, nothing related in server log.
For some of the depressing history of this, see bug #875002 (which has been incorrectly marked as fixed by someone without a clue) from way back in 2011.
I’m using 20.04 and a Wayland session. My preferred focus mode is to have it follow the mouse cursor:
$ gsettings get org.gnome.desktop.wm.preferences focus-mode
’mouse’
Unfortunately this causes GTK apps’ popup (RMB) menu to jump to the app window corner when opened. I’m attaching a screencast, where I demonstrate the bug first, then reset focus-mode to ’click’ to demonstrate the bug no longer manifesting. (Please excuse the flashing. It’s just a video artefact caused by Gnome’s built in screen recorder, which was the only one that at least somewhat worked.)
This has been reported upstream, where a fix was recently merged: https://gitlab.gnome.org/GNOME/mutter/issues/1103
Folders for auto upload? I have Camera twice (/storage/emulated/0/DCIM/Camera
; once for pictures, the other for videos), OpenCamera (/storage/emulated/0/DCIM/OpenCamera
) and Screenshots (/storage/emulated/0/DCIM/Screenshots
).
(I only tried OpenCamera briefly, recently, and have since uninstalled it. The issue at hand was present already back when I first got this phone and installed Nextcloud on it, last July.)
I’ve always had auto upload enabled until now, so can’t say whether it’s dependent on that. I could try disabling it next time the issue re-emerges; as dictated by Murphy’s law, I was unable to trigger it just now that I intentionally tried to.
Oh, and I am running Beta (so currently 3.11.0 RC4) of the Nextcloud app. Can’t remember when I enrolled in.
I presume updating an existing installation is just a matter of replacing the existing files with files from the new release, but as this isn’t made explicit in the readme, I’m just a bit apprehensive about going ahead with it.
Problem description
Using ctrl-v to paste content into a comment causes the view to scroll back horizontally so that if the card was already at the right edge of the view, it seemingly pops out of view. This happens when using Firefox; Chrome seems unaffected.
I’m currently unable to test whether the non-rich editor is affected due to #2967, and also, as I was exclusively using non-rich editor prior to this, I can’t say if this occurred with the 3.85 refresh or whether it was here with the rich editor even before.
Server Setup Information
- Wekan version: 3.85
- Operating System: Ubuntu 16.04 (19.10 in another test VM)
- Deployment Method: snap
- What webbrowser version? Firefox 74.0, Chrome 80.0.3987.149
Logs contain nothing related to this AFAICT.
Steps to reproduce
- Copy something to clipboard
- Have a board with enough lists to fill the view horizontally, or contract the browser window to have one list at the right edge
- Open a card from the rightmost list
- Select the comment field, press ctrl-v
Demo
Here I’m first typing something, then pasting below it (using ctrl-v) to cause the unwanted scrolling to occur.