Your message dated Sun, 18 Feb 2007 22:51:56 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Solved
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: splashy
Version: 0.1.8.1-3.1
Severity: normal

Hi,

for some reason, splashy_config produces a config file which in turn
causes error messages from the xml parser:

denkbrett:/etc/splashy# rm config.xml 
denkbrett:/etc/splashy# dpkg -i --force-confmiss 
/tmp/splashy_0.1.8.1-3.1_i386.deb > /dev/null

Configuration file `/etc/splashy/config.xml', does not exist on system.
Installing new config file as you request.
denkbrett:/etc/splashy# splashy_config --set-theme debiansplashy
>Set theme as: debiansplashy          [ DONE ]
denkbrett:/etc/splashy# splashy_config --set-theme debiansplashy

** (process:4010): CRITICAL **: xml_parser_text_handler: assertion `text_len > 
0' failed

** (splashy_config:4010): CRITICAL **: _xml_parser_compare_element: assertion 
`_node->got_text == TRUE' failed
>Set theme as: debiansplashy
** (splashy_config:4010): CRITICAL **: _xml_parser_compare_element: assertion 
`_node->got_text == TRUE' failed

** (splashy_config:4010): CRITICAL **: _xml_parser_compare_element: assertion 
`_node->got_text == TRUE' failed

** (splashy_config:4010): CRITICAL **: _xml_parser_compare_element: assertion 
`_node->got_text == TRUE' failed
          [ DONE ]
denkbrett:/etc/splashy# 

This is the diff of the original file and the one which was
created by splashy_config:

denkbrett:/etc/splashy# diff /tmp/config.xml config.xml 
7c7
<     <current_theme>default</current_theme>
---
>     <current_theme>debiansplashy</current_theme>

The diff is the same after the first and the second call to splashy_config.


Cheers,

Wolf


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.9
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages splashy depends on:
ii  libc6                        2.3.6.ds1-6 GNU C Library: Shared libraries
ii  libgcc1                      1:4.1.1-17  GCC support library

Versions of packages splashy recommends:
ii  lsb-base                      3.1-17     Linux Standard Base 3.1 init scrip

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi Tim,

Tim Dijkstra wrote:

> Can you check if this bug is solved in the meantime?

I cannot reproduce this anymore, I'm closing this bug.

Thanks, Wolf

-- 
Büroschimpfwort des Tages: Maustouretti - Mitarbeiter, die am PC immer wild auf 
der Maus rumklicken und sich dann bald so verklickt haben, dass nur noch ein 
Systemneustart helfen kann. (Georg-Thomas Bau)

--- End Message ---

Reply via email to