kmod crashed with SIGABRT in raise()

Bug #1101116 reported by Toni
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kmod (Ubuntu)
New
Undecided
Unassigned

Bug Description

kmod crash on login gnome session
nvidia-310

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: kmod 9-2ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Wed Jan 16 10:40:56 2013
ExecutablePath: /bin/kmod
InstallationDate: Installed on 2011-04-07 (652 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
MarkForUpload: True
ProcCmdline: modprobe --set-version=3.8.0-0-generic --ignore-install --quiet --show-depends nouveau
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=es_ES.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: kmod
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: kmod crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-01-07 (10 days ago)
UserGroups:

mtime.conffile..etc.modprobe.d.blacklist.conf: 2011-08-04T10:35:19.018341

Revision history for this message
Toni (antoniovx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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