totem crashed with SIGSEGV in g_io_channel_unix_new()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
totem (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Was trying to confirm Bug 855100: In the plugins tried to activate the python console (didn't work) and then clicked on Bemused I think and it crashed.
Console Output:
sergio@Sergio-L:~$ totem
/usr/lib/
import gobject._gobject
Traceback (most recent call last):
File "/usr/lib/
class PythonConsolePl
TypeError: Error when calling the metaclass bases
metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases
(totem:10164): libpeas-WARNING **: Error loading plugin 'pythonconsole'
Totem-Message: socket created
Totem-Message: bind launched
Totem-Message: listen launched
Totem-Message: io chan set
Falha de segmentação (core dumped)
ProblemType: CrashDistroRelease: Ubuntu 11.10
Package: totem 3.0.1-0ubuntu5
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Sep 20 22:58:51 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/totem
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: totem
SegvAnalysis:
Segfault happened at: 0x7f7ff2563095: mov 0x10(%rax),%rdi
PC (0x7f7ff2563095) ok
source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11SourcePackage: totem
StacktraceTop:
?? () from /lib/x86_
g_io_channel_
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
Title: totem crashed with SIGSEGV in g_io_channel_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #852882, 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.