Garbage written to main configuration file when overwriting theme file

[nick]

 ============================================================================
        Cairo-Dock version : 3.4.0
        Compiled date : Oct 17 2014 09:05:35
        Built with GTK : 3.14
        Running with OpenGL: 1
 ============================================================================

This bug has been discovered when using KDE 4.14.2.

I am seeing an issue where overwriting an existing theme is causing garbage to be written to the main dock configuration file. This appears to occur with all types of themes. It looks like some form of memory corruption.

== STEPS TO REPRODUCE ==

1. Modify the existing theme and save the theme to a new name e.g. foo
2. Change the theme again by adding or removing a component and save the theme by the same name i.e. foo

Any attempt to apply this theme will cause the dock to disappear owing to a corruption of cairo-dock.conf.

The corruption differs each time (sometimes extra characters are dumped at the end of the file) but causes the key file to become invalid. For example, when using the default theme, the overwrite causes the following corruption in cairo-dock.conf:

#P+ Text font:
font=Normal
e

As you can see an <e> character has been written to the file.

[Fabounet (fabounet03)]

Hi,
thanks for the clear bug description.
However I'm unable to reproduce it (on Gnome).
Is the config file in the saved theme ok (in
~/.config/cairo-dock/themes/<name>/cairo-dock.conf) ?

2014-11-10 16:08 GMT+01:00 nick <email address hidden>:

> Public bug reported:
>
>
> ============================================================================
> Cairo-Dock version : 3.4.0
> Compiled date : Oct 17 2014 09:05:35
> Built with GTK : 3.14
> Running with OpenGL: 1
>
> ============================================================================
>
> This bug has been discovered when using KDE 4.14.2.
>
> I am seeing an issue where overwriting an existing theme is causing
> garbage to be written to the main dock configuration file. This appears
> to occur with all types of themes. It looks like some form of memory
> corruption.
>
> == STEPS TO REPRODUCE ==
>
> 1. Modify the existing theme and save the theme to a new name e.g. foo
> 2. Change the theme again by adding or removing a component and save the
> theme by the same name i.e. foo
>
> Any attempt to apply this theme will cause the dock to disappear owing
> to a corruption of cairo-dock.conf.
>
> The corruption differs each time (sometimes extra characters are dumped
> at the end of the file) but causes the key file to become invalid. For
> example, when using the default theme, the overwrite causes the
> following corruption in cairo-dock.conf:
>
> #P+ Text font:
> font=Normal
> e
>
> As you can see an <e> character has been written to the file.
>
> ** Affects: cairo-dock-core
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are a member of Cairo-
> Dock Devs, which is subscribed to Cairo-Dock Core.
> https://bugs.launchpad.net/bugs/1391199
>
> Title:
> Garbage written to main configuration file when overwriting theme file
>
> Status in Cairo-Dock : Core:
> New
>
> Bug description:
>
> ============================================================================
> Cairo-Dock version : 3.4.0
> Compiled date : Oct 17 2014 09:05:35
> Built with GTK : 3.14
> Running with OpenGL: 1
>
> ============================================================================
>
> This bug has been discovered when using KDE 4.14.2.
>
> I am seeing an issue where overwriting an existing theme is causing
> garbage to be written to the main dock configuration file. This
> appears to occur with all types of themes. It looks like some form of
> memory corruption.
>
> == STEPS TO REPRODUCE ==
>
> 1. Modify the existing theme and save the theme to a new name e.g. foo
> 2. Change the theme again by adding or removing a component and save the
> theme by the same name i.e. foo
>
> Any attempt to apply this theme will cause the dock to disappear owing
> to a corruption of cairo-dock.conf.
>
> The corruption differs each time (sometimes extra characters are
> dumped at the end of the file) but causes the key file to become
> invalid. For example, when using the default theme, the overwrite
> causes the following corruption in cairo-dock.c...

[nick (thedarkstuff)]

Sorry for the late reply. I've actually rebuild my computer and have been out of the loop. The base configuration in the themes directory is corrupted as well as the conf file in the current_theme directory. (I did a diff on the files and they are identical). I am up and running again with KDE so will do some further investigation.

[Launchpad Janitor (janitor)]

[Expired for Cairo-Dock Core because there has been no activity for 60 days.]