[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Lonnie Lee Best]

This is still an issue in Ubuntu 20.04.

Instead of remembering my preference of wanting to use my television's
speakers as output, each time I reboot, the laptop's internal speakers
are set to be the output device instead.

I'm astonished that after all this time this is still not fixed.

How hard can this be to fix? When someone changes the output device,
save that setting to a file! When the user reboots, access that file and
set it to whatever their saved preference was if that device is
currently connected.

The status of this is Fix Released? Then why doesn't this still not work
in Ubuntu 20.04 LTS. LTS stands for Long Term Support, not Long Tardy
Support!

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Lonnie Lee Best]

I have 2 4K monitors, that do not even have speakers hooked up to them
(but they apparently have Audio Controllers). Ubuntu 19.10 gnome-
control-center chooses one of these speakerless monitors over my
Laptop's built-in speakers on each reboot. It will not persist my
preference.

Screenshot: https://i.stack.imgur.com/kLYWy.png
AskUbuntu: https://askubuntu.com/questions/1183052/

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Lonnie Lee Best]

This work-around is working for me:
https://askubuntu.com/a/1183074/256054

However, this is only a work-around and the bug remains.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1765726] [NEW] libgoo-canvas-perl [needs-packaging]

[Lonnie Lee Best]

Public bug reported:

The ability to edit screenshots using shutter has been broken because
Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its
repository anymore:

https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-desktop 1.417
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 20 09:05:10 2018
InstallationDate: Installed on 2018-04-17 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic needs-packaging

-- 
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/1765726

Title:
  libgoo-canvas-perl [needs-packaging]

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The ability to edit screenshots using shutter has been broken because
  Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its
  repository anymore:

  https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 09:05:10 2018
  InstallationDate: Installed on 2018-04-17 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1765726/+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 1765726] Re: libgoo-canvas-perl [needs-packaging]

[Lonnie Lee Best]

sudo apt-get install shutter

If you launch shutter from the command line it notifies these warnings:

WARNING: Goo::Canvas/libgoo-canvas-perl is missing --> drawing tool will
be disabled!

WARNING: Image::ExifTool is missing --> writing Exif information will be
disabled!

WARNING: Gtk2::AppIndicator is missing --> there will be no icon showing
up in the status bar when running Unity!

-- 
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/1765726

Title:
  libgoo-canvas-perl [needs-packaging]

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The ability to edit screenshots using shutter has been broken because
  Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its
  repository anymore:

  https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 20 09:05:10 2018
  InstallationDate: Installed on 2018-04-17 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1765726/+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 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus

[Lonnie Lee Best]

** Tags added: bionic

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

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1723403/+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 1770889] [NEW] Bad webm vp9 Performance as You Skip Ahead

[Lonnie Lee Best]

Public bug reported:

For videos encoded with VP9 .webm, it takes Totem a long time to resume
playback if you skip ahead to later portions of the video.

When the very same videos are opened in the browser (Using either
firefox or chromium), skipping ahead resumes playback quickly.

Testing:

To test this, try converting a long video to vp9 webm. For example, you
can convert an avi to webm using ffmpeg like this:

#Set threads to the number of real cores minus 1 (I just set it to 3 below) :
ffmpeg -i input.avi -c:v libvpx-vp9 -threads 3 -lossless 1 output.webm

#You can also convert a whole folder of avi to webm like this:
for file in *.avi; do ffmpeg -i "$file" -c:v libvpx-vp9 -threads 3 -lossless 1 
"${file%avi}webm"; done

After this, try playing those videos in Totem and skip around the video
to see poor resume performance.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 12 13:52:36 2018
InstallationDate: Installed on 2018-05-12 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Bad webm vp9 Performance as You Skip Ahead

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  For videos encoded with VP9 .webm, it takes Totem a long time to
  resume playback if you skip ahead to later portions of the video.

  When the very same videos are opened in the browser (Using either
  firefox or chromium), skipping ahead resumes playback quickly.

  Testing:

  To test this, try converting a long video to vp9 webm. For example,
  you can convert an avi to webm using ffmpeg like this:

  #Set threads to the number of real cores minus 1 (I just set it to 3 below) :
  ffmpeg -i input.avi -c:v libvpx-vp9 -threads 3 -lossless 1 output.webm

  #You can also convert a whole folder of avi to webm like this:
  for file in *.avi; do ffmpeg -i "$file" -c:v libvpx-vp9 -threads 3 -lossless 
1 "${file%avi}webm"; done

  After this, try playing those videos in Totem and skip around the
  video to see poor resume performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May 12 13:52:36 2018
  InstallationDate: Installed on 2018-05-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1770889/+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 1771062] [NEW] LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

[Lonnie Lee Best]

Public bug reported:

After Ubuntu 16.04.4 turns off my monitor (due to inactivity time out),
I cannot get it to come back on without rebooting.

Monitor: LG 27UK650
Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon May 14 01:15:22 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
 nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
 virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
 virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
InstallationDate: Installed on 2018-05-12 (2 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: System76 Bonobo WS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=905343e7-683c-43f3-9ee8-b5e8909f865b ro acpi_backlight=vendor quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Bonobo WS
dmi.board.vendor: System76
dmi.board.version: bonw13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Bonobo WS
dmi.product.version: bonw13
dmi.sys.vendor: System76
version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon May 14 01:02:31 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-bug compiz-0.9 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/1771062

Title:
  LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Status in xorg package in Ubuntu:
  New

Bug description:
  After Ubuntu 16.04.4 turns off my monitor (due to inactivity time
  out), I cannot get it to come back on without rebooting.

  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
   
  Com

[Touch-packages] [Bug 1771062] Re: LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

[Lonnie Lee Best]

The work-arounds below did not work for me:
https://askubuntu.com/questions/873589/

-- 
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/1771062

Title:
  LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Status in xorg package in Ubuntu:
  New

Bug description:
  After Ubuntu 16.04.4 turns off my monitor (due to inactivity time
  out), I cannot get it to come back on without rebooting.

  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 14 01:15:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=905343e7-683c-43f3-9ee8-b5e8909f865b ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon May 14 01:02:31 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771062/+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 1771062] Re: LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

[Lonnie Lee Best]

** Description changed:

- After Ubuntu 16.04.4 turns off my monitor (due to inactivity time out),
- I cannot get it to come back on without rebooting.
+ After Ubuntu 16.04.4 turns off my monitor (due to inactivity timeout), I
+ cannot get it to come back on without rebooting.
  
  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
-  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
+  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 14 01:15:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
-  nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
-  virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
-  virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
+  bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
+  nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
+  virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
+  virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
-Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
+  NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
+    Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=905343e7-683c-43f3-9ee8-b5e8909f865b ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon May 14 01:02:31 2018
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

-- 
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/1771062

Title:
  LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Status in xorg package in Ubuntu:
  New

Bug description:
  After Ubuntu 16.04.4 turns off my monitor (due to inactivity timeout),
  I cannot get it to come back on without rebooting.

  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

  Probl

[Touch-packages] [Bug 465689] Re: Ubuntu Clock Won't Show Year

[Lonnie Lee Best]

Will I ever be able to convenience people that "show year" is actually a
useful feature when taking screenshots over time?

Now, that I've upgraded to Ubuntu 18.04 and GNOME 3.28, it looks like
I'll have to start this 2009 battle all over again. It will not allow me
to format the clock the way I want it to display.

In Unity, I could at least achieved my desired clock format with a
command:

gsettings set com.canonical.indicator.datetime time-format "'custom'" ;
gsettings set com.canonical.indicator.datetime custom-time-format "'%A |
%m-%d-%Y | %l:%M%p'"

In GNOME 3.28 on Ubuntu 18.04, I've yet to figure out a way to achieved
my desired format. The GUI doesn't offer "show year" and I've yet to
discover a command (like the one above) that achieves the exact custom
format I desire.

** Tags added: bionic

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/465689/+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 465689] Re: Ubuntu Clock Won't Show Year

[Lonnie Lee Best]

I was ultimately able to achieve my exactly desired format using a GNOME
extension made by Daniel Khodabakhsh. Thank you Daniel!

I found that here:
https://github.com/Daniel-Khodabakhsh/datetime-format

Screenshot:
http://neartalk.com/ss/2018-04-06_003_1919x1079.png

Format:
%A | %m-%d-%G | %I:%M %p

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

Title:
  Ubuntu Clock Won't Show Year

Status in GNOME Panel:
  In Progress
Status in Indicator Date and Time:
  Fix Released
Status in gnome-panel package in Ubuntu:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  indicator-datetime, Ubuntu 12.10

  The Ubuntu menu bar clock offers no setting to "show year".

  Yes, I know what year it is, but I have very good reason for wanting
  it shown. For years, I've been collecting screen-shots, when I'm doing
  something I think is pretty cool. When I use to use windows, these
  screen shots (over the years) have always showed the current year.

  However, since April of 2007 (The date I started using Ubuntu
  exclusively), my screen shots have not included the year, because the
  Gnome clock doesn't provide this capability.

  : "'Year' should be both
  insensitive and unchecked whenever 'Date and month' is unchecked..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/465689/+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 1771062] Re: LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

[Lonnie Lee Best]

A clean install of 16.04 has fixed this issue for me.

-- 
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/1771062

Title:
  LG 27UK650 Monitor Won't Come Back On After Inactivity Turn Off

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After Ubuntu 16.04.4 turns off my monitor (due to inactivity timeout),
  I cannot get it to come back on without rebooting.

  Monitor: LG 27UK650
  Specs:   
http://www.lg.com/us/support/products/documents/27UK650-W%20Spec%20Sheet.pdf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 14 01:15:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-41-generic, x86_64: installed
   nvidia-384, 384.111, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.13.0-41-generic, x86_64: installed
   virtualbox, 5.1.34, 4.4.0-124-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1be1] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:087a]
  InstallationDate: Installed on 2018-05-12 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=905343e7-683c-43f3-9ee8-b5e8909f865b ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon May 14 01:02:31 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771062/+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 1789717] [NEW] Totem Won't Play AV1 Video

[Lonnie Lee Best]

Public bug reported:

Totem cannot yet play the new AV1 format (an open and royalty-free video coding 
format):
https://en.wikipedia.org/wiki/AV1

Sample videos can be download from here for testing:
https://www.elecard.com/videos

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Aug 29 14:01:52 2018
InstallationDate: Installed on 2018-07-19 (41 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Totem Won't Play AV1 Video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Totem cannot yet play the new AV1 format (an open and royalty-free video 
coding format):
  https://en.wikipedia.org/wiki/AV1

  Sample videos can be download from here for testing:
  https://www.elecard.com/videos

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 29 14:01:52 2018
  InstallationDate: Installed on 2018-07-19 (41 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1789717/+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 1273752] Re: Can't Copy Crash Report Details to Clipboard

[Lonnie Lee Best]

This bug was submitted 4 years ago and still applies to each additional
Ubuntu release.

What is the next step that could actually contribute progress on this
issue?

To me it is kind of ironic that a bug regarding the bug reporting system
itself could go so long unfixed.

** Tags added: artful bionic

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

Title:
  Can't Copy Crash Report Details to Clipboard

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Often times, after receiving a crash report, if I click the "Continue"
  button it doesn't launch the browser for me to submit my crash to
  launchpad.net.

  Because of this, I'd always like to copy the crash report to my
  clipboard before clicking the continue button, so that I can manually
  provide this information into a bug report to launchpad.net.

  However, this option is not available.

  More over, there is absolutely *no way* to copy any text from this
  crash report's dialog window!

  1) You cannot ctrl-a to select all.
  2) Ctrl-c doesn't copy anything
  3) Right-clicking doesn't produce a context menu where you can select "Copy".

  This is an unfinished design. You should always give the user the
  ability to copy any text displayed in the UI.

  Next to the "Show/Hide details" button, I suggest adding a "Copy to
  Clipboard" button. If not this, please offer some way to achieve this
  from the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:

  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 28 10:21:00 2014
  InstallationDate: Installed on 2013-10-07 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+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 1403293] Re: Unity Dash can't understand "logout", "reboot", or "shutdown"

