Bug 874908 - [abrt] gnome-lirc-properties-0.5.1-4.fc17: connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal was not provided by any .service files
Summary: [abrt] gnome-lirc-properties-0.5.1-4.fc17: connection.py:630:call_blocking:DB...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-lirc-properties
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:376e7467868117b66b00d8c51ad...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-09 03:56 UTC by Pablo Carle
Modified: 2013-07-31 21:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-31 21:14:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: executable (30 bytes, text/plain)
2012-11-09 03:56 UTC, Pablo Carle
no flags Details
File: dso_list (32 bytes, text/plain)
2012-11-09 03:56 UTC, Pablo Carle
no flags Details
File: environ (1.65 KB, text/plain)
2012-11-09 03:57 UTC, Pablo Carle
no flags Details
File: smolt_data (3.31 KB, text/plain)
2012-11-09 03:57 UTC, Pablo Carle
no flags Details
File: core_backtrace (1.15 KB, text/plain)
2012-11-09 03:57 UTC, Pablo Carle
no flags Details

Description Pablo Carle 2012-11-09 03:56:54 UTC
Description of problem:
yum install gnome-lirc-properties.noarch

Version-Release number of selected component:
gnome-lirc-properties-0.5.1-4.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
cmdline:        /usr/bin/python /usr/bin/gnome-lirc-properties
kernel:         3.6.5-1.fc17.x86_64

backtrace:
:connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal was not provided by any .service files
:
:Traceback (most recent call last):
:  File "/usr/bin/gnome-lirc-properties", line 31, in <module>
:    gnome_lirc_properties.run(sys.argv[1:], datadir)
:  File "/usr/lib/python2.7/site-packages/gnome_lirc_properties/__init__.py", line 59, in run
:    return ui.RemoteControlProperties(builder, datadir).run()
:  File "/usr/lib/python2.7/site-packages/gnome_lirc_properties/ui/RemoteControlProperties.py", line 53, in __init__
:    self.__setup_models()
:  File "/usr/lib/python2.7/site-packages/gnome_lirc_properties/ui/RemoteControlProperties.py", line 80, in __setup_models
:    self.__hardware_manager = hardware.HardwareManager(receivers_db)
:  File "/usr/lib/python2.7/site-packages/gnome_lirc_properties/hardware.py", line 255, in __init__
:    self.__hal = self.__bus.get_object(HAL_SERVICE, HAL_MANAGER_PATH)
:  File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 244, in get_object
:    follow_name_owner_changes=follow_name_owner_changes)
:  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 241, in __init__
:    self._named_service = conn.activate_name_owner(bus_name)
:  File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 183, in activate_name_owner
:    self.start_service_by_name(bus_name)
:  File "/usr/lib/python2.7/site-packages/dbus/bus.py", line 281, in start_service_by_name
:    'su', (bus_name, flags)))
:  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
:    message, timeout)
:DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Hal was not provided by any .service files
:
:Local variables in innermost frame:
:byte_arrays: False
:self: <dbus._dbus.SystemBus (system) at 0x135ea70>
:args: ('org.freedesktop.Hal', 0)
:utf8_strings: False
:bus_name: 'org.freedesktop.DBus'
:get_args_opts: {'byte_arrays': False, 'utf8_strings': False}
:object_path: '/org/freedesktop/DBus'
:timeout: -1.0
:signature: 'su'
:dbus_interface: 'org.freedesktop.DBus'
:message: <dbus.lowlevel.MethodCallMessage object at 0x119b228>
:method: 'StartServiceByName'

Potential duplicate bug: 701065

Comment 1 Pablo Carle 2012-11-09 03:56:58 UTC
Created attachment 641243 [details]
File: executable

Comment 2 Pablo Carle 2012-11-09 03:56:59 UTC
Created attachment 641244 [details]
File: dso_list

Comment 3 Pablo Carle 2012-11-09 03:57:01 UTC
Created attachment 641245 [details]
File: environ

Comment 4 Pablo Carle 2012-11-09 03:57:03 UTC
Created attachment 641246 [details]
File: smolt_data

Comment 5 Pablo Carle 2012-11-09 03:57:07 UTC
Created attachment 641247 [details]
File: core_backtrace

Comment 6 Fedora End Of Life 2013-07-03 20:48:49 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2013-07-31 21:14:55 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.