dpkg segfaulted during dist-upgrade when processing the tex-common package

Bug #1232176 reported by dc
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

During the upgrade to Saucy dpkg segfaulted when processing tex-common.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: tex-common 3.15
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
Date: Fri Sep 27 14:04:30 2013
InstallationDate: Installed on 2012-04-27 (518 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: tex-common
UpgradeStatus: Upgraded to saucy on 2013-09-27 (0 days ago)

Revision history for this message
dc (darkcharl) wrote :
Revision history for this message
dc (darkcharl) wrote :

Attaching the (s)trace of dpkg -i tex-common. As you can see, it explodes right after it opens /var/lib/dpkg/info/texlive-lang-all.list and calls ioctl.

Revision history for this message
dc (darkcharl) wrote :

At this point installing other packages results in a similar error. Might be due to the broken upgrade.

Revision history for this message
dc (darkcharl) wrote :

The issue appears to be stemming from ext4_fiemap()... Attached trace.

Revision history for this message
dc (darkcharl) wrote :

After reboot the issue cleared itself and I could continue the upgrade.

Revision history for this message
dc (darkcharl) wrote :

Based on the above it looks like this bug is actually kernel/ext4 related. Changing package assignment.

affects: tex-common (Ubuntu) → linux (Ubuntu)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you have a way to reproduce the bug, or was it a one time event?

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
dc (darkcharl) wrote :

Not anymore, the bug cleared itself after reboot. Before reboot I could reproduce it arbitrarily.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.