25.0.3 (as indicated by output from `occ –version` above).
25.0.3 (as indicated by output from `occ –version` above).
25.0.3 (as indicated by output from `occ –version` above).
The exit code issue is still there:
# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ --version
Nextcloud 25.0.3
# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ files:scan -- nonexistantuser
Unknown user 1 nonexistantuser
+---------+-------+--------------+
| Folders | Files | Elapsed time |
+---------+-------+--------------+
| 0 | 0 | 00:00:00 |
+---------+-------+--------------+
# echo $?
0
Hi @hmhealey,
Yes, it’s mainly about expectation. For an actual use case, I noticed this when mentioning an IRC channel name, which became a long, distracting and useless hashtag link, exacerbated by agglutination and multi-word hyphenation typical in Finnish, (e.g. #channelname-irc-kanavalla). I tried to make it less distracting by editing in a preceding backslash, only to discover that it didn’t work here.
There is no way to escape a word-starting hash character (#) in plaintext.
In MM 7.3.0, post this, verbatim: \#anything
#anything
Workaround: instead of ”\#anything”, post this: #anything
Using backticks (`\#anything`) also works, but obviously the word then gets formatted as code and not plaintext.
This is mainly an issue of inconsistency and surprise: backslash works to escape most other special formatting, so I’d expect it to work here too.
Still present in Nextcloud 3.21.2. My device is a Samsung A9 running Android 10.
Please tell me more about your window environment; Gnome/Mutter don’t support Client Side Decoration (CSD) for Wayland clients, so wezterm draws its own limited decorations. Those don’t support right clicking or context menus, so I’m not sure how that maximize menu you described shows up.
Sure, though I don’t yet know anything beyond ”this is a standard Ubuntu 20.04 (Gnome) desktop, using Wayland”. Are there any commands I could run to find out more?
Copy & paste doesn’t work in the debug overlay (any selection I make is deselected as soon as I hit Ctrl), but there’s nothing there anyway apart from the intro (no matter how many times I trigger the resizing issue).
Linux Wayland
Gnome
20220927-071112-9be05951
Yes, and I updated the version box above to show the version of the nightly that I tried
I’m running a standard Ubuntu 20.04 Gnome desktop, but with Wayland. Resizing of wezterm window is broken on this setup: selecting ”maximize” from the title bar context menu or dragging the window against the top or the sides of the screen doesn’t maximize/tile the window, but any resizing that does happen results in any text entered in the terminal thereafter to be get garbled. In this screenshot I’ve first entered wezterm --version
before resizing, then dragged the window against the top, then entered wezterm --version
again:
no config
After step 5, I expect the window to be maximized (i.e. to fill the desktop). After step 6, I expect to see what I typed.
no logs available
The issue is not present in an X11 session. Ubuntu 20.04 defaults to X11, but I’ve used it with Wayland exclusively since the release without issues. More specifically, I can’t remember seeing resizing issues similar to this with any other application.
I also have a laptop running Ubuntu 22.04 and Wayland, and there all resizing of the wezterm window works just as I’d expect (i.e. just as in any other application).
Hi @claucambra, I tested the appimage and the issue still reproduces.
Using a path with umlauts as logDir
causes an incorrectly encoded directory to be created and used as log directory, instead of the specified directory.
nextcloud.cfg
. Set logDir=/home/jani/Tänne
(applying appropriately to your home directory)ls /home/jani/Tänne
A listing of new log files residing in /home/jani/Tänne
.
This question is unclear. The log files are the ones affected.
Linux
Ubuntu 20.04
Distro package manager
24.0.4
3.5.4-20220806.084713.fea986309-1.0~focal1
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Encryption is Disabled
No response
This bizarre and otherwise exhaustingly long issue form is lacking a ”What happens instead of my expected outcome” question, so I’m entering it here instead: there are no logs in the specified target directory (it doesn’t even exist if you’ve not created it beforehand). Instead, like in the ye olden days, there is now a directory called Tänne
containing the logs. In nextcloud.cfg
the path has been re-encoded as logDir=/home/jani/T\xc3\xa4nne/
which is apparently how it should be, since a similarly re-encoded value for a ...localPath
with umlauts in the [accounts]
section has been working just fine for as long as I can remember using it.
I’m affected by this. Storied from PBS appears the only one of my followed channels to exhibit this, though it may very well just be the only one with audio description tracks provided. For instance, this video has the first description at t=71 (”A huge orange eye opens”). As with Yuseldin’s example, the descriptive track is available, but not selected by default when I open the video in a browser.