muon-discover crashed with SIGSEGV in QApt::Backend::availablePackages()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
muon (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I was opening Muon Package manager it suddenly crashed and closed.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: muon-discover 4:5.4.1-0ubuntu1
ProcVersionSign
Uname: Linux 4.2.0-12-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Oct 1 11:18:07 2015
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2015-09-29 (1 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=es
PATH=(custom, no user)
XDG_RUNTIME_
LANG=es_CL.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f6604cbaff0: mov (%rsi),%rax
PC (0x7f6604cbaff0) ok
source "(%rsi)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%rax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: muon
StacktraceTop:
?? () from /usr/lib/
QApt::
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: muon-discover crashed with SIGSEGV in QApt::Backend:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
(process:1680): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
(firefox:1680): Gtk-WARNING **: Theme directory apps/system-
(firefox:1680): Gtk-WARNING **: Theme directory apps/toolbar of theme breeze has no size field
(firefox:1680): Gtk-WARNING **: Theme directory categories/
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 #1495016, 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.