[Lonnie Lee Best]

** Tags added: wily

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

Title:
  Unity Dash can't understand "logout", "reboot", or "shutdown"

Status in Unity:
  Triaged
Status in Unity Applications Lens:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  This bug proposes the additional surfacing of power-management and
  session actions directly within the Dash:

    - Reboot ("restart" is another good alias for this)
    - Shutdown (other intuitive aliases: "shut down", "turn off")
    - logout (aliases: "log out", "log off" and "logoff")
    - Suspend/hibernate
    - Lock
    - Switch User

  Currently these user-initiated actions are presented via the Devices
  (cog/gear-icon-menu), and can be accessed via the keyboard using
  either:

    1. [Alt]+[F10] [Left] [Up/Down] [Enter]
    2. [Alt] "Shutdown"/"Log out" [Up/Down] [Enter]
    3. [Ctrl]+[Alt]+[Del] [Enter]  ("Log off" only)
    4. [Ctrl]+[Alt]+[t] "sudo reboot" [Enter]

  (Note that "Restart"/"Reboot" can not be accessed directly via 1-3).

  These methods are less likely to be found by the user than surfacing these 
actions additionally within the Dash.  This would help in cases where a 
mouse/pointer is no longer available, such as "mouse-cursor did not appear 
after logging in to the Unity Desktop"
    https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

  This would also assist with "ctrl-alt-delete doesn't provide a reboot option"
    https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289

  It is proposed by surfacing these options in the Unity Dash, that
  finding the actions would be more intuitive, and would make the Dash
  feel more complete as the defacto first-point-of-call for user
  initiated actions.

  Implementation possibilities:

    1. Hard-code special-case actions into the Dash (requires Design review, 
code and ship acceptance)
    2. Implement as Dash plugin (requires code and ship acceptance)
    3. Install additional .desktop listing the Name, Icon and Aliases in 
