[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

[Michael Gratton]

Err, I mean "dnsmasq's 127.0.1.1"

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

Title:
  Name resolution stops working after resume from suspend

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1631241/+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 1631241] Re: Name resolution stops working after resume from suspend

[Michael Gratton]

Well I'm posting this from the computer with the problem, so yes I'm
online. :)

To fix the problem I need to manually edit /etc/resolv.conf and replace
dnsmasq's 127.0.0.1 with resolve's 127.0.0.53 (or any other reachable
name server).

> mjg@payens:~$ nmcli g
> STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
> connected  full  enabled  enabled  enabled  enabled 
> mjg@payens:~$ dig A www.ubuntu.com @8.8.8.8
> 
> ; <<>> DiG 9.10.3-P4-Ubuntu <<>> A www.ubuntu.com @8.8.8.8
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16454
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 512
> ;; QUESTION SECTION:
> ;www.ubuntu.com.  IN  A
> 
> ;; ANSWER SECTION:
> www.ubuntu.com.   164 IN  A   91.189.90.58
> 
> ;; Query time: 6 msec
> ;; SERVER: 8.8.8.8#53(8.8.8.8)
> ;; WHEN: Fri Oct 07 17:51:58 AEDT 2016
> ;; MSG SIZE  rcvd: 59

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

Title:
  Name resolution stops working after resume from suspend

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1631241/+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 57091] Re: proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to permit SYN flood defense...

[Simon Iremonger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

> Bog standard 16.04 has it turned on (from the above referenced 10
> -network-security.conf).
> But, if you then enabled ufw, it gets disabled, due to the default
> setting in /etc/ufw/sysctl.conf.

> There seems to be serious debate as to whether or not enabling it is
> correct.

I haven't seen why not to enable use of adaptive syncookies, aiui
this creates no _disadvantage_ if not being triggered...

I CAN understand that for some scenarios the 'right thing to do'
is Increase the tcp_max_syn_backlog as cookies are triggering too
easily, even then it won't stop connections being accepted albeit
with less tcp options possible, but then without syncookies
the connections would be dropped as the syn queue fills...

> What I know is that I just spent two hours trying to figure out why SANE 
> took forever to detect my network scanner, and this syslog entry clued 
> me in:
> Oct  6 22:54:26 hiro kernel: [48562.817258] TCP: request_sock_TCP:
> Possible SYN flooding on port 34029. Dropping request.  Check SNMP
> The dropped request was responsible for the delay. If I enable syn
> cookies, I get:
> Oct  6 22:57:28 hiro kernel: [48744.796029] TCP: request_sock_TCP:
> Possible SYN flooding on port 42041. Sending cookies.  Check SNMP
> capture it, there's ONE SYN request and the kernel thinks it's a
> "flood".. which makes no sense.

Weird :).
I can't say I'm familiar with uwf, but I wonder if it is somehow
oversensitive in its' own ip(6)tables or they are fiddling with:-

/proc/sys/net/ipv4/tcp_max_syn_backlog


Do raise bug in the ufw // ufw sysctl.conf   Also email me 
separately the relevant bug numbers etc., be curious to see!!

- --Simon
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Topal (http://freshmeat.net/projects/topal)

iF4EAREIAAYFAlf3SqEACgkQA62i3HuJ2aHNCwEAnK4NvLNm/tKHzFNSEK+KRNMB
6hZOZ6tcnbecljP1+dAA/3C0bmEHFXEzeLF3xYNSco+py2TbD2bNPzXbG0NKsupb
=Fh0+
-END PGP SIGNATURE-

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

Title:
  proc/sys/net/ipv4/tcp_syncookies=1 should be seriously considered to
  permit SYN flood defense...

Status in procps package in Ubuntu:
  Fix Released

Bug description:
  This is intended to be a 'wishlist' wulnerability -- w.r.t. procps and
  Edgy.

  In my opinion,the /etc/sysctl.conf should have
  'proc/sys/net/ipv4/tcp_syncookies=1' in order to permit the linux
  SYNcookies syn-flood trivial DoS attack to be mitigated as-necessary,
  by default.

  Note that the disadvantages of connections initiated w/ SYNcookies
  enabled only apply when the system is under attack (SYN queue getting
  rather full), as the syncookies reply-with-only-one-SYN+ACK behaviour
  only 'kicks in' when the system has a SYN_RECVD backlog problem.  (If
  SYNcookies were not permitted incoming TCP connections have a very low
  chance of succeeding at all while under SYN-flood attack).

  Without this setting enabled, any TCP services on the machine can be
  DoSed from a dial-up line sending a stream of SYN packets from weird
  source addresses to open TCP ports like Samba/VNC/http/whatever

  
  Does anybody have any legitimate reason tcp_syncookies should be disabled?

  Some people claimed that SYNcookies break some RFCs once but I have
  not seen any evidence to this effect, only notes from djb saying that
  this is not true.

  Comments wanted please ;-)
  Thankyou in advance,
  -- enyc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/57091/+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 1631172] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paweł Stołowski]

Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
Traceback (most recent call last):
  File "/usr/bin/click", line 55, in 
from click import commands
ImportError: cannot import name 'commands'
dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1

It looks like click failed, perhaps click and/or its dependencies needs
upgrading. In any case, libunity-scopes package is innocent here.

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

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => Invalid

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in click package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  Invalid

Bug description:
  appears upon logging in

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 19:25:54 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-07-01 (96 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-04 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1631172/+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 1631288] [NEW] XV video screen always on top

[dabrain]

Public bug reported:

When playing a video with vlc, gstreamer(xvimagesink), the video stays on top 
of every X window.
In VLC this bug can be bypassed disabling overlay video. 
In Gstreamer using ximagsink is ok too.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Oct  7 09:45:31 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Toshiba America Info Systems Skylake Integrated Graphics 
[1179:001d]
   Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d]
InstallationDate: Installed on 2016-10-03 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
MachineType: TOSHIBA TECRA Z50-C
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2016
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 5.70
dmi.board.asset.tag: 00
dmi.board.name: TECRA Z50-C
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA Z50-C
dmi.product.version: PT577E-01100GCE
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.68-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Oct  6 17:44:07 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1237 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.1

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages 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/1631288

Title:
  XV video screen always on top

Status in xorg package in Ubuntu:
  New

Bug description:
  When playing a video with vlc, gstreamer(xvimagesink), the video stays on top 
of every X window.
  In VLC this bug can be bypassed disabling overlay video. 
  In Gstreamer using ximagsink is ok too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 09:45:31 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Gr

[Touch-packages] [Bug 1625877] Re: VLC screen always on top

[dabrain]

Here is the new bug created with ubuntu-bug xorg

Hope it will help.

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

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

Title:
  VLC screen always on top

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  After new installed VLC on 16.04
  The video screen always on top only while playing with VLC

  the interface disappeared while minimum VLC (video playing)
  video screen remains only

  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"

  in Preference > Video > Display

  Reference:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  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: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
  InstallationDate: Installed on 2016-09-01 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: SY Series
  dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: SY Series
  dmi.product.version: Not Applicable
  dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 20 22:21:24 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1191
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625877/+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 1628790] Re: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop

[Joel]

Lubuntu version is 16.04.1 (with latest stable updates) LightDM version 
1.18.20ubuntu2. lightdm-gtk-greeter is 2.0.1-2ubuntu4.
I'll check out the permissions later and get back to you.

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

Title:
  Changing the user settings to autologin on Lubuntu 16.04 causes
  LightDM to get stuck in a login loop

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  After setting my account to login automatically through the user and
  groups setting in Lubuntu. After the computer reboots it gets stuck in
  a loop on the login screen. Logging in will just send you back to the
  same screen.

  The only way I could fix the issue was to press CRTL + ALT + F1, logging in 
through the CLI and typing:
  "sudo mv .Xauthority .Xauthority.bak"
  and then once I was back to the login screen I was able to login and turn the 
setting off. 

  I did check to see weather that was what caused it, by restarting the
  computer without turning off the auto-login. However the same issue
  happened and only turning off auto-login would stop the login loop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1628790/+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 1631288] Re: XV video screen always on top

[Christopher M. Penalver]

** Tags added: bios-outdated-7.40

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

Title:
  XV video screen always on top

Status in xorg package in Ubuntu:
  New

Bug description:
  When playing a video with vlc, gstreamer(xvimagesink), the video stays on top 
of every X window.
  In VLC this bug can be bypassed disabling overlay video. 
  In Gstreamer using ximagsink is ok too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 09:45:31 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Toshiba America Info Systems Skylake Integrated Graphics 
[1179:001d]
 Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d]
  InstallationDate: Installed on 2016-10-03 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: TOSHIBA TECRA Z50-C
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.70
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z50-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z50-C
  dmi.product.version: PT577E-01100GCE
  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.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct  6 17:44:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1237 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1623666] Re: iOS10 will not connect to Ubuntu

[per]

Sorry for the miss-understanding I slip on the keyboard last night it was dark 
when I change the status
Changed in libimobiledevice (Ubuntu):
status: Confirmed → Fix Committed
status: Fix Committed → Confirmed 

Ignore this Sorry / Per

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

Title:
  iOS10 will not connect to Ubuntu

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1623198] [NEW] Masking and then disabling dbus.service causes the system to freeze

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using Ubuntu 16.10 dev with systemd-sysv 231-6 and if I'm executing
the command "systemctl mask dbus.service" and then "systemctl stop
dbus.service" the system does freeze after a few seconds (even switching
to the console is not possible anymore). But booting then the system
works fine without any freezes while dbus got successfully disabled.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Won't Fix

-- 
Masking and then disabling dbus.service causes the system to freeze
https://bugs.launchpad.net/bugs/1623198
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1595963] Re: vt1-6 getting stuck or blank

[Jesper Noer]

After a fresh reboot it was working fine, but today after the laptop has
been suspended the tty is just blank. I usually use the KDE desktop, so
I'm just switching to a tty from time to time. Not sure if there is a
connection between suspending and blank screen, but it is possible.

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

Title:
  vt1-6 getting stuck or blank

Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  It's happening from time to time that my vt1-6 are getting stuck
  (showing tty1 and no input) or blank (just black) completely.

  Restarting system-getty.slice or console-getty.slice doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 24 10:00:54 2016
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 12-9Q33
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: systemd 229-4ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=ZFS=/root ro root=ZFS=username-laptop/root quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1595963/+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 1624571] Re: White lines visible around LibreOffice toolbars in when using GTK3

[Martin Wimpress]

** Summary changed:

- White lines visible around toolbars in LibreOffice when using GTK3 and a dark 
theme
+ White lines visible around LibreOffice toolbars in when using GTK3

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

Title:
  White lines visible around LibreOffice toolbars in when using GTK3

Status in ubuntu-mate:
  Triaged
Status in libreoffice package in Ubuntu:
  Triaged
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  There are some portions where the theme is not consistent like on the right 
side "x" and so on.
  In the pictures you will see a comparation side by side with UBUNTU Mate 
16.04 with Mate 1.14 gtk2 ppa
  The top bar from the picture it's from 16.10 and the next bar it's from 16.04

  OS: Ubuntu 16.10 daily
  Interface : Mate 1.15.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1623198] Re: Masking and then disabling dbus.service causes the system to freeze

