#13 v 4.6.2 errors with Jaunty

closed-fixed
nanotube
None
5
2009-08-24
2009-07-22
Paul Menchini
No

Trying to upgrade from FF 3.5 to 3.5.1 on Jaunty using Ubuntuzilla 4.6.2. Errors out with 'ERROR: could not get DBUS_SESSION_BUS_ADDRESS, notification cannot be shown.' The command line I used was 'ubuntuzilla.py -p firefox -a checkforupdategui' (with appropriate redirection). Log file attached.

Discussion

  • Paul Menchini
    Paul Menchini
    2009-07-22

     
  • nanotube
    nanotube
    2009-07-23

    Hi,
    Hmm, yea, the old code to get at the dbus session was quite a kludge.
    I have updated it to use the python dbus interface (which did not exist at the time the original was written - hence, the kludge).
    Please give it a try and see if it gives you any trouble - if not, I'll make a release.
    Attaching the .deb files (both i386 and amd64, just in case, since you didn't specify your architecture.)

     
  • nanotube
    nanotube
    2009-07-23

    • assigned_to: nobody --> nanotube
    • status: open --> pending-fixed
     
  • nanotube
    nanotube
    2009-07-23

    attached some new versions - fixed another bug, and also realized that i still need to get the dbus session manually when running from cron. but now i'm using a better method than before, so should work better. :)

     
  • Paul Menchini
    Paul Menchini
    2009-07-24

    Thanks for the quick response! I tried 4.6.3 rc2. (Using i386 version, btw.) DBUS errors gone, but still some others. See the file ubuntuzilla-4.6.3-rc2-errors.txt.

     
  • Paul Menchini
    Paul Menchini
    2009-07-24

    • status: pending-fixed --> open-fixed
     
  • nanotube
    nanotube
    2009-07-24

    hmm, weird - this worked just fine on my intrepid install...

    will try to test with a jaunty livecd in a bit.

    in the meantime, some questions:
    does this happen all the time, or just occasionally?
    does it happen only when running from cron, or also directly from a terminal?
    if you run " notify-send 'bla' " from a terminal, does that work to give you a notification?

     
  • Gargh. Answers:

    1. AFAIK, all the time.
    2. Definitely happens from the terminal. I don't yet have a run from cron with your latest code. Will have in 1/2 hour. But, older version seems to give same errors in cron as on terminal.
    3. notify-send didn't seem to work the other night when I was testing, but now seems to work. Go figure....

    Again, thanks muchly for your assistance!

     
  • nanotube
    nanotube
    2009-07-24

    hrm... maybe the notification daemon wasn't spawned - if you try again now that notify-send is working, any difference?

     
  • Paul Menchini
    Paul Menchini
    2009-07-24

    Yep! I get the notify box. However, when I click on the link, I get the "Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system." popup. And, if I try to copy the link address from the notify box and paste it into a FF address bar, nothing happens. Still, an improvement!

    I'll try closing FF and running ubuntuzilla, and will let you know what happens then....

     
  • nanotube
    nanotube
    2009-07-24

    hmm, good news. :)
    by the way, which desktop environment are you using (i mean, gnome, xfce, kde?)

     
  • Paul Menchini
    Paul Menchini
    2009-07-24

    gnome + compiz And, after closing FF and clicking the link, I get the detailed update instructions. Followed them, and now on FF 3.5.1! (Minor problems with temporarily losing my bookmarks and history, due to ^C'ing out of the root FF, rather than graceful exit, but all is now well!)

    So, I'd call it fixed, other than the link to the detailed update instructions not opening a tab/new window in an existing FF invocation.

    One other nit. I'm a programmer and have been using *nix for >25 yrs and I found the update instructions a bit dense. I eventually did figure them out though!

    And, just in case I didn't say so, overall a very nice utility! Thanks for writing and deploying it!

     
  • nanotube
    nanotube
    2009-07-24

    Cool. Well, i'll make the release then :)
    I'm installing jaunty in a VM as we speak, will do some more testing on everything...

    As to the instructions being dense - could you specify what part was hard to grok, and maybe offer some suggestions? Would appreciate your help on this. :)

     
  • nanotube
    nanotube
    2009-07-24

    hmm, it appears that the bugtracker is eating packages - the attachments are getting corrupted.
    i have uploaded the latest .debs to this ubuntuforums thread:
    http://ubuntuforums.org/showthread.php?p=7673196#post7673196

     
  • Paul Menchini
    Paul Menchini
    2009-07-25

    NT, I lost the URL where the "detailed installation instructions" live. If you'll supply, I'll comment on them.... adTHANKSvance!

     
  • nanotube
    nanotube
    2009-07-26

    everything is just on the main page (ubuntuzilla.sourceforge.net)

     
  • Paul Menchini
    Paul Menchini
    2009-07-26

    DoH! Actually, that's the problem. I had to wade through everything to find the nugget I needed. I suggest either changing the link on the notifier script to directly point to the "Update Official Mozilla Build of Firefox" section, or put this code on a separate page and point to that. (If I could choose, I'd elect the former.)

    Again, thanks for a nice product!

     
  • nanotube
    nanotube
    2009-07-27

    Hmm
    the link already points directly to the firefox update section...
    That said, you are probably right that having it on a separate page would be better.
    Sourceforge is about to phase out the current wiki system and move things over to mediawiki, so once they get that going, i'll be sure to update the pages and all.
    Thanks a lot for your help and comments!

     
  • nanotube
    nanotube
    2009-08-09

    just an update: new ubuntuzilla wiki is up. :)

     
  • nanotube
    nanotube
    2009-08-09

    • status: open-fixed --> pending-fixed
     
    • status: pending-fixed --> closed-fixed
     
  • This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).