Bug 500410 - puplet dies with a traceback
Summary: puplet dies with a traceback
Keywords:
Status: CLOSED DUPLICATE of bug 480339
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pirut
Version: 5.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-12 15:32 UTC by Alexander Todorov
Modified: 2013-04-12 20:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-01 11:02:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Todorov 2009-05-12 15:32:27 UTC
Description of problem:
$ /usr/bin/puplet 
Introspect error: The name edu.duke.linux.yum was not provided by any .service files
Traceback (most recent call last):
  File "/usr/bin/puplet", line 467, in ?
    main()
  File "/usr/bin/puplet", line 464, in main
    p.run()
  File "/usr/bin/puplet", line 451, in run
    self._refreshInfo()
  File "/usr/bin/puplet", line 191, in _refreshInfo
    if self.updatesObject is not None and \
AttributeError: DBusException instance has no attribute '_dbus_error_name'


Version-Release number of selected component (if applicable):
pirut-1.3.28-13.el5

How reproducible:
Always

Steps to Reproduce:
1. System is registered to RHN
2. run /usr/bin/puplet 
3.
  
Actual results:
Traceback

Expected results:
Successful execution

Additional info:
IIRC puplet is the application which shows a notification icon in GNOME that there are pending updates. Since this used to work in previous releases I'm marking it as regression.

I have additional repos if that matters.

Comment 3 Andrew Gormanly 2009-06-17 10:55:27 UTC
Possible dupe of bug 480339

Comment 4 Alexander Todorov 2009-07-01 10:59:05 UTC
*** Bug 508840 has been marked as a duplicate of this bug. ***

Comment 5 Alexander Todorov 2009-07-01 11:02:19 UTC

*** This bug has been marked as a duplicate of bug 480339 ***


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