[Sworddragon]

No, switching to the console for example with CTRL + ALT + F1 doesn't
work anymore (and the freeze causes also that constantly the last frame
before the freeze is shown).

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

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

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

Title:
  Masking and then disabling dbus.service causes the system to freeze

Status in dbus package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I'm using Ubuntu 16.10 dev with systemd-sysv 231-6 and if I'm
  executing the command "systemctl mask dbus.service" and then
  "systemctl stop dbus.service" the system does freeze after a few
  seconds (even switching to the console is not possible anymore). But
  booting then the system works fine without any freezes while dbus got
  successfully disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1623198/+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 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

[David DIDIER]

See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622005/comments/9

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

Title:
  [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep 13 21:49:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 13 21:14:29 2016
  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)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623173/+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 1631288] Re: XV video screen always on top

[Christopher M. Penalver]

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

To clarify:
1) Did this issue start after an update?
2) Did this issue occur in a Ubuntu release prior to 16.04?
3) To see if this is resolved in Ubuntu, could you please test 
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? 

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  XV video screen always on top

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When playing a video with vlc, gstreamer(xvimagesink), the video stays on top 
of every X window.
  In VLC this bug can be bypassed disabling overlay video. 
  In Gstreamer using ximagsink is ok too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 09:45:31 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Toshiba America Info Systems Skylake Integrated Graphics 
[1179:001d]
 Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d]
  InstallationDate: Installed on 2016-10-03 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: TOSHIBA TECRA Z50-C
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.70
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z50-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z50-C
  dmi.product.version: PT577E-01100GCE
  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.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct  6 17:44:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1237 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1624571] Re: White lines visible around LibreOffice toolbars in when using GTK3

[Iain Lane]

** Branch linked: lp:~flexiondotorg/ubuntu-themes/lp1624571

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

Title:
  White lines visible around LibreOffice toolbars in when using GTK3

Status in ubuntu-mate:
  Triaged
Status in libreoffice package in Ubuntu:
  Triaged
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  There are some portions where the theme is not consistent like on the right 
side "x" and so on.
  In the pictures you will see a comparation side by side with UBUNTU Mate 
16.04 with Mate 1.14 gtk2 ppa
  The top bar from the picture it's from 16.10 and the next bar it's from 16.04

  OS: Ubuntu 16.10 daily
  Interface : Mate 1.15.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1631288] Re: XV video screen always on top

[dabrain]

Christorpher, first thank you for your concern.

1) I just buy this computer and the previous releases were not correctly 
working whith the hardware that's why i chose this release and test it only.
2) I did not have time to test this issue seen that i was facing other HW issue 
such as network.
3) I will perform a test ASAP.

Steph

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

Title:
  XV video screen always on top

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When playing a video with vlc, gstreamer(xvimagesink), the video stays on top 
of every X window.
  In VLC this bug can be bypassed disabling overlay video. 
  In Gstreamer using ximagsink is ok too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct  7 09:45:31 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Toshiba America Info Systems Skylake Integrated Graphics 
[1179:001d]
 Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d]
  InstallationDate: Installed on 2016-10-03 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: TOSHIBA TECRA Z50-C
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 5.70
  dmi.board.asset.tag: 00
  dmi.board.name: TECRA Z50-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA Z50-C
  dmi.product.version: PT577E-01100GCE
  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.68-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Oct  6 17:44:07 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1237 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1624738] Re: Firefox search and location boxes have black borders when unselected

[Martin Wimpress]

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-mate-artwork (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

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

Title:
  Firefox search and location boxes have black borders when unselected

Status in ubuntu-mate-artwork package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  As seen in the attached screen shot the borders around Firefox
  location and search entry boxes are black when unselected but they
  should be grey.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1624738/+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 1624738] Re: Firefox search and location boxes have black borders when unselected

[Martin Wimpress]

The border colour can be set with:

frame {
border-width: 1px;
border-style: solid;
border-color: shade (@bg_color, 0.82);
}

But 'frame' is used widely in many applications which results in borders
being rendered where you really don't want them. The following will
style Firefox and then override that styling where it is not required.
I've tested most default applications in Ubuntu and the following
appears to work well, more testing would be good.

/* Style frame for firefox to set the search/location entry box borders*/
frame {
border-width: 1px;
border-style: solid;
border-color: shade (@bg_color, 0.82);
}

/* Override frame styling set for firefox to prevent erroneous frames being 
rendered */
box > frame, /* common in settings panels */
statusbar > frame, /* common in application status bars, etc. */
statusbar > widget > frame, /* common in application status bars, etc. */
GvcMixerDialog frame { /* some audio mixers */
border-width: 0px;
border-style: none;
}

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

Title:
  Firefox search and location boxes have black borders when unselected

Status in ubuntu-mate-artwork package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  As seen in the attached screen shot the borders around Firefox
  location and search entry boxes are black when unselected but they
  should be grey.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1624738/+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 1630969] Re: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 5

[Launchpad Bug Tracker]

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

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

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

Title:
  package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 5

Status in android-tools package in Ubuntu:
  Confirmed

Bug description:
  that package is not upgadable, that is all i can say, sorry)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Oct  6 04:03:47 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 5
  InstallationDate: Installed on 2016-09-23 (13 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160726)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: android-tools
  Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu4 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 5
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1630969/+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 1542029] Re: New windows have incorrect dimensions on launch (not the dimensions the app specifies)

[Michael Zanetti]

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

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

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

Title:
  New windows have incorrect dimensions on launch (not the dimensions
  the app specifies)

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Ubuntu UX:
  Invalid
Status in miral package in Ubuntu:
  New
Status in puritine package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  currently, the shell is picking some random window size.
  They are about to change it to be close to what is on the phone - as this 
will match most apps.
  however the Xapps should have something "larger"

  shell is landing the ability to communicate to it, the desire default
  first launch window size

  it would also be good to have design input on this selection

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542029/+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 1524376] Re: One site started giving standard "Network error" on a single phone

[Chris Coulson]

There's not much point in keeping this bug open (see my last comment),
so I'm going to close it for now. Feel free to reopen if you this might
be a bug in Oxide

** Changed in: oxide
   Status: New => Invalid

** No longer affects: webbrowser-app (Ubuntu)

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

Title:
  One site started giving standard "Network error" on a single phone

Status in Oxide:
  Invalid

Bug description:
  Browsing to http://www.uusisuomi.fi/ now gives me a standard Network
  Error immediately instead of loading. This only happens for this
  single site, and only in my daily use Bq using stable OTA-8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1524376/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~daniel-thewatkins/cloud-init/+git/cloud-init/+merge/307927

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in dbus package in Ubuntu:
  Triaged

Bug description:
  During boot, cloud-init does DNS resolution checks to if particular
  metadata services are available (in order to determine which cloud it
  is running on).  These checks happen before systemd-resolved is up[0]
  and if they resolve unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1630510] Re: webbrowser-app crashed with SIGSEGV in QNetworkSession::~QNetworkSession()

[Timo Jyrinki]

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

** This bug has been marked a duplicate of bug 1630765
   webbrowser-app crashed with SIGSEGV in 
QNetworkConfiguration::~QNetworkConfiguration()

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

Title:
  webbrowser-app crashed with SIGSEGV in
  QNetworkSession::~QNetworkSession()

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Crash on close

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: webbrowser-app 0.23+16.10.20160928-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 20:49:26 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-08-14 (51 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160813)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   QNetworkSession::~QNetworkSession() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QNetworkSession::~QNetworkSession() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QApplicationPrivate::notify_helper(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
   QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  Title: webbrowser-app crashed with SIGSEGV in 
QNetworkSession::~QNetworkSession()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630510/+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 1610499] Re: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group

[Jochen]

** Package changed: alsa-driver (Ubuntu) => procps (Ubuntu)

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

Title:
  hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process
  group

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499/+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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[asier urbina]

Hello all,

I am getting the same problem.
I use BQ Aquaris E4.5 and my car is Seat Altea XL 2010 version.
The phone finds the car bluetooth, I can connect to it, I get the PIN request, 
and the device gets paired. Even the bluetooth icon changes its colour to white.
But when i try to make a call, or to access the contacts, the connection goes 
down.

I would like to tell that for me it is really frustrating to see how the 
problems with the bluetooth system are going from one OTA to the following, or 
worse in this case that it is being redirected to backlog, without being solved.
In my case it is very important to connect the phone with the car, as i haveto 
drive long distances and need to make or recieve calls for work purposes.

Thank you for your support and work.
Best regards.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+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 1631241] Re: Name resolution stops working after resume from suspend

[Martin Pitt]

> To fix the problem

Please tell us what actually *is* the problem.

> I need to manually edit /etc/resolv.conf and replace dnsmasq's
127.0.0.1 with resolve's 127.0.0.53

So are you trying to not use NM's dnsmasq instance because that stops
working after suspend/resume?

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

Title:
  Name resolution stops working after resume from suspend

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1631241/+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 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image

[Alexandros Frantzis]

** Also affects: ubuntu-touch-session (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-touch-session (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-touch-session (Ubuntu)
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

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

Title:
  Device appears to be off after updating to 15Sept2016's rc-proposed
  image

Status in Canonical System Image:
  Confirmed
Status in repowerd package in Ubuntu:
  Confirmed
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  Krillin, rc-proposed/bq-aquaris.en r429

  Description:
  Many people, myself included, are reporting that their devices seemed to have 
turned off after upgrading to today's rc-proposed

  In my case it was an updated from r428 to r429.
  The device rebooted to install the upgrade, then at one point I noticed the 
display was off and not responding to PwrKey.
  I had for force shutdown via press-holding PwrKey.

  A few community members reported the same problem on Arale (MX4) and
  Freiza (M10), so it seems to be device-independent.

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

[Launchpad Bug Tracker]

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

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

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

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

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  The update did not install. Maybe because the net got disconnected in
  between ???

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   ntp: Install
   ntpdate: Install
   ntp: Configure
   ntpdate: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Aug 26 19:39:18 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-26  19:36:04
   Commandline: aptdaemon role='role-commit-packages' sender=':1.65'
   Upgrade: ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1), 
ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5, 1:4.2.8p4+dfsg-3ubuntu5.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-28 (151 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=790d64f7-9847-4d8c-bbaa-3c87b8aaac16 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1617341/+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 1623198] Re: Masking and then disabling dbus.service causes the system to freeze

[Martin Pitt]

** Changed in: dbus (Ubuntu)
   Status: New => Won't Fix

** No longer affects: systemd (Ubuntu)

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

Title:
  Masking and then disabling dbus.service causes the system to freeze

Status in dbus package in Ubuntu:
  Won't Fix

Bug description:
  I'm using Ubuntu 16.10 dev with systemd-sysv 231-6 and if I'm
  executing the command "systemctl mask dbus.service" and then
  "systemctl stop dbus.service" the system does freeze after a few
  seconds (even switching to the console is not possible anymore). But
  booting then the system works fine without any freezes while dbus got
  successfully disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1623198/+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 1631346] [NEW] spurious colord authentication request for remote session

[Pierre Ossman (Cendio AB)]

Public bug reported:

Remote sessions get nagged with polkit authentication requests, despite
no action from the user.

