Thanks for the application! Great work, however I've been experiencing huge memory usage while using it.

I set the background to a 300KB large gif, but oguri uses more than 3GB of memory. I understand that you cache the frames, but I believe this is a bit too much. I'm using arch linux, on wayfire.

There appears to be a code path somewhere that doesn't initialize the wl_list of buffers on an output:

Core was generated by `/home/vil/Code/oguri/build/oguri -s 0 /home/vil/.config/wallpaper fill'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fc5b7be88e0 in wl_list_insert () from /usr/lib/libwayland-client.so.0
(gdb) back
#0  0x00007fc5b7be88e0 in wl_list_insert () at /usr/lib/libwayland-client.so.0
#1  0x000055ac33a2b1f7 in oguri_next_buffer (output=0x55ac33bd0080) at ../buffers.c:99
#2  0x000055ac33a2a9c5 in oguri_render_frame (anim=0x55ac33bc4b90) at ../animation.c:103
#3  0x000055ac33a2bc58 in main (argc=5, argv=0x7ffe2f72bbf8) at ../oguri.c:250
(gdb) frame 2
#2  0x000055ac33a2a9c5 in oguri_render_frame (anim=0x55ac33bc4b90) at ../animation.c:103
warning: Source file is more recent than executable.
103			struct oguri_buffer * buffer = oguri_next_buffer(output);
(gdb) info locals
buffer = 0x0
image = 0x55ac33be1640
first_cycle = true
output = 0x55ac33bd0080
(gdb) print *output
$2 = {oguri = 0x7ffe2f72ba90, link = {prev = 0x55ac33bc4bd8, next = 0x55ac33bc4bd8}, 
  name = 0x55ac33bcff70 "DP-3", output = 0x55ac33bd0030, surface = 0x55ac33bd00e0, 
  layer_surface = 0x55ac33bd0900, width = 2560, height = 1440, scale = 1, 
  cached_frames = 0, buffer_ring = {prev = 0x0, next = 0x0}}

I don't know exactly when this occurred (just noticed it in coredumpctl), but I believe it was immediately after oguri was started by sway (as swaybg_command) when I connected the output.

Not sure how this is happening, as list initialization is the very first thing that oguri_output_create does.

This is a pretty uncommon thing to do, but it can happen for instance when testing a nested compositor. It could also happen by accident. Two options:

• When creating the socket, attempt to connect to it first to determine if an oguri already lives there. If so, disable the new instance's IPC. (Can't just check the file exists, could get stuck.)
• Add the pid to the filename, at the cost of the path no longer being predictable.

The second option could be improved by a configurable path.

Issue 31 mentions a case where ogurictl output * --image whatever.png doesn't override the config file value if it is set.

But I have config output value set as

[output *]

and I'm not able to change images with ogurictl output * --image whatever.png

My images change as expected with a specific output ogurictl output eDP-1 --image whatever.png

I'm using oguri in a small dynamic wallpaper script so it would be nice to be able to set wallpapers with * instead of trying to figure out what displays are available.

Thanks for your help.

Finally tried it, doesn't work.

Currently animations rely on there being a next frame to change scale. We need to schedule a redraw of the current frame unconditionally after output scale changes, since we don't know when or if the next frame will occur.

If I don't open this issue, someone else will. ;)

See here.

This can result in multiple oguris running on the same display when new ones are connected, leaving the new one out in the cold. This isn't worth fixing before #3, at which point this mode can be moved to the ipc client and we can have just a single oguri running.

I would love for people to share their favorites here

Currently if you change config like ogurictl output * --image whatever.png but you have a non-wildcard output section in the config file, the change will not affect that output. This is technically correct, but not what any user would expect.

Before passing an image path over to oguri it needs to be made into an absolute path.

Is there any possibility of supporting formats like

• APNG
• WebP
• FLIF

or even a video format like mp4?

I ask because I have a detailed animation that I would like as a wallpaper that gif's 256 color limit absolutely destroys. If there is another way I can get a full color range with oguri as it is, that would also work. Thanks for your hard work and awesome project!

This isn't urgent, but a library that would give us more control of the animation would be preferrable. Right now we're relying on a pretty awful hack to be able to determine the number of frames present in a gif.

If you're using the same image on all displays, it would be nice to have just one process hogging CPU time instead of n.

It would be nice to use the fact that we have all of cairo already available to draw shadows/gradients along the screen edges to help readability of transparent bars.

I'd like to run https://github.com/adi1090x/dynamic-wallpaper on swaywm. I read to the readme but I still have no idea how to use it.

Sent from my OnePlus 7 using FastHub

Idk how can I decrase cpu usage. I got ryzen7 3700u cpu. Its always usa that much cpu. These are my config file

Hello! First of all thank you for this I really enjoy it. However one issue I have found is when using ogurictl after looking at the code from what I understand instead of drawing the new image then getting rid of the last one it seems you just keep drawing the new image over the new one. This wouldn't be an issue but if you switch wallpapers a lot(like a wallpaper switcher or something). It leads to very high memory usage.

Thanks for making oguri, This looks nice!

Do you have suggestions regarding good resources to pick gif wallpapers from?
I usually find mine on http://wallheaven.cc/ , but they don't seem to share gifs there. And https://giphy.com/ doesn't seem to offer the possibility to search by resolution.

Hello, very promising project indeed. I have a problem with one thing though.

$ oguri -h
Usage: oguri [-c <config-path>]

  -c  Path to the configuration file to use.
      (default: $XDG_CONFIG_HOME/oguri/config)
  -h  Show this text.

To control oguri while it is running, use `ogurictl`.

To control oguri while it is running, use ogurictl.

The promised utility is nowhere to be seen 😱

Hi, I have added swaybg_command oguri-swaybg to my sway config but all i get is a grey backround.

There are no errors in the log so I don't know what the problem is

Is there a way to leave the animation in the original resolution ie. smaller than the resolution of the output?

I would just like to make a small animated "amblem" in the center of the display with the surrounding background fixed black color.

I don't want my wallpaper tool to depend on CUPS. We can use the same code as emersion/mako#142.

Hey,

to use the same wallpaper in multiple tools I set it as an environment variable called WALLPAPER. Prior to 6937fee it was possible to simply set image=$WALLPAPER inside the config file, but as a regression this is not possible anymore.
Possible workarounds might be to symlink the current wallpaper or to rewrite the config file on change if the fix is not trivial, but I really liked to simply expand my variable. :)

By the way: I am packaging oguri for openSUSE: https://build.opensuse.org/package/show/home:jlkDE/oguri

Hi there, thanks so much for oguri, it's a great tool!

I'm opening this issue to express interest in a way to have oguri re-read its config file and seamlessly apply any changes. My use case is that I want to have my wallpaper change depending on the time of day. I have a system that re-writes configs for color schemes and other theme elements depending on the time of day, and I'd like to have it re-write my oguri config and then reload oguri to show a new wallpaper.

I could use ogurictl now to directly load a path to a new background image, but that would require running a different ogurictl command depending on the time of day which doesn't quite work for me.

Thanks for your consideration!

Nearest neighbor is nice for pixel art, and not a whole lot else.

This could be useful for a few things, off the top of my head:

• Changing the image on the fly
• Pausing/resuming animation (for example, while the desktop is mostly covered)
• Ok, maybe just two things

➜ oguri git:(master) ✗ build/oguri
oguri: ../oguri.c:308: main: Assertion `oguri.display' failed.
[1] 165840 IOT instruction (core dumped) builda/oguri

