Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
On Sun, 2010-01-24 at 17:51 -0800, Mike Castle wrote: ii debconf 1.5.28 Debian configuration management system ii debconf-i18n 1.5.28 full internationalization support for debcon Configured to use dialog ii dialog 1.1-20080819-1 Displays user-friendly dialog boxes from she It appears that the 'dialog' front-end to debconf actually uses 'whiptail' if it is installed, which it is on the systems I tried. After I removed whiptail, debconf used the dialog program and although I did not see this exact behaviour I did see some odd formatting, which I was able to correct. This should be fixed in the next upload. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
I do not have whiptail installed (saw no sense in having both dialog and whiptail installed). -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
ii debconf 1.5.28 Debian configuration management system ii debconf-i18n 1.5.28 full internationalization support for debcon Configured to use dialog ii dialog 1.1-20080819-1 Displays user-friendly dialog boxes from she mrc -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
Package: linux-2.6 Version: 2.6.32-5 Severity: minor During the upgrade process, apt-get causes a message to display that starts with this text: │ Required firmware files may be missing│ │ │ │ This system is currently running Linux 2.6.30-2-686 and you are │ │ installing Linux 2.6.32-trunk-486. In the new version some of the│ │ drivers used on this system may require additional firmware files:│ While scrolling down, I noticed the following: │ radeon/RV630_me.bin, radeon/RV630_pfp.bin, radeon/RV610_me.bin, │ │ radeon/RV610_pfp.bin, radeon/R600_me.bin, radeon/R600_pfp.bin\nr8169: │ │ rtl8168d-2.fw, rtl8168d-1.fw │ I don't think that \n is supposed to be there. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] [1106:0691] (rev c4) Subsystem: ASUSTeK Computer Inc. Device [1043:8038] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR+ INTx- Latency: 0 Region 0: Memory at fc00 (32-bit, prefetchable) [size=32M] Capabilities: access denied Kernel driver in use: agpgart-via 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] [1106:8598] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: de80-dfdf Prefetchable memory behind bridge: e000-fbff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied 00:04.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] (rev 40) Subsystem: ASUSTeK Computer Inc. Device [1043:8038] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: parport_pc 00:04.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) (prog-if 8a [Master SecP PriP]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 Region 0: [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] Region 1: [virtual] Memory at 03f0 (type 3, non-prefetchable) [size=1] Region 2: [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] Region 3: [virtual] Memory at 0370 (type 3, non-prefetchable) [size=1] Region 4: I/O ports at b800 [size=16] Capabilities: access denied Kernel driver in use: VIA_IDE 00:04.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 16) (prog-if 00 [UHCI]) Subsystem: First International Computer, Inc. VA-502 Mainboard [0925:1234] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32, Cache Line Size: 32 bytes Interrupt: pin D routed to IRQ 10 Region 4: I/O ports at b400 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:04.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 16) (prog-if 00 [UHCI]) Subsystem: First International Computer, Inc. VA-502 Mainboard [0925:1234] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32, Cache Line Size: 32 bytes Interrupt: pin D routed to IRQ 10 Region 4: I/O ports at b000 [size=32]
Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
On Sat, 2010-01-23 at 11:15 -0800, Mike Castle wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: minor During the upgrade process, apt-get causes a message to display that starts with this text: │ Required firmware files may be missing│ │ │ │ This system is currently running Linux 2.6.30-2-686 and you are │ │ installing Linux 2.6.32-trunk-486. In the new version some of the│ │ drivers used on this system may require additional firmware files:│ While scrolling down, I noticed the following: │ radeon/RV630_me.bin, radeon/RV630_pfp.bin, radeon/RV610_me.bin, │ │ radeon/RV610_pfp.bin, radeon/R600_me.bin, radeon/R600_pfp.bin\nr8169: │ │ rtl8168d-2.fw, rtl8168d-1.fw │ I don't think that \n is supposed to be there. The \n should be converted into a line-break by debconf, and I thought I saw this working when I added the code that generates such messages. However, it looks like I need to do a little more to enable that. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Bug#566539: linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update
On Sat, 2010-01-23 at 21:17 +, Ben Hutchings wrote: On Sat, 2010-01-23 at 11:15 -0800, Mike Castle wrote: Package: linux-2.6 Version: 2.6.32-5 Severity: minor During the upgrade process, apt-get causes a message to display that starts with this text: │ Required firmware files may be missing │ │ │ │ This system is currently running Linux 2.6.30-2-686 and you are │ │ installing Linux 2.6.32-trunk-486. In the new version some of the │ │ drivers used on this system may require additional firmware files: │ While scrolling down, I noticed the following: │ radeon/RV630_me.bin, radeon/RV630_pfp.bin, radeon/RV610_me.bin, │ │ radeon/RV610_pfp.bin, radeon/R600_me.bin, radeon/R600_pfp.bin\nr8169: │ │ rtl8168d-2.fw, rtl8168d-1.fw │ I don't think that \n is supposed to be there. The \n should be converted into a line-break by debconf, and I thought I saw this working when I added the code that generates such messages. However, it looks like I need to do a little more to enable that. I still can't reproduce this. Which version of debconf is installed and which front-end is enabled? Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