This has already been reported upstream:

https://bugzilla.gnome.org/show_bug.cgi?id=751775
https://github.com/hughsie/colord/issues/16
https://bugs.kde.org/show_bug.cgi?id=357247

However it still needs to be fixed in current versions in Ubuntu,
especially the latest LTS release.

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


** Tags: xenial

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

Title:
  spurious colord authentication request for remote session

Status in colord package in Ubuntu:
  New

Bug description:
  Remote sessions get nagged with polkit authentication requests,
  despite no action from the user.

  This has already been reported upstream:

  https://bugzilla.gnome.org/show_bug.cgi?id=751775
  https://github.com/hughsie/colord/issues/16
  https://bugs.kde.org/show_bug.cgi?id=357247

  However it still needs to be fixed in current versions in Ubuntu,
  especially the latest LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1631346/+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 1631241] Re: Name resolution stops working after resume from suspend

[Michael Gratton]

On Fri, Oct 7, 2016 at 10:44 PM, Martin Pitt  
wrote:
>>  To fix the problem
> 
> Please tell us what actually *is* the problem.

My apologies, I should have said "To work around the problem" in the 
last comment.

>>  I need to manually edit /etc/resolv.conf and replace dnsmasq's
> 127.0.0.1 with resolve's 127.0.0.53
> 
> So are you trying to not use NM's dnsmasq instance because that stops
> working after suspend/resume?

It looks like it, yes. As I (obliquely) mentioned in comment 3, dnsmasq 
seems to stop responding to UDP requests on 127.0.0.1 after resume.

-- 
⊨ Michael Gratton, Percept Wrangler.
⚙ 

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

Title:
  Name resolution stops working after resume from suspend

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1631241/+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 1631003] Re: OSK is slow to appear the first time

[Bill Filler]

** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

** Changed in: ubuntu-keyboard (Ubuntu)
   Importance: Undecided => High

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

Title:
  OSK is slow to appear the first time

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  If you boot a phone and go to log in at the passcode entry, you may
  have to wait a few seconds for the OSK to appear.

  This is partially because (A) the OSK takes a while to start and (B)
  we only start maliit-server *after* unity8 starts.

  Can we fix either A or B?

  B seems to be because the OSK assumes u8 and its Mir server already
  exists, but could we fix the OSK to wait for u8 to appear?

  Or just make maliit/OSK faster?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1631003/+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 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"

[James Page]

Not a charm bug - marking invalid.

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

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

Title:
  ceph-osd stays blocked on Yakkety: "No block devices detected using
  current configuration"

Status in ceph package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in ceph-osd package in Juju Charms Collection:
  Invalid

Bug description:
  The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo
  specs @ Yakkety are failing like so:

  Units are consistently blocked in Juju status:
  ceph-osd stays blocked on Yakkety: "No block devices detected using current 
configuration"

  Snippets from ceph-osd unit syslog:
  mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: 
(13) Permission denied

  Oct  7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start
  Ceph disk activation: /dev/vdb1.

  See:

  http://pastebin.ubuntu.com/23288515/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+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 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"

[James Page]

** Changed in: ceph (Ubuntu)
   Status: New => Triaged

** Changed in: ceph (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  ceph-osd stays blocked on Yakkety: "No block devices detected using
  current configuration"

Status in ceph package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in ceph-osd package in Juju Charms Collection:
  Invalid

Bug description:
  The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo
  specs @ Yakkety are failing like so:

  Units are consistently blocked in Juju status:
  ceph-osd stays blocked on Yakkety: "No block devices detected using current 
configuration"

  Snippets from ceph-osd unit syslog:
  mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: 
(13) Permission denied

  Oct  7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start
  Ceph disk activation: /dev/vdb1.

  See:

  http://pastebin.ubuntu.com/23288515/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+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 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"

[Martin Pitt]

> This is a little chicken and egg - the ceph-common package configures
the ceph/ceph user/group, however udev notices the new rule file prior
to that happening

udev uses inotify to pick up the new rule, but in order to actually
"run" the rule the handled device must either be removed and added or
udevadm trigger'ed (like in comment #8). So the postinst shold do that
after creating the groups.

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

Title:
  ceph-osd stays blocked on Yakkety: "No block devices detected using
  current configuration"

Status in ceph package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in ceph-osd package in Juju Charms Collection:
  Invalid

Bug description:
  The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo
  specs @ Yakkety are failing like so:

  Units are consistently blocked in Juju status:
  ceph-osd stays blocked on Yakkety: "No block devices detected using current 
configuration"

  Snippets from ceph-osd unit syslog:
  mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: 
(13) Permission denied

  Oct  7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start
  Ceph disk activation: /dev/vdb1.

  See:

  http://pastebin.ubuntu.com/23288515/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+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 1631241] Re: Name resolution stops working after resume from suspend

[Martin Pitt]

OK. This could be because NM does not feed it with correct DNS data, or
dnsmasq itself gets confused after resuming. Assigning to NetworkManager
for now.

** Package changed: systemd (Ubuntu) => network-manager (Ubuntu)

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

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

Title:
  Name resolution stops working after resume from suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+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 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image

[Alexandros Frantzis]

** Branch linked: lp:~afrantzis/ubuntu-touch-session/keep-display-on-
during-boot

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

Title:
  Device appears to be off after updating to 15Sept2016's rc-proposed
  image

Status in Canonical System Image:
  Confirmed
Status in repowerd package in Ubuntu:
  Confirmed
Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  Krillin, rc-proposed/bq-aquaris.en r429

  Description:
  Many people, myself included, are reporting that their devices seemed to have 
turned off after upgrading to today's rc-proposed

  In my case it was an updated from r428 to r429.
  The device rebooted to install the upgrade, then at one point I noticed the 
display was off and not responding to PwrKey.
  I had for force shutdown via press-holding PwrKey.

  A few community members reported the same problem on Arale (MX4) and
  Freiza (M10), so it seems to be device-independent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Jamie Strandboge]

im-config 0.29-1ubuntu12.2 is uploaded to xenial-proposed and ensures
the newer apparmor is installed. Please see the updated description for
im-config in Test Case and Regression Potential for details.

** Description changed:

  IMPORTANT: SRU Team, see comment #25 for why this bug is temporarily
  marked verification-failed
  
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.
  
  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.
  
  [Test Case]
  1. start a unity session before updating to the package in -proposed
  
  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76
  
  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM
  
  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before
  
  5. logout of unity, then log back in
  
  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e
  
  (notice '/tmp/ibus/' in the path)
  
  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...
  
  (notice '@/tmp/ibus/' in the path)
  
  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting 'Text
  Entry'. From there, add an input source on the right, make sure 'Show
  current input source in the menu bar' is checked, then use the input
  source panel indicator to change input sources.
  
+ 
+ Extended test case to verify input support still works in unconfined and 
confined applications:
+ 
+ 1. Systems Settings Language Support, if prompted install the complete 
language support
+ 2. Install Chinese (simple and traditional)
+ 3. sudo apt-get install ibus-pinyin ibus-sunpinyin
+ 4. logout / login
+ 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
+ 6. select pinyin from the indicator
+ 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
+ 8. open gnome-calculator and try to type something in (should get a pop-up)
+ 9. open evince and try to search a pdf (should get a pop up)
+ 10. upgrade apparmor and im-config from xenial-proposed
+ 11. logout and back in
+ 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
+ 13. open gnome-calculator and try to type something in (should get a pop-up)
+ 14. open evince and try to search a pdf (should get a pop up)
+ 15. verify no new apparmor denials
+ 
+ 
  [Regression Potential]
  
  The regression potential is considered low because there are no compiled
  code changes and because the changes only occur after ibus-daemon is
  restarted, which is upon session start, not package upgrade. When it is
  restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated
  accordingly for other applications to pick up.
  
  This change intentionally requires a change to the unity7 snapd
- interface, which is in progress. Currently the change should not regress
- snapdsbehavior due to other issues surrounding using ibus unrelated to
- security policy.
+ interface, which is in already done.
+ 
+ This change intentionally requires a change to apparmor to add a unix
+ rule for communicating with the new ibus address. This is in xenial-
+ proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
+ changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
+ ensure that the apparmor abstraction is updated and policy recompiled
+ before ibus is restarted. This was omitted from the initial im-config
+ upload which resulted in bug #1588197. Test cases ensuring this is
+ working properly is included above under 'Extended test case'.
+ 
  
  = SRU apparmor =
  [Impact]
  The upload that adjusts ibus-daemon to start with "--address 
'unix:tmpdir=/tmp/ibus'" causes the ibus AppArmor abstraction to no longer be 
sufficient due to the lack of a rule for the new socket path. This upload adds 
such a rule.
  
  [Test Case]
  1. Start a unity session after updating to the im-config package in -proposed 
but before the appa

[Touch-packages] [Bug 1623198] Re: Masking and then disabling dbus.service causes the system to freeze

[Sworddragon]

@Martin: I would be fine if this action would throw me to the console
and still accept input. But that the system does fully freeze without
accepting any input similar to a kernel panic and that from an userspace
process looks definitely not correct. What should be done now?

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

Title:
  Masking and then disabling dbus.service causes the system to freeze

Status in dbus package in Ubuntu:
  Won't Fix

Bug description:
  I'm using Ubuntu 16.10 dev with systemd-sysv 231-6 and if I'm
  executing the command "systemctl mask dbus.service" and then
  "systemctl stop dbus.service" the system does freeze after a few
  seconds (even switching to the console is not possible anymore). But
  booting then the system works fine without any freezes while dbus got
  successfully disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1623198/+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 1630765] Re: webbrowser-app crashed with SIGSEGV in QNetworkConfiguration::~QNetworkConfiguration()

[Timo Jyrinki]

https://bileto.ubuntu.com/#/ticket/2054 contains a patch that Michael
Sheldon reported fixing his bug #1630941, but read the description and
comments of that ticket.

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  webbrowser-app crashed with SIGSEGV in
  QNetworkConfiguration::~QNetworkConfiguration()

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I changed the session to unity 7 and I guess the browser didn't
  stopped.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: webbrowser-app 0.23+16.10.20160928-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Wed Oct  5 22:00:38 2016
  ExecutablePath: /usr/bin/webbrowser-app
  ExecutableTimestamp: 1475051112
  InstallationDate: Installed on 2016-10-05 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  ProcCmdline: webbrowser-app
  ProcCwd: /home/jbenitez
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=es_ES
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd1d609a5df <_ZN21QNetworkConfigurationD2Ev+63>:
mov0x8(%rax),%rax
   PC (0x7fd1d609a5df) ok
   source "0x8(%rax)" (0x7fd15ef5b7d8) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   QNetworkConfiguration::~QNetworkConfiguration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QHashData::free_helper(void (*)(QHashData::Node*)) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QThreadStorageData::finish(void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplicationPrivate::cleanupThreadData() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: webbrowser-app crashed with SIGSEGV in 
QNetworkConfiguration::~QNetworkConfiguration()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1630765/+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 1630941] Re: Crash at shutdown in ~QNetworkConfiguration

[Timo Jyrinki]

See bug #1630765 for updates.

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

