[Touch-packages] [Bug 1732300] [NEW] i don't know what this is

[Groyper13]

Public bug reported:

This started whn i trid to in stall th application Discord

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
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
Date: Tue Nov 14 15:38:00 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family 
Integrated Graphics Controller [1179:fc30]
InstallationDate: Installed on 2017-11-14 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: TOSHIBA Satellite P755
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=45d2d6e6-c951-4ca8-9bdd-4d8fbeb9f1c8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2012
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 2.80
dmi.board.asset.tag: NULL
dmi.board.name: PEQAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvr2.80:bd10/30/2012:svnTOSHIBA:pnSatelliteP755:pvrPSAY1U-02C027:rvnTOSHIBA:rnPEQAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite P755
dmi.product.version: PSAY1U-02C027
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
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: Tue Nov 14 15:05:32 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: modeset

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


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

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

Title:
  i don't know what this is

Status in xorg package in Ubuntu:
  New

Bug description:
  This started whn i trid to in stall th application Discord

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Tue Nov 14 15:38:00 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 2nd Generation Core Processor 
Family Integrated Graphics Controller [1179:fc30]
  InstallationDate: Installed on 2017-11-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: TOSHIBA Satellite P755
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=45d2d6e6-c951-4ca8-9bdd-4d8fbeb9f1c8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2012
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 2.80
  dmi.board.asset.tag: NULL
  dmi.board.name: PEQAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy

[Martin Pitt]

Patches backported into Debian packaging git:
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=9bba5469f2b95ea9

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

Title:
  Systemd - Bypassing MemoryDenyWriteExecution policy

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  New
Status in systemd source package in Zesty:
  New
Status in systemd source package in Artful:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Hello,

  We would like to report to you a vulnerability about systemd which
  allows to bypass the MemoryDenyWriteExecution policy on Linux 4.9+.

  The vulnerability is described in the attached PDF file.

  
  Sincerely, 
  Thomas IMBERT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725348/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Ray Link]

Sjors:

I'm interested to know how it goes for you with this update (either from
the included debdiff, or from the packages when they hit -proposed.)  We
were seeing the exact same symptoms you were, and deep-dove into your
backported fix from the GNOME bug and it all seems like it should fix
the issue.  We've tested extensively with your fix and the symptoms
completely disappeared, even from the machines most frequently affected.

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').

  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Sjors Gielen]

Hi Ray/Julian,

>  * NOTE: The final comment on the upstream GNOME bug claims that the fix
> is incomplete. However, it is possible that the running NetworkManager was
> not restarted (see Regression Potential notes above), which is why
> nm-dhcp-helper is falling back to Event.

This is not the case. Even today, one of the machines is showing the
message from the wrapper that indicates the DHCP lease was not correctly
applied according to the journal:

➜ sjors@cuba  ~  cat /tmp/nm-helper-retries.log 
Tue Nov 14 07:23:07 CET 2017: needed 5 attempts to update NetworkManager 
(RENEW).
Tue Nov 14 09:17:45 CET 2017: needed 5 attempts to update NetworkManager 
(RENEW).
Tue Nov 14 10:06:58 CET 2017: needed 4 attempts to update NetworkManager 
(RENEW).

This is even though the machine was rebooted yesterday, so the daemon
was restarted:

➜ sjors@cuba  ~  uptime  
 23:12:16 up 1 day, 14:04,  3 users,  load average: 0,59, 0,49, 0,47

And the machine is using the patched version of the network-manager:

➜ sjors@cuba  ~  apt-cache policy network-manager
network-manager:
  Installed: 1.2.6-0ubuntu0.16.04.1screenpoint1
  Candidate: 1.2.6-0ubuntu0.16.04.1screenpoint1
  Version table:
 *** 1.2.6-0ubuntu0.16.04.1screenpoint1 100
100 /var/lib/dpkg/status
 1.2.6-0ubuntu0.16.04.1 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages

However, I have not investigated why this happens, as the wrapper script
is an acceptable work-around. I'll report back, however, whether we
still have this problem with the updated Xenial packages -- there is
always a chance I made an error somewhere.

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from 

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Luke Faraone]

** Description changed:

- I've found an issue on some of our Xenial office machines, causing
- NetworkManager to drop its IP address lease in some cases when it
- shouldn't. I'm not sure if the actual bug is in NetworkManager or
- perhaps dbus or dhclient, but I'll do my best to help to figure out
- where it is.
+ SRU REQUEST:
+ 
+ Debdiff (nm-dhcp-helper.debdiff) attached.
+ 
+ Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug
+ was fixed upstream in 1.4.
+ 
+ [Impact]
+ 
+  * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
+    lease renewal due to a DBus race condition.
+ 
+  * Upstream NetworkManager 1.4 fixes the race condition by changing
+    nm-dhcp-helper's DBus notification from signal "Event" to method
+    "Notify".
+ 
+  * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
+    NM 1.2.x.
+ 
+ [Test Case]
+ 
+  * Not reliably reproducible. Out of hundreds of machines, only a
+    dozen or so fail to notify NetworkManager of a DHCP lease
+    renewal about 30-50% of the time. (i.e. It's always the same
+    handful of machines that fail.)
+ 
+  * All such machines with the patched packages have been fine for weeks,
+    over many dozens of lease renewals.
+ 
+ [Regression Potential]
+ 
+ * The patch changes both nm-dhcp-helper and NetworkManager itself. As
+ soon as the new packages are unpacked, the new nm-dhcp-helper will be
+ used on DHCP lease renewals, with the new Notify mechanism. Since the
+ running, old NetworkManager is still expecting Event notifications, the
+ patched nm-dhcp-helper has fallback capability to Event.
+ 
+ * Once NetworkManager is restarted and is running the patched version,
+ it will have the new Notify support.
+ 
+ [Other Info]
+ 
+  * Upstream bug w/ patch:
+ https://bugzilla.gnome.org/show_bug.cgi?id=784636
+ 
+  * RHEL bug with links to the 1.4 commits from which the patch was
+    derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276
+ 
+  * NOTE:  The final comment on the upstream GNOME bug claims that the
+ fix is incomplete.  However, it is possible that the running
+ NetworkManager was not restarted (see Regression Potential notes above),
+ which is why nm-dhcp-helper is falling back to Event.  The remainder of
+ the log messages in that final comment are from a custom wrapper the
+ submitter was running around nm-dhcp-helper.  I have deployed the exact
+ same patch (without said wrapper) to real-world systems and tested
+ extensively, and see nothing but successful DHCP lease renewal
+ notifications using D-Bus Notify, not D-Bus Event.
+ 
+ 
+ 
+ I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.
  
  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.
  
  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').
  
  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager
  reports a new lease with lease time 7200.
  
  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound
  
  After this, dhclient is supposed to keep the lease fresh, which it does.
  E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this
  DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds.
  
  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 

[Touch-packages] [Bug 1721102] Re: Thin line at the left of Simple Scan's "Scan" headerbar button

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20171114-0ubuntu1