My use-case for this would be that I'm currently trying to "force" GLava to work on Wayland. What I plan to do is to trick OBS into recording into a FIFO and make oguri play back the fifo. Unfortunately, oguri doesn't recognize the FIFO as a valid GIF file:

File does not appear to be a GIF file
Could not open image '/home/user/glava-fifos/test.gif': File does not appear to be a GIF file

I've tried looking for the error in the code, and I don't see it. If I knew where to find it, I'd definitely make a PR instead of making a feature request.

edit1: This is actually very probably an A/B problem, but GLava probably won't ever be on wayland, best I could hope for is probably GIF output to a FIFO which is.. still this feature request.

Hi,

I just tried oguri and its awesome. Its totally worth the 18GB Ram it would use to load my 388MB Gif which I converted from an Webm, but sadly my Kernel thinks differently. Can you add support to other Video formats like webm?

Hi,
I haven't installed sway yet. How can I use oguri (some tutorial for beginner)? My command in terminal (I'm in ../oguri/build/) ./oguri -c /home/user/Wallpaper/config give me back:
Segmentation fault
My config is:

[output LVDS-1]
image=/home/zic/Wallpaper/background.jpg
filter=nearest
scaling-mode=fill
anchor=center

so I look at log:
sudo tail -f /var/log/syslog

