> Sorry, it seems I forgot to add "@fabounet" :-)
>
> *@fabounet*: Any idea of what has changed between 3.3.2 (Trusty's
> version, with a few patches[1]) and 3.3.99 to cause this crash? :-)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1360681
>
> Title:
> Cairo-Dock 3.3.99-rc1: crash at startup
>
> Status in Cairo-Dock : Core:
> New
>
> Bug description:
> Hey guys!
>
> Welp, today I had a bunch of upgrades for my computer, so I went ahead
> and upgraded them. Since it was a while since the last reboot and
> there was a ton of X-sever updates I decided to go ahead and just
> reboot my computer.
>
> Cario-dock never ran again, however my startup apps did, so I used one
> to open a terminal and run cairo dock from the terminal.
>
> Not sure what happened really, any suggestion would be greatly
> appreciated.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cairo-dock-core/+bug/1360681/+subscriptions
>
I'll take a look, most probably the "iNbRows == -1" in the gdb backtrace is
the reason.
2014-08-25 15:24 GMT+02:00 Matthieu Baerts <email address hidden>:
> Sorry, it seems I forgot to add "@fabounet" :-) /bugs.launchpad .net/bugs/ 1360681 /bugs.launchpad .net/cairo- dock-core/ +bug/1360681/ +subscriptions
>
> *@fabounet*: Any idea of what has changed between 3.3.2 (Trusty's
> version, with a few patches[1]) and 3.3.99 to cause this crash? :-)
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> Cairo-Dock 3.3.99-rc1: crash at startup
>
> Status in Cairo-Dock : Core:
> New
>
> Bug description:
> Hey guys!
>
> Welp, today I had a bunch of upgrades for my computer, so I went ahead
> and upgraded them. Since it was a while since the last reboot and
> there was a ton of X-sever updates I decided to go ahead and just
> reboot my computer.
>
> Cario-dock never ran again, however my startup apps did, so I used one
> to open a terminal and run cairo dock from the terminal.
>
> Not sure what happened really, any suggestion would be greatly
> appreciated.
>
> To manage notifications about this bug go to:
> https:/
>