Arch Linux User Repository

A package provides and conflicts with itself. This package needs no provides() or conflicts(); especially with packages that don't exist. The wavebox-beta package should only provide and conflict with wavebox.

Thanks, @etrigan63. Looks like a change to our build script popped just the first character of the md5 hash into the files :facepalm:

I've updated the repo with the correct hashes and also the build script for next time, so it should be working again now

Today's update failed to install.

Aur (1) wavebox-10.101.21_2-1

:: Proceed with installation? [Y/n]:

:: Downloading PKGBUILDs...
 PKGBUILDs up to date
==> Making package: wavebox 10.101.21_2-1 (Thu 12 May 2022 10:23:08 AM EDT)
==> Retrieving sources...
  -> Found wavebox-10.101.21_2.tar.gz
  -> Found wavebox.appdata.xml
  -> Found wavebox.menu
  -> Found LICENSE
==> Validating source files with md5sums...
    wavebox-10.101.21_2.tar.gz ... FAILED
    wavebox.appdata.xml ... Passed
    wavebox.menu ... Passed
    LICENSE ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'wavebox-10.101.21_2-1':
error: packages failed to build: wavebox-10.101.21_2-1

@benvosper glad you got it working! I know getting HW acceleration has been a bit tricky to nail down on Linux with Chromium & its derivates.

The chromium-flags.conf isn't part of standard Chromium, it's something that's been added to the arch version.

With Wavebox, I think the best way would be to update the desktop file, normally under /usr/share/applications/. You can append these to the exec line...

- Exec=/opt/wavebox.io/wavebox/wavebox-launcher %U
+ Exec=/opt/wavebox.io/wavebox/wavebox-launcher --ignore-gpu-blocklist --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder %U

Can anyone advise as to whether hardware video acceleration is expected to be working with this build of Wavebox and its bundled chromium?

I have acceleration correctly configured according to the guide here (as confirmed by vainfo). And Hardware Acceleration is Enabled in the Wavebox settings. But going to about:gpu in Wavebox shows:

Canvas: Hardware accelerated
Canvas out-of-process rasterization: Disabled
Direct Rendering Display Compositor: Disabled
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
OpenGL: Enabled
Rasterization: Hardware accelerated on all pages
Raw Draw: Disabled
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Video Encode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated

This manifests as high CPU usage when streaming video or video conferencing.

I've tried the notes for enabling hardware acceleration with Chromium detailed here but I'm unsure if these are being correctly applied to Wavebox's bundled chromium.

Does anyone else have it working on their system? I'm using an i7-1165G7 with integrated graphics with the intel mesa drivers.

@tomwavebox

EDIT: I can now get it to work correctly (showing "Video Decode: Hardware accelerated") by adding the following flags to the wavebox launcher:

--ignore-gpu-blocklist 
--enable-features=VaapiVideoDecoder 
--disable-features=UseChromeOSDirectVideoDecoder

I had thought that these would be picked up from the chromium-flags.conf file, but I realise now that this is only used by the arch chromium package.

So the question now is: what's the best way of making these startup flags persist without needing to manually modify the package files? Or, is there a way to set these values from within the application itself?

@tomncooper thanks for reporting! I've just pushed version 10.92.15 to the beta channel (https://aur.archlinux.org/packages/wavebox-beta), this uses Chromium 92.0.4515.131 which should fix this. All being well, that version should come out into this package later this week.

@Mordavolt I'll try to get this into the next cycle!

Since the latest update Wavebox simply renders as an empty untitled chrome window and is unresponsive. Loading on the command line shows:

[36146:36146:0803/104616.351388:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[36146:36146:0803/104617.599034:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[36146:36146:0803/104618.713908:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[36146:36146:0803/104620.543984:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[36146:36146:0803/104622.790717:ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
[0803/104623.093311:ERROR:scoped_ptrace_attach.cc(37)] process not stopped
[0803/104623.093428:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
[0803/104623.093466:ERROR:exception_handler_server.cc(142)] tgkill: No such process (3)

Which seems to match this issue with the latest chromium version on Arch.

Could you please add wavebox-launcher to the path as part of the build? I don't have a "desktop", so to run wavebox I have to run /opt/wavebox.io/wavebox/wavebox-launcher.

Hi everyone, I'm Tom from the Wavebox team. Firstly I just wanted to say a giant thank you to droidbot1711 for creating the Wavebox package and maintaining it for so long!

With his help, we've added the Wavebox AUR into our CI and are happy to officially support it as one of our distribution methods! We're also publishing the wavebox-beta package (https://aur.archlinux.org/packages/wavebox-beta/) for anyone who likes to try features out a little bit before they hit the mainline channel :-).

If anyone needs help with the Wavebox repo, or Wavebox itself, please feel free to reach out here, or contact us on Wavebox support (https://wavebox.io/support) we'd be happy to help!