Errors with none utf-8 strings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Diodon |
Fix Released
|
High
|
Oliver Sauder |
Bug Description
Hi,
I use Natty on eee pc with Unity-2d. After about week of good work diodon doesn´t start and doesn´t appear on panel. Submenu on unity launchbar is empty. I can run diodon as superuser and it works well (but menu of sidebar of unity-2d still empty).
When the app starts in terminal I see this:
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): libunity-DEBUG: unity-place.
(diodon:2317): dee-CRITICAL **: clone_leader: assertion `self->
(diodon:2317): dee-CRITICAL **: clone_leader: assertion `self->
(diodon:2317): dee-CRITICAL **: clone_leader: assertion `dee_model_
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): dee-CRITICAL **: Trying to build a row with a NULL member on position 4. This is probably an error in an application using libdee
(diodon:2317): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): dee-CRITICAL **: dee_sequence_
(diodon:2317): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): dee-CRITICAL **: dee_sequence_
(diodon:2317): dee-CRITICAL **: Internal error: Column 4 in DeeSequenceMode
(diodon:2317): dee-CRITICAL **: Internal error: Column 5 in DeeSequenceMode
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
(diodon:2317): GLib-CRITICAL **: g_variant_
(diodon:2317): GLib-CRITICAL **: g_variant_
Segmentation failed
Thanks
Pavel
Related branches
Changed in diodon: | |
milestone: | none → 0.4.1 |
Changed in diodon: | |
milestone: | 0.4.1 → 0.5.0 |
This is not normal. Therefore I have opened up this bug report.
For better investigation please attach your diodon history located in ~/.local/ share/diodon/ storage. xml