Debconf-communicate Input Output Error

AMI DLed 10.10 iso and burned it to cd. When I try to boot with cd, it starts up fine, I get the Ubuntu logo with rolling dots, but after a few mins it (initramfs) mount: mounting dev/loop0 on //filesystem.squashfs failed freezes (with logo still on screen). I have been running Ubuntu on this comp

Mounting Dev Loop0 On Filesystem Squashfs Failed No Such Device

for years. Any ideas? 73ckn797October 19th, 2010, 03:08 AMI DLed 10.10 iso and burned it to cd. When I try to

Mounting Dev Loop0 On Filesystem Squashfs Failed Invalid Argument

boot with cd, it starts up fine, I get the Ubuntu logo with rolling dots, but after a few mins it freezes (with logo still on screen). I have been running Ubuntu on this comp for

Linux Mint Cannot Mount /dev/loop0

years. Any ideas? Burn another CD? I have had to do that even after verifying md5sums and checking disk after a slow burn. dhavalbbhattOctober 19th, 2010, 03:38 AMBurn another CD? I have had to do that even after verifying md5sums and checking disk after a slow burn. Don't burn another CD without doing a couple of things - verify the MD5 of the ISO you downloaded and if that checks out, unetbootin then before installing the OS, do a "check the CD for errors" test. If that checks out as well, then download the DVD version of 10.10 and burn the DVD. Apparently, that worked for me. Dhaval 73ckn797October 19th, 2010, 03:51 AMDon't burn another CD without doing a couple of things - verify the MD5 of the ISO you downloaded and if that checks out, then before installing the OS, do a "check the CD for errors" test. If that checks out as well, then download the DVD version of 10.10 and burn the DVD. Apparently, that worked for me. Dhaval I was assuming those steps were already performed. I have not used a DVD download but may consider it due to the issues I have had with 10.10. brad1138October 20th, 2010, 04:56 AMNone of that worked, I can't even run the "check disc" option. no matter what I select from the initial menu, "Install" or "run from cd" or "check disc for errors" I get a lock up. I did hit Esc and saw this: (process:330): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (0) stdin:error 0 chroot: can't execute 'mktemp': Input/output error chroot: can't execute 'debconf-communicate': Input/output error etc, etc It will keep going on and list at

familiar with the basics of debian package construction. This manual begins by explaining two new files that are added to debian packages that use debconf. Then it explains how the debconf protocol works, and points you at some libraries download ubuntu that will let your programs speak the protocol. It discusses other maintainer scripts that debconf is typically used in: the postinst and postrm scripts. Then moves on to more advanced topics like shared debconf templates, debugging, and some common techniques and pitfalls of programming with debconf. It closes with a discussion of debconf's current shortcomings. THE CONFIG SCRIPT Debconf adds an additional maintainer script, the config script, to the set of maintainer scripts that can https://ubuntuforums.org/archive/index.php/t-1600358.html be in debian packages (the postinst, preinst, postrm, and prerm). The config script is responsible for asking any questions necessary to configure the package. Note: It is a little confusing that dpkg refers to running a package's postinst script as "configuring" the package, since a package that uses debconf is often fully pre-configured, by its config script, before the postinst ever runs. Oh well. Like the postinst, the config script is passed two parameters http://manpages.ubuntu.com/manpages/wily/man7/debconf-devel.7.html when it is run. The first tells what action is being performed, and the second is the version of the package that is currently installed. So, like in a postinst, you can use dpkg --compare-versions on $2 to make some behavior happen only on upgrade from a particular version of a package, and things like that. The config script can be run in one of three ways: 1 If a package is pre-configured, with dpkg-preconfigure, its config script is run, and is passed the parameters "configure", and installed-version. 2 When a package's postinst is run, debconf will try to run the config script then too, and it will be passed the same parameters it was passed when it is pre-configured. This is necessary because the package might not have been pre- configured, and the config script still needs to get a chance to run. See HACKS for details. 3 If a package is reconfigured, with dpkg-reconfigure, its config script it run, and is passed the parameters "reconfigure" and installed-version. Note that since a typical package install or upgrade using apt runs steps 1 and 2, the config script will typically be run twice. It should do nothing the second time (to ask questions twice in a row is annoying), and it should definitely be idempotent. Luckily, debconf avoids repeating questions by default,

