Submitter: Zuul (
Branch:    R4.0

commit e45f84e5a28728f7c1f65935d1f28490a2ef2d70
Author: ankitja <>
Date:   Mon Jan 15 15:12:41 2018 +0530

Fix attach_logs_cores issue

Closes-bug: #38694

Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9

** Changed in: juniperopenstack/r4.0
       Status: In Progress => Fix Committed

** Changed in: juniperopenstack/r4.0
    Milestone: None => r4.0.3.0

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.

  No XChat in Dapper

Status in Juniper Openstack:
  Fix Committed
Status in Juniper Openstack r4.0 series:
  Fix Committed
Status in Juniper Openstack r4.1 series:
  Fix Committed
Status in Juniper Openstack trunk series:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:

Bug description:
  Apparently someone made the decision to remove XChat from the default
  installation for Dapper.  This is important because it is the means
  new users use to reach the various IRC channels on Freenode and all
  the support those have to offer.  I understand that Gaim is still
  included and supports IRC, but this has a few problems as an
  alternative.  First, new users are not going to thing that Gaim
  Internet Messenger in their Applications menu has anything to do with
  getting support.  Second, setting up, connecting to, and using IRC
  isn't entirely intuitive.  Third, many people simply don't like Gaim's
  IRC UI.  Fourth, it does not have the built-in setting like XChat had
  to automatically join #ubuntu when first started.  In short, a brand
  new user is significantly less likely to manage to find the support of
  the IRC channels on their first boot of Ubuntu without XChat included
  and not knowing the ropes pretty well already.  The IRC channels are
  an absolutely vital way of helping new users, and must be very easily
  accessible.  Inclusion of XChat is a big step towards that.  (Further
  UI setup for first boot are an issue as well, but that's a separate

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to