Title:
  Crash at shutdown in ~QNetworkConfiguration

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  After the recent landing for bug 1618590 the Ubuntu Download Manager
  tests frequently crash at shutdown with the following stack trace:

  Thread 1 "test_mms_downlo" received signal SIGSEGV, Segmentation fault.
  0x77201b23 in QNetworkConfiguration::~QNetworkConfiguration() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  (gdb) bt
  #0  0x77201b23 in QNetworkConfiguration::~QNetworkConfiguration() () 
from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  #1  0x76f31169 in QMetaType::destroy(int, void*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #2  0x76f46bf9 in QMetaCallEvent::~QMetaCallEvent() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #3  0x76f46c79 in QMetaCallEvent::~QMetaCallEvent() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #4  0x76f1c9a8 in QCoreApplicationPrivate::cleanupThreadData() () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #5  0x76f1ca8a in QCoreApplicationPrivate::~QCoreApplicationPrivate() 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #6  0x76f1cba9 in QCoreApplicationPrivate::~QCoreApplicationPrivate() 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #7  0x76f510dc in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #8  0x76f1ed12 in QCoreApplication::~QCoreApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #9  0x00449bbc in main (argc=1, argv=) at 
/home/mike/src/udm/fix-1628635/tests/downloads/daemon/test_mms_download.cpp:97

  This commit seems especially relevant: https://codereview.qt-
  project.org/#/c/172173/

  Neither this test, nor UDM itself make any explicit use of
  QPluginLoader, so this is unlikely to be a case of UDM incorrectly
  unloading a plugin itself.

  To reproduce simply run UDM's test_mms_download test a number of times
  (crashes only occur intermittently).

  When tested with a silo without the three patches added for bug
  1618590 this crash no-longer occurs.

  A similar crash appears to be happening in webbrowser-app as well:
  https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765

  Possibly another similar crash in ~QNetworkSession:
  https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630510

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1630941/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Jamie Strandboge]

** Description changed:

  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.
  
  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.
  
  [Test Case]
  1. start a unity session before updating to the package in -proposed
  
  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76
  
  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM
  
  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before
  
  5. logout of unity, then log back in
  
  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e
  
  (notice '/tmp/ibus/' in the path)
  
  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...
  
  (notice '@/tmp/ibus/' in the path)
  
  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting 'Text
  Entry'. From there, add an input source on the right, make sure 'Show
  current input source in the menu bar' is checked, then use the input
  source panel indicator to change input sources.
  
  Extended test case to verify input support still works in unconfined and
  confined applications:
  
  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials
  
  [Regression Potential]
  
  The regression potential is considered low because there are no compiled
  code changes and because the changes only occur after ibus-daemon is
  restarted, which is upon session start, not package upgrade. When it is
  restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated
  accordingly for other applications to pick up.
  
  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.
  
  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
- working properly is included above under 'Extended test case'.
+ working properly are included above under 'Extended test case'.
  
  = SRU apparmor =
  [Impact]
  The upload that adjusts ibus-daemon to start with "--address 
'unix:tmpdir=/tmp/ibus'" causes the ibus AppArmor abstraction to no longer be 
sufficient due to the lack of a rule for the new socket path. This upload adds 
such a rule.
  
  [Test Case]
  1. Start a unity session after updating to the im-config package in -proposed 
but before the apparmor package in -proposed
  
  2. Use the ibus client program to list the available engines
  $ ibus list-engine
  language: Spanish; Castilian
    xkb:latam::spa - Spanish (Latin American)
    xkb:es::spa - Spanish
  language: Slovak
    xkb:sk:qwerty:slo - Slovak (qwerty)
    xkb:sk::slo - Slovak
  ...
  
  3. Create an AppArmor profile file, called ibus, with the following
  contents:
  
  #include 
  
  profi

[Touch-packages] [Bug 1631328] Re: ceph-osd stays blocked on Yakkety: "No block devices detected using current configuration"

[James Page]

** Changed in: ceph (Ubuntu)
 Assignee: (unassigned) => James Page (james-page)

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

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

Title:
  ceph-osd stays blocked on Yakkety: "No block devices detected using
  current configuration"

Status in ceph package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in ceph-osd package in Juju Charms Collection:
  Invalid

Bug description:
  The "ceph/default," "ceph_radosgw/simple_nonha" and "ceph/harden" mojo
  specs @ Yakkety are failing like so:

  Units are consistently blocked in Juju status:
  ceph-osd stays blocked on Yakkety: "No block devices detected using current 
configuration"

  Snippets from ceph-osd unit syslog:
  mkjournal error creating journal on /var/lib/ceph/tmp/mnt.W59Jhd/journal: 
(13) Permission denied

  Oct  7 03:13:30 juju-osci-sv13-machine-4 systemd[1]: Failed to start
  Ceph disk activation: /dev/vdb1.

  See:

  http://pastebin.ubuntu.com/23288515/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1631328/+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 1626244] Re: [phone] [ubuntu touch] indicator-network-service fail to start

[Launchpad Bug Tracker]

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

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

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

Title:
  [phone] [ubuntu touch] indicator-network-service fail to start

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  When I start my BQ Aquaris 4.5, I see a gear with "indicator-network"
  written with nothing in the panel instead of the real indicator menu.

  The settings are also buggy : 
  Wifi : I see only saved networks
  Phone network : I cannot enable data.

  I do not know much about ubuntu touch, I tried the following command,
  and I get an error :

  
  root@ubuntu-phablet:/#  
./usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service 
  Error getting the bus address: Cannot autolaunch D-Bus without X11 $DISPLAY
  (process:8397): GLib-GIO-CRITICAL **: g_dbus_connection_get_unique_name: 
assertion 'G_IS_DBUS_CONNECTION (connection)' failed
  terminate called after throwing an instance of 'std::logic_error'
what():  basic_string::_S_construct null not valid

  Aborted (core dumped)

  
  Before the bug, I activated simultaneously : 
   - 3G
   - wifi
   - VPN

  I turned wifi hotspot on, and a bit later the phone froze on a black
  screen. I turn it off with power button for 5 seconds.

  On reboot, the indicator-network show a gear with empty menu.

  3G + wifi hotspot + vpn worked many times before.

  I run last update : OTA 13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1626244/+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 1630340] Re: Need DBus API to get screen orientation

[Michael Zanetti]

IMHO this really sounds like you want to start unity8 with with
testability enabled so that autopilot can connect to unity8 and get all
the things it needs from there...

Exporting those internals additionally on a d-bus interface that would
be just used for testing seems a) redundant and b) short-sighted to me.
I worry that after this autopilot would need more and more on this
interface, while starting it with testability enabled would give you
everything at once, just like it is intended for testing.

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

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

** Changed in: canonical-devices-system-image
   Status: New => Incomplete

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

Title:
  Need DBus API to get screen orientation

Status in Canonical System Image:
  Incomplete
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  To be effectively implement features like window snapping and dragging
  of windows in autopilot, we need to know the current height and width
  of the screen. mirout gives a hard-coded widthXheight, so if we know
  the orientation we can easily figure out what the real height and
  width are based on the rotation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  Uname: Linux 4.7.0-040700-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Oct  4 22:53:42 2016
  InstallationDate: Installed on 2016-09-21 (12 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630340/+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 1631365] [NEW] unity8 greeter does not save the last used session

[Albert Astals Cid]

Public bug reported:

How to reproduce:
 * Have both unity7 and unity8 sessions installed
 * Log in to unity8
 * Log out
 * The greeter suggests unity7 as the session to log in 

It should save the last session and suggest that one.

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

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

Title:
  unity8 greeter does not save the last used session

Status in unity8 package in Ubuntu:
  New

Bug description:
  How to reproduce:
   * Have both unity7 and unity8 sessions installed
   * Log in to unity8
   * Log out
   * The greeter suggests unity7 as the session to log in 

  It should save the last session and suggest that one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1631365/+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 1630653] Re: unity8-dash crashed with SIGSEGV in mir_buffer_stream_get_egl_native_window()

[Albert Astals Cid]

** Information type changed from Private to Public

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

Title:
  unity8-dash crashed with SIGSEGV in
  mir_buffer_stream_get_egl_native_window()

Status in unity8 package in Ubuntu:
  New

Bug description:
  unity 8 has lost its system settings,since I deleted /usr/bin/system-settings 
for removing unity8 and reinstalling as per some blog.
  How can I make a clean install for unity8 mir

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 21:13:00 2016
  ExecutablePath: /usr/bin/unity8-dash
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f26b88afdd6 
:   mov(%rdi),%rax
   PC (0x7f26b88afdd6) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   mir_buffer_stream_get_egl_native_window () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
   QWindowPrivate::create(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: unity8-dash crashed with SIGSEGV in 
mir_buffer_stream_get_egl_native_window()
  UpgradeStatus: Upgraded to yakkety on 2016-10-04 (0 days ago)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1630653/+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 1630845] Re: unity8-dash crashed with SIGSEGV in scopes_ng::UbuntuLocationService::update()

[Albert Astals Cid]

** Information type changed from Private to Public

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

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

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

Title:
  unity8-dash crashed with SIGSEGV in
  scopes_ng::UbuntuLocationService::update()

Status in unity-scopes-shell package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  unity8-dash crashed with SIGSEGV in
  scopes_ng::UbuntuLocationService::update()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 16:03:28 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-10-05 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161005)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f759446f4c5 
<_ZN9scopes_ng21UbuntuLocationService6updateEv+213>:mov(%rdi),%rax
   PC (0x7f759446f4c5) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   scopes_ng::UbuntuLocationService::update() () from 
/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notifyInternal2(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8-dash crashed with SIGSEGV in 
scopes_ng::UbuntuLocationService::update()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1630845/+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 1630906] Re: QML segfault on arm64 due to builder kernel change

[Timo Jyrinki]

xenial and yakkety needed symbol updates but now they have compiled and
work at least on desktop, and the arm64 build finished so it's likely
the arm64 build issue would be solved now. I've asked QA to look into
it.

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

Title:
  QML segfault on arm64 due to builder kernel change

Status in linux package in Ubuntu:
  Confirmed
Status in online-accounts-api package in Ubuntu:
  New
Status in qmenumodel package in Ubuntu:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Builders were changed from wily to xenial (4.4) kernel for arm64, and
  likely due to this the following kind of errors started happening:

  https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64
  .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz

  They happen when executing QML code.

  I've ruled out that reverting to previous qtbase and qtdeclarative
  versions don't affect this, so it's not coming from a Qt change. I've
  also verified there's no problem eg on our Bq tablet running the same
  tests on xenial+overlay. There are currently no found changes at least
  in Qt upstream to backport arm64 related fixes.

  Cause is unknown. But the same problem is there on vivid, xenial and yakkety 
builds:
  
https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz

  This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6,
  or glibc 2.21, 2.23 or 2.24.

  More logs from affected packages:
  
https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz
  
https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1630845] Re: unity8-dash crashed with SIGSEGV in scopes_ng::UbuntuLocationService::update()

[Paweł Stołowski]

** Changed in: unity-scopes-shell (Ubuntu)
   Status: New => Triaged

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

Title:
  unity8-dash crashed with SIGSEGV in
  scopes_ng::UbuntuLocationService::update()

