mythbuntu-bugs team mailing list archive

[Thomas Mashos <1214269@xxxxxxxxxxxxxxxxxx>]

We really do appreciate you opening this ticket to help improve
Mythbuntu, but it needs to be closed for a number of reasons. The
biggest one is that upstream has moved on to a new version and believes
this to be fixed. Could you please verify if this issue still exists in
the latest version?

Please do not let the closing of this ticket dissuade you from opening a
new ticket if this (or any other) problem occurs with the newer
versions.

** Changed in: mythbuntu
       Status: New => Expired

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/1214269

Title:
  mythlogserver crashed with SIGSEGV

Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
  Expired

Bug description:
  Mythfrontend locks up when trying to exit. Sudo kill process did not
  appear to clear mythfrontend so rebooted and it automatically
  generated this crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: mythtv-common 2:0.26.1+fixes.20130816.016ff03-0ubuntu0mythbuntu3 [origin: LP-PPA-mythbuntu-0.26]
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic i686
  NonfreeKernelModules: nvidia
  .var.log.mythtv.mythavtest.log:
   
  .var.log.mythtv.mythbackend.log:
   
  .var.log.mythtv.mythccextractor.log:
   
  .var.log.mythtv.mythcommflag.log:
   
  .var.log.mythtv.mythfilldatabase.log:
   
  .var.log.mythtv.mythjobqueue.log:
   
  .var.log.mythtv.mythlcdserver.log:
   
  .var.log.mythtv.mythmediaserver.log:
   
  .var.log.mythtv.mythmetadatalookup.log:
   
  .var.log.mythtv.mythpreviewgen.log:
   
  .var.log.mythtv.mythshutdown.log:
   
  .var.log.mythtv.mythtranscode.log:
   
  .var.log.mythtv.mythtv.setup.log:
   
  .var.log.mythtv.mythutil.log:
   
  .var.log.mythtv.mythwelcome.log:
   
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: i386
  CrashCounter: 1
  CrashDB: mythbuntu
  Date: Tue Aug 20 16:06:42 2013
  Disassembly: => 0x0:	Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/mythlogserver
  InstallationDate: Installed on 2013-07-16 (34 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Installed_mythtv_dbg: 2:0.26.1+fixes.20130816.016ff03-0ubuntu0mythbuntu3
  MarkForUpload: True
  MythTVDirectoryPermissions:
   total 8
   drwxrwsr-x 2 mythtv mythtv 4096 Jul 16 23:24 bare-client
   drwxr-xr-x 2 root   root   4096 Nov 19  2012 videos
  ProcCmdline: /usr/bin/mythlogserver --daemon --verbose general --loglevel info --syslog local7
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:	Cannot access memory at address 0x0
   PC (0x00000000) not located in a known VMA region (needed executable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: mythtv
  Stacktrace:
   #0  0x00000000 in ?? ()
   No symbol table info available.
  StacktraceTop: ?? ()
  Title: mythlogserver crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo
  XsessionErrors:
   (nautilus:1580): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed
   (nautilus:1580): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1214269/+subscriptions