Ubuntu
fglrx-installer package

update crash

Bug #321208 reported by Benjamin corse on 2009-01-25

This bug report is a duplicate of: Bug #108189: files list file for package `*' is missing final newline. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	fglrx-installer (Ubuntu)	New	Undecided	Unassigned

Bug Description

E: /var/cache/apt/archives/fglrx-kernel-source_2%3a8.543-0ubuntu4_i386.deb: files list file for package `fglrx-kernel-source' is missing final newline

ProblemType: Package
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 8.10
ErrorMessage: files list file for package `fglrx-kernel-source' is missing final newline
Package: fglrx-kernel-source 2:8.543-0ubuntu4
ProcVersion: Linux version 2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008

SourcePackage: fglrx-installer
Title: package fglrx-kernel-source 2:8.543-0ubuntu4 failed to install/upgrade: files list file for package `fglrx-kernel-source' is missing final newline
Uname: Linux 2.6.27-9-generic i686
xkbcomp:

Tags:

Revision history for this message

Benjamin corse (hbcorse) wrote on 2009-01-25:

DpkgTerminalLog.txt Edit (387.5 KiB, text/plain; charset="utf-8")
LsMod.txt Edit (4.1 KiB, text/plain; charset="utf-8")
LsPci.txt Edit (7.6 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (1.0 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (54.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (61.8 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (7.9 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (234 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (2.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Florian Diesch (diesch) wrote on 2009-01-26:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #108189, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.