Do.exe crashed with SIGABRT in __kernel_vsyscall()

Bug #755058 reported by Jitech
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-do (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gnome-do

kill gnome-do

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-do 0.8.4-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Apr 8 23:19:23 2011
ExecutablePath: /usr/lib/gnome-do/Do.exe
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/mono
ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
ProcEnviron:
 PATH=(custom, user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-do
StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: Do.exe crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-04-02 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jitech (jitech) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-do (Ubuntu):
status: New → Confirmed
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.