Error message when uploading media files to this forum

[papiris (JD Ludvigsen)]

I get an error message when trying to upload photos and videos (of accepted format) to this forum.
The upload message progresses to 100%, and then I get a pop up saying:
“Sorry, there was an error uploading that file. Please try again.”

I’m accessing the forum via Firefox beta 96.0b3 (64-bit) installed from flatpak.
Is this the expected behaviour, or have I encountered a bug?

output of inxi

inxi -Fazy

System:
  Kernel: 5.15.6-200.fc35.x86_64 x86_64 bits: 64 compiler: gcc v: 2.37-10.fc35
  parameters: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.15.6-200.fc35.x86_64
  root=UUID=3194dff3-054c-4207-a389-80cecdcb9f97 ro rootflags=subvol=root rhgb
  quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
  nvidia-drm.modeset=1
  Desktop: KDE Plasma 5.23.3 tk: Qt 5.15.2 wm: kwin_wayland vt: 1 dm: SDDM
  Distro: Fedora release 35 (Thirty Five)
Machine:
  Type: Laptop System: Notebook product: P95xER v: N/A
  serial: <superuser required> Chassis: No Enclosure type: 10
  serial: <superuser required>
  Mobo: Notebook model: P95xER serial: <superuser required>
  UEFI: American Megatrends v: 1.07.15 date: 11/16/2018
Battery:
  ID-1: BAT0 charge: 46.8 Wh (89.7%) condition: 52.2/53.2 Wh (98.2%)
  volts: 16.5 min: 15.2 model: Notebook BAT type: Li-ion serial: <filter>
  status: Unknown
