date:20160624

[Expired for gdb (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gdb (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  
/usr/bin/gdb:11:bfd_getl32:read_initial_length:decode_frame_entry_1:decode_frame_entry:dwarf2_build_frame_info

Status in gdb package in Ubuntu:
  Expired

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gdb.  This problem was most recently seen with version
  7.10-1ubuntu2, the problem page at
  https://errors.ubuntu.com/problem/22f5f037100c62a5bbcd15be4788969a49262727
  contains more details.

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

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

[Touch-packages] [Bug 1573995] Re: I just upgraded to 16.04 and I'm getting a AppArmor Message AppArmor Message Profile:usr?sbin/dnsmasq Operation: connect Name: run/dbus/system_bus_socket Denied:wr L

[Expired for apparmor (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apparmor (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  I just upgraded to 16.04  and I'm getting a AppArmor Message AppArmor
  Message Profile:usr?sbin/dnsmasq Operation: connect Name:
  run/dbus/system_bus_socket Denied:wr Logfile: /var/log/kern.log
  DebuggingApparmor" for Ubuntu and when I try and enter my encription
  phrase it says something like no shell. Also, when I try and check for
  updates I am told I'm up to date ? Please let me know how I can debug
  AppArmor ? Randy Adamson adamsonran...@gmail.com Thanks

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  I just upgraded to 16.04  and I'm getting a AppArmor Message AppArmor
  Message Profile:usr?sbin/dnsmasq Operation: connect Name:
  run/dbus/system_bus_socket Denied:wr Logfile: /var/log/kern.log
  DebuggingApparmor" for Ubuntu and when I try and enter my encription
  phrase it says something like no shell. Also, when I try and check for
  updates I am told I'm up to date ? Please let me know how I can debug
  AppArmor ? Randy Adamson adamsonran...@gmail.com Thanks

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

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

[Touch-packages] [Bug 1574097] Re: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Expired for sysvinit (Ubuntu) because there has been no activity for 60
days.]

** Changed in: sysvinit (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in sysvinit package in Ubuntu:
  Expired

Bug description:
  Like bug installation when upgrade from 14.04 (dell factory state) to
  ubuntu 16.04. I think, its kernel version problem. Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 22:29:07 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-23 (0 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: sysvinit
  Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

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

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

[Touch-packages] [Bug 1581206] Re: Cannot read the time and SIM information on a message

This bug was fixed in the package messaging-app -
0.1+16.10.20160624.1-0ubuntu1

---
messaging-app (0.1+16.10.20160624.1-0ubuntu1) yakkety; urgency=medium

  [ Gustavo Pichorim Boiko ]
  * Update colors, sizes and message bubbles to the latest spec. (LP:
#1581206)

  [ Michael Terry ]
  * Center contact name in the page header. (LP: #1547581)

  [ Tiago Salem Herrmann ]
  * Avoid text overlap in the main view. (LP: #1582630)
  * Don't run tests when cross compiling and don't use xvfb.

 -- Gustavo Pichorim Boiko   Fri, 24 Jun
2016 13:50:22 +

** Changed in: messaging-app (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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1581206

Title:
  Cannot read the time and SIM information on a message

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  Light gray on a white background with miniscule font size is illegible
  for many people

  See bug #1579704

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1581206/+subscriptions

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

[Touch-packages] [Bug 1547581] Re: Chat header text is not vertically aligned

This bug was fixed in the package messaging-app -
0.1+16.10.20160624.1-0ubuntu1

---
messaging-app (0.1+16.10.20160624.1-0ubuntu1) yakkety; urgency=medium

  [ Gustavo Pichorim Boiko ]
  * Update colors, sizes and message bubbles to the latest spec. (LP:
#1581206)

  [ Michael Terry ]
  * Center contact name in the page header. (LP: #1547581)

  [ Tiago Salem Herrmann ]
  * Avoid text overlap in the main view. (LP: #1582630)
  * Don't run tests when cross compiling and don't use xvfb.

 -- Gustavo Pichorim Boiko   Fri, 24 Jun
2016 13:50:22 +

** Changed in: messaging-app (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Chat header text is not vertically aligned

Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  Latest version, as of today. Click on a contact to enter chat view,
  notice the header text (the contact name) is lower than the back
  arrow. Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1547581/+subscriptions

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

[Touch-packages] [Bug 1582630] Re: Long text is written over timestamp in UI

This bug was fixed in the package messaging-app -
0.1+16.10.20160624.1-0ubuntu1

---
messaging-app (0.1+16.10.20160624.1-0ubuntu1) yakkety; urgency=medium

  [ Gustavo Pichorim Boiko ]
  * Update colors, sizes and message bubbles to the latest spec. (LP:
#1581206)

  [ Michael Terry ]
  * Center contact name in the page header. (LP: #1547581)

  [ Tiago Salem Herrmann ]
  * Avoid text overlap in the main view. (LP: #1582630)
  * Don't run tests when cross compiling and don't use xvfb.

 -- Gustavo Pichorim Boiko   Fri, 24 Jun
2016 13:50:22 +

** Changed in: messaging-app (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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1582630

Title:
  Long text is written over timestamp in UI

Status in Canonical System Image:
  In Progress
Status in messaging-app package in Ubuntu:
  Fix Released

Bug description:
  15.04 r329 (krillin)

  When receiving a text message from a person with a Very Long Name (see
  attachment), the text "Very Long Name" is written on top of the
  timestamp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1582630/+subscriptions

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

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

2016-06-24 Thread zhang sheng

** Summary changed:

- 15:10: bluetoothd reports "Not enough handles to register service" at start
+ 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" 
at start

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Touch-packages] [Bug 1596122] [NEW] apparmor denail on unity8-desktop

Public bug reported:

Fresh boot of unity8-desktop session
launched webbrowser
launched libreoffice
launched terminal, set GDK_BACKEND=mir & SDL_VIDEODRIVER=mir tried to launch 
Gedit with -- --desktop-file-hint
Flipped between apps abit, after a few minutes completely frozen, no cursor 
response
swtich VT, logged in to see unity8 pegged
tailed var/log/syslog and saw repeating of AA denial for browser

will attach copy i made of syslog before reboot
please let me know of any other files that might be useful

** Affects: webbrowser-app (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/1596122

Title:
  apparmor denail on unity8-desktop

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Fresh boot of unity8-desktop session
  launched webbrowser
  launched libreoffice
  launched terminal, set GDK_BACKEND=mir & SDL_VIDEODRIVER=mir tried to launch 
Gedit with -- --desktop-file-hint
  Flipped between apps abit, after a few minutes completely frozen, no cursor 
response
  swtich VT, logged in to see unity8 pegged
  tailed var/log/syslog and saw repeating of AA denial for browser

  will attach copy i made of syslog before reboot
  please let me know of any other files that might be useful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1596122/+subscriptions

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

[Touch-packages] [Bug 1596041] Re: corrupted text various elements on unity8

** Summary changed:

- corrupted text in launcher tooltip on unity8
+ corrupted text various elements on unity8

** Summary changed:

- corrupted text various elements on unity8
+ corrupted text various elements on unity8-desktop

** Description changed:

- Running unity8 desktop and on my open applications, I see the first letter 
corrupted in the action words "Unpin" and "Quit" (so "U" and "Q" respectively 
are what is corrupted.
+ Seen 2 varities of this problem.
+ 
+ #1) while running unity8 desktop and clicking for tooltip on launcher on my 
open applications, I see the first letter corrupted in the action words "Unpin" 
and "Quit" (so "U" and "Q" respectively are what is corrupted.
  Interesting is the Application's name is not corrupted.
+ This seems intermittent as well
+ 
+ #2) selecting "Shut down" provides the usual user prompt to cancel or power 
off, in this case only the "ff"s were corrupted
+ See attached image for this case

** Attachment added: "IMG_2167.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1596041/+attachment/4689967/+files/IMG_2167.JPG

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

Title:
  corrupted text various elements on unity8-desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  Seen 2 varities of this problem.

  #1) while running unity8 desktop and clicking for tooltip on launcher on my 
open applications, I see the first letter corrupted in the action words "Unpin" 
and "Quit" (so "U" and "Q" respectively are what is corrupted.
  Interesting is the Application's name is not corrupted.
  This seems intermittent as well

  #2) selecting "Shut down" provides the usual user prompt to cancel or power 
off, in this case only the "ff"s were corrupted
  See attached image for this case

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

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

[Touch-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

@Andrea

There are two tests I'd like you to run for me.

First, let's verify the baseline by flashing OTA10 ( pre-NM 1.1.93
landing ) on a spare krillin, and then set the WiFi connection to the
opposite as earlier suggested, this time setting ipv4.method to ignore.
This will validate that IPv6 connections were actually working ( vs.
just not causing DNS to fail ), even though the kernels lack support for
IPv6 peer addresses ( which NM 1.2x always uses when adding IPv6
addresses, and which in turn always fail ).

Second, there are three cases currently that I can see where NM adds
IPv6 addresses ( note, there are more possible, but these are the most
common when method=auto ):

 - NM always configures an IPv6 Link Local address with the peer set to
the "Any" address ( all zeros or :: ); the code states that a LL address
is always added for any method other than "ignore"

 - a VPN configuration specifies an IPv6 address ( in this case, our VPN
always sets the peer with the interface identifier part of the address
set to ::1/64 )

 - an address is received via RDP ( router discovery protocol ); this is
the case that happens when you associate to an AP that supports IPv6 and
method=auto

As I can't reproduce the last case ( my ISP doesn't support IPv6 yet ),
it would be great if you could run NetworkManager in the foreground with
an env var specified which triggers netlink debug messages.  This will
let me see what peer_address is being set when you connect to the work
AP.  If you want to send me these traces privately, that might be best.
Please use a recent rc-proposed image.

Here are the steps:

1. From system-settings::wifi, "forget" the access point

2. adb into the phone, and start an interactive sudo session:

# sudo -i

3. Stop NM

# stop network-manager

4. Run the script command to capture output:

# script nm-nl.out

5. Start NetworkManager in the foreground like this:

# NLCB=debug /usr/sbin/NetworkManager -n -d --log-level=debug --log-
domains=ip6,wifi,vpn

6. From the indicator, connect to the AP

7. Leave the connection up and NM running for 5-10m

8. Kill NM via Ctl-C

9. Exit the script via Ctl-D

10. Grab the script output and send it to me direct, or put on a
fileshare

Please let me know if you have any questions, or want to discuss before
you try any of this.

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580146/+subscriptions

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

[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

2016-06-24 Thread bpowell

Clean install, 16.04 64 bit...volume indicator keeps popping up. Also,
the volume position does not agree with my system volume position.

System volume may be at 50%, the volume indicator that keeps popping up
is around 80%.

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

Title:
Volume notification keeps popping up constantly(the notifyosd bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1126385] Re: Migrate to mulitarch indicators

2016-06-24 Thread Jeremy Bicha

See also bug 1126360.

The fix for that bug has resulted in different behavior on Ubuntu and
Debian.

workrave fails to build currently in yakkety because in Debian the indicator is 
stored in
 /usr/lib/*/indicators3/7/libworkrave.so
but in Yakkety, it's:
 /usr/lib/indicators3/7/libworkrave.so

https://launchpad.net/ubuntu/+source/workrave/1.10.15-1/+build/9731661

So please either fix Debian's libindicator or Ubuntu's so that they have
the same behavior. Personally, I prefer the multiarch directory.

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

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

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

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

Title:
  Migrate to mulitarch indicators

Status in libindicator:
  Confirmed
Status in Unity:
  Confirmed
Status in libindicator package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in workrave package in Ubuntu:
  Triaged

Bug description:
  Currently, the indicators are all non-multiarch for historical
  reasons.  We should enable multiarch indicators.

  1) Add a new variable to the libindicator .pc files called something like 
genericindicatordir which continues to be just /usr/lib
  2) Switch the indicatordir variable to a multiarch location (again -- we 
reverted away from that for bug 1126360)
  3) Have unity fallback to look in the genericindicatordir as well as the 
(now-) multiarch indicatordir for plugins
  4) As each indicator gets rebuilt, it will automatically migrate to 
multiarch, since "indicatordir" is now multiarch.  But old indicators will 
still work.

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

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

[Touch-packages] [Bug 1596117] [NEW] clicking enter/return hides keyboard and there is no way to show it again without clicking the lock button

2016-06-24 Thread Daniel

Public bug reported:

This obviously is a bug - once I click return/enter button on the keyboard when 
entering a passphrase, the keyboard is hidden and there is not way to show it 
again (unless i click the physical lock button and unlock it again).
It is not working on Meizu PRO 5 (Ubuntu Edition) OTA 11 version 112 (did not 
try 113 - it never boots up).

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

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

Title:
  clicking enter/return hides keyboard and there is no way to show it
  again without clicking the lock button

Status in libusermetrics package in Ubuntu:
  New

Bug description:
  This obviously is a bug - once I click return/enter button on the keyboard 
when entering a passphrase, the keyboard is hidden and there is not way to show 
it again (unless i click the physical lock button and unlock it again).
  It is not working on Meizu PRO 5 (Ubuntu Edition) OTA 11 version 112 (did not 
try 113 - it never boots up).

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

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

[Touch-packages] [Bug 1595421] Re: Location trusted prompt for Scopes shown immediately after the wizard

This bug was fixed in the package unity-scopes-shell -
0.5.7+16.10.20160624.2-0ubuntu1

---
unity-scopes-shell (0.5.7+16.10.20160624.2-0ubuntu1) yakkety; urgency=medium

  * Treat search triggered by registry changes as programmatic search
(i.e. not triggering location prompt). Enhanced debug messages. (LP:
#1595421)

 -- Pawel Stolowski   Fri, 24 Jun 2016
14:08:26 +

** Changed in: unity-scopes-shell (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 unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1595421

Title:
  Location trusted prompt for Scopes shown immediately after the wizard

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

Bug description:
  The trusted prompt for location access for Scopes is shown immediately
  after the wizard and not after first search or pull-to-refresh
  initiated by the user as intended. For some reason it happens only if
  wizard is involved in the boot sequence, and not if trusted prompt for
  location is just forced by removing .scopesLocationPrompt and trust
  store db.

  Looking at the unity8-dash.log file from the first boot after wiping
  the device, it seems that there is a forced refresh of scopes registry
  metadata early during the dash startup:

  [2016-04-23:07:04:42.593] Refreshing scope metadata
  [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope 
with id 'com.canonical.scopes.weatherchannel'"
  [2016-04-23:07:04:42.983] Dispatching search: 
"com.canonical.scopes.dashboard_dashboard" "" ""
  [2016-04-23:07:04:42.987] Enabling location updates

  This calls invalidateResults() and has the same effect as pull-to-
  refresh.

  This is most likely caused by the network becoming available & remote
  scopes getting fetched for the first time, signaling new scopes get
  available to the shell.

  To reproduce, reflash with --wipe or perform factory reset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+subscriptions

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

[Touch-packages] [Bug 1126385] Re: Migrate to mulitarch indicators

2016-06-24 Thread Jeremy Bicha

Isn't the fix just to revert bug 1126360 and fix Unity to look in both
the old and new directories?

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

Title:
  Migrate to mulitarch indicators

Status in libindicator:
  Confirmed
Status in Unity:
  Confirmed
Status in libindicator package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in workrave package in Ubuntu:
  Triaged

Bug description:
  Currently, the indicators are all non-multiarch for historical
  reasons.  We should enable multiarch indicators.

  1) Add a new variable to the libindicator .pc files called something like 
genericindicatordir which continues to be just /usr/lib
  2) Switch the indicatordir variable to a multiarch location (again -- we 
reverted away from that for bug 1126360)
  3) Have unity fallback to look in the genericindicatordir as well as the 
(now-) multiarch indicatordir for plugins
  4) As each indicator gets rebuilt, it will automatically migrate to 
multiarch, since "indicatordir" is now multiarch.  But old indicators will 
still work.

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

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

[Touch-packages] [Bug 1584367] Re: Samsung printer automatically diabled; cannot print

2016-06-24 Thread Till Kamppeter

I see that you access the printer through the URI

lpd://localhost

meaning that an LPD server (port 515) must be on your local machine. Are
you running some daemon on your machine to access the printer via a
proprietary communication protocol? Some software you got somehow from
Samsung (download or a CD supplied with the printer)?

You should try two possibilities:

1. If you use software from Samsung, use it completely, not use only the
communication daemon (if there is one) but also the PPD files supplied
by Samsung.

2. If you want to use the software supplied with Ubuntu Linux, run
system-config-printer (printer tool reachable from the System Settings)
and click "Add printer" at the top. Then a dialog appears in which
available printers are detected, first the local (USB, parallel, ...)
ones and after around 10 or 15 seconds the network printers (note that
your printer must be connected and turned on during this process).
Select your printer and then proceed through the wizard.

Please check andf try, especially (2).

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

Title:
  Samsung printer automatically diabled; cannot print

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Samsung ML-1660 laser printer is found and installed, but cannot print
  as it is automatically disabled. CUPS error log is filled with the
  following:

  E [21/May/2016:10:55:13 -0600] [cups-deviced] PID 26623
  (gutenprint52+usb) stopped with status 1!

  This behaviour is new in Xenial, it worked fine in Trusty.

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

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

[Touch-packages] [Bug 1596116] [NEW] no physical button to take picture/video

2016-06-24 Thread Daniel

Public bug reported:

This feature should obviously be integrated - taking a picture/video with a 
click of a physical button.
If it is/should be integrated - it is not working on Meizu PRO 5 (Ubuntu 
Edition) OTA 11 version 112 (did not try 113 - it never boots up).

** Affects: camera-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  no physical button to take picture/video

Status in camera-app package in Ubuntu:
  New

Bug description:
  This feature should obviously be integrated - taking a picture/video with a 
click of a physical button.
  If it is/should be integrated - it is not working on Meizu PRO 5 (Ubuntu 
Edition) OTA 11 version 112 (did not try 113 - it never boots up).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1596116/+subscriptions

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

[Touch-packages] [Bug 1592386] Re: [SRU] add links for obtaining management and support, fix documentation link in 10-help-text

2016-06-24 Thread Jeremy Bicha

I tested this on Ubuntu GNOME 16.04 LTS. I enabled proposed and
installed base-files and openssh-server.

The first link changes from
* Documentation:  https://help.ubuntu.com/ to
* Documentation:  https://help.ubuntu.com (without the trailing slash)

and the two new links show up.
The strings weren't translated when I tried French, but the old message wasn't 
either.
The message looks fine.

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

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

Title:
  [SRU] add links for obtaining management and support, fix
  documentation link in 10-help-text

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add links for obtaining management and support in 10-help-text, and
  fix the documentation link.  Should look very simple, concise, and
  clean, like this:

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

  == SRU ==

  [Impact]

  This impacts command line users of Ubuntu server (and desktop)
  systems.  When logging into an Ubuntu console (tty, ssh), pam displays
  a dynamically generated MOTD (message of the day).  The current
  message of the day on Ubuntu servers has a broken link for
  documentation.  We need to fix that.  We should also add simple,
  clean, friendly links on how to obtain support and remotely manage the
  system.

  [Test Case]

  Upgrade the base-files package, and then regenerate the MOTD using
  'sudo update-motd'.  The new motd should be printed to screen.

  [Regression Potential]

  None.  This change affects one simple shell script in /etc/update-
  motd.d/10-help-text

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1592386/+subscriptions

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

[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2

2016-06-24 Thread genepool

Oops.thanks Alberto. Thought it had been in progress and was waiting for
me.

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2016-06-24 Thread Cruz Fernandez

With kernel 4.4.0-24-generic the problem DID appeared on my machine

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

I have an external audio speaker connected to it. When I disconnect the
speaker and reconnect it again it stops working.
Even more, laptop audio stops working too. And after the reboot, I don't even
see any of the audio devices.

I've googled a lot and tried different fixes from forums with no luck.
After a while, I've accidentally discovered that putting the laptop to
the sleep mode and rebooting system after brings audio back to live.
Even more, if speakers were attached during this sleep-reboot
procedure, they are starting to work as well.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: kop3224 F...m pulseaudio
/dev/snd/controlC0: kop3224 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 12:17:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Встроенное аудио - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after
a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

2016-06-24 Thread Cruz Fernandez

After running the commands mentioned on #7 the problem seems to be
fixed! (I'm using kernel 4.4.0-27-generic, Ubuntu Unity 16.04) . Or
maybe an update fixed this problem?

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

Title:
[XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
while

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
I'm experiencing a strange behavior with a headphone jack on my
laptop.

However, after the next reboot speakers are not working again. And if
I will plug them out and in - problem with completely missing audio
returns.

P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
hibernation made me believe that it's somehow related. But after
uninstalling this package nothing really changed.

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

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

[Touch-packages] [Bug 1580917] Re: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all

2016-06-24 Thread Cruz Fernandez

Have you tried to suspend and resume the laptop? I've got the same
laptop and that kind of things bring back the sound.

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

Title:
  [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  All was working fine, then one day it goes silent when plugging in my
  speakers to the headphone socket, and forever after with something
  plugged in (internal speakers still work fine).

  Looking at pavucontrol and/or "Sound settings" under Gnome it shows
  that the sound should be playing on the Headphones output port - the
  VU meter is bouncing up and down ok, but it's silent. Pull out the
  wire (or select internal speakers for the Output) and the sound
  switches to the internal speakers OK.

  Last time this happened I fiddled for ages and then got distorted
  sound (sounds like some sort of cross-channel thing) and this only
  went a away with a complete re-install of Ubuntu (which I did to try
  to fix a separate bug but am not willing to do again!).

  I ran alsa-info.sh from the command line and uploaded the info. Here's
  the URL it gave me to share: http://www.alsa-
  project.org/db/?f=06...3f7ebb379442a7

  It's now happened again, having spent all Friday enjoying music,
  Monday morning turn on and silence! I've not done any upgrades since.

  
  I have tried completely reinstalling pulseaudio (based on suggestions found 
on the ubuntu wiki) to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.8-040408-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   7826 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 12 09:31:00 2016
  InstallationDate: Installed on 2016-04-22 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rich   7826 F...m pulseaudio
   /dev/snd/controlC0:  rich   7826 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-05-09T13:36:55.718771

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

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

[Touch-packages] [Bug 1562636] Re: battery percentage drops suddenly from 10% to 1%

2016-06-24 Thread Thomas Meyssonnier

At this time (OTA-11-20160524.1), the bug still persists.
Battery stayed fixed at 10% for hours, then dropped suddenly (the unit powered 
off before I could plug it, which takes less than 5 seconds usually).
I also have instances of the phone consuming its battery overnight, when it 
should be sleeping. Although maybe this is another issue.

A phone that can't be relied on will be difficult to accept by the
public, so could someone please look into this ?

Thanks, TM

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

Title:
  battery percentage drops suddenly from 10% to 1%

Status in upower package in Ubuntu:
  New

Bug description:
  The battery percentage drops from 10% to 1% and probably less in about a 
minute, even with phone locked and inactive.
  This has happened twice in a row already, and probably will systematically.
  Battery warning means I need to plug in instantly to avoid shutdown.
  There seems to be no way to calibrate battery measurements, or set a 
different warning level.
  I have no idea where to get log history for battery level, but I'll do it if 
someone gives me directions.
  Thanks,
  TM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: upower 0.99.2-2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Mon Mar 28 01:20:15 2016
  InstallationDate: Installed on 2016-02-17 (39 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160217-111536)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1547024] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise
  Problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure what's happening, my sound works great, there's just a
  static noise in the background that can get very annoying.

  Let me know if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.5.0-040500rc4-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zkanda 1519 F pulseaudio
  CurrentDesktop: MATE
  Date: Thu Feb 18 21:34:15 2016
  InstallationDate: Installed on 2016-02-16 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160216)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.204:bd11/12/2015: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.

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

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

[Touch-packages] [Bug 1570749] Re: Upgrade to 11.7 from May 2016

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

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

Title:
  Upgrade to 11.7 from May 2016

Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade to 11.6 from February 2016, see https://libav.org/ and
  https://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v11.6

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

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

[Touch-packages] [Bug 1574240] Re: package plymouth (not installed) failed to install/upgrade: conflicting packages - not installing plymouth

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

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

Title:
  package plymouth (not installed) failed to install/upgrade:
  conflicting packages - not installing plymouth

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  bug on "do-release-upgrade"

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: plymouth (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  Date: Sun Apr 24 15:01:57 2016
  DuplicateSignature: package:plymouth:(not installed):conflicting packages - 
not installing plymouth
  ErrorMessage: conflicting packages - not installing plymouth
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu2
  SourcePackage: plymouth
  Title: package plymouth (not installed) failed to install/upgrade: 
conflicting packages - not installing plymouth
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago)

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

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

[Touch-packages] [Bug 1594574] Re: package uuid-runtime 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 4

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  update install resets during install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Mon Jun 20 15:31:46 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 4
  InstallationDate: Installed on 2016-06-20 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1596101] [NEW] ubuntuBSD support

2016-06-24 Thread Jon Boden

Public bug reported:

Hi

Please could you update the .symbols file for ubuntuBSD support?

Here's a patch:

http://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
xenial/download/jon%40ubuntubsd.org-20160624215803-qem7wly2ey4810ej/libcolumbus.diff-20160624215559-t27ewosesk616k1t-1/libcolumbus.diff

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


** Tags: patch ubuntubsd

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

Title:
  ubuntuBSD support

Status in libcolumbus package in Ubuntu:
  New

Bug description:
  Hi

  Please could you update the .symbols file for ubuntuBSD support?

  Here's a patch:

  http://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
  
xenial/download/jon%40ubuntubsd.org-20160624215803-qem7wly2ey4810ej/libcolumbus.diff-20160624215559-t27ewosesk616k1t-1/libcolumbus.diff

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

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

[Touch-packages] [Bug 1578762] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  but i know no further about initramfs, i'm sure it pertains to ram
  drive creation, well..best guess anyhow

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   iucode-tool: Install
   intel-microcode: Install
   iucode-tool: Configure
   intel-microcode: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu May  5 18:13:46 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1578762/+subscriptions

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

[Touch-packages] [Bug 1536158] Re: Upgrade to 1.1.1 that was released in March 2016

** Changed in: alsa-driver-2.6.28-12 (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Upgrade to 1.1.1 that was released in March 2016

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver-2.6.28-12 package in Ubuntu:
  Confirmed

Bug description:
  Please, upgrade to 1.1.1 that was released in March 2016, see
  http://www.alsa-project.org/main/index.php/Changes_v1.1.0_v1.1.1

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

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

[Touch-packages] [Bug 1581302] Re: Monitor remains blanked with Intel Graphics

** Changed in: xfce4-settings (Ubuntu)
   Importance: Undecided => High

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

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the code is getting the CRTC error?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May 12 20:33:01 2016
  InstallationDate: Installed on 2016-05-08 (4 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  LightdmLog:
   [+80180.09s] DEBUG: Seat seat0 changes active session to 
   [+80189.53s] DEBUG: Seat seat0 changes active session to 64
   [+80222.67s] DEBUG: Seat seat0 changes active session to c4
   [+80222.67s] DEBUG: Session c4 is already active
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1561278] Re: internal sound card not detected HP X2

@ genepool

"In progress" mean that a developer is currently working on it.

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

** Changed in: alsa-driver (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1596099] [NEW] my update software do not work

2016-06-24 Thread krux

Public bug reported:

when i want to update al my software and operation sistem i get this error
 
,, the package system is broken..
,,Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f,,

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
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog: /dev/sda6: clean, 334380/2501856 files, 2230569/9997312 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Jun 25 00:40:55 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-24-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobility Radeon HD 4530 [103c:3628]
InstallationDate: Installed on 2016-06-19 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=11527bee-f9f6-4191-bf0c-4dfb8b300961 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/12/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.41
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3628
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 18.50
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.41:bd11/12/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.50:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
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: Sat Jun 25 00:26:02 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: radeon

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


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

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

Title:
  my update software do not work

Status in xorg package in Ubuntu:
  New

Bug description:
  when i want to update al my software and operation sistem i get this error
   
  ,, the package system is broken..
  ,,Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f,,

  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
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/sda6: clean, 334380/2501856 files, 2230569/9997312 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jun 25 00:40:55 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-24-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobility Radeon HD 4530

[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29 
  Device 44:5E:F3:B4:07:29
Name: BlueBuds X
Alias: BlueBuds X
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

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

[Touch-packages] [Bug 603128] Re: python-magic is incomplete on Ubuntu LTS?

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

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

Title:
  python-magic is incomplete on Ubuntu LTS?

Status in file package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file

  I'm running Ubuntu 10.04 LTS.

  I installed python-magic with: sudo apt-get install python-magic (the
  file that gets installed is python-magic_5.03-5ubuntu1_i386.deb)

  However, when I start Python (version 2.6.5) and I "import magic" and
  I then do "dir(magic)", it seems as though the module does not contain
  all the definitions that I can see on python-magic's github repo (i.e.
  the Ubuntu package seems outdated):

  ['MAGIC_APPLE', 'MAGIC_CHECK', 'MAGIC_COMPRESS', 'MAGIC_CONTINUE',
  'MAGIC_DEBUG', 'MAGIC_DEVICES', 'MAGIC_ERROR', 'MAGIC_MIME',
  'MAGIC_MIME_ENCODING', 'MAGIC_MIME_TYPE', 'MAGIC_NONE',
  'MAGIC_NO_CHECK_APPTYPE', 'MAGIC_NO_CHECK_CDF',
  'MAGIC_NO_CHECK_COMPRESS', 'MAGIC_NO_CHECK_ELF',
  'MAGIC_NO_CHECK_ENCODING', 'MAGIC_NO_CHECK_SOFT',
  'MAGIC_NO_CHECK_TAR', 'MAGIC_NO_CHECK_TEXT', 'MAGIC_NO_CHECK_TOKENS',
  'MAGIC_PRESERVE_ATIME', 'MAGIC_RAW', 'MAGIC_SYMLINK', '__doc__',
  '__file__', '__name__', '__package__', 'error', 'open']

  What's up? Am I doing something wrong?

  Joubert

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

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

[Touch-packages] [Bug 1596091] [NEW] command "less" not installed by default in Xenial

2016-06-24 Thread Dave Coleman

Public bug reported:

In previous version of Ubuntu "less" came by default, now it seems we
have to install it manually using apt-get. This is bad for programs like
"man" or "diff" that use less' scrolling capability.

Note: I'm using the Docker version of 16.04 which is built on ubuntu-
xenial-core-cloudimg-amd64-root.tar.gz as shown here:

https://github.com/tianon/docker-brew-ubuntu-
core/blob/f2682b59c32241b97e904af6691e997fa9c79c91/xenial/Dockerfile

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

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

Title:
  command "less" not installed by default in Xenial

Status in less package in Ubuntu:
  New

Bug description:
  In previous version of Ubuntu "less" came by default, now it seems we
  have to install it manually using apt-get. This is bad for programs
  like "man" or "diff" that use less' scrolling capability.

  Note: I'm using the Docker version of 16.04 which is built on ubuntu-
  xenial-core-cloudimg-amd64-root.tar.gz as shown here:

  https://github.com/tianon/docker-brew-ubuntu-
  core/blob/f2682b59c32241b97e904af6691e997fa9c79c91/xenial/Dockerfile

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

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

[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary

** Description changed:

  I have a folder with a bunch of subfolder and several hundred or
  thousands files, most of them PHP files (obviously text).
  
  I often use grep recursively, like this:
-   $ grep -R somepattern *
+   $ grep -R somepattern *
  
  Since the upgrade from 15.04 to 15.10, it often happens that a lot of text 
files are wrongly treated as binary. That means that, when a match is found, 
instead of getting the normal output which would show the file name and the 
matching line (with the matching substring highlighted), I get the bogus 
message:
-   binary file whatever.php matches
+   binary file whatever.php matches
  
  Just to be clear: in one invocation of grep -R, I get mixed output with
  a lot of matches shown in the expected way and quit e a few matches
  shown in the wrong way, even though ALL matching files are text files.
  
- 
  This worked as expected before the upgrade from 15.04 and 15.10.
  
+ This is a HUGE issue that makes it impossible to do everyday developing
+ work.
  
- This is a HUGE issue that makes it impossible to do everyday developing work.
+ Until you fix it, please roll back grep to the previous version, because
+ it is unusable.
  
- 
- Until you fix it, please f***ing roll back grep to the previous version, 
because this sh** is unusable.
+ Thanks for your attention 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grep 2.21-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:43:51 2016
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: grep
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)

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

Title:
  [15.10 REGRESSION] Randomly wrongly detects files as binary

Status in grep package in Ubuntu:
  Confirmed
Status in grep package in Debian:
  Fix Released

Bug description:
  I have a folder with a bunch of subfolder and several hundred or
  thousands files, most of them PHP files (obviously text).

  I often use grep recursively, like this:
    $ grep -R somepattern *

  Since the upgrade from 15.04 to 15.10, it often happens that a lot of text 
files are wrongly treated as binary. That means that, when a match is found, 
instead of getting the normal output which would show the file name and the 
matching line (with the matching substring highlighted), I get the bogus 
message:
    binary file whatever.php matches

  Just to be clear: in one invocation of grep -R, I get mixed output
  with a lot of matches shown in the expected way and quit e a few
  matches shown in the wrong way, even though ALL matching files are
  text files.

  This worked as expected before the upgrade from 15.04 and 15.10.

  This is a HUGE issue that makes it impossible to do everyday
  developing work.

  Until you fix it, please roll back grep to the previous version,
  because it is unusable.

  Thanks for your attention 

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: grep 2.21-2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 18 22:43:51 2016
  InstallationDate: Installed on 2013-10-11 (829 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: grep
  UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago)

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

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

[Touch-packages] [Bug 1373463] Re: [indicators] Impossible to disable cellular data from indicator

This bug was fixed in the package indicator-network -
0.8.0+16.10.20160622.1-0ubuntu1

---
indicator-network (0.8.0+16.10.20160622.1-0ubuntu1) yakkety; urgency=medium

  [ Pete ]
  * Add SIM management API.

  [ Antti Kaijanmäki ]
  * New Connectivity Service Private API for managing mobile data and
SIM cards. (LP: #1373463)

  [ Pete Woods ]
  * Improve logging (LP: #1580908)
  * add mobile data switch (LP: #1373463)

  [ Antti Kaijanmäki, Pete Woods ]
  * New Connectivity Service Private API for managing mobile data and
SIM cards. Tests. (LP: #1373463)

 -- Antti Kaijanmäki   Wed, 22 Jun 2016 09:49:15
+

** Changed in: indicator-network (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: ubuntu-system-settings (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 indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1373463

Title:
  [indicators] Impossible to disable cellular data from indicator

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Triaged
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  I was wondering : Why it isn't possible to disable data from the
  network indicator ? Probably with a switch button that offer the
  choice between no data or data activated (with the last data activated
  state (2g only or 2G,3G,4G).

  Why this ? Because it's the first setting to change to save battery,
  and probably one of the most used (I asked around me, everyone agreed
  they would prefer that over Wi-Fi if only one was possible).

  I think it's stupid to go to the settings app for the most common
  action (and very frustrating). Of course, this also apply for the
  battery setting page (that already contain Wi-Fi, GPS, Bluetooth and
  brightness settings).

  I asked that on the phone ML, I've been invited to file a wishlist bug
  there to "help" designers with next iteration of network indicator. So
  here it is !

  [1] : mailing list discussion with already some support to this idea :
  https://lists.launchpad.net/ubuntu-phone/msg09910.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+subscriptions

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

[Touch-packages] [Bug 1373463] Re: [indicators] Impossible to disable cellular data from indicator

This bug was fixed in the package ubuntu-system-settings -
0.4+16.10.20160624-0ubuntu1

---
ubuntu-system-settings (0.4+16.10.20160624-0ubuntu1) yakkety; urgency=medium

  [ Antti Kaijanmäki ]
  * use Connectivity API for cellular data and roaming control. (LP:
#1373463)

 -- Ken VanDine   Fri, 24 Jun 2016 13:42:47
+

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

Title:
  [indicators] Impossible to disable cellular data from indicator

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Triaged
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  I was wondering : Why it isn't possible to disable data from the
  network indicator ? Probably with a switch button that offer the
  choice between no data or data activated (with the last data activated
  state (2g only or 2G,3G,4G).

  Why this ? Because it's the first setting to change to save battery,
  and probably one of the most used (I asked around me, everyone agreed
  they would prefer that over Wi-Fi if only one was possible).

  I think it's stupid to go to the settings app for the most common
  action (and very frustrating). Of course, this also apply for the
  battery setting page (that already contain Wi-Fi, GPS, Bluetooth and
  brightness settings).

  I asked that on the phone ML, I've been invited to file a wishlist bug
  there to "help" designers with next iteration of network indicator. So
  here it is !

  [1] : mailing list discussion with already some support to this idea :
  https://lists.launchpad.net/ubuntu-phone/msg09910.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+subscriptions

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

[Touch-packages] [Bug 1580908] Re: Sim lock screen doesn't appear after restarting the device

This bug was fixed in the package indicator-network -
0.8.0+16.10.20160622.1-0ubuntu1

---
indicator-network (0.8.0+16.10.20160622.1-0ubuntu1) yakkety; urgency=medium

  [ Pete ]
  * Add SIM management API.

  [ Antti Kaijanmäki ]
  * New Connectivity Service Private API for managing mobile data and
SIM cards. (LP: #1373463)

  [ Pete Woods ]
  * Improve logging (LP: #1580908)
  * add mobile data switch (LP: #1373463)

  [ Antti Kaijanmäki, Pete Woods ]
  * New Connectivity Service Private API for managing mobile data and
SIM cards. Tests. (LP: #1373463)

 -- Antti Kaijanmäki   Wed, 22 Jun 2016 09:49:15
+

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

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

Title:
   Sim lock screen doesn't appear after restarting the device

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Fix Released
Status in ofono package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  From https://bugs.launchpad.net/zhongshan/+bug/1572886

  current build number: 4
  device name: turbo
  channel: ubuntu-touch/rc/meizu.en
  last update: 2016-04-19 10:38:50
  version version: 4
  version ubuntu: 20160418
  version device: 20160412-d272a77
  version custom: 20160324-945-18-69

  Steps:
  1.turn on sim pin lock
  2.reboot the device
  3.swipe to dismiss the greeter

  Actual result:
  phone lock screen is displayed

  Expected result:
  sim lock screen should appear before the phone lock screen

  It also happens sometimes on arale without any pattern to reproduce,
  just random on reboot.

  =

  After debugging it seems that this is caused by ofono removing the
  modems in the middle of the unlock process. You can see the difference
  for Turbo and Krillin below.

  Log for Turbo: http://paste.ubuntu.com/1147/

  Log for Krillin: http://paste.ubuntu.com/16675431/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580908/+subscriptions

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

[Touch-packages] [Bug 1595421] Re: Location trusted prompt for Scopes shown immediately after the wizard

** 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 unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1595421

Title:
  Location trusted prompt for Scopes shown immediately after the wizard

Status in Canonical System Image:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  The trusted prompt for location access for Scopes is shown immediately
  after the wizard and not after first search or pull-to-refresh
  initiated by the user as intended. For some reason it happens only if
  wizard is involved in the boot sequence, and not if trusted prompt for
  location is just forced by removing .scopesLocationPrompt and trust
  store db.

  Looking at the unity8-dash.log file from the first boot after wiping
  the device, it seems that there is a forced refresh of scopes registry
  metadata early during the dash startup:

  [2016-04-23:07:04:42.593] Refreshing scope metadata
  [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope 
with id 'com.canonical.scopes.weatherchannel'"
  [2016-04-23:07:04:42.983] Dispatching search: 
"com.canonical.scopes.dashboard_dashboard" "" ""
  [2016-04-23:07:04:42.987] Enabling location updates

  This calls invalidateResults() and has the same effect as pull-to-
  refresh.

  This is most likely caused by the network becoming available & remote
  scopes getting fetched for the first time, signaling new scopes get
  available to the shell.

  To reproduce, reflash with --wipe or perform factory reset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+subscriptions

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

[Touch-packages] [Bug 1593378] Re: crash in slap_bv2ad using repeated tags

2016-06-24 Thread Eric Desrochers

** Tags removed: sts-sponsor

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

Title:
  crash in slap_bv2ad using repeated tags

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Trusty:
  Fix Committed

Bug description:
  [SRU JUSTIFICATION]

  [Impact]

  The effect of the bug on users is that the program (slapd) terminated
  with signal SIGSEGV, Segmentation fault when ldapsearch tries to query
  using multiple language tags.

  GDB output:
  ...
  Core was generated by `/usr/sbin/slapd -h ldap://:389 ldap://:389/ 
ldapi:/// -g o'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  ...

  (gdb) bt
  #0 __strncasecmp_l_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
  #1 0x7f674ae8cab2 in slap_bv2ad (bv=bv@entry=0x7f6741e0e830, 
ad=ad@entry=0x7f6741e0e848, text=text@entry=0x7f6741e0f980) at 
../../../../servers/slapd/ad.c:268
  ...

  In frame #1 the 'tags' struct is corrupt.

  Line #272 checks for duplication and jumps to the done label (line
  #294) when a duplicate is found. The code increases 'ntags' without
  filling in the tags struct with values. In later iterations this could
  lead to copying and using uninitialised memory.

  [Test Case]

  One way to reproduce the issue :

  $ ldapsearch -D
  
"cn=,dc=,dc=,dc="
  -x -W -b
  
"dc=,dc=,dc="
  "cn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de
  ;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-
  de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;;lang-de
  ;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-
  de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn
  ;lang-de;lang-encn;lang-de;lang-encn;lang-de;;lang-de;lang-encn;lang-
  de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn
  ;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-
  encn;lang-de;lang-encn;lang-de;;lang-de;lang-encn;lang-de;lang-encn
  ;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-
  encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de
  ;lang-encn;lang-de"

  Explanation :

  Reference:
  http://manpages.ubuntu.com/cgi-bin/search.py?q=ldapsearch

  -D binddn
  Use the Distinguished Name binddn to bind to the LDAP directory.
  For SASL binds, the server is expected to ignore this value.

  -x
  Use simple authentication instead of SASL.

  -W
  Prompt  for  simple  authentication.   This  is  used instead of
  specifying the password on the command line.

  -b searchbase
  Use searchbase as the starting point for the search  instead  of the default.

  [Regression Potential]

  The patch is already in place in Debian & Wily and late Ubuntu release
  version.

  A hotfix has been tested by the user that originally reported the issue.
  The hotfix solves the issue.

  [Other Info]

  Upstream OpenLDAP Bug :
  http://www.openldap.org/its/index.cgi/Software%20Bugs?id=7941;page=9

  Upstream OpenLDAP Commit  :
  af8f1e0 ITS#7941 fix for repeated tags

  Upstream OpenLDAP Commit Web  :
  http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=af8f1e0

  (The commit has been introduced first in upstream branch :
  OPENLDAP_REL_ENG_2_4_40~6)

  [Original Description]

  Core was generated by `/usr/sbin/slapd -h ldap://:389 ldap://:389/ 
ldapi:/// -g o'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  __strncasecmp_l_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
  210   ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory.
  (gdb) bt
  #0  __strncasecmp_l_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
  #1  0x7f674ae8cab2 in slap_bv2ad (bv=bv@entry=0x7f6741e0e830, 
ad=ad@entry=0x7f6741e0e848, text=text@entry=0x7f6741e0f980) at 
../../../../servers/slapd/ad.c:268
  #2  0x7f674ae4d235 in get_filter (op=op@entry=0x7f672c000a80, 
ber=, filt=filt@entry=0x7f672c000af0, 
text=text@entry=0x7f6741e0f980)
  at ../../../../servers/slapd/filter.c:190
  #3  0x7f674ae4b985 in do_search (op=0x7f672c000a80, rs=0x7f6741e0f960) at 
../../../../servers/slapd/search.c:127
  #4  0x7f674ae496dc in connection_operation (ctx=ctx@entry=0x7f6741e0fb90, 
arg_v=arg_v@entry=0x7f672c000a80) at ../../../../servers/slapd/connection.c:1150
  #5  0x7f674ae49a40 in connection_read_thread (ctx=0x7f6741e0fb90, 
argv=0x19) at ../../../../servers/slapd/connection.c:1286
  #6  0x7f674a9a7aba in ?? () from 
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2
  #7  0x7f67498dc182 in start_thread (arg=0x7f6741e10700) at 
pthread_create.c:312
  #8  0x7f674960947d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

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

-- 
Mailing list:

[Touch-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

2016-06-24 Thread Cindy Quach

Is there a reason why this wasn't backported to Trusty initramfs-tools?
We just saw an incident of this with 4.2.0.36 on Trusty

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Trusty:
  Invalid
Status in initramfs-tools source package in Trusty:
  Triaged
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  Won't Fix

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Touch-packages] [Bug 1596069] Re: recent LightDM changes stop XApps from launching in Unity 8

2016-06-24 Thread Stephen M. Webb

** Also affects: unity8-desktop-session
   Importance: Undecided
   Status: New

** Changed in: unity8-desktop-session
   Status: New => In Progress

** Changed in: unity8-desktop-session
   Importance: Undecided => Critical

** Changed in: unity8-desktop-session
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Also affects: unity8-desktop-session (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity8-desktop-session (Ubuntu)
   Status: New => In Progress

** Changed in: unity8-desktop-session (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity8-desktop-session (Ubuntu)
 Assignee: (unassigned) => Stephen M. Webb (bregma)

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

Title:
  recent LightDM changes stop XApps from launching in Unity 8

Status in unity8-desktop-session:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress
Status in unity8-desktop-session package in Ubuntu:
  In Progress

Bug description:
  Changes made to LightDM to fix bug #1583624 cause Unity 8
  configuration to fail in its upstart job, which causes the symptom
  that XApps no longer launch.  It may cause other problems as well.

  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-desktop-session/+bug/1596069/+subscriptions

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

[Touch-packages] [Bug 1590833] Re: Update to bug fix release 1.4.14

2016-06-24 Thread Hans Joachim Desserud

Looks like 1.4.14 has been packaged in Debian, but it will probably need
a merge since the Ubuntu package includes some additional patches.

** Tags added: needs-debian-merge

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

Title:
  Update to bug fix release 1.4.14

Status in modemmanager package in Ubuntu:
  New

Bug description:
  ModemManager 1.4.14
  ---
  This is a new bugfix release of ModemManager.

  Among other things fixed:

   * Core: improved several AT response parsers (+CREG, +CGDCONT, +CPMS...).
   * Core: explicitly disconnect bearer before removing it.
   * 3GPP: allow LAC/CID updates while registering.
   * QMI: don't assume LAC/CID updates are always given in system indications.
   * QMI: don't add APN auth settings if user/pass not given.
   * QMI: load SIM operator id and name with "NAS home network"
   * QMI: power-cycle reset functionality implemented.
   * Telit: added udev rules for Telite LE910 V2.
   * Telit: implemented modem reset & power down.
   * Telit: implemented unlock retries loading.
   * Telit: implemented supported/current bands loading/setting.
   * Telit: implemented supported/current modes loading/setting.
   * Blacklist: ignored proxmark3.
   * and some other minor fixes...

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

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

[Touch-packages] [Bug 1588127] Re: Phone abandons incoming call

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

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

Title:
  Phone abandons incoming call

Status in Canonical System Image:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete
Status in telephony-service package in Ubuntu:
  New

Bug description:
  I just received five incoming calls but I couldn't answer any of them.
  In each case the phone started vibrating, then after a while the ring
  tone started and the answer buttons were displayed, but before I had a
  chance to answer, the phone seemed to give up and go back to sleep.
  Then I could see the green envelope meaning that I had missed a call.

  The fifth time was me trying from another phone.  In this case it
  seemed that the line was still ringing, but again I was unable to
  answer the call.

  After rebooting the phone, I can now answer incoming calls no problem.
  So it seems this is some bad state that the phone gets into after a
  while.

  I've previously had problems with my phone's cover blocking the light
  sensor and preventing me answering calls.  However in this case I was
  expecting the call and had prepared by opening the cover, so this
  can't be the problem.

  Phone is an MX4.  OS Ubuntu 15.04 (OTA-10.1).

  FYI, this was a job interview, with a CTO who was phoning from New
  York.  I'd already had to delay a week after missing the first
  appointment due to the exact same problem.  I've been barely
  tolerating Ubuntu Phone's bugs up to now, but this is the final straw.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588127/+subscriptions

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

[Touch-packages] [Bug 1596069] Re: recent LightDM changes stop XApps from launching in Unity 8

** Branch linked: lp:~bregma/unity8/lp-1596069

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

Title:
  recent LightDM changes stop XApps from launching in Unity 8

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Changes made to LightDM to fix bug #1583624 cause Unity 8
  configuration to fail in its upstart job, which causes the symptom
  that XApps no longer launch.  It may cause other problems as well.

  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

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

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

[Touch-packages] [Bug 1596076] Re: SIM pin screen is incorrectly resized after wrong PIN

2016-06-24 Thread Víctor R . Ruiz

** Attachment added: "screenshot20160624_202817717.png"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1596076/+attachment/4689905/+files/screenshot20160624_202817717.png

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

Title:
  SIM pin screen is incorrectly resized after wrong PIN

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Test case.
  - With SIM card inserted, reboot the phone.
  - After boot, cancel the SIM pin screen.
  - Pass through lock screen.
  - Open network indicator.
  - Tap to unlock SIM.
  - Introduce an incorrect pin.

  Expected result.
  - SIM pin screen is full screen.

  Actual result.
  - SIM pin screen is not correctly resized, the top of the indicator menu can 
be seen.

  current build number: 767
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1596076/+subscriptions

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

[Touch-packages] [Bug 1596076] [NEW] SIM pin screen is incorrectly resized after wrong PIN

2016-06-24 Thread Víctor R . Ruiz

Public bug reported:

Test case.
- With SIM card inserted, reboot the phone.
- After boot, cancel the SIM pin screen.
- Pass through lock screen.
- Open network indicator.
- Tap to unlock SIM.
- Introduce an incorrect pin.

Expected result.
- SIM pin screen is full screen.

Actual result.
- SIM pin screen is not correctly resized, the top of the indicator menu can be
seen.

current build number: 767
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed

** Affects: canonical-devices-system-image
Importance: Undecided
Status: New

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

** Tags: qa-regression

** Attachment added: "screenshot20160624_203334704.png"

https://bugs.launchpad.net/bugs/1596076/+attachment/4689904/+files/screenshot20160624_203334704.png

** Also affects: canonical-devices-system-image
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/1596076

Title:
SIM pin screen is incorrectly resized after wrong PIN

Status in Canonical System Image:
New
Status in unity8 package in Ubuntu:
New

Bug description:
Test case.
- With SIM card inserted, reboot the phone.
- After boot, cancel the SIM pin screen.
- Pass through lock screen.
- Open network indicator.
- Tap to unlock SIM.
- Introduce an incorrect pin.

Expected result.
- SIM pin screen is full screen.

Actual result.
- SIM pin screen is not correctly resized, the top of the indicator menu can
be seen.

current build number: 767
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1596076/+subscriptions

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

[Touch-packages] [Bug 1596069] [NEW] recent LightDM changes stop XApps from launching in Unity 8

2016-06-24 Thread Stephen M. Webb

Public bug reported:

Changes made to LightDM to fix bug #1583624 cause Unity 8 configuration
to fail in its upstart job, which causes the symptom that XApps no
longer launch.  It may cause other problems as well.

The root of the problem is that the variable MIR_SOCKET is no longer
present in the enviroment when Unity 8 is started.

** Affects: unity8 (Ubuntu)
 Importance: High
 Assignee: Stephen M. Webb (bregma)
 Status: In Progress

** Description changed:

- Changes made to LightDM to fix #1583624 cause Unity 8 configuration to
- fail in its upstart job, which causes the symptom that XApps no longer
- launch.  It may cause other problems as well.
+ Changes made to LightDM to fix bug #1583624 cause Unity 8 configuration
+ to fail in its upstart job, which causes the symptom that XApps no
+ longer launch.  It may cause other problems as well.
  
  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

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

Title:
  recent LightDM changes stop XApps from launching in Unity 8

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Changes made to LightDM to fix bug #1583624 cause Unity 8
  configuration to fail in its upstart job, which causes the symptom
  that XApps no longer launch.  It may cause other problems as well.

  The root of the problem is that the variable MIR_SOCKET is no longer
  present in the enviroment when Unity 8 is started.

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

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

[Touch-packages] [Bug 1595421] Re: Location trusted prompt for Scopes shown immediately after the wizard

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

** Changed in: canonical-devices-system-image
Milestone: None => 12

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

Title:
  Location trusted prompt for Scopes shown immediately after the wizard

Status in Canonical System Image:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  The trusted prompt for location access for Scopes is shown immediately
  after the wizard and not after first search or pull-to-refresh
  initiated by the user as intended. For some reason it happens only if
  wizard is involved in the boot sequence, and not if trusted prompt for
  location is just forced by removing .scopesLocationPrompt and trust
  store db.

  Looking at the unity8-dash.log file from the first boot after wiping
  the device, it seems that there is a forced refresh of scopes registry
  metadata early during the dash startup:

  [2016-04-23:07:04:42.593] Refreshing scope metadata
  [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope 
with id 'com.canonical.scopes.weatherchannel'"
  [2016-04-23:07:04:42.983] Dispatching search: 
"com.canonical.scopes.dashboard_dashboard" "" ""
  [2016-04-23:07:04:42.987] Enabling location updates

  This calls invalidateResults() and has the same effect as pull-to-
  refresh.

  This is most likely caused by the network becoming available & remote
  scopes getting fetched for the first time, signaling new scopes get
  available to the shell.

  To reproduce, reflash with --wipe or perform factory reset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+subscriptions

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

[Touch-packages] [Bug 1584367] Re: Samsung printer automatically diabled; cannot print

2016-06-24 Thread crottl

Hiya Till, here's the logged info you requested; hope you find it
useful.

Cheers, Chris


** Attachment added: "error.log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1584367/+attachment/4689886/+files/error.log

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

Title:
  Samsung printer automatically diabled; cannot print

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Samsung ML-1660 laser printer is found and installed, but cannot print
  as it is automatically disabled. CUPS error log is filled with the
  following:

  E [21/May/2016:10:55:13 -0600] [cups-deviced] PID 26623
  (gutenprint52+usb) stopped with status 1!

  This behaviour is new in Xenial, it worked fine in Trusty.

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

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

[Touch-packages] [Bug 1551811] Re: First trust prompt leads to reboot (arale, midori)

2016-06-24 Thread Pat McGowan

This will block midori rc

** Summary changed:

- Opening the camera for the first time leads to reboot
+ First trust prompt leads to reboot (arale, midori)

** No longer affects: camera-app

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

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

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

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

Title:
  First trust prompt leads to reboot (arale, midori)

Status in arale:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in Midori:
  Confirmed
Status in Mir:
  Invalid
Status in Telegram app:
  Invalid
Status in trust-store:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  --

  Same happens with the following steps:

  1. Flash device (arale) with

  $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
  proposed/meizu.en --recovery-image 
  --bootstrap

  2. Wait until flash process is done
  3. Go through first-start wizard
  4. Pass tutorial
  5. Directly launch camera-app, approve trust-prompt

  Repeat 1-5 multiple times and you will see a frozen device after step
  5. You can verify it happened due to a kernel panic mentioned in
  comment #7.

  You can reset the trust db entry for the camera app using :
  $rm -rf ~/.local/share/CameraService
  $restart cameraservice-trust-stored

  Run the following to get the command line for all threads so you can match 
the pid from the kmsg later (see below):
  ps H -eo 'pid tid cmd:250 comm'

  To verify it was really the kernel panic run

  $ sudo cat /proc/last_kmsg

  once the device has rebooted.

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

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

[Touch-packages] [Bug 1052936] Re: Progress bar in "Progress" section has a hole in it

2016-06-24 Thread franco_bez

Excelent work :-)

On my System ( Linux B513 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8
19:27:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ) the bug is fixed.

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

Title:
  Progress bar in "Progress" section has a hole in it

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in ubuntu-themes source package in Xenial:
  Fix Committed

Bug description:
  Problem occurs with: Ambiance, Radiance
  Does not occur with: Adwaita

  [ Description, QA ]

  Open System Monitor, switch to "File Systems".

  What you see: Progress bars with orange borders but white middles

  What you should see: All colour

  [ Fix ]

  Don't use the border images - use CSS to colour the borders and
  backgrounds.

  [ Regression potential ]

  Could break styling of progress bars elsewhere; look in gtk3-widget-
  factory, unity-control-center and anywhere else you can think of to
  make sure they all still look good.

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

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

[Touch-packages] [Bug 1596056] [NEW] output of invoke-rc.d for systemd units un-debuggable on failure

2016-06-24 Thread Steve Langasek

Public bug reported:

When invoke-rc.d is called on a systemd system, if the unit fails to
start, you get output like:

Created symlink 
/etc/systemd/system/multi-user.target.wants/openafs-fileserver.service → 
/lib/systemd/system/openafs-fileserver.service.
Job for openafs-fileserver.service failed because the control process exited 
with error code.
See "systemctl status openafs-fileserver.service" and "journalctl -xe" for 
details.
invoke-rc.d: initscript openafs-fileserver, action "start" failed.
dpkg: error processing package openafs-fileserver (--configure):
 subprocess installed post-installation script returned error exit status 1

The output shown here comes from systemctl itself, and is usually fine.
The admin who ran systemctl can run those other commands to debug.

However, when called by invoke-rc.d, this output is usually seen only in
a log file; maybe submitted in a bug report, maybe attached to something
like an autopkgtest:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-yakkety/yakkety/armhf/o/openafs/20160624_174535@/log.gz

By the time someone looks at this log output, it is often too late to
run those commands in order to debug the failure.

invoke-rc.d should call these commands for us on systemd unit failure,
so that the relevant debugging information is included in the log where
it can help.

We don't want to call 'journalctl -xe', which might leak information
into the log from other jobs, but 'journalctl -x -u ' may be
appropriate.

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

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

Title:
  output of invoke-rc.d for systemd units un-debuggable on failure

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  When invoke-rc.d is called on a systemd system, if the unit fails to
  start, you get output like:

  Created symlink 
/etc/systemd/system/multi-user.target.wants/openafs-fileserver.service → 
/lib/systemd/system/openafs-fileserver.service.
  Job for openafs-fileserver.service failed because the control process exited 
with error code.
  See "systemctl status openafs-fileserver.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript openafs-fileserver, action "start" failed.
  dpkg: error processing package openafs-fileserver (--configure):
   subprocess installed post-installation script returned error exit status 1

  The output shown here comes from systemctl itself, and is usually
  fine.  The admin who ran systemctl can run those other commands to
  debug.

  However, when called by invoke-rc.d, this output is usually seen only
  in a log file; maybe submitted in a bug report, maybe attached to
  something like an autopkgtest:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/armhf/o/openafs/20160624_174535@/log.gz

  By the time someone looks at this log output, it is often too late to
  run those commands in order to debug the failure.

  invoke-rc.d should call these commands for us on systemd unit failure,
  so that the relevant debugging information is included in the log
  where it can help.

  We don't want to call 'journalctl -xe', which might leak information
  into the log from other jobs, but 'journalctl -x -u ' may
  be appropriate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1596056/+subscriptions

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

[Touch-packages] [Bug 1590099] Re: Need to support pointer confinement

2016-06-24 Thread Daniel d'Andrada

** Changed in: qtmir (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  Need to support pointer confinement

Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in mir package in Ubuntu:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  We need to support pointer confinement set by the client. This way we
  can generate relative mouse events on a surface without the cursor
  being able to leave the edge of the window.

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

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

[Touch-packages] [Bug 1596050] [NEW] switching windows requires 2 clicks on unity8 desktop

Public bug reported:

Just saw this occur, but then problem seems to have gone away.

I had multiple windows open on unity8 desktop session, non full screen -
using my laptops cursor/mouse I attempted to toggle between windows by
selecting their surface.

It didn't matter which app, for some time, it required 2 clicks to
change focus/topmost app.

** 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/1596050

Title:
  switching windows requires 2 clicks on unity8 desktop

Status in unity8 package in Ubuntu:
  New

Bug description:
  Just saw this occur, but then problem seems to have gone away.

  I had multiple windows open on unity8 desktop session, non full screen
  - using my laptops cursor/mouse I attempted to toggle between windows
  by selecting their surface.

  It didn't matter which app, for some time, it required 2 clicks to
  change focus/topmost app.

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

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

[Touch-packages] [Bug 1592447] Re: camera startup time regression

2016-06-24 Thread Florian Boucault

Re 2): improvements specific to the camera app are landing soon. See
https://code.launchpad.net/~phablet-team/camera-
app/staging/+merge/298329

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

Title:
  camera startup time regression

Status in Canonical System Image:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Please see 
  http://reqorts.qa.ubuntu.com/reports/qa/performance/dashboard/index.html

  the camera time recently jumped in startup time, but this did not seem
  to be something caused by a common component when comparing to other
  apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1592447/+subscriptions

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

[Touch-packages] [Bug 1574240] Re: package plymouth (not installed) failed to install/upgrade: conflicting packages - not installing plymouth

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

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

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

Title:
  package plymouth (not installed) failed to install/upgrade:
  conflicting packages - not installing plymouth

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  bug on "do-release-upgrade"

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: plymouth (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  Date: Sun Apr 24 15:01:57 2016
  DuplicateSignature: package:plymouth:(not installed):conflicting packages - 
not installing plymouth
  ErrorMessage: conflicting packages - not installing plymouth
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu2
  SourcePackage: plymouth
  Title: package plymouth (not installed) failed to install/upgrade: 
conflicting packages - not installing plymouth
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (0 days ago)

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

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

[Touch-packages] [Bug 1596041] [NEW] corrupted text in launcher tooltip on unity8

Public bug reported:

Running unity8 desktop and on my open applications, I see the first letter 
corrupted in the action words "Unpin" and "Quit" (so "U" and "Q" respectively 
are what is corrupted.
Interesting is the Application's name is not corrupted.

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


** Tags: unity8-desktop

** Tags added: unity8-desktop

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

Title:
  corrupted text in launcher tooltip on unity8

Status in unity8 package in Ubuntu:
  New

Bug description:
  Running unity8 desktop and on my open applications, I see the first letter 
corrupted in the action words "Unpin" and "Quit" (so "U" and "Q" respectively 
are what is corrupted.
  Interesting is the Application's name is not corrupted.

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

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

[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in libertine apps does not work

this is really annoying trying to use unity8 as a daily driver

** Changed in: libertine (Ubuntu)
   Importance: Medium => High

** No longer affects: unity8 (Ubuntu)

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => High

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

Title:
  keyboard autorepeat in libertine apps & gtk-mir does not work

Status in X.Org X server:
  New
Status in libertine package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  How to reproduce:
   * Install xterm in libertine
   * Start xterm from the "Xapps" scope
   * Wait for xterm to appear
   * Press and hold a key
   * See how it only appears once and not multiple times as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1591356/+subscriptions

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

[Touch-packages] [Bug 1595711] Re: HexChat delete/backspace key doesn't repeat running on unity8

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

for sure, duping

** This bug has been marked a duplicate of bug 1591356
   keyboard autorepeat in libertine apps does not work

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

Title:
  HexChat delete/backspace key doesn't repeat running on unity8

Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  running, latest/greatest unity8/mir desktop - have libertine install of 
HexChat.
  simply noticed the repeat of backspace does not occur (it's labeled as 
"delete" key on my mac)

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

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

[Touch-packages] [Bug 1572576] Re: Taking a photo not working / xenial

2016-06-24 Thread Florian Boucault

** Changed in: qtubuntu-camera (Ubuntu)
   Status: New => Fix Released

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

Title:
  Taking a photo not working / xenial

Status in Canonical System Image:
  Fix Committed
Status in camera-app package in Ubuntu:
  Fix Released
Status in qtubuntu-camera package in Ubuntu:
  Fix Released

Bug description:
  It seems taking a photo (or video) buttons are dimmed for some reason
  on Qt 5.6.

  Update to summarize comments:
  - On mako + xenial, trying to use camera (easily/always?) leads to a reboot
  - On krillin + xenial, viewfinder works but taking the photo button is dimmed.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1572576/+subscriptions

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2016-06-24 Thread zanonmark

Tested with 12.04.5, kernel was "Linux ubuntu 3.13.0-32-generic
#57~precise1-Ubuntu SMP Tue Jul 15 03:51:20 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux".

Please let me know if you need further information.

Thanks,
MZ

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

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 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:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-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
  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: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1578190] Re: New text input visuals very heavy

** 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 ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1578190

Title:
  New text input visuals very heavy

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  Since the UITK introduced the new text input focus ring, it also
  replaced the shaded Shape with a flat outline. That outline seems
  overly heavy (see attachment).

  The only visual spec of this that I saw (remarked as "old") is
  http://bit.ly/1TtDOqu ([1] says "spec is outdated", too).

  [1] https://sites.google.com/a/canonical.com/apps-and-platform-
  team/3-platform/toolkit/16-text-input

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qml-module-ubuntu-components 1.3.1960+16.04.20160428.1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  4 14:23:21 2016
  SourcePackage: ubuntu-ui-toolkit
  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/1578190/+subscriptions

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

[Touch-packages] [Bug 1596028] Re: Dangling entries in list of available devices

2016-06-24 Thread flohack

** Attachment added: "Details of dangling device #2"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+attachment/4689862/+files/screenshot20160624_183209829%5B1%5D.png

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

Title:
  Dangling entries in list of available devices

Status in bluez package in Ubuntu:
  New

Bug description:
  Accidently I seem to have paired with foreign devices, which I do not
  own, nor do I know exactly where it happened. Maybe I was just curious
  if the BQ phone would pair with them. However, now it is not possible
  to remove the entries again.

  Those entries are Roku Player and some TV device...

  See attached screenshots. The delete button is gray and klicking does
  nothing. Please help, the entries are really annyoing!

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

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

[Touch-packages] [Bug 1596028] Re: Dangling entries in list of available devices

2016-06-24 Thread flohack

** Attachment added: "Details of dangling device #1"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1596028/+attachment/4689861/+files/screenshot20160624_183214382%5B1%5D.png

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

Title:
  Dangling entries in list of available devices

Status in bluez package in Ubuntu:
  New

Bug description:
  Accidently I seem to have paired with foreign devices, which I do not
  own, nor do I know exactly where it happened. Maybe I was just curious
  if the BQ phone would pair with them. However, now it is not possible
  to remove the entries again.

  Those entries are Roku Player and some TV device...

  See attached screenshots. The delete button is gray and klicking does
  nothing. Please help, the entries are really annyoing!

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

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

[Touch-packages] [Bug 1596028] [NEW] Dangling entries in list of available devices

2016-06-24 Thread flohack

Public bug reported:

Accidently I seem to have paired with foreign devices, which I do not
own, nor do I know exactly where it happened. Maybe I was just curious
if the BQ phone would pair with them. However, now it is not possible to
remove the entries again.

Those entries are Roku Player and some TV device...

See attached screenshots. The delete button is gray and klicking does
nothing. Please help, the entries are really annyoing!

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

** Attachment added: "Overview of dangling devices"

https://bugs.launchpad.net/bugs/1596028/+attachment/4689860/+files/screenshot20160624_183849140%5B1%5D.png

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

Title:
Dangling entries in list of available devices

Status in bluez package in Ubuntu:
New

Bug description:
Accidently I seem to have paired with foreign devices, which I do not
own, nor do I know exactly where it happened. Maybe I was just curious
if the BQ phone would pair with them. However, now it is not possible
to remove the entries again.

Those entries are Roku Player and some TV device...

See attached screenshots. The delete button is gray and klicking does
nothing. Please help, the entries are really annyoing!

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

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

[Touch-packages] [Bug 1595485] Re: packages to remove from yakkety

2016-06-24 Thread LocutusOfBorg

** Also affects: ppc64-diag (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16
  
  no reverse dependencies I can see
- 2) insighttoolkit 
+ 2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)
  
  just removing vmtk/powerpc should allow its removal too
  
- 3) vtk 
+ 3) vtk
  Superseded by vtk6
  
  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)
  
  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
- old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1) 
+ old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  
  removed in Debian too
  
  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore
  
  6) singular [armhf]
  removed in Debian too
  
  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480
  
  8) mame [ppc64el]
  sandness on that arch, removed in Debian
  
- thanks
+ 9) ppc64-diag-doc [NBS]
+ missing build on amd64: ppc64-diag-doc (from 2.7.1-2)
+ missing build on arm64: ppc64-diag-doc (from 2.7.1-2)
+ missing build on armhf: ppc64-diag-doc (from 2.7.1-2)
+ missing build on i386: ppc64-diag-doc (from 2.7.1-2)
+ missing build on s390x: ppc64-diag-doc (from 2.7.1-2) 
+ 
+ this is due to the move of the doc package from arch:all to arch:any (it
+ doesn't build on debian / amd64 all builder

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

Title:
  packages to remove from yakkety

Status in fpc package in Ubuntu:
  New
Status in insighttoolkit package in Ubuntu:
  New
Status in libpng package in Ubuntu:
  New
Status in mame package in Ubuntu:
  New
Status in pepperflashplugin-nonfree package in Ubuntu:
  New
Status in ppc64-diag package in Ubuntu:
  New
Status in samtools package in Ubuntu:
  New
Status in singular package in Ubuntu:
  New
Status in vtk package in Ubuntu:
  New

Bug description:
  (NOTE: all of them are gone from Debian)
  1) libpng.
  Superseded by libpng16

  no reverse dependencies I can see
  2) insighttoolkit
  Superseded by insighttoolkit4
  it doesn't build on powerpc, so we have to remove binaries here
  (sorry, but Debian maintains only amd64 and i386, and we can't maintain all 
the others including powerpc)

  just removing vmtk/powerpc should allow its removal too

  3) vtk
  Superseded by vtk6

  needs vmtk migration
  and fslview removal or demote to proposed.
  Debian broke it, because it is already broken, and it has little fix in time 
probability
  (probably we will remove in Debian soon)

  4) samtools
  old binaries left on armhf: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on powerpc: libbam-dev, samtools (from 0.1.19-1ubuntu1)
  old binaries left on s390x: libbam-dev, samtools (from 0.1.19-1ubuntu1)

  removed in Debian too

  5) pepperflashplugin-nonfree [i386]
  please remove on i386 (removed in Debian too)
  upstream is not supporting it, so it can't be downloaded/installed on i386 
anymore

  6) singular [armhf]
  removed in Debian too

  7) fpc [powerpc]
  powerpc sadness with glib 2.23
  https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/1562480

  8) mame [ppc64el]
  sandness on that arch, removed in Debian

  9) ppc64-diag-doc [NBS]
  missing build on amd64: ppc64-diag-doc (from 2.7.1-2)
  missing build on arm64: ppc64-diag-doc (from 2.7.1-2)
  missing build on armhf: ppc64-diag-doc (from 2.7.1-2)
  missing build on i386: ppc64-diag-doc (from 2.7.1-2)
  missing build on s390x: ppc64-diag-doc (from 2.7.1-2) 

  this is due to the move of the doc package from arch:all to arch:any
  (it doesn't build on debian / amd64 all builder

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

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

[Touch-packages] [Bug 1596001] [NEW] WiFi password prompt empty when reconnecting

Public bug reported:

This might be on purpose (so we don't leak the password on a locked
phone), but compared to unity7 the WiFi password prompt does not come
pre-filled with the password.

This makes it very annoying when you have a flaky WiFi connection, OTOH
you can cancel the prompt and click on the network in the indicator and
have NM try and reconnect with the previously set password.

Filing this so we can have a record of why it is like that.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: indicator-network 0.7.1+15.04.20160511-0ubuntu1
Uname: Linux 3.10.100-user-01769-g42b9fe3 aarch64
ApportVersion: 2.17.2-0ubuntu1.3touch1
Architecture: armhf
Date: Fri Jun 24 11:35:45 2016
InstallationDate: Installed on 2016-06-24 (0 days ago)
InstallationMedia: Ubuntu 15.04 - armhf (20160624-085657)
SourcePackage: indicator-network
UpgradeStatus: No upgrade log present (probably fresh install)
indicator-network.log:
 void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const QDBusObjectPath&) 
: Tried to remove access point  "/org/freedesktop/NetworkManager/AccessPoint/9" 
 that has not been added.
 
 (process:5074): GLib-GIO-WARNING **: Error releasing name 
com.canonical.indicator.network: Połączenie jest zamknięte
 void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const QDBusObjectPath&) 
: Tried to remove access point  
"/org/freedesktop/NetworkManager/AccessPoint/11"  that has not been added.
 void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const QDBusObjectPath&) 
: Tried to remove access point  
"/org/freedesktop/NetworkManager/AccessPoint/12"  that has not been added.
upstart.indicator-network-secret-agent.log:
 QVariantDictMap agent::SecretAgent::GetSecrets(const QVariantDictMap&, const 
QDBusObjectPath&, const QString&, const QStringList&, uint) 
"/org/freedesktop/NetworkManager/Settings/11" "802-11-wireless-security" () 3
 QVariantDictMap agent::SecretAgent::GetSecrets(const QVariantDictMap&, const 
QDBusObjectPath&, const QString&, const QStringList&, uint) Requesting secret 
from user
 virtual notify::Notification::~Notification() Closing notification: 1
 virtual notify::Notification::~Notification() "Client ':1.68' tried to close 
notification 1, which it does not own or does not exist."
upstart.indicator-network.log:
 void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const QDBusObjectPath&) 
: Tried to remove access point  "/org/freedesktop/NetworkManager/AccessPoint/9" 
 that has not been added.
 
 (process:5074): GLib-GIO-WARNING **: Error releasing name 
com.canonical.indicator.network: Połączenie jest zamknięte
 void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const QDBusObjectPath&) 
: Tried to remove access point  
"/org/freedesktop/NetworkManager/AccessPoint/11"  that has not been added.
 void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const QDBusObjectPath&) 
: Tried to remove access point  
"/org/freedesktop/NetworkManager/AccessPoint/12"  that has not been added.

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


** Tags: apport-bug armhf vivid

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

Title:
  WiFi password prompt empty when reconnecting

Status in indicator-network package in Ubuntu:
  New

Bug description:
  This might be on purpose (so we don't leak the password on a locked
  phone), but compared to unity7 the WiFi password prompt does not come
  pre-filled with the password.

  This makes it very annoying when you have a flaky WiFi connection,
  OTOH you can cancel the prompt and click on the network in the
  indicator and have NM try and reconnect with the previously set
  password.

  Filing this so we can have a record of why it is like that.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-network 0.7.1+15.04.20160511-0ubuntu1
  Uname: Linux 3.10.100-user-01769-g42b9fe3 aarch64
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Fri Jun 24 11:35:45 2016
  InstallationDate: Installed on 2016-06-24 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160624-085657)
  SourcePackage: indicator-network
  UpgradeStatus: No upgrade log present (probably fresh install)
  indicator-network.log:
   void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const 
QDBusObjectPath&) : Tried to remove access point  
"/org/freedesktop/NetworkManager/AccessPoint/9"  that has not been added.
   
   (process:5074): GLib-GIO-WARNING **: Error releasing name 
com.canonical.indicator.network: Połączenie jest zamknięte
   void nmofono::wifi::WifiLinkImpl::Private::ap_removed(const 
QDBusObjectPath&) : Tried to remove access point  
"/org/freedesktop/NetworkManager/Acces

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

Hello Nathaniel, or anyone else affected,

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

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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!

** Changed in: bash (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

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

Title:
  Please add ~/.local/bin to the default $PATH

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

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1595869] Re: SRU: apply four upstream bug fixes in bash for 16.04 LTS

Hello Matthias, or anyone else affected,

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

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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!

** Also affects: bash (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: bash (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  SRU: apply four upstream bug fixes in bash for 16.04 LTS

Status in bash package in Ubuntu:
  Invalid
Status in bash source package in Xenial:
  Fix Committed

Bug description:
  Proposing to apply the four upstream changes to the bash package for
  xenial, plus the addition to the PATH variable.

* Apply upstream patches 043 - 046. Fixes:
  - When the lastpipe option is enabled, the last component can contain
nested pipelines and cause a segmentation fault under
certain circumstances.
  - A typo prevents the `compat42' shopt option from working as intended.
  - If a file open attempted as part of a redirection fails because it is
interrupted by a signal, the shell needs to process any pending traps
to allow the redirection to be canceled.
  - An incorrect conversion from an indexed to associative array can result
in a core dump.
* Add $HOME/.local/bin to PATH, and add the user's home directories
  unconditionally to the path, so that they are available without
  a new login. Closes: #820856, LP: #1588562.

  The rationale for the PATH change is explained in LP: #1588562.

  Verification: The package builds, passes it's tests, and for new users
  you'll find $HOME/.local/bin in PATH.

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

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

[Touch-packages] [Bug 1593378] Re: crash in slap_bv2ad using repeated tags

Hello Eric, or anyone else affected,

Accepted openldap into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openldap/2.4.31-1+nmu2ubuntu8.3 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!

** Changed in: openldap (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  crash in slap_bv2ad using repeated tags

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Trusty:
  Fix Committed

Bug description:
  [SRU JUSTIFICATION]

  [Impact]

  The effect of the bug on users is that the program (slapd) terminated
  with signal SIGSEGV, Segmentation fault when ldapsearch tries to query
  using multiple language tags.

  GDB output:
  ...
  Core was generated by `/usr/sbin/slapd -h ldap://:389 ldap://:389/ 
ldapi:/// -g o'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  ...

  (gdb) bt
  #0 __strncasecmp_l_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
  #1 0x7f674ae8cab2 in slap_bv2ad (bv=bv@entry=0x7f6741e0e830, 
ad=ad@entry=0x7f6741e0e848, text=text@entry=0x7f6741e0f980) at 
../../../../servers/slapd/ad.c:268
  ...

  In frame #1 the 'tags' struct is corrupt.

  Line #272 checks for duplication and jumps to the done label (line
  #294) when a duplicate is found. The code increases 'ntags' without
  filling in the tags struct with values. In later iterations this could
  lead to copying and using uninitialised memory.

  [Test Case]

  One way to reproduce the issue :

  $ ldapsearch -D
  
"cn=,dc=,dc=,dc="
  -x -W -b
  
"dc=,dc=,dc="
  "cn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de
  ;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-
  de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;;lang-de
  ;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-
  de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn
  ;lang-de;lang-encn;lang-de;lang-encn;lang-de;;lang-de;lang-encn;lang-
  de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn
  ;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-
  encn;lang-de;lang-encn;lang-de;;lang-de;lang-encn;lang-de;lang-encn
  ;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-
  encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de
  ;lang-encn;lang-de"

  Explanation :

  Reference:
  http://manpages.ubuntu.com/cgi-bin/search.py?q=ldapsearch

  -D binddn
  Use the Distinguished Name binddn to bind to the LDAP directory.
  For SASL binds, the server is expected to ignore this value.

  -x
  Use simple authentication instead of SASL.

  -W
  Prompt  for  simple  authentication.   This  is  used instead of
  specifying the password on the command line.

  -b searchbase
  Use searchbase as the starting point for the search  instead  of the default.

  [Regression Potential]

  The patch is already in place in Debian & Wily and late Ubuntu release
  version.

  A hotfix has been tested by the user that originally reported the issue.
  The hotfix solves the issue.

  [Other Info]

  Upstream OpenLDAP Bug :
  http://www.openldap.org/its/index.cgi/Software%20Bugs?id=7941;page=9

  Upstream OpenLDAP Commit  :
  af8f1e0 ITS#7941 fix for repeated tags

  Upstream OpenLDAP Commit Web  :
  http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=af8f1e0

  (The commit has been introduced first in upstream branch :
  OPENLDAP_REL_ENG_2_4_40~6)

  [Original Description]

  Core was generated by `/usr/sbin/slapd -h ldap://:389 ldap://:389/ 
ldapi:/// -g o'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  __strncasecmp_l_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
  210   ../sysdeps/x86_64/multiarch/../strcmp.S: No such file or directory.
  (gdb) bt
  #0  __strncasecmp_l_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
  #1  0x7f674ae8cab2 in slap_bv2ad (bv=bv@entry=0x7f6741e0e830,

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

Note for the trusty update: This includes the SRU for bug 1568485 which
is v-failed, so the current package cannot be accepted. Either upload an
ubuntu12.6 without the changes from 12.5, or coordinate with the
uploader of the previous SRU to fix/update/merge the changes.

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

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

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

Bug description:
  [Impact]

   * Infiniband users relying on DHCP can't use DHCP relay.

  [Test Case]

   * Comment #13
   * Mellanox has tested themselves. 
   * Clear way of knowing if fix worked (tcpdump).

  [Regression Potential]

   * Only related to Infiniband.
   * Infiniband support could stop working (unlikely, already tested).

  [Other Info]

  None

  [ Original Description ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

  DHCP client is sending discover with Unicast type request for the
  offer, in this configuration of IB to ETH through a relay we need the
  type to be broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  DHCP CLIENT (IPoIB)
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

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

[Touch-packages] [Bug 1052936] Re: Progress bar in "Progress" section has a hole in it

Hello Matthew, or anyone else affected,

Accepted ubuntu-themes into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
themes/14.04+16.04.20160621-0ubuntu1 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!

** Changed in: ubuntu-themes (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

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

Title:
  Progress bar in "Progress" section has a hole in it

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in ubuntu-themes source package in Xenial:
  Fix Committed

Bug description:
  Problem occurs with: Ambiance, Radiance
  Does not occur with: Adwaita

  [ Description, QA ]

  Open System Monitor, switch to "File Systems".

  What you see: Progress bars with orange borders but white middles

  What you should see: All colour

  [ Fix ]

  Don't use the border images - use CSS to colour the borders and
  backgrounds.

  [ Regression potential ]

  Could break styling of progress bars elsewhere; look in gtk3-widget-
  factory, unity-control-center and anywhere else you can think of to
  make sure they all still look good.

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

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

[Touch-packages] [Bug 1101881] Re: software-properties-gtk crashed with TypeError in new(): object of type 'NoneType' has no len()

Hello Ryland, or anyone else affected,

Accepted software-properties into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.20.2 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!

** Changed in: software-properties (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  software-properties-gtk crashed with TypeError in __new__(): object of
  type 'NoneType' has no len()

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Wily:
  Triaged
Status in software-properties source package in Xenial:
  Fix Committed

Bug description:
  [ Impact ]
  Users on architectures other than amd64 of i386 trying to use 
software-properties to choose a server from which to download software will 
receive a crash after closing the "Choose a Download Server" dialog.

  [ Test Case ]
  1) Be on a not i386 or amd64 system (or be on amd64 and use a hack found in 
comment #11)
  2) Launch software-properties-gtk
  3) In the Download from: drop-down choose "Other..."
  4) Observe an empty list of download servers
  5) Click "Cancel"
  6) Observe a traceback in the terminal which you launched 
software-properties-gtk

  Wit the version of software-properties-gtk from -proposed you will not
  receive a crash.

  ---

  on nexus 7

  ProblemType: CrashDistroRelease: Ubuntu 13.04
  Package: software-properties-gtk 0.92.13
  Uname: Linux 3.1.10-8-nexus7 armv7l
  ApportVersion: 2.8-0ubuntu2
  Architecture: armhf
  CrashCounter: 1
  Date: Sat Jan 19 14:44:31 2013
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2013-01-16 (3 days ago)
  InstallationMedia: Ubuntu Raring Ringtail (development branch) - armhf 
(20130115-15:18)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', 
'2']SourcePackage: software-properties
  Title: software-properties-gtk crashed with TypeError in __new__(): object of 
type 'NoneType' has no len()
  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/software-properties/+bug/1101881/+subscriptions

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

[Touch-packages] [Bug 1585689] Re: [webapp-container] The header bar does not hides anymore

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 12

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

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

Title:
  [webapp-container] The header bar does not hides anymore

Status in Canonical System Image:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  In rc-proposed, the header bar in the webapp container does not hide
  at all when sliding down in long scroll applications such as facebook
  or twitter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1585689/+subscriptions

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

[Touch-packages] [Bug 1563398] Re: Set the front camera as the default for video media requests

This bug was fixed in the package webbrowser-app -
0.23+16.10.20160620-0ubuntu1

---
webbrowser-app (0.23+16.10.20160620-0ubuntu1) yakkety; urgency=medium

  * Set the front camera as the default for video media requests (LP:
#1563398)
  * Handle theme color change and properly update browsing widgets (LP:
#1567430)
  * Properly propagate touchscreen detection flag (LP: #1585689)
  * Print help when no app-id is present (LP: #1591306)

 -- Alexandre Abreu   Mon, 20 Jun 2016
15:08:41 +

** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1563398

Title:
  Set the front camera as the default for video media requests

Status in Canonical System Image:
  Fix Committed
Status in webapps-sprint:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  At the moment, the selected camera (in form factors having multiple
  ones) defaults to the back camera which does not work very well for
  cases like hangouts, the container and the browser should default to
  the front camera.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563398/+subscriptions

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

[Touch-packages] [Bug 1585689] Re: [webapp-container] The header bar does not hides anymore

This bug was fixed in the package webbrowser-app -
0.23+16.10.20160620-0ubuntu1

---
webbrowser-app (0.23+16.10.20160620-0ubuntu1) yakkety; urgency=medium

  * Set the front camera as the default for video media requests (LP:
#1563398)
  * Handle theme color change and properly update browsing widgets (LP:
#1567430)
  * Properly propagate touchscreen detection flag (LP: #1585689)
  * Print help when no app-id is present (LP: #1591306)

 -- Alexandre Abreu   Mon, 20 Jun 2016
15:08:41 +

** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1585689

Title:
  [webapp-container] The header bar does not hides anymore

Status in Canonical System Image:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  In rc-proposed, the header bar in the webapp container does not hide
  at all when sliding down in long scroll applications such as facebook
  or twitter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1585689/+subscriptions

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

[Touch-packages] [Bug 1567430] Re: [webapp-container] Controls in header need same theme-color adjustments that text gets

This bug was fixed in the package webbrowser-app -
0.23+16.10.20160620-0ubuntu1

---
webbrowser-app (0.23+16.10.20160620-0ubuntu1) yakkety; urgency=medium

  * Set the front camera as the default for video media requests (LP:
#1563398)
  * Handle theme color change and properly update browsing widgets (LP:
#1567430)
  * Properly propagate touchscreen detection flag (LP: #1585689)
  * Print help when no app-id is present (LP: #1591306)

 -- Alexandre Abreu   Mon, 20 Jun 2016
15:08:41 +

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [webapp-container] Controls in header need same theme-color
  adjustments that text gets

Status in webapps-sprint:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  This is a follow-on issue to bug 1548573.

  In that bug, text color now is a more responsive to the background
  color of the header, chosen by "theme-color" in CSS.

  But the controls of the header (back, forward, refresh) stay grey.
  Which is hard to see on some colors.  They should become the same
  color as the header text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1567430/+subscriptions

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

[Touch-packages] [Bug 1595414] Re: Awful generic selection for zh in Firefox

2016-06-24 Thread Gunnar Hjalmarsson

Please note that if you use a Chinese locale, it's 69-language-selector-
zh-??.conf which is effective, not 65-fonts-arphic-*.conf.

As regards the latter, one thought is to change it so UMing is preferred
over UKai. Another thought is to drop the sans-serif items in 65-fonts-
arphic-*.conf. Probably we'd need to test to see how Firefox behaves
with those changes.

Also, this is reasonably not a trusty specific issue. It would be good
if we could study this in the current development release (yakkety)
first, and then backport if we figure out something better.

@Aron: Any thoughts?

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

Title:
  Awful generic selection for zh in Firefox

Status in fonts-arphic-ukai package in Ubuntu:
  New
Status in fonts-arphic-uming package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in fonts-arphic-ukai source package in Trusty:
  New
Status in fonts-arphic-uming source package in Trusty:
  New
Status in language-selector source package in Trusty:
  New

Bug description:
  In https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/fonts-
  arphic-ukai/wily/revision/6, UMing and UKai are set as generics for
  fonts. However, this set of generics is completely intolerable --
  setting UKai as a generic is like setting Zapfino and/or Comic Sans as
  a system-wise generic, while UMing as a normal (just a bit thin) serif
  sounds a bit better. This yields terrible results on non-Chinese
  systems with non-Chinese lang-attributed websites, like Twitter, on
  Ubuntu 14.04 LTS after installing Chinese language support which
  includes the two arphic fonts mentioned in this report.

  This problem is similar to
  https://bugs.freedesktop.org/show_bug.cgi?id=20911, a long-standing
  system-global fontconfig non-latin fallback problem. See also bug
  #1560548 where these generic settings are considered as 'redundant'
  and proposed for deletion. I have mentioned a third-person report
  about such selection in #1560548 previously, but I have just
  reproduced this bug by myself by installing zh-cn support by mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1595414/+subscriptions

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

[Touch-packages] [Bug 1595461] Re: API file uses namespace inconsistently

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/listsAndNameSpaces

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

Title:
  API file uses namespace inconsistently

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

Bug description:
  With the recent move of c++ types from Ubuntu.Components plugin into
  UbuntuToolkit and embedding them into a namespace caused API dump to
  use the namespace inconsistently. In some places has a "." in other
  places a "::".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1595461/+subscriptions

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

[Touch-packages] [Bug 1591306] Re: [webapp-container] --help needs --app-id

This bug was fixed in the package webbrowser-app -
0.23+16.10.20160620-0ubuntu1

---
webbrowser-app (0.23+16.10.20160620-0ubuntu1) yakkety; urgency=medium

  * Set the front camera as the default for video media requests (LP:
#1563398)
  * Handle theme color change and properly update browsing widgets (LP:
#1567430)
  * Properly propagate touchscreen detection flag (LP: #1585689)
  * Print help when no app-id is present (LP: #1591306)

 -- Alexandre Abreu   Mon, 20 Jun 2016
15:08:41 +

** Changed in: webbrowser-app (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [webapp-container] --help needs --app-id

Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  To reproduce:

  $ webapp-container --help
  The application has been launched with no explicit or system provided app id. 
An application id can be set by using the --app-id command line parameter and 
setting it to a unique application specific value or using the APP_ID 
environment variable.

  Workaround:

  webapp-container --help --app-id=foobar
  Usage: webapp-container [-h|--help] ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1591306/+subscriptions

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

[Touch-packages] [Bug 1595989] [NEW] Ubuntu 15.10 crashes with Kernel later than 4.2.0_30

2016-06-24 Thread Florian

Public bug reported:

Since the installation of the kernel 4.2.0_34 and later, my Ubuntu does not 
work properly.
It hangs during start, or short after login. I found this message in the 
system.log:

Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970170] 
[ cut here ]
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970188] WARNING: 
CPU: 0 PID: 3142 at /build/linux-qsdjht/linux-4.2.0/fs/block_dev.c:57 
__blkdev_put+0xbf/0x250()
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970191] Modules 
linked in: nls_iso8859_1 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) drbg ansi_cprng ctr ccm binfmt_misc rfcomm bnep snd_hrtimer 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common ath3k 
btusb arc4 ath9k videodev btrtl btbcm ath9k_common btintel bluetooth ath9k_hw 
media intel_rapl ath snd_hda_codec_hdmi mac80211 intel_soc_dts_iosf 
intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic coretemp 
snd_hda_intel snd_hda_codec punit_atom_debug cfg80211 snd_hda_core 
crct10dif_pclmul snd_hwdep hp_wmi sparse_keymap crc32_pclmul snd_pcm 
snd_seq_midi snd_seq_midi_event input_leds joydev snd_rawmidi serio_raw cryptd 
snd_seq kvm_intel snd_seq_device snd_timer kvm snd mei_txe lpc_ich soundcore 
shpchp mei wmi hp_wireless intel_smartconnect mac_hid parport_pc ppdev lp 
parport autofs4 uas usb_storage i915 psmouse i2c_algo_bit drm_kms_helper r8169 
drm mii ahci libahci video
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970290] CPU: 0 
PID: 3142 Comm: umount Tainted: G   OE   4.2.0-38-generic #45-Ubuntu
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970293] Hardware 
name: Hewlett-Packard HP 250 G2 Notebook PC/2190, BIOS F.1A 12/04/2014
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970297]  
0286 e8188e49 880178d97d98 817f250e
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970303]  
 81cbfce8 880178d97dd8 8107cae6
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970308]  
 880078dd5380 880078dd54f8 880078dd5470
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970313] Call Trace:
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970323]  
[] dump_stack+0x63/0x81
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970331]  
[] warn_slowpath_common+0x86/0xc0
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970335]  
[] warn_slowpath_null+0x1a/0x20
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970339]  
[] __blkdev_put+0xbf/0x250
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970344]  
[] blkdev_put+0x50/0x120
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970350]  
[] kill_block_super+0x41/0x70
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970354]  
[] deactivate_locked_super+0x43/0x70
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970358]  
[] deactivate_super+0x64/0x70
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970364]  
[] cleanup_mnt+0x43/0x90
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970368]  
[] __cleanup_mnt+0x12/0x20
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970373]  
[] task_work_run+0x73/0x90
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970381]  
[] do_notify_resume+0x69/0x70
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970386]  
[] int_signal+0x12/0x17
Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970390] ---[ end 
trace 427c1d4aa86831c9 ]---

With the Kernel 4.2.0_30 I can work without any problems.

Here some additional Informations: 
florian@florian-HP-250-G2-Notebook-PC:~$ lsb_release -rd
Description:Ubuntu 15.10
Release:15.10

Hardware: HP-250-G2-Notebook

** Affects: openal-soft (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu 15.10 crashes with Kernel later than 4.2.0_30

Status in openal-soft package in Ubuntu:
  New

Bug description:
  Since the installation of the kernel 4.2.0_34 and later, my Ubuntu does not 
work properly.
  It hangs during start, or short after login. I found this message in the 
system.log:

  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970170] 
[ cut here ]
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970188] WARNING: 
CPU: 0 PID: 3142 at /build/linux-qsdjht/linux-4.2.0/fs/block_dev.c:57 
__blkdev_put+0xbf/0x250()
  Jun 23 17:52:34 florian-HP-250-G2-Notebook-PC kernel: [  305.970191] Modules 
linked in: nls_iso8859_1 pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) 
vboxdrv(OE) drbg ansi_cprng ctr ccm binfmt_misc

[Touch-packages] [Bug 1563398] Re: Set the front camera as the default for video media requests

** 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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1563398

Title:
  Set the front camera as the default for video media requests

Status in Canonical System Image:
  Fix Committed
Status in webapps-sprint:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  At the moment, the selected camera (in form factors having multiple
  ones) defaults to the back camera which does not work very well for
  cases like hangouts, the container and the browser should default to
  the front camera.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563398/+subscriptions

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

[Touch-packages] [Bug 1595986] Re: [1951F5G, Analog Devices AD1981, Green Line Out, Left] Pulseaudio fails to detect card

2016-06-24 Thread grofaty

By the way, I already reported a bug 1594570, but got no reply...

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

Title:
  [1951F5G, Analog Devices AD1981, Green Line Out, Left] Pulseaudio
  fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I saw a help to report audio problem with command:
  ubuntu-bug -s audio

  I have no sound in Ubuntu 16.04. In System Settings | Sound there is
  empty list o output and input devices (see attachment). I did clean
  install couple of weeks back. Previously I have got installed Ubuntu
  14.04 with zero problems with sound.

  I don't know how to fix this problem.
  By the way, I can fear audio well e.g. in youtube using Firefox browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Jun 24 16:48:11 2016
  InstallationDate: Installed on 2016-06-03 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Title: [1951F5G, Analog Devices AD1981, Green Line Out, Left] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2006
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ET62WW (1.07 )
  dmi.board.name: 1951F5G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1951F5G
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1595986] [NEW] [1951F5G, Analog Devices AD1981, Green Line Out, Left] Pulseaudio fails to detect card

2016-06-24 Thread grofaty

Public bug reported:

I saw a help to report audio problem with command:
ubuntu-bug -s audio

I have no sound in Ubuntu 16.04. In System Settings | Sound there is
empty list o output and input devices (see attachment). I did clean
install couple of weeks back. Previously I have got installed Ubuntu
14.04 with zero problems with sound.

I don't know how to fix this problem.
By the way, I can fear audio well e.g. in youtube using Firefox browser.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: Unity
Date: Fri Jun 24 16:48:11 2016
InstallationDate: Installed on 2016-06-03 (20 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel
Symptom_Jack: Green Line Out, Left
Title: [1951F5G, Analog Devices AD1981, Green Line Out, Left] Pulseaudio fails 
to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/12/2006
dmi.bios.vendor: LENOVO
dmi.bios.version: 79ET62WW (1.07 )
dmi.board.name: 1951F5G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 1951F5G
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO

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


** Tags: apport-bug i386 xenial

** Attachment added: "sound_output.png"
   
https://bugs.launchpad.net/bugs/1595986/+attachment/4689817/+files/sound_output.png

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

Title:
  [1951F5G, Analog Devices AD1981, Green Line Out, Left] Pulseaudio
  fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I saw a help to report audio problem with command:
  ubuntu-bug -s audio

  I have no sound in Ubuntu 16.04. In System Settings | Sound there is
  empty list o output and input devices (see attachment). I did clean
  install couple of weeks back. Previously I have got installed Ubuntu
  14.04 with zero problems with sound.

  I don't know how to fix this problem.
  By the way, I can fear audio well e.g. in youtube using Firefox browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Jun 24 16:48:11 2016
  InstallationDate: Installed on 2016-06-03 (20 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Title: [1951F5G, Analog Devices AD1981, Green Line Out, Left] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2006
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ET62WW (1.07 )
  dmi.board.name: 1951F5G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1951F5G
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1595822] Re: Monospace not Monospace in Japanese

2016-06-24 Thread Gunnar Hjalmarsson

This issue was fixed in xenial via .
OTOH, we don't use the fonts-droid-fallback package by default in
Ubuntu. The replacement conf file in xenial (64-language-selector-
prefer.conf) is correct in this respect.

The question is if the issue is important enough to backport the fix to
trusty. If you think it is, please feel free to prepare a patch and
accomplish a SRU in accordance with
.

** Bug watch added: Debian Bug tracker #787149
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787149

** Package changed: fonts-droid (Ubuntu) => fonts-android (Ubuntu)

** Changed in: fonts-android (Ubuntu)
   Status: New => Fix Released

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

Title:
  Monospace not Monospace in Japanese

Status in fonts-android package in Ubuntu:
  Fix Released

Bug description:
  I found this problem when testing FF for bug #1595414, on an English
  installation of 14.04. In short:

  $ LC_ALL='ja_JP.UTF-8' fc-match 'Monospace'
  DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1595822/+subscriptions

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

[Touch-packages] [Bug 1565717] Re: No connection after returning from area without coverage

** Changed in: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1565717

Title:
  No connection after returning from area without coverage

Status in Canonical System Image:
  In Progress
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  After moving in an out of my own "faraday cage" an ubuntu phone, NM
  got into an state where *both* WiFi and cellular data were
  disconnected and NM was not able to recover.

  
  * This still happens with network-manager 1.1.93-0ubuntu1~vivid3, in

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 336
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-17 09:19:51
  version version: 336
  version ubuntu: 20160517
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9
  

  Originally reported for:

  NM version:
  network-manager  0.9.10.0-4ubuntu15.1.11

  root@ubuntu-phablet:/home/phablet# system-image-cli -i
  current build number: 298
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-30 16:58:21
  version version: 298
  version ubuntu: 20160330
  version device: 20160323-1467d3c
  version custom: 20160324--36-54-vivid

  phablet@ubuntu-phablet:~$ nmcli d
  DEVICE   TYPE  STATE CONNECTION
  ril_0gsm   connecting (prepare)  /214050030479893/context1
  wlan0wifi  disconnected  --
  ril_1gsm   unavailable   --
  ifb0 ifb   unmanaged --
  ifb1 ifb   unmanaged --
  lo   loopback  unmanaged --
  ip6tnl0  unknown   unmanaged --
  sit0 unknown   unmanaged --
  tunl0unknown   unmanaged --

  phablet@ubuntu-phablet:~$ nmcli c
  NAME   UUID  TYPE 
DEVICE
  WLAN_1609  fe9b17ad-88fa-43b7-bcab-8fbc1985ce42  
802-11-wireless  --
  Wireless   98ff5b6f-b0d9-471a-b867-8a7be51e12c2  
802-11-wireless  --
  Ubuntu 549c352f-8a2b-4e48-b8c8-eb7ab0e53089  
802-11-wireless  --
  /234304107917083/context1  1f192cdc-ccea-2dc3-fa13-619ed3053828  gsm  
--
  /214321010036211/context1  0992421f-2369-0765-ceaa-ba2a3091e111  gsm  
--
  /214050030479893/context1  d30e4f19-9d00-ab1f-ab43-6d9c1b628556  gsm  
ril_0
  /214019301737411/context1  88b28978-e2fc-6336-8665-b0ae78d321ae  gsm  
--

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  Settings = { Gateway=10.50.83.25 
DomainNameServers=80.58.61.250,80.58.61.254, Interface=ccmni0 
Address=10.50.83.25 Method=static Netmask=255.255.255.0 }
  Name = Pepephone
  Type = internet
  AccessPointName = gprs.pepephone.com
  Active = 1
  Protocol = ip
  AuthenticationMethod = chap
  Password =
  Preferred = 0
  Username =
  IPv6.Settings = { }

  [ /ril_0/context2 ]
  Name = MMS Pepephone
  Type = mms
  Active = 0
  Settings = { }
  MessageCenter = http://www.pepephone.com
  MessageProxy = 10.138.255.43:8080
  Preferred = 0
  Password =
  AccessPointName = gprs.pepephone.com
  Protocol = ip
  AuthenticationMethod = chap
  Username =
  IPv6.Settings = { }

  phablet@ubuntu-phablet:~$ ifconfig
  ccmni0Link encap:Ethernet  HWaddr 46:23:7c:fb:73:cb
    inet addr:10.50.83.25  Mask:255.0.0.0
    UP RUNNING NOARP  MTU:1500  Metric:1
    RX packets:1995 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2299 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:603432 (603.4 KB)  TX bytes:193513 (193.5 KB)

  loLink encap:Local Loopback
    inet addr:127.0.0.1  Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING  MTU:16436  Metric:1
    RX packets:11189 errors:0 dropped:0 overruns:0 frame:0
    TX packets:11189 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:1733281 (1.7 MB)  TX bytes:1733281 (1.7 MB)

  wlan0 Link encap:Ethernet  HWaddr b8:64:91:47:21:b6
    UP BROADCAST MULTICAST  MTU:1500  Metric:1
    RX packets:3184 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1626 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:308130 (308.1 KB)  TX bytes:172906 (172.9 KB)

[Touch-packages] [Bug 1595822] [NEW] Monospace not Monospace in Japanese

You have been subscribed to a public bug:

I found this problem when testing FF for bug #1595414, on an English
installation of 14.04. In short:

$ LC_ALL='ja_JP.UTF-8' fc-match 'Monospace'
DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular"

** Affects: fonts-android (Ubuntu)
 Importance: Undecided
 Status: Fix Released

-- 
Monospace not Monospace in Japanese
https://bugs.launchpad.net/bugs/1595822
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to fonts-android 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 1579098] Re: [touch] Mobile data connection drops, and doesn't automatically reconnect

** Changed in: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1579098

Title:
  [touch] Mobile data connection drops, and doesn't automatically
  reconnect

Status in Canonical System Image:
  In Progress
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  Krillin, rc-proposed, r325

  In the last couple of weeks it often happened that the mobile data
  connection dropped without reconnecting afterwards. I often find my
  device without mobile data connection without apparent reason.

  Switching mobile data connection Off and back On from settings
  restores the connection.

  I don't have any useful additional info to provide, unfortunately.
  Please let me know if you need log/cmd output in particular.

  phablet@ubuntu-phablet:~$ nmcli d status
  DEVICE   TYPE  STATE CONNECTION 
  ril_1gsm   disconnected  -- 
  wlan0wifi  disconnected  -- 
  ril_0gsm   unavailable   -- 
  ifb0 ifb   unmanaged -- 
  ifb1 ifb   unmanaged -- 
  ip6tnl0  ip6tnlunmanaged -- 
  sit0 iptunnel  unmanaged -- 
  lo   loopback  unmanaged -- 
  tunl0unknown   unmanaged --

  Syslog since last time mobile data was connected:
  http://pastebin.ubuntu.com/16259803/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579098/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1595963/+attachment/4689766/+files/Lsusb.txt

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

Title:
  vt1-6 getting stuck or blank

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

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 1595963] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1595963/+attachment/4689768/+files/ProcEnviron.txt

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

Title:
  vt1-6 getting stuck or blank

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

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 1595963] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1595963/+attachment/4689769/+files/ProcInterrupts.txt

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

Title:
  vt1-6 getting stuck or blank

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

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 1595963] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1595963/+attachment/4689770/+files/ProcModules.txt

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

Title:
  vt1-6 getting stuck or blank

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

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 1595963] SystemdFailedUnits.txt

apport information

** Attachment added: "SystemdFailedUnits.txt"
   
https://bugs.launchpad.net/bugs/1595963/+attachment/4689771/+files/SystemdFailedUnits.txt

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

Title:
  vt1-6 getting stuck or blank

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

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 1595421] Re: Location trusted prompt for Scopes shown immediately after the wizard

2016-06-24 Thread Pawel Stolowski

** Summary changed:

- Location trusted prompt shown immediately after the wizard
+ Location trusted prompt for Scopes shown immediately after the wizard

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

Title:
  Location trusted prompt for Scopes shown immediately after the wizard

Status in Canonical System Image:
  New
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  The trusted prompt for location access for Scopes is shown immediately
  after the wizard and not after first search or pull-to-refresh
  initiated by the user as intended. For some reason it happens only if
  wizard is involved in the boot sequence, and not if trusted prompt for
  location is just forced by removing .scopesLocationPrompt and trust
  store db.

  Looking at the unity8-dash.log file from the first boot after wiping
  the device, it seems that there is a forced refresh of scopes registry
  metadata early during the dash startup:

  [2016-04-23:07:04:42.593] Refreshing scope metadata
  [2016-04-23:07:04:42.982] "SettingsModel::update_child_scopes(): no scope 
with id 'com.canonical.scopes.weatherchannel'"
  [2016-04-23:07:04:42.983] Dispatching search: 
"com.canonical.scopes.dashboard_dashboard" "" ""
  [2016-04-23:07:04:42.987] Enabling location updates

  This calls invalidateResults() and has the same effect as pull-to-
  refresh.

  This is most likely caused by the network becoming available & remote
  scopes getting fetched for the first time, signaling new scopes get
  available to the shell.

  To reproduce, reflash with --wipe or perform factory reset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595421/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] UdevDb.txt