Hi,
what items do you have in the systray ? did it crash when you hover any of
them with the mouse ?
I think the best is to reproduce the bug and catch it with gdb.
2013/5/15 Matthieu Baerts matt...@gmail.com
If this was in fact corrupted data from D-Bus or GTK, would there be
any way to
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
Hello and thank you for this bug report!
Is it maybe possible to give us a backtrace of this crash with GDB? It's
easy because it's explained there: http://glx-
dock.org/ww_page.php?p=dddlang=en
PS: I see that this bug is assigned to you, that means: you should be
the guy who will try to fix
Interesting, I downloaded the source to work on this bug, which seems to
have triggered an update notification to show up in the notification
area. After this, I haven't been able to reproduce the crash. I'll play
around with it a bit though, and see what I can come up with.
--
You received this
Oh great, I just reassigned this bug to you ;)
** Changed in: cairo-dock (Ubuntu)
Assignee: (unassigned) = Stephen Kraemer (straemer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179297
Thanks. Although I'm having no such luck reproducing this crash now. Is
there a way to create a notification for debugging purposes? I suspect
that this might be caused by a notification coming up when the dock
isn't launched or something like that... Although that seems a bit
peculiar since it
Is there a way to create a notification for debugging purposes?
Yes, you can easily create an 'indicator' applet:
https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators#Python_version
I suspect that this might be caused by a notification coming up when
the dock isn't launched or
Ya, so creating the indicator when it was closed seems to be fine. If
this was in fact corrupted data from D-Bus or GTK, would there be any
way to verify this? A more likely cause would probably be that a corrupt
indicator was created, or something along those lines.
--
You received this bug
