Ubuntu
gnomeradio package

gnomeradio crashed with SIGSEGV in g_closure_invoke()

Bug #450640 reported by yalcin on 2009-10-13

This bug report is a duplicate of: Bug #1110660: [SRU] gnomeradio crashed with SIGABRT in __libc_message(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnomeradio (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: gnomeradio

Check your settings and make sure that no other
program is using /dev/radio.
Also make sure that you have read-access to it

ProblemType: Crash
Architecture: amd64
Date: Tue Oct 13 22:05:13 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnomeradio
Package: gnomeradio 1.8-1
ProcCmdline: gnomeradio
ProcEnviron:
LANG=tr_TR.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
SegvAnalysis:
Segfault happened at: 0x40d9b2: mov 0x70(%rax),%r12
PC (0x0040d9b2) ok
source "0x70(%rax)" (0x00000070) not located in a known VMA region (needed readable region)!
destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnomeradio
StacktraceTop:
?? ()
g_closure_invoke ()
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist ()
g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: gnomeradio crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-13-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

yalcin (yalcinbedirhan) wrote on 2009-10-13:

Dependencies.txt Edit (4.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (574 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (63.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (772 bytes, text/plain; charset="utf-8")
Registers.txt Edit (865 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (3.1 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (8.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Marc Deslauriers (mdeslaur) wrote on 2009-10-14:

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.