Bug#675866: marked as done (installation-reports: Gnome 3 launches in fallback mode after install)
Your message dated Wed, 13 Jun 2012 11:04:39 +0100 with message-id 4fd865b7.4070...@debianpt.org and subject line Re: Bug#675866: installation-reports: Gnome 3 launches in fallback mode after install has caused the Debian Bug report #675866, regarding installation-reports: Gnome 3 launches in fallback mode after install 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.) -- 675866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Installed Wheezy to a virtual machine using VirtualBox running in Ubuntu 12.04. First boot reported that Gnome 3 was in fallback mode * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: Boot method: network Image version: debain-wheezy-DI-a1-i386-netinst built May 31 2012 Date: Date and time of the install Machine: Virtualbox running on IBM Thinkpad X1 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20120508 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux imwfbx 3.2.0-2-486 #1 Sun Apr 15 16:53:08 UTC 2012 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01) lspci -knn: Kernel driver in use: ata_piix lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 02) lspci -knn: Subsystem: Intel Corporation Device [8086:001e] lspci -knn: Kernel driver in use: e1000 lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] lspci -knn: 00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01) lspci -knn: Subsystem: Intel Corporation Device [8086:] lspci -knn: 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB [106b:003f] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08) lspci -knn: 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02) lspci -knn: Kernel driver in use: ahci usb-list: usb-list: Bus 01 Device 01: OHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 3.2.0-2-486 ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB Tablet [80ee:0021] usb-list:Level 01 Parent 01 Port 00 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Manufacturer: VirtualBox usb-list:Interface 00: Class 03(HID )
Mount options for procfs
Since linux version 3.2.20-1, it is possible to set a 'hidepid' mount option on procfs, which restricts the visibility of unprivileged users to see other users' processes. initscripts correctly applies this option if present in /etc/fstab. Should d-i allow procfs mount opions to be configured at installation time (and presumably pre-seeded), or should this be left to post- installation? Ben. -- Ben Hutchings Computers are not intelligent. They only think they are. signature.asc Description: This is a digitally signed message part
tasksel upload
Hi Is there anything that speaks against an upload of tasksel? It works fine in my tests. Okay, #676777 in debhelper needs to be fixed also. Bastian -- No one wants war. -- Kirk, Errand of Mercy, stardate 3201.7 -- 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/20120613125349.ga...@wavehammer.waldi.eu.org
Re: Mount options for procfs
Ben Hutchings wrote: Since linux version 3.2.20-1, it is possible to set a 'hidepid' mount option on procfs, which restricts the visibility of unprivileged users to see other users' processes. initscripts correctly applies this option if present in /etc/fstab. Should d-i allow procfs mount opions to be configured at installation time (and presumably pre-seeded), or should this be left to post- installation? I think the problem with doing that is it would add /proc to the displayed partition table in partman, which could be confusing. OTOH, if d-i ever gets tmpfs support, /run and possibly /tmp might be there too. -- see shy jo signature.asc Description: Digital signature
Re: Debian the FSF Secure Boot petition
On Sun, Jun 10, 2012 at 11:17:25AM +0200, Stefano Zacchiroli wrote:
Dear d-i hackers, I've been contacted by Paul Wise about FSF campaign on
secure boot [1] (thanks Paul!). As observed by various commenters over
the net, it is indeed striking that no FOSS distros is in there. I plan
to contact the FSF asking that Debian is listed as an endorser of the
campaign.
As you are the Debian people working on our installer, I think it should
be done in agreement with you.
Thanks a lot for your feedback. I'll check tomorrow with the FSF if they
accept project-level subscriptions and, if they do, submit one on behalf
of Debian.
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences .. http://upsilon.cc/zack .. . . o
Debian Project Leader... @zack on identi.ca ...o o o
« the first rule of tautology club is the first rule of tautology club »
signature.asc
Description: Digital signature
Bug#670938: marked as done (flash-kernel: support is missing for LaCie Kirkwood NASes)
Your message dated Wed, 13 Jun 2012 23:48:56 + with message-id e1sexj2-x6...@franck.debian.org and subject line Bug#670938: fixed in flash-kernel 3.0~rc.5 has caused the Debian Bug report #670938, regarding flash-kernel: support is missing for LaCie Kirkwood NASes 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.) -- 670938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: flash-kernel Version: 3.0~rc.4 Severity: normal Tags: patch Dear Maintainer, uImage et uInitrd files are not generated for LaCie Kirkwood NASes. Please, consider applying the attached patch. Regards, Simon -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: armel (armv5tel) Kernel: Linux 3.2.0-00010-g0a7ba17 (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages flash-kernel depends on: ii devio1.2-1+b1 ii initramfs-tools 0.102 ii linux-base 3.5 flash-kernel recommends no packages. Versions of packages flash-kernel suggests: ii u-boot-tools 2011.12-3 -- no debconf information From 3d9c8dc8e5719d2dbf22da4fecb3005e8dc620fb Mon Sep 17 00:00:00 2001 From: Simon Guinot simon.gui...@sequanux.org Date: Thu, 26 Apr 2012 19:16:27 +0200 Subject: [PATCH] Add support for LaCie Kirkwood NASes This patch provides support for the following LaCie boards: - LaCie 2Big Network v2 - LaCie 5Big Network v2 - LaCie Internet Space v2 - LaCie Network Space v2 - LaCie Network Space Max v2 - LaCie d2 Network v2 --- README|6 ++ db/all.db | 54 ++ 2 files changed, 60 insertions(+) diff --git a/README b/README index 4eb4f35..1d2c600 100644 --- a/README +++ b/README @@ -25,6 +25,12 @@ The following systems are supported: - HP t5325 Thin Client - HP Media Vault mv2120 - Intel SS4000-E + - LaCie 2Big Network v2 + - LaCie 5Big Network v2 + - LaCie Internet Space v2 + - LaCie Network Space v2 + - LaCie Network Space Max v2 + - LaCie d2 Network v2 - Linksys NSLU2 - Marvell DB-78x00-BP Development Board - Marvell OpenRD-Base diff --git a/db/all.db b/db/all.db index 2ce4645..b7f7caa 100644 --- a/db/all.db +++ b/db/all.db @@ -116,6 +116,60 @@ Boot-Multi-Path: /boot/uImage Required-packages: u-boot-tools Bootloader-sets-root: yes +Machine: LaCie 2Big Network v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie 5Big Network v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie Internet Space v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie Network Space v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie Network Space Max v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + +Machine: LaCie d2 Network v2 +Kernel-Flavors: kirkwood +U-Boot-Kernel-Address: 0x8000 +U-Boot-Initrd-Address: 0x0 +Boot-Kernel-Path: /boot/uImage +Boot-Initrd-Path: /boot/uInitrd +Required-Packages: u-boot-tools +Bootloader-sets-root: no + # Really: Intel SS4000-e and compatibles Machine: Lanner EM7210 Method: redboot -- 1.7.9.5 ---End Message--- ---BeginMessage--- Source: flash-kernel Source-Version: 3.0~rc.5 We believe that the bug you reported is fixed in the latest version of flash-kernel, which is due to be installed in the Debian FTP archive: flash-kernel-installer_3.0~rc.5_armel.udeb to main/f/flash-kernel/flash-kernel-installer_3.0~rc.5_armel.udeb flash-kernel_3.0~rc.5.dsc to main/f/flash-kernel/flash-kernel_3.0~rc.5.dsc flash-kernel_3.0~rc.5.tar.gz to main/f/flash-kernel/flash-kernel_3.0~rc.5.tar.gz flash-kernel_3.0~rc.5_armel.deb to
Processing of flash-kernel_3.0~rc.5_armel.changes
flash-kernel_3.0~rc.5_armel.changes uploaded successfully to localhost along with the files: flash-kernel_3.0~rc.5.dsc flash-kernel_3.0~rc.5.tar.gz flash-kernel_3.0~rc.5_armel.deb flash-kernel-installer_3.0~rc.5_armel.udeb Greetings, Your Debian queue daemon (running on host franck.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/e1sex6x-0008o8...@franck.debian.org
flash-kernel_3.0~rc.5_armel.changes ACCEPTED into unstable
Accepted: flash-kernel-installer_3.0~rc.5_armel.udeb to main/f/flash-kernel/flash-kernel-installer_3.0~rc.5_armel.udeb flash-kernel_3.0~rc.5.dsc to main/f/flash-kernel/flash-kernel_3.0~rc.5.dsc flash-kernel_3.0~rc.5.tar.gz to main/f/flash-kernel/flash-kernel_3.0~rc.5.tar.gz flash-kernel_3.0~rc.5_armel.deb to main/f/flash-kernel/flash-kernel_3.0~rc.5_armel.deb Changes: flash-kernel (3.0~rc.5) unstable; urgency=low . * Add support for FK_MACHINE and FK_PROC_CPUINFO. - Makes it possible to pass machine name for use under chrooted setups. Setting FK_MACHINE to none avoids flash-kernel run. Thanks Johannes Schauer for patch. * Add support for LaCie Kirkwood NASes. Thanks Simon Guinot for patch. (Closes: #670938) Override entries for your package: flash-kernel-installer_3.0~rc.5_armel.udeb - standard debian-installer flash-kernel_3.0~rc.5.dsc - source utils flash-kernel_3.0~rc.5_armel.deb - optional utils Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 670938 Thank you for your contribution to Debian. -- 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/e1sexj2-wr...@franck.debian.org
powerpc with GPT and MD?
I want to install 6.0.5 on a powerpc platform that has a SoC-specific kernel. The platform I'm working on already has disks set up with GPTs and partitions mirrored with MD (no LVM involved; in fact it is not configured into the kernel). I copied the necessary kernel and modules to a partition, along with expanding the installer initrd. It boots from there and runs the installer. I can get to either the full DVD or netinst CD by loading the necessary modules. The problem is that the partitioning code doesn't work well enough for me to continue installing the base system. Given that I have booted the installer from one of the MDs, and that another MD is where I want to install Debian, how can I let the installer know where I want the file system installed? It is no problem for me to escape to the shell, since I do that to load the CD modules; I can format the target MD and mount it to the installer ramdisk root while I'm there, but what, if any, information can I use to tell the installer to use it? I don't mind chasing this through the source myself, if there's an anonymous git, or whatever, to acquire the source, and, of course, any changes would be returned for your consideration. Thanks, Dan Taylor Sr. Staff Engineer WD Branded Products 949.672.7761 -- 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/5a9bc72fd5cec94ea024ced8e31d701a2fd20...@wdscexmb03.sc.wdc.com