---
ubuntu-themes (16.10+18.04.20171114-0ubuntu1) bionic; urgency=medium

  [ Andrea Azzarone ]
  * Fix osd progress bar look. (LP: #1724808)

  [ Carlo Lobrano ]
  * Ambiance, Radiance: fix horizontal linked suggested-action and
destructive-action (LP: #1721102)
  * Ambiance, Radiance: Fixed border in switcher widget (LP: #1719355)

  [ Marco Trevisan (Treviño) ]
  * Ambiance, Radiance (gtk2): remove undefined "murrine-scrollbar" from
mate panel (LP: #1723422)
  * Ambiance, Radiance: add theming for headerbar .destructive-action
button's (LP: #1726318)
  * Ambiance, Radiance: Use inverted gradient for button actions in
maximized titlebars (LP: #1726322)

 -- Marco Trevisan (Treviño)   Tue, 14 Nov 2017 17:50:15
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Thin line at the left of Simple Scan's "Scan" headerbar button

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  There is a thin colored line (green or red) at the left of rounded button, 
for example in simple-scan in the screenshot attached (I didn't find any other 
app affected ATM)

  [Test case]
  1. Run simple scan
  2. Expect "Scan" button background color to fill all the space.

  4. Start scanning and expect the same for "Stop" button too

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170930-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  3 20:16:32 2017
  InstallationDate: Installed on 2013-09-03 (1490 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1721102/+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 1719355] Re: Switcher widget background goes outside its border

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20171114-0ubuntu1

---
ubuntu-themes (16.10+18.04.20171114-0ubuntu1) bionic; urgency=medium

  [ Andrea Azzarone ]
  * Fix osd progress bar look. (LP: #1724808)

  [ Carlo Lobrano ]
  * Ambiance, Radiance: fix horizontal linked suggested-action and
destructive-action (LP: #1721102)
  * Ambiance, Radiance: Fixed border in switcher widget (LP: #1719355)

  [ Marco Trevisan (Treviño) ]
  * Ambiance, Radiance (gtk2): remove undefined "murrine-scrollbar" from
mate panel (LP: #1723422)
  * Ambiance, Radiance: add theming for headerbar .destructive-action
button's (LP: #1726318)
  * Ambiance, Radiance: Use inverted gradient for button actions in
maximized titlebars (LP: #1726322)

 -- Marco Trevisan (Treviño)   Tue, 14 Nov 2017 17:50:15
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Switcher widget background goes outside its border

Status in Ubuntu theme:
  In Progress
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  In both Ambiance and Radiance themes, the switcher background is
  visible outside the widget border when inside a headerbar.

  See picture from Gnome Control Settings -> Search

  [Test case]

  1. Open Gnome Control Settings -> Search
  2. Ensure that no extra border is around the switcher (especially in the 
headerbar)

  [Regression potential]

  Switchers  borders are incorrect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1719355/+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 1722151] Update Released

[Brian Murray]

The verification of the Stable Release Update for language-selector has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in accountsservice source package in Artful:
  Fix Committed
Status in language-selector source package in Artful:
  Fix Released

Bug description:
  [Impact]

  When the syntax for the entries in ~/.pam_environment was changed, the
  GUI in language-selector-gnome for maintaining the language priority
  list was broken since language-selector-gnome reads from
  ~/.pam_environment. The language-selector upload to artful makes
  language-selector-gnome handle both the old and the new syntax
  correctly.

  An additional similar change to accountsservice (the update-langlist
  script) is needed; hence also an accountsservice upload to artful.

  [Test Case]

  * Log in to an "Ubuntu on Xorg" session.
  * Open Language Support and find that it appears as if you can only
    set one item before the "English" item in the language list.

  With the new version, it works as expected again.

  [Regression Potential]

  Low. This is necessary to fix the regression caused by the change in
  accountsservice.

  [Original description]

  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

[Launchpad Bug Tracker]

This bug was fixed in the package language-selector - 0.180.1

---
language-selector (0.180.1) artful-proposed; urgency=medium

  * LanguageSelector/LocaleInfo.py:
Adapt to changed syntax in ~/.pam_environment (LP: #1722151).

 -- Gunnar Hjalmarsson   Fri, 27 Oct 2017 19:43:00
+0200

** Changed in: language-selector (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in accountsservice source package in Artful:
  Fix Committed
Status in language-selector source package in Artful:
  Fix Released

Bug description:
  [Impact]

  When the syntax for the entries in ~/.pam_environment was changed, the
  GUI in language-selector-gnome for maintaining the language priority
  list was broken since language-selector-gnome reads from
  ~/.pam_environment. The language-selector upload to artful makes
  language-selector-gnome handle both the old and the new syntax
  correctly.

  An additional similar change to accountsservice (the update-langlist
  script) is needed; hence also an accountsservice upload to artful.

  [Test Case]

  * Log in to an "Ubuntu on Xorg" session.
  * Open Language Support and find that it appears as if you can only
    set one item before the "English" item in the language list.

  With the new version, it works as expected again.

  [Regression Potential]

  Low. This is necessary to fix the regression caused by the change in
  accountsservice.

  [Original description]

  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20171114-0ubuntu1

---
ubuntu-themes (16.10+18.04.20171114-0ubuntu1) bionic; urgency=medium

  [ Andrea Azzarone ]
  * Fix osd progress bar look. (LP: #1724808)

  [ Carlo Lobrano ]
  * Ambiance, Radiance: fix horizontal linked suggested-action and
destructive-action (LP: #1721102)
  * Ambiance, Radiance: Fixed border in switcher widget (LP: #1719355)

  [ Marco Trevisan (Treviño) ]
  * Ambiance, Radiance (gtk2): remove undefined "murrine-scrollbar" from
mate panel (LP: #1723422)
  * Ambiance, Radiance: add theming for headerbar .destructive-action
button's (LP: #1726318)
  * Ambiance, Radiance: Use inverted gradient for button actions in
maximized titlebars (LP: #1726322)

 -- Marco Trevisan (Treviño)   Tue, 14 Nov 2017 17:50:15
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  That installation is a default Ubuntu , no Mate installed, and
  Ambiance is set for 'applications' into tweaks

  [Test case]

  1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal
  2. App has to run without any error

  [Possible regression]

  Different scrollbars in gtk2 apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1724808] Re: osd progress looks odd using Ambiance or Radiance

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20171114-0ubuntu1

---
ubuntu-themes (16.10+18.04.20171114-0ubuntu1) bionic; urgency=medium

  [ Andrea Azzarone ]
  * Fix osd progress bar look. (LP: #1724808)

  [ Carlo Lobrano ]
  * Ambiance, Radiance: fix horizontal linked suggested-action and
destructive-action (LP: #1721102)
  * Ambiance, Radiance: Fixed border in switcher widget (LP: #1719355)

  [ Marco Trevisan (Treviño) ]
  * Ambiance, Radiance (gtk2): remove undefined "murrine-scrollbar" from
mate panel (LP: #1723422)
  * Ambiance, Radiance: add theming for headerbar .destructive-action
button's (LP: #1726318)
  * Ambiance, Radiance: Use inverted gradient for button actions in
maximized titlebars (LP: #1726322)

 -- Marco Trevisan (Treviño)   Tue, 14 Nov 2017 17:50:15
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  osd progress looks odd using Ambiance or Radiance

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  == Impact ==
  osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.

  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.

  == Potential Regressions ==
  Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.

  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1724808/+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 1726318] Re: Destructive actions on headerbar aren't properly themed

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+18.04.20171114-0ubuntu1

---
ubuntu-themes (16.10+18.04.20171114-0ubuntu1) bionic; urgency=medium

  [ Andrea Azzarone ]
  * Fix osd progress bar look. (LP: #1724808)

  [ Carlo Lobrano ]
  * Ambiance, Radiance: fix horizontal linked suggested-action and
destructive-action (LP: #1721102)
  * Ambiance, Radiance: Fixed border in switcher widget (LP: #1719355)

  [ Marco Trevisan (Treviño) ]
  * Ambiance, Radiance (gtk2): remove undefined "murrine-scrollbar" from
mate panel (LP: #1723422)
  * Ambiance, Radiance: add theming for headerbar .destructive-action
button's (LP: #1726318)
  * Ambiance, Radiance: Use inverted gradient for button actions in
maximized titlebars (LP: #1726322)

 -- Marco Trevisan (Treviño)   Tue, 14 Nov 2017 17:50:15
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Destructive actions on headerbar aren't properly themed

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  On simple scan (for example) there's a .destructive-action button in
  the headerbar and it's not drawn as red unless the button is hovered,
  clicked or unfocused. It also uses inconsistent gradients

  [ Test case ]

  1. Run gnome-scan
  2. Start a scan session (or use the inspector to set the "Stop" button as 
visible)
  3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered)

  [ Regression Potential]

  Destructive buttons in headerbar could be broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1726318/+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 1629782] Re: Hotspot crashes the device and reboots

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Hotspot crashes the device and reboots

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  The device hangs and reboots after some tasks related to hotspot.

  There are a couple of ways that this bug occurred.

  1. While the hotspot is on, try to change hotspot settings like
  requiring passwords. Upon clicking the Change button, the bug occurs.
  (happens always)

  2. Turning on the hotspot from the settings app while the wifi is off
  the bug occurs. (happened once)

  
  Not sure what log will be helpful. Please let me know and I'll attach them.

  Device:
  bq E5 HD (OTA 13)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629782/+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 1727694] Update Released

[Brian Murray]

The verification of the Stable Release Update for apt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] apt/artful 1.5.1 microrelease

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Artful:
  Fix Released

Bug description:
  [Impact]
  This release fixes the test suite failures with dpkg 1.19, updates two 
translations, fixes an error message, and finally makes apt-key not fail 
silently if some files are in the wrong format.

[ Julian Andres Klode ]
* travis: CI: Test 1.5.y on artful
* Fix testsuite for and add new fields from dpkg 1.19
* debian/gbp.conf: Switch to 1.5.y branch

[ Mo Zhou ]
* zh_CN.po: Update Simplified Chinese programs translation

[ Frans Spiesschaert ]
* Dutch program translation update (Closes: #879137)

[ David Kalnischkies ]
* proper error reporting for v3 onion services
* ignore unsupported key formats in apt-key (Closes: #876508)

  [Test case]
  All changes are tested by autopkgtests.

  [Regression potential]
  Could maybe be warning about potentially valid gpg files now. Seems unlikely, 
though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1727694/+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 1447748] Re: SIM unlock screen unusable when launched from indicator

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

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

Title:
  SIM unlock screen unusable when launched from indicator

Status in indicator-network package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The SIM lock screen behaves differently during boot and launching it
  from indicator network. Mostly unusable from indicator to unlock PIN
  (those were the failures reported below).

  Test case.
  - Reboot the phone with a valid SIM card.
  - Unlock the device.
  - Dismiss the PIN unlock screen.
  - Open the network indicator.
  - Tap on unlock SIM card.
  - Introduce incorrect PINs.

  Expected result.
  - The behaviour is the same as when the SIM unlock page is run on boot time.

  Actual result.
  - The number of remaining PIN trials is not correctly shown.
  - When the PIN is locked, no PUK lock screen is shown. Must be closed and 
opened (tap on unlock SIM card in indicator) to be shown.
  - After PUK has been correctly introduced, PIN screen should be shown. It is 
not.
  - Close and re-open the screen does show the PIN screen to introduce the new 
one.

  Tested with vivid-proposed 183 / Arale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1447748/+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 1589149] Re: the two Hotspots buttons seem to disagree

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  the two Hotspots buttons seem to disagree

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  When i try to activate the hotspot using the menu that you can make appear 
from above (the black-background one) it seems not to work (no hotspot and no 
hotspot symbol on the top menu appearing).
  If I open setting->hotspot, there the hotspot button is deactivated (not 
green) while the hotspot button in the black menu is green.
  It seems the button in the Settings if activated can really make the hotspot 
work (and make the hotspot button in the black menu green) but the hotspot 
button in the black menu seems to just do nothing (except cutting wifi)

  
  On the meizu 4 with ota 11. I think the problem came with ota 11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589149/+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 1412716] Re: [dash] Make Soundcloud scope background "waveform" lighter

[Pete Woods]

** Changed in: unity-scope-soundcloud
 Assignee: Pete Woods (pete-woods) => (unassigned)

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

Title:
  [dash] Make Soundcloud scope background "waveform" lighter

Status in Ubuntu UX:
  Fix Committed
Status in Unity SoundCloud Scope:
  New
Status in unity-scope-soundcloud package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  We would love to change the color of the design in the streaming as
  the image attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1412716/+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 1280372] Re: Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

[Pete Woods]

** No longer affects: hud

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

Title:
  Unknown Qt application causes HUD / libdbusmenu-qt to use 100% CPU

Status in libdbusmenu-qt:
  Fix Released
Status in hud package in Ubuntu:
  Fix Released
Status in libdbusmenu-qt package in Ubuntu:
  Fix Released

Bug description:
  See the following debug output:
  * http://paste.ubuntu.com/6931329/
  * http://paste.ubuntu.com/6931331/
  * http://paste.ubuntu.com/6931338/
  * http://paste.ubuntu.com/7151579/

  14:09:09 QVariantMap DBusMenuExporterDBus::getProperties(int, const 
QStringList&) const: Condition failed: action
  14:09:09 bool DBusMenuExporterDBus::AboutToShow(int): Condition failed: menu

  Was also seen in the console.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libdbusmenu-qt/+bug/1280372/+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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in Canonical System Image:
  Fix Released
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+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 1567250] Re: ssh signin problem since OTA-10

[Pete Woods]

** Changed in: gnome-keyring (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (unassigned)

** Changed in: indicator-network (Ubuntu)
 Assignee: Pete Woods (pete-woods) => (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/1567250

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Incomplete
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+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 1727694] Re: [SRU] apt/artful 1.5.1 microrelease

[Launchpad Bug Tracker]

This bug was fixed in the package apt - 1.5.1

---
apt (1.5.1) artful; urgency=medium

  * New microrelease (LP: #1727694)

  [ Julian Andres Klode ]
  * travis: CI: Test 1.5.y on artful
  * Fix testsuite for and add new fields from dpkg 1.19
  * debian/gbp.conf: Switch to 1.5.y branch
  * debian/tests/control: Add dpkg so we get triggered by it

  [ Mo Zhou ]
  * zh_CN.po: Update Simplified Chinese programs translation

  [ Frans Spiesschaert ]
  * Dutch program translation update (Closes: #879137)

  [ David Kalnischkies ]
  * proper error reporting for v3 onion services
  * ignore unsupported key formats in apt-key (Closes: #876508)

 -- Julian Andres Klode   Thu, 26 Oct 2017 13:36:39
+0200

** Changed in: apt (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] apt/artful 1.5.1 microrelease

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Artful:
  Fix Released

Bug description:
  [Impact]
  This release fixes the test suite failures with dpkg 1.19, updates two 
translations, fixes an error message, and finally makes apt-key not fail 
silently if some files are in the wrong format.

[ Julian Andres Klode ]
* travis: CI: Test 1.5.y on artful
* Fix testsuite for and add new fields from dpkg 1.19
* debian/gbp.conf: Switch to 1.5.y branch

[ Mo Zhou ]
* zh_CN.po: Update Simplified Chinese programs translation

[ Frans Spiesschaert ]
* Dutch program translation update (Closes: #879137)

[ David Kalnischkies ]
* proper error reporting for v3 onion services
* ignore unsupported key formats in apt-key (Closes: #876508)

  [Test case]
  All changes are tested by autopkgtests.

  [Regression potential]
  Could maybe be warning about potentially valid gpg files now. Seems unlikely, 
though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1727694/+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 1452567] Re: Wifi icon disappears at the first connection with a hidden network

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Wifi icon disappears at the first connection with a hidden network

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  $ system-image-cli -i
  current build number: 274
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-05-07 02:27:02
  version version: 274
  version ubuntu: 20150505
  version device: 20150505-db7b5bd
  version custom: 20150505-682-29-215

  Steps to reproduce the issue:
  1.Tap Wifi settings
  2.Select 'Connect to hidden network…
  3.Enter the SSID and correct password for the network

  Expected results:
  The icon should be shown in the network indicator even if a hidden network is 
connected

  Actual results:
  Wifi icon disappears when connecting to a hidden network on the first try, 
and the SSID is invisible too,
  Both the wifi icon and SSID will appear after forget and re-connect.

  Not sure if it is a regression of issue
  https://bugs.launchpad.net/barajas/+bug/1404195

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1452567/+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 1339792] Re: Panel network icon - too much latency when network type changes

[Pete Woods]

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: indicator-network (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

** Changed in: indicator-network (Ubuntu RTM)
   Status: Confirmed => Won't Fix

** Changed in: ofono (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ofono (Ubuntu Utopic)
   Status: Confirmed => Won't Fix

** Changed in: ofono (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

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

Title:
  Panel network icon - too much latency when network type changes

Status in indicator-network package in Ubuntu:
  Won't Fix
Status in ofono package in Ubuntu:
  Won't Fix
Status in indicator-network source package in Utopic:
  Won't Fix
Status in ofono source package in Utopic:
  Won't Fix
Status in indicator-network source package in Vivid:
  Won't Fix
Status in ofono source package in Vivid:
  Won't Fix
Status in indicator-network package in Ubuntu RTM:
  Won't Fix

Bug description:
  Testing image #u122 this morning, I ran into two separate scenarios
  where the panel network icon didn't always accurately reflect the
  current network technology due to some kind of latency detecting
  network changes ( ie. WiFi -> 3G -> WiFi ).

  Both scenarios were reproduced on mako.

  Scenario 1:

  3G: online
  WiFi: enabled; connected to AP 1

  - display network menu
  - tap another secure network
  - tap cancel when Password dialog is displayed

  At this point the indicator shows '3G' whereas the network menu still
  shows the original AP 1 as connected.  After some period of time ( 10s
  - 1m ), the icon will change back to show that WiFi is connected.

  Scenario 2:

  3G: online
  WiFi: connected to AP 1

  - go to System Settings::WiFi
  - click "Previous Networks"
  - select the currently connected AP/network
  - click Forget Network
  - go back to WiFi settings

  The WiFi settings correctly shows the AP is no longer connected,
  however again the network icon takes some time ( 10s - 1m ) to reflect
  the change back to "3G".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Julian Andres Klode]

Fix uploaded.

** Changed in: network-manager (Ubuntu Xenial)
   Status: Triaged => In Progress

** Description changed:

  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.
  
  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.
  
  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').
  
  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager
  reports a new lease with lease time 7200.
  
  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound
  
  After this, dhclient is supposed to keep the lease fresh, which it does.
  E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this
  DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds.
  
  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.
  
  However, at 03:21:07 (exactly 2 hours and 1 second after the last lease
  reported by NetworkManager) Avahi and NTP report that the IP address is
  gone:
  
  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs
  
  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   default via 192.168.0.5 dev eth0  proto static  metric 100
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166  metric 
100
  IwConfig:
   lono wireless extensions.
  
   eth1  no wireless extensions.
  
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
  
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH 

[Touch-packages] [Bug 1385903] Re: imagemagick crashes with "stack smashing detected"

[Christopher M. Penalver]

Vivid EOL as per:
https://wiki.ubuntu.com/Releases

** Changed in: libjpeg-turbo (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

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

Title:
  imagemagick crashes with "stack smashing detected"

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg-turbo source package in Precise:
  Won't Fix
Status in libjpeg-turbo source package in Trusty:
  Confirmed
Status in libjpeg-turbo source package in Utopic:
  Won't Fix
Status in libjpeg-turbo source package in Vivid:
  Won't Fix

Bug description:
  Every now and then imagemagick convert crashes like this:

  $ convert -rotate 270 003632r270.jpg koe.jpg
  *** stack smashing detected ***: convert terminated
  Aborted (core dumped)

  This is perfectly reproducible and happens in every Ubuntu 14.04 box
  I have at hand that has ImageMagick in it, but not in 12.04.
  I'll attach the file used in above example (I have several more
  in case someone wants them).
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tt 2149 F pulseaudio
  CurrentDesktop: LXDE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  IwConfig:
   br0   no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GM
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1385903] Re: imagemagick crashes with "stack smashing detected"

[Christopher M. Penalver]

Precise EOL as per:
https://wiki.ubuntu.com/Releases

** Changed in: libjpeg-turbo (Ubuntu Precise)
   Status: Confirmed => Won't Fix

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

Title:
  imagemagick crashes with "stack smashing detected"

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg-turbo source package in Precise:
  Won't Fix
Status in libjpeg-turbo source package in Trusty:
  Confirmed
Status in libjpeg-turbo source package in Utopic:
  Won't Fix
Status in libjpeg-turbo source package in Vivid:
  Won't Fix

Bug description:
  Every now and then imagemagick convert crashes like this:

  $ convert -rotate 270 003632r270.jpg koe.jpg
  *** stack smashing detected ***: convert terminated
  Aborted (core dumped)

  This is perfectly reproducible and happens in every Ubuntu 14.04 box
  I have at hand that has ImageMagick in it, but not in 12.04.
  I'll attach the file used in above example (I have several more
  in case someone wants them).
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tt 2149 F pulseaudio
  CurrentDesktop: LXDE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  IwConfig:
   br0   no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GM
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Ray Link]

** Description changed:

  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.
  
  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.
  
  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').
- 
- 
  
  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager
  reports a new lease with lease time 7200.
  
  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound
  
  After this, dhclient is supposed to keep the lease fresh, which it does.
  E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this
  DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds.
  
  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.
  
  However, at 03:21:07 (exactly 2 hours and 1 second after the last lease
  reported by NetworkManager) Avahi and NTP report that the IP address is
  gone:
  
  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs
  
  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
-  default via 192.168.0.5 dev eth0  proto static  metric 100 
-  192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166 
-  192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166  metric 
100
+  default via 192.168.0.5 dev eth0  proto static  metric 100
+  192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166
+  192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166  metric 
100
  IwConfig:
-  lono wireless extensions.
-  
-  eth1  no wireless extensions.
-  
-  eth0  no wireless extensions.
+  lono wireless extensions.
+ 
+  eth1  no wireless extensions.
+ 
+  eth0  no wireless extensions.
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Julian Andres Klode]

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

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

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

** Changed in: network-manager (Ubuntu Xenial)
   Importance: Undecided => Low

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Triaged

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   default via 192.168.0.5 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  

[Touch-packages] [Bug 1732270] [NEW] this computer is very unresponsive

[Cathy Buck]

Public bug reported:

Takes a long time to load on various sites. Sometimes the commands do
not work ! Navigation response is very spotty.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Nov 14 15:17:11 2017
DistUpgraded: 2017-01-26 19:38:06,653 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[1028:01f2]
   Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f2]
InstallationDate: Installed on 2013-10-06 (1499 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
MachineType: Dell Inc. Inspiron 1720
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=380418a6-87fb-4c43-b576-c68c8e1df6bb ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-01-27 (291 days ago)
dmi.bios.date: 07/11/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0UK439
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn0UK439:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1720
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Nov 14 10:04:19 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   0 
 vendor LPL
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  this computer is very unresponsive

Status in xorg package in Ubuntu:
  New

Bug description:
  Takes a long time to load on various sites. Sometimes the commands do
  not work ! Navigation response is very spotty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Nov 14 15:17:11 2017
  DistUpgraded: 2017-01-26 19:38:06,653 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [1028:01f2]
 Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [1028:01f2]
  InstallationDate: Installed on 2013-10-06 (1499 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
  MachineType: Dell Inc. Inspiron 1720
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=380418a6-87fb-4c43-b576-c68c8e1df6bb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  

[Touch-packages] [Bug 1385903] Re: imagemagick crashes with "stack smashing detected"

[Ubuntu Foundations Team Bug Bot]

The attachment "Debdiff, adapted from Debian 1:1.3.1-11" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  imagemagick crashes with "stack smashing detected"

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg-turbo source package in Precise:
  Confirmed
Status in libjpeg-turbo source package in Trusty:
  Confirmed
Status in libjpeg-turbo source package in Utopic:
  Won't Fix
Status in libjpeg-turbo source package in Vivid:
  Confirmed

Bug description:
  Every now and then imagemagick convert crashes like this:

  $ convert -rotate 270 003632r270.jpg koe.jpg
  *** stack smashing detected ***: convert terminated
  Aborted (core dumped)

  This is perfectly reproducible and happens in every Ubuntu 14.04 box
  I have at hand that has ImageMagick in it, but not in 12.04.
  I'll attach the file used in above example (I have several more
  in case someone wants them).
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tt 2149 F pulseaudio
  CurrentDesktop: LXDE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  IwConfig:
   br0   no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GM
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1724808] Re: osd progress looks odd using Ambiance or Radiance

[Andrea Azzarone]

** Description changed:

- osd progress bar, used e.g. the one used by epiphany-browser when
- loading pages, looks odd with Ambiance or Radiance.
+ == Impact ==
+ osd progress bars looks poor with Ambiance or Radiance in Ubuntu 17.10.
+ osd progress bars are used e.g. in epiphany web browser.
+ 
+ == Test Case ==
+ 1. Open gnome control center
+ 2. Go to online accounts panel
+ 3. Add a google account
+ 4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.
+ 
+ == Potential Regressions ==
+ Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix. 
+ 
+ == Original Bug Report ==
+ osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

** Description changed:

  == Impact ==
- osd progress bars looks poor with Ambiance or Radiance in Ubuntu 17.10.
+ osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.
  
  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.
  
  == Potential Regressions ==
- Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix. 
+ Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.
  
  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

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

Title:
  osd progress looks odd using Ambiance or Radiance

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.

  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.

  == Potential Regressions ==
  Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.

  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1724808/+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 1385903] Re: imagemagick crashes with "stack smashing detected"

[Micah Cowan]

Suggest increasing the importance of this bug, considering it has a CVE
assignment? I realize that it's a DoS, which is low on the
"vulnerability" totem pole; but especially with buffer overruns I tend
to suspect that "DoS" is code for "might allow code execution but no
one's bothered to prove it". Anyway, the fix is trivial, and provided in
the attached debdiff.

Cheers!

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

Title:
  imagemagick crashes with "stack smashing detected"

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg-turbo source package in Precise:
  Confirmed
Status in libjpeg-turbo source package in Trusty:
  Confirmed
Status in libjpeg-turbo source package in Utopic:
  Won't Fix
Status in libjpeg-turbo source package in Vivid:
  Confirmed

Bug description:
  Every now and then imagemagick convert crashes like this:

  $ convert -rotate 270 003632r270.jpg koe.jpg
  *** stack smashing detected ***: convert terminated
  Aborted (core dumped)

  This is perfectly reproducible and happens in every Ubuntu 14.04 box
  I have at hand that has ImageMagick in it, but not in 12.04.
  I'll attach the file used in above example (I have several more
  in case someone wants them).
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tt 2149 F pulseaudio
  CurrentDesktop: LXDE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  IwConfig:
   br0   no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GM
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1385903] Re: imagemagick crashes with "stack smashing detected"

[Micah Cowan]

I've supplied a debdiff to address the fix for this CVE, based on
upstream Debian's fix.

** Patch added: "Debdiff, adapted from Debian 1:1.3.1-11"
   
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+attachment/5009069/+files/libjpeg-turbo.diff

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

Title:
  imagemagick crashes with "stack smashing detected"

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg-turbo source package in Precise:
  Confirmed
Status in libjpeg-turbo source package in Trusty:
  Confirmed
Status in libjpeg-turbo source package in Utopic:
  Won't Fix
Status in libjpeg-turbo source package in Vivid:
  Confirmed

Bug description:
  Every now and then imagemagick convert crashes like this:

  $ convert -rotate 270 003632r270.jpg koe.jpg
  *** stack smashing detected ***: convert terminated
  Aborted (core dumped)

  This is perfectly reproducible and happens in every Ubuntu 14.04 box
  I have at hand that has ImageMagick in it, but not in 12.04.
  I'll attach the file used in above example (I have several more
  in case someone wants them).
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tt 2149 F pulseaudio
  CurrentDesktop: LXDE
  CurrentDmesg:
   Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg 
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
   dmesg: write failed: Broken pipe
  DistroRelease: Ubuntu 14.04
  IwConfig:
   br0   no wireless extensions.
   
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic 
root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic i686
  UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/09/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 945GM
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1724808] Re: osd progress looks odd using Ambiance or Radiance

[Treviño]

** Changed in: ubuntu-themes
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  osd progress looks odd using Ambiance or Radiance

Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  == Impact ==
  osd progress bars look poor with Ambiance or Radiance in Ubuntu 17.10.
  osd progress bars are used e.g. in epiphany web browser.

  == Test Case ==
  1. Open gnome control center
  2. Go to online accounts panel
  3. Add a google account
  4. Make sure the progress bar close to the title bar of the login dialog does 
not present borders and paddings.

  == Potential Regressions ==
  Please check thare are no regressions with osd toolbars. An example of 
application using osd toolbars is totem. Make sure the overlay with play/pause 
controls is not affected by the fix.

  == Original Bug Report ==
  osd progress bar, used e.g. the one used by epiphany-browser when loading 
pages, looks odd with Ambiance or Radiance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1724808/+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 1648183] Re: Crackling and popping sound when using headphones

[Adrian Casais]

Same problem with HP Pavilion Power 15-cb. Kernel 4.10.0-38-generic.
Although @robertjjoynt workaround WORKED for me also, I think this issue
should be fixed from it's root...

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

[Łukasz Zemczak]

I accepted the packages as is. Was worried a bit as the patch is not
handling the case of dev->dnsdomainname being NULL when being passed to
write_option() (causing a SEGFAULT), but as per discussion with Matt -
since upstream doesn't do a check for it != NULL it might mean such a
case is not really a possible edge case.

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

[Łukasz Zemczak]

Hello Mathieu, or anyone else affected,

Accepted klibc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu1.16.04.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: klibc (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

[Łukasz Zemczak]

Hello Mathieu, or anyone else affected,

Accepted klibc into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/klibc/2.0.4-8ubuntu4.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-zesty to verification-done-zesty. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: klibc (Ubuntu Zesty)
   Status: Triaged => Fix Committed

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Zesty:
  Fix Committed
Status in klibc source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1713747/+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 1713004] Re: Temporary files left under /var/tmp by mkinitramfs

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Temporary files left under /var/tmp by mkinitramfs

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  I recently ran out of disk space on my / mount.  While looking for
  what consumed the disk I noticed a large number (130) of directories
  with names / paths beginning /var/tmp/mkinitramfs.  These directories
  seem to be either ~103 MB or ~927 MB in size.  Many of these files are
  months old, some are almost a year.

  Having had a quick look about for an explanation as to why these files
  are here and found Debian Bug #814345.  That explains that temporary
  files are left behind by the initramfs-tools if something fails in the
  process.  If this is the cause of my files then updating the Ubuntu
  package to version 0.123 should resolve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  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.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 25 09:40:41 2017
  InstallationDate: Installed on 2015-03-12 (896 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1713004/+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 1659339] Re: "libmtp error: Could not send object" when copying a file to MTP folder

[Another Nymous]

Same problem here, also with mp3 files.  I use Thunar to copy some
folder within `mtp://[usb:001,054]/SD-Card/Music/`, and the first few-
ish work, then I get the error dialog, and no matter what I do next,
thunar is extremely slow or completely unresponsive in *every*
operation, even when I kill the process and open an unrelated folder.
My guess is that thunar lists all devices/places/networks, thus accesses
libmtp, which locked up.  Only disconnecting the device lets me try it
again.

Happens on both my systems, both use libmtp 1.1.13.

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

Title:
  "libmtp error: Could not send object" when copying a file to MTP
  folder

Status in Linux Mint:
  New
Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  Linux Mint 17.2/17.3/18/18.1 (problem arises in all of these).

  I connect my Android phone over MTP, LM opens the folder (for example
  "mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono"), then I
  try to copy a file from my filesystem to the phone.

  I get a window that says:

  Error while copying "foo.png".//There was an error copying the file
  into
  mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono/.//libmtp
  error:  Could not send object info.//Cancel/Skip.

  I think that the copy operation should proceed and having my file
  "foo.png" in phone's memory.

  The problem happens always, indeed the copy never worked for me in any
  of the LM versions mentioned above, that is, from the very first time
  I used LM.

  I can read (copy) files from the phone to the laptop, and I can delete
  files from the phone.

  $ lsusb
  Bus 002 Device 002: ID 13b1:0041 Linksys 
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
  Bus 001 Device 005: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 
/ G1 / Magic / Tattoo (Debug)
  Bus 001 Device 002: ID 0458:00f2 KYE Systems Corp. (Mouse Systems) 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1659339/+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 1732241] [NEW] graphic card driver

[abderrahman]

Public bug reported:

issue in starting lubuntu 17.10
it seems like a screen problem 
but i think its a driver issue since itried aditional driver tool but its not 
aorking
and thanks.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: i386
CurrentDesktop: LXDE
Date: Tue Nov 14 17:44:48 2017
InstallationDate: Installed on 2017-11-13 (0 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug artful i386

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

Title:
  graphic card driver

Status in xorg package in Ubuntu:
  New

Bug description:
  issue in starting lubuntu 17.10
  it seems like a screen problem 
  but i think its a driver issue since itried aditional driver tool but its not 
aorking
  and thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Tue Nov 14 17:44:48 2017
  InstallationDate: Installed on 2017-11-13 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732241/+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 1730647] Re: on s390x one should alway be able to manipulate z devices

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

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

Title:
  on s390x one should alway be able to manipulate z devices

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730647/+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 1726093] Re: ubuntu-desktop: Install gir1.2-gmenu-3.0 by default

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.404.1

---
ubuntu-meta (1.404.1) artful; urgency=medium

  * Refreshed dependencies
  * Added gir1.2-gmenu-3.0 to desktop-recommends LP: #1726093
  * Added s390-tools to server [s390x] LP: #1730647

 -- Dimitri John Ledkov   Tue, 07 Nov 2017 11:11:54
+

** Changed in: ubuntu-meta (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-desktop: Install gir1.2-gmenu-3.0 by default

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed 
by several popular GNOME Shell extensions.

  Test Case
  =
  Install the update to Ubuntu 17.10.
  Open the Ubuntu Software app.
  Search for Arc Menu
  Install it.
  There should be an A menu in the top left of the screen.

  Other Info
  ==
  Debian-based distros are somewhat unique in that they split gir files into 
separate packages. This is normally not a problem since .deb packages should 
simply depend on the packages they need. It is a bit of a problem for GNOME 
Shell extensions distributed through extensions.gnome.org since they can't 
depend on system packages except as a comment in the extension description that 
may or may be read even if it is mentioned.

  Specifically, there are several extensions that add a traditional
  applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0.

  This wasn't noticed much before because both Debian GNOME and Ubuntu
  GNOME installed the gnome-shell-extensions package by default which
  depends on gir1.2-gmenu-3.0.

  Now though, it just feels to users like Ubuntu is broken. I've read
  comments that think that Ubuntu is intentionally trying to make it
  difficult to use these app menu extensions.

  Approved at the Ubuntu Desktop meeting (discussion continues until 15:09)
  https://irclogs.ubuntu.com/2017/10/24/%23ubuntu-desktop.html#t14:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726093/+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 1730647] Re: on s390x one should alway be able to manipulate z devices

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.361.1

---
ubuntu-meta (1.361.1) xenial; urgency=medium

  * Refreshed dependencies
  * Added s390-tools to server [s390x] LP: #1730647

 -- Dimitri John Ledkov   Tue, 07 Nov 2017 11:30:35
+

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

Title:
  on s390x one should alway be able to manipulate z devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730647/+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 1726093] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for ubuntu-meta has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  ubuntu-desktop: Install gir1.2-gmenu-3.0 by default

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed 
by several popular GNOME Shell extensions.

  Test Case
  =
  Install the update to Ubuntu 17.10.
  Open the Ubuntu Software app.
  Search for Arc Menu
  Install it.
  There should be an A menu in the top left of the screen.

  Other Info
  ==
  Debian-based distros are somewhat unique in that they split gir files into 
separate packages. This is normally not a problem since .deb packages should 
simply depend on the packages they need. It is a bit of a problem for GNOME 
Shell extensions distributed through extensions.gnome.org since they can't 
depend on system packages except as a comment in the extension description that 
may or may be read even if it is mentioned.

  Specifically, there are several extensions that add a traditional
  applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0.

  This wasn't noticed much before because both Debian GNOME and Ubuntu
  GNOME installed the gnome-shell-extensions package by default which
  depends on gir1.2-gmenu-3.0.

  Now though, it just feels to users like Ubuntu is broken. I've read
  comments that think that Ubuntu is intentionally trying to make it
  difficult to use these app menu extensions.

  Approved at the Ubuntu Desktop meeting (discussion continues until 15:09)
  https://irclogs.ubuntu.com/2017/10/24/%23ubuntu-desktop.html#t14:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726093/+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 1730647] Re: on s390x one should alway be able to manipulate z devices

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.379.1

---
ubuntu-meta (1.379.1) zesty; urgency=medium

  * Refreshed dependencies
  * Added s390-tools to server [s390x] LP: #1730647

 -- Dimitri John Ledkov   Tue, 07 Nov 2017 11:25:35
+

** Changed in: ubuntu-meta (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  on s390x one should alway be able to manipulate z devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730647/+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 1730647] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for ubuntu-meta has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  on s390x one should alway be able to manipulate z devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730647/+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 1730647] Re: on s390x one should alway be able to manipulate z devices

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.404.1

---
ubuntu-meta (1.404.1) artful; urgency=medium

  * Refreshed dependencies
  * Added gir1.2-gmenu-3.0 to desktop-recommends LP: #1726093
  * Added s390-tools to server [s390x] LP: #1730647

 -- Dimitri John Ledkov   Tue, 07 Nov 2017 11:11:54
+

** Changed in: ubuntu-meta (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  on s390x one should alway be able to manipulate z devices

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * Currently s390-tools is not installed as part of the server seed,
  which leads to inconsistencies between manually installed systems with
  d-i and systems originating from cloud images - containers, cloud
  images, maas. d-i installs s390-tools, whilst the rest do not.
  However, s390-tools ship tooling to inspect, list, operate on z
  specific devices and should always be available across all of ubuntu,
  including containers, maas, etc. Hence seeding it to server seed.

  [Test Case]

   * s390x containers have s390-tools package installed
   * s390x cloud images have s390-tools package installed
   * s390x maas images have s390-tools package installed

  [Regression Potential]

   * This is calling ubuntu-meta update script only
   * The only other changes are those that have been introduced in other srus.
   * s390-tools is in main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1730647/+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 1732172] Re: [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

[Hans Joachim Desserud]

** Tags added: trusty

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

Title:
  [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

Status in openssh package in Ubuntu:
  New

Bug description:
  Does anyone know when the following OpenSSH venerabilities will be
  patched on Ubuntu 14.04

  CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012,
  CVE-2016-8858

  As these are coming up repeatedly on or security scans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1732172/+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 508522] Re: Mic is not available with A2DP Bluetooth profile

[Jorge Pereira]

I'm on kubuntu 17.04 with pulseaudio 10.0, I'm still having this issue.

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

Title:
  Mic is not available with A2DP Bluetooth profile

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1731910] Re: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x0000559ef762f960 ***

[Bug Watch Updater]

** Changed in: evolution-data-server
   Status: Unknown => Fix Released

** Changed in: evolution-data-server
   Importance: Unknown => High

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

Title:
  gnome-shell-calendar-server assert failure: *** Error in `/usr/lib
  /gnome-shell/gnome-shell-calendar-server': free(): invalid pointer:
  0x559ef762f960 ***

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Committed

Bug description:
  no idea how to reproduce.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.1-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AssertionMessage: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:13:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   e_cal_component_free_datetime () at 
/usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
  Title: gnome-shell-calendar-server assert failure: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1731910/+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 1637235] Re: xorg crashes on lock screen

[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/1637235

Title:
  xorg crashes on lock screen

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I return from a locked screen, I get a the crash dialog "System
  program problem detected". The related file in /var/log crash shows
  this in the header lines:

  ProblemType: Crash
  Architecture: amd64
  Date: Thu Oct 27 10:33:08 2016
  DistroRelease: Ubuntu 16.04
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1473867446
  ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
  ProcCwd: /
  ProcEnviron: 

  It appears that the xorg instance on vt8 is crashing while starting
  the lock process; the crash file in /var/crash appears just after
  locking the screen. I have attached the xorg log from the display that
  is crashing (Xorg.1.log). There is a related output in the main
  display log (Xorg.0.log):

  [ 10248.316] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 10248.350] (II) NOUVEAU(G0): NVLeaveVT is called.
  [ 10254.968] (II) AIGLX: Resuming AIGLX clients after VT switch
  [ 10254.968] (II) intel(0): switch to mode 1920x1080@60.0 on LVDS2 using pipe 
0, position (0, 0), rotation normal, reflection none
  [ 10255.002] (II) NOUVEAU(G0): NVEnterVT is called.
  [ 10255.340] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found

  The screen locking appears to be working. VT7 is locked with a re-
  direct to VT8. I can log back in through VT8 and everything is normal,
  with the exception of the initial crash and subsequent crash dialog
  pop-up.

  Here is some relevant system information:

  Lenovo ThinkPad W520
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  lightdm:  Installed: 1.18.3-0ubuntu1
  xorg:  Installed: 1:7.7+13ubuntu3
  xserver-xorg-video-intel:  Installed: 2:2.99.917+git20160325-1ubuntu1.1
  xserver-xorg-video-nouveau:  Installed: 1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637235/+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 1731467] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1731467

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+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 1732195] Re: [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor after second monitor HDMI connected to Startech USB32HD4K

[Christopher M. Penalver]

** Summary changed:

- Mouse cursor keep flickering on primary monitor after a second monitor is 
connected via Displaylink USB3-TO-HDMI adapter
+ [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor after 
second monitor HDMI connected to Startech USB32HD4K

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

Title:
  [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor
  after second monitor HDMI connected to Startech USB32HD4K

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Alienware Alpha R2

  Primary monitor is connected to Nvidia GTX 960
  Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu 
Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu)

  If only one monitor is connected via Nvidia GTX 960, it is totally
  normal.

  If the second monitor is also connected via Startech USB32HD4K, mouse
  cursor flickers frequently and can even disappear on the PRIMARY
  monitor (the one that is connected to Nvidia GTX 960). On the second
  monitor, everything is fine.

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Tue Nov 14 23:59:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:072b]
  InstallationDate: Installed on 2017-11-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 002: ID 17e9:4301 DisplayLink
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware ASM201
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.8
  dmi.board.name: 0GWM1Y
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00:
  dmi.product.name: ASM201
  dmi.product.version: 1.0.8
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Nov 14 23:55:35 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732195/+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 1731910] Re: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x0000559ef762f960 ***

[Jeremy Bicha]

** Package changed: gnome-shell (Ubuntu) => evolution-data-server
(Ubuntu)

** Changed in: evolution-data-server (Ubuntu)
   Status: Confirmed => Fix Committed

** Bug watch added: GNOME Bug Tracker #789677
   https://bugzilla.gnome.org/show_bug.cgi?id=789677

** Also affects: evolution-data-server via
   https://bugzilla.gnome.org/show_bug.cgi?id=789677
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell-calendar-server assert failure: *** Error in `/usr/lib
  /gnome-shell/gnome-shell-calendar-server': free(): invalid pointer:
  0x559ef762f960 ***

Status in evolution-data-server:
  Unknown
Status in evolution-data-server package in Ubuntu:
  Fix Committed

Bug description:
  no idea how to reproduce.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.1-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  AssertionMessage: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:13:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
  InstallationDate: Installed on 2013-09-03 (1531 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   e_cal_component_free_datetime () at 
/usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
  Title: gnome-shell-calendar-server assert failure: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1731910/+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 1732195] Re: Mouse cursor keep flickering on primary monitor after a second monitor is connected via Displaylink USB3-TO-HDMI adapter

[Christopher M. Penalver]

Wei Cai, thank you for reporting this and helping make Ubuntu better.

In order for DisplayLink to review this issue, could you please cross post this 
to them following their instructions from:
http://support.displaylink.com/knowledgebase/articles/757047-how-can-i-report-ubuntu-issues-to-displaylink

Please provide the URL of the post to them once submitted for tracking.

** Description changed:

  Alienware Alpha R2
- Ubuntu 16.04.3 LTS
  
  Primary monitor is connected to Nvidia GTX 960
  Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu 
Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu)
  
  If only one monitor is connected via Nvidia GTX 960, it is totally
  normal.
  
  If the second monitor is also connected via Startech USB32HD4K, mouse
  cursor flickers frequently and can even disappear on the PRIMARY monitor
  (the one that is connected to Nvidia GTX 960). On the second monitor,
  everything is fine.
  
- One interesting thing I noticed is that if I set rotation in "All
- Settings"->"Screen Display" to "Clockwise", "Anti-clockwise" or "180
- degrees" (just not "Normal") on the PRIMARY monitor, this issue is
- mitigated.
+ WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
+ Clockwise
+ Anti-clockwise
+ 180 degrees
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Tue Nov 14 23:59:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:072b]
+  NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller])
+    Subsystem: Dell Device [1028:072b]
  InstallationDate: Installed on 2017-11-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
-  Bus 002 Device 002: ID 17e9:4301 DisplayLink 
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
-  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 002: ID 17e9:4301 DisplayLink
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
+  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware ASM201
  ProcEnviron:
-  LANGUAGE=en_AU:en
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_AU:en
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_AU.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.8
  dmi.board.name: 0GWM1Y
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00:
  dmi.product.name: ASM201
  dmi.product.version: 1.0.8
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Nov 14 23:55:35 2017
  xserver.configfile: default
  xserver.errors:
-  Failed to load module "nvidia" (module does not exist, 0)
-  Failed to load module "nvidia" (module does not exist, 0)
-  modeset(G0): glamor initialization failed
+  Failed to 

[Touch-packages] [Bug 1731467] Re: Cannot pair BLE remote devices when using combo BT SoC

[Kleber Sacilotto de Souza]

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

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

Title:
  Cannot pair BLE remote devices when using combo BT SoC

Status in bluez package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  New

Bug description:
  It has been observed that sometimes it is not possible to pair with
  BLE remote devices when the host system is using combo (WiFi + BT)
  chip.

  The root cause of the disconnection has been identified as coming from
  the internal to bluez timeout. If bluez does not hear any reply from for
  two seconds the link is automagically disconnected. The reason fro the
  silence is not however a failure of the remote device but quite often a
  delay in the WiFi/BT combo driver that causes the packages not to reach
  the bluez stack.

  [Impact]

  Not possible to pair BLE remote devices such as sensors and such with
  Ubuntu when the host system uses BT+WiFi combo SoC. The connection
  attempt is disturbed with a timeout.

  [Fix]

  It has been fixed by increasing the timeout value from 2 seconds to
  4 seconds. It is enough for the events to reach the stack (measured
  that it takes between 3 and 3.5 seconds).

  [Testcase]

  Tested with the device that failed to connect to Ubuntu Core gateway.
  It fails w/o the patch, it connects just fine with the patch applied.

  [Regression Potential]

  Very small. The increased timeout is taken into consideration only for
  new and scan report triggered connections. It will not make any already
  working device to fail to pair.

  [Other Info]

  The bug has been discussed and fixed here:

  https://marc.info/?l=linux-bluetooth=150824844606937=2

  [Patch]

  https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
  next.git/commit/?id=1f01d8be0e6a04bd682a55f6d50c14c1679e7571

  The patch has been accepted by the upstream and will be a part of the next
  kernel release. Currently in the bluetooth-next tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1731467/+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 1731910] [NEW] gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x0000559ef762f960 ***

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

no idea how to reproduce.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.1-0ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
AssertionMessage: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  8 10:13:10 2017
DisplayManager: gdm3
ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server
InstallationDate: Installed on 2013-09-03 (1531 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid 
pointer", ptr=, ar_ptr=) at malloc.c:5425
 _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) at 
malloc.c:4174
 __GI___libc_free (mem=) at malloc.c:3144
 e_cal_component_free_datetime () at /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19
Title: gnome-shell-calendar-server assert failure: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

** Affects: evolution-data-server (Ubuntu)
 Importance: Medium
 Status: Fix Committed


** Tags: amd64 apport-crash bionic third-party-packages
-- 
gnome-shell-calendar-server assert failure: *** Error in 
`/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 
0x559ef762f960 ***
https://bugs.launchpad.net/bugs/1731910
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to evolution-data-server in Ubuntu.

-- 
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 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel

[Amr Ibrahim]

I notice that the amd64-microcode package never gets updated in a stable
Ubuntu release.

amd microcode is part of upstream linux-firmware. Is it also shipped
inside the ubuntu linux-firmware package?

For example, this is the latest amd microcode commit upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=5f8ca0c1db6106a2d6d7e85eee778917ff03c3de

So my point is, is there a local policy to organize where the amd
microcode is going to be shipped in Ubuntu? amd64-microcode or linux-
firmware?

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

Title:
  intel-microcode should be installed by default, when the CPU is
  GenuineIntel

Status in intel:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in amd64-microcode package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released

Bug description:
  intel-microcode should be installed by default on the bare-metal
  systems which are running on GenuineIntel CPUs, by the installers.

  Similarly other microcode packages for other CPUs brands should be
  considered for inclusion (e.g. amd64-microcode).

  I hope that ubuntu-drivers-common can gain ability to detect cpu
  series and/or vendors, packages that provide microcodes similarly
  declare support for cpu series and/or vendors, the microcode packages
  are shipped on the CDs in the pool directory, and installed on to the
  target machines as part of the installation.

  This should help with rapid correction of bugs and behaviour of the
  CPUs in the field.

  2017 update, amd64-microcode should also be seeded, as it is useful to
  have it autoinstallable. In the recent years there have been critical
  CPU security vulnerabilities which got fixed with microcode updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1386257/+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 263369] Re: Save file reverts to last location used. If not available, error is displayed.

[Bug Watch Updater]

** Changed in: gimp
   Status: New => Confirmed

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

Title:
  Save file reverts to last location used. If not available, error is
  displayed.

Status in The Gimp:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Binary package hint: gimp

  If saving a file, some programs (such as GIMP and Thunderbird) will
  try to revert to the last location used when saving. If that location
  no longer exists (disk off line, path name changed, etc.), it warns
  you that it could not be found.

  Steps to reproduce:
  1) Insert USB key
  2) Create file, then save file
  3) Unmount USB key
  4) Create a new file then save file
  -ERROR- (Screenshot attached)
  "Error stating file: No such file or directory"

  What is expected: Ignore the error, do not display error to user as it
  is not productive, instead show the user's home directory as the
  default path to save if the last path used is not available.

  I will report if this happens under any other applications as well. If
  anyone has experienced this using another application please report it
  below.

  Version Information:
  Ubuntu Hardy (2.6.24-19-generic)
  gimp 2.4.5-1ubuntu2
  thunderbird 2.0.0.16+nobinonly-0ubuntu0.8.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gimp/+bug/263369/+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 1732195] [NEW] Mouse cursor keep flickering on primary monitor after a second monitor is connected via Displaylink USB3-TO-HDMI adapter

[Wei Cai]

Public bug reported:

Alienware Alpha R2
Ubuntu 16.04.3 LTS

Primary monitor is connected to Nvidia GTX 960
Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu Driver 
version 1.4.210, http://www.displaylink.com/downloads/ubuntu)

If only one monitor is connected via Nvidia GTX 960, it is totally
normal.

If the second monitor is also connected via Startech USB32HD4K, mouse
cursor flickers frequently and can even disappear on the PRIMARY monitor
(the one that is connected to Nvidia GTX 960). On the second monitor,
everything is fine.

One interesting thing I noticed is that if I set rotation in "All
Settings"->"Screen Display" to "Clockwise", "Anti-clockwise" or "180
degrees" (just not "Normal") on the PRIMARY monitor, this issue is
mitigated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
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
Date: Tue Nov 14 23:59:01 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:072b]
InstallationDate: Installed on 2017-11-14 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 002: ID 17e9:4301 DisplayLink 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Alienware ASM201
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2017
dmi.bios.vendor: Alienware
dmi.bios.version: 1.0.8
dmi.board.name: 0GWM1Y
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Alienware
dmi.chassis.version: 00
dmi.modalias: 
dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00:
dmi.product.name: ASM201
dmi.product.version: 1.0.8
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
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: Tue Nov 14 23:55:35 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: nouveau

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


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

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

Title:
  Mouse cursor keep flickering on primary monitor after a second monitor
  is connected via Displaylink USB3-TO-HDMI adapter

Status in xorg package in Ubuntu:
  New

Bug description:
  Alienware Alpha R2
  Ubuntu 16.04.3 LTS

  Primary monitor is connected to Nvidia GTX 960
  Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu 
Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu)

  If only one monitor is connected via Nvidia GTX 960, it is totally
  normal.

  If the second monitor is also connected via Startech USB32HD4K, mouse
  cursor flickers frequently and can even disappear on the PRIMARY
  monitor (the one that is connected to Nvidia GTX 960). On the second
  monitor, everything is fine.

  One interesting thing I noticed is that if I set rotation in "All
  Settings"->"Screen Display" to 

[Touch-packages] [Bug 1732182] [NEW] /lib/systemd/systemd-udevd:6:__GI_epoll_pwait:sd_event_wait:sd_event_run:sd_event_loop:run

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
234-2ubuntu12.1, the problem page at 
https://errors.ubuntu.com/problem/e1e4b6f7791262623c4db6101f6110330b56e59c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic xenial

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

Title:
  /lib/systemd/systemd-
  udevd:6:__GI_epoll_pwait:sd_event_wait:sd_event_run:sd_event_loop:run

Status in systemd package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
234-2ubuntu12.1, the problem page at 
https://errors.ubuntu.com/problem/e1e4b6f7791262623c4db6101f6110330b56e59c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732182/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => In Progress

** Changed in: hwe-next
   Status: Triaged => In Progress

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1732172] Re: [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

[Chris Collins]

The current installed version is: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8

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

Title:
  [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

Status in openssh package in Ubuntu:
  New

Bug description:
  Does anyone know when the following OpenSSH venerabilities will be
  patched on Ubuntu 14.04

  CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012,
  CVE-2016-8858

  As these are coming up repeatedly on or security scans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1732172/+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 1732172] [NEW] OpenSSH on Ubuntu 14.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Does anyone know when the following OpenSSH venerabilities will be
patched on Ubuntu 14.04

CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012,
CVE-2016-8858

As these are coming up repeatedly on or security scans

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


** Tags: bot-comment
-- 
OpenSSH on Ubuntu 14.04
https://bugs.launchpad.net/bugs/1732172
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to openssh in Ubuntu.

-- 
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 1732171] [NEW] package libperl5.24 5.24.1-2ubuntu1 [modified: usr/share/doc/libperl5.24/changelog.Debian.gz] failed to install/upgrade: intentando sobreescribir el compartido `/u

[Erica]

Public bug reported:

No se cuál es el problema, solo me largó ese error

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.10.0-38.42-lowlatency 4.10.17
Uname: Linux 4.10.0-38-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Nov 14 09:09:45 2017
ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libperl5.24/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libperl5.24:amd64
InstallationDate: Installed on 2016-10-20 (389 days ago)
InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.8
SourcePackage: perl
Title: package libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz] failed to install/upgrade: 
intentando sobreescribir el compartido 
`/usr/share/doc/libperl5.24/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libperl5.24:amd64
UpgradeStatus: Upgraded to zesty on 2017-10-01 (44 days ago)

** Affects: perl (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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1732171

Title:
  package libperl5.24 5.24.1-2ubuntu1 [modified:
  usr/share/doc/libperl5.24/changelog.Debian.gz] failed to
  install/upgrade: intentando sobreescribir el compartido
  `/usr/share/doc/libperl5.24/changelog.Debian.gz', que es distinto de
  otras instancias del paquetes libperl5.24:amd64

Status in perl package in Ubuntu:
  New

Bug description:
  No se cuál es el problema, solo me largó ese error

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.10.0-38.42-lowlatency 4.10.17
  Uname: Linux 4.10.0-38-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Nov 14 09:09:45 2017
  ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libperl5.24/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libperl5.24:amd64
  InstallationDate: Installed on 2016-10-20 (389 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.8
  SourcePackage: perl
  Title: package libperl5.24 5.24.1-2ubuntu1 [modified: 
usr/share/doc/libperl5.24/changelog.Debian.gz] failed to install/upgrade: 
intentando sobreescribir el compartido 
`/usr/share/doc/libperl5.24/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libperl5.24:amd64
  UpgradeStatus: Upgraded to zesty on 2017-10-01 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1732171/+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 1732173] [NEW] Java GUI apps do not work properly under Wayland

[Sergio Bossa]

Public bug reported:

I'm running Ubuntu 17.10 with Wayland enabled. I noticed Java GUI apps
running with native look and feel (i.e. Swing based apps with GTK look
and feel) do not properly work, i.e. fonts are not displayed properly,
windows sometimes do not draw correctly and other problems.

If I switch to X11 all works fine instead.

The Java version is:

java version "1.8.0_152"
Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 14 12:20:33 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07bf]
   Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
InstallationDate: Installed on 2017-10-24 (20 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=4f5a6ba3-2eb6-42d3-aa57-c85c628e312d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.4
dmi.board.name: 0X41RR
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  Java GUI apps do not work properly under Wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 17.10 with Wayland enabled. I noticed Java GUI apps
  running with native look and feel (i.e. Swing based apps with GTK look
  and feel) do not properly work, i.e. fonts are not displayed properly,
  windows sometimes do not draw correctly and other problems.

  If I switch to X11 all works fine instead.

  The Java version is:

  java version "1.8.0_152"
  Java(TM) SE Runtime Environment (build 1.8.0_152-b16)
  Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 12:20:33 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07bf]
 Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf]
  InstallationDate: Installed on 2017-10-24 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1732172] Re: OpenSSH on Ubuntu 14.04

[Amr Ibrahim]

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10009

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10010

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10011

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10012

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-8858

** Package changed: ubuntu => openssh (Ubuntu)

** Information type changed from Public to Public Security

** Summary changed:

- OpenSSH on Ubuntu 14.04
+ [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

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

Title:
  [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

Status in openssh package in Ubuntu:
  New

Bug description:
  Does anyone know when the following OpenSSH venerabilities will be
  patched on Ubuntu 14.04

  CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012,
  CVE-2016-8858

  As these are coming up repeatedly on or security scans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1732172/+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 388553] Re: Wi-Fi Protected Setup (WPS) not supported

[Jackalux]

Grazie mille!

Sadly, I'm a very long way from being able to handle the creation of the
GUI side... it's too many decades since I used to programme.
Respect to the coders!

On 14 November 2017 at 09:08, Daniele Napolitano 
wrote:

> This was fixed upstream with Network Manager 1.10:
> https://cgit.freedesktop.org/NetworkManager/NetworkManager/
> tree/NEWS?h=nm-1-10
>
>
> Now we need a good GUI to configure all the WPS stuff
> (gnome-control-center).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/388553
>
> Title:
>   Wi-Fi Protected Setup (WPS) not supported
>
> Status in Ayatana Design:
>   New
> Status in NetworkManager:
>   In Progress
> Status in network-manager package in Ubuntu:
>   Triaged
>
> Bug description:
>   As the title the Wi-Fi Protected Setup (WPS) is not supported by
>   NetworkManager (but is supported by wpa_supplicant).
>
>   The WPS WI-Fi standard is implementated in various newer access points
>   and allow user to configure the access point in just a few of steps
>   and do all configuring process very simple.
>
>   Specifications: http://www.wi-fi.org/wifi-protected-setup/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions
>

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

Title:
  Wi-Fi Protected Setup (WPS) not supported

Status in Ayatana Design:
  New
Status in NetworkManager:
  In Progress
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  As the title the Wi-Fi Protected Setup (WPS) is not supported by
  NetworkManager (but is supported by wpa_supplicant).

  The WPS WI-Fi standard is implementated in various newer access points
  and allow user to configure the access point in just a few of steps
  and do all configuring process very simple.

  Specifications: http://www.wi-fi.org/wifi-protected-setup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1732151] [NEW] [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all

[Rafael Gonzaga]

Public bug reported:

That's the second time i wanted to use Ubuntu and had the same issue.
This is a fresh installation and I didn't install nothing related to
sound.

ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: alsa-base 1.0.25+dfsg-0ubuntu5 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rchgonzaga   1613 F pulseaudio
CurrentDesktop: Pantheon
Date: Tue Nov 14 08:36:00 2017
InstallationDate: Installed on 2017-11-12 (1 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rchgonzaga   1613 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.1
dmi.board.name: 09WC1G
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd02/14/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 7460
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug loki third-party-packages

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

Title:
  [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  That's the second time i wanted to use Ubuntu and had the same issue.
  This is a fresh installation and I didn't install nothing related to
  sound.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: alsa-base 1.0.25+dfsg-0ubuntu5 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rchgonzaga   1613 F pulseaudio
  CurrentDesktop: Pantheon
  Date: Tue Nov 14 08:36:00 2017
  InstallationDate: Installed on 2017-11-12 (1 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rchgonzaga   1613 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd02/14/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7460
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1732151/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

[Nafallo Bjälevik]

Any progress in seeing this fixed in Xenial?

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Incomplete
Status in wpa package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in ubiquity source package in Xenial:
  Confirmed
Status in wpa source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Users booting from OEM setup may find that their wireless device is "not 
ready" as per NetworkManager, because wpasupplicant is not running. This is 
because the steps taken to start in OEM prepare, before moving to the real 
system runs systemctl isolate, and wpasupplicant gets caught in the crossfire.

  
  [Test case]
  * Steps to reproduce:
  1. Install in OEM mode
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  
  [Regression potential]
  The following are examples of possible regression scenarios from this stable 
update:
  - Failure to get the wireless device ready at session start
  - Driver loading issues for the wireless devices
  - Failure to complete OEM preparation steps, due to the oem user remaining 
connected while it's being removed by the last steps of the OEM preparation 
process.

  
  [Background information]
  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1732116] [NEW] HDMI device is not working / not found

[Roland Lohninger]

Public bug reported:

after conecting TV over HDMI, Ubuntu doenst find the external display

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Nov 14 10:29:17 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec]
InstallationDate: Installed on 2017-09-10 (64 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Hewlett-Packard HP EliteBook 8730w
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=95c3f524-8551-407a-91a0-65632f3854b3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PAD Ver. F.13
dmi.board.name: 30EC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.25
dmi.chassis.asset.tag: CNU911000L
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8730w
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
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: Tue Nov 14 09:58:47 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: nouveau

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


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

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

Title:
  HDMI  device is not working / not found

Status in xorg package in Ubuntu:
  New

Bug description:
  after conecting TV over HDMI, Ubuntu doenst find the external display

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 14 10:29:17 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec]
  InstallationDate: Installed on 2017-09-10 (64 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 8730w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=95c3f524-8551-407a-91a0-65632f3854b3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.13
  dmi.board.name: 30EC
  

[Touch-packages] [Bug 1732113] [NEW] [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal] No sound at all

[Roland Lohninger]

Public bug reported:

no sound at all

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D1p:   l  1719 F...m pulseaudio
 /dev/snd/pcmC0D0c:   l  1719 F...m pulseaudio
 /dev/snd/controlC0:  l  1719 F pulseaudio
  l  2727 F alsamixer
CurrentDesktop: Unity
Date: Tue Nov 14 10:17:50 2017
InstallationDate: Installed on 2017-09-10 (64 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Internes Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D1p:   l  1719 F...m pulseaudio
 /dev/snd/pcmC0D0c:   l  1719 F...m pulseaudio
 /dev/snd/controlC0:  l  1719 F pulseaudio
  l  2727 F alsamixer
Symptom_Jack: Green Speaker, Internal
Symptom_Type: No sound at all
Title: [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PAD Ver. F.13
dmi.board.name: 30EC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.25
dmi.chassis.asset.tag: CNU911000L
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8730w
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  no sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   l  1719 F...m pulseaudio
   /dev/snd/pcmC0D0c:   l  1719 F...m pulseaudio
   /dev/snd/controlC0:  l  1719 F pulseaudio
l  2727 F alsamixer
  CurrentDesktop: Unity
  Date: Tue Nov 14 10:17:50 2017
  InstallationDate: Installed on 2017-09-10 (64 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internes Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   l  1719 F...m pulseaudio
   /dev/snd/pcmC0D0c:   l  1719 F...m pulseaudio
   /dev/snd/controlC0:  l  1719 F pulseaudio
l  2727 F alsamixer
  Symptom_Jack: Green Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.13
  dmi.board.name: 30EC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.25
  dmi.chassis.asset.tag: CNU911000L
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8730w
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1732113/+subscriptions

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

[Touch-packages] [Bug 388553] Re: Wi-Fi Protected Setup (WPS) not supported

[Daniele Napolitano]

This was fixed upstream with Network Manager 1.10:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-10


Now we need a good GUI to configure all the WPS stuff (gnome-control-center).

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

Title:
  Wi-Fi Protected Setup (WPS) not supported

Status in Ayatana Design:
  New
Status in NetworkManager:
  In Progress
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  As the title the Wi-Fi Protected Setup (WPS) is not supported by
  NetworkManager (but is supported by wpa_supplicant).

  The WPS WI-Fi standard is implementated in various newer access points
  and allow user to configure the access point in just a few of steps
  and do all configuring process very simple.

  Specifications: http://www.wi-fi.org/wifi-protected-setup/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1582986] Re: NetworkManager service does not start during bootup

[Launchpad Bug Tracker]

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

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nfs-utils (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/1582986

Title:
  NetworkManager service does not start during bootup

Status in network-manager package in Ubuntu:
  Confirmed
Status in nfs-utils package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 4.4.0-22
  systemd 229-4
  network-manager 1.1.93
  network-manager-gnome 1.2.0

  Multiple services and targets are deleted by systemd to "break
  ordering cycle" (cf. boot.log), but NetworkManager is the only one of
  them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote-
  fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective
  logs) which is not started after bootup:

  sudo systemctl status NetworkManager.service
  ● NetworkManager.service - Network Manager
 Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; 
vendor preset: enabled)
 Active: inactive (dead)

  May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job
  NetworkManager.service/verify-active deleted to break ordering cycle
  starting with network.target/start

  Attachments:
  ---
  - journalctl -l -b0 --system _COMM=systemd > boot.log
  - systemctl -l status rpcbind  > rpcbind.log
  - systemctl -l status network.target  > network.target.txt
  - systemctl -l status remote-fs-pre.target  > remote-fs-pre.target.log
  - systemctl -l status sysinit.target  > sysinit.target.log
  - systemctl -l status zfs-fuse.service  > zfs-fuse.service.log
  - systemctl -l status open-iscsi.service  > open-iscsi.service.log
  - systemctl -l status iscsid.service  > iscsid.service.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

[Gunnar Hjalmarsson]

@Magezi: Please note that this is a bug report, not a support forum.
This Ask Ubuntu question may help:

https://askubuntu.com/q/915415

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  Fix Released

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

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