Bug#776151: Installation bug in Expert mode
Package: installation-reports Boot method: CD Image version: Jessie Beta 2 NetInstall Date: 2015-01-24 Machine: Mac Mini Server Mid 2011 Processor: Intel Core 2 Duo Memory: 4 GB Partitions: none yet, 2 brand new 1 TB WD Red HDs Output of lspci -knn (or lspci -nn): N/A Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Rest N/A, see below. Comments/Problems: The first menu boots without problems and the USB keyboard works. When selecting "Advanced - Expert Install", the keyboard no longer works when the first selection menu appears, no language selection nor anything else works then. When "Install" is selected on the first menu, the keyboard works correctly. Repeatable: Always. I was not able to enter Expert Install mode. When installing via default, the Mac Mini Server could be setup without any further issues. HTH, ändu -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c3c157.8050...@worldwideweber.ch
Bug#744865: Add check and warning for unetbootin
Control: tag -1 +patch
On Wed, Jan 21, 2015 at 03:46:20PM +, Steve McIntyre wrote:
>So, some progress on this front. I've filed a bug against unetbootin
>itself to ask for warnings "Don't use this for Debian CD images"
>(#775689) and there has been some discussion there.
>
>I've now tried the current stable and unstable versions of unetbootin
>myself with the latest Jessie d-i RC1 amd64 netinst CD and could not
>get it to work at all usefully. *sigh* I've no idea how people ever
>manage to get unetbootin to work for them - documentation is
>non-existent.
>
>What I *do* have now is some information about the contents of the
>resulting USB stick, so I can add a checks in d-i for various files
>and trigger a warning something like
Here's my patch. Not sure I can test it 100%, as I've yet to get
unetbootin to reliably *get* to this stage for me! But I've made a
local image with filenames that match these and it triggered
correctly.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane
diff --git a/debian/cdrom-detect.postinst b/debian/cdrom-detect.postinst
index 3446a06..6bf2454 100755
--- a/debian/cdrom-detect.postinst
+++ b/debian/cdrom-detect.postinst
@@ -223,6 +223,22 @@ while true; do
fi
done
+# Check for unetbootin files
+UNETBOOTIN_FILES="ubnfilel.txt ubninit ubnkern ubnpathl.txt"
+UNETBOOTIN_DETECTED=0
+for file in ${UNETBOOTIN_FILES}; do
+ if [ -f /cdrom/$file ] ; then
+ UNETBOOTIN_DETECTED=1
+ break
+ fi
+done
+
+# If we found any, warn the user
+if [ $UNETBOOTIN_DETECTED = 1 ]; then
+ db_input critical cdrom-detect/unetbootin_detected || [ $? -eq 30 ]
+ db_go
+fi
+
# Get all the pool directories into the dentry cache, to cut down on seek
# times.
poolcount="$(set -- /cdrom/pool/*/*; echo $#)"
diff --git a/debian/cdrom-detect.templates b/debian/cdrom-detect.templates
index 3db18bc..96253af 100644
--- a/debian/cdrom-detect.templates
+++ b/debian/cdrom-detect.templates
@@ -94,6 +94,19 @@ _Description: CD-ROM detected
The CD-ROM autodetection was successful. A CD-ROM drive has been found and it
currently contains the CD ${cdname}. The installation will now continue.
+Template: cdrom-detect/unetbootin_detected
+Type: note
+# :sl2:
+_Description: UNetbootin media detected
+ It appears that your installation disk was generated using
+ UNetbootin. UNetbootin is regularly linked with difficult or
+ unreproducible problem reports from Debian Installer users; if you
+ have problems using this installation disk, please try your
+ installation again without using UNetbootin before reporting issues.
+ .
+ The installation guide contains more information on how to create a
+ USB installation disk directly without UNetbootin.
+
Template: cdrom-detect/wrong-cd
Type: error
# :sl2:
diff --git a/debian/changelog b/debian/changelog
index 22c2e1d..a4b037a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+cdrom-detect (1.49) UNRELEASED; urgency=medium
+
+ [ Steve McIntyre ]
+ * Add checks for UNetbootin media at cdrom mount time. If we detect it,
+warn the user about potential problems. Closes: #744865
+
+ -- Steve McIntyre <93...@debian.org> Fri, 23 Jan 2015 01:03:28 +0100
+
cdrom-detect (1.48) unstable; urgency=low
[ Updated translations ]
Processed: Re: Bug#744865: Add check and warning for unetbootin
Processing control commands: > tag -1 +patch Bug #744865 [debian-installer] Add check and warning for unetbootin Added tag(s) patch. -- 744865: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b744865.142212655623954.transcr...@bugs.debian.org
Bug#744865: Add check and warning for unetbootin
Hi Steve, Regarding your unetbootin patch: > +Template: cdrom-detect/unetbootin_detected > +Type: note > +# :sl2: > +_Description: UNetbootin media detected > + It appears that your installation disk was generated using > + UNetbootin. UNetbootin is regularly linked with difficult or > + unreproducible problem reports from Debian Installer users; if you > + have problems using this installation disk, please try your > + installation again without using UNetbootin before reporting issues. > + . > + The installation guide contains more information on how to create a > + USB installation disk directly without UNetbootin. Maybe I'm wrong, but since unetbootin is a tool to create a bootable usb-stick, better mention "installation stick" oder "installation medium" instead of "installation disk"? Holger -- Created with Sylpheed 3.2.0 under D E B I A N L I N U X 7 . 0 W H E E Z Y ! Registered Linux User #311290 - https://linuxcounter.net/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150124211849.8582ae0dee5e7fd4688b2...@wansing-online.de
Bug#744865: Add check and warning for unetbootin
On Sat, Jan 24, 2015 at 09:18:49PM +0100, Holger Wansing wrote: >Hi Steve, > >Regarding your unetbootin patch: >> +Template: cdrom-detect/unetbootin_detected >> +Type: note >> +# :sl2: >> +_Description: UNetbootin media detected >> + It appears that your installation disk was generated using > >> + UNetbootin. UNetbootin is regularly linked with difficult or >> + unreproducible problem reports from Debian Installer users; if you >> + have problems using this installation disk, please try your > >> + installation again without using UNetbootin before reporting issues. >> + . >> + The installation guide contains more information on how to create a >> + USB installation disk directly without UNetbootin. > > >Maybe I'm wrong, but since unetbootin is a tool to create a bootable >usb-stick, better mention "installation stick" oder "installation medium" >instead of "installation disk"? Yeah, good point. :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com "When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150124235135.ga5...@einval.com
Jessie wkly build - installer fails on acer 720 chromebook
acer 720 chromebook in development mode seabios debian-testing-amd64-xfce-CD-1.iso wkly build 1/19/2015 install screen appears, click on either graphical or non-graphical install - screen flashes then goes back to seabios screen 1) this usb build works on macbook 2) debian wheezy installs on this machine 3) fedora 20 installs on this machine 4) fedora 21 flashes and does not work thus sounds like something related to newer kernel or packages suspected it neeeded a boot line such as mem=1048M but this does not work - tried many different mem settings, nothing worked -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54c4470c.1060...@gmail.com
Bug#776101: aptitude: hangs forever on 'setting up console-setup (1.116)'
On Sat, 24 Jan 2015 00:38:29 +0100, Axel Beckert wrote: > Control: reassign -1 console-setup 0.116 > > Hi, > > Gordon Morehouse wrote: > > running 'aptitude upgrade' followed by 'aptitude update' > > You mean "running 'aptitude update' followed by 'aptitude upgrade'", > don't you? Ah, yes, indeed. :) > > on a Debian testing system hangs > > How long did you approximately wait? I was doing other things, so more than 20 minutes. > > after similar output from aptitude: > > > > Installing new version of config file > > /etc/console-setup/compose.ISO-8859-3.inc ... > > Installing new version of config file > > /etc/console-setup/compose.ISO-8859-4.inc ... > > Installing new version of config file > > /etc/console-setup/compose.ISO-8859-7.inc ... > > Installing new version of config file > > /etc/console-setup/compose.ISO-8859-9.inc ... > > This output is not from aptitude but either from dpkg or ucf. > > > Setting up console-setup (1.116) ... > > This is output from dpkg, announcing that it will now run > console-setup's postinst script. Okay. Posted to wrong package due to lack of knowledge :) > > 'top' shows aptitude taking about 3-4% CPU but it is stuck. > > Because aptitude is probably not the one which is working at that > time. The one which should do something is either a postinst script > from some to-be-installed package or some trigger. But dpkg would have > announce triggers. As well as aptitude is mentioning that it's > re-reading it's database. > > Did top show any other child process of aptitude? I didn't look into the process tree, but the system appeared completely idle (or as idle as it can get), with 'top' and 'aptitude' the top users of CPU time. > > Ctrl-C is not effective. > > Ok. > > > Kill with SIGTERM does stop the process while breaking terminal > > echo. > > Sure, because it doesn't leave aptitude a chance to do so. IMHO > expected behaviour. > > > It leaves the aptitude /var lockfile dirty. > > Dito. > > > Running 'sudo dpkg --configure -a' has a couple errors about > > /var/cache/debconf/config.dat being locked as well. > > This sounds as if the aptitude including its children processes were > killed while debconf tried to ask you a question or -- more likely -- > generate a config file. If it takes 20+ minutes on an Athlon64, there should probably be a status report...? > I'm quite sure this is no issue with aptitude at all but likely with > the postinst script of a to-be-installed package. I currently assume > it's console-setup, also because it's a heavy debconf user. Hence > reassigning. I managed to reboot and then re-run aptitude and it completed without complaint. Thanks, -Gordon M. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1yffcb-0001rr...@rmm6prod02.runbox.com
Bug#776186: busybox: CVE-2014-9645: modprobe wrongly accepts paths as module names
Source: busybox Version: 1:1.20.0-7 Severity: normal Tags: security patch upstream fixed-upstream Hi, the following vulnerability was published for busybox. CVE-2014-9645[0]: modprobe wrongly accepts paths as module names Upstream report is at [1] with fix at [2]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2014-9645 [1] https://bugs.busybox.net/show_bug.cgi?id=7652 [2] http://git.busybox.net/busybox/commit/?id=4e314faa0aecb66717418e9a47a4451aec59262b Regards, Salvatore -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150125070417.17788.49948.report...@lorien.valinor.li