Status in unity-scopes-shell package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  unity8-dash crashed with SIGSEGV in
  scopes_ng::UbuntuLocationService::update()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 16:03:28 2016
  ExecutablePath: /usr/bin/unity8-dash
  InstallationDate: Installed on 2016-10-05 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161005)
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f759446f4c5 
<_ZN9scopes_ng21UbuntuLocationService6updateEv+213>:mov(%rdi),%rax
   PC (0x7f759446f4c5) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   scopes_ng::UbuntuLocationService::update() () from 
/usr/lib/x86_64-linux-gnu/unity8/qml/Unity/libUnity-qml.so
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notifyInternal2(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8-dash crashed with SIGSEGV in 
scopes_ng::UbuntuLocationService::update()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1630845/+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 1631370] Re: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-system-settings-online-accounts 0.7+16.10.20161004-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Oct  6 19:18:51 2016
  ExecutablePath: /usr/bin/online-accounts-ui
  InstallationDate: Installed on 2016-06-05 (123 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/online-accounts-ui --socket 
/run/user/1000/online-accounts-ui/ui-1-google --profile unconfined
  Signal: 6
  SourcePackage: ubuntu-system-settings-online-accounts
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1631370/+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 1630167] Re: SlotsLayout with Column as mainSlot: endless loop when resizing view so that Column has negative width

[Launchpad Bug Tracker]

** Branch linked: lp:~faenil/ubuntu-ui-
toolkit/slotslayout_implicitwidthloop_bug1630167

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

Title:
  SlotsLayout with Column as mainSlot: endless loop when resizing view
  so that Column has negative width

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  With a simple code such as

  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import QtQuick.Window 2.0

  Window {
  SlotsLayout {
  id: slotsLayout
  onHeightChanged: print("SlotsLayout height",height)
  width: parent.width
  mainSlot: Column {
  onHeightChanged: print("COlumn height",height)
  onWidthChanged: console.log("Column width", width)

  Rectangle {
  id: rect
  width: parent.width
  onWidthChanged: console.log("RECT WIDTH", width)
  onHeightChanged: console.log("RECT HEIGHT!", height)
  height: 5
  }

  }
  }
  }

  
  Or something similar (http://archive.is/N0jnM), when resizing the view 
horizontally to only use few pixels, an infinite resizing loop starts and the 
view freezes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630167/+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 1631398] [NEW] package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf

[rumseed]

Public bug reported:

hi my frends

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
Uname: Linux 4.8.0-19-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Fri Oct  7 07:55:35 2016
DuplicateSignature:
 package:account-plugin-google:0.13+16.10.20160831-0ubuntu1
 Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over 
