[Touch-packages] [Bug 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule

2017-04-19 Thread ChristianEhrhardt
@JJohansen - for testing I'd need that for ppc64el if possible.
My x86 machines go often down due to FW bugs if testing these cases.
Any chance to build a test kernel for that arch?

Since you have a test kernel it seems you have found the issue.
What is the way of delivery for this - normal kernel updates or anything more 
special?
Also do you know what Ubuntu releases are affected?

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+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 1681652] Re: Laptop screen does not turn off when closing lid from login screen.

2017-04-19 Thread Kai-Heng Feng
Ok, I misunderstood it.

I think what you want to say here (as slodki pointed out) is that Unity
Lockscreen does not turn off under this configuration.

** Also affects: unity (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Laptop screen does not turn off when closing lid from login screen.

Status in systemd package in Ubuntu:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  I'm running a new install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme 7414.
  I only changed in Power Settings: When plugged in >  When lid is close = Do 
Nothing
  Brightness & Lock Settings were not changed; Lock Screen after: Screen turns 
off

  If I close the laptop lid while logged in at the Unity Desktop, the
  screen will fade to black and turn off, which I think is normal and
  expected.

  Then when I open the lid I get the login screen, which I also expect.

  Now, if I don't login and just close the lid, the screen does not fade to 
black nor turn off.
  I would expect the screen to fade to black and turn off also from the login 
screen.

  This appears to be a small issue, at least on my system.
  If anyone needs specific information about the system, please ask.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681652/+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 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode

2017-04-19 Thread James Henstridge
With Chris's help we got the tests to get past the D-Bus errors on Zesty
by creating a file /etc/polkit-1/localauthority/50-local.d/manage-
units.pkla on the test system with the following contents:

# Allow the "ubuntu" user to manage systemd units unconditionally
for testing

[Allow manage-units]
Identity=unix-user:ubuntu

Action=org.freedesktop.systemd1.manage-units;org.freedesktop.systemd1.manage-unit-files
ResultAny=yes
ResultInactive=yes
ResultActive=yes

(It turned out that manage-unit-files was also needed to enable/disable
services).  This basically instructs polkitd to tell systemd that it is
okay for the "ubuntu" user to manage system services without having to
re-enter their password.  Assuming that's what you expect while running
the tests, the CI scripts should be updated to add this file to the
container.

There shouldn't be any need to special case this for Zesty: it should be
fine to create the .pkla file on older releases too.

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

Title:
  MachineSuite.TestMachineWorkers timed out waiting for workers zesty
  because dbus is in interactive mode

Status in juju:
  Incomplete
Status in juju 2.1 series:
  Won't Fix
Status in dbus package in Ubuntu:
  New

Bug description:
  As seen at
  http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e

  A unit test is exclusively failing on our new zesty machine. the
  previous issues is not related to the zesty falures

  machine-0: has workers [agent api-address-updater api-caller 
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater 
machine-action-runner machiner migration-fortress migration-inactive-flag 
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater 
state-config-watcher storage-provisioner termination-signal-handler 
unconverted-api-workers upgrade-check-flag upgrade-check-gate 
upgrade-steps-flag upgrade-steps-gate upgrader]
  machine-0: waiting for [unit-agent-deployer]
  machine-0: unexpected []
  machine-0: report: 
  {}

  
  machine_test.go:1272:
  WaitMatch(c, matcher.Check, coretesting.LongWait, 
s.BackingState.StartSync)
  engine_test.go:234:
  c.Fatalf("timed out waiting for workers")
  ... Error: timed out waiting for workers

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+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 1680421] Re: Computer suspends/sleeps before login

2017-04-19 Thread Kai-Heng Feng
HandleLidSwitch=ignore
HandleLidSwitchDocked=ignore

Does either one of the option work, or both are needed?

Also, what's the output of 'cat /proc/acpi/button/lid/LID0/state'?

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

Title:
  Computer suspends/sleeps before login

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  I am not able to login into the system because it sleeps in the boot
  process. To fix this, I need to edit (in recovery mode) the
  /etc/systemd/logind.conf to replace the following options:

  HandleLidSwitch=ignore
  HandleLidSwitchDocked=ignore

  This behaviour started in Ubuntu 14.10.

  Some other users have this issue too:
  
http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  6 08:25:20 2017
  InstallationDate: Installed on 2017-04-06 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405)
  MachineType: Positivo Positivo Mobile
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic 
root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: M5X0V
  dmi.board.vendor: CLEVO Co.
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Positivo Mobile
  dmi.product.version: VT6198
  dmi.sys.vendor: Positivo
  mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1680421/+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


Re: [Touch-packages] [Bug 1684324] [NEW] [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

2017-04-19 Thread Luke Yelavich
Try moving your pulseaudio config out of the way. Log out of your
desktop session, switch to a text virtual terminal by pressing control +
alt + f1, logging in there, and moving the pulseaudio config like so:

mv .config/pulse .config/pulse.old

Log out of the text terminal, switch back to the GUI login by pressing
Alt + F7, and then log in as normal, and see how things go.

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

Title:
  [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Upgraded to 17.04 from 16.10 today. Sound worked ok in previous
  versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed Apr 19 19:36:52 2017
  InstallationDate: Installed on 2015-03-28 (753 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)
  dmi.bios.vendor: Dell Inc.
  dmi.board.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1684324/+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 1670959] Re: systemd-resolved using 100% CPU

2017-04-19 Thread Tamas Papp
> This is a good workaround, but perhaps the actual fix should be to
remove the package on upgrade to 17.04?

What do you mean by this?
The fix should not ever something like this.
There is reason why dnsmasq is installed on these machines.

This is a workaround by not good.

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: 

[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode

2017-04-19 Thread James Henstridge
Anastasia asked me to take a look at this.  I'm still not sure what the
underlying cause is, but here is some of what I've discovered so far.

1. There has been a change in policykit-1 that sounds like it might be
relevant.  Namely:

  [ Martin Pitt ]
  * Use PAM's common-session-noninteractive modules for pkexec instead of
common-session. The latter also runs pam_systemd (the only difference
normally) which is a no-op under the classic session-centric
D-BUS/graphical login model (as it won't start a new one if it is already
running within a logind session), but very expensive when using
dbus-user-session and being called from a service that runs outside the
PAM session. This causes long delays in e. g. gnome-settings-daemon's
backlight helpers. (LP: #1626651)

So if something is being run by pkexec, it is no longer executing
pam_systemd.so.  That module is responsible for registering with logind,
setting up the user bus, etc.

So it seems possible that there is some code in the test suite that
looked like it was running under an interactive user session on Xenial,
but doesn't any more on Zesty.

2. The default policies for systemd1.manage-units haven't changed
between versions.  In both cases, it reads:



auth_admin
auth_admin
auth_admin_keep



So it is possible that the test works on previous versions by piggy
backing off a previous authorisation via auth_admin_keep.  If we look
like a non-interactive invocation on Zesty, we may need authentication
every time now.

3. Maybe we can bypass all of this by configuring the polkit local
authority to allow the test process to manage units unconditionally.
This would work for all versions irrespective of whether we look like an
interactive session.

This would involve placing a policy file under
/etc/polkit-1/localauthority/50-local.d before running the tests.

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

Title:
  MachineSuite.TestMachineWorkers timed out waiting for workers zesty
  because dbus is in interactive mode

Status in juju:
  Incomplete
Status in juju 2.1 series:
  Won't Fix
Status in dbus package in Ubuntu:
  New

Bug description:
  As seen at
  http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e

  A unit test is exclusively failing on our new zesty machine. the
  previous issues is not related to the zesty falures

  machine-0: has workers [agent api-address-updater api-caller 
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater 
machine-action-runner machiner migration-fortress migration-inactive-flag 
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater 
state-config-watcher storage-provisioner termination-signal-handler 
unconverted-api-workers upgrade-check-flag upgrade-check-gate 
upgrade-steps-flag upgrade-steps-gate upgrader]
  machine-0: waiting for [unit-agent-deployer]
  machine-0: unexpected []
  machine-0: report: 
  {}

  
  machine_test.go:1272:
  WaitMatch(c, matcher.Check, coretesting.LongWait, 
s.BackingState.StartSync)
  engine_test.go:234:
  c.Fatalf("timed out waiting for workers")
  ... Error: timed out waiting for workers

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+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 1684337] [NEW] CUPS 1.8.3 Canon MX330 Printer pauses at end of job

2017-04-19 Thread salemboot
Public bug reported:

I've had a history of issues with this printer and all versions of Ubuntu after 
10.04.
The cause is CUPS changed after 10.04.  There are various documented instances 
of it continuously happening.  Most of the threads end with a patch being made 
but unfortunately I've yet to see a new version of Ubuntu (14/15/16.04) finally 
resolve the issue.

I know running this command temporarily fixes the problem.
I experienced another hang tonight during a print job.  So even this solution 
seems interim.

lpadmin -p MX330-series -o usb-unidir-default=true

If anyone else with the issues is going to try the above command, you
need to get your printer designation from 'lpstat -p' command output.

Thanks for your time.

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

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

Title:
  CUPS 1.8.3 Canon MX330 Printer pauses at end of job

Status in cups package in Ubuntu:
  New

Bug description:
  I've had a history of issues with this printer and all versions of Ubuntu 
after 10.04.
  The cause is CUPS changed after 10.04.  There are various documented 
instances of it continuously happening.  Most of the threads end with a patch 
being made but unfortunately I've yet to see a new version of Ubuntu 
(14/15/16.04) finally resolve the issue.

  I know running this command temporarily fixes the problem.
  I experienced another hang tonight during a print job.  So even this solution 
seems interim.

  lpadmin -p MX330-series -o usb-unidir-default=true

  If anyone else with the issues is going to try the above command, you
  need to get your printer designation from 'lpstat -p' command output.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1684337/+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 1684332] [NEW] package click-apparmor 0.3.17 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-04-19 Thread Guangning
Public bug reported:

This happens when I am upgrading from 16.10 to 17.04 via terminal.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: click-apparmor 0.3.17
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Wed Apr 19 20:38:04 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-04-08 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: click-apparmor
Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: click-apparmor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  This happens when I am upgrading from 16.10 to 17.04 via terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 19 20:38:04 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1684332/+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 1684332] Re: package click-apparmor 0.3.17 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-04-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  This happens when I am upgrading from 16.10 to 17.04 via terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 19 20:38:04 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1684332/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection

2017-04-19 Thread TylerKinkade
Sorry, just now saw your comment, Po-Hsu Lin. I will try with 17.04
LiveCD when I have a spare moment. It's the beginning of the school year
here, so I have my hands full teaching at the moment.

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-19 Thread Tamas Papp
Weird, I can reproduce the issue again after about 1-2 weeks of silence...
I can test the DNSSEC=off setting.

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2017-04-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-19 Thread Colan Schwartz
@clvx: I think the other bug is unrelated, although maybe that's what
you're running into instead of this one.

I was also able to fix this problem by removing dnsmasq:

* sudo apt remove dnsmasq

As soon as I did that, both processes dropped to nothing, and DNS still
resolves.

This is a good workaround, but perhaps the actual fix should be to
remove the package on upgrade to 17.04?

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  

[Touch-packages] [Bug 1684324] [NEW] [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

2017-04-19 Thread Jack Timothy Dicus
Public bug reported:

Upgraded to 17.04 from 16.10 today. Sound worked ok in previous
versions.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tim1857 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Wed Apr 19 19:36:52 2017
InstallationDate: Installed on 2015-03-28 (753 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tim1857 F pulseaudio
Symptom_Jack: Green Line Out, Rear
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all
UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)
dmi.bios.vendor: Dell Inc.
dmi.board.vendor: Dell Inc.

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


** Tags: amd64 apport-bug zesty

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

Title:
  [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Upgraded to 17.04 from 16.10 today. Sound worked ok in previous
  versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Wed Apr 19 19:36:52 2017
  InstallationDate: Installed on 2015-03-28 (753 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim1857 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)
  dmi.bios.vendor: Dell Inc.
  dmi.board.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1684324/+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 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi adapters from working (mac address randomization)

2017-04-19 Thread wolfy1339
This affects Microsoft Surface Pro devices (internal WiFi adapter)

** Summary changed:

- Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi 
adapters from working (mac address randomization)
+ Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi adapters 
from working (mac address randomization)

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi
  adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1654918] Re: No Internet access with default of Automatic (DHCP)

2017-04-19 Thread IrishGuy
Same thing on an upgrade from 16.04 to 17.04. Some internet immediately
after the upgrade, same issue as noted above with software updates
needing multiple tries to access the repos, currently internet
completely dead even with a reboot.

Note this was a Software Updater suggested dist upgrade - I think that
should be pulled, 17.04 shouldn't be auto suggesting for users in this
state.

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

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  New
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & 
manually add Google DNS nameservers: then internet is enabled. screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlp8s0
     version: 73
     serial: 
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 
link=ye s multicast=yes wireless=IEEE 802.11
     resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+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

2017-04-19 Thread 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 1629611] Re: dns server priority broken

2017-04-19 Thread 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 1633874] Re: VPN - "Additional DNS servers" Settings are being Ignored

