Bug#718855: desktop=xfce installs Gnome stuff and evenmore gnome appears as the default window manager from lightdm
Package: installation-reports Boot method: iso image of testing installer in a USB pendrive. Image version: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-xfce-CD-1.iso Date: 2013-08-06 8:00:00 GMT+2 Machine: MSI GT60 Processor: i7-3630QM Memory: 8 GiB Partitions: /boot, / (in sda disk) Comments/Problems: It is just what I said in the subject: I chose to install XFCE as the Window Manager for X, but Gnome installs. I supposed that thins kind of installation would set XFCE as the only WM. And I add that in this case, from lightdm, default WM is not XFCE -- -- Salutacions...Josep -- -- 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/capbo7tblzci0wn-pk-j6hxzgg-mdcxfoq26rjfjmsoq3ncx...@mail.gmail.com
Bug#718698: marked as done ([os-prober] ReiserFS support)
Your message dated Tue, 6 Aug 2013 13:16:51 +0200 with message-id <201308061316.56999.hol...@layer-acht.org> and subject line Re: Bug#718698: [os-prober] ReiserFS support has caused the Debian Bug report #718698, regarding [os-prober] ReiserFS support 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.) -- 718698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718698 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: os-prober Version: 1.63 Severity: important Please continue to support the ReiserFS until is supported by the kernel --- System information. --- Architecture: i386 Kernel: Linux 3.9.8 Debian Release: jessie/sid 500 testing ftp.it.debian.org --- End Message --- --- Begin Message --- Hi, On Sonntag, 4. August 2013, Francesco Muzio wrote: > Please continue to support the ReiserFS until is supported by the kernel it is supported now, so there is nothing to be done, thus closing. its equally not useful to open bugs for keeping other features. cheers, Holger signature.asc Description: This is a digitally signed message part. --- End Message ---
Bug#718698: [os-prober] ReiserFS support
Hi, On Sonntag, 4. August 2013, Francesco Muzio wrote: > Please continue to support the ReiserFS until is supported by the kernel it is supported now, so there is nothing to be done, thus closing. its equally not useful to open bugs for keeping other features. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#718698: (no subject)
if the latest version of os-prober it's able yet to recognize a kernel image on a ReiserFS filesystem you did not have to enter that worrying message in the changelog. -- 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/5200f62e.4080...@gmail.com
Bug#716978: initramfs not setting up crypto
On Mon, 2013-08-05 at 16:31 -0700, Matt Taggart wrote: > I think I am seeing the same bug reported in #716978... > > I just did an install of wheezy using a d-i daily (updated today > 2013-08-05). The root is md raid->crypt->lvm. Upon boot the initramfs > started up the md raid devices properly, but failed to setup the crypto > and dropped to an initramfs shell. When I poke around I see that > > /lib/modules/3.2.0-4-amd64/kernel/crypto/ > > is lacking most of the crypto modules (including the xts/serpant/etc > that my system needed). So I am unable to bring things up by hand > either. > > During the install, for the question about how much to include in the > initramfs, I picked the "just what's needed by this system" answer, > although I think that should have been OK. I doubt we'll ever be able to get it completely right. That option should be warned against in general. It is useful for machines with limited memory or space for the initramfs (e.g. ARM systems where the bootloader looks for it in a specific flash partition). Otherwise it just saves a fraction of a second of boot time, or fails to boot. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part
Bug#716978: initramfs not setting up crypto
Ben Hutchings writes: > On Mon, 2013-08-05 at 16:31 -0700, Matt Taggart wrote: > > I think I am seeing the same bug reported in #716978... > >=20 > > I just did an install of wheezy using a d-i daily (updated today > > 2013-08-05). The root is md raid->crypt->lvm. Upon boot the initramfs > > started up the md raid devices properly, but failed to setup the crypto > > and dropped to an initramfs shell. When I poke around I see that > >=20 > > /lib/modules/3.2.0-4-amd64/kernel/crypto/ > >=20 > > is lacking most of the crypto modules (including the xts/serpant/etc > > that my system needed). So I am unable to bring things up by hand > > either. > >=20 > > During the install, for the question about how much to include in the > > initramfs, I picked the "just what's needed by this system" answer, > > although I think that should have been OK. > > I doubt we'll ever be able to get it completely right. That option > should be warned against in general. It is useful for machines with > limited memory or space for the initramfs (e.g. ARM systems where the > bootloader looks for it in a specific flash partition). Otherwise it > just saves a fraction of a second of boot time, or fails to boot. I used d-i rescue mode to mount the disks and switch from "dep" to "most" mode for update-initramfs and that pulled the crypto modules in. But now the problem is that the LVM tools aren't in the initramfs so it gets stuck at that point. -- Matt Taggart tagg...@debian.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/20130806171758.2a97e...@taggart.lackof.org
Bug#716978: initramfs not setting up crypto
On Tue, 2013-08-06 at 10:17 -0700, Matt Taggart wrote: > Ben Hutchings writes: > > On Mon, 2013-08-05 at 16:31 -0700, Matt Taggart wrote: > > > I think I am seeing the same bug reported in #716978... > > >=20 > > > I just did an install of wheezy using a d-i daily (updated today > > > 2013-08-05). The root is md raid->crypt->lvm. Upon boot the initramfs > > > started up the md raid devices properly, but failed to setup the crypto > > > and dropped to an initramfs shell. When I poke around I see that > > >=20 > > > /lib/modules/3.2.0-4-amd64/kernel/crypto/ > > >=20 > > > is lacking most of the crypto modules (including the xts/serpant/etc > > > that my system needed). So I am unable to bring things up by hand > > > either. > > >=20 > > > During the install, for the question about how much to include in the > > > initramfs, I picked the "just what's needed by this system" answer, > > > although I think that should have been OK. > > > > I doubt we'll ever be able to get it completely right. That option > > should be warned against in general. It is useful for machines with > > limited memory or space for the initramfs (e.g. ARM systems where the > > bootloader looks for it in a specific flash partition). Otherwise it > > just saves a fraction of a second of boot time, or fails to boot. > > I used d-i rescue mode to mount the disks and switch from "dep" to "most" > mode for update-initramfs and that pulled the crypto modules in. But now > the problem is that the LVM tools aren't in the initramfs so it gets stuck > at that point. That's strange. The LVM tools are added by /usr/share/initramfs-tools/hooks/lvm2 which is part of the lvm2 package. So this implies lvm2 wasn't installed either, though that seems unlikely. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part
Bug#716978: initramfs not setting up crypto
On 6 August 2013 19:35, Ben Hutchings wrote: > On Tue, 2013-08-06 at 10:17 -0700, Matt Taggart wrote: >> Ben Hutchings writes: >> > On Mon, 2013-08-05 at 16:31 -0700, Matt Taggart wrote: >> > > I think I am seeing the same bug reported in #716978... >> > >=20 >> > > I just did an install of wheezy using a d-i daily (updated today >> > > 2013-08-05). The root is md raid->crypt->lvm. Upon boot the initramfs >> > > started up the md raid devices properly, but failed to setup the crypto >> > > and dropped to an initramfs shell. When I poke around I see that >> > >=20 >> > > /lib/modules/3.2.0-4-amd64/kernel/crypto/ >> > >=20 >> > > is lacking most of the crypto modules (including the xts/serpant/etc >> > > that my system needed). So I am unable to bring things up by hand >> > > either. >> > >=20 >> > > During the install, for the question about how much to include in the >> > > initramfs, I picked the "just what's needed by this system" answer, >> > > although I think that should have been OK. >> > >> > I doubt we'll ever be able to get it completely right. That option >> > should be warned against in general. It is useful for machines with >> > limited memory or space for the initramfs (e.g. ARM systems where the >> > bootloader looks for it in a specific flash partition). Otherwise it >> > just saves a fraction of a second of boot time, or fails to boot. >> >> I used d-i rescue mode to mount the disks and switch from "dep" to "most" >> mode for update-initramfs and that pulled the crypto modules in. But now >> the problem is that the LVM tools aren't in the initramfs so it gets stuck >> at that point. > > That's strange. The LVM tools are added by > /usr/share/initramfs-tools/hooks/lvm2 which is part of the lvm2 package. > So this implies lvm2 wasn't installed either, though that seems > unlikely. > Do we have full debug level logs for the broken install available? cause I did some refactoring on partman-lvm and partman-crypto together with new upstream releases of lvm2, crypto, kernel there are plenty of things that could have gone wrong. Also just recently in ubuntu this upload was made: https://launchpad.net/ubuntu/+source/lvm2/2.02.98-1ubuntu4 To fix a very nasty: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1206235 Not sure if debian is also affected, and whether it's related at all. Regards, Dmitrijs. -- 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/canbhlugx1w1dre9weh5nh2xfu6n8qmkzkj_hiwypc30rfet...@mail.gmail.com
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Aug 06 00:35 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Aug 06 00:37 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log * FAILED BUILD: kfreebsd-amd64 Aug 06 00:40 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * FAILED BUILD: kfreebsd-amd64 Aug 06 00:43 buildd@fano build_netboot-gtk-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk-9.log * FAILED BUILD: kfreebsd-i386 Aug 07 00:29 buildd@finzi build_cdrom_grub http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_cdrom_grub.log * FAILED BUILD: kfreebsd-i386 Aug 07 00:33 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log * FAILED BUILD: kfreebsd-i386 Aug 07 00:34 buildd@finzi build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot-9.log Totals: 158 builds (7 failed, 2 old) -- 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/e1v6s6i-ww...@ravel.debian.org
