Bug#646704: Bug severity is too high
Quoting Christian PERRIER (bubu...@debian.org): > release and that it's not planned to happen in 2012, I'll be fine with s/2012/2014 signature.asc Description: Digital signature
Bug#646704: Bug severity is too high
Quoting Daniel Baumann (daniel.baum...@progress-technologies.net): > since you put yourself into uploaders of live-installer some time ago, > maybe you want to look at it yourself too? You know the reasons for this: be able to do l10n upload when needed without them to be considered NMUs. That's it and mostly it and, no, I can't (understand I don't have the skills) try finding a fix. > > > Sorry, I'm still deeply convinced that this issue is mostly a case > > that doesn't deserve an RC severity. I'll downgrade this bug again > > in 4 weeks if nothing happened in the meantime. > > should that be the case, i'll restore the original severity of course. Well, as long as you remember that we're currently working on a release and that it's not planned to happen in 2012, I'll be fine with that. But, still, this bug is not release critical as it doesn't fit the definition of "serious". signature.asc Description: Digital signature
Re: Bug#695328: [testing/wheezy] UEFI installed system fails to boot
On 2012-12-29T19:25:59-0800, Kenyon Ralph wrote: > I have a feeling that using grub2 2.00 (like Ubuntu uses) would work. > I'll try to build an installer including that if I can figure it out. Instead of building a new installer, I just installed grub2 2.00-8 from experimental in rescue mode. System still did not boot, so I don't know what to try now. It would be nice if we could figure out why Ubuntu 12.10 installs and boots in EFI mode, and bring those changes into the Debian packages. -- Kenyon Ralph signature.asc Description: Digital signature
Re: Bug#695328: [testing/wheezy] UEFI installed system fails to boot
On 2012-12-29T16:28:59-0800, Kenyon Ralph wrote: > This is probably part of the problem: on the installed system, > /boot/efi is empty. Rerunning grub-install doesn't change that. Actually, /boot/efi contains EFI/debian/grubx64.efi. For some reason, rescue mode was showing that /boot/efi was mounted, but it actually wasn't. umounting it and then mount -va properly mounted /boot/efi. Then grub-install /dev/sda seems to have created a correct EFI boot entry: BootCurrent: 0003 Timeout: 1 seconds BootOrder: ,0001,0002,0003 Boot* debian HD(1,800,f3800,f8636d01-62af-4d23-9ab6-5b22c5ffd5e6)File(\EFI\debian\grubx64.efi) Boot0001* SATA : PORT 6G 0 : INTEL SSDSC2CW120A3 : PART 0 : Boot Drive BIOS(2,0,00)AMBO Boot0002* USB : 0.00 : PART 0 : Boot Drive BIOS(2,0,00)AMBO Boot0003* UEFI : USB : 0.00 : PART 1 : OS Bootloader ACPI(a0341d0,0)PCI(1d,0)USB(1,0)USB(1,0)HD(2,6f800,380,13a64ed1)AMBO But the system still doesn't boot. I retried installation using the 2012-12-29T22:11 build of debian-testing-amd64-netinst.iso, followed by rescue mode, umount /boot/efi, mount -va, grub-install /dev/sda, resulting in a good Boot line like above. System still doesn't boot. Strangely, booting again into rescue mode, the Boot line reverts back to Vendor(99e275e7-75a0-4b37-a2e6-c5385e6c00cb,), even after mounting /boot/efi properly. I have a feeling that using grub2 2.00 (like Ubuntu uses) would work. I'll try to build an installer including that if I can figure it out. -- Kenyon Ralph signature.asc Description: Digital signature
Re: Re: building and testing d-i with jenkins
Hi Holger, On 5 Dec 2012 21:19:00, Holger Levsen wrote: > there is now > http://jenkins.debian.net/view/cd-tests/job/cd-test_wheezy_lxde/ > doing a g-i installation of lxde desktop and producing a nice video This is great! But what happened to that link, it is a 404 already? I see that wheezy d-i is at least being tested regularly for the purposes of Debian Edu so that's good. I noticed what looks like some false positives though, e.g.: http://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian-edu_wheezy-test_standalone/15/ The install was thought to 'hang' and fail, because it rebooted into the installed system within qemu. I think you are missing the qemu '-no-reboot' flag here? Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50df9fb1.4010...@pyro.eu.org
Processed: Re: Bug#696968: rootskel-gtk: theme=dark results in ever-looping X
Processing control commands: > clone -1 -2 Bug #696968 [rootskel-gtk] rootskel-gtk: theme=dark results in ever-looping X Bug 696968 cloned as bug 696972 > retitle -2 brltty wants to be able to terminate Xorg while theme=dark wants > not to terminate it Bug #696972 [rootskel-gtk] rootskel-gtk: theme=dark results in ever-looping X Changed Bug title to 'brltty wants to be able to terminate Xorg while theme=dark wants not to terminate it' from 'rootskel-gtk: theme=dark results in ever-looping X' > tags -1 + pending Bug #696968 [rootskel-gtk] rootskel-gtk: theme=dark results in ever-looping X Added tag(s) pending. -- 696968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696968 696972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696972 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: http://lists.debian.org/handler.s.b696968.135683160118911.transcr...@bugs.debian.org
Bug#696968: rootskel-gtk: theme=dark results in ever-looping X
Control: clone -1 -2 Control: retitle -2 brltty wants to be able to terminate Xorg while theme=dark wants not to terminate it Control: tags -1 + pending Hello, Cyril Brulebois, le Sun 30 Dec 2012 01:26:25 +0100, a écrit : > adding theme=dark to the command line for accessibility purposes leads > to an ever-looping X. Basically, options for the X server (see > rootskel-gtk's S62Xorg) lead to its termination after a first client > exited, and that's what's happening when the theme is set (S65theme). Augggh. That's precisely what brltty wants in order to nicely shut the graphical installer down. I have reverted that for now: * Revert passing -terminate to the X server, to unbreak theme=dark. As long as the graphical installer is not the default, brltty not being able to nicely shut Xorg down is less required than a working graphical dark theme. Closes: #696968. That should be enough for an rc1, and can be used for Wheezy, under the condition that the graphical installer is not made the default. We'll have to find a solution for the long term, thus cloning. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121230013957.GY6406@type
Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner
Samuel Thibault (30/12/2012): > Maybe just use the same solid background color as the rest of the > screen, to make the output as simple as possible. The diamond-shaped > dot can probably remain pink indeed. ACK; Paul ↑ ;) > I'm not sure why you consider the rest of the screen as nasty. I > guess the dark blue background was used because IIRC there are > studies saying that it'd be nicer than just black. Probably because of a poor choice of words. I should have mentioned it wasn't in line with either squeeze's or wheezy's colours. And yeah, having a specific colour isn't entirely insane. :) Here are the comments at the top of the gtkrc file: | # High-Contrast, Large Print, Inverse Video Theme v0.1 | # This is the whole basic theme, just this one gtkrc file. | # It uses components of the standard theme engine | # Written by Bill Haneman, based on Standard theme by T. Liebeck, | # which was in turn based on lots of different gtkrc files but | # primarily the one for the metal theme. | # email: bill.hane...@sun.com Either that or a README should probably mention that point, so that there's no regression in future releases because somebody thought updating colours in all themes was the way to go. ;) (Hello whoever is managing d-i and desktop themes in a few months/years!) Mraw, KiBi. signature.asc Description: Digital signature
Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner
Cyril Brulebois, le Sun 30 Dec 2012 01:26:27 +0100, a écrit : > Nonetheless, I'd be happy to see an improved banner soonish; I'd suggest > something like a solid background color, and just a white debian > text+swirl there (maybe keep a pink, diamond-shaped dot on the 'i'). Maybe just use the same solid background color as the rest of the screen, to make the output as simple as possible. The diamond-shaped dot can probably remain pink indeed. I'm not sure why you consider the rest of the screen as nasty. I guess the dark blue background was used because IIRC there are studies saying that it'd be nicer than just black. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121230004059.GV6406@type
Bug#696970: cdebconf-gtk-udeb: Add support for an alternate logo in the banner
Package: cdebconf-gtk-udeb Version: 0.181 Severity: normal Tags: d-i Hi, currently we have a logo defined by: | #define LOGO_IMAGE_PATH \ | BASE_IMAGE_PATH "/logo_installer.png" In a bug report against rootskel-gtk (bug number is pending), I suggested we improve support for theme=dark, especially on the banner side. That'll likely include shipping an extra logo, so a little less of hardcoding will probably be needed at that point. Opening this bug report as a placeholder for now. Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121230002630.400.71116.reportbug@kathleen
Bug#696969: rootskel-gtk: Improve theme=dark, especially the banner
Package: rootskel-gtk Version: 1.26 Severity: normal Tags: d-i Hi -boot@/-accessibility@/Paul, as mentioned on IRC, when enabling accessibility through theme=dark (warning, it’s been broken for a while, see the other rootskel-gtk bug report on that topic), one gets a quite nasty screen, see attached screenshot. I think we could improve the gtk theme, but that might wait until we switch (if we do that) to gtk3. Nonetheless, I'd be happy to see an improved banner soonish; I'd suggest something like a solid background color, and just a white debian text+swirl there (maybe keep a pink, diamond-shaped dot on the 'i'). If people on -accessibility have more hints to improve that screen, please report back. ;) Mraw, KiBi. <>
Bug#696968: rootskel-gtk: theme=dark results in ever-looping X
Package: rootskel-gtk Version: 1.26 Severity: important Tags: d-i Hi folks, adding theme=dark to the command line for accessibility purposes leads to an ever-looping X. Basically, options for the X server (see rootskel-gtk's S62Xorg) lead to its termination after a first client exited, and that's what's happening when the theme is set (S65theme). Switching -terminate and -noreset fixes that (but see the manpage…). Looks like we need to review those options. Regression from (ironically for accessibility purposes ;)): | commit 46997e8b58a1076a9293382379c17377730395b7 | Author: Samuel Thibault | Date: Tue Jul 26 23:39:34 2011 +0200 | | Pass -terminate option to X server, so that brltty can nicely kill debconf and see Xorg terminate as a consequence. | | diff --git a/debian/changelog b/debian/changelog | index 4b58b58..55cc0cd 100644 | --- a/debian/changelog | +++ b/debian/changelog | @@ -1,3 +1,11 @@ | +rootskel-gtk (1.23) UNRELEASED; urgency=low | + | + [ Samuel Thibault ] | + * Pass -terminate option to X server, so that brltty can nicely kill debconf | +and see Xorg terminate as a consequence. | + | + -- Samuel Thibault Tue, 26 Jul 2011 23:37:47 +0200 | + | rootskel-gtk (1.22) unstable; urgency=low | |[ Miguel Figueiredo ] | diff --git a/src/lib/debian-installer.d/S62Xorg b/src/lib/debian-installer.d/S62Xorg | index 37ace7c..83d15c8 100644 | --- a/src/lib/debian-installer.d/S62Xorg | +++ b/src/lib/debian-installer.d/S62Xorg | @@ -1,6 +1,6 @@ | if [ "$DEBIAN_FRONTEND" = gtk ] && [ -z "$LIVE_INSTALLER_MODE" ]; then | trap : SIGUSR1 | - (trap '' SIGUSR1; exec Xorg -noreset -nolisten tcp) & | + (trap '' SIGUSR1; exec Xorg -noreset -nolisten tcp -terminate) & | wait | export DISPLAY=:0 | fi Mraw, KiBi. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121230002625.32483.46103.reportbug@kathleen
Processed: found 679293 in 4.0.5, found 656586 in 2.4.1-1, found 672372 in 3.2.1-4, found 672160 in 1.89 ...
Processing commands for cont...@bugs.debian.org: > found 679293 4.0.5 Bug #679293 [fai-quickstart] fai-quickstart: fails to purge: fai-quickstart.postrm: 7: .: Can't open /etc/fai/nfsroot.conf Marked as found in versions fai/4.0.5. > found 656586 2.4.1-1 Bug #656586 [routino-www] fails to purge - rmdir: failed to remove '/var/lib/routino/data': No such file or directory Marked as found in versions routino/2.4.1-1. > found 672372 3.2.1-4 Bug #672372 [backuppc] backuppc: unowned files after purge (policy 6.8, 10.8) Marked as found in versions backuppc/3.2.1-4. > found 672160 1.89 Bug #672160 [console-setup] console-setup: unowned files after purge (policy 6.8, 10.8) Marked as found in versions console-setup/1.89. > found 619244 44-7 Bug #619244 [systemd] systemd: unowned files after purge (policy 6.8, 10.8): /etc/machine-id Marked as found in versions systemd/44-7. > found 658108 1:4.10.2.2614-1 Bug #658108 [squeak-vm] squeak-vm: unowned files after purge (policy 6.8, 10.8) Marked as found in versions squeak-vm/1:4.10.2.2614-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 619244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619244 656586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656586 658108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658108 672160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672160 672372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672372 679293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679293 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: http://lists.debian.org/handler.s.c.13568245147292.transcr...@bugs.debian.org
Bug#646704: Bug severity is too high
On 12/29/2012 10:33 PM, Samuel Thibault wrote: > As Christian said, it's not just a bug "in live-installer", but "with > crypted volume", which makes it much less grave. the purpose of live-installer is to be able to use d-i to install live-images. like i said, if that fails (by an original bug in live-installer or by lacking a workaround in live-installer for something else in d-i), it's serious. if the bug is not to be fixed (or workarounded) in live-installer, the bug needs to be reassigned (please do so; and then i don't care about the severity, as it's none of the packages i'm looking after). -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50df6470.8050...@progress-technologies.net
Bug#646704: Bug severity is too high
On 12/29/2012 10:10 PM, Christian PERRIER wrote: > Which probably explains why you haven't done anything since > September, I guess. i for my part have clearly said publicly many times when i'm going to work on live-installer parts (when the other live-* parts are done, that is), so that's no surprise there. since you put yourself into uploaders of live-installer some time ago, maybe you want to look at it yourself too? > Sorry, I'm still deeply convinced that this issue is mostly a case > that doesn't deserve an RC severity. I'll downgrade this bug again > in 4 weeks if nothing happened in the meantime. should that be the case, i'll restore the original severity of course. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50df6398.4060...@progress-technologies.net
Re: d-i manual (Re: building and testing d-i with jenkins)
Hi, today I found the following on http://jenkins.debian.net/view/d-i_manual/job/d-i_manual_pt_pdf/lastBuild/console rmdir: failed to remove `pdf/pt.amd64': Directory not empty rmdir: failed to remove `pdf/pt.armel': Directory not empty rmdir: failed to remove `pdf/pt.armhf': Directory not empty rmdir: failed to remove `pdf/pt.hppa': Directory not empty rmdir: failed to remove `pdf/pt.hurd-i386': Directory not empty rmdir: failed to remove `pdf/pt.i386': Directory not empty rmdir: failed to remove `pdf/pt.ia64': Directory not empty rmdir: failed to remove `pdf/pt.kfreebsd-amd64': Directory not empty rmdir: failed to remove `pdf/pt.kfreebsd-i386': Directory not empty rmdir: failed to remove `pdf/pt.mips': Directory not empty rmdir: failed to remove `pdf/pt.mipsel': Directory not empty rmdir: failed to remove `pdf/pt.powerpc': Directory not empty rmdir: failed to remove `pdf/pt.s390': Directory not empty rmdir: failed to remove `pdf/pt.s390x': Directory not empty rmdir: failed to remove `pdf/pt.sparc': Directory not empty Just to let you know ... This is most probably not an issue, as long as the remaining directories don't make problems at the next build ... Nevertheless, this should probably be avoided? Holger W. -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 3.0.2 under D e b i a n G N U / L I N U X 6.0 ( S q u e e z e ) Registered LinuxUser #311290 - http://linuxcounter.net/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121229223356.f736a528.li...@wansing-online.de
Bug#646704: Bug severity is too high
Daniel Baumann, le Sat 29 Dec 2012 20:16:57 +0100, a écrit : > On 12/29/2012 0502 PM, Christian PERRIER wrote: > > This bug doesn't fit the definition of "serious" as it only shows up > > for a precise set of installation types, those not being the most > > common, particularly when people use the Live CD to install. > > a bug in live-installer which leads to an incomplete installation is > serious. As Christian said, it's not just a bug "in live-installer", but "with crypted volume", which makes it much less grave. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121229213352.GL6406@type
Bug#696952: marked as done (installation-reports: evdev crashed with backtrace - kernel oops)
Your message dated Sat, 29 Dec 2012 22:14:27 +0100 with message-id <20121229211427.gz6...@mykerinos.kheops.frmug.org> and subject line Re: Bug#696952: installation-reports: evdev crashed with backtrace - kernel oops has caused the Debian Bug report #696952, regarding installation-reports: evdev crashed with backtrace - kernel oops 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 696952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: CD Image version: debian-wheezy-DI-b4-amd64-i386-netinst.iso Date: 28dec2012 22:00 EST Machine: personal build - intel D845grg 2.2Ghz p4 512Mb pc2100 ddr 8Mb shared vide http://downloadmirror.intel.com/15328/eng/D845GRG_D845GBV_ProductGuide_English.pdf Partitions: sfdisk -l Disk /dev/sda: 14593 cylinders, 255 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/sda1 * 0+ 46 47-377496 83 Linux /dev/sda2 47 419 3732996122+ 83 Linux /dev/sda3420 792 3732996122+ 83 Linux /dev/sda4793+ 14592 13800- 110848469+ 5 Extended /dev/sda5793+ 22811489- 11960361 83 Linux /dev/sda6 2282+ 37701489- 11960361 83 Linux /dev/sda7 3771+ 52591489- 11960361 83 Linux /dev/sda8 5260+ 67481489- 11960361 83 Linux /dev/sda9 6749+ 82371489- 11960361 83 Linux /dev/sda10 8238+ 97261489- 11960361 83 Linux /dev/sda11 9727+ 112151489- 11960361 83 Linux /dev/sda12 11216+ 127041489- 11960361 83 Linux /dev/sda13 12705+ 141931489- 11960361 83 Linux /dev/sda14 14194+ 14392 199- 1598436 83 Linux /dev/sda15 14393+ 14592 200- 1606468+ 82 Linux swap / Solaris Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: install was flawless to sda10 using an ext4 default filesystem. see # 695476 After install issues with X for this machine. I did a minimal Debian install (unchecked everything during tasksel) then I did a minimal X install with firmware-linux and firmware-linux-nonfree ( original dmesg showed firmware for intel E100 network was missing ), X started fine ( as far as I could see ), to fallback xterm session. until I tried to open a second xterm and run a command in the second xterm when the system hung with an audible buzz. I'll setup ssh if debian-boot or debian-x want moreinfo. dmesg tail shows [1.984621] usbcore: registered new interface driver usbhid [1.984626] usbhid: USB HID core driver [3.640313] PM: Starting manual resume from disk [3.640321] PM: Hibernation image partition 8:15 present [3.640324] PM: Looking for hibernation image. [3.640641] PM: Image not found (code -22) [3.640644] PM: Hibernation image not present or could not be loaded. [3.688199] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null) [5.063867] udevd[292]: starting version 175 [5.371286] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2 [5.371301] ACPI: Sleep Button [SLPB] [5.371407] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [5.371414] ACPI: Power Button [PWRF] [5.403965] intel_rng: Firmware space is locked read-only. If you can't or [5.403968] intel_rng: don't want to disable this in firmware setup, and if [5.403970] intel_rng: you are certain that your system has a functional [5.403972] intel_rng: RNG, try using the 'no_fwh_detect' option. [5.419455] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [5.458430] parport_pc 00:09: reported by Plug and Play ACPI [5.458461] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] [5.616917] input: PC Speaker as /devices/platform/pcspkr/i
Bug#646704: Bug severity is too high
Quoting Daniel Baumann (daniel.baum...@progress-technologies.net): > severity 646704 serious > thanks > > On 12/29/2012 0502 PM, Christian PERRIER wrote: > > This bug doesn't fit the definition of "serious" as it only shows up > > for a precise set of installation types, those not being the most > > common, particularly when people use the Live CD to install. > > a bug in live-installer which leads to an incomplete installation is > serious. Which probably explains why you haven't done anything since September, I guess. Sorry, I'm still deeply convinced that this issue is mostly a case that doesn't deserve an RC severity. I'll downgrade this bug again in 4 weeks if nothing happened in the meantime. signature.asc Description: Digital signature
Bug#696952: installation-reports: evdev crashed with backtrace - kernel oops
Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: CD Image version: debian-wheezy-DI-b4-amd64-i386-netinst.iso Date: 28dec2012 22:00 EST Machine: personal build - intel D845grg 2.2Ghz p4 512Mb pc2100 ddr 8Mb shared vide http://downloadmirror.intel.com/15328/eng/D845GRG_D845GBV_ProductGuide_English.pdf Partitions: sfdisk -l Disk /dev/sda: 14593 cylinders, 255 heads, 63 sectors/track Warning: extended partition does not start at a cylinder boundary. DOS and Linux will interpret the contents differently. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/sda1 * 0+ 46 47-377496 83 Linux /dev/sda2 47 419 3732996122+ 83 Linux /dev/sda3420 792 3732996122+ 83 Linux /dev/sda4793+ 14592 13800- 110848469+ 5 Extended /dev/sda5793+ 22811489- 11960361 83 Linux /dev/sda6 2282+ 37701489- 11960361 83 Linux /dev/sda7 3771+ 52591489- 11960361 83 Linux /dev/sda8 5260+ 67481489- 11960361 83 Linux /dev/sda9 6749+ 82371489- 11960361 83 Linux /dev/sda10 8238+ 97261489- 11960361 83 Linux /dev/sda11 9727+ 112151489- 11960361 83 Linux /dev/sda12 11216+ 127041489- 11960361 83 Linux /dev/sda13 12705+ 141931489- 11960361 83 Linux /dev/sda14 14194+ 14392 199- 1598436 83 Linux /dev/sda15 14393+ 14592 200- 1606468+ 82 Linux swap / Solaris Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: install was flawless to sda10 using an ext4 default filesystem. see # 695476 After install issues with X for this machine. I did a minimal Debian install (unchecked everything during tasksel) then I did a minimal X install with firmware-linux and firmware-linux-nonfree ( original dmesg showed firmware for intel E100 network was missing ), X started fine ( as far as I could see ), to fallback xterm session. until I tried to open a second xterm and run a command in the second xterm when the system hung with an audible buzz. I'll setup ssh if debian-boot or debian-x want moreinfo. dmesg tail shows [1.984621] usbcore: registered new interface driver usbhid [1.984626] usbhid: USB HID core driver [3.640313] PM: Starting manual resume from disk [3.640321] PM: Hibernation image partition 8:15 present [3.640324] PM: Looking for hibernation image. [3.640641] PM: Image not found (code -22) [3.640644] PM: Hibernation image not present or could not be loaded. [3.688199] EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: (null) [5.063867] udevd[292]: starting version 175 [5.371286] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input2 [5.371301] ACPI: Sleep Button [SLPB] [5.371407] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [5.371414] ACPI: Power Button [PWRF] [5.403965] intel_rng: Firmware space is locked read-only. If you can't or [5.403968] intel_rng: don't want to disable this in firmware setup, and if [5.403970] intel_rng: you are certain that your system has a functional [5.403972] intel_rng: RNG, try using the 'no_fwh_detect' option. [5.419455] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [5.458430] parport_pc 00:09: reported by Plug and Play ACPI [5.458461] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] [5.616917] input: PC Speaker as /devices/platform/pcspkr/input/input4 [5.750580] iTCO_vendor_support: vendor-support=0 [5.776920] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [5.777052] iTCO_wdt: Found a ICH4 TCO device (Version=1, TCOBASE=0x0460) [5.778483] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [5.802503] [drm] Initialized drm 1.1.0 20060810 [5.807824] Error: Driver 'pcspkr' is already registered, aborting... [5.821557] snd_intel8x0 :00:1f.5: setting latency timer to 64 [6.192037] intel8x0_measure_ac97_clock: measured 54684 usecs (2635 samples) [6.192043] intel8x0: clocking to 48000 [6.193208] i915 :00:02.0: setting latency timer to 64 [6.230894] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [6.230899] [drm] Driver supports precise vblank timestamp query. [6.231731] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [6.246855] [
Bug#646704: live-installer: installer doesn't write /etc/crypttab for crypt+LVM
tag 646704 - confirmed thanks usage of the tag 'confirmed' is reserved for the maintainer to indicate that he could reproduce it, not users (re)reporting it. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50df4272.50...@progress-technologies.net
Processed: Re: live-installer: installer doesn't write /etc/crypttab for crypt+LVM
Processing commands for cont...@bugs.debian.org: > tag 646704 - confirmed Bug #646704 [live-installer] live-installer: installer doesn't write /etc/crypttab for crypt+LVM Removed tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 646704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646704 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: http://lists.debian.org/handler.s.c.135680866530347.transcr...@bugs.debian.org
Processed: Re: Bug#646704: Bug severity is too high
Processing commands for cont...@bugs.debian.org: > severity 646704 serious Bug #646704 [live-installer] live-installer: installer doesn't write /etc/crypttab for crypt+LVM Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 646704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646704 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: http://lists.debian.org/handler.s.c.135680846629136.transcr...@bugs.debian.org
Bug#646704: Bug severity is too high
severity 646704 serious thanks On 12/29/2012 0502 PM, Christian PERRIER wrote: > This bug doesn't fit the definition of "serious" as it only shows up > for a precise set of installation types, those not being the most > common, particularly when people use the Live CD to install. a bug in live-installer which leads to an incomplete installation is serious. > Downgrading to "important" as per the definition of "improtant" severity. restoring original severity. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50df41a9.7040...@progress-technologies.net
Re: Installing Lenny
NM. I found the "enter information manually" option. Sorry for bugging. On Sat, Dec 29, 2012 at 12:00 PM, Shawn Willden wrote: > I have an LVS which is still running Lenny (I know, I know) and I need to > upgrade it to Squeeze. Before I do, though, I need to first replicate the > system in a VM, test it, upgrade it and test that. So I'm trying to install > Lenny in order to upgrade it to Sqeeze. I'm on a fairly slow Internet > connection (working from the in-laws for the holidays) so I'd like to use > the netinst CD image that I've already downloaded. > > But the netinst CD installer wants to grab packages from the original > lenny archive locations, not from their new home on archive.debian.org. > > Is there some way I can convince the installer to use the new archive > location? Or do I need to download the full CD (in progress, will take some > hours). > > Thanks, > > -- > Shawn > -- Shawn
Installing Lenny
I have an LVS which is still running Lenny (I know, I know) and I need to upgrade it to Squeeze. Before I do, though, I need to first replicate the system in a VM, test it, upgrade it and test that. So I'm trying to install Lenny in order to upgrade it to Sqeeze. I'm on a fairly slow Internet connection (working from the in-laws for the holidays) so I'd like to use the netinst CD image that I've already downloaded. But the netinst CD installer wants to grab packages from the original lenny archive locations, not from their new home on archive.debian.org. Is there some way I can convince the installer to use the new archive location? Or do I need to download the full CD (in progress, will take some hours). Thanks, -- Shawn
Processed: Re: Bug#696903: [1.83->1.84 regression]: GRUB won't install to a character device
Processing control commands: > tags -1 + patch Bug #696903 [grub-installer] [1.83->1.84 regression]: GRUB won't install to a character device Added tag(s) patch. -- 696903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696903 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: http://lists.debian.org/handler.s.b696903.135680707319437.transcr...@bugs.debian.org
Bug#696903: [1.83->1.84 regression]: GRUB won't install to a character device
Control: tags -1 + patch Allow installing GRUB to a character device, as on GNU/kFreeBSD diff --git a/grub-installer b/grub-installer index 5d9fd77..6e2c7fc 100755 --- a/grub-installer +++ b/grub-installer @@ -651,9 +651,9 @@ if [ -z "$frdisk" ]; then # Install grub on each space separated disk in the list bootdevs="$bootdev" for bootdev in $bootdevs; do # workaround for #681227 - if [ ! -b $bootdev -a $bootdev != dummy ]; then + if [ ! -b $bootdev -a ! -c $bootdev -a $bootdev != dummy ]; then continue fi grub_install_params= if ! is_floppy "$bootdev"; then Or instead - make the logical IMHO clearer, and while here, wrap $bootdev in quotes to be paranoid: diff --git a/grub-installer b/grub-installer index 5d9fd77..552c9bc 100755 --- a/grub-installer +++ b/grub-installer @@ -651,9 +651,9 @@ if [ -z "$frdisk" ]; then # Install grub on each space separated disk in the list bootdevs="$bootdev" for bootdev in $bootdevs; do # workaround for #681227 - if [ ! -b $bootdev -a $bootdev != dummy ]; then + if ! [ "$bootdev" = dummy -o -b "$bootdev" -o -c "$bootdev" ]; then continue fi grub_install_params= if ! is_floppy "$bootdev"; then Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121229185107.ga21...@squeeze.pyro.eu.org
Bug#696942: [1.83->1.84 regression]: GRUB won't install to a dummy device
Package: grub-installer Version: 1.84 Severity: grave Tags: d-i X-Debbugs-Cc: paj...@gmail.com Control: block 681227 by -1 Hello, On 29/12/12 10:39, alberto fuentes wrote: > Dec 29 00:41:32 grub-installer: info: Installing grub on 'dummy' > Dec 29 00:41:32 grub-installer: error: no boot device found to install to That is new a problem affecting at least grub-efi and grub-yeeloong and was fixed in Git but I think we need a bug number for it now: http://lists.debian.org/debian-boot/2012/12/msg00463.html http://anonscm.debian.org/gitweb/?p=d-i/grub-installer.git;a=commitdiff;h=99389d59fc539c399e147eb74acedfce04da011f Does it matter that $bootdev is not in quotes? Every other use of it in the script is quoted. It can't contain spaces at least: > --- a/grub-installer > +++ b/grub-installer > @@ -651,7 +651,7 @@ if [ -z "$frdisk" ]; then > # Install grub on each space separated disk in the list > bootdevs="$bootdev" > for bootdev in $bootdevs; do > # workaround for #681227 > - if [ ! -b $bootdev ]; then > + if [ ! -b $bootdev -a $bootdev != dummy ]; then > continue > fi Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50df34a9.2070...@pyro.eu.org
Processed: [1.83->1.84 regression]: GRUB won't install to a dummy device
Processing control commands: > block 681227 by -1 Bug #681227 [grub-installer] installation-reports: grub-install tries to install to a nonsense string 681227 was blocked by: 696903 681227 was not blocking any bugs. Added blocking bug(s) of 681227: 696942 -- 681227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681227 696942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696942 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: http://lists.debian.org/handler.s.b.13568053017154.transcr...@bugs.debian.org
Bug#695500: debian-installer-7.0-netboot-kfreebsd-amd64: does not boot from pxe
Hi Michael, Michael Tsang (09/12/2012): > I cannot boot the installer from pxe. GRUB says prefix is not set > and dies. It seems to be a configuration bug. I see now that the "prefix is not set" message appears very quickly, before GRUB switches into graphical mode. It seems harmless, because at the GRUB command line the prefix is correctly set. My guess is that the machine booting via PXE was unable to show the GRUB menu properly. For example, if some kind of console redirection was being used. This can be worked around by simply removing this file from the TFTP server: debian-installer/kfreebsd-amd64/font.pf2 And GRUB should fall back to text mode. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50df2348.8050...@pyro.eu.org
Processed: Bug severity is too high
Processing commands for cont...@bugs.debian.org: > severity 646704 important Bug #646704 [live-installer] live-installer: installer doesn't write /etc/crypttab for crypt+LVM Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 646704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646704 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: http://lists.debian.org/handler.s.c.135679695415114.transcr...@bugs.debian.org
Bug#646704: Bug severity is too high
severity 646704 important thanks This bug doesn't fit the definition of "serious" as it only shows up for a precise set of installation types, those not being the most common, particularly when people use the Live CD to install. Downgrading to "important" as per the definition of "improtant" severity. -- signature.asc Description: Digital signature
Bug#693839: debian-installer: kernel install fails on armel buffalo linkstation pro, missing uboot-mkimage
Quoting Cyril Brulebois (k...@debian.org): > Hi, and thanks for your report. > > u-boot-tools is only in “Suggests” for flash-kernel, while your > situation suggests it might be better to have it in “Recommends”. > What do others think? Well, I even moved it to Depends in my commit. I'm not sure it is a good idea to rely on Recommends being installed if the mkimage program is required in some situations. I'm ready to upload flash-kernel with that fix. signature.asc Description: Digital signature
Bug#693485: Re[2]: Bug#693485: keyboard-configuration: XKBLAYOUT, XKBOPTIONS values manually set in /etc/default/keyboard lost on upgrade
On Fri, Dec 28, 2012 at 01:32:50AM +0400, Bob Bib wrote: > > OK, but the output is a little bit too verbose (see it attached). Good. I think this will be an exciting reading. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121229141012.ga16...@logic.fmi.uni-sofia.bg
Bug#433568: add vlan support
On Sat, Dec 29, 2012 at 08:34:27AM +0100, Christian PERRIER wrote: > Taking over KiBi's hat, I would say there is no chance this makes it > to wheezy. And taking mine, too, with several addition to localization > bits. The debconf templates need minor edits to compleltely fit with > the writing style we're using elsewhere...and they add 8 > stringsand we have 56 complete translations (more than we *ever* > had). I'd say that this is something that must be preseeded and if anything it would show errors in English. So I'm not too concerned about that. But if we agree that it is "useful" to show netcfg/use_vlan in jessie in expert mode, we can do that too. Kind regards Philipp Kern signature.asc Description: Digital signature
Re: d-i wheezy rc1 status; and unblock(-udeb)s, round 4
Nice new installer. I tried this and the beta3. Less bugs. The dialogs are more clear and the text that goes with it. The way the questions are separated from the explanations. The borderless window in the gui. Overall I saw a great improvement in the experience. small details i found: - A little of inconsistency presenting yes/no questions with a continue button, in the same way we present the rest of the steps of the installation. I had to think for a while why i had no back button. - When selecting a partition with data it knows the format of the fs, but it does not autoselect it. Im i remember correctly once you select the format, it does selects keep the data by default, witch is desirable :) - Make partitions does hasnt been deal with stand out from the ones that has (either automatically or by the user) would be great. In my case the, the installation of the GRUB boot loader on the hard disk failed. But I was only presented with a big general error screen... with little detail on why it failed. Maybe some more info is desirable without having to look at the logs. Installer logs are huge. A little error grepping found the problem, but i think it would be friendlier to log errors to a separate file.err as well These are the relevant lines: Dec 29 00:41:32 linux-boot-prober: debug: running /usr/lib/linux-boot-probes/mounted Dec 29 00:41:32 grub-installer: info: Installing grub on 'dummy' Dec 29 00:41:32 grub-installer: error: no boot device found to install to Dec 29 00:41:32 main-menu[629]: (process:11487): File descriptor 3 (pipe:[6373]) leaked on lvdisplay invocation. Parent PID 12210: /bin/sh Dec 29 00:41:32 main-menu[629]: (process:11487): File descriptor 4 (/dev/tty1) leaked on lvdisplay invocation. Parent PID 12210: /bin/sh Dec 29 00:41:32 main-menu[629]: (process:11487): File descriptor 5 (/dev/tty1) leaked on lvdisplay invocation. Parent PID 12210: /bin/sh Dec 29 00:41:32 main-menu[629]: (process:11487): File descriptor 6 (/dev/tty1) leaked on lvdisplay invocation. Parent PID 12210: /bin/sh Dec 29 00:41:32 main-menu[629]: (process:11487): grub-probe: error: no such disk. Dec 29 00:41:32 main-menu[629]: (process:11487): grub-probe: error: no such disk. Dec 29 00:41:32 main-menu[629]: WARNING **: Configuring 'grub-installer' failed with error code 1 Dec 29 00:41:32 main-menu[629]: WARNING **: Menu item 'grub-installer' failed. Not sure if I did something wrong on the partitioning or a bug, probably the former, but i havent figured out why it is trying to install grub on dummy nor i found any more references to this dummy device on this or the rest of the logs. Thanks! On Thu, Dec 27, 2012 at 5:48 PM, Cyril Brulebois wrote: > Hi folks! > > (Including debian-devel@ to let people know where we stand.) > > I'm happy to report we're getting closer to a first release candidate > for the Debian Installer. I've still got a few packages on my radar, > but the list has been steadily shrinking during the last week. > > That basically boils down to: > - busybox vs. setupcon: #606395 (console keymap in g-i) > - cdebconf: Info message position (comments welcome): #696699; >apparently that one didn't reach the list when I submitted it, >bounced today. > - grub-installer: install from USB issues. > - manual: needs an upload after a few more patches are reviewed. > - qcontrol: #696815 (armhf addition, via t-p-u). > - yaboot-installer: needs review+upload > > I'm currently awaiting feedback on the first two; the third one needs > some code changes and I'm going to work on it right now; qcontrol can > be handled by Ian/release team; yaboot-installer wants somebody to > look at it, will do once I'm done with grub-installer unless somebody > beats me to it. > > If you see other things you want to get fixed, now is the time to > mention them (by mailing -boot@). > > > Release team, here's a fourth list of unblock(-udeb)s. Still no need > for urgents since there's some more work to do. :) > > ### blindly trusting Samuel > unblock brltty/4.4-7 > unblock-udeb brltty/4.4-7 > > ### add preseeding support for keyboard-configuration/xkb-keymap > unblock console-setup/1.89 > unblock-udeb console-setup/1.89 > > ### fix for #679327 > unblock debconf/1.5.49 > > ### l10n + unrelated-hopefully-harmless better support for crossbuilding > unblock eject/2.1.5+deb1+cvs20081104-13 > unblock-udeb eject/2.1.5+deb1+cvs20081104-13 > > ### fix for #694156 (= workaround for #696773) > unblock finish-install/2.41 > unblock-udeb finish-install/2.41 > > ### l10n > unblock lvmcfg/1.29 > unblock-udeb lvmcfg/1.29 > > ### bits of l10n and tiny improvement merged from Ubuntu > unblock partman-partitioning/90 > unblock-udeb partman-partitioning/90 > > ### bug fix for #695908, and a test suite addition, which helped > ### confirm the first iteration of the patches was buggy and the > ### second one a bit less: > unblock preseed/1.57 > unblock-udeb preseed/1.57 > > ### l10n > unblock s390-dasd/0.0.29 > unblock-udeb s390-dasd