2017-04-19 Thread 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 1684308] [NEW] Randomly stops printing, leaving zebra printer in a state that overheats.

2017-04-19 Thread Dustin R
Public bug reported:

Both Cups versions below are using the same KR203 ppd and rasterfile.

Cups 1.5.3-0ubuntu8
Zebra KR203 printer works fine

Cups 2.1.3-4
Zebra KR203 printer will print a couple test pages sent from Cups. In less 
than 10 test pages it will start to feed the paper and print a little, then 
stops everything. It has the paper partially fed through with only some of the 
test page printed. There is not a set number of pages that work before it 
breaks, it is random.

If the printer is left in this state it will start to get hot! I smelled
a hot electronic smell after only a few minuets. To recover, I have to
power cycle the printer.

This happened on two seperate brand new Zebra KR203 printers. As I
mentioned this printer works fine on the Version mentioned above.
Obviously once I noticed it will overheat I do not leave it in that
state very long as to not damage the hardware.

I checked cups logs and I did not noticed anything.

Let me know what other information I can provide so we can resolve this.

Thank you

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


** Tags: xenialxerus

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

Title:
  Randomly stops printing, leaving zebra printer in a state that
  overheats.

Status in cups package in Ubuntu:
  New

Bug description:
  Both Cups versions below are using the same KR203 ppd and rasterfile.

  Cups 1.5.3-0ubuntu8
  Zebra KR203 printer works fine

  Cups 2.1.3-4
  Zebra KR203 printer will print a couple test pages sent from Cups. In 
less than 10 test pages it will start to feed the paper and print a little, 
then stops everything. It has the paper partially fed through with only some of 
the test page printed. There is not a set number of pages that work before it 
breaks, it is random.

  If the printer is left in this state it will start to get hot! I
  smelled a hot electronic smell after only a few minuets. To recover, I
  have to power cycle the printer.

  This happened on two seperate brand new Zebra KR203 printers. As I
  mentioned this printer works fine on the Version mentioned above.
  Obviously once I noticed it will overheat I do not leave it in that
  state very long as to not damage the hardware.

  I checked cups logs and I did not noticed anything.

  Let me know what other information I can provide so we can resolve
  this.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1684308/+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

2017-04-19 Thread Thomas M Steenholdt
Seems to work in 1.4.4-1ubuntu3 in 17.04 at least... Thanks

-- 
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 1684306] Re: tracker-extract crashed with signal 5 in g_malloc()

2017-04-19 Thread Apport retracing service
*** This bug is a duplicate of bug 1347620 ***
https://bugs.launchpad.net/bugs/1347620

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1347620, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1684306/+attachment/4865199/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1684306/+attachment/4865201/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1684306/+attachment/4865203/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1684306/+attachment/4865204/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1684306/+attachment/4865205/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1684306/+attachment/4865206/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1684306/+attachment/4865207/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1347620

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with signal 5 in g_malloc()

Status in tracker package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 14.04.5 LTS
  Release:14.04
  tracker:
Paigaldatud: 0.16.5-0ubuntu0.2
Kandidaat:   0.16.5-0ubuntu0.2
Versioonitabel:
   *** 0.16.5-0ubuntu0.2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu/ trusty-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.16.2-1ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: tracker-extract 0.16.5-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Apr 19 19:18:26 2017
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-04-18 (732 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  Signal: 5
  SourcePackage: tracker
  StacktraceTop:
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_buffer_new_allocate () from 
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0
  Title: tracker-extract crashed with signal 5 in g_malloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1684306/+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 1681228] Re: LightDM Unityt-Gretter is wrong resolution

2017-04-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lightdm (Ubuntu)
   Status: New => Confirmed

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

Title:
  LightDM Unityt-Gretter is wrong resolution

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Running on a macbook pro 15" at 2880 x 1800.

  At 16.04 the greeter starts at the correct resolution and then after a
  couple of secs changes to what looks like 2X scaling.

  I updated to 16.10 and now the greeter boots directly into the 2z
  scaling.

  It almost seems like the bug was fixed backwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr  9 10:27:54 2017
  InstallationDate: Installed on 2017-04-01 (8 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to yakkety on 2017-04-07 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1681228/+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 1421923] Re: No notifications for new mails

2017-04-19 Thread Gregory Opera
Ubuntu 16.04 LTS ("Xenial Xerus") here, and I too have no notifications
for new e-mails... "Pulling" to refresh does not seem to work, and
closing then re-opening usually doesn't work either.

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

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Canonical System Image:
  In Progress
Status in Dekko:
  In Progress
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty

2017-04-19 Thread Andrei Coada
** Summary changed:

- Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty
+ Security issues (solved in Debian) - affecting icu52 in trusty

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

Title:
  Security issues (solved in Debian) - affecting icu52 in trusty

Status in icu package in Ubuntu:
  New

Bug description:
  Date Reported:
  19 Apr 2017

  Security database references:
  In the Debian bugtracking system: 860314.
  In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868.

  More information:
  It was discovered that icu, the International Components for Unicode library, 
did not correctly validate its input. An attacker could use this problem to 
trigger an out-of-bound write through a heap-based buffer overflow, thus 
causing a denial of service via application crash, or potential execution of 
arbitrary code.

  For the stable distribution (jessie), these problems have been fixed
  in version 52.1-8+deb8u5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+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 1684233] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-04-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ntp package in Ubuntu:
  New

Bug description:
  no idea how to explain or fix the issue, but it is causing me to not
  be able to access the school network or internet from the school
  network ethernet switch.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 11:02:59 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-14 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+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 1684233] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-04-19 Thread Seth Arnold
Hello, your logs indicate some problems. It sure looks like your
/usr/sbin/adduser and /usr/sbin/addgroup programs have been modified and
that appears to be preventing other programs from running correctly.
Repairing this may be difficult depending upon when those programs were
corrupted and what might have tried to use them in the meantime.

Perhaps this is accidental and perhaps this is malicious. (If malicious
it's very sloppy.)

If you think this is accidental try:
sudo apt-get install --reinstall adduser

The logs:

adduser 3.113+nmu3ubuntu4 [modified: usr/sbin/adduser]

Setting up ntp (1:4.2.8p4+dfsg-3ubuntu5.4) ...
Installing new version of config file /etc/dhcp/dhclient-exit-hooks.d/ntp ...
/usr/sbin/addgroup: 32: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 33: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 34: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 35: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 38: /usr/sbin/addgroup: my: not found
/usr/sbin/addgroup: 43: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 44: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 45: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 46: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 47: /usr/sbin/addgroup: use: not found
/usr/sbin/addgroup: 52: /usr/sbin/addgroup: BEGIN: not found
/usr/sbin/addgroup: 53: local: not in a function
dpkg: error processing package ntp (--configure):
 subprocess installed post-installation script returned error exit status 2

Thanks

** Information type changed from Private Security to Public

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in ntp package in Ubuntu:
  New

Bug description:
  no idea how to explain or fix the issue, but it is causing me to not
  be able to access the school network or internet from the school
  network ethernet switch.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.4
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 11:02:59 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-02-14 (63 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=28cffc81-a318-4788-996b-6ba760b5a61d ro priority=low quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1684233/+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 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi adapters from working (mac address randomization)

2017-04-19 Thread Don Cady
I have this problem too. Adding wifi.scan-rand-mac-address=no to
NetworkManager.conf does resolve it.

A relevant question: Why does this only affect usb wifi dongles? My
internal iwl3945 chip was/is not affected. How does Network Manager
treat pci and usb devices differently?

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some USB
  WiFi adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1684298] [NEW] Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty

2017-04-19 Thread Andrei Coada
*** This bug is a security vulnerability ***

Public security bug reported:

Date Reported:
19 Apr 2017

Security database references:
In the Debian bugtracking system: 860314.
In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868.

More information:
It was discovered that icu, the International Components for Unicode library, 
did not correctly validate its input. An attacker could use this problem to 
trigger an out-of-bound write through a heap-based buffer overflow, thus 
causing a denial of service via application crash, or potential execution of 
arbitrary code.

For the stable distribution (jessie), these problems have been fixed in
version 52.1-8+deb8u5.

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

** Information type changed from Public to Public Security

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7867

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7868

** Description changed:

  Date Reported:
  19 Apr 2017
  
  Security database references:
- In the Debian bugtracking system: Bug 860314.
+ In the Debian bugtracking system: 860314.
  In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868.
  
  More information:
  It was discovered that icu, the International Components for Unicode library, 
did not correctly validate its input. An attacker could use this problem to 
trigger an out-of-bound write through a heap-based buffer overflow, thus 
causing a denial of service via application crash, or potential execution of 
arbitrary code.
  
  For the stable distribution (jessie), these problems have been fixed in
  version 52.1-8+deb8u5.

** Summary changed:

- Security issues (solved in Debian)
+ Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty

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

Title:
  Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5
  trusty

Status in icu package in Ubuntu:
  New

Bug description:
  Date Reported:
  19 Apr 2017

  Security database references:
  In the Debian bugtracking system: 860314.
  In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868.

  More information:
  It was discovered that icu, the International Components for Unicode library, 
did not correctly validate its input. An attacker could use this problem to 
trigger an out-of-bound write through a heap-based buffer overflow, thus 
causing a denial of service via application crash, or potential execution of 
arbitrary code.

  For the stable distribution (jessie), these problems have been fixed
  in version 52.1-8+deb8u5.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+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 1684279] Re: /dev/dri/card0 missing

2017-04-19 Thread Timo Aaltonen
you need to make sure linux-image-...-extra is installed, and that
nomodeset is not used

** Changed in: libdrm (Ubuntu)
   Status: New => Invalid

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

Title:
  /dev/dri/card0 missing

Status in libdrm package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04.5 with kernel 3.19.0-80 working fine, but when kernels
  4.4+ installed /dev/dri/card0 went missing. It was from 4.4.0-59 till
  4.4.0-74. In old bugs I've found the same issue, but there was "card0"
  in the "/dev". I don't have one. Software rendering is not good at
  all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1684279/+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 1684223] Re: package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2017-04-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in ido package in Ubuntu:
  New

Bug description:
  dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Wed Apr 19 21:47:57 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-16 (154 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ido
  Title: package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1684223/+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 1615482] Re: apt-daily timer runs at random hours of the day

2017-04-19 Thread Achim Spangler
According to https://ubuntuforums.org/showthread.php?t=2330407=2 I
am not the only user, where the package list is never updated due to the
default timer setting in /etc/systemd/system/timers.target.wants/apt-
daily.timer . This way, the Taskbar-GUI App never displays any available
package updates, as long as you don't call "sudo apt-get update"
manually.

This problem is caused by using the computer only for short durations
(e.g. notebook), so that the calculated random wait time is longer than
the average usage time per day (i.e. "apt-get update" is never called).

My personal solution was to use a fixed wait time after system boot of
about 5 minutes (see attachement), and use "After=network.target" to
make sure, that the network is ready for successfull call of "apt-get
update" (see attachement).

Maybe the system could get enhanced to derive the average uptime per
session / day, so that the apt-daily timer gets restricted to this
average time interval.

Or the system could detect, whether the computer is used as a
continually running system, or whether the computer is each time only
running for some hours. In the latter case, at least the package list
should get updated a short time after system start / boot.

My system is running Kubuntu 6.04 LTS _Xenial.

** Attachment added: "Call apt 5 minutes after system boot for short running 
computer"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+attachment/4865174/+files/apt-daily.timer

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Triaged

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+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 1654918] Re: No Internet access with default of Automatic (DHCP)

2017-04-19 Thread hrvooje
All day at work no problems. Neither WiFi or ethernet. At home after a
while can't load a website. After restarting service network-manager it
works again. It is interesting that in that time torrents
download/upload worked and I could ping 8.8.8.8 and other IPs on the
Internet. Just couldn't load websites. It is not my broadcom card driver
problem, I can access my router.

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

Title:
  No Internet access with default of  Automatic (DHCP)

Status in Linux:
  New
Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Fresh 17.04 install, wireless router connects without any issue but there is 
no internet connection/access.
  This continues thru disconnecting, reconnecting, rebooting ect, Nothing..

  If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses only & 
manually add Google DNS nameservers: then internet is enabled. screen attached
  Note this also affects ethernet, not just wireless
  Hardware is:
  description: Wireless interface
     product: Wireless 7260
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:08:00.0
     logical name: wlp8s0
     version: 73
     serial: 
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4 latency=0 
link=ye s multicast=yes wireless=IEEE 802.11
     resources: irq:32 memory:c240-c2401fff

  To note: this hardware works perfectly in 14.04 > 16.04
  Add. note; issue doesn't arise with 4.11.x kernel

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.2-2ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  8 22:08:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-09 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
  IpRoute:
   default via 192.168.1.1 dev wlp8s0  proto static  metric 600
   169.254.0.0/16 dev wlp8s0  scope link  metric 1000
   192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4  metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1654918/+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 1684127] Re: ok

2017-04-19 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  ok

Status in xorg package in Ubuntu:
  New