Sep  9 23:47:58 Debian-zic kernel: [20781.071150] oguri[14287]: segfault at 0 ip 00007fe704d54274 sp 00007ffc918334a0 error 4 in libwayland-client.so.0.3.0[7fe704d53000+6000]
Sep  9 23:47:58 Debian-zic kernel: [20781.071156] Code: 29 ac 24 50 01 00 00 0f 29 b4 24 60 01 00 00 0f 29 bc 24 70 01 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 c8 00 00 00 31 c0 <48> 8b 13 4c 8d 6c 24 20 48 8d 4c 24 08 48 8d 84 24 b0 01 00 00 c7

but I don't understand what it means..

files in : /home/user/Wallpaper/ : ls -lah

drwxr-xr-x 2 zic zic 4,0K wrz 10 00:16 .
drwxr-xr-x 7 zic zic 4,0K wrz 9 23:23 ..
-rwxr-xr-x 1 zic zic 189K wrz 9 02:01 background.jpg
-rw-r--r-- 1 zic zic 93 wrz 10 00:15 config
-rw-r--r-- 1 zic zic 24M wrz 9 03:42 matrix.mp4

OS: Debian 10 (Wayland)

Reload image from disc, if ogurictl output * --image path/to/wallpaper.png issued with --image argument pointing to current image.

Use case: I have single wallpaper file and timer, that periodicaly replaces that file with new one. After image is replaced, I have option to issue ogurictl command, but currently nothin changes. I assume this is optimization to reduce load.

Another solution would be something like ougrictl reload to ask reload image from disk.

It seems that running oguri from a crontab results in a socket not found error

Unable to connect to oguri socket: No such file or directory

I am not sure what this means.

We have config for this, but only fill actually works.

When using ogurictl with an image that has a space in the filename it outputs Invalid configuration, and oguri outputs [ipc:2] Failed to parse property 'image'.

There is a workaround to this which is to add escaped quotes to the filename, such as ogurictl output --image \"/tmp/with\ space.jpg\" '*' instead of ogurictl output --image /tmp/with\ space.jpg '*'.

It seems like not providing a name makes you lose the control capacity.

Hello, today i found this great repository and tried to use and therefore build it, but during the building process i encountered a strange issue, despite cairo (cairo-1.17.4-3.fc34.x86_64) being already installed i received this:
`Build type: native build
Project name: oguri
Project version: 1.0.0
C compiler for the host machine: cc (gcc 11.1.1 "cc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1)")
C linker for the host machine: cc ld.bfd 2.35.1-41
Host machine cpu family: x86_64
Host machine cpu: x86_64
Found pkg-config: /usr/bin/pkg-config (1.7.3)
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency cairo found: NO (tried pkgconfig)

meson.build:14:0: ERROR: Dependency "cairo" not found, tried pkgconfig`

Hi, sorry to create two issues in one day. Now that the previous one was fixed I have found this one.

Basically, when integrated with sway the background seems to flicker in between image changes. The reason I had switched to oguri was because I was led to believe (while reading about this exact same problem with swaybg) that oguri would not flicker.

Is this something that can easily fixed?

Oguri crashes after playing through the gif once with the following in its log:

request could not be marshaled: can't send file descriptor
Error sending request: Broken pipe
Failed to read Wayland events: Broken pipe

I'm on a very minimal debian install, so I may be missing some obvious dependency. Also, the file I'm playing is quite large (originally a 1:15 1080p video before conversion to a gif)

Varlink is a simple IPC API. This could be used for directly controlling oguri from other applications, without having to invoke ogurictl.
https://varlink.org/