/usr/share/applications/*.desktop (can be provided by a separate optional 
package, only requires ship acceptance)

  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1403293/+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 437429] Re: No GUI to configure/disable login sound

[Lonnie Lee Best]

I wish this was more like Windows 7. See "Play Windows Startup Sound" :
http://neartalk.com/ss/2015-06-08_004_1294x554.png

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

Title:
  No GUI to configure/disable login sound

Status in GDM: The Gnome Display Manager:
  Unknown
Status in gdm package in Ubuntu:
  Fix Released
Status in ubuntu-sounds package in Ubuntu:
  Invalid
Status in gdm source package in Lucid:
  Fix Released
Status in ubuntu-sounds source package in Lucid:
  Invalid

Bug description:
  ==
  WORKAROUNDS
  ==
  NOTE: These workarounds disable the "system ready" sound (the drums). They 
will not disable the "successful login" and "logout" sounds. Go to Settings -> 
Sounds and set the sound theme to "no sounds" to disable these.

  1) Disable all sounds for the login screen via gconf
  $ sudo su gdm -c "gconftool-2 --set /desktop/gnome/sound/event_sounds --type 
bool false"

  -OR-

  2) Rename the system-ready.ogg sound file
  $ sudo mv -v /usr/share/sounds/ubuntu/stereo/system-ready.ogg{,.disabled}

  ==
  BUG
  ==
  When you log into Karmic using a Gnome session, you get a drum sound.  There 
are many situations where you need a silent boot process, but it appears that 
this is impossible under Karmic.

  In Jaunty and previous, you could configure gdm to log you in
  silently.  This configuration has been removed from Karmic.  Even
  opening Sound Preferences and choosing "No sounds" for "Sound theme"
  or disabling window and button sounds does not prevent the login sound
  from occurring.

  Users must have the ability to login silently.

  Package: xsplash 0.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: xsplash
  Uname: Linux 2.6.31-11-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/437429/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

I'm amazed that a bug of this bug's fundamental importance gets
introduced during a Long Term Support release.

On top of that surprise, 6 months later, I'm still waiting on the fix.

This is fundamental stuff that should be tested before moving Ubuntu to
a later version of Network-Manager in a long term release.

Network Manager 1.1.93-0ubuntu4 was stable and should have remained
default in Ubuntu 16.04.2 until the issues in this bug report were
tested and fixed in later versions.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

Please take a look at these too:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611

and

https://bugs.launchpad.net/network-manager-applet/+bug/1633877

All are closely related, but each specifies diferent aspects that need
to be checked-off as this is being fixed.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

@gatoguan-os : You must have been speaking about the work-around here?
https://bugs.launchpad.net/network-manager-applet/+bug/1633874

Is the above really a duplicate or not?

Lately, I have not even been able to get that work-around (in the link
above) to work in 16.04.

Also, this is a related bug, but not exactly what's reported here (it might be 
a ramification of what's reported here):
https://bugs.launchpad.net/network-manager-applet/+bug/1633877

Right? I hope all these ramifications get fixes.

@tmus : I wonder if 1.4.4-1ubuntu3 will make it into 16.04 (Long term
release).

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

Related:

- https://bugs.launchpad.net/network-manager-applet/+bug/1633874

- https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611

** This bug is no longer a duplicate of bug 1629611
   dns server priority broken

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1273752] Re: Can't Copy Crash Report Details to Clipboard

[Lonnie Lee Best]

** Tags added: xenial yakkety zesty

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

Title:
  Can't Copy Crash Report Details to Clipboard

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Often times, after receiving a crash report, if I click the "Continue"
  button it doesn't launch the browser for me to submit my crash to
  launchpad.net.

  Because of this, I'd always like to copy the crash report to my
  clipboard before clicking the continue button, so that I can manually
  provide this information into a bug report to launchpad.net.

  However, this option is not available.

  More over, there is absolutely *no way* to copy any text from this
  crash report's dialog window!

  1) You cannot ctrl-a to select all.
  2) Ctrl-c doesn't copy anything
  3) Right-clicking doesn't produce a context menu where you can select "Copy".

  This is an unfinished design. You should always give the user the
  ability to copy any text displayed in the UI.

  Next to the "Show/Hide details" button, I suggest adding a "Copy to
  Clipboard" button. If not this, please offer some way to achieve this
  from the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:

  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 28 10:21:00 2014
  InstallationDate: Installed on 2013-10-07 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+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 1676385] [NEW] indicator-datetime crashed

[Lonnie Lee Best]

Public bug reported:

I was not aware that this crashed happened, but I thought I'd report it
anyway, because I was prompted to submit this crash report. Maybe the
auto-collection of data regarding this crash will be helpful.

ProblemType: RecoverableProblem
DistroRelease: Ubuntu 17.04
Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
BadURL: appid://ubuntu-clock-app/ubuntu-clock-app/current-user-version
CurrentDesktop: Unity:Unity8
Date: Mon Mar 27 04:54:20 2017
DuplicateSignature: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url
ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
ExecutableTimestamp: 1490207290
InstallationDate: Installed on 2017-01-30 (56 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
ProcCwd: /home/lonnie
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-datetime
UpgradeStatus: Upgraded to zesty on 2017-03-27 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-recoverableproblem need-duplicate-check zesty

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

Title:
  indicator-datetime crashed

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I was not aware that this crashed happened, but I thought I'd report
  it anyway, because I was prompted to submit this crash report. Maybe
  the auto-collection of data regarding this crash will be helpful.

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  BadURL: appid://ubuntu-clock-app/ubuntu-clock-app/current-user-version
  CurrentDesktop: Unity:Unity8
  Date: Mon Mar 27 04:54:20 2017
  DuplicateSignature: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ExecutableTimestamp: 1490207290
  InstallationDate: Installed on 2017-01-30 (56 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcCwd: /home/lonnie
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1676385/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state

[Lonnie Lee Best]

I'm just started experiencing this in 16.04 this evening.

** Tags added: xenial

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

Title:
  Volume Slider Jumps, due to rapidly changing hardware jack sense state

Status in alsa-driver package in Ubuntu:
  Triaged

Bug description:
  In Oneiric Release,  The volume slider randomly jump down a notch or
  two for fraction of  a second, even when there is no audio playing on
  the system.  If mute is selected, the menu will quickly flip out of
  mute mode and back again.  This change actually affects the audio
  output, resulting in pops correlated with the volume changes.

  nVidia GF106 Audio Controller
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jfrorie9959 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1462522c,00100302'
 Controls  : 35
 Simple ctrls  : 20
  Card2.Amixer.info:
   Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card2.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Package: pulseaudio 1:1.0-0ubuntu3.1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-14-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/16/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V25.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X58A-GD45 (MS-7522)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
  dmi.product.name: MS-7522
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

Can someone please address this issue?

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1825959 ***
https://bugs.launchpad.net/bugs/1825959

** This bug has been marked a duplicate of bug 1825959
   Missing "Additional Search Domain" Feature

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1825965 ***
https://bugs.launchpad.net/bugs/1825965

** This bug has been marked a duplicate of bug 1825965
   Missing "Additional DNS Servers"

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1075405] Re: Sound Only From Right Speaker after Upgrade

[Lonnie Lee Best]

That's ok. I've had 8 years to acclimate myself to right-speaker-only
audio. At this point, I wouldn't have it any other way!

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

Title:
  Sound Only From Right Speaker after Upgrade

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 12.04 to Ubuntu 12.10, my laptop's sound
  will only come from its right speaker (despite that the balance is
  centered).

  ALSA Info:
  http://www.alsa-project.org/db/?f=c964bb7dd7d08f5e86818c56533dc519c45291fd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1075405/+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 1075405] Re: Sound Only From Right Speaker after Upgrade

[Lonnie Lee Best]

No Marcus. I was just teasing. All is well. Thanks for your concern.

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

Title:
  Sound Only From Right Speaker after Upgrade

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 12.04 to Ubuntu 12.10, my laptop's sound
  will only come from its right speaker (despite that the balance is
  centered).

  ALSA Info:
  http://www.alsa-project.org/db/?f=c964bb7dd7d08f5e86818c56533dc519c45291fd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1075405/+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 1273752] Re: Can't Copy Crash Report Details to Clipboard

[Lonnie Lee Best]

@Ola Asfalt: Thanks for telling me where these details can be copied.

Never the less, (though) however, the purpose of this bug report is so
that a normal user of Ubuntu doesn't have to be told by Ola Asfalt in a
bug report, where to find the details of a crash.

It should be copy and paste. Don't show a user text he cannot copy and
paste. This a golden rule that should be followed.

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

Title:
  Can't Copy Crash Report Details to Clipboard

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Often times, after receiving a crash report, if I click the "Continue"
  button it doesn't launch the browser for me to submit my crash to
  launchpad.net.

  Because of this, I'd always like to copy the crash report to my
  clipboard before clicking the continue button, so that I can manually
  provide this information into a bug report to launchpad.net.

  However, this option is not available.

  More over, there is absolutely *no way* to copy any text from this
  crash report's dialog window!

  1) You cannot ctrl-a to select all.
  2) Ctrl-c doesn't copy anything
  3) Right-clicking doesn't produce a context menu where you can select "Copy".

  This is an unfinished design. You should always give the user the
  ability to copy any text displayed in the UI.

  Next to the "Show/Hide details" button, I suggest adding a "Copy to
  Clipboard" button. If not this, please offer some way to achieve this
  from the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:

  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 28 10:21:00 2014
  InstallationDate: Installed on 2013-10-07 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+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 1273752] Re: Can't Copy Crash Report Details to Clipboard

[Lonnie Lee Best]

Here's another example:
http://neartalk.com/ss/2015-02-01_019_827x523.png

Remmina has been crashing like crazy. When I send this report it does
not pull up bugs.launchpad.net for me to detail what was happening when
the crash happened. I have no clue whether the bug report is getting
sent to bugs.launchpad.net or not.

Plus, getting back to the top of this bug, you can't copy any of the
information details from this dialog. I'd expect this kind of crap from
Microsoft Windows, but not Ubuntu!

Please add an option to this dialog so I can *copy details to
clipboard*, so that I can file an explicit bug report after the the "
Send error report" feature fails to launch bugs.launchpad.net

I never want to see any text on my screen that I cannot copy and paste!
This is UI 101 stuff.

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

Title:
  Can't Copy Crash Report Details to Clipboard

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Often times, after receiving a crash report, if I click the "Continue"
  button it doesn't launch the browser for me to submit my crash to
  launchpad.net.

  Because of this, I'd always like to copy the crash report to my
  clipboard before clicking the continue button, so that I can manually
  provide this information into a bug report to launchpad.net.

  However, this option is not available.

  More over, there is absolutely *no way* to copy any text from this
  crash report's dialog window!

  1) You cannot ctrl-a to select all.
  2) Ctrl-c doesn't copy anything
  3) Right-clicking doesn't produce a context menu where you can select "Copy".

  This is an unfinished design. You should always give the user the
  ability to copy any text displayed in the UI.

  Next to the "Show/Hide details" button, I suggest adding a "Copy to
  Clipboard" button. If not this, please offer some way to achieve this
  from the GUI.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport-gtk 2.13.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  NonfreeKernelModules: wl
  ApportLog:

  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 28 10:21:00 2014
  InstallationDate: Installed on 2013-10-07 (113 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+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 1403293] Re: Unity Dash can't understand "logout", "reboot", or "shutdown"

[Lonnie Lee Best]

@Andrea Azzarone

Why did you mark this as "Incomplete" in Unity? This is absolutely
complete and can be verified by any existing user of Unity.

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

Title:
  Unity Dash can't understand "logout", "reboot", or "shutdown"

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  In their efforts to make the Unity Dash the "goto place for everything
  you want to do", the developers have over looked 3 fundamental tasks
  that a user might intuitively try to achieve with the unity dash:

    - Reboot ("restart" is another good alias for this)
    - Shutdown (other intuitive aliases: "shut down", "turn off")
    - logout (aliases: "log out", "log off" and "logoff")

  I realize that the gear-icon-menu is the intended method for achieving
  such tasks, but consider this:

  That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encountered a bug where my mouse-cursor did not 
appear after logging in to the Unity Desktop:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

  Additionally, ctrl-alt-delete doesn't provide a reboot option:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289

  There are clearly circumstances where it would be very nice to reboot
  or shutdown your computer via the dash. As a matter of fact, I think
  it would be my preferred method of achieving these task if it were
  available. Instead of mousing to the gear menu (and clicking a menu
  option), I would much rather hit the super key and type "reboot" or
  "restart".

  Granted, I could achieve this via Unity Alt-key menu, or by hitting
  ctrl-alt-T, but you have to type "sudo reboot" (and enter your dang
  password) to achieve this. I'd rather go the gear-icon-method than be
  required to type my password!

  Therefore, this unity-dash method I'm proposing would be a nice
  compromise. And, from an intuitive perspective, its simply an
  oversight (everyone has ignored) that should have been there all
  along, respectfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:31:36 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu

[Touch-packages] [Bug 1403293] Re: Unity Dash can't understand "logout", "reboot", or "shutdown"

[Lonnie Lee Best]

I guess you are saying that this is more specific to Ayatana Design than
Unity as a whole?

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

Title:
  Unity Dash can't understand "logout", "reboot", or "shutdown"

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  In their efforts to make the Unity Dash the "goto place for everything
  you want to do", the developers have over looked 3 fundamental tasks
  that a user might intuitively try to achieve with the unity dash:

    - Reboot ("restart" is another good alias for this)
    - Shutdown (other intuitive aliases: "shut down", "turn off")
    - logout (aliases: "log out", "log off" and "logoff")

  I realize that the gear-icon-menu is the intended method for achieving
  such tasks, but consider this:

  That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encountered a bug where my mouse-cursor did not 
appear after logging in to the Unity Desktop:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

  Additionally, ctrl-alt-delete doesn't provide a reboot option:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289

  There are clearly circumstances where it would be very nice to reboot
  or shutdown your computer via the dash. As a matter of fact, I think
  it would be my preferred method of achieving these task if it were
  available. Instead of mousing to the gear menu (and clicking a menu
  option), I would much rather hit the super key and type "reboot" or
  "restart".

  Granted, I could achieve this via Unity Alt-key menu, or by hitting
  ctrl-alt-T, but you have to type "sudo reboot" (and enter your dang
  password) to achieve this. I'd rather go the gear-icon-method than be
  required to type my password!

  Therefore, this unity-dash method I'm proposing would be a nice
  compromise. And, from an intuitive perspective, its simply an
  oversight (everyone has ignored) that should have been there all
  along, respectfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:31:36 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-i

[Touch-packages] [Bug 1403289] Re: ctrl-alt-delete is missing a reboot option in Unity Desktop

[Lonnie Lee Best]

While logged into Ubuntu Desktop, if you hit the power button for one
second, it produces a menu similar to what I'm proposing for ctrl-alt-
delete.

Perhaps, as a quick fix, we can just point ctrl-alt-delete to that same
menu (produced by hit the power button). The only proposed option
missing from this menu is "System Monitor" Windows OS offers "Task
Manager" as an option when a user hits ctrl-alt-delete and I never want
Ubuntu to be out-done by windows, so it seems we should put our System
Monitor option there as well.

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

Title:
  ctrl-alt-delete is missing a reboot option in Unity Desktop

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  The Unity Desktop doesn't allow a user to reboot their computer by
  hitting ctrl-alt-delete.

  When ctrl-alt-delete his hit, only two options are provided:
  - Lock
  - Log out

  This bugs is requesting that 4 more options be added to this menu:
  - Reboot
  - Shutdown
  - System Monitor
  - Command Prompt

  Use Case:

  Today I encountered a situation where I did not have a mouse-cursor
  after logging into the Unity desktop. That bug is reported in detail
  here:

  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

  Ultimately, I had to hit ctrl-alt-t to acquire a command prompt, and
  type the command "sudo reboot" in order to reboot my computer.

  The most widely familiar "first step" for dealing with a computer that
  is either "locked up" or "missing a mouse cursor" is the Windows
  tradition of hitting ctrl-alt-delete. The Unity desktop understands
  ctrl-alt-delete, but offers a super limited menu of options after the
  user hits ctrl-alt-delete.

  Additionally, keep this mind: Although most menus are accessible (in
  Unity) via the keyboard, the little gear icon (top-right: used to
  reboot your computer) is NOT intuitively accessible via the keyboard.

  Furthermore, the unity dash should understand what "REBOOT" or
  "SHUTDOWN" means! I'm not saying that the unity dash should restart
  you computer when you type restart or reboot there, but it should at
  least offer the option of doing so after such things are typed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:05:26 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  versio

[Touch-packages] [Bug 1403293] Re: Unity Dash can't understand "logout", "reboot", or "shutdown"

[Lonnie Lee Best]

My intent, in reporting this bug, is not to find a work-around for me
specifically, but is to propose a default behavior for the masses. We
want to maximize the user-friendliness to a brand new user of Ubuntu
Unity, without harming the work-flow of a seasoned professional.

This proposal is intended as a usability completeness, in keeping with
the goal of achieving tasks via the Unity Dash.

The designers of the Unity Dash, have taken great effort to allow new
users (and old) to achieve numerous tasks by hitting the super key and
typing a short phrase. They've designed several scopes allowing a user
find almost anything on their computer (and even scopes that search for
things on the internet).

So, it seems unusual to me, that (out of all the things you can do with
the dash) you cannot search and find such fundamental task as : logout,
reboot, suspend, or shutdown.

I'm proposing additions to the *default* dash lookup scope, that not
only make these tasks available (via the dash), but also activate the
corresponding alias-phrases mentioned previously:

  - Reboot ("restart" is another good alias for this)
  - Shutdown (other intuitive aliases: "shut down", "turn off")
  - logout (aliases: "log out", "log off" and "logoff")
  - suspend/hibernate

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

Title:
  Unity Dash can't understand "logout", "reboot", or "shutdown"

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  In their efforts to make the Unity Dash the "goto place for everything
  you want to do", the developers have over looked 3 fundamental tasks
  that a user might intuitively try to achieve with the unity dash:

    - Reboot ("restart" is another good alias for this)
    - Shutdown (other intuitive aliases: "shut down", "turn off")
    - logout (aliases: "log out", "log off" and "logoff")

  I realize that the gear-icon-menu is the intended method for achieving
  such tasks, but consider this:

  That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encountered a bug where my mouse-cursor did not 
appear after logging in to the Unity Desktop:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

  Additionally, ctrl-alt-delete doesn't provide a reboot option:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289

  There are clearly circumstances where it would be very nice to reboot
  or shutdown your computer via the dash. As a matter of fact, I think
  it would be my preferred method of achieving these task if it were
  available. Instead of mousing to the gear menu (and clicking a menu
  option), I would much rather hit the super key and type "reboot" or
  "restart".

  Granted, I could achieve this via Unity Alt-key menu, or by hitting
  ctrl-alt-T, but you have to type "sudo reboot" (and enter your dang
  password) to achieve this. I'd rather go the gear-icon-method than be
  required to type my password!

  Therefore, this unity-dash method I'm proposing would be a nice
  compromise. And, from an intuitive perspective, its simply an
  oversight (everyone has ignored) that should have been there all
  along, respectfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:31:36 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log pre

[Touch-packages] [Bug 1403293] Re: Unity Dash can't understand "logout", "reboot", or "shutdown"

[Lonnie Lee Best]

While were looking into this, I've added a couple more dash additions to the 
original description (for completeness sake):
  - Lock Computer
  - Switch User

** Description changed:

  In their efforts to make the Unity Dash the "goto place for everything
  you want to do", the developers have over looked 3 fundamental tasks
  that a user might intuitively try to achieve with the unity dash:
  
    - Reboot ("restart" is another good alias for this)
    - Shutdown (other intuitive aliases: "shut down", "turn off")
    - logout (aliases: "log out", "log off" and "logoff")
+   - Suspend/hibernate
+   - Lock
+   - Switch User
  
- I realize that the gear-icon-menu is the intended method for achieving
- such tasks, but consider this:
+ 
+ I realize that the gear-icon-menu is the intended method for achieving such 
tasks, but consider this:
  
  That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encountered a bug where my mouse-cursor did not 
appear after logging in to the Unity Desktop:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287
  
  Additionally, ctrl-alt-delete doesn't provide a reboot option:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289
  
  There are clearly circumstances where it would be very nice to reboot or
  shutdown your computer via the dash. As a matter of fact, I think it
  would be my preferred method of achieving these task if it were
  available. Instead of mousing to the gear menu (and clicking a menu
  option), I would much rather hit the super key and type "reboot" or
  "restart".
  
  Granted, I could achieve this via Unity Alt-key menu, or by hitting
  ctrl-alt-T, but you have to type "sudo reboot" (and enter your dang
  password) to achieve this. I'd rather go the gear-icon-method than be
  required to type my password!
  
  Therefore, this unity-dash method I'm proposing would be a nice
  compromise. And, from an intuitive perspective, its simply an oversight
  (everyone has ignored) that should have been there all along,
  respectfully.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:31:36 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  v

[Touch-packages] [Bug 1403287] Re: [HP Pavilion dv8t-1200 CTO Entertainment Notebook PC] Missing Mouse-Cursor After Login

[Lonnie Lee Best]

I have not had this happen again recently. It seems there was a nvidia
video driver update shortly after I originally reported this, and I
think that it may have fixed the issue. I'll report back here if I
experience this further.

-- 
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/1403287

Title:
  [HP Pavilion dv8t-1200 CTO Entertainment Notebook PC] Missing Mouse-
  Cursor After Login

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

Bug description:
  In the last couple of weeks, I've experienced problems (off and on),
  where after logging into the Unity desktop, I do not have a mouse-
  cursor.

  When this happens, with the intention of rebooting, I hit ctrl-alt-
  delete. This produces a dialog that allows me to logout (but does not
  provide an option to reboot my machine). If I logout, and then log
  back in, the mouse-cursor still remains missing. However, if I this
  ctrl-alt-t, and type sudo reboot, after rebooting the mouse cursor
  beings to appear again.

  I never experienced this behavior in Ubuntu 14.04 until the last two
  weeks or so. So it seems some recent package upgrade (via Ubuntu
  Software Updater) is the culprit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 20:55:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Dec 16 20:55:06 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403287/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Lonnie Lee Best]

Please upgrade the software version for Remmina in the Ubuntu 14.04
repository.

I use Ubuntu exclusively, on my work-computer, and Remmina is among the
most important Linux programs I use on a daily basis. This bug is
driving me crazy.

Ubuntu 14.04 is a Long Term Release. A bug like this should not have to
be endured for 4 years. Please assist.

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in remmina package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  Essentially, when using the Unity desktop in a Multiple Monitor setup
  (using workspaces), Remmina is launching remote sessions into a window
  larger than the workspace to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1370014/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Lonnie Lee Best]

** Description changed:

  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8
+ 
+ To reproduce this bug, you will have to Enable Workspaces In Ubuntu
+ Unity, like this:
+ 
+ System Settings > Appearance > Behavior > Enable Workspaces
  
  Essentially, when using the Unity desktop in a Multiple Monitor setup
  (using workspaces), Remmina is launching remote sessions into a window
  larger than the workspace to which I'm launching it.
  
  Another thing to note about my set up, is that I do use Ubuntu's scaling
  feature to make things about 10% larger than the default size (to
  accommodate my otherwise straining eyes). Some times I use large text
  too. These facts may be totally unrelated to the bug, but I thought I
  would at least mention them.
  
  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

** Description changed:

  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8
  
  To reproduce this bug, you will have to Enable Workspaces In Ubuntu
  Unity, like this:
  
  System Settings > Appearance > Behavior > Enable Workspaces
  
- Essentially, when using the Unity desktop in a Multiple Monitor setup
- (using workspaces), Remmina is launching remote sessions into a window
- larger than the workspace to which I'm launching it.
+ Essentially, when using the Unity desktop (using workspaces), Remmina is
+ launching remote sessions into a window larger than the workspace to
+ which I'm launching it.
  
  Another thing to note about my set up, is that I do use Ubuntu's scaling
  feature to make things about 10% larger than the default size (to
  accommodate my otherwise straining eyes). Some times I use large text
  too. These facts may be totally unrelated to the bug, but I thought I
- would at least mention them.
+ would at least mention them. Also, I do use multiple monitors, but this
+ too might be unrelated to the bug. I think the essential thing, is that
+ I have Workspaces enabled.
  
  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in remmina package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  To reproduce this bug, you will have to Enable Workspaces In Ubuntu
  Unity, like this:

  System Settings > Appearance > Behavior > Enable Workspaces

  Essentially, when using the Unity desktop (using workspaces), Remmina
  is launching remote sessions into a window larger than the workspace
  to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them. Also, I do use multiple
  monitors, but this too might be unrelated to the bug. I think the
  essential thing, is that I have Workspaces enabled.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1370014/+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 1410946] [NEW] Task Switching between Workspaces Fails if Window placement overflows

[Lonnie Lee Best]

Public bug reported:


To reproduce this bug you must enable workspaces:
System Settings > Appearance > Behavior > Enable Workspaces.

Now, I'm assuming you have firefox open in this current workspace (from
where you are reading this message). It doesn't matter if it is chrome,
but later we will switch back to this web browser.

Hit ctrl-alt-downArrow to switch to another workspace.

Launch Gimp (for example) into this new workspace
SuperKey > type "gimp"  (no quotes) and hit the enter key.

Now, make sure that gimp's window is not maximized, and then move the
window so that any part of is clipped by the workspace, meaning, drag
the window down so that the bottom 10 pixels of the window are not
viewable on the workspace.

Now, on the launcher bar, click on an icon that is open in another
workspace (firefox or chromium for example). Then try to go back to gimp
by clicking on its launcher icon.

For me, unless the workspace encapsulates the gimp window 100%, I am not
able to switch back to gimp by clicking its launcher icon.

I was using Gimp as an example, but the same is true for any other
application whose window is not completely encapsulated by the workspace
that it primarily resides.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Jan 14 13:27:15 2015
InstallationDate: Installed on 2014-11-23 (52 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Task Switching between Workspaces Fails if Window placement overflows

Status in unity package in Ubuntu:
  New

Bug description:

  To reproduce this bug you must enable workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces.

  Now, I'm assuming you have firefox open in this current workspace
  (from where you are reading this message). It doesn't matter if it is
  chrome, but later we will switch back to this web browser.

  Hit ctrl-alt-downArrow to switch to another workspace.

  Launch Gimp (for example) into this new workspace
  SuperKey > type "gimp"  (no quotes) and hit the enter key.

  Now, make sure that gimp's window is not maximized, and then move the
  window so that any part of is clipped by the workspace, meaning, drag
  the window down so that the bottom 10 pixels of the window are not
  viewable on the workspace.

  Now, on the launcher bar, click on an icon that is open in another
  workspace (firefox or chromium for example). Then try to go back to
  gimp by clicking on its launcher icon.

  For me, unless the workspace encapsulates the gimp window 100%, I am
  not able to switch back to gimp by clicking its launcher icon.

  I was using Gimp as an example, but the same is true for any other
  application whose window is not completely encapsulated by the
  workspace that it primarily resides.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Jan 14 13:27:15 2015
  InstallationDate: Installed on 2014-11-23 (52 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1410946/+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 1408783] Re: Failure to Sustain Universal Access (small text)

[Lonnie Lee Best]

Know of a good workaround to persist these settings, until the bug is
fixed?

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

Title:
  Failure to Sustain Universal Access (small text)

Status in unity package in Ubuntu:
  New

Bug description:
  At some point, I changed my Universal Access setting to Large Text via this 
menu:
  System Settings > Universal Access > Large Text

  Later, I changed it back to "small text" (meaning I turned large text
  off).

  Despite this, many times I will login to Ubuntu, and everything will
  be in Large Text again, despite the fact that I've explicitly turned
  that off.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan  8 14:11:33 2015
  InstallationDate: Installed on 2014-11-23 (46 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1408783/+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 1418078] [NEW] Maximize Window Bug - Using Workspaces

[Lonnie Lee Best]

Public bug reported:

The code that gets initiated when a window is maximize is flawed in
regards to which workspace it targets for maximization.

When a window becomes maximized it should always maximize to the
workspace "where the mouse-cursor was at" at the time that the
maximization was initiated. Yet, in Unity, the windows manager will
maximize to a different workspace if a certain portion of that window is
outside the bounds of the current workspace.

To easily reproduce this undesired behavior:

1) Enable Workspaces:
System Settings > Appearance > Behavior > Enable Workspaces

2) Drag the window to the bottom of the screen, so that its title-bar is
still visible on the current workspace, but a fair portion overflows to
the underneath-workspace.

3) Maximize the window.

Result: It will maximize the window to another workspace than the
workspace you were in at the time of the maximization.

Watch the video posted in this bug:
https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014

Although this is a different bug, it would benefit greatly if the
Window-Maximization code was based on the workspace "where the mouse-
cursor was at" at the time of maximization.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Feb  4 09:18:46 2015
InstallationDate: Installed on 2014-11-23 (73 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Maximize Window Bug - Using Workspaces

Status in unity package in Ubuntu:
  New

Bug description:
  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.

  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window
  is outside the bounds of the current workspace.

  To easily reproduce this undesired behavior:

  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces

  2) Drag the window to the bottom of the screen, so that its title-bar
  is still visible on the current workspace, but a fair portion
  overflows to the underneath-workspace.

  3) Maximize the window.

  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.

  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014

  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1418078/+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 1418078] Re: Maximize Window Bug - Using Workspaces

[Lonnie Lee Best]

** Description changed:

  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.
  
  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window is
  outside the bounds of the current workspace.
  
  To easily reproduce this undesired behavior:
  
  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces
  
- 2) Drag the window to the bottom of the screen, so that its title-bar is
- still visible on the current workspace, but a fair portion overflows to
- the underneath-workspace.
+ 2) Drag any maximizable window (of any application) to the bottom of the
+ screen, so that its title-bar is still visible on the current workspace,
+ but a fair portion overflows into the underneath-workspace.
  
  3) Maximize the window.
  
  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.
  
  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014
  
  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Maximize Window Bug - Using Workspaces

Status in unity package in Ubuntu:
  New

Bug description:
  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.

  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window
  is outside the bounds of the current workspace.

  To easily reproduce this undesired behavior:

  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces

  2) Drag any maximizable window (of any application) to the bottom of
  the screen, so that its title-bar is still visible on the current
  workspace, but a fair portion overflows into the underneath-workspace.

  3) Maximize the window.

  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.

  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014

  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1418078/+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 1418078] Re: Maximize Window Bug - Using Workspaces

[Lonnie Lee Best]

** Also affects: compiz
   Importance: Undecided
   Status: New

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

Title:
  Maximize Window Bug - Using Workspaces

Status in Compiz:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.

  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window
  is outside the bounds of the current workspace.

  To easily reproduce this undesired behavior:

  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces

  2) Drag any maximizable window (of any application) to the bottom of
  the screen, so that its title-bar is still visible on the current
  workspace, but a fair portion overflows into the underneath-workspace.

  3) Maximize the window.

  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.

  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014

  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1418078/+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 1418078] Re: Maximize Window Bug - Using Workspaces

[Lonnie Lee Best]

I determined my window manager with this command:

wmctrl -m :

Name: Compiz
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: OFF

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

Title:
  Maximize Window Bug - Using Workspaces

Status in Compiz:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.

  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window
  is outside the bounds of the current workspace.

  To easily reproduce this undesired behavior:

  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces

  2) Drag any maximizable window (of any application) to the bottom of
  the screen, so that its title-bar is still visible on the current
  workspace, but a fair portion overflows into the underneath-workspace.

  3) Maximize the window.

  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.

  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014

  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1418078/+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 1418078] Re: Maximize Window Bug - Using Workspaces

[Lonnie Lee Best]

** Description changed:

  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.
  
  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window is
  outside the bounds of the current workspace.
  
  To easily reproduce this undesired behavior:
  
  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces
  
  2) Drag any maximizable window (of any application) to the bottom of the
  screen, so that its title-bar is still visible on the current workspace,
  but a fair portion overflows into the underneath-workspace.
  
  3) Maximize the window.
  
  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.
  
  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014
  
+ A direct link to the video:
+ http://youtu.be/wKGLff7HhS8
+ 
  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Maximize Window Bug - Using Workspaces

Status in Compiz:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.

  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window
  is outside the bounds of the current workspace.

  To easily reproduce this undesired behavior:

  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces

  2) Drag any maximizable window (of any application) to the bottom of
  the screen, so that its title-bar is still visible on the current
  workspace, but a fair portion overflows into the underneath-workspace.

  3) Maximize the window.

  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.

  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014

  A direct link to the video:
  http://youtu.be/wKGLff7HhS8

  In that video, at the beginning, if I were to have maximized that
  window, it would send it to the bottom (wrong) workspace. Because of
  that fact, you can see how much trouble it took to achieve the desired
  result of maximizing it in the currently focused workspace.

  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1418078/+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 1418078] Re: Maximize Window Bug - Using Workspaces

[Lonnie Lee Best]

** Description changed:

  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.
  
  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window is
  outside the bounds of the current workspace.
  
  To easily reproduce this undesired behavior:
  
  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces
  
  2) Drag any maximizable window (of any application) to the bottom of the
  screen, so that its title-bar is still visible on the current workspace,
  but a fair portion overflows into the underneath-workspace.
  
  3) Maximize the window.
  
  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.
  
  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014
  
  A direct link to the video:
  http://youtu.be/wKGLff7HhS8
  
+ In that video, at the beginning, if I were to have maximized that
+ window, it would send it to the bottom (wrong) workspace. Because of
+ that fact, you can see how much trouble it took to achieve the desired
+ result of maximizing it in the currently focused workspace.
+ 
  Although this is a different bug, it would benefit greatly if the
  Window-Maximization code was based on the workspace "where the mouse-
  cursor was at" at the time of maximization.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  The code that gets initiated when a window is maximize is flawed in
  regards to which workspace it targets for maximization.
  
  When a window becomes maximized it should always maximize to the
  workspace "where the mouse-cursor was at" at the time that the
  maximization was initiated. Yet, in Unity, the windows manager will
  maximize to a different workspace if a certain portion of that window is
  outside the bounds of the current workspace.
  
  To easily reproduce this undesired behavior:
  
  1) Enable Workspaces:
  System Settings > Appearance > Behavior > Enable Workspaces
  
  2) Drag any maximizable window (of any application) to the bottom of the
  screen, so that its title-bar is still visible on the current workspace,
  but a fair portion overflows into the underneath-workspace.
  
  3) Maximize the window.
  
  Result: It will maximize the window to another workspace than the
  workspace you were in at the time of the maximization.
  
  Watch the video posted in this bug:
  https://bugs.launchpad.net/ubuntu/utopic/+source/remmina/+bug/1370014
  
  A direct link to the video:
  http://youtu.be/wKGLff7HhS8
  
  In that video, at the beginning, if I were to have maximized that
  window, it would send it to the bottom (wrong) workspace. Because of
  that fact, you can see how much trouble it took to achieve the desired
  result of maximizing it in the currently focused workspace.
  
- Although this is a different bug, it would benefit greatly if the
- Window-Maximization code was based on the workspace "where the mouse-
- cursor was at" at the time of maximization.
+ Although that is a different bug, you can see how much that bug would
+ have benefited if the Window-Maximization code was based on the
+ workspace "where the mouse-cursor was at" at the time of maximization.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Feb  4 09:18:46 2015
  InstallationDate: Installed on 2014-11-23 (73 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Touch-packages] [Bug 1135515] Re: Parcellite Applet-Indicator Doesn't Show on All Monitor's Workspaces

[Lonnie Lee Best]

Sorry, I was only able to test version 1.1.7-1ubuntu0.1.

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

Title:
  Parcellite Applet-Indicator Doesn't Show on All Monitor's Workspaces

Status in Ayatana Design:
  Confirmed
Status in Unity:
  Confirmed
Status in parcellite package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Parcellite's applet/indicators icon only shows up on desktop
  workspaces of monitor 1, but does not show up on the desktop
  workspaces of additional monitors.

  Typically (and I prefer this), applet-indicator-icons (of an
  application) will appear on each workspace of each monitor (on the
  left side of the clock of each top-panel).

  This common practice would be especially helpful in Parcellite; it
  would make it more convenient to access Parcellite's clippings, while
  working on additional monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: parcellite 1.0.2~rc5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Thu Feb 28 03:47:06 2013
  InstallationDate: Installed on 2012-11-28 (91 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: parcellite
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2013-03-06 (22 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: parcellite 1.1.4-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Tags:  raring
  Uname: Linux 3.8.0-15-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-03-28 (0 days ago)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1135515/+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 1135515] Re: Parcellite Applet-Indicator Doesn't Show on All Monitor's Workspaces

[Lonnie Lee Best]

The indicator now appears on each workspace of each monitor. So this bug
is fixed.

However, the context menu of the indicator does NOT list your clipboard
history like it once did (back when it worked). To be clear, it does
list "History" as an option, but what I mean is that is use to list your
last x clipping right there at the top of the menu, so you could
conveniently switch between your clippings.

https://bugs.launchpad.net/ubuntu/+source/parcellite/+bug/1419753

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

Title:
  Parcellite Applet-Indicator Doesn't Show on All Monitor's Workspaces

Status in Ayatana Design:
  Confirmed
Status in Unity:
  Confirmed
Status in parcellite package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Parcellite's applet/indicators icon only shows up on desktop
  workspaces of monitor 1, but does not show up on the desktop
  workspaces of additional monitors.

  Typically (and I prefer this), applet-indicator-icons (of an
  application) will appear on each workspace of each monitor (on the
  left side of the clock of each top-panel).

  This common practice would be especially helpful in Parcellite; it
  would make it more convenient to access Parcellite's clippings, while
  working on additional monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: parcellite 1.0.2~rc5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-25.39-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Thu Feb 28 03:47:06 2013
  InstallationDate: Installed on 2012-11-28 (91 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: parcellite
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 13.04
  InstallationDate: Installed on 2013-03-06 (22 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: parcellite 1.1.4-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Tags:  raring
  Uname: Linux 3.8.0-15-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-03-28 (0 days ago)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1135515/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Lonnie Lee Best]

Can someone please upgrade this package in 14.04 LTS, so that an update
is released via Ubuntu Software Updater?

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in remmina package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  Essentially, when using the Unity desktop in a Multiple Monitor setup
  (using workspaces), Remmina is launching remote sessions into a window
  larger than the workspace to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1370014/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Lonnie Lee Best]

You can detect which version of remmina you are using by running this as
one command:

sudo apt-get install apt-show-versions ; sudo apt-show-versions remmina

In Ubuntu 14.01 this returns:

remmina:amd64/trusty 1.0.0-4ubuntu3 uptodate

What version is being run in Ubuntu 14.10?

It seems like I tested 14.10 and did not have this bug we are reporting
here. I'm hoping we can get the corrected version of Remmina into the
14.01 LTS. Is this likely?

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in remmina package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  Essentially, when using the Unity desktop in a Multiple Monitor setup
  (using workspaces), Remmina is launching remote sessions into a window
  larger than the workspace to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1370014/+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 1403287] [NEW] Missing Mouse-Cursor After Login

[Lonnie Lee Best]

Public bug reported:

In the last couple of weeks, I've experienced problems (off and on),
where after logging into the Unity desktop, I do not have a mouse-
cursor.

When this happens, with the intention of rebooting, I hit ctrl-alt-
delete. This produces a dialog that allows me to logout (but does not
provide an option to reboot my machine). If I logout, and then log back
in, the mouse-cursor still remains missing. However, if I this ctrl-
alt-t, and type sudo reboot, after rebooting the mouse cursor beings to
appear again.

I never experienced this behavior in Ubuntu 14.04 until the last two
weeks or so. So it seems some recent package upgrade (via Ubuntu
Software Updater) is the culprit.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Dec 16 20:55:51 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:7001]
InstallationDate: Installed on 2014-11-23 (23 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 7001
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 35.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv8 Notebook PC
dmi.product.version: 04992224121000104
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Dec 16 20:55:06 2014
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.5

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  Missing Mouse-Cursor After Login

Status in unity package in Ubuntu:
  New

Bug description:
  In the last couple of weeks, I've experienced problems (off and on),
  where after logging into the Unity desktop, I do not have a mouse-
  cursor.

  When this happens, with the intention of rebooting, I hit ctrl-alt-
  delete. This produces a dialog that allows me to logout (but does not
  provide an option to reboot my machine). If I logout, and then log
  back in, the mouse-cursor still remains missing. However, if I this
  ctrl-alt-t, and type sudo reboot, after rebooting the mouse cursor
  beings to appear again.

  I never experienced this behavior in Ubuntu 14.04 until the last two
  weeks or so. So it seems some recent package upgrade (via Ubuntu
  Software Updater) is the culprit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.201408

[Touch-packages] [Bug 1403289] [NEW] ctrl-alt-delete is missing a reboot option in Unity Desktop

[Lonnie Lee Best]

Public bug reported:

The Unity Desktop doesn't allow a user to reboot their computer by
hitting ctrl-alt-delete.

When ctrl-alt-delete his hit, only two options are provided:
- Lock
- Log out

This bugs is requesting that 4 more options be added to this menu:
- Reboot
- Shutdown
- System Monitor
- Command Prompt

Use Case:

Today I encountered a situation where I did not have a mouse-cursor
after logging into the Unity desktop. That bug is reported in detail
here:

https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

Ultimately, I had to hit ctrl-alt-t to acquire a command prompt, and
type the command "sudo reboot" in order to reboot my computer.

The most widely familiar "first step" for dealing with a computer that
is either "locked up" or "missing a mouse cursor" is the Windows
tradition of hitting ctrl-alt-delete. The Unity desktop understands
ctrl-alt-delete, but offers a super limited menu of options after the
user hits ctrl-alt-delete.

Additionally, keep this mind: Although most menus are accessible (in
Unity) via the keyboard, the little gear icon (top-right: used to reboot
your computer) is NOT intuitively accessible via the keyboard.

Furthermore, the unity dash should understand what "REBOOT" or
"SHUTDOWN" means! I'm not saying that the unity dash should restart you
computer when you type restart or reboot there, but it should at least
offer the option of doing so after such things are typed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Dec 16 21:05:26 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:7001]
InstallationDate: Installed on 2014-11-23 (23 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 7001
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 35.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv8 Notebook PC
dmi.product.version: 04992224121000104
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Dec 16 20:55:06 2014
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.5

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu utopic vivid

** Tags added: utopic vivid

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

Title:
  ctrl-alt-delete is missing a reboot option in Unity Desktop

Status in unity package in Ubuntu:
  New

[Touch-packages] [Bug 1403293] [NEW] Unity Dash can't understand "restart", "reboot", or "shutdown"

[Lonnie Lee Best]

Public bug reported:

In their efforts to make the Unity Dash the "goto place for everything you want 
to do", the developers have over looked 3 fundamental tasks that a user might 
intuitively try to achieve with the unity dash:
  - Reboot
  - Restart (another alias a user might intuitively type to achieve reboot)
  - Shutdown (other intuitive possibilities: , "shut down", "turn off")

I realize that the gear-icon-menu is the intended method for achieving
such tasks, but consider this:

That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encounter a bug where my mouse cursor did not 
appear after logging in to the Unity Desktop:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287

Additionally, ctrl-alt-delete doesn't provide a reboot option:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289

There are clearly circumstances where it would be very nice to reboot or
shutdown your computer via the dash. As a matter of fact, I think it
would be my preferred method of achieving these task if it were
available. Instead of mousing to the gear menu (and clicking a menu
option), I would much rather hit the super key and type "reboot" or
"restart".

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Dec 16 21:31:36 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:7001]
InstallationDate: Installed on 2014-11-23 (23 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 7001
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 35.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv8 Notebook PC
dmi.product.version: 04992224121000104
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Dec 16 20:55:06 2014
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.5

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu utopic vivid

** Tags added: utopic vivid

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

Title:
  Unity Dash can't understand "restart", "reboot", or "shutdown"

Status in unity package in Ubuntu:
  New

Bug description:
  In their efforts to make the Unity Dash the "goto place for everything you 
want to do", the developers hav

[Touch-packages] [Bug 1403293] Re: Unity Dash can't understand "restart", "reboot", or "shutdown"

[Lonnie Lee Best]

** Description changed:

  In their efforts to make the Unity Dash the "goto place for everything you 
want to do", the developers have over looked 3 fundamental tasks that a user 
might intuitively try to achieve with the unity dash:
-   - Reboot
-   - Restart (another alias a user might intuitively type to achieve reboot)
-   - Shutdown (other intuitive possibilities: , "shut down", "turn off")
+   - Reboot
+   - Restart (another alias a user might intuitively type to achieve reboot)
+   - Shutdown (other intuitive possibilities: , "shut down", "turn off")
  
  I realize that the gear-icon-menu is the intended method for achieving
  such tasks, but consider this:
  
  That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encounter a bug where my mouse cursor did not 
appear after logging in to the Unity Desktop:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287
  
  Additionally, ctrl-alt-delete doesn't provide a reboot option:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289
  
  There are clearly circumstances where it would be very nice to reboot or
  shutdown your computer via the dash. As a matter of fact, I think it
  would be my preferred method of achieving these task if it were
  available. Instead of mousing to the gear menu (and clicking a menu
  option), I would much rather hit the super key and type "reboot" or
  "restart".
  
+ Granted, I could achieve this via Unity Alt-key menu, or by hitting
+ ctrl-alt-delete, but you have to type "sudo reboot" (and enter your dang
+ password) to achieve this. I'd rather go the gear-icon-method than be
+ required to type my password!
+ 
+ Therefore, this unity-dash method I'm proposing would be a nice
+ compromise. And, from an intuitive perspective, its simply an oversight
+ (everyone has ignored) that should have been there all along,
+ respectfully.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
-  GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
+  GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:31:36 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
-  NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:7001]
+  NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  version.xser

[Touch-packages] [Bug 1403293] Re: Unity Dash can't understand "restart", "reboot", or "shutdown"

[Lonnie Lee Best]

** Description changed:

  In their efforts to make the Unity Dash the "goto place for everything you 
want to do", the developers have over looked 3 fundamental tasks that a user 
might intuitively try to achieve with the unity dash:
    - Reboot
    - Restart (another alias a user might intuitively type to achieve reboot)
    - Shutdown (other intuitive possibilities: , "shut down", "turn off")
  
  I realize that the gear-icon-menu is the intended method for achieving
  such tasks, but consider this:
  
- That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encounter a bug where my mouse cursor did not 
appear after logging in to the Unity Desktop:
+ That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encountered a bug where my mouse-cursor did not 
appear after logging in to the Unity Desktop:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287
  
  Additionally, ctrl-alt-delete doesn't provide a reboot option:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289
  
  There are clearly circumstances where it would be very nice to reboot or
  shutdown your computer via the dash. As a matter of fact, I think it
  would be my preferred method of achieving these task if it were
  available. Instead of mousing to the gear menu (and clicking a menu
  option), I would much rather hit the super key and type "reboot" or
  "restart".
  
  Granted, I could achieve this via Unity Alt-key menu, or by hitting
- ctrl-alt-delete, but you have to type "sudo reboot" (and enter your dang
+ ctrl-alt-T, but you have to type "sudo reboot" (and enter your dang
  password) to achieve this. I'd rather go the gear-icon-method than be
  required to type my password!
  
  Therefore, this unity-dash method I'm proposing would be a nice
  compromise. And, from an intuitive perspective, its simply an oversight
  (everyone has ignored) that should have been there all along,
  respectfully.
- 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:31:36 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-

[Touch-packages] [Bug 1403293] Re: Unity Dash can't understand "logout", "reboot", or "shutdown"

[Lonnie Lee Best]

** Summary changed:

- Unity Dash can't understand "restart", "reboot", or "shutdown"
+ Unity Dash can't understand "logout", "reboot", or "shutdown"

** Description changed:

  In their efforts to make the Unity Dash the "goto place for everything
  you want to do", the developers have over looked 3 fundamental tasks
  that a user might intuitively try to achieve with the unity dash:
  
    - Reboot ("restart" is another good alias for this)
-   - Shutdown (other intuitive possibilities: , "shut down", "turn off")
-   - logout ("log out" alias)
+   - Shutdown (other intuitive aliases: "shut down", "turn off")
+   - logout (aliases: "log out", "log off" and "logoff")
  
- 
- I realize that the gear-icon-menu is the intended method for achieving such 
tasks, but consider this:
+ I realize that the gear-icon-menu is the intended method for achieving
+ such tasks, but consider this:
  
  That menu is not intuitively accessible via the keyboard. Try to access it 
without your mouse! It might be possible, but if so, it is not intuitive. I 
realized this today, when I encountered a bug where my mouse-cursor did not 
appear after logging in to the Unity Desktop:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287
  
  Additionally, ctrl-alt-delete doesn't provide a reboot option:
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289
  
  There are clearly circumstances where it would be very nice to reboot or
  shutdown your computer via the dash. As a matter of fact, I think it
  would be my preferred method of achieving these task if it were
  available. Instead of mousing to the gear menu (and clicking a menu
  option), I would much rather hit the super key and type "reboot" or
  "restart".
  
  Granted, I could achieve this via Unity Alt-key menu, or by hitting
  ctrl-alt-T, but you have to type "sudo reboot" (and enter your dang
  password) to achieve this. I'd rather go the gear-icon-method than be
  required to type my password!
  
  Therefore, this unity-dash method I'm proposing would be a nice
  compromise. And, from an intuitive perspective, its simply an oversight
  (everyone has ignored) that should have been there all along,
  respectfully.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 16 21:31:36 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:7001]
  InstallationDate: Installed on 2014-11-23 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=8b3cc691-0444-4efd-8504-0ae5dd9ba3eb ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: x

[Touch-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

** This bug is no longer a duplicate of bug 1629611
   dns server priority broken

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

When configuring the IPv4 settings of a VPN connection, clicking the
"Routes" button produces this menu:

http://neartalk.com/ss/2016-12-05_001_634x674.png

I always check the box for "Use this connection only for resources on
its network".

However, (due to recent updates) when this box is check I cannot ping
machines on the remote network by computer name.

When this box is checked, the network-manger is failing to query the two remote 
DNS servers for computer-names:
http://neartalk.com/ss/2016-12-05_001_634x674.png

It should query these additional DNS servers whether that box is check
or not.

Can someone please fix this?

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

** Tags added: zesty

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

Why is the status of this incomplete. I've verified this issue from
numerous perspectives that probably all fundamental point directly to
the issue Thomas has reported; see post#2.

This is a terrible bug. Network-Manager updates were prematurely
released to 14.04 stable and all succeeding releases and no one caught
this. I keep waiting as patiently as possible. Please fix!

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

Bryn, thank for the suggested work around. However, it is not a workaround for 
me. My issue is that I have over 100 Remmina RDP desktop configurations saved 
that connect to numerous computers on different VPNs by computer name (not by 
ip address). However, I cannot ping those computers by name when I'm connected 
to their respective VPNs anymore like I could before recent Network Manger 
updates. My issue is described in detail here:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874

When you are connected to a VPN, your computer is suppose to check that
virtual private network's DNS servers too, when it cannot find (on your
local network) the computer-name you are you are trying to reach by
name.

Network Manger gives you the opportunity to specify "Additional DNS
Servers" for each connection you set up whether it be LAN, WiFi, or VPN.
Yet Network manager now fails to queries those DNS servers in the proper
order. It seems to just give up at the local DNS level when the other
DNSs you've configured could certainly tell you the ip address of the
computer name you are trying to reach if it were simply asked. It is not
being ASKED.

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+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 1633874] [NEW] VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

Public bug reported:

During configuring of a VPN, Network Manager normally allows you to
specify additional DNS servers that are located on the virtual private
network:

http://neartalk.com/ss/2016-10-16_001_601x625.png

However, in Ubuntu 16.10 the network manager is ignoring the additional
DNS that I've specified at the dialog I've linked above.

Normally, after connecting to a VPN (where additional DNS servers are
specified), the command (below) will show (in addition to your local DNS
servers) the remote DNS servers (located on the VPN):

nmcli dev show | grep DNS

Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
cannot resolve remote computers by their computer-name, which is very
inconvenient considering that I have over 100 Remmina connections set to
resolve by name. Right now, I have to manually discover the IP addresses
of the remote computer-names before connecting to the computers with
Remmina.

I've confirm this issue on both OpenVPN and Cisco vpnc connections. The
additional DNS server are not making it here:

nmcli dev show | grep DNS

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 16 09:31:31 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-10-13 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager-applet
 Importance: Undecided
 Status: New

** Affects: network-manager-openvpn
 Importance: Undecided
 Status: New

** Affects: network-manager-vpnc
 Importance: Undecided
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

** Also affects: network-manager-openvpn
   Importance: Undecided
   Status: New

** Also affects: network-manager-vpnc
   Importance: Undecided
   Status: New

** Also affects: network-manager-applet
   Importance: Undecided
   Status: New

** Description changed:

  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:
  
  http://neartalk.com/ss/2016-10-16_001_601x625.png
  
  However, in Ubuntu 16.10 the network manager is ignoring the additional
  DNS that I've specified at the dialog I've linked above.
  
  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local DNS
- servers) the remote DNS servers located on the VPN:
+ servers) the remote DNS servers (located on the VPN):
  
  nmcli dev show | grep DNS
  
  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set to
  resolve by name. Right now, I have to manually discover the IP addresses
  of the remote computer-names before connecting to the computers with
  Remmina.
  
  I've confirm this issue on both OpenVPN and Cisco vpnc connections. The
  additional DNS server are not making it here:
  
  nmcli dev show | grep DNS
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled
+  RUNNING  VERSION  STATE  STARTUP  CO

[Touch-packages] [Bug 1633877] [NEW] VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

Public bug reported:

During configuring of a VPN, Network Manager normally allows you to
specify "additional Search Domains" that are located on the virtual
private network:

http://neartalk.com/ss/2016-10-16_001_601x625.png

However, in Ubuntu 16.10 the network manager is ignoring the "additional
Search Domains" that I've specified at the dialog I've linked above.

Normally, after connecting to a VPN (where additional Search Domains are
specified), the command (below) will show (in addition to your local
Search Domains) the remote Search Domains (located on the VPN):

nmcli dev show | grep DOMAIN

Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
cannot resolve remote computers by their computer-name because the
"Search Domains" I've specified are not getting appended to the
computer-names I'm pinging.

I've confirm this issue on both OpenVPN and Cisco vpnc connections. The
additional Search Domains are not making it here:

nmcli dev show | grep DOMAIN

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 16 10:16:04 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-10-13 (2 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   WIFI 
 WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

** Affects: network-manager-applet
 Importance: Undecided
 Status: New

** Affects: network-manager-openvpn
 Importance: Undecided
 Status: New

** Affects: network-manager-vpnc
 Importance: Undecided
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

** Also affects: network-manager-vpnc
   Importance: Undecided
   Status: New

** Also affects: network-manager-openvpn
   Importance: Undecided
   Status: New

** Also affects: network-manager-applet
   Importance: Undecided
   Status: New

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
ht

[Touch-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

** Information type changed from Private to Public

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

** Information type changed from Private to Public

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

I've reproduced this bug on a completely fresh installation of Ubuntu
16.10

Steps:

1) Install these packages:
sudo apt install network-manager-openvpn-gnome network-manager-vpnc-gnome

2) Create an openVPN or cisco-vpnc VPN-Connection and input the remote
dns servers of the network you are connecting to here:
http://neartalk.com/ss/2016-10-16_001_601x625.png

3) Connect to the VPN

4) Try to ping a computer (on the remote network) by its name:
ping computer-name

(it won't work)

5) Try to find the Additional DNS server you've configured in the VPN:
nmcli dev show | grep DNS

(you won't find them)

In Ubuntu 16.04, you could easily ping by computer-name to computers in
remote networks and nmcli would also show additional DNS servers
specified in the VPN configuration. In 16.10, this is broken.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

I've reproduced this bug on a completely fresh installation of Ubuntu
16.10

Steps:

1) Install these packages:
sudo apt install network-manager-openvpn-gnome network-manager-vpnc-gnome

2) Create an openVPN or cisco-vpnc VPN-Connection and input the
additional search domains of the network you are connecting to here:
http://neartalk.com/ss/2016-10-16_001_601x625.png

3) Connect to the VPN

4) Try to find the Additional search domains you've configured in the VPN:
nmcli dev show | grep DOMAIN

(you won't find them)

In Ubuntu 16.04, "nmcli dev show" would show the additional search
domains specified in the VPN configuration. In 16.10, they do not show
up and additional search domains do not work.

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

Can someone else please confirm this bug?

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

Can someone else please confirm this bug?

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

I just downgraded back to Ubuntu 16.04, and I'm experience the same
problem.

My home directory is located on a separate partition. So, although I've
reinstalled 16.04, there may be some previously existing config files in
my home folder that were corrupted by 16.10.

Please advise which files I should delete to see if that's the case.

** Tags added: xenial

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

After doing a fresh install of Ubuntu 16.04 into a fresh virtual machine
without doing any upgrades both "VPN - Additional DNS Server" and "VPN-
Additional Search Domains" worked.

However, these features *stopped working* after doing an upgrade like this:
sudo apt-get update ; sudo apt-get upgrade

I've attached to this post, a log of the initial install (time stamped),
and if you scroll to the bottom you can see a list of upgrades (time
stamped).

One of these upgrades broke both "VPN - Additional DNS Server" and "VPN-
Additional Search Domains" functionality!

Most likely, one of these is the culprit:

2016-10-19 18:18:44 upgrade network-manager:amd64 1.2.0-0ubuntu0.16.04.3 
1.2.2-0ubuntu0.16.04.3
2016-10-19 18:18:45 upgrade network-manager-gnome:amd64 1.2.0-0ubuntu0.16.04.3 
1.2.0-0ubuntu0.16.04.4

See attachment.

** Attachment added: "InstallandUpgrade.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633877/+attachment/4763972/+files/InstallandUpgrade.txt

** Tags added: xenial

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

After doing a fresh install of Ubuntu 16.04 into a fresh virtual machine
without doing any upgrades both "VPN - Additional DNS Server" and "VPN-
Additional Search Domains" worked.

However, these features *stopped working* after doing an upgrade like this:
sudo apt-get update ; sudo apt-get upgrade

I've attached to this post, a log of the initial install (time stamped),
and if you scroll to the bottom you can see a list of upgrades (time
stamped).

One of these upgrades broke both "VPN - Additional DNS Server" and "VPN-
Additional Search Domains" functionality!

Most likely, one of these is the culprit:

2016-10-19 18:18:44 upgrade network-manager:amd64 1.2.0-0ubuntu0.16.04.3 
1.2.2-0ubuntu0.16.04.3
2016-10-19 18:18:45 upgrade network-manager-gnome:amd64 1.2.0-0ubuntu0.16.04.3 
1.2.0-0ubuntu0.16.04.4

See attachment.

** Attachment added: "InstallandUpgrade.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633874/+attachment/4763973/+files/InstallandUpgrade.txt

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

Work-around:

Using Synaptic Package Manager, downgrading the network-manager package
to version 1.1.93-0ubuntu4 and restarting the network-manager causes the
unwanted behavior to stop.

Work around steps:

1) Install Synaptic Package Manager
sudo apt-get install synaptic

2) Search for "network-manager" (no quotes), and then select "network-
manager" so that it is highlighted.

3) In the "Package" menu, select "Force Version" and choose 1.1.93-0ubuntu4 
from the drop-down-menu:
http://neartalk.com/ss/2016-10-19_005_1918x1077.png

4) Click the Apply button

5) Restart the network-manger service:
sudo service network-manager restart

6) Reconnect to your vpn

After these steps I was able to ping computers on the remote VPN network
by their computer-name as prescribed by the "Additional DNS Server"
option in the VPN configuration dialog.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

Work-around:

Using Synaptic Package Manager, downgrading the network-manager package
to version 1.1.93-0ubuntu4 and restarting the network-manager causes the
unwanted behavior to stop.

Work around steps:

1) Install Synaptic Package Manager
sudo apt-get install synaptic

2) Search for "network-manager" (no quotes), and then select "network-
manager" so that it is highlighted.

3) In the "Package" menu, select "Force Version" and choose 1.1.93-0ubuntu4 
from the drop-down-menu:
http://neartalk.com/ss/2016-10-19_005_1918x1077.png

4) Click the Apply button

5) Restart the network-manger service:
sudo service network-manager restart

6) Reconnect to your vpn

After these steps I was able to ping computers on the remote VPN network
by their computer-name without having to explicitly type the "Search
Domain" portion of their address, as prescribed by the "Additional
Search Domain" option in the VPN configuration dialog.

This is only a work-around, there is definitely a bug in network-manager
version 1.2.2-0ubuntu0.16.04.3.

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1589005] Re: After update DNS work unstable

[Lonnie Lee Best]

In two other bugs, I too am suffering from the latest Network Manger
update.

Additional DNS Servers are ignored when specified via VPN configured 
connections:
-https://bugs.launchpad.net/network-manager-applet/+bug/1633874

Additional Search Domains are ignored when specified via VPN configured 
connections:
-https://bugs.launchpad.net/network-manager-applet/+bug/1633877

** Tags added: yakkety

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589005/+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 1634208] Re: VPN cannot resolve DNS entries on second connect

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1633874 ***
https://bugs.launchpad.net/bugs/1633874

** This bug has been marked a duplicate of bug 1633874
   VPN - "Additional DNS servers" Settings are being Ignored

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

Title:
  VPN cannot resolve DNS entries on second connect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10
  The first time I connect to a VPN (vpnc) everything works fine, but if I 
disconnect and then reconnect I can no longer resolve DNS entries although I 
can connect directly via IP address. The only solution seems to be a reboot.

  This was working fine in 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1634208/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

network-manager version 1.2.0-0ubuntu0.16.04.3 works in Ubuntu 16.04.1

So far, this is the latest version I can confirm is working correctly.

Since this is a stable release, the Update Manager should not upgrade to
later versions than this until someone confirms that this bug is not in
those versions.

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

Once you have a working network-manager (in regards to this bug), you
can prevent that version from being upgraded (until you verify the bug
is fixed) like this:

sudo apt-mark hold network-manager

To prove this is working you can run:
sudo apt-get upgrade -V

Then you'll see this:

   The following packages have been kept back:
   network-manager (1.1.93-0ubuntu4 => 1.2.2-0ubuntu0.16.04.3)

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633003] Re: (Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1633874 ***
https://bugs.launchpad.net/bugs/1633874

This issue is not just Cisco vpnc specific; it also happens with openVPN
and possibly all VPN connections.

** This bug has been marked a duplicate of bug 1633874
   VPN - "Additional DNS servers" Settings are being Ignored

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

Title:
  (Cisco) VPN name resolution breaks after upgrade to
  1.2.2-0ubuntu0.16.04.3

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading my 16.04 installation today I noticed my VPN sessions
  suddenly had no name resolution anymore.

  Digging through /var/log/apt/history.log I noticed these were the
  updates:

  Start-Date: 2016-10-13  09:00:37
  Commandline: apt dist-upgrade
  Requested-By: jeroenr (1000)
  Upgrade: libnm-glib4:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), 
libsystemd0:amd64 (229-4ubuntu10, 229-4ubuntu11), libsystemd0:i386 
(229-4ubuntu10, 229-4ubuntu11), libdbusmenu-glib4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), 
google-chrome-stable:amd64 (53.0.2785.143-1, 54.0.2840.59-1), 
libnm-glib-vpn1:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), 
udev:amd64 (229-4ubuntu10, 229-4ubuntu11), libnm0:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), network-manager:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libdbusmenu-gtk4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), kbd:amd64 
(1.15.5-1ubuntu4, 1.15.5-1ubuntu5), libudev1:amd64 (229-4ubuntu10, 
229-4ubuntu11), libudev1:i386 (229-4ubuntu10, 229-4ubuntu11), libnm-util2:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libappstream-glib8:amd64 
(0.5.13-1ubuntu3, 0.5.13-1ubuntu4), gnome-calculator:amd64 (1:3.18.3-0ubuntu1, 
1:3.18.3-0
 ubuntu1.16.04.1), systemd-sysv:amd64 (229-4ubuntu10, 229-4ubuntu11), 
libpam-systemd:amd64 (229-4ubuntu10, 229-4ubuntu11), systemd:amd64 
(229-4ubuntu10, 229-4ubuntu11), gir1.2-dbusmenu-glib-0.4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), 
libdbusmenu-gtk3-4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 
16.04.1+16.04.20160927-0ubuntu1), lightdm:amd64 (1.18.2-0ubuntu2, 
1.18.3-0ubuntu1), liblightdm-gobject-1-0:amd64 (1.18.2-0ubuntu2, 
1.18.3-0ubuntu1)
  End-Date: 2016-10-13  09:01:06

  After downloading version 1.2.2-0ubuntu0.16.04.1 copies of libnm-glib-
  vpn1:amd64 libnm-glib4:amd64 libnm-util2:amd64 libnm0:amd64 network-
  manager:amd64 and installing them via: sudo -H dpkg -i *.deb my name
  resolution started working again.

  Additional information:

  % lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  % apt-cache policy libnm-glib-vpn1 libnm-glib4 libnm-util2 libnm0 
network-manager
  libnm-glib-vpn1:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libnm-glib4:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libnm-util2:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libnm0:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  network-manager:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  % apt-cache policy vpnc   
  vpnc:

[Touch-packages] [Bug 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

Also see:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633003

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

This seems related:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

The scope of this bug may not be limited to just VPN. There are reports of DNS 
being ignored for WiFi connections also:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629276

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1629276] Re: network-manager ignoring DNS settings in wifi connections

[Lonnie Lee Best]

DNS settings are being ignored on VPN connections as well:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874

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

Title:
  network-manager ignoring DNS settings in wifi connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since updating to network-manager 1.2.4-0ubuntu1 and libnss-resolve
  231-7 on the 28th, yakkety is now ignoring manual DNS settings on wifi
  connections.  The resolv.conf file is points to 127.0.1.1 instead of
  what is configured in the connection.

  
  To recreate
  ---
  On Ubuntu 16.10 (fully patched as of 2016-09-30):

  1) Create an ipv4 wifi connection, with a manually set a dns server.
  2) Connect to that wifi connection
  3) Test name resolution - it will still be using 127.0.1.1 instead of your 
manually configured server

  
  This might be considered a security problem for people that use special DNS 
configurations or dnscrypt.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep 30 05:47:57 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.9.240 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.9.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.9.153  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   wlp3s0wifi  connected
/org/freedesktop/NetworkManager/Devices/0  dusk
f7b9d8b8-06b6-4d6a-850b-cfd4ebec44ab  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp2s0f1  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   hfp/org/bluez/hci0/dev_4C_7C_5F_9E_A6_3C  gsm   unavailable  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   loloopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629276/+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 1633877] Re: VPN - "Additional Search Domains" Settings are being Ignored

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1629611 ***
https://bugs.launchpad.net/bugs/1629611

** This bug has been marked a duplicate of bug 1629611
   dns server priority broken

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

Title:
  VPN - "Additional Search Domains" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify "additional Search Domains" that are located on the virtual
  private network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  "additional Search Domains" that I've specified at the dialog I've
  linked above.

  Normally, after connecting to a VPN (where additional Search Domains
  are specified), the command (below) will show (in addition to your
  local Search Domains) the remote Search Domains (located on the VPN):

  nmcli dev show | grep DOMAIN

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name because the
  "Search Domains" I've specified are not getting appended to the
  computer-names I'm pinging.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional Search Domains are not making it here:

  nmcli dev show | grep DOMAIN

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 10:16:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

If the "order in which dns servers are queried" is flawed, as you've
discovered. That might be the root cause of a lot of other outstanding
bugs:

VPN - "Additional DNS servers" Settings are being Ignored:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874

network-manager ignoring DNS settings in wifi connections:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629276

VPN - "Additional Search Domains" Settings are being Ignored:
https://bugs.launchpad.net/network-manager-applet/+bug/1633877

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

Title:
  dns server priority broken

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1629611 ***
https://bugs.launchpad.net/bugs/1629611

** This bug has been marked a duplicate of bug 1629611
   dns server priority broken

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

Title:
  VPN - "Additional DNS servers" Settings are being Ignored

Status in Network Manager Applet:
  New
Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  During configuring of a VPN, Network Manager normally allows you to
  specify additional DNS servers that are located on the virtual private
  network:

  http://neartalk.com/ss/2016-10-16_001_601x625.png

  However, in Ubuntu 16.10 the network manager is ignoring the
  additional DNS that I've specified at the dialog I've linked above.

  Normally, after connecting to a VPN (where additional DNS servers are
  specified), the command (below) will show (in addition to your local
  DNS servers) the remote DNS servers (located on the VPN):

  nmcli dev show | grep DNS

  Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I
  cannot resolve remote computers by their computer-name, which is very
  inconvenient considering that I have over 100 Remmina connections set
  to resolve by name. Right now, I have to manually discover the IP
  addresses of the remote computer-names before connecting to the
  computers with Remmina.

  I've confirm this issue on both OpenVPN and Cisco vpnc connections.
  The additional DNS server are not making it here:

  nmcli dev show | grep DNS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 09:31:31 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874/+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 1634208] Re: VPN cannot resolve DNS entries on second connect

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1629611 ***
https://bugs.launchpad.net/bugs/1629611

** This bug is no longer a duplicate of bug 1633874
   VPN - "Additional DNS servers" Settings are being Ignored
** This bug has been marked a duplicate of bug 1629611
   dns server priority broken

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

Title:
  VPN cannot resolve DNS entries on second connect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10
  The first time I connect to a VPN (vpnc) everything works fine, but if I 
disconnect and then reconnect I can no longer resolve DNS entries although I 
can connect directly via IP address. The only solution seems to be a reboot.

  This was working fine in 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1634208/+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 1629276] Re: network-manager ignoring DNS settings in wifi connections

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1629611 ***
https://bugs.launchpad.net/bugs/1629611

** This bug has been marked a duplicate of bug 1629611
   dns server priority broken

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

Title:
  network-manager ignoring DNS settings in wifi connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since updating to network-manager 1.2.4-0ubuntu1 and libnss-resolve
  231-7 on the 28th, yakkety is now ignoring manual DNS settings on wifi
  connections.  The resolv.conf file is points to 127.0.1.1 instead of
  what is configured in the connection.

  
  To recreate
  ---
  On Ubuntu 16.10 (fully patched as of 2016-09-30):

  1) Create an ipv4 wifi connection, with a manually set a dns server.
  2) Connect to that wifi connection
  3) Test name resolution - it will still be using 127.0.1.1 instead of your 
manually configured server

  
  This might be considered a security problem for people that use special DNS 
configurations or dnscrypt.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Sep 30 05:47:57 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.9.240 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.9.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.9.153  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATEDBUS-PATH   
   CONNECTION  CON-UUID 
 CON-PATH   
   wlp3s0wifi  connected
/org/freedesktop/NetworkManager/Devices/0  dusk
f7b9d8b8-06b6-4d6a-850b-cfd4ebec44ab  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp2s0f1  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   hfp/org/bluez/hci0/dev_4C_7C_5F_9E_A6_3C  gsm   unavailable  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   loloopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629276/+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 1633003] Re: (Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1629611 ***
https://bugs.launchpad.net/bugs/1629611

** This bug is no longer a duplicate of bug 1633874
   VPN - "Additional DNS servers" Settings are being Ignored
** This bug has been marked a duplicate of bug 1629611
   dns server priority broken

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

Title:
  (Cisco) VPN name resolution breaks after upgrade to
  1.2.2-0ubuntu0.16.04.3

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading my 16.04 installation today I noticed my VPN sessions
  suddenly had no name resolution anymore.

  Digging through /var/log/apt/history.log I noticed these were the
  updates:

  Start-Date: 2016-10-13  09:00:37
  Commandline: apt dist-upgrade
  Requested-By: jeroenr (1000)
  Upgrade: libnm-glib4:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), 
libsystemd0:amd64 (229-4ubuntu10, 229-4ubuntu11), libsystemd0:i386 
(229-4ubuntu10, 229-4ubuntu11), libdbusmenu-glib4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), 
google-chrome-stable:amd64 (53.0.2785.143-1, 54.0.2840.59-1), 
libnm-glib-vpn1:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), 
udev:amd64 (229-4ubuntu10, 229-4ubuntu11), libnm0:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), network-manager:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libdbusmenu-gtk4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), kbd:amd64 
(1.15.5-1ubuntu4, 1.15.5-1ubuntu5), libudev1:amd64 (229-4ubuntu10, 
229-4ubuntu11), libudev1:i386 (229-4ubuntu10, 229-4ubuntu11), libnm-util2:amd64 
(1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libappstream-glib8:amd64 
(0.5.13-1ubuntu3, 0.5.13-1ubuntu4), gnome-calculator:amd64 (1:3.18.3-0ubuntu1, 
1:3.18.3-0
 ubuntu1.16.04.1), systemd-sysv:amd64 (229-4ubuntu10, 229-4ubuntu11), 
libpam-systemd:amd64 (229-4ubuntu10, 229-4ubuntu11), systemd:amd64 
(229-4ubuntu10, 229-4ubuntu11), gir1.2-dbusmenu-glib-0.4:amd64 
(12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), 
libdbusmenu-gtk3-4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 
16.04.1+16.04.20160927-0ubuntu1), lightdm:amd64 (1.18.2-0ubuntu2, 
1.18.3-0ubuntu1), liblightdm-gobject-1-0:amd64 (1.18.2-0ubuntu2, 
1.18.3-0ubuntu1)
  End-Date: 2016-10-13  09:01:06

  After downloading version 1.2.2-0ubuntu0.16.04.1 copies of libnm-glib-
  vpn1:amd64 libnm-glib4:amd64 libnm-util2:amd64 libnm0:amd64 network-
  manager:amd64 and installing them via: sudo -H dpkg -i *.deb my name
  resolution started working again.

  Additional information:

  % lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  % apt-cache policy libnm-glib-vpn1 libnm-glib4 libnm-util2 libnm0 
network-manager
  libnm-glib-vpn1:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libnm-glib4:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libnm-util2:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  libnm0:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  network-manager:
Installed: 1.2.2-0ubuntu0.16.04.1
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   1.2.2-0ubuntu0.16.04.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.2-0ubuntu0.16.04.1 100
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  % apt-cache policy vpnc   
  vpnc:
Installed: 0.5.3r550-2

[Touch-packages] [Bug 1629611] Re: dns server priority broken

[Lonnie Lee Best]

** Tags added: xenial yakkety

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

Title:
  dns server priority broken

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

Can someone figure out which of these debian bugs should be linked with
this Ubuntu bug report:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=dnsmasq;dist=unstable

** Bug watch added: Debian Bug tracker #777004
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777004

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

Title:
  dns server priority broken

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

Is this the cause:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777004

???

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

Title:
  dns server priority broken

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

One of us is going to have to endure submitting a new bug to debian
regarding this issue and then linking that bug to this ubuntu bug. I
think their bug system is email based and it is always an extra pain for
me to deal with. So, I'd appreciate not having to be the one to do this.
Thomas seems to have a good handle on this issue (hint hint).

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

Title:
  dns server priority broken

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

For me, on 16.04.1, that's:
debian stretch/sid

I'm experiencing the issue on both 16.04.1 and 16.10. I posted a work around 
here:
https://bugs.launchpad.net/network-manager-applet/+bug/1633874

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

Title:
  dns server priority broken

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

You can find out with this command:
cat /etc/debian_version

Source:
http://askubuntu.com/questions/445487/which-ubuntu-version-is-equivalent-to-debian-squeeze

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

Title:
  dns server priority broken

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+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 1629611] Re: dns server priority broken

[Lonnie Lee Best]

** Also affects: network-manager-openvpn
   Importance: Undecided
   Status: New

** Also affects: network-manager-vpnc
   Importance: Undecided
   Status: New

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+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 1542286] [NEW] package linux-image-4.4.0-2-generic 4.4.0-2.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Lonnie Lee Best]

*** This bug is a duplicate of bug 1541486 ***
https://bugs.launchpad.net/bugs/1541486

Public bug reported:

I got this error while upgrading from Ubuntu 15.10 to 16.04 (Alpha 2 I
think).

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-2-generic 4.4.0-2.16
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  lonnie 1656 F pulseaudio
 /dev/snd/controlC0:  lonnie 1656 F pulseaudio
Date: Fri Feb  5 05:38:49 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=154ec9be-4204-4fe0-9dcd-3e13f4b66375
InstallationDate: Installed on 2015-10-28 (99 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=97d572db-5554-4fa8-915d-e8bf227ce4a5 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-2-generic 4.4.0-2.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to xenial on 2016-02-05 (0 days ago)
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 7001
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 35.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv8 Notebook PC
dmi.product.version: 04992224121000104
dmi.sys.vendor: Hewlett-Packard

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

** This bug has been marked a duplicate of bug 1541486
   package linux-image-4.4.0-2-generic 4.4.0-2.16 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

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

Title:
  package linux-image-4.4.0-2-generic 4.4.0-2.16 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I got this error while upgrading from Ubuntu 15.10 to 16.04 (Alpha 2 I
  think).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lonnie 1656 F pulseaudio
   /dev/snd/controlC0:  lonnie 1656 F pulseaudio
  Date: Fri Feb  5 05:38:49 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=154ec9be-4204-4fe0-9dcd-3e13f4b66375
  InstallationDate: Installed on 2015-10-28 (99 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=97d572db-5554-4fa8-915d-e8bf227ce4a5 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-35ubuntu1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-2-generic 4.4.0-2.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-02-05 (0 days ago)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.na

[Touch-packages] [Bug 1558331] Re: After upgrading to apt 1.2.7 in Xenial, PPAs and most other third-party repositories become unusable with "The repository is insufficiently signed by key (weak diges

[Lonnie Lee Best]

I'm having the same issue with the google talk plugin, remmina, shutter,
and variety:

W: 
gpgv:/var/lib/apt/lists/ppa.launchpad.net_peterlevi_ppa_ubuntu_dists_xenial_InRelease:
 The repository is insufficiently signed by key 
876E675CB1AABA3494F27BA6C45A53C1A546BE4F (weak digest)
W: 
gpgv:/var/lib/apt/lists/partial/dl.google.com_linux_talkplugin_deb_dists_stable_Release.gpg:
 The repository is insufficiently signed by key 
4CCA1EAF950CEE4AB82976DCA040830F7FAC5991 (weak digest)
W: 
gpgv:/var/lib/apt/lists/ppa.launchpad.net_remmina-ppa-team_remmina-next_ubuntu_dists_xenial_InRelease:
 The repository is insufficiently signed by key 
04E38CE134B269B9F38F82EE8A993C2521C5F0BA (weak digest)
W: 
gpgv:/var/lib/apt/lists/ppa.launchpad.net_shutter_ppa_ubuntu_dists_xenial_InRelease:
 The repository is insufficiently signed by key 
5017D4931D0ACADE295B68ADFC6D8D9D009ED615 (weak digest)
W: Failed to fetch 
http://dl.google.com/linux/talkplugin/deb/dists/stable/Release  No Hash entry 
in Release file 
/var/lib/apt/lists/partial/dl.google.com_linux_talkplugin_deb_dists_stable_Release,
 which is considered strong enough for security purposes
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

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

Title:
  After upgrading to apt 1.2.7 in Xenial, PPAs and most other third-
  party repositories become unusable with "The repository is
  insufficiently signed by key  (weak digest)"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  The title pretty much says it all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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 1558331] Re: After upgrading to apt 1.2.7 in Xenial, PPAs and most other third-party repositories become unusable with "The repository is insufficiently signed by key (weak diges

[Lonnie Lee Best]

Can someone please set this bug to the highest reasonable importance?

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

Title:
  After upgrading to apt 1.2.7 in Xenial, PPAs and most other third-
  party repositories become unusable with "The repository is
  insufficiently signed by key  (weak digest)"

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  The title pretty much says it all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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