from:"admin"

While logged in via ssh to the machine with the "hung" Xorg (screen
blank, no way to recover except Alt-SysRq-k), I dumped the output of
Alt-SysRq-t into the syslog -- see attached file. Not sure this is much
use, however. Just trying to be complete while I'm on-site with a hung
machine.

** Attachment added: "syslog with output from Alt-SysRq-t in ssh session"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117347/+files/syslog

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Bug description:
I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
LTS and 16.04. As we have gradually transitioned them to 16.04, we
have noticed that the machines running 16.04.1 now regularly exhibit
problems restoring from the blank screen which appears after a period
of inactivity.

This only occurs on the machines where we've installed 16.04. All of
the 16.04.1 installations are "fresh", that is, complete re-installs
from scratch, and we install all security and other updates on a
regular basis. This problem has persisted right from the beginning
when we started using 16.04.

Following a period of user inactivity, the screen goes blank; this is,
of course, expected. When the user tries to restore the session by
typing a key or moving the mouse, one of three outcomes occurs.

Sometimes, the session restores normally. Other times, the screen
remains blank regardless of all normal keyboard input, until a magic
SysRq sequence is performed. After Alt-SysRq-k, either the virtual
console resets to a login screen (as expected after this SysRq
sequence), or we get a kernel panic text screen (see attached screen
photo) and can only restore via a hard power-cycle reboot.

I will continue to try to capture a better trace output from one of
these conditions, perhaps from /var/log/kern.log or by installing
linux-crashdump (although these old machines may not have enough
memory for the stock package). But in the meantime, I'm attaching a
photo of the kernel panic we see, which suggests a problem may reside
in the Radeon driver ... which would seem possible, given the general
blank-screen no-resume problem on these systems.

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

Further debugging today while I'm on-site with the kiosks.  The system
froze, as usual, after normal idle screen blanking.  I was able to login
via ssh and retrieve some details.

First, it appears that the basic screen blanking problem is somehow
related to the Radeon driver.  I will attach the Xorg.0.log file and a
gdb backtrace on the running but non-responsive Xorg process.  No
keyboard or mouse activity will un-blank the screen.

Here's the output from lspci | grep VGA:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 
[Radeon X1300/X1550 Series]

I'll also attach the PCI ROM dump from the /sys/devices rom file for
this device.

This suggests that when we use Alt-SysRq-k to restore the system,
sometimes we trigger *another* bug in the driver which results in the
overall system crash.  See the attached apr1.full.kern.log file for what
details I could recover from the crash on April 1st; that corresponds to
the screen photo I took that day (the radeon_kernel_panic1.jpg
attachment).

The Xorg "hang" bug which precedes this appears similar, but not
identical, to what is documented in #1664979:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979

I will continue to try to study the live Xorg process to see if I can
determine where its hung, but I may not have time this evening.  Let me
know if there are specific further debugging steps I can take to examine
either the Xorg hang or the subsequent crash which (sometimes) follows
on attempting to recover with Alt-SysRq-k.  (And note that I'll copy in
the files apport-bug generated from #1764211 later tonight, using my
"cdarroch" personal account, and then I'll try to close that extra bug
report.)

Thanks very much,
Chris.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "Xorg.0.log"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117322/+files/Xorg.0.log

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "gdb-Xorg.txt"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117324/+files/gdb-Xorg.txt

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "rom.vga.bin"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117323/+files/rom.vga.bin

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

Further details from apport-bug are in #1764211; I'll copy them into
this account using my "cdarroch" personal Launchpad account in a few
hours, when I get home.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1764211] Re: apport bug details for #1763273 (radeon crash while screen blank)

When I get home I'll copy these attachments and data into the original
bug report under my personal Launchpad account.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1764211

Title:
  apport bug details for #1763273 (radeon crash while screen blank)

Status in xorg package in Ubuntu:
  New

Bug description:
  Unfortunately, I had to create a second bug report because apport-
  collect will not accept a different set of Launchpad user credentials
  from those I used to create the original bug report (#1763273).  My
  apologies, but I had to use a different Launchpad account to run
  apport-bug, so this is the result.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 15 18:28:07 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] [174b:e020]
 Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] (Secondary) [174b:e021]
  InstallationDate: Installed on 2017-07-24 (265 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JKT30AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr:
  dmi.product.name: 8811BJ8
  dmi.product.version: ThinkCentre M55
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 15 17:45:51 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputUSB Optical MouseMOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764211/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1764211] [NEW] apport bug details for #1763273 (radeon crash while screen blank)

Public bug reported:

Unfortunately, I had to create a second bug report because apport-
collect will not accept a different set of Launchpad user credentials
from those I used to create the original bug report (#1763273).  My
apologies, but I had to use a different Launchpad account to run apport-
bug, so this is the result.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Apr 15 18:28:07 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] [174b:e020]
   Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] (Secondary) [174b:e021]
