mythfrontend.real crashed with SIGABRT in raise()

Bug #1018410 reported by bance
130
This bug affects 30 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Expired
Undecided
Unassigned

Bug Description

  297.559694] mythfrontend.re[3842]: segfault at 0 ip b54d2b73 sp a8bfde00 error 4 in libQtCore.so.4.8.1[b5446000+2d4000]
[ 299.108486] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-frontend 2:0.25.0+fixes.20120622.73bc45e-0ubuntu0mythbuntu4 [origin: LP-PPA-mythbuntu-0.25]
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
Uname: Linux 3.2.0-25-generic-pae i686
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythtranscode.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
CrashDB: mythbuntu
Date: Wed Jun 27 15:20:31 2012
ExecutablePath: /usr/bin/mythfrontend.real
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
Installed_mythtv_dbg: 0.0
ProcCmdline: /usr/bin/mythfrontend.real --syslog local7
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: mythtv
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 qt_message_output(QtMsgType, char const*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 qFatal(char const*, ...) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
Title: mythfrontend.real crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin mythtv plugdev sambashare sudo
XsessionErrors:
 (compiz:4096): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed
 (gnome-settings-daemon:4079): power-plugin-WARNING **: failed to turn the panel on: Could not change DPMS mode
 (gnome-settings-daemon:4079): power-plugin-WARNING **: failed to turn the panel on: Could not change DPMS mode
 (gnome-settings-daemon:4079): power-plugin-WARNING **: failed to turn the panel on: Could not change DPMS mode
 (gnome-settings-daemon:4079): power-plugin-WARNING **: failed to turn the panel on: Could not change DPMS mode

Revision history for this message
bance (bance) wrote :
Revision history for this message
Steff (s-teff) wrote :

Had the same problem while Internet was down.

When internet worked again mythfrontend started up and presented a message to update the Theme.

Revision history for this message
paul summers (paulsum) wrote :

nothing really special, i was exiting mythfront end with the esc key, (it was 8:30, and a more recordings were taking place, and the cpu usage was using 3 processors on high.... )

so I think it was a caused by a "traffic jam"... this bug has never happen to me before... I think it is a non-bug...

Revision history for this message
Peter Marshall (peter-marshall) wrote :

Crashed when exiting front end using escape key. No recording taking place, just updated software, so that may have a bearing.

Revision history for this message
Henry Ivey (hnivideo) wrote :

Crashed when exiting front end using escape key. No recording taking place, just updated software.

Revision history for this message
Thomas Mashos (tgm4883) wrote :

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
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.