notifications problem after detach

Bug #486511 reported by Martin Koelewijn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
byobu
Fix Released
Wishlist
Dustin Kirkland 
byobu (Ubuntu)
Fix Released
Wishlist
Dustin Kirkland 

Bug Description

Issue: run byobu, try: << notify-send "test" >> and it will work. Now detach, logout and back in, run byobu -x and try to notify-send again, I get: "libnotify-Message: Unable to get session bus: Failed to connect to socket /tmp/dbus-Ihg2aBjYyI: Connection refused"
Expected: working notifications (I use them in irssi; otherwise notifications from a terminal wouldn't be a big deal of course).
Settings: ubuntu 9.10 desktop i386; also (if it matters) e17 window manager (svn 43487) with ecomorph.

Maybe this is a problem in dbus or notify-send or even e17 or ecomorph, but I wouldn't know how to check on that.

Related branches

Revision history for this message
Martin Koelewijn (vcoolio) wrote :

To file the bug I found out about this repo, so I installed 2.39-0ubuntu1~ppa4 but the problem persists (I had the current karmic package, 2.38-0ubuntu3).

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Thanks for the report. I suspect I'll need to solve in a similar manner to how I solve the ssh socket issue.

Changed in byobu:
status: New → Triaged
importance: Undecided → Wishlist
Changed in byobu (Ubuntu):
importance: Undecided → Wishlist
assignee: nobody → Dustin Kirkland (kirkland)
Changed in byobu:
assignee: nobody → Dustin Kirkland (kirkland)
status: Triaged → In Progress
Changed in byobu (Ubuntu):
status: New → In Progress
Changed in byobu (Ubuntu):
status: In Progress → Fix Committed
Changed in byobu:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.4 KiB)

This bug was fixed in the package byobu - 2.40-0ubuntu1

---------------
byobu (2.40-0ubuntu1) lucid; urgency=low

  * bin/updates_available, statusrc: move the color coding out to the config
    file
  * byobu-config, byobu.1, po/*, profiles/common,
    profiles_generator/profile.skel, rpm/byobu.spec, statusrc:
    - add an apport hook, LP: #485380
  * bin/apport: improve the formatting of the detailed output to
    suggest installing apport if necessary
  * debian/control: suggest apport
  * bin/apport, bin/battery, bin/cpu_freq, bin/disk, bin/ec2_cost,
    bin/fan_speed, bin/hostname, bin/ip_address, bin/load_average,
    bin/logo, bin/mail, bin/mem_available, bin/mem_used, bin/menu,
    bin/network, bin/processes, bin/reboot_required, bin/release,
    bin/temp_c, bin/temp_f, bin/updates_available, bin/uptime, bin/users,
    bin/whoami, bin/wifi_quality statusrc: define a set of color variables,
    such that it's easier to make these theme-able
  * windows/common: suggest w3m rather than elinks
  * byobu-status, profiles/common, profiles_generator/profile.skel,
    statusrc: obviate the need for separate profiles per color; read the
    profile colors from a config file, and use a special "color" status
    item to dynamically render it
  * bin/menu: add a space to the -r test, LP: #490894
  * profiles_generator/profile.skel: use the reverse color for the current
    window highlighting; works better with odd color combinations, maximizes
    contrast
  * byobu-status: separate COLOR into FOREGROUND and BACKGROUND; more
    flexibility
  * byobu-config, byobu-select-profile: rework to independently select
    background color and foreground color, rather than profile; improve text
  * debian/install, debian/rules, profiles/common,
    profiles_generator/generate, profiles_generator/profile.skel,
    rpm/byobu.spec: get rid of the generated profiles; now, everything is
    handled by FOREGROUND and BACKGROUND colors, dynamically
  * byobu-janitor: clean up old ~/.byobu/profile symlinks; guess the user's
    colors and set them in ~/.byobu/colors; ensure that profile gets linked
    to the common one
  * byobu-select-profile, byobu-select-profile.1: deprecate the --set
    option, only support --background and --foreground now; update the
    documentation
  * debian/profile: establish symlinks for the color profiles to ensure
    smooth upgrades; all point to the common profile now
  * byobu-config, statusrc: enable whoami, hostname, ip_address by default;
    it seems I almost *always* turn these on, seem useful; re-disable if
    there are noisy complaints
  * byobu-janitor, statusrc: seed the ~/.byobu/status file with the
    default values, making it easier for users to customize themselves
  * bin/custom, byobu-config, byobu.1, profiles/common, rpm/byobu.spec,
    statusrc: add support for a custom status script indicator
  * byobu-config, byobu-select-profile: make color selection more readable;
    support ctrl-<space> escape sequence
  * bin/custom, byobu-status: support --detail in custom scripts
  * byobu-export, byobu-config:
    - comprehensively rewritten, basically put all of byobu's installed
      files in ~/.byobu, and use...

Read more...

Changed in byobu (Ubuntu):
status: Fix Committed → Fix Released
Changed in byobu:
status: Fix Committed → Fix Released
Revision history for this message
Martin Koelewijn (vcoolio) wrote :

Thanks for working on this. I can't try the fix because byobu 2.40 or 2.41 doesn't run on karmic (exits with error but without messages, so I don't know what to fix). I'll hopefully enjoy the improvements on lucid then...

Revision history for this message
Martin Koelewijn (vcoolio) wrote :

Hi, I installed byobu 2.43-0ubuntu1~ppa4 and this one works. But the issue is the same:
libnotify-Message: Unable to get session bus: Failed to connect to socket /tmp/dbus-Vmbvq6Wjxr: Connection refused

If you need more info than I gave on the original bug report, let me know. You understood I was talking about logout and back into an x session, and then byobu -x, right? I may not have been clear on that.
Thanks in advance for investigating.

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 486511] Re: notifications problem after detach

Okay, then I don't know how to solve this problem.

Patches welcome.

Revision history for this message
Martin Koelewijn (vcoolio) wrote :

Probably it didn't work because of some ubuntu / dbus configuration; in archlinux it works fine. Thanks.

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.