cairo-dock random crash, no self-restart

Hello !

Thanks to have reported this strange bug !

Can you give us the output of this command (from a terminal):
  $ grep modules ~/.config/cairo-dock/current_theme/cairo-dock.conf

Can you try without the AlsaMixer applet ?

If it still happens, can you try with the default settings
  $ mv ~/.config/cairo-dock/current_theme/ ~/.config/cairo-dock/current_theme.bak/

If you no longer have this bug, can you send us an archive of this repertory ? (~/.config/cairo-dock/current_theme.bak/)

Thanks for your help !

"cairo_dock_launch_command_full (/usr/bin/jockey-gtk , (null))
Assertion 'pthread_setspecific(t->key, userdata) == 0' failed at pulsecore/thread-posix.c:196, function pa_tls_set(). Aborting."

Seems like a bug in pulse-audio ...
is jockey-gtk related to the sound ?
it would be useful to report it at the pulse-audio project.
I don't think it's a bug inside Cairo-Dock, since there is no thread in the Alsamixer applet, we merely call the same function from libalsa each second (which I guess call pulse-audio).

@Matthieu
I am the one supposed to thank, also for your very fast feedback.
I didn't reply before because I was consistently doing the tests you asked for. So:

1. ~$ grep modules ~/.config/cairo-dock/current_theme/cairo-dock.conf
modules=switcher;System Monitor;Quick Browser;shortcuts;Clipper;illusion;logout;weather;showDesktop;PowerManager;Note-Taking;clock;Animated icons;dustbin;GMenu;icon effects;netspeed

2. I don't have the AlsaMixer applet selected

3. ~$ mv ~/.config/cairo-dock/current_theme/ ~/.config/cairo-dock/current_theme.bak/
Let CD reinstall default theme and operated for a couple of hours with no problems.
Before going to bed, reinstated my theme from .bak, reopened CD and after a couple of minutes got another crash.
This morning got back to default theme and have been operating since then without a single problem.
So, apparently, my theme is the culprit. I'm attaching it for your information.
Revision 2.1.3-5 just showed-up on my update manager but I hold it back in case you need some more tests, look forward to your agreement to install it.

@Fabounet
Hello; I don't know what jockey-gtk is, should I?
Am I supposed to reply to your post?

Sorry, forgot the attachment.

oh, I thought Alsamixer was involved, but it's obviously not the case.
jokey-gtk seems to be related with drivers management, especially graphic ones.
I don't see the direct link with it, but according to the output, it may be a track.
especially considering your "PS".
thanks for providing your theme, I'm running it now, so far nothing bad happened. I think it would be relevant to link this bug with jokey-gtk.
by the way is it normal that you have 2 instances of system-monitor and that the dock doesn't stick to the screen border ?

when you say the dock doesn't self-restart, do you mean the process doesn't exist anymore, or is it trying to launch itself in loop ?
(you can see that with a "ps -ef | grep cairo-dock")

Can you also try without 'weather" applet ?

thinking of it, it may be a problem with pbuffers (again)
what graphic card do you have ?
could you try without any gauge (system-monitor, netspeed, etc) ?
and also with cairo-dock -O instead of cairo-dock -o
Thanks.

2010/2/24 Matthieu Baerts <email address hidden>

