Crash on startup: 'Cairo error "invalid value (typically too big) for the size of the input (surface, pattern, etc.)"''

[Jonathan Schuster]

I just updated my Arch Linux install the other day, and after that (possibly related, possibly not) cairo-dock started crashing on startup with the following error message. It then tries to restart a few times and eventually launches itself into maintenance mode, where it shows me the configuration window, but the dock never shows up even if I close that window.

I'll try removing some of the applets and see what happens; I'll report back here if I can find out any more information.

warning : (/build/cairo-dock/src/cairo-dock-core-3.4.1/src/implementations/cairo-dock-egl.c:gldi_register_egl_backend:232)
  Cairo-Dock was not built with EGL support

 ============================================================================
 Cairo-Dock version : 3.4.1
 Compiled date : May 18 2015 12:32:11
 Built with GTK : 3.16
 Running with OpenGL: 1
 ============================================================================

warning : (/build/cairo-dock/src/cairo-dock-core-3.4.1/src/gldit/cairo-dock-module-manager.c:gldi_module_new_from_so_file:160)
  while opening module '/usr/lib/cairo-dock/libcd-Recent-Events.so' : (libzeitgeist-2.0.so.0: cannot open shared object file: No such file or directory)
warning : (/build/cairo-dock/src/cairo-dock-core-3.4.1/src/gldit/cairo-dock-module-manager.c:gldi_module_new_from_so_file:160)
  while opening module '/usr/lib/cairo-dock/libcd-mail.so' : (libetpan.so.20: cannot open shared object file: No such file or directory)
g_file_test: assertion 'filename != NULL' failed
g_file_test: assertion 'filename != NULL' failed

(cairo-dock:6697): Gtk-WARNING **: 13:31:55.657: Theme parsing error: <data>:7:1467: The :insensitive pseudo-class is deprecated. Use :disabled instead.

(cairo-dock:6697): Gtk-WARNING **: 13:31:55.657: Theme parsing error: <data>:7:3649: The :inconsistent pseudo-class is deprecated. Use :indeterminate instead.
thread '<unnamed>' panicked at 'Cairo error "invalid value (typically too big) for the size of the input (surface, pattern, etc.)"', /build/.cargo/registry/src/github.com-1ecc6299db9ec823/cairo-sys-rs-0.5.0/src/enums.rs:75:13
stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: rsvg_handle_render_cairo_sub
  14: cairo_dock_create_surface_from_image
  15: cairo_dock_load_image_buffer_full
  16: cairo_dock_load_dock_background
  17: <unknown>
  18: g_main_context_dispatch
  19: <unknown>
  20: g_main_loop_run
  21: gtk_main
  22: main
  23: __libc_start_main
  24: _start
fatal runtime error: failed to initiate panic, error 5
warning : (/build/cairo-dock/src/cairo-dock-core-3.4.1/src/cairo-dock.c:_cairo_dock_intercept_signal:180)
  Cairo-Dock has crashed (sig 6).
It will be restarted now.
Feel free to report this bug on glx-dock.org to help improving the dock!
info on the system :
Linux atlantis 4.16.7-1-ARCH #1 SMP PREEMPT Wed May 2 21:12:36 UTC 2018 x86_64 GNU/Linux
Couldn't guess if it was an applet's fault or not. It may have crashed inside the core or inside a thread
restarting with 'cairo-dock -w 2 -q 1'...

[Miguel Rasero (skuda21)]

Same problem here :|

[Jed Liu (jed-ubuntu-com)]

Steps to reproduce from an empty .config/cairo-dock:

1. Start `cairo-dock -o` and enter configuration.
2. Enable advanced mode.
3. Under Docks, make the following changes:
    - in Background, change Style to "Image"
    - in Views, change Main Dock to "3D plane".
4. Apply and close configuration.
5. Restart cairo-dock.

[Jonathan Schuster (jschuster)]

I get many of the same warnings on another up-to-date Arch Linux machine where cairo-dock works fine, so the relevant portion of the output above appears to be the part starting at "thread '<unnamed>' panicked".

[Michael Kogan (michael-kogan)]

Downgrading librsvg from 2:2.42.4-1 to 2:2.42.3-1 is a workaround for me on my Arch machine. Seems like Cairo-Dock needs to be update to support the new librsvg version.

[Michael Kogan (michael-kogan)]

Reported the problem upstream, not sure if anybody will read it there though, the forums looks dead but I couldn't find a better place for reporting a bug: http://www.glx-dock.org/bg_topic.php?t=13227

[Jed Liu (jed-ubuntu-com)]

Thanks for tracking down the librsvg issue, and for reporting it upstream. I'm not optimistic for a fix, though. It looks like Cairo-Dock has been abandoned. The last commit to core was in Sep 2016: https://github.com/Cairo-Dock/cairo-dock-core.

I've looked for alternatives and have settled on latte-dock, which seems to integrate well with Plasma. Plank looked nice too. Both are in the Arch community repos.

[Michael Kogan (michael-kogan)]

Well, I wouldn't give up on Cairo-Dock so fast, it has received no development during the last year, but already for several years there were only 2-3 commits per year were pushed done, so I assume that we can hope the development to continue with this slow pace rather than being completely dead. If the developers receive the bug report, I am quite positive that the issue will be fixed. I would propose to wait for some reaction to my post on the official forums and, if none follows for some days, contact the devs by mail.

[Michael Kogan (michael-kogan)]

Sent a mail three days ago, no reply yet - looks like I was wrong in the end...

[Michael Kogan (michael-kogan)]

Reported at Arch's bug tracker as well: https://bugs.archlinux.org/task/58803

[Michael Kogan (michael-kogan)]

Further findings:

1. The bug appears on some machines but not on all: I have a Manjaro install where librsvg has been updated to .4 already and the bugs doesn't appear.

2. The bug appears only if the plugins package cairo-dock-plug-ins is installed.

3. Rebuilding the core and plugins packages didn't solve the issue.

4. The first commit to librsvg causing this bug is https://github.com/GNOME/librsvg/commit/628180823876d7ff446f5d6cb5f8448b65d287a2 Bisection log: https://pastebin.com/ytM64MBa

Can anybody confirm any of these?

[Michael Kogan (michael-kogan)]

Reported issue upstream at librsvg: https://gitlab.gnome.org/GNOME/librsvg/issues/276

[Michael Kogan (michael-kogan)]

The issue will be fixed in librsvg 2.42.5. Though the origin of the problem is in cairo-dock, librsvg will now handle the problem without crashing.

[Michael Kogan (michael-kogan)]

librsvg 2.42.5 has landed in Arch now.