(0.13+16.10.20160831-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
  trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
InstallationDate: Installed on 2016-02-11 (239 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: account-plugins
Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 
2016-07-02T19:13:58

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


** Tags: amd64 apport-package package-conflict yakkety

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

Title:
  package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/accounts.google.com.conf', which is also in package
  kaccounts-providers 4:16.04.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  hi my frends

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Oct  7 07:55:35 2016
  DuplicateSignature:
   package:account-plugin-google:0.13+16.10.20160831-0ubuntu1
   Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over 
(0.13+16.10.20160831-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  InstallationDate: Installed on 2016-02-11 (239 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: account-plugins
  Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 
2016-07-02T19:13:58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631398/+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 1593586] Re: Issue with two external screens

[Michael Rauch]

This problem is solved for me after applying the latest updates.

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

Title:
  Issue with two external screens

Status in xorg package in Ubuntu:
  New

Bug description:
  When I boot my Laptop (Dell latitude 7470 + Dell E-Port Plus II docking 
station) with two external Dell screens attached (via Display port, each 
separate connected) at the beginning of my session everything works fine.
  The lid is closed while booting.

  After starting Firefox the focus of the mouse is some how lost. Then
  it is not possible to open the context menu of Firefox. Typed letters
  appear on the other screen.

  The focus is also lost when I remove the Laptop from the
  dockingstation and attach it back to the docking station.

  The focus works fine when only the built-in display is used.

  WORKAROUND: Boot the laptop at the beginning with only one attached
  screen (cable disconnected). After login attach the second screen,
  open the "Displays" configuration menu, and click on something without
  changing the configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jun 17 08:16:07 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
     Subsystem: Dell Skylake Integrated Graphics [1028:06dc]
  InstallationDate: Installed on 2016-06-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Latitude E7470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jun 17 08:04:44 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1168
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1593586/+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 1631398] Re: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf',

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/accounts.google.com.conf', which is also in package
  kaccounts-providers 4:16.04.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  hi my frends

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Oct  7 07:55:35 2016
  DuplicateSignature:
   package:account-plugin-google:0.13+16.10.20160831-0ubuntu1
   Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over 
(0.13+16.10.20160831-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb
 (--unpack):
trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  InstallationDate: Installed on 2016-02-11 (239 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: account-plugins
  Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in 
package kaccounts-providers 4:16.04.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 
2016-07-02T19:13:58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631398/+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 1631409] [NEW] Update usr.sbin.dnsmasq profile for network api in lxd

[hda_launchpad]

Public bug reported:

Intro:
Currently dnsmasq profile includes extra rights for lxd. Current 
usr.sbin.dnsmasq profile works with current lxd from xenial repository. But in 
lxd git (available in lxd-git-master ppa now) version network api was 
introduced, and since lxd quite active, is not too long since new lxd will be 
xenial repository. And that means people will lose network in all containers in 
production in future. This could be fixed with this extra rule in 
usr.sbin.dnsmasq profile:
/var/lib/lxd/networks/** rw, 
in usr.sbin.dnsmasq profile.

1) Ubuntu 16.04.1 LTS

2) apparmor-profiles (currently 2.10.95-0ubuntu2.4). I couldn't select
apparmor-profiles, only apparmor or apparmor-profiles-extra. Don't know
why, mb launchpad bug.

3) What you expected to happen:
network in lxd will start 

4) apparmor usr.sbin.dnsmasq profile blocks network in new lxd version

Bug original source:
https://github.com/lxc/lxd-pkg-ubuntu/issues/21

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

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

Title:
  Update usr.sbin.dnsmasq profile for network api in lxd

Status in apparmor package in Ubuntu:
  New

Bug description:
  Intro:
  Currently dnsmasq profile includes extra rights for lxd. Current 
usr.sbin.dnsmasq profile works with current lxd from xenial repository. But in 
lxd git (available in lxd-git-master ppa now) version network api was 
introduced, and since lxd quite active, is not too long since new lxd will be 
xenial repository. And that means people will lose network in all containers in 
production in future. This could be fixed with this extra rule in 
usr.sbin.dnsmasq profile:
  /var/lib/lxd/networks/** rw, 
  in usr.sbin.dnsmasq profile.

  1) Ubuntu 16.04.1 LTS

  2) apparmor-profiles (currently 2.10.95-0ubuntu2.4). I couldn't select
  apparmor-profiles, only apparmor or apparmor-profiles-extra. Don't
  know why, mb launchpad bug.

  3) What you expected to happen:
  network in lxd will start 

  4) apparmor usr.sbin.dnsmasq profile blocks network in new lxd version

  Bug original source:
  https://github.com/lxc/lxd-pkg-ubuntu/issues/21

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1631409/+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 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb

[Marcus Tomlinson]

** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from
  QObjectPrivate::isSignalConnected from QMetaObject::activate from
  QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset

Status in Canonical System Image:
  Fix Released
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.14+15.04.20160831.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627795/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

[hackeron]

I'm on Xenial and I ran an apt-get update; apt-get dist-upgrade and my
eth0 changed back to enxb827djdk after reboot :(

My biggest issue is virtual interfaces do NOT work with these
"predictable" network names. I can do ifconfig eth0:0 192.168.123.123
but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just
overrites the main IP, rather than creating another virtual interface :(

Previously, I was able to follow these steps:

Edit/boot/firmware/config.txt to add:
  net.ifnames=0
  biosdevname=0

Run: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

Make sure this file is absent (which it was anyway):
/lib/udev/rules.d/73-usb-net-by-mac.rules

Run: update-initramfs -k all -u

But now, running the above steps no longer works and I'm getting
enxb827djdk again :(

I also checked /proc/cmdline and I have net.ifnames=0 there so it's
definitely being passed. I'm running kernel 4.4.0-1023-raspi2 Sep 6
16:12:44 UTC 2016

Is there a solution/workaround?

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

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1607427] Re: super key not showing scopes home

[Launchpad Bug Tracker]

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

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

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

Title:
  super key not showing scopes home

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Hey,

  if I press super key, the scopes home does not appear. In OTA-11 it
  worked as it should, but in OTA-12 it doesn't work.

  I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+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 1248044] Re: xzless report an error

[Bug Watch Updater]

** Changed in: xz-utils (Debian)
   Status: Confirmed => Fix Released

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

Title:
  xzless report an error

Status in xz-utils package in Ubuntu:
  Fix Released
Status in xz-utils package in Debian:
  Fix Released

Bug description:
  when using the command xzless, I have always this line

  /usr/bin/xzless: line 49: test: 458 (GNU regular expressions): integer
  expression expected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1248044/+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 1607427] Re: super key not showing scopes home

[Lukáš Tinkl]

** Changed in: unity8 (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)

** Changed in: mir (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  super key not showing scopes home

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Hey,

  if I press super key, the scopes home does not appear. In OTA-11 it
  worked as it should, but in OTA-12 it doesn't work.

  I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

[Martin Pitt]

hackeron, which systemd version are you using? Note that the one
currently in xenial-updates reverted the previous SRU, you need version
229-4ubuntu11.

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

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1612367] Re: [Touch] Incoming call gets silent randomly

[Anupam]

Excuse this naive comment, but if I'm not mistaken, while the phone
rings on an incoming call, pressing the power button pauses the
ringtone. Is it possible that the same/similar action is simulated here
even when the user is not pressing the power button?

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

[Robie Basak]

On Fri, Oct 07, 2016 at 03:20:29PM -, hackeron wrote:
> My biggest issue is virtual interfaces do NOT work with these
> "predictable" network names. I can do ifconfig eth0:0 192.168.123.123
> but I cannot do ifconfig enxb827djdk:0 192.168.123.123 - it just
> overrites the main IP, rather than creating another virtual interface :(

I can't help with the bug in general, but for this particular use case,
try "ip addr add 192.168.123.123 dev enxb827djdk". ifconfig isn't going
away, but all new development has moved to the "ip" command which
replaces it.

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

Title:
  systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
  /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  Description:Ubuntu 16.04 LTS
  Release:16.04

  The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
  devices.

  It appears the regression is here:
  * Set MAC based name for USB network interfaces only for universally
  administered (i. e. stable) MACs, not for locally administered (i. e.
  randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
  (as link files don't currently support globs for MACAddress=) and replace
  with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
  (Closes: #812575, LP: #1574483)

  As Raspberry Pi's use eth0 via USB, this breaks running systems.

  Before:
  ii  systemd229-4ubuntu4 armhfsystem and service manager
  ii  udev   229-4ubuntu4 armhf/dev/ and hotplug management daem

  3: eth0:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  After:

  ii  systemd  229-4ubuntu6armhf   
system and service manager
  ii  udev 229-4ubuntu6armhf   
/dev/ and hotplug management daemon

  3: enxb827eb1639e9:  mtu 1500 qdisc 
pfifo_fast state UP mode DEFAULT group default qlen 1000
  link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff

  cat /proc/cmdline
  dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 
rootfstype=ext4 elevator=deadline rootwait

  With the default interfaces configuration, all networking is lost on
  reboot after upgrade.

  
  SRU TEST CASE
  =
   * Boot with "net.ifnames=0" on the kernel command line, and connect an USB 
ethernet device. It will still be called enxDEADBEEF with current xenial. With 
the -proposed version it will instead keep the kernel name, like "usb0" as 
intended.

   * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
  (the other documented way to disable ifnames) and do the above
  connect/name check test again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS

[James Troup]

I'm afraid this didn't work for me.  I installed network-manager
1.2.2-0ubuntu0.16.04.3 from xenial-proposed, ran 'systemctl restart
NetworkManager' as root and reconnected to the VPN and I see the same
behaviour (i.e. I get DNS resolution failure for non-VPN domains).  I
am on wifi only and both v4 and v6 are set to route all outbound
traffic.

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

Title:
  Don't write search domains to resolv.conf in the case of split DNS

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  All VPN users meaning to use split-tunnelling in a situation where leaking 
DNS data to the internet about what might be behind their VPN is undesirable.

  [Test case]
  1) connect to VPN
  2) Use dig to request a name that should be on the VPN
  3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only 
gone through the VPN nameservers (only its request number should have increased 
by one)
  4) Use dig to request a name off-VPN, such as google.com.
  5) Verify (kill -USR1 again) that the request has caused the non-VPN 
nameserver request number to increase, and that the VPN number has not 
increased.

  It is easier to verify this when there is as little traffic as
  possible on the system, to avoid spurious DNS requests which would
  make it harder to validate the counters.

  [Regression potential]
  This change modifies the way in which DNS nameservers and search domains are 
passed to dnsmasq, as such, if a VPN is configured in a non-standard way and 
intended to be used to resolve all network requests (which is typically not the 
case for split-tunnelling) or if the public network is intended to always 
resolve all requests while the VPN still provides search domains, one might 
observe incorrect behavior.

  Possible failure cases would include failure to resolve names
  correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving
  to the incorrect values (if the wrong nameserver is used).

  ---

  Currently, NM will write all search domains to both any DNS-handling
  plugins running, and also to resolv.conf / resolvconf; in all cases.

  The issue is that doing so means that in the split-DNS case on VPNs,
  you might get a negative response from all nameservers, then a new
  request by glibc with the search tacked on, to nameservers again,
  which might cause DNS requests for "private" resources (say, on the
  VPN) to be sent to external, untrusted resolvers, or for DNS queries
  not meant for VPN nameservers to be sent through the VPN anyway.

  This is fixable in the case where we have a caching plugin running
  (such as dnsmasq). dnsmasq will already know about the search domains
  and use that to limit queries to the right nameservers when a VPN is
  running. Writing search domains to resolv.conf is unnecessary in this
  case.

  We should still write search domains if no caching gets done, as we
  then need to expect glibc to send requests as it otherwise would.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1630167] Re: SlotsLayout with Column as mainSlot: endless loop when resizing view so that Column has negative width

[Andrea Bernabei]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => In Progress

** Also affects: ubuntu-ui-toolkit (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
 Assignee: (unassigned) => Andrea Bernabei (faenil)

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
   Status: New => In Progress

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

Title:
  SlotsLayout with Column as mainSlot: endless loop when resizing view
  so that Column has negative width

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  In Progress

Bug description:
  With a simple code such as

  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import QtQuick.Window 2.0

  Window {
  SlotsLayout {
  id: slotsLayout
  onHeightChanged: print("SlotsLayout height",height)
  width: parent.width
  mainSlot: Column {
  onHeightChanged: print("COlumn height",height)
  onWidthChanged: console.log("Column width", width)

  Rectangle {
  id: rect
  width: parent.width
  onWidthChanged: console.log("RECT WIDTH", width)
  onHeightChanged: console.log("RECT HEIGHT!", height)
  height: 5
  }

  }
  }
  }

  
  Or something similar (http://archive.is/N0jnM), when resizing the view 
horizontally to only use few pixels, an infinite resizing loop starts and the 
view freezes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630167/+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 1624337] Re: Scrollbar tests fail on Qt 5.6.

[Andrea Bernabei]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Scrollbar tests fail on Qt 5.6.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  FAIL!  : components::Scrollbar::test_defaultStylingValues(vertical scrollbar) 
Wrong styling property default value.
 Actual   (): #5d5d5d
 Expected (): #11
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)]
  FAIL!  : components::Scrollbar::test_defaultStylingValues(horizontal 
scrollbar) Wrong styling property default value.
 Actual   (): #5d5d5d
 Expected (): #11
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)]
  FAIL!  : components::Scrollbar::test_dragThumbAndCheckStyling(vertical 
scrollbar) Uncaught exception: Type error
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(800)]
  FAIL!  : components::Scrollbar::test_dragThumbAndCheckStyling(horizontal 
scrollbar) Uncaught exception: Type error
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(838)]

  and

  * Start testing of components *
  Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 5.4.0 20160609)
  PASS   : components::Scrollbar::initTestCase()
  FAIL!  : components::Scrollbar::test_handlingOfMovingHeader(Standard header) 
Uncaught exception: Type error
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)]
  FAIL!  : components::Scrollbar::test_handlingOfMovingHeader(Edit header (with 
extensions)) Uncaught exception: Type error
 Loc: 
[/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)]
  PASS   : components::Scrollbar::cleanupTestCase()
  Totals: 2 passed, 2 failed, 0 skipped, 0 blacklisted
  * Finished testing of components *

  
  See 
https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624337/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

[Scott Moser]

** Changed in: cloud-init (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  In Progress
Status in dbus package in Ubuntu:
  Triaged

Bug description:
  During boot, cloud-init does DNS resolution checks to if particular
  metadata services are available (in order to determine which cloud it
  is running on).  These checks happen before systemd-resolved is up[0]
  and if they resolve unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1631302] [NEW] System becomes unresponsive when running code with deep-recursion under unprivileged user

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In Ubuntu 16.04 if you run
perl -e 'sub x { x() }; x()'
(this commands does a deep recursion, eats all memory)

under non-root user

whole system becomes unresponsive, mouse, keyboard does not work. Screen
does not update when you plug/unplug charger, for example. The only way
to quit is to press power button and shut down machine.

Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least
something should work.

Repsoduced on HP Pavilion 16, SSD with encryption, encrypted Swap.
Reproduced by at least one another person with Ubuntu 16.04 with SSD.

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


** Tags: bot-comment
-- 
System becomes unresponsive when running code with deep-recursion under 
unprivileged user
https://bugs.launchpad.net/bugs/1631302
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to perl 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 1631302] Re: System becomes unresponsive when running code with deep-recursion under unprivileged user

[Paul White]

Reassigning bug against perl so someone with more knowledge that I can
look into it further.

I have no idea if this is a bug or not but I can confirm that an Ubuntu
16.10 test system locks up as described.

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

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

Title:
  System becomes unresponsive when running code with deep-recursion
  under unprivileged user

Status in perl package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04 if you run
  perl -e 'sub x { x() }; x()'
  (this commands does a deep recursion, eats all memory)

  under non-root user

  whole system becomes unresponsive, mouse, keyboard does not work.
  Screen does not update when you plug/unplug charger, for example. The
  only way to quit is to press power button and shut down machine.

  Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least
  something should work.

  Repsoduced on HP Pavilion 16, SSD with encryption, encrypted Swap.
  Reproduced by at least one another person with Ubuntu 16.04 with SSD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1631302/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

[Dan Watkins]

To determine if this has been fixed, boot an image that has the GCE data
source enabled (e.g. the image from cloud-images.ubuntu.com) but not on
GCE.  Examine the output of `journalctl` and look for the following
lines:

Oct 07 16:17:39 ubuntu cloud-init[1009]: [CLOUDINIT] __init__.py[DEBUG]: Seeing 
if we can get any data from 
Oct 07 16:19:19 ubuntu cloud-init[1009]: [CLOUDINIT] DataSourceGCE.py[DEBUG]: 
http://metadata.google.internal/computeMetadata/v1/ is not resolvable


The timestamps on them should be no more than fractions of a second apart (the 
above example is on a _broken_ instance).

(Note that, (a) there may be lines in between these two, and (b) you
have to use `journalctl` because cloud-init.log doesn't have correct
timestamps.)

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

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  In Progress
Status in dbus package in Ubuntu:
  Triaged

Bug description:
  During boot, cloud-init does DNS resolution checks to if particular
  metadata services are available (in order to determine which cloud it
  is running on).  These checks happen before systemd-resolved is up[0]
  and if they resolve unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1612367] Re: [Touch] Incoming call gets silent randomly

[Pat McGowan]

@anupam thats an interesting theory, I got a log of when the power
button is pressed and it goes from paused to stopped almost instantly,
whereas your logs generally show a delay and stopped is only issued once
the call is answered.

@jim I still thinks its a thread issue in media hub, I can't get by the
fact that its logging engine playing uri multiple times on each incoming
call and logging paused multiple times. Perhaps thats benign but unclear
to me why the same code is executed more than once "sometimes".

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1631302] Re: System becomes unresponsive when running code with deep-recursion under unprivileged user

[vsespb]

I suspect it's not about perl, probably system can be locked same way
with any programming language.

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

Title:
  System becomes unresponsive when running code with deep-recursion
  under unprivileged user

Status in perl package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.04 if you run
  perl -e 'sub x { x() }; x()'
  (this commands does a deep recursion, eats all memory)

  under non-root user

  whole system becomes unresponsive, mouse, keyboard does not work.
  Screen does not update when you plug/unplug charger, for example. The
  only way to quit is to press power button and shut down machine.

  Expected bahaviour: Ctrl-C, Ctrl-Alt-Del, Ctrl-Alt-F1, mouse, at least
  something should work.

  Repsoduced on HP Pavilion 16, SSD with encryption, encrypted Swap.
  Reproduced by at least one another person with Ubuntu 16.04 with SSD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1631302/+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 1631436] [NEW] Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3

[Pierre BLONDEAU]

Public bug reported:

In the past, until the version  0.122ubuntu8.1, we used the syntax
"ip=:eth0:dhcp" as described in the kernel's documentation :
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0"
syntax as far as i have tested it.

So, the current last package version leaves the machine without network
on boot. Any host that needs network on boot (nfsroot / using dropbear
for example) might not boot properly.

Regards

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Some network configuration cmdline arguments doesn't work anymore with
  version 0.122ubuntu8.3

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  In the past, until the version  0.122ubuntu8.1, we used the syntax
  "ip=:eth0:dhcp" as described in the kernel's documentation :
  https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

  The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0"
  syntax as far as i have tested it.

  So, the current last package version leaves the machine without
  network on boot. Any host that needs network on boot (nfsroot / using
  dropbear for example) might not boot properly.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436/+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 1622002] Re: dhcp_release6 can be called when it is not present

[Ihar Hrachyshka]

** Tags removed: newton-rc-potential

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

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+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 1607427] Re: super key not showing scopes home

[Lukáš Tinkl]

** Branch linked: lp:~lukas-kde/unity8/superKeyPressFix

** Changed in: mir
   Status: New => Invalid

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

Title:
  super key not showing scopes home

Status in Canonical System Image:
  New
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Hey,

  if I press super key, the scopes home does not appear. In OTA-11 it
  worked as it should, but in OTA-12 it doesn't work.

  I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607427/+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 1561861] Re: UbuntuColors.Orange should be Ubuntu.orange instead

[Andrea Bernabei]

Hi liu-xiao-guo,
I have just sent an MR that fixes the typo you reported.

Sorry if it took so long, I was not aware of this bug (as I'm not in the
SDK team, but I implemented ListItemLayout) and only just found it while
I was doing a random text search for launchpad bugs that were affecting
components I wrote.

Thanks for reporting the bug, it's important to have a polished and
reliable documentation!

** Summary changed:

- UbuntuColors.Orange should be Ubuntu.orange instead
+ UbuntuColors.Orange should be UbuntuColors.orange instead

** Summary changed:

- UbuntuColors.Orange should be UbuntuColors.orange instead
+ ListItemLayout documentation: UbuntuColors.Orange should be 
UbuntuColors.orange instead

** Also affects: ubuntu-ui-toolkit (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
   Status: New => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
   Importance: Undecided => Low

** Changed in: ubuntu-ui-toolkit (Ubuntu RTM)
 Assignee: (unassigned) => Andrea Bernabei (faenil)

** No longer affects: ubuntu-ui-toolkit (Ubuntu RTM)

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

Title:
  ListItemLayout documentation: UbuntuColors.Orange should be
  UbuntuColors.orange instead

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/

  The code:

  ListItemLayout {
  id: layout
  title.text: "Hello..."
  title.color: UbuntuColors.Orange
  subtitle.text: "...world!"
  Rectangle {
  SlotsLayout.position: SlotsLayout.Leading
  color: "pink"
  height: units.gu(6)
  width: height
  }

  
  UbuntuColors.Orange should be Ubuntu.orange

  Best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1561861/+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 1561861] Re: UbuntuColors.Orange should be Ubuntu.orange instead

[Launchpad Bug Tracker]

** Branch linked: lp:~faenil/ubuntu-ui-
toolkit/listitemlayout_doc_typofix

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

Title:
  ListItemLayout documentation: UbuntuColors.Orange should be
  UbuntuColors.orange instead

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/

  The code:

  ListItemLayout {
  id: layout
  title.text: "Hello..."
  title.color: UbuntuColors.Orange
  subtitle.text: "...world!"
  Rectangle {
  SlotsLayout.position: SlotsLayout.Leading
  color: "pink"
  height: units.gu(6)
  width: height
  }

  
  UbuntuColors.Orange should be Ubuntu.orange

  Best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1561861/+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 1561861] Re: UbuntuColors.Orange should be Ubuntu.orange instead

[Andrea Bernabei]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Andrea Bernabei (faenil)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

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

Title:
  ListItemLayout documentation: UbuntuColors.Orange should be
  UbuntuColors.orange instead

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.ListItemLayout/

  The code:

  ListItemLayout {
  id: layout
  title.text: "Hello..."
  title.color: UbuntuColors.Orange
  subtitle.text: "...world!"
  Rectangle {
  SlotsLayout.position: SlotsLayout.Leading
  color: "pink"
  height: units.gu(6)
  width: height
  }

  
  UbuntuColors.Orange should be Ubuntu.orange

  Best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1561861/+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 1631447] [NEW] SlotsLayout padding grouped property needs to assigned member-by-member, can't be assigned as a whole

[Treviño]

Public bug reported:

ubuntu-ui-toolkit/staging branch, r2139

At the moment to assign paddings of a SlotsLayout you can only do:
SlotsLayout {
  id: myLayout
  padding.top: units.gu(15)
  padding.bottom: units.gu(5)
}

Assigning the whole padding at once is not possible:
SlotsLayout {
  padding: myLayout.padding
}
as that returns an error:

Slots.qml: Invalid property assignment: "padding" is a read-only property
So to achieve this we need to manually assign the subvalues.

It would be nice to do it all at once.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Wishlist
 Assignee: Andrea Bernabei (faenil)
 Status: Triaged

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

Title:
  SlotsLayout padding grouped property needs to assigned member-by-
  member, can't be assigned as a whole

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  ubuntu-ui-toolkit/staging branch, r2139

  At the moment to assign paddings of a SlotsLayout you can only do:
  SlotsLayout {
    id: myLayout
    padding.top: units.gu(15)
    padding.bottom: units.gu(5)
  }

  Assigning the whole padding at once is not possible:
  SlotsLayout {
    padding: myLayout.padding
  }
  as that returns an error:

  Slots.qml: Invalid property assignment: "padding" is a read-only property
  So to achieve this we need to manually assign the subvalues.

  It would be nice to do it all at once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1631447/+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 1631447] Re: SlotsLayout padding grouped property needs to assigned member-by-member, can't be assigned as a whole

[Andrea Bernabei]

Thanks Marco!
That makes sense, I'll have a look at that next week!

** Summary changed:

- SlotsLayout paddings can't be bound to another layout values
+ SlotsLayout padding grouped property needs to assigned member-by-member, 
can't be assigned as a whole

** Description changed:

+ ubuntu-ui-toolkit/staging branch, r2139
+ 
+ At the moment to assign paddings of a SlotsLayout you can only do:
  SlotsLayout {
-   id: myLayout
-   padding.top: units.gu(15)
-   padding.bottom: units.gu(5)
+   id: myLayout
+   padding.top: units.gu(15)
+   padding.bottom: units.gu(5)
  }
  
+ Assigning the whole padding at once is not possible:
  SlotsLayout {
-   padding: myLayout.padding
+   padding: myLayout.padding
  }
- 
- Would return an error:
+ as that returns an error:
  
  Slots.qml: Invalid property assignment: "padding" is a read-only property
  So to achieve this we need to manually assign the subvalues.
  
  It would be nice to do it all at once.

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

Title:
  SlotsLayout padding grouped property needs to assigned member-by-
  member, can't be assigned as a whole

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  ubuntu-ui-toolkit/staging branch, r2139

  At the moment to assign paddings of a SlotsLayout you can only do:
  SlotsLayout {
    id: myLayout
    padding.top: units.gu(15)
    padding.bottom: units.gu(5)
  }

  Assigning the whole padding at once is not possible:
  SlotsLayout {
    padding: myLayout.padding
  }
  as that returns an error:

  Slots.qml: Invalid property assignment: "padding" is a read-only property
  So to achieve this we need to manually assign the subvalues.

  It would be nice to do it all at once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1631447/+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 729831] Re: Output controls are not switched to headset

[Launchpad Bug Tracker]

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

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

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

Title:
  Output controls are not switched to headset

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  After my bluetooth headset is connected to the system, the sound output is 
switched from the speakers to the headset, but the volume control does not set 
the volume of the headset. I have to go to "Sound Preferences... -> Output", 
then choose my headset here. Then I can control the volume.
  Also, after selecting a new output device, the "Output volume" slider changes 
its position, but the volume remains the same. I have to either click on the 
slider or use the volume keys on the keyboard to actually set the volume.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
  Uname: Linux 2.6.35-27-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xvro   2336 F pulseaudio
   /dev/snd/pcmC1D0c:   xvro   2336 F...m pulseaudio
   /dev/snd/controlC0:  xvro   2336 F pulseaudio
   /dev/snd/pcmC0D0p:   xvro   2336 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xea40 irq 49'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,1458a002,00100101'
 Controls  : 38
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'SAA7134'/'saa7133[0] at 0xea315000 irq 19'
 Mixer name : 'SAA7134 Mixer'
 Components : ''
 Controls  : 6
 Simple ctrls  : 3
  Date: Sat Mar  5 21:36:59 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 04/24/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4B
  dmi.board.name: EX38-DQ6
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EX38-DQ6
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  mtime.conffile..etc.pulse.default.pa: 2010-12-19T18:10:08.489783

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/729831/+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 1277030] Re: Scrollbar should match overlay-scrollbar style.

[Andrea Bernabei]

Hi Robert, I implemented the new scrollbars a few months ago. 
Can you have a look and confirm if the new scrollbars fix your problems?

(I'm not sure I understand, from the description)

The Scrollbars I implemented are for Qt apps that use the Ubuntu UI
Toolkit

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

Title:
  Scrollbar should match overlay-scrollbar style.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  qml apps on the unity7 desktop don't scroll very well, they
  technically have a scrollbar but it's non-interactive, and doesn't
  match the overlay-scrollbar style of gtk and qt apps (instead of being
  bright orange, it's faint, dark grey, barely noticable, and hides
  while not actively scrolling).

  Requiring desktop users to click&drag scroll makes for quite an
  inconsistent desktop experience and should be fixed.

  This is blocking a decent webapps-container experience on the 14.04
  desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1277030/+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 1628042] Re: Doesn't vibrate on incoming calls if "Other vibrations" not active

[Pat McGowan]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Doesn't vibrate on incoming calls if "Other vibrations" not active

Status in Canonical System Image:
  Fix Committed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Set "Vibrate on ring" and "Vibrate in silent mode" active under "Ringtone" 
in System settings > Sound.
  2. Make sure "Other vibrations" is NOT active in System settings > Sound.
  3. Get an incoming call.

  Expected:
  Phone vibrates.

  What happens:
  Phone doesn't vibrate. If the "Other vibrations" is set active, then the 
vibration works.

  Device: E5, stable, OTA-13.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628042/+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 729831] Re: Output controls are not switched to headset

[Ivan Baldo]

The same thing happens with USB headsets, so, it seems related to having
multiple output devices dynamically connected.

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

Title:
  Output controls are not switched to headset

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  After my bluetooth headset is connected to the system, the sound output is 
switched from the speakers to the headset, but the volume control does not set 
the volume of the headset. I have to go to "Sound Preferences... -> Output", 
then choose my headset here. Then I can control the volume.
  Also, after selecting a new output device, the "Output volume" slider changes 
its position, but the volume remains the same. I have to either click on the 
slider or use the volume keys on the keyboard to actually set the volume.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11
  Uname: Linux 2.6.35-27-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xvro   2336 F pulseaudio
   /dev/snd/pcmC1D0c:   xvro   2336 F...m pulseaudio
   /dev/snd/controlC0:  xvro   2336 F pulseaudio
   /dev/snd/pcmC0D0p:   xvro   2336 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xea40 irq 49'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,1458a002,00100101'
 Controls  : 38
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'SAA7134'/'saa7133[0] at 0xea315000 irq 19'
 Mixer name : 'SAA7134 Mixer'
 Components : ''
 Controls  : 6
 Simple ctrls  : 3
  Date: Sat Mar  5 21:36:59 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 04/24/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4B
  dmi.board.name: EX38-DQ6
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EX38-DQ6
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  mtime.conffile..etc.pulse.default.pa: 2010-12-19T18:10:08.489783

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/729831/+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 1611227] Re: Don't use gold linker on powerpc (GCC6)

[Steve Langasek]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-3.6 into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.6/1:3.6.2-3ubuntu4 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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!

** Tags added: verification-needed

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

Title:
  Don't use gold linker on powerpc (GCC6)

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  GCC is now configured with --enable-secureplt. On powerpc, one may now
  get /usr/bin/ld.gold: --secure-plt: unknown option

  According to doko gold linker should not be used on powerpc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1611227/+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 1277030] Re: Scrollbar should match overlay-scrollbar style.

[Robert Bruce Park]

Seems fine I guess? I tried to confirm with address-book-app and
messaging-app, but on my desktop I wasn't able to get either of them to
have a scrollbar (I can neither add contacts nor send messages, so both
apps just show an empty, scroll-less window). webbrowser-app at least
displays a real scrollbar that I can interact with, unlike what it did
those years ago when i reported this bug.

Thanks!

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Scrollbar should match overlay-scrollbar style.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  qml apps on the unity7 desktop don't scroll very well, they
  technically have a scrollbar but it's non-interactive, and doesn't
  match the overlay-scrollbar style of gtk and qt apps (instead of being
  bright orange, it's faint, dark grey, barely noticable, and hides
  while not actively scrolling).

  Requiring desktop users to click&drag scroll makes for quite an
  inconsistent desktop experience and should be fixed.

  This is blocking a decent webapps-container experience on the 14.04
  desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1277030/+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 1628306] Re: network booting fails for iscsi root if no ip is set

[scotte]

initramfs-tools 0.122ubuntu8.3 has resulted in a serious regression for
instances running in AWS when the ip=dhcp boot option set.
0.122ubuntu8.2 (and previous versions) do not exhibit the problem.

I'll create a new issue for tracking, but wanted to add a comment here.

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

Title:
  network booting fails for iscsi root if no ip is set

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration 
is simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools 
(0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a 
remote root filesystem would constitue a regression.

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1628306/+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 1631474] [NEW] No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[scotte]

Public bug reported:

initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
networking is not initialized when the boot option "ip=dhcp" is
provided. We are seeing this problem in AWS, but cannot confirm if this
issue is specific to AWS or will occur with different hardware or in
different environments.

Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in
networking being configured.

The issue does not occur with 0.122ubuntu8.2 or previous versions when
"ip=dhcp" is set.

AWS has no console so debugging is not a trivial task. I do have a
console log with some output, and will update this bug shortly with it.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1629466] Re: Can't open a PDF from a webapp

[Alexandre Abreu]

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

This is a duplicate of https://bugs.launchpad.net/webapps-
core/+bug/1560086 for which there is a branch in progress, sorry for the
delay on this, I will MR it ASAP,

** This bug has been marked a duplicate of bug 1560086
   cannot download files with no destination app from webapps

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

Title:
  Can't open a PDF from a webapp

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  And potentially any Content Hub file?

  When trying to open pdfs in the fastmail or reddit webapps, I get the
  following and the pdf never opens:

  
file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Content/ContentPeerPicker13.qml:194:
 TypeError: Cannot read property 'peers' of null
  file:///usr/share/webbrowser-app/webcontainer/WebappWebview.qml:219: 
ReferenceError: startDownload is not defined

  I'm assuming it's the second message that is fatal, so I've opened
  against webbrowser-app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1629466/+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 1560086] Re: cannot download files with no destination app from webapps

[Alexandre Abreu]

** Changed in: webapps-sprint
Milestone: sprint-25 => sprint-26

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

Title:
  cannot download files with no destination app from webapps

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in The Webapps-core project:
  New
Status in webapps-sprint:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Using the webbrowser-app I can download any file, and will be prompted
  to open in an app (if apps that support that content-type exist on the
  system) or to download the file in the browser. The same behavior
  should be available webapps but is not.

  Steps to reproduce:
  - Open Gmail webapp
  - Open a message that has an attachment of a file of unsupported type (like a 
.tar, .click, etc)
  - click on the file to download

  Expected results:
  - I should be prompted to open the file in supported app or to download
  - If I choose download the file should be downloaded into ~/Downloads by the 
webbrowser-app

  Actual results:
  - I am told that no apps exist to support this type of file and am not 
allowed to download it

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560086/+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 1631436] Re: Some network configuration cmdline arguments doesn't work anymore with version 0.122ubuntu8.3

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

Title:
  Some network configuration cmdline arguments doesn't work anymore with
  version 0.122ubuntu8.3

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  In the past, until the version  0.122ubuntu8.1, we used the syntax
  "ip=:eth0:dhcp" as described in the kernel's documentation :
  https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

  The version 0.122ubuntu8.3 breaks it. It works only with "ip=eth0"
  syntax as far as i have tested it.

  So, the current last package version leaves the machine without
  network on boot. Any host that needs network on boot (nfsroot / using
  dropbear for example) might not boot properly.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.8-15-g6e45ffb-
0ubuntu1

---
cloud-init (0.7.8-15-g6e45ffb-0ubuntu1) yakkety; urgency=medium

  * New upstream snapshot.
- systemd: Run cloud-init.service Before dbus.socket not dbus.target
  [Daniel Watkins] (LP: #1629797).

 -- Scott Moser   Fri, 07 Oct 2016 12:41:38 -0400

** Changed in: cloud-init (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 dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1629797

Title:
  resolve service in nsswitch.conf adds 25 seconds to failed lookups
  before systemd-resolved is up

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in dbus package in Ubuntu:
  Triaged

Bug description:
  During boot, cloud-init does DNS resolution checks to if particular
  metadata services are available (in order to determine which cloud it
  is running on).  These checks happen before systemd-resolved is up[0]
  and if they resolve unsuccessfully they take 25 seconds to complete.

  This has substantial impact on boot time in all contexts, because
  cloud-init attempts to resolve three known-invalid addresses ("does-
  not-exist.example.com.", "example.invalid." and a random string) to
  enable it to detect when it's running in an environment where a DNS
  server will always return some sort of redirect.  As such, we're
  talking a minimum impact of 75 seconds in all environments.  This
  increases when cloud-init is configured to check for multiple
  environments.

  This means that yakkety is consistently taking 2-3 minutes to boot on
  EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
  seconds thereafter in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1629797/+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 1629009] Re: Does not work inside a snap due to hardcoded paths

[Michael Terry]

** Branch linked: lp:~mterry/unity8/snap-root2

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in Ubuntu File Manager App:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Fix Committed
Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New
Status in unity-scope-scopes package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1629009/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[scotte]

This was on xenial, unknown if other versions are affected.

Related:

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631436
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[scotte]

Here's the initial portion of console output, with only a couple of
minor redactions related to keys, hostname, MAC address.

The most important bit is:

ip: SIOCGIFFLAGS: No such device
Error getting hardware address for "dhcp": No such device

Where the "ip=dhcp" kernel is not being processed correctly per kernel
documentation - see
https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

=== CUT HERE===
[2.179049] registered taskstats version 1
[2.179074] Loading compiled-in X.509 certificates
[2.179821] Loaded X.509 cert 'Build time autogenerated kernel key: REDACTED'
[2.179848] zswap: loaded using pool lzo/zbud
[2.190763] Key type trusted registered
[2.195735] Key type encrypted registered
[2.195747] AppArmor: AppArmor sha1 policy hashing enabled
[2.195753] ima: No TPM chip found, activating TPM-bypass!
[2.195778] evm: HMAC attrs: 0x1
[2.213710] blkfront: xvda1: barrier or flush: disabled; persistent grants: 
disabled; indirect descriptors: enabled;
[2.218079] blkfront: xvdb: flush diskcache: enabled; persistent grants: 
disabled; indirect descriptors: enabled;
[2.292145]   Magic number: 1:252:3141
[2.292190] hctosys: unable to open rtc device (rtc0)
[2.292239] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[2.292244] EDD information not available.
[2.292964] Freeing unused kernel memory: 1480K (81f41000 - 
820b3000)
[2.292973] Write protecting the kernel read-only data: 14336k
[2.296529] Freeing unused kernel memory: 1868K (88000182d000 - 
880001a0)
[2.296620] Freeing unused kernel memory: 176K (880001dd4000 - 
880001e0)
Loading, please wait...
starting version 229
[2.337933] random: udevadm urandom read with 7 bits of entropy available
[2.595423] SSE version of gcm_enc/dec engaged.
Begin: Loading essential drivers ...
[3.942253] md: linear personality registered for level -1
[3.954483] md: multipath personality registered for level -4
[3.957749] md: raid0 personality registered for level 0
[3.975096] md: raid1 personality registered for level 1
[4.059760] raid6: sse2x1   gen()  3697 MB/s
[4.124589] raid6: sse2x1   xor()  3003 MB/s
[4.192058] raid6: sse2x2   gen()  4609 MB/s
[4.260062] raid6: sse2x2   xor()  3242 MB/s
[4.335089] raid6: sse2x4   gen()  5511 MB/s
[4.400055] raid6: sse2x4   xor()  3912 MB/s
[4.400061] raid6: using algorithm sse2x4 gen() 5511 MB/s
[4.400064] raid6:  xor() 3912 MB/s, rmw enabled
[4.400068] raid6: using ssse3x2 recovery algorithm
[4.407087] xor: measuring software checksum speed
[4.468056]prefetch64-sse:  8536.000 MB/sec
[4.524066]generic_sse:  8099.000 MB/sec
[4.524076] xor: using function: prefetch64-sse (8536.000 MB/sec)
[4.527357] async_tx: api initialized (async)
[4.548551] md: raid6 personality registered for level 6
[4.548560] md: raid5 personality registered for level 5
[4.548564] md: raid4 personality registered for level 4
[4.595063] md: raid10 personality registered for level 10
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ...
[4.687584] Btrfs loaded
Scanning for Btrfs filesystems
done.
Warning: fsck not present, so skipping root file system
[4.809766] EXT4-fs (xvda1): mounted filesystem with ordered data mode. 
Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... 0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

ip: SIOCGIFFLAGS: No such device
Error getting hardware address for "dhcp": No such device

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

exiting.
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

ip: SIOCGIFFLAGS: No such device
ip: either "dev" is duplicate, or "permanent" is garbage
no link-local IPv6 address for dhcp

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging..

exiting.
0
Warning: overlayroot: debug is busted
done.
[5.649291] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +G

[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[Dave Chiluk]

** Tags added: regression-update

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[Dave Chiluk]

Dediff from 8.2 to 8.3.
http://launchpadlibrarian.net/286956415/initramfs-tools_0.122ubuntu8.2_0.122ubuntu8.3.diff.gz

** Tags added: cpc sts

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+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 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option

[Dave Chiluk]

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

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

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

Title:
  No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
  option

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  initramfs-tools 0.122ubuntu8.3 introduced a serious regression where
  networking is not initialized when the boot option "ip=dhcp" is
  provided. We are seeing this problem in AWS, but cannot confirm if
  this issue is specific to AWS or will occur with different hardware or
  in different environments.

  Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results
  in networking being configured.

  The issue does not occur with 0.122ubuntu8.2 or previous versions when
  "ip=dhcp" is set.

  AWS has no console so debugging is not a trivial task. I do have a
  console log with some output, and will update this bug shortly with
  it.

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