> If this was in fact corrupted data from D-Bus or GTK, would there be
any way to verify this?
Yes I guess it's easy to verify this with GDB. (and with dbus-monitor
and 'cairo-dock -l debug' to have more debugs info)
> A more likely cause would probably be that a corrupt indicator was
created, or something along those lines.
But I'm not sure that it's easy to do (I hope that it's not easy to create a
corrupted indicator :) ).
If it's no longer possible to reproduce this crash, we'll have to check the
code and find where it can crash if the data are corrupted... not so easy and
maybe too much work if we can't reproduce it...
@fabounet: any idea? :)
I'm going to modify the status to 'Invalid' but feel free to re-open
this bug if you've this crash again. (and of course feel free to report
any other bug or patch ;) )
** Changed in: cairo-dock (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179297
Title:
Cairo Dock crashes on Notification Area Mouse-Over
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/1179297/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