InstallationDate: Installed on 2017-07-24 (265 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JKT30AUS
dmi.board.name: LENOVO
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr:
dmi.product.name: 8811BJ8
dmi.product.version: ThinkCentre M55
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Apr 15 17:45:51 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Keyboard KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1764211

Title:
  apport bug details for #1763273 (radeon crash while screen blank)

Status in xorg package in Ubuntu:
  New

Bug description:
  Unfortunately, I had to create a second bug report because apport-
  collect will not accept a different set of Launchpad user credentials
  from those I used to create the original bug report (#1763273).  My
  apologies, but I had to use a different Launchpad account to run
  apport-bug, so this is the result.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 15 18:28:07 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "Full kern.log from April 1 crash"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117229/+files/apr1.full.kern.log

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1763273

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+subscriptions

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] A change has been merged

Reviewed:  https://review.opencontrail.org/39136
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e2ce2e05bf864f8c96750073fc35f98cff70c386
Submitter: Zuul v3 CI (zuu...@zuul.opencontrail.org)
Branch:master

commit e2ce2e05bf864f8c96750073fc35f98cff70c386
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/trunk
   Status: In Progress => Fix Committed

** Changed in: juniperopenstack/trunk
Milestone: None => r5.0.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  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:
  Invalid

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] A change has been merged

Reviewed:  https://review.opencontrail.org/39137
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e45f84e5a28728f7c1f65935d1f28490a2ef2d70
Submitter: Zuul (z...@lists.opencontrail.org)
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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  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:
  Invalid

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] A change has been merged

Reviewed:  https://review.opencontrail.org/39136
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e2ce2e05bf864f8c96750073fc35f98cff70c386
Submitter: Zuul v3 CI (zuu...@zuul.opencontrail.org)
Branch:master

commit e2ce2e05bf864f8c96750073fc35f98cff70c386
Author: ankitja 
Date:   Mon Jan 15 15:12:41 2018 +0530

Fix attach_logs_cores issue

Closes-bug: #38694

Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  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:
  Invalid

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] A change has been merged

Reviewed:  https://review.opencontrail.org/39137
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e45f84e5a28728f7c1f65935d1f28490a2ef2d70
Submitter: Zuul (z...@lists.opencontrail.org)
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.
https://bugs.launchpad.net/bugs/38694

Title:
  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:
  Invalid

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] R4.0

Review in progress for https://review.opencontrail.org/39137 
Submitter: Ankit Jain (anki...@juniper.net)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

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

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] master

Review in progress for https://review.opencontrail.org/39136 
Submitter: Ankit Jain (anki...@juniper.net)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

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

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] R4.0

Review in progress for https://review.opencontrail.org/39137 
Submitter: Ankit Jain (anki...@juniper.net) 


** Also affects: juniperopenstack/trunk
   Importance: Undecided
   Status: New

** Also affects: juniperopenstack/trunk
   Importance: Medium
   Status: In Progress

** Also affects: juniperopenstack/r4.0
   Importance: Undecided
   Status: New

** Also affects: juniperopenstack/r4.0
   Importance: Medium
   Status: In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

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

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] master

Review in progress for https://review.opencontrail.org/39136 
Submitter: Ankit Jain (anki...@juniper.net)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

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

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] A change has been merged

2018-01-18 Thread OpenContrail Admin

Reviewed:  https://review.opencontrail.org/38895
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/f47e0cab468567a39d58cdb7cc3c5c93a4907f33
Submitter: Zuul (z...@lists.opencontrail.org)
Branch:R4.1

commit f47e0cab468567a39d58cdb7cc3c5c93a4907f33
Author: ankitja 
Date:   Mon Jan 15 15:12:41 2018 +0530

Fix attach_logs_cores issue

Closes-bug: #38694

Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

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

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] A change has been merged

2018-01-18 Thread OpenContrail Admin

Reviewed:  https://review.opencontrail.org/38895
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/f47e0cab468567a39d58cdb7cc3c5c93a4907f33
Submitter: Zuul (z...@lists.opencontrail.org)
Branch:R4.1

commit f47e0cab468567a39d58cdb7cc3c5c93a4907f33
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.1
   Status: In Progress => Fix Committed

** Changed in: juniperopenstack/r4.1
Milestone: None => r4.1.1.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

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

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] R4.1

Review in progress for https://review.opencontrail.org/38895 
Submitter: Ankit Jain (anki...@juniper.net)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

Status in Juniper Openstack:
  New
Status in Juniper Openstack r4.1 series:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Invalid

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] R4.1

Review in progress for https://review.opencontrail.org/38895 
Submitter: Ankit Jain (anki...@juniper.net)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

Status in Juniper Openstack:
  New
Status in Juniper Openstack r4.1 series:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Invalid

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] R4.1

Review in progress for https://review.opencontrail.org/38895 
Submitter: Ankit Jain (anki...@juniper.net) 


** Also affects: juniperopenstack/r4.1
   Importance: Undecided
   Status: New

** Also affects: juniperopenstack/r4.1
   Importance: Medium
   Status: In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/38694

Title:
  No XChat in Dapper

Status in Juniper Openstack:
  New
Status in Juniper Openstack r4.1 series:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  Invalid

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
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 38694] [Review update] R4.1