Bug description:
  ok

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Wed Apr 19 19:12:51 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GF119M [NVS 4200M] [1028:0493]
  InstallationDate: Installed on 2017-04-16 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=7500dc41-1b41-47c4-8e48-515e3cce049d ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A21
  dmi.board.name: 04GH8W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn04GH8W:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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: Wed Apr 19 18:28:08 2017
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1684127/+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 1684223] Re: package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2017-04-19 Thread Seth Arnold
Hello, I suggest trying

sudo apt-get install --reinstall libido3-0.1-0

Thanks

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

Title:
  package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in ido package in Ubuntu:
  New

Bug description:
  dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Wed Apr 19 21:47:57 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-16 (154 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ido
  Title: package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1684223/+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 1684223] Re: package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

2017-04-19 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in ido package in Ubuntu:
  New

Bug description:
  dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Wed Apr 19 21:47:57 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-16 (154 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: ido
  Title: package libido3-0.1-0:i386 13.10.0+15.10.20151002-0ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1684223/+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 1634598] Re: gnome-online-accounts Problems on Wayland

2017-04-19 Thread Christopher
@Jeremy Two things,

The issue of using the accounts with google identity platform seems to
be fixed (latest 16.10 patches). Not sure when that fix went in but I
tried it in testing.

Your workaround for rebooting to make online accounts work does work.
I'm able to confirm that you need to reboot to get online accounts to
accept an added credential. Is there a subsystem that I can restart to
just "make it work"? Like what if I HUP gnome?

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

Title:
  gnome-online-accounts Problems on Wayland

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  When using gnome-online-accounts + wayland.

  When tshooting [LP1610944](https://bugs.launchpad.net/bugs/1610944) I
  noticed that you can't add a google account that utilizes
  customizations from [Google's Identity
  Platform](https://developers.google.com/identity/). This is used by
  many Google Apps for Work systems (including mine). This however does
  work on gnome with X. I believe this is a wayland specific issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1634598/+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 1634598] Re: gnome-online-accounts Problems on Wayland

2017-04-19 Thread Christopher
Additionally, I'll be installing 17.04 in the coming weeks so I'll be
able to try and confirm if this is the case in that version too.

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

Title:
  gnome-online-accounts Problems on Wayland

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  When using gnome-online-accounts + wayland.

  When tshooting [LP1610944](https://bugs.launchpad.net/bugs/1610944) I
  noticed that you can't add a google account that utilizes
  customizations from [Google's Identity
  Platform](https://developers.google.com/identity/). This is used by
  many Google Apps for Work systems (including mine). This however does
  work on gnome with X. I believe this is a wayland specific issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1634598/+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


Re: [Touch-packages] [Bug 1654918] Re: No Internet access with default of Automatic (DHCP)

2017-04-19 Thread David Oser
On second thoughts, despite 'dnsutils' and 'bind9-host' updates 17.04 is
still buggy on my two Toshiba laptops (one ancient, one less so). Can take
up to three attempts to resolve all repositories with 'sudo apt update'
after boot. Alternatively, on first attempts, browsers (Firefox, Chromium)
do not connect to sites - but then, after a while do so. Bizarre.
Been using Ubuntu since 9.x - never encountered this irritation before. So
it's not because I'm using USB stick installations. However, I am, as ever
using copper wire at 16-20 Mbit/s - but that's never beena problem before...
To actually receive the updates I needed to use the Google DNS 8.8.8.8 on
IPV4 - thereafter deleting this.
I'm now using two (full install, not 'live) USB sticks with 17.04 booting
to them on either laptop - but am holding off upgrading from 16.10 on my
main (newer uefi) machine until the issue is fully resolved.

On 18 April 2017 at 10:22, David Oser  wrote:

> Fortunately I had retained 17.04 full installation on a USB stick.
> Downloaded new update via Google DNS on IPV4, then deleted 8.8.8.8 and
> tested. Seems to be working. So far so good Thanks for the heads-up
> hrvooje!
> Best
> David
>
> On 18 April 2017 at 07:09, hrvooje <1654...@bugs.launchpad.net> wrote:
>
>> This morning I got dnsutils and bind9-host updates. Could this be the
>> fix? So far so good, no disconecting last hour.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1654918
>>
>> Title:
>>   No Internet access with default of  Automatic (DHCP)
>>
>> Status in Linux:
>>   New
>> Status in NetworkManager:
>>   New
>> Status in network-manager package in Ubuntu:
>>   Confirmed
>>
>> Bug description:
>>   Fresh 17.04 install, wireless router connects without any issue but
>> there is no internet connection/access.
>>   This continues thru disconnecting, reconnecting, rebooting ect,
>> Nothing..
>>
>>   If I edit the connection > IPv4 Settings to Automatic (DCHP) addresses
>> only & manually add Google DNS nameservers: then internet is enabled.
>> screen attached
>>   Note this also affects ethernet, not just wireless
>>   Hardware is:
>>   description: Wireless interface
>>  product: Wireless 7260
>>  vendor: Intel Corporation
>>  physical id: 0
>>  bus info: pci@:08:00.0
>>  logical name: wlp8s0
>>  version: 73
>>  serial: 
>>  width: 64 bits
>>  clock: 33MHz
>>  capabilities: pm msi pciexpress bus_master cap_list ethernet
>> physical wireless
>>  configuration: broadcast=yes driver=iwlwifi
>> driverversion=4.9.0-11-generic firmware=17.352738.0 ip=192.168.1.4
>> latency=0 link=ye s multicast=yes wireless=IEEE 802.11
>>  resources: irq:32 memory:c240-c2401fff
>>
>>   To note: this hardware works perfectly in 14.04 > 16.04
>>   Add. note; issue doesn't arise with 4.11.x kernel
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 17.04
>>   Package: network-manager 1.4.2-2ubuntu4
>>   ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
>>   Uname: Linux 4.9.0-11-generic x86_64
>>   ApportVersion: 2.20.4-0ubuntu1
>>   Architecture: amd64
>>   CurrentDesktop: Unity
>>   Date: Sun Jan  8 22:08:26 2017
>>   IfupdownConfig:
>># interfaces(5) file used by ifup(8) and ifdown(8)
>>auto lo
>>iface lo inet loopback
>>   InstallationDate: Installed on 2017-01-09 (0 days ago)
>>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170108)
>>   IpRoute:
>>default via 192.168.1.1 dev wlp8s0  proto static  metric 600
>>169.254.0.0/16 dev wlp8s0  scope link  metric 1000
>>192.168.1.0/24 dev wlp8s0  proto kernel  scope link  src 192.168.1.4
>> metric 600
>>   NetworkManager.conf:
>>[main]
>>plugins=ifupdown,keyfile
>>
>>[ifupdown]
>>managed=false
>>   NetworkManager.state:
>>[main]
>>NetworkingEnabled=true
>>WirelessEnabled=true
>>WWANEnabled=true
>>   SourcePackage: network-manager
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   nmcli-dev:
>>DEVICE  TYPE  STATEDBUS-PATH
>> CONNECTION  CON-UUID  CON-PATH
>>wlp8s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2
>> 06F21A  fb815a75-4091-455e-b73d-2c1f2d97220f
>> /org/freedesktop/NetworkManager/ActiveConnection/0
>>enp7s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1
>> --  ----
>>lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0
>> --  ----
>>   nmcli-nm:
>>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
>> WIFI-HW  WIFI WWAN-HW  WWAN
>>running  1.4.2connected  started  full  enabled
>>  enabled  enabled  enabled  enabled
>>
>> To manage notifications about this bug go to:
>> 

[Touch-packages] [Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

2017-04-19 Thread Seth Forshee
Confirmed that the test in the 232-21ubuntu3 source package no longer
hangs.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Due to upgraded netcat in zesty, ADT testcase 12 started to hang upon 
calls to netcat.
   * The upgraded netcat changed default behaviour from -q0 (quit straight 
away) to -q-1 (wait infinity)
   * Proposed fix is an upstream cherry-pick to add a `-w1` option (quit after 
1 second) which resolves the test-suite hang and is compatible across Ubuntu 
and Fedora (uses nmap netcat).

  [Test Case]

   * ADT tests should pass on kvm architectures.

  [Regression Potential]

   * This is a testsuite fix for netcat-openbsd compat, does not affect
  systemd runtime binaries / libraries.

  [Other Info]
   
   * Original bug report.

  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+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 1684279] [NEW] /dev/dri/card0 missing

2017-04-19 Thread Wizard
Public bug reported:

Ubuntu 14.04.5 with kernel 3.19.0-80 working fine, but when kernels 4.4+
installed /dev/dri/card0 went missing. It was from 4.4.0-59 till
4.4.0-74. In old bugs I've found the same issue, but there was "card0"
in the "/dev". I don't have one. Software rendering is not good at all.

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

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

Title:
  /dev/dri/card0 missing

Status in libdrm package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.5 with kernel 3.19.0-80 working fine, but when kernels
  4.4+ installed /dev/dri/card0 went missing. It was from 4.4.0-59 till
  4.4.0-74. In old bugs I've found the same issue, but there was "card0"
  in the "/dev". I don't have one. Software rendering is not good at
  all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1684279/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt

2017-04-19 Thread Tyler Hicks
Thanks! The debdiff looks good. The only adjustment that I made was
yakkety -> yakkety-security since this needs to go to the security
pocket.

I've uploaded the package to the ubuntu-security-proposed PPA:

  https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa

Let the security team know when this package should be copied to
yakkety-proposed.

** Also affects: software-properties (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: shim-signed (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: shim-signed (Ubuntu Trusty)

** No longer affects: shim-signed (Ubuntu Xenial)

** No longer affects: shim-signed (Ubuntu Yakkety)

** Changed in: software-properties (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: software-properties (Ubuntu Yakkety)
   Importance: Undecided => Critical

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

Title:
  Changing from Xorg video driver to NVIDIA driver using Software &
  Updates does not display debconf prompt

Status in shim-signed package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Trusty:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Yakkety:
  Confirmed

Bug description:
  I've encountered this repeatedly.

  In the first installation -- on updating via Software Updater, this
  crashed on upgrading the shim-signed package.

  On suggestions from here:

  I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
  however when I now try to swap the display driver, from xorg -->
  nvidia. This now triggered the same issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 18:21:32 2017
  DuplicateSignature:
   package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
   Processing triggers for shim-signed 
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
   Running in non-interactive mode, doing nothing.
   dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shim-signed
  Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+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


Re: [Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

2017-04-19 Thread Sam Hartman
> "Joshua" == Joshua Powers  writes:

Joshua> If we want to fix this in zesty, then a release with only
Joshua> the bug fixes would be desired. That could be SRU'ed
Joshua> assuming it is not too big of a change such that it would
Joshua> limit the exposure to new issues or changes in
Joshua> features/functionality.

OK, I'll look at pulling a bugfix release into experimental now.  I sure
hope stretch releases before  17.10:-)

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Changed in: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: isc-dhcp (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Xenial also has both distinct dhclient binary package but in the
  opposite way. We have decided to use the opposite way approach for not
  impacting actual Trusty users by changing the nature of isc-dhcp-
  client itself.

  Caribou and I, slashd, have also tested a couple of release upgrades from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  Results :
  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient

  ** Upgrade tested with isc-dhcp-noddns (4.2.4-7ubuntu12.9) 

[Touch-packages] [Bug 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt

2017-04-19 Thread Steve Langasek
debdiff for yakkety. In order to ensure the correct upgrade semantics,
this needs to go to the security pocket.

** Patch added: "software-properties-1679784-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1679784/+attachment/4865065/+files/software-properties-1679784-yakkety.debdiff

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

Title:
  Changing from Xorg video driver to NVIDIA driver using Software &
  Updates does not display debconf prompt

Status in shim-signed package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  I've encountered this repeatedly.

  In the first installation -- on updating via Software Updater, this
  crashed on upgrading the shim-signed package.

  On suggestions from here:

  I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
  however when I now try to swap the display driver, from xorg -->
  nvidia. This now triggered the same issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 18:21:32 2017
  DuplicateSignature:
   package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
   Processing triggers for shim-signed 
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
   Running in non-interactive mode, doing nothing.
   dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: shim-signed
  Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+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 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

2017-04-19 Thread Joshua Powers
If we want to fix this in zesty, then a release with only the bug fixes
would be desired. That could be SRU'ed assuming it is not too big of a
change such that it would limit the exposure to new issues or changes in
features/functionality.

For fixing this in the 17.10 release, then picking up the new release
with fixes makes sense.

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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


Re: [Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

2017-04-19 Thread Sam Hartman
I can put something in debian experimental if that makes the sync
easier.
So, you'd prefer just the Debian 1.15-1 with bug fixes rather than a
1.15.1?

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1684252] [NEW] package account-plugin-google (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/accounts/services/google-im.service », qui appar

2017-04-19 Thread Matthieu Agn
Public bug reported:

i have no graphical interface whatsoever, only see the desktop

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-google (not installed)
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Apr 19 19:41:09 2017
ErrorMessage: tentative de remplacement de « 
/usr/share/accounts/services/google-im.service », qui appartient aussi au 
paquet kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2016-12-20 (120 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: account-plugins
Title: package account-plugin-google (not installed) failed to install/upgrade: 
tentative de remplacement de « /usr/share/accounts/services/google-im.service 
», qui appartient aussi au paquet kde-config-telepathy-accounts 
4:15.12.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package account-plugin-google (not installed) failed to
  install/upgrade: tentative de remplacement de «
  /usr/share/accounts/services/google-im.service », qui appartient aussi
  au paquet kde-config-telepathy-accounts 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  i have no graphical interface whatsoever, only see the desktop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-google (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr 19 19:41:09 2017
  ErrorMessage: tentative de remplacement de « 
/usr/share/accounts/services/google-im.service », qui appartient aussi au 
paquet kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-12-20 (120 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: account-plugins
  Title: package account-plugin-google (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/share/accounts/services/google-im.service », qui appartient aussi au 
paquet kde-config-telepathy-accounts 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1684252/+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 1668593] Re: Wireless adapter causes hard crash

2017-04-19 Thread Don Cady
The two adapters you've listed are both using the rtl8192cu driver that
is bug #1666421 , this is a possible duplicate.

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

Title:
  Wireless adapter causes hard crash

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to a wifi using a USB wifi adapter, the system
  crashes/freezes immediately. There is nothing in the syslog or
  anywhere else. This can be reproduced on Ubuntu 14.04 and 16.04.
  Enabling the adapter works, but the freeze occurs as soon as I try to
  log into the network.

  This used to work, but has been broken for a few weeks I assume. It
  happens with all USB adapters I tested, on all machines.

  Adapter 1:

     description: Wireless interface
     physical id: 1
     bus info: usb@2:1.1.1
     logical name: wlx74da388dc809
     serial: [redacted]
     capabilities: ethernet physical wireless
     configuration: broadcast=yes driver=rtl8192cu 
driverversion=4.4.0-64-generic firmware=N/A link=no multicast=yes wireless=IEEE 
802.11bgn

  Adapter 2:

     description: Wireless interface
     physical id: 1
     bus info: usb@2:1.1.1
     logical name: wlx24050f75f9a2
     serial: [redacted]
     capabilities: ethernet physical wireless
     configuration: broadcast=yes driver=rtl8192cu 
driverversion=4.4.0-64-generic firmware=N/A link=no multicast=yes wireless=IEEE 
802.11bgn

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1668593/+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 1671611] Re: USB wi-fi dongles not working with latest updates

2017-04-19 Thread Don Cady
So with that rtl8192 dongle, it crashes/freezes/locks up?
See bug #1666421 , this is a possible duplicate.

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

Title:
  USB wi-fi dongles not working with latest updates

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same laptop - two different network dongles (ASUS USB-N13 + Edimax
  cheap commonly used with RaspPis). Confirmed issue with xenial-updates
  and xenial-security versions. Going to try to force a downgrade to
  original xenial to see if it still happens.

  ASUS dongle -> $ inxi -Fxxrzc0 | pastebin
  https://gist.github.com/d926d05c2bd23226a9f4b4a593b9de65

  Edimax dongle -> $ inxi -Fxxrzc0 | pastebin
  https://gist.github.com/f76284151c225ae43af82de8439efe02

  
  They work fine w/ the 18.1 Installer/Live Boot.. They worked fine after the 
install.. when I did the latest update they broke. 

  uname -a ->  Linux thinkpad 4.8.0-41-generic #44~16.04.1-Ubuntu SMP
  Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -rd
  Description:  Linux Mint 18.1 Serena
  Release:  18.1

  kern.log paste:

  
  Mar  9 12:11:17 thinkpad kernel: [  244.854264] usb 1-2: USB disconnect, 
device number 4
  Mar  9 12:11:17 thinkpad kernel: [  244.864634] wlx2c4d5406c9c1: 
deauthenticating from 58:6d:8f:8e:02:5d by local choice (Reason: 
3=DEAUTH_LEAVING)
  Mar  9 12:11:17 thinkpad kernel: [  244.864846] rtl_usb: reg 0x102, 
usbctrl_vendorreq TimeOut! status:0xffed value=0xf00069ce
  Mar  9 12:11:17 thinkpad kernel: [  244.864858] rtl_usb: reg 0x422, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424
  Mar  9 12:11:17 thinkpad kernel: [  244.864866] rtl_usb: reg 0x542, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424
  Mar  9 12:11:17 thinkpad kernel: [  244.864879] rtl_usb: reg 0x1cc, 
usbctrl_vendorreq TimeOut! status:0xffed value=0x1950812
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3310] 
sup-iface[0xa2d380,wlx2c4d5406c9c1]: connection disconnected (reason -3)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3318] 
device (wlx2c4d5406c9c1): state change: activated -> unmanaged (reason 
'removed') [100 10 36]
  Mar  9 12:11:17 thinkpad kernel: [  244.899266] cfg80211: World regulatory 
domain updated:
  Mar  9 12:11:17 thinkpad kernel: [  244.899273] cfg80211:  DFS Master region: 
unset
  Mar  9 12:11:17 thinkpad kernel: [  244.899275] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Mar  9 12:11:17 thinkpad kernel: [  244.899280] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899283] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899286] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899290] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899295] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Mar  9 12:11:17 thinkpad kernel: [  244.899298] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Mar  9 12:11:17 thinkpad kernel: [  244.899301] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Mar  9 12:11:17 thinkpad kernel: [  244.899304] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3642] dhcp4 
(wlx2c4d5406c9c1): canceled DHCP transaction, DHCP client pid 2225
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3643] dhcp4 
(wlx2c4d5406c9c1): state changed bound -> done
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3703] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3705] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3708] 
dns-mgr: Writing DNS information to /sbin/resolvconf
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  [1489083077.3879] 
platform-linux: do-change-link[2]: failure changing link: failure 19 (No such 
device)
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3879] 
device (wlx2c4d5406c9c1): failed to disable userspace IPv6LL address handling
  Mar  9 12:11:17 thinkpad NetworkManager[989]:   [1489083077.3880] radio 