> Can you also try without 'weather" applet ?
>
> --
> cairo-dock random crash, no self-restart
> https://bugs.launchpad.net/bugs/526664
> You received this bug notification because you are a member of Cairo-
> Dock Team, which is subscribed to Cairo-Dock Core.
>
> Status in Cairo-Dock : Core: Incomplete
>
> Bug description:
> I love CD, installed it a few months ago and it increased my productivity a
> lot.
> Suddenly this problem started a few days ago, CD suddenly disappears and
> doesn't restart, process monitor doesn't show it running.
> This happens randomly, cannot reproduce it, but usually when I click on an
> option of the main menu (penguin applet).
> The present debug session, listed below, stopped when I clicked the
> Application->Administration->update manager
> I run Ubuntu 9.10, all upgrades done with Gnome / Compiz
> Laptop is Asus A8Js, nvidia Go 7700, nvidia driver 195.36.03
> CD version 2.1.3-4
>
> debug :
> (cairo-dock-draw-opengl.c:cairo_dock_create_texture_from_surface:723)
> + texture 99 generee (9de1c78, 57x23)
> message : (cairo-dock-menu.c:_cairo_dock_delete_menu:1697)
> on force a quitter
> debug : (cairo-dock-callbacks.c:cairo_dock_launch_command_full:949)
> cairo_dock_launch_command_full (/usr/bin/jockey-gtk , (null))
> Assertion 'pthread_setspecific(t->key, userdata) == 0' failed at
> pulsecore/thread-posix.c:196, function pa_tls_set(). Aborting.
> warning : (cairo-dock.c:_cairo_dock_intercept_signal:181)
> Cairo-Dock has crashed (sig 6).
> It will be restarted now (cairo-dock -o -l debug).
> Feel free to report this bug on glx-dock.org to help improving the dock !
> info on the system :
> Assertion 'pthread_setspecific(t->key, userdata) == 0' failed at
> pulsecore/thread-posix.c:196, function pa_tls_set(). Aborting.
> Linux albatroz 2.6.31-19-generic #56-Ubuntu SMP Thu Jan 28 01:26:53 UTC
> 2010 i686 GNU/Linux
> Aborted
> :~$
>
> P.S. It just happened again when I clicked the menu option of nvidia
> settings to look at the graphics card type
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~cairo-dock-team<https://launchpad.net/%7Ecairo-dock-team>
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~cairo-dock-team<https://launchpad.net/%7Ecairo-dock-team>
> More help : https://help.launchpad.net/ListHelp
>

@Fabounet
So, just saw your post, reinstated my theme and I'm waiting for it to happen.

As far as I know, I only have one instance of system-monitor although I use widget layer and a screenlet sysmonitor is running there. What I do have is three instances of clock running, one on the dock and two on the widget, for different time-zones.

Thank you for noticing that I had 8 pixels wasted space between the dock and the screen edge, it was certainly a misconfiguration that I never noticed.

Concerning the process, I looked

@Matthieu
Do you want me to try what you say now, or wait for a crash to tell Fabounet whether the process is running or not?

Never mind, just happened again after I clicked Process Monitor. I can now reply to Fabounet
Before crash:
~$ ps -ef | grep cairo-dock
myuser 5891 1 3 19:14 ? 00:00:20 cairo-dock -o
myuser 7444 7389 0 19:23 pts/1 00:00:00 grep cairo-dock
After crash:
~$ ps -ef | grep cairo-dock
myuser 8237 7389 0 19:33 pts/1 00:00:00 grep cairo-dock

Looking forward to instructions

@Mathieu
GeForce Go 7700, VBIOS 05.73.22.50.a5, Memory 512 MB

@Mathieu
Reinstated my theme, removed system monitor applets (Fabounet was right, there were two, one on the widget layer); crashed after some time, although longer than usual.

Again reinstated my theme, removed weather applet; has been working normally until now, more than 3 hours with a lot of menu clicking.

I guess your hunch was right, thank you.

Can I install 2.1.3-5 now? I've been holding it back.

Installed 2.1.3-5, worked for several hours without the weather applet with no crash.

CD configure, selected weather applet. Crashed as soon as I clicked the icon to configure the applet.

lp:cairo-dock-plug-ins : (1523 by fabounet) fixed the bug with weather that broke libxml's internal memory, preventing the VFS from working in all the dock

I don't know if here is a good place to report a similar bug (tell me if it's not), however, Cairo-Dock crashed and restarted after Weather applet tried to get weather information from Internet while all my band width was used up by synaptic. I got this message in xsession-errors:

[1;38mwarning :  (/home/pedram/Desktop/tmp/cairo-dock-2.3.1-bzr20110514/src/cairo-dock.c:_cairo_dock_intercept_signal:271) 
  Cairo-Dock has crashed (sig 11).
It will be restarted now (cairo-dock -o).
Feel free to report this bug on glx-dock.org to help improving the dock !
info on the system :
Linux debian 2.6.38-pf8 #1 SMP PREEMPT Wed May 11 03:02:34 IRDT 2011 x86_64 GNU/Linux

I use the latest Bazaar version and it's the first time I see such a crash. I'm not sure if it's related to the band width being used up by another process.

@Tsu Jan,

Yes can you open a new bug report because this one seems fixed.
Don't hesitate to join a backtrace if it's a bug. About the backtrace, simply have a look to this wiki page: http://wiki.glx-dock.org/?p=ddd