← Back to team overview

cairo-dock-team team mailing list archive

[Bug 1398238] Re: cairo-dock crash if applications menu enabled, segfault

 

Incompatable package identified:

Updating from Trusty's version of libgnome-menu to

libgnome-menu-3-0_3.10.1-0ubuntu4_amd64.deb

breaks the applications menu in Cairo-dock, but you may have to reboot
after the update to reproduce the crash to maintainance mode (normal
start) or segfault indication (test mode). Reverting the package to the
prior version fixes the menu,

-- 
You received this bug notification because you are a member of Cairo-
Dock Devs, which is subscribed to Cairo-Dock Core.
https://bugs.launchpad.net/bugs/1398238

Title:
  cairo-dock crash if applications menu enabled, segfault

Status in Cairo-Dock : Core:
  New

Bug description:
  Using cairo-doc version 3.4.0 in Ubuntu Vivid Vervet (alpha version of
  Ubuntu), installed from Ubuntu packages.

  cairo-dock_3.4.0-0ubuntu1_all.deb
  cairo-dock-core_3.4.0-0ubuntu1_amd64.deb

  To reproduce, install cairo-dock from these packages and their
  dependencies into Ubuntu Vivid as last updated on or after Nov 21.
  Enable the applications menu and attempt to start the dock. No
  difference between opengl and cairo rendering, the crash always occurs
  either way.

  Cairo-dock core has not updated since 3.4.0 came out in Utopic,
  plugins have updated once. Rolling back the plugins versions has no
  effect.

  Crash started (every time) beginning with the Nov 21 round of updates
  to Ubuntu vivid, and not present after the Nov 16 round of updates (no
  updates between those dates, not enough bandwidth at home), cairo-dock
  can no longer start normally if the applications menu is enabled,
  opening into maintainance mode instead with a crash and restart listed
  if started in terminal.

  Experimenting with launching from from terminal and attempting to
  enable the menu by various means I got these results, a debug.txt file
  is also attached to this bug report:

  As desklet, enabling from inside module configuration (does NOT write
  to config file!):

  g_strsplit: assertion 'string != NULL' failed
  g_once_init_leave: assertion 'result != 0' failed
  warning :  (/build/buildd/cairo-dock-3.4.0/src/cairo-dock.c:_cairo_dock_intercept_signal:180)  
    Cairo-Dock has crashed (sig 11).

  
  As desklet, enabling from main configuration

  context mis-match in pipe_sampler_view_release()
  g_strsplit: assertion 'string != NULL' failed
  g_once_init_leave: assertion 'result != 0' failed
  warning :  (/build/buildd/cairo-dock-3.4.0/src/cairo-dock.c:_cairo_dock_intercept_signal:180)  
    Cairo-Dock has crashed (sig 11).
  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 ubuntu 3.18.0-999-generic #201411162130 SMP Mon Nov 17 02:31:34 UTC 2014 x86_64 x86_64 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 --keep-above -m -q 3'...

  MORE DETAILS:

  
  context mis-match in pipe_sampler_view_release()
  Mesa: User error: GL_INVALID_OPERATION in glFramebufferTexture2D
  g_ptr_array_free: assertion 'rarray' failed

  
  Comes up in the terminal BEFORE crash, while running configuration screen in "-T" mode, these 4 lines come up in the crash when enabling applications-menu:

  g_ptr_array_free: assertion 'rarray' failed
  g_strsplit: assertion 'string != NULL' failed
  g_once_init_leave: assertion 'result != 0' failed
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/1398238/+subscriptions


References