Yeah apport should be catching this stuff for you I believe.
On Wed, Oct 31, 2012 at 3:40 PM, Thomas Mashos
<email address hidden>wrote:
> Shouldn't the crash file already be written to /var/crash/ ?
> http://www.mythtv.org/wiki/Debugging#Ubuntu_packages
>
>
> ** Changed in: mythtv (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: mythtv (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: mythtv (Ubuntu)
> Assignee: (unassigned) => Thomas Mashos (tgm4883)
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to mythtv in Ubuntu.
> https://bugs.launchpad.net/bugs/1073580
>
> Title:
> mythtv-backend needs to run in writable directory
>
> Status in “mythtv” package in Ubuntu:
> Incomplete
>
> Bug description:
> The mythtv-backend process needs to be run in a directory that it can
> write into, ~mythtv for example. This is required so that a core file
> can be collected if/when it segfaults -- like it has been doing here.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: mythtv-backend
> 2:0.25.2+fixes.20121002.139bd59-0ubuntu0mythbuntu4 [origin:
> LP-PPA-mythbuntu-0.25]
> ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
> Uname: Linux 3.2.0-31-generic i686
> .var.log.mythtv.mythavtest.log:
>
> .var.log.mythtv.mythbackend.log:
>
> .var.log.mythtv.mythccextractor.log:
>
> .var.log.mythtv.mythcommflag.log:
>
> .var.log.mythtv.mythfrontend.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.0.1-0ubuntu13
> Architecture: i386
> CrashDB: mythbuntu
> Date: Wed Oct 31 10:07:13 2012
> Installed_mythtv_dbg: 2:0.25.2+fixes.20121002.139bd59-0ubuntu0mythbuntu4
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> SourcePackage: mythtv
> UpgradeStatus: No upgrade log present (probably fresh install)
> modified.conffile..etc.logrotate.d.mythtv.backend: [modified]
> mtime.conffile..etc.init.mythtv.backend.conf: 2012-10-31T10:05:57
> mtime.conffile..etc.logrotate.d.mythtv.backend: 2012-06-04T22:15:10
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1073580/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help : https://help.launchpad.net/ListHelp
>
Yeah apport should be catching this stuff for you I believe.
On Wed, Oct 31, 2012 at 3:40 PM, Thomas Mashos
<email address hidden>wrote:
> Shouldn't the crash file already be written to /var/crash/ ? www.mythtv. org/wiki/ Debugging# Ubuntu_ packages /bugs.launchpad .net/bugs/ 1073580 2+fixes. 20121002. 139bd59- 0ubuntu0mythbun tu4 [origin: mythbuntu- 0.25] ature: Ubuntu 3.2.0-31.50-generic 3.2.28 mythtv. mythavtest. log: mythtv. mythbackend. log: mythtv. mythccextractor .log: mythtv. mythcommflag. log: mythtv. mythfrontend. log: mythtv. mythjobqueue. log: mythtv. mythlcdserver. log: mythtv. mythmediaserver .log: mythtv. mythmetadataloo kup.log: mythtv. mythpreviewgen. log: mythtv. mythshutdown. log: mythtv. mythtranscode. log: mythtv. mythtv. setup.log: mythtv. mythutil. log: mythtv. mythwelcome. log: mythtv_ dbg: 2:0.25. 2+fixes. 20121002. 139bd59- 0ubuntu0mythbun tu4 conffile. .etc.logrotate. d.mythtv. backend: [modified] .etc.init. mythtv. backend. conf: 2012-10-31T10:05:57 .etc.logrotate. d.mythtv. backend: 2012-06-04T22:15:10 /bugs.launchpad .net/ubuntu/ +source/ mythtv/ +bug/1073580/ +subscriptions _______ _______ _______ _______ _______ _____ /launchpad. net/~mythbuntu- bugs /launchpad. net/~mythbuntu- bugs /help.launchpad .net/ListHelp
> http://
>
>
> ** Changed in: mythtv (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: mythtv (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: mythtv (Ubuntu)
> Assignee: (unassigned) => Thomas Mashos (tgm4883)
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to mythtv in Ubuntu.
> https:/
>
> Title:
> mythtv-backend needs to run in writable directory
>
> Status in “mythtv” package in Ubuntu:
> Incomplete
>
> Bug description:
> The mythtv-backend process needs to be run in a directory that it can
> write into, ~mythtv for example. This is required so that a core file
> can be collected if/when it segfaults -- like it has been doing here.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: mythtv-backend
> 2:0.25.
> LP-PPA-
> ProcVersionSign
> Uname: Linux 3.2.0-31-generic i686
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> .var.log.
>
> ApportVersion: 2.0.1-0ubuntu13
> Architecture: i386
> CrashDB: mythbuntu
> Date: Wed Oct 31 10:07:13 2012
> Installed_
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> SourcePackage: mythtv
> UpgradeStatus: No upgrade log present (probably fresh install)
> modified.
> mtime.conffile.
> mtime.conffile.
>
> To manage notifications about this bug go to:
>
> https:/
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>
--
Mario Limonciello
<email address hidden>