killswitch 
/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/ieee80211/phy0/rfkill0 
disappeared
  Mar  9 12:11:17 thinkpad NetworkManager[989]:  

[Touch-packages] [Bug 459730] Re: rsyslog doesn't create /dev/xconsole

2017-04-19 Thread Paul Belanger
This is not fixed in Xenial, rsyslog.postinst will still install
50-default.conf, which is packaged to also include /dev/xconsole still.

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

Title:
  rsyslog doesn't create /dev/xconsole

Status in One Hundred Papercuts:
  Fix Released
Status in rsyslog package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  Looks like this was missed in the move to upstart.

  This function was called in init.d/rsyslog start:

  create_xconsole() {
  if [ ! -e /dev/xconsole ]
  then
  mknod -m 640 /dev/xconsole p
  chown root:adm /dev/xconsole
  [ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
  fi
  }

  I can't find any reference to it now. If this is old school then it should be 
re
  moved from the config.

  rsyslog:
Installed: 4.2.0-2ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+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 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-19 Thread Dave Kuhlman
This comment pertains to the bug report/comment by my above, and *not*
to the bug originally reported by Brian Kelly, I believe.

I upgraded 4 machine.  Two of those machines had Python 3 installed
under /usr/local (from source).  The other two did not have Python 3
installed under /usr/local.  The two machines with Python 3 at
/usr/local failed during the upgrade; the two that did not have Python 3
under /usr/local did not fail.

So, I removed Python 3 from /usr/local/bin and /usr/local/lib.  Now, I
can run `sudo aptitude full-upgrade` without failures.

Is it possible that this means that there is some Python script that is
run during the install/upgrade than has "#!/usr/bin/env python3" at the
top and that is being run as:

$ ./somescript.py

instead of as:

$ python3 ./somescript.py

Although, since "local" does not seem to show up in the traceback, I'm
not sure ...

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

Title:
  package python3 3.5.1-4 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682934/+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 1683884] Re: openresolv is less crippled than debian-resolvconf for security-focused configurations

2017-04-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: resolvconf (Ubuntu)
   Status: New => Confirmed

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

Title:
  openresolv is less crippled than debian-resolvconf for security-
  focused configurations

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu relies on Debian's own "resolvconf" which is vastly inferior to
  Openresolv and makes it impossible to securely set up DNS servers for
  ephemeral secure tunnel interfaces.

  Specifically, Debian's "resolvconf" relies on a hard coded list of
  interface templates. For virtual interfaces or renamed interfaces --
  such as those used for creating secure tunnels -- the DNS entries will
  be lowest priority. This means it's not possible to override the
  current DNS with a DNS bound to particular arbitrarily-named
  interface. In other words, Debian's "resolvconf" explicitly ties
  interface naming templates to interface metrics. Openresolv has the
  `-m` option for this. Using `-m 0` will give an interface's DNS
  servers top priority.

  Secondly, and importantly, Debian's "resolvconf" does not support the
  `-x` option, which specifies that a DNS servers of an interface should
  be the _exclusive_ servers in use. This option is necessary to prevent
  leaking DNS queries over another interface. Even with the
  aforementioned `-m 0` option, an attacker could DoS the top priority
  DNS server in order to leak queries to the second priority DNS server.
  Openresolv's `-x` option fixes this, by allowing marking an interface
  as having "exclusive" control over DNS.

  Therefore, I'd suggest that either:
  a) Ubuntu switch to using Openresolv by default instead of its own 
"resolvconf". The openresolv package already "Provides: resolvconf",so it 
should be a drop-in replacement; or
  b) Debian's "resolvconf" backport these useful and necessary features from 
Openresolv.

  For my specific usage, the recommendation in
  https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1680811
  might work as a fix for the `-m 0` issue, but it is less than ideal
  and does accomplish `-x`. Therefore, I recommend doing either (a) or
  (b), preferably (a).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1683884/+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 1611078] Re: Support snaps inside of lxd containers

2017-04-19 Thread Stéphane Graber
No, the solution is that snapd shouldn't assume that /lib/modules exist
and just not attempt to bind-mount it if it's missing.

Systems that don't have kernels installed (like containers) shouldn't
have /lib/modules at all.

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1611078/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Description changed:

  [Impact]
  
  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.
  
  Impact reported by users :
  
  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."
  
  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.
  
  There is no realtime configuration to disable the feature or workaround
  this. The only possible way is at compile time.
  
  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.
  
  Xenial has separated dhclient in two packages :
  
  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)
  
  The goal here is to reproduce the same situation in Trusty, for this bug
  to be less painful for at least users that doesn't require DDNS
  functionnality.
  
  [Test Case]
  
  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common
  
  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```
  
  [Regression Potential]
  
  I did the split such that Trusty users will automatically get "isc-dhcp-
  client-ddns" installed but users bothered by this bug will have the
  option to switch to "isc-dhcp-client-noddns".
  
  Existing Trusty users can continue to use this DDNS functionality after
  the SRU without any necessary intervention.
  
  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  
  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  
  Xenial also has both distinct dhclient binary package but in the
  opposite way. We have decided to use the opposite way approach for not
  impacting actual Trusty users by changing the nature of isc-dhcp-client
  itself.
  
  Caribou and I, slashd, have also tested a couple of release upgrades from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns"
  
  and both scenarios worked as expected for caribou and I. (See comment
  #42)
  
  Results :
  ===
  ** Upgrade tested with isc-dhcp-client **
  
  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages
  
  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient
  
  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages
  
  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient
  
  ** Upgrade tested with isc-dhcp-noddns (4.2.4-7ubuntu12.9) **
  
  # dpkg -l
  ii  isc-dhcp-client-noddns   4.2.4-7ubuntu12.9
  amd64Dynamic DNS (DDNS) disabled DHCP client
  
  # netstat -anputa | grep dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  682/dhclient
  
  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  
  # dpkg -l | grep -i dhcp
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  rc  isc-dhcp-client-noddns   

[Touch-packages] [Bug 1684097] Re: Date format isn't good

2017-04-19 Thread Gunnar Hjalmarsson
** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Ubuntu French Translators (ubuntu-l10n-fr)

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

Title:
  Date format isn't good

Status in Ubuntu Translations:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Date format isn't good in date indicator whereas the translation
  format is good https://translations.launchpad.net/ubuntu/zesty/+source
  /indicator-datetime/+pots/indicator-datetime/fr/1/+translate

  In french, it should be displayed "mer. 19 avril" ; not "mer. avril
  19"

  I think it miss this translation witch was present on xenial:
  https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
  datetime/+pots/indicator-datetime/fr/5/+translate

  See the attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1684097/+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 1106158] Re: Applications using D-Bus crash on Wayland

2017-04-19 Thread Fred
Yes, gedit now works on Weston. I no longer have this problem.

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

Title:
  Applications using D-Bus crash on Wayland

Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  ** (gedit:783): WARNING **: Could not connect to session bus

  Applications using D-Bus crash on Wayland.
  They work if ran through the 'dbus-launch' command tho.
  Such as 'dbus-launch gedit'.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: dbus 1.6.8-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Sat Jan 26 17:13:20 2013
  InstallationDate: Installed on 2011-10-21 (463 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: dbus
  UpgradeStatus: Upgraded to raring on 2013-01-20 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1106158/+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 1632772] Re: GNOME on Wayland does not start from LightDM

2017-04-19 Thread Fred
I no longer experience this issue.
I can login to my Wayland session now.

However, I do have a related issue where I cannot login to Wayland as
guest.

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  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
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1684097] Re: Date format isn't good

2017-04-19 Thread Hans Joachim Desserud
** Also affects: ubuntu-translations
   Importance: Undecided
   Status: New

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

Title:
  Date format isn't good

Status in Ubuntu Translations:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Date format isn't good in date indicator whereas the translation
  format is good https://translations.launchpad.net/ubuntu/zesty/+source
  /indicator-datetime/+pots/indicator-datetime/fr/1/+translate

  In french, it should be displayed "mer. 19 avril" ; not "mer. avril
  19"

  I think it miss this translation witch was present on xenial:
  https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
  datetime/+pots/indicator-datetime/fr/5/+translate

  See the attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1684097/+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 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

2017-04-19 Thread Joshua Powers
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Thank you also for reporting this to Debian and finding the
upstream record.

If you need a fix for the bug in previous versions of Ubuntu, then the
relevant procedure is documented here:

https://wiki.ubuntu.com/StableReleaseUpdates

However, uploading point releases is generally not done to existing
releases in an effort to prevent additional regressions. Because
we currently do not have a delta with Debian, ideally we would sync over
from Debian directly and get the fix. However, with the existing freeze
this may not happen right away. I have added this to the server-next
backlog to get looked at during the next release.

Also I believe this is the commit to fix:
https://github.com/krb5/krb5/commit/bc7594058011c2f9711f24af4fa15a421a8d5b62

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Description changed:

  [Impact]
  
  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.
  
  Impact reported by users :
  
  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."
  
  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.
  
  There is no realtime configuration to disable the feature or workaround
  this. The only possible way is at compile time.
  
  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.
  
  Xenial has separated dhclient in two packages :
  
  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)
  
  The goal here is to reproduce the same situation in Trusty, for this bug
  to be less painful for at least users that doesn't require DDNS
  functionnality.
  
  [Test Case]
  
  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common
  
  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```
  
  [Regression Potential]
  
  I did the split such that Trusty users will automatically get "isc-dhcp-
  client-ddns" installed but users bothered by this bug will have the
  option to switch to "isc-dhcp-client-noddns".
  
  Existing Trusty users can continue to use this DDNS functionality after
  the SRU without any necessary intervention.
  
