Mythbuntu live frontend fails to start (AttributeError: MythbuntuStartup instance has no attribute 'remote_list')

Bug #506588 reported by Ronald McCollam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mythbuntu-live-autostart (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: mythbuntu-live-autostart

Tested on 20100112.1 amd64 mythbuntu image.

When booted into the live environment, activating the desktop icon to start the live frontend has no effect. When run from the terminal, the following output is received:

ubuntu@ubuntu:~$ gksudo -k mythbuntu-startup

(mythbuntu-startup:3472): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mythbuntu-startup:3472): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mythbuntu-startup:3478): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mythbuntu-startup:3478): GVFS-RemoteVolumeMonitor-WARNING **: cannot connect to the session bus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/mythbuntu-startup", line 607, in <module>
    mythbuntu.run()
  File "/usr/bin/mythbuntu-startup", line 306, in run
    self.populate_lirc()
  File "/usr/bin/mythbuntu-startup", line 471, in populate_lirc
    self.remote_list.append_text(list[0].translate(string.maketrans('',''),','))
AttributeError: MythbuntuStartup instance has no attribute 'remote_list'

DBUS is running:
ubuntu@ubuntu:~$ service dbus status
dbus start/running, process 3240

ProblemType: Bug
Architecture: amd64
Date: Tue Jan 12 19:49:00 2010
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Mythbuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100112.1)
Package: mythbuntu-live-autostart 0.35-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SourcePackage: mythbuntu-live-autostart
Tags: lucid
Uname: Linux 2.6.32-10-generic x86_64

Revision history for this message
Ronald McCollam (fader) wrote :
tags: added: iso-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mythbuntu-live-autostart - 0.36-0ubuntu1

---------------
mythbuntu-live-autostart (0.36-0ubuntu1) lucid; urgency=low

  * Fix crashes with changes from new GTK version in lucid. (LP: #506588)
  * Fix remote selection debconf (LP: #498821)
  * Fix crash when trying to find configuration (LP: #316631)
 -- Mario Limonciello <email address hidden> Tue, 12 Jan 2010 20:53:00 -0600

Changed in mythbuntu-live-autostart (Ubuntu):
status: New → Fix Released
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.