Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I got some power issues at home and got a bunch of files in my computer corrupted. I could fix most of them, but one that's bugging me is a debconf script. Everytime I try to install something I get this:

Configuring php5-curl (5.4.9-ubuntu2.4) ...
Attempt to access disallowed key '�png' in a restricted hash at /usr/share/perl5/Debconf/Config.pm line 43, <DEBCONF_CONFIG> chunk 1.
dpkg: error processing php5-curl (--configure):
 sub-process script post-installation returned error state code 255

I searched a little bit that script (Config.pm) but found nothing strange, what makes me think it's something it reads or includes - but my perl knowledge is null and I have no idea how to fix that manually.

Is it possible to reinstall debconf and make that work again?

share|improve this question

1 Answer 1

up vote 1 down vote accepted

I tried to download a random deb to install, and the graphical interface said there could be a error with my sources.list. I grep'd the /etc/apt folder instead of the perl scripts and found a PNG disguised as a sources file in sources.list.d. In the end, the problem wasn't the scripts but what they read from :P

Also, there was another of those bad PNGs itself in /etc/debconf.conf, which was probably the root of all problems. I found that by using the same method of outputting the buggy file - but in a healthy machine, so I had text strings to grep, found the complete file and copied it on top of that PNG.

share|improve this answer
    
well, that's interesting, because dpkg does not need any apt configs. –  user224465 Apr 5 at 11:57
    
actually, I still found another png trash. fiddling with perl I could regenerate the image and found it to be the linux mint logo. hahaha now I'm working out a way to find where that image is located :/ –  Igoru Apr 5 at 15:58
    
I just wonder how this is possible :-) –  user224465 Apr 5 at 17:03
    
when you discover, please, tell me! hahaha there's also some trash in some file vi reads before opening, and the same with bash. see: i.imgur.com/RxeHw8x.png & i.imgur.com/HE81ZFg.png –  Igoru Apr 6 at 2:51
    
edited the answer to explain where the second PNG were, @bersch ;) –  Igoru Apr 6 at 6:16

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.