- With  isc-dhcp-client-ddns :
+ With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  
- Without isc-dhcp-client-ddns :
+ With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  
  Note that this is how Xenial does it.
  
  Caribou and I, slashd, have also tested a couple of release upgrade from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2-  Trusty upgrade to Xenial with "isc-dhcp-client-noddns"
  
  and both scenarios worked as expected for caribou and I. (See comment
  #42)
  
+ Results :
  ===
  ** Upgrade tested with isc-dhcp-client **
  
  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages
  
  # netstat -anputa | grep -i dhclient
- udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
- udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
+ udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
+ udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient
  
  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages
  
  # netstat -anputa | grep -i dhclient
- udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient 
- 
+ udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient
  
  ** Upgrade tested with isc-dhcp-noddns (4.2.4-7ubuntu12.9) **
  
  # dpkg -l
  ii  isc-dhcp-client-noddns   4.2.4-7ubuntu12.9
  amd64Dynamic DNS (DDNS) disabled DHCP client
  
  # netstat -anputa | grep dhclient
- udp0  0 0.0.0.0:68  0.0.0.0:* 
  682/dhclient 
+ udp0  0 0.0.0.0:68  0.0.0.0:* 
  682/dhclient
  
  After 

[Touch-packages] [Bug 1684213] Status changed to Confirmed

2017-04-19 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1684213/+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 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS

2017-04-19 Thread Joshua Powers
** Changed in: krb5 (Ubuntu)
   Status: New => Triaged

** Changed in: krb5 (Ubuntu)
   Importance: Undecided => High

** Tags added: server-next

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

Title:
  krb5-user: kinit fails for OTP user when using kdc discovery via DNS

Status in krb5 package in Ubuntu:
  Triaged
Status in krb5 package in Debian:
  New

Bug description:
  Zesty is now affected, please see the debian bug 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
  and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554

  Would it be possible to get 1.15.1 (already released upstream) in
  zesty/zesty-updates?

  Thanks
  Jochen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+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 1684213] [NEW] Intel Wireless 7260 often crashes

