kmod crashed with SIGABRT in raise()

[Rainer Rohde]

This just keeps happening... no idea what I am doing to trigger this.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: kmod 9-2ubuntu7
ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6
Uname: Linux 3.8.0-5-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 8 20:58:53 2013
ExecutablePath: /bin/kmod
MarkForUpload: True
ProcCmdline: modprobe --set-version=3.8.0-5-generic --ignore-install --quiet --show-depends nouveau
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: kmod
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_perror_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: kmod crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.modprobe.d.blacklist.framebuffer.conf: 2012-10-26T13:03:20.636589

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Vincent Ladeuil (vila)]

Encounter this one while upgrading a raring laptopn this morning, the kernel update was for 3.8.0-6-generic (instead of -5-generic for the initial bug report).

May be off-topic but chromium was launched to report the bug (while I always use firefox, chromium is installed for test purposes and not my main browser).

[Bruce Pieterse (octoquad)]

This occurred after gdk-pixbuf-query-loaders crashed twice.

[Bruce Pieterse (octoquad)]

Happened again a few moments ago when the software centre crashed and opting in for relaunch of the application.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1097462, so 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. Please continue to report any other bugs you may find.