CPU:
  Info: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP
  arch: Kaby Lake note: check family: 6 model-id: 9E (158) stepping: A (10)
  microcode: EA cache: L1: 384 KiB L2: 1.5 MiB L3: 9 MiB
  flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  bogomips: 52799
  Speed: 1217 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 3901 2: 3776
  3: 1640 4: 1210 5: 2188 6: 2508 7: 2649 8: 2357 9: 2819 10: 3790 11: 3954
  12: 3900
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
  mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
  IBRS_FW, STIBP: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: CLEVO/KAPOK
  driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
  Device-2: NVIDIA GP104M [GeForce GTX 1070 Mobile] vendor: CLEVO/KAPOK
  driver: nvidia v: 495.44 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
  chip-ID: 10de:1ba1 class-ID: 0300
  Device-3: Chicony Chicony USB 2.0 Camera type: USB driver: uvcvideo
  bus-ID: 1-8:3 chip-ID: 04f2:b5a7 class-ID: 0e02
  Display: wayland server: X.Org 1.21.1.3 compositor: kwin_wayland driver:
  loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa alternate: nv
  display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
  s-diag: 582mm (22.9")
  Monitor-1: XWAYLAND0 res: 1920x1080 hz: 60 dpi: 139
  size: 350x190mm (13.8x7.5") diag: 398mm (15.7")
  OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.3.1
  direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: CLEVO/KAPOK
  driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl
  bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel v: kernel
  bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.6-200.fc35.x86_64 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.40 running: yes
Network:
  Device-1: Intel Wireless-AC 9260 vendor: Rivet Networks driver: iwlwifi
  v: kernel bus-ID: 03:00.0 chip-ID: 8086:2526 class-ID: 0280
  IF: wlp3s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: CLEVO/KAPOK driver: r8169 v: kernel port: 3000 bus-ID: 04:00.0
  chip-ID: 10ec:8168 class-ID: 0200
  IF: enp4s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB driver: btusb
  v: 0.8 bus-ID: 1-14:5 chip-ID: 8087:0025 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
  rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 2.05 TiB used: 349.9 GiB (16.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 EVO 250GB
  size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
  lanes: 4 type: SSD serial: <filter> rev: 3B7QCXE7 temp: 42.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000LX001-1RG174
  size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
  type: HDD rpm: 5400 serial: <filter> rev: SDM1
Partition:
  ID-1: / raw-size: 231.3 GiB size: 231.3 GiB (100.00%)
  used: 114.73 GiB (49.6%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
  ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%)
  used: 252.1 MiB (25.9%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-3: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%)
  used: 13.8 MiB (2.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-4: /home raw-size: 231.3 GiB size: 231.3 GiB (100.00%)
  used: 114.73 GiB (49.6%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
  dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 53.0 C pch: 64.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 420 Uptime: 1h 52m wakeups: 1 Memory: 31.2 GiB
  used: 6.66 GiB (21.4%) Init: systemd v: 249 runlevel: 5
  target: graphical.target tool: systemctl Compilers: gcc: 11.2.1 Packages:
  note: see --pkg flatpak: 33 Shell: Zsh v: 5.8 running-in: yakuake
  inxi: 3.3.09

[ilikelinux (L.S.)]

@ruzko

The upload message progresses to 100%, and then I get a pop up saying:
“Sorry, there was an error uploading that file. Please try again.”

I can imagine that has something to do with your trust level. As in the following topic you can see when trust-levels alias user rights are changed manually the error-messages are incorrect.

Why am I unable to send direct messages to Ask Fedora members here?

Yeah — it’s currently set to Trust Level 2. I set it that way because people kept sending me personal messages asking for direct support, which I can’t scale to. I like to help people, but there’s no way I can do it all myself. But it’s not really just about me — this isn’t meant to be a platform for private support. It’s better for conversations to be in the open. Generally, if you have a question or problem, someone else does too. If you have something that’s sensitive and you need a modera…

[papiris (JD Ludvigsen)]

@computersavvy

This is not a forum for photos and videos.

No obvious place in the #start-here category does it say this forum does not accept photos or videos. I mean, it’s reasonable to prefer text based communication over large files, but it should say so somewhere, as well. What is the maximum allowed file size, and does it depend on trust level?

@ilikelinux

I can imagine that has something to do with your trust level

My trust level is Basic User, aka TL 1. According to Discourse I should be able to upload files… I can’t recall having my trust level manually altered.
As an aside, when I check my messages there are none from discobot. How do I get the user tutorials/badges without them?

@ruzko

“Sorry, there was an error uploading that file. Please try again.”

This error message implies that trying again will make it work. I spent an hour in the middle of the night figuring out how to use kdenlive to edit a screen capture video i made of the issue using OBS studio, and converting it to a gif afterwards. Time which would probably have been better spent sleeping.
If the forum behaviour is not a bug, it would be good to change the error message so others won’t spend time trying again.

[ankursinha]

What browser are you using please? Do you have add-ons etc. installed that may be blocking javascript and so on?

[papiris (JD Ludvigsen)]

@papiris

I’m accessing the forum via Firefox beta 96.0b3 (64-bit) installed from flatpak.

I do have ublock origin installed in firefox, but I’ve set it to allow all javascript on this website. There are also some other privacy related addons which might affect forum behaviour. I’ll check when I get home in a bit.
Uploading a screenshot by accessing the forum via Fennec (libre firefox) on my android phone seems to work:

So it might be related to flatpak or one of the extensions/addons I have installed on desktop firefox.

[dalto]

@ruzko

So it might be related to flatpak or one of the extensions/addons I have installed on desktop firefox.

Try temporarily disabling your extensions or temporarily switching to empty Firefox profile.

If that doesn’t work, since you are using an unreleased browser in beta testing, can you try a different browser and see if the problem persists?

[mattdm (Matthew Miller)]

I don’t think there is anything out of the ordinary in in the site configuration that should prevent uploads, and screenshots and even videos of a problem seem reasonable to have (hopefully at least accompanied by search- and accessibility-friendly text).

I’ll look in the logs and see what I can find. @papiris, can you give details of exactly the media you were trying to upload, and the exact time it failed (try again if you didn’t record that the first time) and I’ll forward it to Discourse support. Thanks!

[grumpey (Joe Walker)]

FYI, I was able to upload with the firefox beta flatpak with no extensions.

[papiris (JD Ludvigsen)]

I am able to upload files when firefox is in troubleshooting mode / all extensions are disabled.
This confirms that the problem is probably due to my particular mix of extensions.

Will continue testing to find the offending extension

*Edit 1: If I disable all extensions, upload a file to a comment, then enable all extensions again before posting the comment, the file will still be posted.

[papiris (JD Ludvigsen)]

Found it by method of elimination. ClearURLs 1.21.0 blocks uploading of files to this forum, somehow.
I created an issue concerning this here

Thanks for all your help and suggestions