2017-04-19 Thread Ben
Public bug reported:

Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything
(kernel, firmware, etc.) is stock. Issue has persisted across multiple
installations.

Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
[  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
[  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
[  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
[  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
[  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
[  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
[  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

Solution: Rebooting doesn't fix the problem. Perhaps a different
firmware version will work better? Configuration settings? etc.?
Unknown.

Thanks ahead of time for the help. Let me know if there's anything you
need/commands I should run/solutions I can attempt.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-19-generic 4.10.0-19.21
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bmueller   1669 F pulseaudio
CurrentDesktop: MATE
Date: Wed Apr 19 10:34:11 2017
InstallationDate: Installed on 2017-04-13 (6 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:07dc Intel Corp.
 Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GOOGLE Gnawty
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-19-generic N/A
 linux-backports-modules-4.10.0-19-generic  N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
dmi.bios.date: 08/16/2015
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Gnawty
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug zesty

** Attachment added: "Dmesg output when issue is occuring."
   
https://bugs.launchpad.net/bugs/1684213/+attachment/4864922/+files/dmesg-errors.txt

** Also affects: linux-firmware (Ubuntu)
   Importance: Undecided
   Status: New

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

** Description changed:

  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
  
  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything
  (kernel, firmware, etc.) is stock. Issue has persisted across multiple
  installations.
  
- Bug: Wifi/Bluetooth crashes crashes and refuses to come back up, even
- after multiple reboots. Issue persists across distros (Arch, Ubuntu,
- etc.)
+ Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
+ multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)
  
  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was 

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Patch removed: "lp1176046_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864920/+files/lp1176046_xenial.debdiff

** Patch added: "lp1176046_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864921/+files/lp1176046_xenial.debdiff

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Xenial also has both distinct dhclient binary package but in the
  opposite way. We have decided to use the opposite way approach for not
  impacting actual Trusty users by changing the nature of isc-dhcp-
  client itself.

  Caribou and I, slashd, have also tested a couple of release upgrades from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  Results :
  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages

  # netstat -anputa | grep 

[Touch-packages] [Bug 1665264] Re: isc-dhcp-server 4.3.3-5ubuntu12.6 BOOTREPLY to wrong MAC address

2017-04-19 Thread Sjors Gielen
Can confirm this with DHCP instead of BOOTP as well:

Apr 19 17:51:48 curacao dhcpd[18031]: reuse_lease: lease age 671 (secs) under 
25% threshold, reply with unaltered, existing lease
Apr 19 17:51:48 curacao dhcpd[18031]: DHCPDISCOVER from 08:00:27:44:28:00 via 
eth0
Apr 19 17:51:49 curacao dhcpd[18031]: DHCPOFFER on 192.168.0.60 to 
08:00:27:04:2f:0f via eth0

Has this been reported upstream?

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

Title:
  isc-dhcp-server 4.3.3-5ubuntu12.6 BOOTREPLY to wrong MAC address

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I am testing network boot on several embedded targets using BOOTP from
  the isc-dhcp-server package using Ubuntu 16.04.2.

  The /etc/dhcp/dhcpd.conf I modified looks like this:

  subnet 192.168.3.0 netmask 255.255.255.0
  {
    # The filenames must correspond to the barebox and MLO files which are 
placed in the /tftpboot directory
    range dynamic-bootp 192.168.3.11 192.168.3.100;
    if substring (option vendor-class-identifier, 0, 10) = "AM335x ROM"
    {
  filename "MLO";
    }
    elsif substring (option vendor-class-identifier, 0, 18) = "am335x 
barebox-mlo"
    {
  filename "barebox.bin";
    }
    range 192.168.3.101 192.168.3.199;
  }

  Booting the first target does work out of the box with no issues:

  Feb 16 09:11:38 lws- dhcpd[4259]: BOOTREPLY on 192.168.3.13 to 
68:c9:0b:4a:3c:fe via enp5s2
  Feb 16 09:11:46 lws- dhcpd[4259]: reuse_lease: lease age 63582 (secs) 
under 25% th
  Feb 16 09:11:46 lws- dhcpd[4259]: BOOTREQUEST from 68:c9:0b:1c:74:8c via 
enp5s2

  And then the booting works..

  Trying to boot the second target (different board with different MAC)
  does not work any more:

  Feb 16 09:16:12 lws- dhcpd[4259]: BOOTREQUEST from 68:c9:0b:1c:74:8c via 
enp5s2
  Feb 16 09:16:12 lws- dhcpd[4259]: BOOTREPLY on 192.168.3.13 to 
68:c9:0b:4a:3c:fe via enp5s2

  The dhcp receives the request but replies to the MAC of the first
  target. I see the same when trying the third, forth target and so on.
  The dhcp always replies to the MAC of the first target.

  This did work with the same configuration setup on Ubuntu 14.04.5 with
  4.2.4-7ubuntu12.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1665264/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Patch added: "lp1176046_trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864919/+files/lp1176046_trusty.debdiff

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  Caribou and I, slashd, have also tested a couple of release upgrade from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2-  Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient 

  
  ** Upgrade tested with isc-dhcp-noddns (4.2.4-7ubuntu12.9) **

  # dpkg -l
  ii  isc-dhcp-client-noddns   4.2.4-7ubuntu12.9
  amd64Dynamic DNS (DDNS) disabled DHCP client

  # netstat -anputa | 

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Patch added: "lp1176046_xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864920/+files/lp1176046_xenial.debdiff

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  Caribou and I, slashd, have also tested a couple of release upgrade from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2-  Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient 

  
  ** Upgrade tested with isc-dhcp-noddns (4.2.4-7ubuntu12.9) **

  # dpkg -l
  ii  isc-dhcp-client-noddns   4.2.4-7ubuntu12.9
  amd64Dynamic DNS (DDNS) disabled DHCP client

  # netstat -anputa | 

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
@rbasak,

* Un-version the "Replaces:" as discussed : DONE
- Upgrade Trusty->Xenial with isc-client-dhcp pkg successfully completed with 
expected result
- Upgrade Trusty->Xenial with isc-client-dhcp-noddns pkg successfully completed 
with expected result

* Fix typo here and there : DONE

* Add (LP: #1176046) in X changelog : DONE

* Update SRU information : DONE

Eric

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  Caribou and I, slashd, have also tested a couple of release upgrade from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2-  Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient 

  
  ** Upgrade tested with 

Re: [Touch-packages] [Bug 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-19 Thread Brian Murray
On Wed, Apr 19, 2017 at 03:09:41PM -, Brian Kelly wrote:
> On 18/04/2017 21:48, Brian Murray wrote:
> > How did you go about upgrading from 16.10 to 17.04? If you used ubuntu-
> > release-upgrader please include the logs in /var/log/dist-upgrade/ so I
> > can better sort out how things went awry.
> > 
> 
> The upgrade was from the GUI following a regular update. I followed the 
> 'new version is available' route and accepted the defaults at each stage 
> of warnings about removing old packages.
> 
> There are 5.8Mb of files under /var/log/dist-upgrade on my machine, do 
> you need them all?  I ask because 'broadband' here means 0.1Mb/s so it's 
> a long upload for me!

The sub-directories should be about previous release upgrades, so those
won't be necessary. You could confirm you are uploading the right log
files by looking at the 'main.log' file and checking the date in it in
addition to looking for the right releases in lines with PreCacheOpen
and PostInitialUpdate.

The file 'apt-clone_system_state.tar.gz' may not necessary so you can
skip that in your initial upload.

--
Brian Murray

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

Title:
  package python3 3.5.1-4 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682934/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Description changed:

  [Impact]
  
  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.
  
  Impact reported by users :
  
  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."
  
  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.
  
  There is no realtime configuration to disable the feature or workaround
  this. The only possible way is at compile time.
  
  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.
  
  Xenial has separated dhclient in two packages :
  
  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)
  
  The goal here is to reproduce the same situation in Trusty, for this bug
  to be less painful for at least users that doesn't require DDNS
  functionnality.
  
  [Test Case]
  
  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common
  
  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```
  
  [Regression Potential]
  
  I did the split such that Trusty users will automatically get "isc-dhcp-
  client-ddns" installed but users bothered by this bug will have the
  option to switch to "isc-dhcp-client-noddns".
  
  Existing Trusty users can continue to use this DDNS functionality after
  the SRU without any necessary intervention.
  
  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  
  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  
  Note that this is how Xenial does it.
  
  Caribou and I, slashd, have also tested a couple of release upgrade from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2-  Trusty upgrade to Xenial with "isc-dhcp-client-noddns"
  
  and both scenarios worked as expected for caribou and I. (See comment
  #42)
  
+ ===
+ ** Upgrade tested with isc-dhcp-client **
+ 
+ # dpkg -l
+ ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
+ ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages
+ 
+ # netstat -anputa | grep -i dhclient
+ udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
+ udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
+ udp6   0  0 :::52249:::*  
  632/dhclient
+ 
+ After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
+ ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
+ ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages
+ 
+ # netstat -anputa | grep -i dhclient
+ udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient 
+ 
+ 
+ ** Upgrade tested with isc-dhcp-noddns (4.2.4-7ubuntu12.9) **
+ 
+ # dpkg -l
+ ii  isc-dhcp-client-noddns   4.2.4-7ubuntu12.9
  amd64Dynamic DNS (DDNS) disabled DHCP client
+ 
+ # netstat -anputa | grep dhclient
+ udp0  0 0.0.0.0:68  0.0.0.0:* 
  682/dhclient 
+ 
+ After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
+ 
+ # dpkg -l | grep -i dhcp
+ ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
+ rc  isc-dhcp-client-noddns   4.2.4-7ubuntu12.9
  amd64Dynamic DNS (DDNS) disabled DHCP client
+ ii  isc-dhcp-common  4.3.3-5ubuntu12.6

[Touch-packages] [Bug 1682386] Re: systemd-resolved can not resolve .coop domain names

2017-04-19 Thread Jeffrey Blanchard
I just updated to Zesty 17.04 and I am having trouble accessing .coop
sites using Chromium and Firefox.

This site can’t be reached
www.gaiahost.coop’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN

I also use a .coop domain for my email server and can't access that
either.

Everything still works fine on my other computer running 16.10

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

Title:
  systemd-resolved can not resolve .coop domain names

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2.

  I found that .coop domain nomes are not being resolved. If I switch to
  another DNS server (instead of 127.0.0.53, which is the current
  default in 17.04), then .coop domains are resolved:

  $ nslookup
  > www.somenergia.coop
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find www.somenergia.coop: SERVFAIL
  > server 8.8.8.8
  Default server: 8.8.8.8
  Address: 8.8.8.8#53
  > www.somenergia.coop
  Server:   8.8.8.8
  Address:  8.8.8.8#53

  Non-authoritative answer:
  Name: www.somenergia.coop
  Address: 164.132.200.9
  >

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682386/+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 1684200] [NEW] Ubuntu phone update problem - Version 36

2017-04-19 Thread vagrale
Public bug reported:

I have a problem with my Ubuntu phone. I can't update. There is
available Ubuntu Version 36, but when i choose restart and install
nothing happens.

Device: BQ Aquaris E4.5
Last updated: 7/12/16
Version: Ubuntu 15.04-armhf (20161118-171123)

** Affects: system-image (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu phone update problem - Version 36

Status in system-image package in Ubuntu:
  New

Bug description:
  I have a problem with my Ubuntu phone. I can't update. There is
  available Ubuntu Version 36, but when i choose restart and install
  nothing happens.

  Device: BQ Aquaris E4.5
  Last updated: 7/12/16
  Version: Ubuntu 15.04-armhf (20161118-171123)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1684200/+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


Re: [Touch-packages] [Bug 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-19 Thread Brian Kelly
On 18/04/2017 21:48, Brian Murray wrote:
> How did you go about upgrading from 16.10 to 17.04? If you used ubuntu-
> release-upgrader please include the logs in /var/log/dist-upgrade/ so I
> can better sort out how things went awry.
> 

The upgrade was from the GUI following a regular update. I followed the 
'new version is available' route and accepted the defaults at each stage 
of warnings about removing old packages.

There are 5.8Mb of files under /var/log/dist-upgrade on my machine, do 
you need them all?  I ask because 'broadband' here means 0.1Mb/s so it's 
a long upload for me!

Brian.

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

Title:
  package python3 3.5.1-4 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682934/+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 1679727] Re: Don't attempt to create devices in lx-brand containers

2017-04-19 Thread RussianNeuroMancer
Same issue in machined containers.

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

Title:
  Don't attempt to create devices in lx-brand containers

Status in makedev package in Ubuntu:
  Confirmed

Bug description:
  This is a similar issue to
  https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163

  In a Joyent lx-brand container environment an upgrade of the makedev
  package fails at the post-installation script:

  # apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up makedev (2.3.1-93ubuntu2~ubuntu14.04.1) ...
  mknod: ‘mem-’: Operation not permitted
  makedev mem c 1 1 root kmem 0640: failed
  mknod: ‘kmem-’: Operation not permitted
  makedev kmem c 1 2 root kmem 0640: failed
  mknod: ‘null-’: Operation not permitted
  makedev null c 1 3 root root 0666: failed
  mknod: ‘port-’: Operation not permitted
  makedev port c 1 4 root kmem 0640: failed
  mknod: ‘zero-’: Operation not permitted
  makedev zero c 1 5 root root 0666: failed
  mknod: ‘full-’: Operation not permitted
  makedev full c 1 7 root root 0666: failed
  mknod: ‘random-’: Operation not permitted
  makedev random c 1 8 root root 0666: failed
  mknod: ‘urandom-’: Operation not permitted
  makedev urandom c 1 9 root root 0666: failed
  mknod: ‘tty-’: Operation not permitted
  makedev tty c 5 0 root tty 0666: failed
  mknod: ‘ram0-’: Operation not permitted
  makedev ram0 b 1 0 root disk 0660: failed
  mknod: ‘ram1-’: Operation not permitted
  makedev ram1 b 1 1 root disk 0660: failed
  mknod: ‘ram2-’: Operation not permitted
  makedev ram2 b 1 2 root disk 0660: failed
  mknod: ‘ram3-’: Operation not permitted
  makedev ram3 b 1 3 root disk 0660: failed
  mknod: ‘ram4-’: Operation not permitted
  makedev ram4 b 1 4 root disk 0660: failed
  mknod: ‘ram5-’: Operation not permitted
  makedev ram5 b 1 5 root disk 0660: failed
  mknod: ‘ram6-’: Operation not permitted
  makedev ram6 b 1 6 root disk 0660: failed
  mknod: ‘ram7-’: Operation not permitted
  makedev ram7 b 1 7 root disk 0660: failed
  mknod: ‘ram8-’: Operation not permitted
  makedev ram8 b 1 8 root disk 0660: failed
  mknod: ‘ram9-’: Operation not permitted
  makedev ram9 b 1 9 root disk 0660: failed
  mknod: ‘ram10-’: Operation not permitted
  makedev ram10 b 1 10 root disk 0660: failed
  mknod: ‘ram11-’: Operation not permitted
  makedev ram11 b 1 11 root disk 0660: failed
  mknod: ‘ram12-’: Operation not permitted
  makedev ram12 b 1 12 root disk 0660: failed
  mknod: ‘ram13-’: Operation not permitted
  makedev ram13 b 1 13 root disk 0660: failed
  mknod: ‘ram14-’: Operation not permitted
  makedev ram14 b 1 14 root disk 0660: failed
  mknod: ‘ram15-’: Operation not permitted
  makedev ram15 b 1 15 root disk 0660: failed
  mknod: ‘ram16-’: Operation not permitted
  makedev ram16 b 1 16 root disk 0660: failed
  mknod: ‘loop0-’: Operation not permitted
  makedev loop0 b 7 0 root disk 0660: failed
  mknod: ‘loop1-’: Operation not permitted
  makedev loop1 b 7 1 root disk 0660: failed
  mknod: ‘loop2-’: Operation not permitted
  makedev loop2 b 7 2 root disk 0660: failed
  mknod: ‘loop3-’: Operation not permitted
  makedev loop3 b 7 3 root disk 0660: failed
  mknod: ‘loop4-’: Operation not permitted
  makedev loop4 b 7 4 root disk 0660: failed
  mknod: ‘loop5-’: Operation not permitted
  makedev loop5 b 7 5 root disk 0660: failed
  mknod: ‘loop6-’: Operation not permitted
  makedev loop6 b 7 6 root disk 0660: failed
  mknod: ‘loop7-’: Operation not permitted
  makedev loop7 b 7 7 root disk 0660: failed
  mknod: ‘tty0-’: Operation not permitted
  makedev tty0 c 4 0 root tty 0600: failed
  mknod: ‘console-’: Operation not permitted
  makedev console c 5 1 root tty 0600: failed
  ln: failed to create symbolic link ‘fd/fd’: Function not implemented
  ln: failed to create symbolic link ‘stdin’: File exists
  ln: failed to create symbolic link ‘stdout’: File exists
  ln: failed to create symbolic link ‘stderr’: File exists
  /sbin/MAKEDEV: don't know how to make device "tty0"
  dpkg: error processing package makedev (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   makedev
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  The workaround is similar to 1675163 except in this case the post-
  installation script should check for "container=zone" in
  '/proc/1/environ':

  
  if grep -q container=zone /proc/1/environ
  then
  echo "lx-brand container detected."
  exit 0
  fi

To manage notifications about this bug go to:

[Touch-packages] [Bug 1612224] Comment bridged from LTC Bugzilla

2017-04-19 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2017-04-19 10:37 EDT---
IBM Bugzilla Status -> Closed ; available with GA version

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

Title:
  [17.04 FEAT] Extend cpu topology to support drawers

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  kernel 4.8: Add support for the additional scheduling layer within the
  kernel and util-linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1612224/+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 1664595] Comment bridged from LTC Bugzilla

2017-04-19 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2017-04-19 10:32 EDT---
IBM Distro Status -> Closed ; available with GA version

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

Title:
  [17.04 FEAT] Upgrade to newest version of zlib >=1.2.11

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in zlib package in Ubuntu:
  Fix Released

Bug description:
  Upgrade to newest version available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1664595/+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 1670745] Re: ssh-keyscan : bad host signature when using port option

2017-04-19 Thread Joshua Powers
@ghusson,
This will be available soon in Xenial and Yakkety. As of today it is still in 
-proposed.

@sru-team,
Based on ghusson's comment and my own testing of Xenial (7.2p2-4ubuntu2.2) and 
Yakkety (7.3p1-1ubuntu0.1) I am marking this as verification-done. I followed 
the test case I originally developed and is documented in the SRU template and 
confirmed that the port is no longer in the ssh-keyscan output.

** Tags added: verification-done-xenial verification-done-yakkety

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * using ssh-keyscan while using the port (-p) option of it will create 
 bad entries. They will contain the port and thereby be invalid for 
 latter use under the purpose of known_hosts.

   * Fix by backporting upstream fix.

  [Test Case]

   * Further evolving from the simplification Josh provided:
  Testcase:
  $ release=xenial
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
  $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port 
/' /etc/ssh/sshd_config
  $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
  $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
  $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p  
${IP}

  # See the port in the Hash still

  # Install the fixed version in *-client and see the port gone from the
  output

  [Regression Potential]

   * Change is limited to ssh-keyscan (not any touching other parts of openssh)
   * Fix is from upstream (no "Ubuntu special" change)
   * Fix is small and "only" changing string creation (11 lines touched)
   So overall the regression potential should be low.

  [Other Info]

   * n/a

  ---

  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password:

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot see the port number as it is well hashed !

  REMARKS :
  ==
  Same problem has already reported here (on macOS): 
https://github.com/ansible/ansible-modules-extras/issues/2651

  It seems that ssh-keyscan version and open-ssh version differs :
  dpkg -l | grep openssh :: ii  openssh-client  1:7.2p2-4ubuntu2.1  [...]
  ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat 

[Touch-packages] [Bug 1670745] Re: ssh-keyscan : bad host signature when using port option

2017-04-19 Thread Joshua Powers
** Changed in: openssh (Ubuntu)
 Assignee: Joshua Powers (powersj) => (unassigned)

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

Title:
  ssh-keyscan : bad host signature when using port option

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Yakkety:
  Fix Committed
Status in openssh package in Debian:
  Fix Released

Bug description:
  [Impact]

   * using ssh-keyscan while using the port (-p) option of it will create 
 bad entries. They will contain the port and thereby be invalid for 
 latter use under the purpose of known_hosts.

   * Fix by backporting upstream fix.

  [Test Case]

   * Further evolving from the simplification Josh provided:
  Testcase:
  $ release=xenial
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-client
  $ lxc launch ubuntu-daily:${release} ${release}-test-ssh-port-scan-server
  $ lxc exec ${release}-test-ssh-port-scan-server -- sed -i 's/Port 22/Port 
/' /etc/ssh/sshd_config
  $ lxc exec ${release}-test-ssh-port-scan-server -- service ssh restart
  $ IP=$(lxc exec ${release}-test-ssh-port-scan-server -- hostname --ip-address)
  $ lxc exec ${release}-test-ssh-port-scan-client -- ssh-keyscan -H -p  
${IP}

  # See the port in the Hash still

  # Install the fixed version in *-client and see the port gone from the
  output

  [Regression Potential]

   * Change is limited to ssh-keyscan (not any touching other parts of openssh)
   * Fix is from upstream (no "Ubuntu special" change)
   * Fix is small and "only" changing string creation (11 lines touched)
   So overall the regression potential should be low.

  [Other Info]

   * n/a

  ---

  When I use the port option with ssh-keygen, the result is not
  compatible with ssh known_host file format.

  UBUNTU VERSION :
  
  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  BAD :
  
  :~/.ssh$ cat /etc/issue
  Ubuntu 16.04.1 LTS \n \l
  :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...]
  debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400
  # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we see the port number because it is not hashed !

  GOOD :
  
  rm ~/.ssh/known_hosts
  :~/$ ssh -p [...port...] [...snip...]
  The authenticity of host '[[...snip...]]:[...port...] 
([[...snip...]]:[...port...])' can't be established.
  ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 
'[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list 
of known hosts.
  [...snip...]@[...snip...]'s password:

  :~/$ !cat
  cat ~/.ssh/known_hosts
  |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=
  |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= 
ecdsa-sha2-nistp256 
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8=

  ==> we cannot see the port number as it is well hashed !

  REMARKS :
  ==
  Same problem has already reported here (on macOS): 
https://github.com/ansible/ansible-modules-extras/issues/2651

  It seems that ssh-keyscan version and open-ssh version differs :
  dpkg -l | grep openssh :: ii  openssh-client  1:7.2p2-4ubuntu2.1  [...]
  ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat 
OpenSSH* compat 0x0400

  It is very annoying because I am trying to manage hand installed VMs
  with Ansible. For that I want to automate SSH host keys storing in
  known_hosts database. And because of this bug I can't. (ansible KIKIN
  project in development).

  Thank you,
  BR,
  Gautier HUSSON.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

2017-04-19 Thread Lev Popov
The behavior I've described seems transient, I can't reproduce it
anymore.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 996917] Re: canberra does not work with wayland

2017-04-19 Thread Jeremy Bicha
libcanberra works in Ubuntu GNOME 16.04 LTS using GNOME on Wayland. I
don't think there's really any support for GNOME on Wayland before that
version.

** Changed in: libcanberra (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  canberra does not work with wayland

Status in libcanberra package in Ubuntu:
  Fix Released

Bug description:
  I follow the directions at https://launchpad.net/~darxus/+archive/wayland-gtk 
to run the gtk apps with wayland backend (installed from darxus PPA 
https://launchpad.net/~darxus/+archive/wayland-gtk), all apps will crash in 
libcanberra-gtk3-module. It seems that libcanberra-gtk3-module has dependency 
on native X11. If I remove the package, apps didn't crash at this point any 
more. 
  ps: Due to the bug #996904 "Cannot connect to crash database on 12.04", I 
can't fire the bug by ubuntu-bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/996917/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Description changed:

  [Impact]
  
  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.
  
  Impact reported by users :
  
  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."
  
- There is a randomization mechanism in libdns that prevent dhclient to take 
the sysctl values into account (net.ipv4.ip_local_port_range & 
net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion 
isc-dhcp upstream doesn't want to rely on kernel for randomization.
-  
- There is no realtime configuration to disable the feature or workaround this. 
The only possible way is at compile time.
+ There is a randomization mechanism in libdns that prevent dhclient to
+ take the sysctl values into account (net.ipv4.ip_local_port_range &
+ net.ipv4.ip_local_reserved_ports) to workaround this, and after
+ discussion isc-dhcp upstream doesn't want to rely on kernel for
+ randomization.
+ 
+ There is no realtime configuration to disable the feature or workaround
+ this. The only possible way is at compile time.
  
  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.
  
  Xenial has separated dhclient in two packages :
  
  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)
  
  The goal here is to reproduce the same situation in Trusty, for this bug
  to be less painful for at least users that doesn't require DDNS
  functionnality.
  
  [Test Case]
  
  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common
  
  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```
  
+ [Regression Potential]
  
- [Regression Potential] 
+ I did the split such that Trusty users will automatically get "isc-dhcp-
+ client-ddns" installed but users bothered by this bug will have the
+ option to switch to "isc-dhcp-client-noddns".
  
- * none expected
- 
- I did the split such that users will automatically get isc-dhcp-client-ddns 
installed but users bothered by this bug then will have the option to switch to 
the one without it by uninstalling (isc-dhcp-client-ddns), 
- so existing Trusty users can continue to use this DDNS functionality after 
the SRU without any necessary intervention.
+ Existing Trusty users can continue to use this DDNS functionality after
+ the SRU without any necessary intervention.
  
  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  
  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  
  Note that this is how Xenial does it.
  
+ Caribou and I, slashd, have also tested a couple of release upgrade from 
Trusty to Xenial with both scenarios :
+ 1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
+ 2-  Trusty upgrade to Xenial with "isc-dhcp-client-noddns"
+ 
+ and both scenarios worked as expected for caribou and I. (See comment
+ #42)
+ 
  [Other Info]
-  
-  * See : 
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to 
look at my discussion with rbasak on if that approach would be acceptable for 
SRU.
+ 
+  * See : https://bugs.launchpad.net/ubuntu/+source/isc-
+ dhcp/+bug/1176046/comments/19 to look at my discussion with rbasak on if
+ that approach would be acceptable for SRU.
  
  [Original Description]
  
  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.
  
  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.
  
  Initial research of the code also suggested omapi, but adding omapi port
   to /etc/dhcp/dhclient.conf only opened a forth port with the two
  random udp ports still enabled.
  
  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.
  
  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605
  
  One impact of these random ports is that security hardening becomes more
  difficult.  The purpose 

[Touch-packages] [Bug 1634598] Re: gnome-online-accounts Problems on Wayland

2017-04-19 Thread Jeremy Bicha
Unfortunately, GNOME Online Accounts will not work if you log out and
then log back in. You have to completely reboot. Yes, that is a very bad
bug.

Could you test if you still have problems with GNOME Online Accounts
immediately after rebooting?

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-online-accounts Problems on Wayland

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  When using gnome-online-accounts + wayland.

  When tshooting [LP1610944](https://bugs.launchpad.net/bugs/1610944) I
  noticed that you can't add a google account that utilizes
  customizations from [Google's Identity
  Platform](https://developers.google.com/identity/). This is used by
  many Google Apps for Work systems (including mine). This however does
  work on gnome with X. I believe this is a wayland specific issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1634598/+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 1106158] Re: Applications using D-Bus crash on Wayland

2017-04-19 Thread Jeremy Bicha
gedit works in Ubuntu GNOME 16.04 LTS using GNOME on Wayland. I don't
think there's really any support for GNOME on Wayland before that
version.

** Changed in: dbus (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Applications using D-Bus crash on Wayland

Status in dbus package in Ubuntu:
  Fix Released

Bug description:
  ** (gedit:783): WARNING **: Could not connect to session bus

  Applications using D-Bus crash on Wayland.
  They work if ran through the 'dbus-launch' command tho.
  Such as 'dbus-launch gedit'.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: dbus 1.6.8-1ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Sat Jan 26 17:13:20 2013
  InstallationDate: Installed on 2011-10-21 (463 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: dbus
  UpgradeStatus: Upgraded to raring on 2013-01-20 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1106158/+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 1616742] Re: xdiagnose does nothing in Wayland

2017-04-19 Thread Jeremy Bicha
New installs of Ubuntu GNOME 17.04 do not have xdiagnose.

Since the Ubuntu Desktop team has a goal of switching to GNOME on
Wayland by default for 18.04 LTS, I propose we drop xdiagnose from the
default Ubuntu install too.

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

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

Title:
  xdiagnose does nothing in Wayland

Status in ubuntu-meta package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  New

Bug description:
  What happens
  ===
  1. Try Ubuntu GNOME 16.10 Beta on a computer using open source graphics 
drivers (Intel is recommended).
  2. On the login screen, select your user name. Before entering your password, 
click the gear button and choose "GNOME on Wayland". Enter your password and 
log in.
  3. Try to run xdiagnose.
  4. Nothing happens

  What I expected
  ===
  1. xdiagnose could be adapted to analyze and report issues with Wayland
  2. xdiagnose could explain why it doesn't work on Wayland
  3. Otherwise, it would be nice if xdiagnose wouldn't show up in the 
Activities Overview when Wayland is running but that's more complicated. (Maybe 
XDG_CURRENT_DESKTOP could be expanded to add Wayland as a string and 
xdiagnose.desktop could add NotShowIn=Wayland)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1616742/+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 1632772] Re: GNOME on Wayland does not start from LightDM

2017-04-19 Thread Jeremy Bicha
** Tags added: wayland

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  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
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Patch added: "verif-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+attachment/4864794/+files/verif-xenial.debdiff

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to take 
the sysctl values into account (net.ipv4.ip_local_port_range & 
net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion 
isc-dhcp upstream doesn't want to rely on kernel for randomization.
   
  There is no realtime configuration to disable the feature or workaround this. 
The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  
  [Regression Potential] 

  * none expected

  I did the split such that users will automatically get isc-dhcp-client-ddns 
installed but users bothered by this bug then will have the option to switch to 
the one without it by uninstalling (isc-dhcp-client-ddns), 
  so existing Trusty users can continue to use this DDNS functionality after 
the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  [Other Info]
   
   * See : 
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to 
look at my discussion with rbasak on if that approach would be acceptable for 
SRU.

  [Original Description]

  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions

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

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
** Patch added: "verif-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+attachment/4864795/+files/verif-trusty.debdiff

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to take 
the sysctl values into account (net.ipv4.ip_local_port_range & 
net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion 
isc-dhcp upstream doesn't want to rely on kernel for randomization.
   
  There is no realtime configuration to disable the feature or workaround this. 
The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  
  [Regression Potential] 

  * none expected

  I did the split such that users will automatically get isc-dhcp-client-ddns 
installed but users bothered by this bug then will have the option to switch to 
the one without it by uninstalling (isc-dhcp-client-ddns), 
  so existing Trusty users can continue to use this DDNS functionality after 
the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  [Other Info]
   
   * See : 
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to 
look at my discussion with rbasak on if that approach would be acceptable for 
SRU.

  [Original Description]

  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  Example netstat -lnp  output:

  udp0  0 0.0.0.0:21117   0.0.0.0:* 
  2659/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  2659/dhclient
  udp6   0  0 :::45664:::*  
  2659/dhclient

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions

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

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

2017-04-19 Thread Eric Desrochers
Hi Robie,

To answer your questions...

* Are you proposing your debdiff in commit 40 as ready for upload to Trusty?
No, here's the final one (that I sent you by email), but I will attach them to 
the LP bug now.

verif-trusty.debdiff
verif-xenial.debdiff

* Or is it still in progress? 
No, I did both debdiffs, and I tested it with differents scenarios (my note are 
above in the LP bug)
caribou also did some testing (upgrade Trusty->Xenial,...) and didn't see any 
particular problems.

Additionally, I have a users running the new binary package from a more
than a month, and everything goes well and as expected (without the
random extra port).

* And do you have a debdiff for the transitional package in Xenial please?
Yes, verif-xenial.debdiff

Eric

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to take 
the sysctl values into account (net.ipv4.ip_local_port_range & 
net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion 
isc-dhcp upstream doesn't want to rely on kernel for randomization.
   
  There is no realtime configuration to disable the feature or workaround this. 
The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  
  [Regression Potential] 

  * none expected

  I did the split such that users will automatically get isc-dhcp-client-ddns 
installed but users bothered by this bug then will have the option to switch to 
the one without it by uninstalling (isc-dhcp-client-ddns), 
  so existing Trusty users can continue to use this DDNS functionality after 
the SRU without any necessary intervention.

  With  isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  Without isc-dhcp-client-ddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Note that this is how Xenial does it.

  [Other Info]
   
   * See : 
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to 
look at my discussion with rbasak on if that approach would be acceptable for 
SRU.

  [Original Description]

  Ubuntu 13.04 Server 64-bit.  Fresh install.  Only one network adapter.

  dhclient process is listening on two randomly chosen udp ports in
  addition to the usual port 68.  This appears to be a bug in the
  discovery code for probing information on interfaces in the system.

  Initial research of the code also suggested omapi, but adding omapi
  port  to /etc/dhcp/dhclient.conf only opened a forth port with the
  two random udp ports still enabled.

  Version of included distro dhclient was 4.2.4.  I also tested with the
  latest isc-dhclient-4.2.5-P1 and got the same results.

  Debian has the same bug:
  http://forums.debian.net/viewtopic.php?f=10=95273=495605#p495605

  One impact of these random ports is that security hardening becomes
  more difficult.  The purpose of these random ports and security
  implications are unknown.

  Example netstat 

[Touch-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB

2017-04-19 Thread Lenin
** Changed in: amiwm (Ubuntu)
   Status: New => Invalid

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

Title:
  Port from legacy Xlib to modern XCB

Status in Compiz:
  Triaged
Status in 9wm package in Ubuntu:
  New
Status in aewm package in Ubuntu:
  New
Status in aewm++ package in Ubuntu:
  New
Status in afterstep package in Ubuntu:
  New
Status in amiwm package in Ubuntu:
  Invalid
Status in blackbox package in Ubuntu:
  New
Status in cairo package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Triaged
Status in ctwm package in Ubuntu:
  New
Status in dwm package in Ubuntu:
  Opinion
Status in enlightenment package in Ubuntu:
  New
Status in fvwm package in Ubuntu:
  New
Status in fvwm1 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in icewm package in Ubuntu:
  New
Status in jwm package in Ubuntu:
  Invalid
Status in larswm package in Ubuntu:
  New
Status in lwm package in Ubuntu:
  New
Status in matchbox-window-manager package in Ubuntu:
  New
Status in metacity package in Ubuntu:
  Invalid
Status in miwm package in Ubuntu:
  New
Status in muffin package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in pekwm package in Ubuntu:
  New
Status in ratpoison package in Ubuntu:
  New
Status in sapphire package in Ubuntu:
  New
Status in sawfish package in Ubuntu:
  New
Status in spectrwm package in Ubuntu:
  Fix Released
Status in tinywm package in Ubuntu:
  New
Status in tritium package in Ubuntu:
  New
Status in twm package in Ubuntu:
  New
Status in vtwm package in Ubuntu:
  New
Status in w9wm package in Ubuntu:
  New
Status in windowlab package in Ubuntu:
  New
Status in wm2 package in Ubuntu:
  New
Status in wmaker package in Ubuntu:
  Opinion
Status in xmonad package in Ubuntu:
  New

Bug description:
  Port/rewrite the window manager to use the modern XCB (X C Binding)
  library instead of the old legacy Xlib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1030022/+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 1518411] Re: "Maximum number of clients reached", new in Ubuntu 15.10

2017-04-19 Thread Billy Barnes
I have been having this problem for a while. I have seen a number of
commands suggested as helpful in various forums: `xwininfo -root
-children`, `xlsclients`, and `lsof -U`. I wrote a script that logged
the number of lines reported by these every 30 seconds.

It took about 5 days for my computer to crash (for most of which the
computer was idle because I was away for the long weekend). xlsclients
and lsof stayed steady at around 20 and 500 lines respectively. xwininfo
climbed steadily from 68 to 362. When the computer was idle and locked,
it would stay steady for hours at a time, then climb by about 10 windows
over 5 minutes, then steady out again. As described by Brett Johnson
above, most of the windows have no name.

I notice that it is always nautilus that crashes, usually while the
computer is unattended. I will return, nautilus will be closed and I
won't be able to open any new windows because the maximum number of
clients is reached. Nautlius exits with a segfault some address "not
located in known VMA region".

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

Title:
  "Maximum number of clients reached", new in Ubuntu 15.10

Status in Compiz:
  Confirmed
Status in compiz package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  In my newly upgraded (from 15.04) Ubuntu 15.10 system, after I've been
  logged in for a while I can no longer open new windows and instead get
  a "Maximum number of clients reached" error.

  This did not happen in 15.04.

  I ran "lsof" on the X server and did not see an excessive number of
  open file descriptors. I ran it again on a newly restarted X server
  and the number of open file descriptors looked about the same.

  I also ran "xlsclients" when the X server was reporting "Maximum
  number of clients reached" and the list of clients looked correct and
  reasonable (and there were less than 30 of them).

  I am happy to collect any additional logs or debugging information to
  help track this down. I don't know where to look further.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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: Fri Nov 20 13:00:09 2015
  DistUpgraded: 2015-11-17 11:59:09,835 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-33-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] 
(rev 08) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:7410]
  MachineType: System76, Inc. Galago UltraPro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=821f94aa-97e2-4384-8494-9f510a75877b ro i915.disable_power_well=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-11-17 (3 days ago)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Nov 20 12:51:23 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  

[Touch-packages] [Bug 1562002] Re: Nautilus: lag after choosing action in top right menu

2017-04-19 Thread Unishop
I can confirm that this bug is fixed in gtk+3.0 version
3.18.9-1ubuntu3.3 from xenial-proposed. From my testing it affected each
machine differently and thus was really hard to understand why freezing
happened.

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

Title:
  Nautilus: lag after choosing action in top right menu

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Committed

Bug description:
  # Impact
  This is known to affect Nautilus, but can potentially affect other 
applications too (the upstream bug has an example test app attached).

  See also the duplicate bug 1644393, which is another appearance of the
  same bug but with other symptoms.

  # Proposed Fix
  The proposed fix is an upstream commit taken from gtk-3-20 branch:
  https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1

  # Test Case
  https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case.

  # Regression Potential
  The bug is fixed in GTK+ 3.20.9, so the fix was already present in the 
version that shipped with Yakkety. I am not aware of any regressions.

  -
  choosing action like New Tab, New Folder, Select Items Matching, will make 
nautilus lag (unresponsive)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 25 20:52:21 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+685+36'"
  InstallationDate: Installed on 2016-03-24 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1562002/+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 1682913] Re: Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

2017-04-19 Thread Brice Terzaghi
So, what will be the solution for games that need it?

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

Title:
  Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed 
graphical issues in some games, that render partially black. E.g.:
  - menu of Payday 2: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
  - menu of Faeria: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

  I've traced the issue to a missing lib, libgles1, which for some
  reason has been removed from the 17.04 repos, as using Oibaf's PPA and
  manually installing the lib from it fixes the issues on these games.

  So, please build a version for Mesa 17.0.3 and put it in the repos,
  it's needed by some games.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1682913/+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 1684097] Re: Date format isn't good

2017-04-19 Thread Olivier Febwin
** Description changed:

  Date format isn't good in date indicator whereas the translation format
  is good https://translations.launchpad.net/ubuntu/zesty/+source
  /indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
  In french, it should be displayed "mer. 19 avril" ; not "mer. avril 19"
  
+ I think it miss this translation :
+ https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
+ datetime/+pots/indicator-datetime/fr/5/+translate
+ 
  See the attachment

** Description changed:

  Date format isn't good in date indicator whereas the translation format
  is good https://translations.launchpad.net/ubuntu/zesty/+source
  /indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
  In french, it should be displayed "mer. 19 avril" ; not "mer. avril 19"
  
- I think it miss this translation :
+ I think it miss this translation witch was present on xenial:
  https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
  datetime/+pots/indicator-datetime/fr/5/+translate
  
  See the attachment

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

Title:
  Date format isn't good

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Date format isn't good in date indicator whereas the translation
  format is good https://translations.launchpad.net/ubuntu/zesty/+source
  /indicator-datetime/+pots/indicator-datetime/fr/1/+translate

  In french, it should be displayed "mer. 19 avril" ; not "mer. avril
  19"

  I think it miss this translation witch was present on xenial:
  https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
  datetime/+pots/indicator-datetime/fr/5/+translate

  See the attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1684097/+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 1684097] [NEW] Date format isn't good

2017-04-19 Thread Olivier Febwin
Public bug reported:

Date format isn't good in date indicator whereas the translation format
is good https://translations.launchpad.net/ubuntu/zesty/+source
/indicator-datetime/+pots/indicator-datetime/fr/1/+translate

In french, it should be displayed "mer. 19 avril" ; not "mer. avril 19"

I think it miss this translation witch was present on xenial:
https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
datetime/+pots/indicator-datetime/fr/5/+translate

See the attachment

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

** Attachment added: "Capture du 2017-04-19 11-33-42.png"
   
https://bugs.launchpad.net/bugs/1684097/+attachment/4864732/+files/Capture%20du%202017-04-19%2011-33-42.png

** Description changed:

- See the attachment.
- The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
+ Date format isn't good in date indicator see the attachment but the
+ translation format is good
+ https://translations.launchpad.net/ubuntu/zesty/+source/indicator-
+ datetime/+pots/indicator-datetime/fr/1/+translate

** Description changed:

- Date format isn't good in date indicator see the attachment but the
+ Date format isn't good in date indicator see the attachment whereas the
  translation format is good
  https://translations.launchpad.net/ubuntu/zesty/+source/indicator-
  datetime/+pots/indicator-datetime/fr/1/+translate

** Description changed:

- Date format isn't good in date indicator see the attachment whereas the
+ Date format isn't good in date indicator (see attachment) whereas the
  translation format is good
  https://translations.launchpad.net/ubuntu/zesty/+source/indicator-
  datetime/+pots/indicator-datetime/fr/1/+translate

** Description changed:

- Date format isn't good in date indicator (see attachment) whereas the
- translation format is good
- https://translations.launchpad.net/ubuntu/zesty/+source/indicator-
- datetime/+pots/indicator-datetime/fr/1/+translate
+ See the attachment.
+ The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
+ 
+ It would be mer. 19 avril

** Description changed:

  See the attachment.
  The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
- It would be mer. 19 avril
+ It would be mer. 19 avril ; not mer. avril 19

** Description changed:

  See the attachment.
  The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
- It would be mer. 19 avril ; not mer. avril 19
+ In franch, it would be mer. 19 avril ; not mer. avril 19

** Description changed:

  See the attachment.
  The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
- In franch, it would be mer. 19 avril ; not mer. avril 19
+ In french, it would be mer. 19 avril ; not mer. avril 19

** Description changed:

  See the attachment.
  The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
- In french, it would be mer. 19 avril ; not mer. avril 19
+ In french, it sould be mer. 19 avril ; not mer. avril 19

** Description changed:

  See the attachment.
  The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
- In french, it sould be mer. 19 avril ; not mer. avril 19
+ In french, it should be mer. 19 avril ; not mer. avril 19

** Description changed:

  See the attachment.
  The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
  
- In french, it should be mer. 19 avril ; not mer. avril 19
+ In french, it should be displayed "mer. 19 avril" ; not "mer. avril 19"

** Description changed:

- See the attachment.
- The translation format is good 
https://translations.launchpad.net/ubuntu/zesty/+source/indicator-datetime/+pots/indicator-datetime/fr/1/+translate
+ The translation format is good
+ https://translations.launchpad.net/ubuntu/zesty/+source/indicator-
+ datetime/+pots/indicator-datetime/fr/1/+translate
  
  In french, it should be displayed "mer. 19 avril" ; not "mer. avril 19"
+ 
+ See the attachment

** Description changed:

- The translation format is good
+ Date format isn't good whereas the translation format is good
  https://translations.launchpad.net/ubuntu/zesty/+source/indicator-
  datetime/+pots/indicator-datetime/fr/1/+translate
  
  In french, it should be displayed "mer. 19 avril" ; not "mer. avril 19"
  
  See the attachment

** Description changed:

- Date format isn't good whereas 

[Touch-packages] [Bug 1334329] Re: Sound input settings not saved

2017-04-19 Thread Davias
...yep, here on Ubuntu 14.04.5 LTS, amd64, years ago I was able to solve
the bug...but now it is back again..

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

Title:
  Sound input settings not saved

Status in alsa-driver package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When attempting to set my preferred sound input device, simply leaving
  sound preferences and going back to sound preferences, and selecting
  input, causes the default SPDIF to be selected again, and not the
  internal microphone I preferred.  I made a video to demonstrate what I
  mean by this here:  http://youtu.be/9Q9EQvLl_rA

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I really don't know.  It's just the sound preferences.

  3) What you expected to happen
  For my selected sound input to be saved.

  4) What happened instead
  Keeps defaulting to the top sound input

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brandon   23953 F pulseaudio
   /dev/snd/controlC0:  brandon   23953 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:20:14 2014
  InstallationDate: Installed on 2014-04-26 (60 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-04-19 Thread aleandro
I add my apt-term.log file.

** Attachment added: "apt-term.log"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+attachment/4864663/+files/apt-term.log

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Confirmed

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 739495] Re: include in .ssh/config

2017-04-19 Thread bhat3
@cjwatson @paelzer Any chance we could backport that patch for xenial as
SRU? It's a long standing bug and helps superb with automation of Ubuntu
LTS for web plattforms. We like to use it for easy and user specific
conf.d style client config updates in deployment scenarios.

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

Title:
  include in .ssh/config

Status in portable OpenSSH:
  Confirmed
Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Could you implement sub-config including feature, please?
  It's very useful to split a user config file into many pieces if you have a 
many hosts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/739495/+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 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue

2017-04-19 Thread Alfonso de Cala
Fix released in Debian?

Reading the bug report (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=711341) they just closed it with a wontfix.

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

Title:
  CUPS cannot print to Kerberos-authenticated SMB print queue

Status in cups package in Ubuntu:
  Confirmed
Status in Debian:
  Fix Released

Bug description:
  Binary package hint: cups

  That was investigated on maverick (cups 1.4.4) and natty (cups 1.4.6).

  CUPS in Ubuntu cannot authenticate using Kerberos to an SMB print
  queue, such as one in an Active Directory.  This is because the smb
  backend is being invoked as user lp, and this user cannot access the
  Kerberos credential cache of the user who submitted the job.  When
  trying to print, the job is held for authentication, and a dialog
  prompting for username/password is being shown.  On Windows (and
  possibly other OS), the user would not be prompted if he has a ticket
  in the Kerberos realm (ie, "logged on to the domain") he is trying to
  print to.

  The CUPS smb backend on Ubuntu is the smbspool binary provided by
  Samba.  When run as a user, it will pick the Kerberos credential cache
  by itself and authenticate seamlessly.  Otherwise, it will read the
  KRB5CCNAME environment variable and try to use that when possible.

  There is two possible solutions to that:

  - Invoke the smb backend as root and pass it the KRB5CCNAME
  environment variable pointing to the user's Kerberos credential cache.
  CUPS execute the backend as user lp if it is world-executable, which
  is currently the case on Ubuntu.  User lp do not have the permission
  to read  the user's credential cache, hence why the smb backend would
  need to be executed as root (by removing the world-executable bit).
  Also, CUPS does not currently set KRB5CCNAME before invoking the smb
  backend (see http://www.cups.org/str.php?L3847).

  - Execute smbspool as the user submitting the job.

  
  I presume we would have the same problem with other backend that would do 
Kerberos authentication, although I do not know of a specific one.  I have only 
tested and investigated with the smb backend.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/788167/+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


  1   2   >