chromium-browser crashed with SIGABRT in __kernel_vsyscall()

Bug #752850 reported by Gionn
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: chromium-browser

Closing chromium-browser

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: chromium-browser 10.0.648.204~r79063-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Apr 6 21:34:48 2011
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcCmdline: /usr/lib/chromium-browser/chromium-browser
ProcEnviron:

Signal: 6
SourcePackage: chromium-browser
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: chromium-browser crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-04-06 (0 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
XsessionErrors:
 (nm-applet:1499): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `dest_y >= 0 && dest_y + dest_height <= dest->height' failed
 (<unknown>:1479): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
 (nautilus:1488): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed
 (<unknown>:1479): libindicator-WARNING **: Unable to find group 'Gwibber Shortcut Group'
chromium-default: CHROMIUM_FLAGS=""

Revision history for this message
Gionn (giovanni.toraldo) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

Natty have reached EOL since a while and that issue is not reproducible with recent version(s); so closing that report.

Changed in chromium-browser (Ubuntu):
status: Confirmed → Invalid
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.