says stopping bootlogd and then the line right before the upgrades line is stopping bluetooth. So it will not be logged. -- You received this bug notification because you are a member http://osdir.com/ml/ubuntu-bugs/2011-05/msg27389.html of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/434835 Title: unattended-upgrades hangs system http://www.fifi.org/doc/debconf-doc/tutorial.html on shutdown -- ubuntu-bugs mailing list ubuntu-bugs@xxxxxxxxxxxxxxxx https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs Thread at a glance: Previous Message by Date: [Bug 636711] Re: 10.10 can't mount squashfs file system I would like to give some information. I initially made a live CD on a CD-RW, and it didn't work or even mount. I remade a live mounting dev CD on a CD-R, and it did work, with all the files showing on the disk and everything. I found that the MD5 checksums match, so there is no problem there. Now, I have a Dell, and I initially just chose to boot from the CD on the startup screen. It goes through the boot process for a bit, and then ends up with two different mounting dev loop0 sets of messages so far. One of them is as shown in this thread. The other one also included many Input/Output errors, and it goes like this: Stdin: error 0 Bus error chroot : can't execute 'debconf-communicate' : Input/Output error /scrpts/casper-botton/IOadduser: .: line 20 can't open '/root/use/share/debconf/confmode' grep: /root/use/ii8n/Supported: I/O error chroot: can't execute /usr/sbin/locale-gen' : I/O error and it goes on like that for a bit, with many other lines Hope its some help with understanding whats going on. Then again, maybe it doesn't matter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636711 Title: 10.10 can't mount squashfs file system -- ubuntu-bugs mailing list ubuntu-bugs@xxxxxxxxxxxxxxxx https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs Next Message by Date: [Bug 362423] Re: "Failed to connect stream: Too large" I notice this bug the first time. But's really annoying because if this bug appears, the PC won't send any signal to the speakers. Here is what the terminal says, when i try to view a file in Totem: (totem:5787): Gtk-CRITICAL **: IA__gtk_tree_view_scroll_to_cell: assertion `tree_view->priv->tree != NULL' failed ** Message: Error: Failed to connect stream: Zu groà pulsesink.c(930): gst_pulseringbuffer_acquire (): /GstPlayBin2:play/GstPlaySink:playsink0/GstBin:abin/GstBin:audiosinkbin/GstGConfAudioSink:audio-sink/GstBin:bin2/GstAutoAudioSink:autoaudiosink1/GstPulseSink:autoaudiosink1-actual-sink-pulse -- You rece

ValidateCSS Whole document tree The Debconf Programmer's Tutorial The Debconf Programmer's Tutorial Joey Hess The Debian Project joeyh@debian.org Copyright © 1999 , 2000 by Joey Hess This text is copyright by the author under the terms of the BSD license, without the advertising clause. Table of Contents Introduction Getting started The Templates file The Config Script Modifying Existing Maintainer Scripts Finishing Up Testing Troubleshooting Advanced Topics A. Commands B. Question hierarchy Introduction This is a guide to using debconf with your packages, aimed at a Debian developer. So, what is debconf? To save you reading the specification (which is in Debian policy if you're interested), debconf is a backend database, with a frontend that talks to it and presents an interface to the user. There can be many different types of frontends, from plain text to a web frontend. The frontend also talks to a special config script in the control section of a debian package, and it can talk to postinst scripts and other scripts as well, all using a special protocol. These scripts tell the frontend what values they need from the database, and the frontend asks the user questions to get those values if they aren't set. Debconf should be used whenever your package needs to output something to the user, or ask a question. I'll assume you already have a package that does this and you want to convert it to use debconf. Getting started First, your package must depend on debconf (or pre-depend on it if it uses debconf in its preinst[1]). This is necessary since debconf isn't essential. The first thing to do is look at your postinst, plus any program your postinst calls (like a "packageconfig" program), plus your preinst, and even your prerm and postrm. Take note of all output they can generate and all input they prompt the user for. All this output and input must be eliminated for your package to use debconf. (Output to stderr can be left as is.) Note: If your preinst uses debconf, you must make your package Pre-Depend on debconf (>= 0.2.17). For example, a hypothetical package "foo" has the following postinst: #!/bin/sh -e echo -n "Do you like debian? [yn] " read like c