[Touch-packages] [Bug 1521803] Re: caps lock not working if auto caps on

[Bill Filler]

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

** Changed in: ubuntu-keyboard (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  caps lock not working if auto caps on

Status in Canonical System Image:
  In Progress
Status in ubuntu-keyboard package in Ubuntu:
  In Progress

Bug description:
  Open address book and create a new contact
  Notice the shift key is highlighted
  double click the shift key to turn on caps lock (I want to type an all caps 
name)
  start typing and the shift key goes back to normal after typing first 
character

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

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

[Touch-packages] [Bug 1479279] Re: Cannot share more than one image at a time

[Launchpad Bug Tracker]

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

** Changed in: gallery-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Cannot share more than one image at a time

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  When multiple images are selected the Share option becomes greyed out
  making it impossible to share multiple images.

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

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

[Touch-packages] [Bug 1419495] Re: Need to share multiple photoes through content hub

[Alexandre Payet]

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

** This bug has been marked a duplicate of bug 1479279
   Cannot share more than one image at a time

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

Title:
  Need to share multiple photoes through content hub

Status in gallery-app package in Ubuntu:
  New

Bug description:
  In galleray app, share button is disabled when multiple photoes are
  selected.

  I have a dropbox client that can do multiple photo upload in one
  contenthub exchange. I would like to use it to upload my photoes
  taken.

  And in upload mode, clicking date won't select all photos in that day.

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

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

[Touch-packages] [Bug 1463353] Re: Notifications not translated on first boot

[Lukáš Tinkl]

** Changed in: indicator-messages (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  Notifications not translated on first boot

Status in Canonical System Image:
  Confirmed
Status in indicator-messages package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Needs a krillin with SD card and working SIM card.

  Test case.
  - Flash a new image.
  - Complete the installation wizard.
  - Make a call to the device (missed one).
  - Open the notification indicator.

  Expected result.
  - SD Card and missed call notifications are not translated on first boot.

  After rebooting the phone, the notifications appear translated.

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

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

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

[Touch-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

[guillaume le louet]

Sorry, it says "willy should work" but it doesn't for me .

lspci --n 
03:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit 
Ethernet Controller [1969:e091] (rev 13)
04:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter [168c:003e] (rev 20)

uname -a
Linux guigolum-GT72-2QE 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

I have a netgear X4 R7500 802.1 g/n/ac router with two access points
(one ac and one n)

network-manager can SEE all the wifi AP (both n and ac) BUT can only
connect to the n. When I try to connect to ac, it asks me for password,
then after some time request the password again. At this moment I can't
connect to any AP unless I enter sudo network-manager restart .

Basically I am stuck with 802.11n now.I also bought other WIFI USB
dongles with 802.11ac but none were working correctly.

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

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Fix Released
Status in HWE Next wily series:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Wily:
  Fix Released
Status in linux-firmware source package in Wily:
  Fix Released
Status in network-manager source package in Wily:
  Confirmed

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  15.10 will work in a week by a simple `apt upgrade`

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  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.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi 

[Touch-packages] [Bug 1528139] Re: serialize_profile_from_old_profile() crash if file contains multiple profiles

[QkiZ]

I'm already downloaded branch version of apparmor and it's still doesn't
see DENIED messages.

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

Title:
  serialize_profile_from_old_profile() crash if file contains multiple
  profiles

Status in AppArmor:
  New
Status in AppArmor 2.10 series:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  = Changed Local Profiles =

  The following local profiles were changed. Would you like to save
  them?

   [1 - /sbin/dhclient]
2 - /usr/sbin/nmbd 
3 - /usr/bin/snx 
4 - /usr/sbin/dnsmasq 
5 - /{usr/,}bin/ping 
6 - /usr/sbin/smbd 
7 - /usr/lib/telepathy/mission-control-5 
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2197, in 
do_logprof_pass
  save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2277, in 
save_profiles
  newprofile = serialize_profile_from_old_profile(aa[which], which, '')
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3961, in 
serialize_profile_from_old_profile
  if write_prof_data[hat]['network'].is_covered(network_obj, True, True):
  AttributeError: 'collections.defaultdict' object has no attribute 'is_covered'

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-v7wx9fu9.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

  When I pressed V button aa-logprof exits with error.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apparmor 2.10-0ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Dec 21 09:54:51 2015
  InstallationDate: Installed on 2014-04-19 (611 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-21-generic 
root=/dev/mapper/ubuntu-root ro splash elevator=cfq nomdmonddf nomdmonisw 
crashkernel=384M-:128M
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to wily on 2015-11-14 (36 days ago)

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

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

[Touch-packages] [Bug 1481673] Re: No mechanism for displaying internal downloads in transfer indicator

[Timo Jyrinki]

indicator-transfer (0.2+15.04.20151216.5-0ubuntu1) vivid; urgency=medium

  [ Renato Araujo Oliveira Filho ]
  * Only allow resume paused downloads.
  * Removed content hub dep from download manager plugin. (LP: #1481673,
#1488547, #1514109)

 -- CI Train Bot   Wed, 16 Dec 2015 19:32:43
+

** Also affects: indicator-transfer (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: indicator-transfer (Ubuntu RTM)
   Status: New => Fix Released

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

Title:
  No mechanism for displaying internal downloads in transfer indicator

Status in Canonical System Image:
  Fix Released
Status in indicator-transfer package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in indicator-transfer package in Ubuntu RTM:
  Fix Released

Bug description:
  We're currently adding support to the webbrowser-app to allow it
  download files internally in addition to sending them to other
  applications, currently download manager has a metadata property
  titled "showInIndicator", however this doesn't appear to have any
  effect when the transfer is happening inside an application without
  content-hub involvement.

  This results in an inconsistent experience for the user, as some
  downloads from the browser show up in the indicator (those opened
  immediately with other apps) and some don't (those downloaded for
  later use).

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

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

[Touch-packages] [Bug 1354391] Re: [browser] Can't download random files

[Timo Jyrinki]

webbrowser-app (0.23+15.04.20151221-0ubuntu1) vivid; urgency=medium

  [ Michael Sheldon ]
  * Add support for handling downloads internally within the browser.
(LP: #1354391)

 -- CI Train Bot   Mon, 21 Dec 2015 20:39:36
+

** Also affects: webbrowser-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: webbrowser-app (Ubuntu RTM)
   Importance: Undecided => High

** Changed in: webbrowser-app (Ubuntu RTM)
   Status: New => Fix Released

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

Title:
  [browser] Can't download random files

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

Bug description:
  I am trying to download a foo.tar.xz file and the browser won't let
  me.

  My use case:
   * Wifi driver in laptop is broken
   * Phone can download stuff
   * Download driver, pass it via adb, mtp or some other way to laptop
   * Be happy again

  This is an hypothetic scenario but i have had this in the past.

  
  UX specification: 
https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g1da5cf439_00

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

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

[Touch-packages] [Bug 1527354] Re: [Jawbone ERA] HFP features not working with Bluez5

[Tony Espy]

** Tags added: bluetooth-ota9

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

Title:
  [Jawbone ERA] HFP features not working with Bluez5

Status in bluez package in Ubuntu:
  New

Bug description:
  While debugging some re-factoring work on the ofono upower plugin, I
  noticed that I wasn't able to answer or terminate calls using my
  Jawbone ERA headset.  I bought this headset last year, and although
  it's an older model, it's spec sheet states that it supports HSP 1.1,
  and HFP 1.5.

  I can pair the device with my krillin, and it properly auto connects (
  note, this seems to work better than my iPhone ).   In-call audio
  works for both incoming and outgoing calls, however I get no ringtone
  in the headset and as mentioned above, I can't answer or terminate the
  call.   I've verified on my iPhone6, that the headset works.  In
  addition to a ringtone in the earpiece, the headset also announces the
  incoming phone number.

  From looking at the ofono debug output, I'm never seeing a new HFP
  connection occur.  I noticed as the upower plugin uses a foreach_atom
  (HFP) style call to update the battery indicators on all attached HFP
  devices.

  I've tested this extensively on krillin, running rc-proposed:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 205
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-12-16 17:53:19
  version version: 205
  version ubuntu: 20151216
  version device: 20151204-2254a36
  version custom: 2015--36-46-vivid

  I've also tested on mako, rc-proposed ( #317 ).

  For reference here's the versions of bluez, ofono, and PulseAudio on
  the device:

  bluez 5.36-0ubuntu2~overlay1
  ofono  1.17.bzr6908+15.04.20151203-0ubuntu1~awe3
  pulseaudio1:6.0-0ubuntu9.11

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

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

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

[Michael Terry]

Moved the bug to be against Trusty, since current Ubuntus don't use a
system upstart.

** Also affects: upstart (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Default values for WAIT_STATE are wrong in the upstart wait-for-state
  job

Status in upstart package in Ubuntu:
  Invalid
Status in upstart source package in Trusty:
  Confirmed

Bug description:
  In Ubuntu 14.04, the wait-for-state job uses the env vars
  WAIT_STATE="started" or WAIT_STATE="stopped". if the GOAL env var is
  set to 'start' or 'stop'.

  However, according to the upstart cookbook, the desired states for a
  already started/stopped job are 'start/running' and 'stop/waiting'.
  Maybe a misunderstood has occurred was the meaning of signals was job
  states (for example, after a job reaches the start/running state, it
  emits the started signal).

  The strange thing is that the waiting/running wait states were
  proposed at the first implementations of this job, and not the
  stopped/started states: https://lists.ubuntu.com/archives/upstart-
  devel/2011-February/001405.html.

  This  bug can make some developers to write upstart jobs that return
  errors (like the GlusterFS developers, that forgot the
  WAIT_STATE="running" condition).

  References:

  - http://upstart.ubuntu.com/cookbook/#job-states
  - http://upstart.ubuntu.com/cookbook/#events-not-states
  - https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1465382

  I'm attaching a patch too.

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

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

[Touch-packages] [Bug 1527275] Re: Current call screen unresponsive during call

[Tomas Öqvist]

I think this is similar to the issue I am having. Dialer-app generally
unresponsive. Can't hang up calls, can't activate loud speaker during
call, sluggishness when pressing number pad icon during call etc.

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

Title:
  Current call screen unresponsive during call

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  - I was in a call
  - I hit the "back" button in the dialer
  - I opened Recent Calls from the bottom
  - I touched the green indicator to go back to the call
  - It brought me to the current call screen, but it didn't show how long the 
call had been going on, and clicking on dialer pad buttons  didn't emit any 
beeps.  Seemed busted / not hooked up to the current call.

  I then tried switching to a different app and using the green
  indicator to go back to the call.  This worked!  So maybe it's just
  when jumping to call when already inside the dialer app?

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

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

[Touch-packages] [Bug 1512327] Re: [dialer-app] Can't hang up phone calls

[Tomas Öqvist]

Yes, this is becoming my number one most annoying issue on my Bq Aquaris
4.5. This happens on most of my outgoing phone calls and if I believe
quite often when receiving phone calls as well.

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

Title:
  [dialer-app] Can't hang up phone calls

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  Recently I had a problem with hanging up. I don't think it was just
  with incoming calls but in that case I was able to reproduce it. I
  have all the recent updates installed and I think the problem only
  occurred after the update to OTA-7.

  - Somebody calls me
  - Name appears in the dialog and I take off
  - The dialer app opens but doesn't show the name nor number nor the calling 
time but the call works
  - It is not possible to hang up the call by pressing the red button
  - I close the dialer app, the green bar at the top appears
  - I reopen it, at this point I might be able to hang up the call otherwise I 
have to redo the closing

  I couldn't find the combination which led to this issue.

  Could be related to bug #1377996.


  - UX comment ---

  The dialer should always show the contact who is calling. Also, it
  should always be possible to hang up the call.

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

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

[Touch-packages] [Bug 1527275] Re: Current call screen unresponsive during call

[Launchpad Bug Tracker]

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

** Changed in: dialer-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Current call screen unresponsive during call

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  - I was in a call
  - I hit the "back" button in the dialer
  - I opened Recent Calls from the bottom
  - I touched the green indicator to go back to the call
  - It brought me to the current call screen, but it didn't show how long the 
call had been going on, and clicking on dialer pad buttons  didn't emit any 
beeps.  Seemed busted / not hooked up to the current call.

  I then tried switching to a different app and using the green
  indicator to go back to the call.  This worked!  So maybe it's just
  when jumping to call when already inside the dialer app?

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

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

[Touch-packages] [Bug 1528668] Re: dialer-app not getting focused after screen unlock

[Michał Sawicz]

Most likely culprit: http://bazaar.launchpad.net/~phablet-
team/qtubuntu/trunk/revision/298

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

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

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

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

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

** Package changed: unity8 (Ubuntu) => qtubuntu (Ubuntu)

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

Title:
  Qt.application.active not working correctly

Status in Canonical System Image:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce:

  1) open dialer-app
  2) lock the screen
  3) unlock the screen

  Expected behavior:
  Qt.application.active == true

  Current behavior
  Qt.application.active == false until we manually switch the app to 
background/foreground again.

  Additional info:
  This is causing a bigger issue in the dialer-app functionality. It currently 
only refreshes the live call view when in foreground, so
  when dialer is in this state, calls are placed but the call controls don't 
work (like hangup or speaker mode).

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

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

[Touch-packages] [Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

[derWalter]

ubuntu 14.04 to cisco catalyst switches and debianboxes

out of nowhere (or maybe with some update from around a week ago) i could not 
access my network anymore...
just to find out its my box fault... had to rdp into windows machines to ssh 
into my linux/unix boxes..

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

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  ssh -vvv  is failing for me where  is a VPN system.

  VPN is configured and connected via network-manager. Last messages
  from ssh (hangs forever):

  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: first_kex_follows 0 
  debug2: kex_parse_kexinit: reserved 0 
  debug2: mac_setup: found hmac-md5
  debug1: kex: server->client aes128-ctr hmac-md5 none
  debug2: mac_setup: found hmac-md5
  debug1: kex: client->server aes128-ctr hmac-md5 none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

  
  = Workaround =

  $ sudo apt-get install putty
  $ putty 

  This works perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.4p1-1
  ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
  Uname: Linux 3.12.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Nov 22 15:37:18 2013
  InstallationDate: Installed on 2010-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  RelatedPackageVersions:
   ssh-askpass   1:1.2.4.1-9
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.4p1-1
  SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago)

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

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

[Touch-packages] [Bug 1528673] [NEW] App doesn't have a qml-project file

[Vamshi Balanaga]

Public bug reported:

There is no way to open this up as a project in Qt Creator because there
isn't a .qml-project file that can be opened by Qt Creator.

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

Title:
  App doesn't have a qml-project file

Status in messaging-app package in Ubuntu:
  New

Bug description:
  There is no way to open this up as a project in Qt Creator because
  there isn't a .qml-project file that can be opened by Qt Creator.

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

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

[Touch-packages] [Bug 1526884] Re: context menu steals focus from the webview

[Olivier Tilloy]

The problem has gotten worse with the latest release of the UITK
(1.3.1778+16.04.20151217.1-0ubuntu1). With the fix for bug #1523828,
popovers are now requesting active focus when they are shown, so the
workaround I mentioned in comment #7 is useless.

In gmail, when long pressing on the compose field of a new message, the
webview looses focus, which hides the OSK, which resizes the webview,
which as a consequence dismisses the context menu. So the context menu
has become unusable in gmail.

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

Title:
  context menu steals focus from the webview

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

Bug description:
  latest rc-proposed on krillin

  1) open webbrowser-app and find a link
  2) long press to get context menu and select "Copy Link"
  3) open gmail webapp and create a new message
  4) go to the message body and try to paste the link by long pressing, and 
selecting "Paste" from the menu

  Expected results:
  link pasted into message body

  Actual results:
  nothing pasted into the message body

  Some additional info:
  - instead of doing step 4) try to paste into the "To" field and it works 
correctly, so the paste buffer has the correct info, just can't be pasted into 
the body of the message

  - also, if I type some text in the message body, the long
  press->"Select all", then long press->"copy", and then long press
  "paste" nothing happens.

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

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

[Touch-packages] [Bug 1384274] Re: silent mode doesn't silence keyboard or dialpad

[Pat McGowan]

** No longer affects: ubuntu-keyboard

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

Title:
  silent mode doesn't silence keyboard or dialpad

Status in Canonical System Image:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in telephony-service source package in Vivid:
  Fix Committed

Bug description:
  As of krillin rtm image 120, silent mode works to silence the phone
  and SMS ringers, but does not affect anything else.  To meet
  expectations of users from other platforms, it should also silence the
  keyboard and dialpad sounds, and probably the three beeps which
  trigger when the other end of a call hangs up.

  As for music, videos, and alarms, almost all platforms still play
  audio for those regardless of the silent mode setting.  (one exception
  is the Palm Treo, which used a physical kill switch for sound and thus
  silenced *everything*)

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

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

[Touch-packages] [Bug 1382860] Re: Keyboard sound not affected by turning volume down/off

[Pat McGowan]

** Tags added: volume

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

Title:
  Keyboard sound not affected by turning volume down/off

Status in Canonical System Image:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed

Bug description:
  On RTM 5 with Mako, the keyboard sound is not affected by turning off
  the main sound. I.e., when putting my phone on 'silent' by turning
  down the sound all the way, they keyboard 'clicks' still sound when
  typing on keyboard. Workaround is to disable keyboard sound in System
  Settings>Sound>Keyboard sounds

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

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

[Touch-packages] [Bug 1521036] Re: upgrade to 12004lts package fail

[Brian Murray]

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but it is better to raise problems you are having in the
support tracker at https://answers.launchpad.net/ubuntu if you are
uncertain if they are bugs. You can also find help posting your problem
in the support forum of your local Ubuntu's community
http://loco.ubuntu.com/ or asking at http://askubuntu.com. For help on
reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

** No longer affects: click-update-manager (Ubuntu)

** Changed in: update-manager (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/update-manager/+question/279933

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

Title:
  upgrade to 12004lts package fail

Status in update-manager package in Ubuntu:
  Invalid

Bug description:
  upgrade package fail with error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1521036/+subscriptions

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

[Touch-packages] [Bug 1523801] Re: Cross compiling Mir from a xenial host fails (dpkg-checkbuilddeps: error: Unmet build dependencies: ...)

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

** Changed in: mir/0.18
   Status: Fix Committed => Fix Released

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

Title:
  Cross compiling Mir from a xenial host fails (dpkg-checkbuilddeps:
  error: Unmet build dependencies: ...)

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Cross compiling Mir from a xenial host fails

  $ ./cross-compile-chroot.sh -d wily -u
  no partial chroot dir detected. attempting to create one
  Building for distro: wily
  Using MIR_NDK_PATH: /home/dan/.cache/mir-armhf-chroot-wily
  creating phablet-compatible armhf partial chroot for mir compilation in 
directory /home/dan/.cache/mir-armhf-chroot-wily
  dpkg-checkbuilddeps: error: Unmet build dependencies: build-essential:native 
cmake cmake-data pkg-config debhelper (>= 9) doxygen xsltproc graphviz 
libboost-dev libboost-date-time-dev libboost-program-options-dev 
libboost-system-dev libboost-filesystem-dev protobuf-compiler libdrm-dev 
libegl1-mesa-dev libgles2-mesa-dev libgbm-dev libglm-dev libprotobuf-dev 
android-headers (>= 4.4.2) libhardware-dev libandroid-properties-dev 
libgoogle-glog-dev liblttng-ust-dev libxkbcommon-dev libumockdev-dev (>= 0.6) 
umockdev (>= 0.8.7) libudev-dev libgtest-dev google-mock (>= 1.6.0+svn437) 
valgrind libglib2.0-dev libfreetype6-dev abi-compliance-checker libevdev-dev 
libinput-dev (>= 0.21) uuid-dev python3:any dh-python nettle-dev

  It just exits silently and gives up without even trying to download
  the dependencies.

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

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

[Touch-packages] [Bug 1528658] Re: sysconfig-hardware is missing from s390x server livecd squashfs builds

[Dimitri John Ledkov]

** Description changed:

  sysconfig-hardware is missing from s390x server livecd squashfs builds
  
  the intention is to always have it, similar to e.g. s390-tools, as
  without s390-tools one doesn't have boot loader and without sysconf-
  hardware the s390x specific hardware will not be brought up online on
  boot (thus dropping user into busybox shell)
+ 
+ Please bump priority from standard to important

** No longer affects: ubuntu-meta (Ubuntu)

** Changed in: sysconfig (Ubuntu)
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

Title:
  sysconfig-hardware is missing from s390x server livecd squashfs builds

Status in sysconfig package in Ubuntu:
  Confirmed

Bug description:
  sysconfig-hardware is missing from s390x server livecd squashfs builds

  the intention is to always have it, similar to e.g. s390-tools, as
  without s390-tools one doesn't have boot loader and without sysconf-
  hardware the s390x specific hardware will not be brought up online on
  boot (thus dropping user into busybox shell)

  Please bump priority from standard to important

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

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

[Touch-packages] [Bug 1528651] Re: Code and functional issues with new download in browser feature

[Michael Sheldon]

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Confirmed

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

Title:
  Code and functional issues with new download in browser feature

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The new "download in browser" feature just landed. This works nicely,
  but there are a few remaining (mostly minor) issues that need to be
  addressed now. I’m filing this bug to track them all, we may want to
  break it up in several bugs if/where relevant.

  Code issues:
  ∘ encapsulation broken in DownloadHandler.qml with references to 
'downloadsModel'
  ∘ encapsulation broken in DownloadDelegate.qml with references to 
'downloadManager'
  ∘ missing autopilot tests for file upload, picking webbrowser-app (including 
multiple files)
  ∘ showDownloadsPage() doesn’t make much sense on WebViewImpl, should be an 
internal function
  ∘ contentHandlerLoader should have "asynchronous: true"
  ∘ use default PageHeader from UITK instead of custom BrowserPageHeader?
  ∘ increase test coverage for the DownloadsModel C++ class
  ∘ for consistency, downloadsContainer should be made a Loader, as done in 
https://code.launchpad.net/~osomon/webbrowser-app/keyboard-shortcuts-focus-fixes/+merge/280083
  ∘ in Downloader.qml and Browser.qml, calls to Component.createObject() should 
pass the properties as second parameter, instead of setting them afterwards
  ∘ DownloadsModel should probably be made a singleton type, like HistoryModel 
and BookmarksModel
  ∘ includes are not ordered alphabetically in downloads-model.cpp
  ∘ in DownloadsModel::moveToDownloads(), the [if (QFile::exists(destination))] 
statement is useless, the do…while loop is enough

  Functional issues:
  ∘ the "No Downloads available" message is confusing in picker mode, it would 
be clearer if it made it explicit that no download matching the expected file 
type is available
  ∘ while in edit mode in the downloads page, the 'delete' icon should probably 
be disabled if no download is selected (it currently is enabled and exits 
select mode)
  ∘ save link from context menu doesn’t work great with links to other pages: 
no mime type is displayed (and sometimes even no title), and then the page is 
saved without an html extension, it can be viewed with the document viewer, but 
this displays the source of the page, it doesn’t render it (we may need special 
casing for HTML files in the download folder to open them directly in the 
browser)
  ∘ (possibly a bug in the UITK?) upload form that accepts only one file, can 
end up selecting two: select first, then second, then first again, then second 
again, and both are selected
  ∘ when downloading an image to the gallery, I’m seeing this message in the 
log: Failed moving file from  
"/home/phablet/.cache/com.ubuntu.gallery/HubIncoming/2/capture2.png"  to  
"/home/phablet/Downloads/capture2.png"

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

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

[Touch-packages] [Bug 1522673] Re: [regression] Mouse wheel events are now unusably over-sensitive and backwards

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

** Changed in: mir/0.18
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Mouse wheel events are now unusably over-sensitive and
  backwards

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] Mouse wheel events are now unusably over-sensitive and
  backwards to how they used to be.

  Test case: In mir_proving_server use: Super+mousewheel.

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

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

[Touch-packages] [Bug 1521651] Re: After exiting Mir (by Ctrl+Alt+BkSp) VT switching by Ctrl+Alt+Fn is broken

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  After exiting Mir (by Ctrl+Alt+BkSp) VT switching by Ctrl+Alt+Fn is
  broken

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ sudo bin/mir_demo_server --vt 1

  Exit using Ctrl+Alt+BkSp

  Now try to switch back to desktop session with Ctrl+Alt+F7

  Expect: switches back to desktop session
  Actual: nothing happens

  A switch by "sudo chvt 7" gets things back to normal

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

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

[Touch-packages] [Bug 1521225] Re: [regression] Ctrl/Alt modifiers not handled correctly

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Ctrl/Alt modifiers not handled correctly

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  $ sudo bin/mir_demo_server  --vt 1 --arw-file --launch-client
  bin/mir_demo_client_egltriangle

  Press Ctrl+F4
  Expect: nothing
  Actual: VT session switches to tty4

  Press Alt+F4
  Expect: client exits
  Actual: VT session switches to tty4

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

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

[Touch-packages] [Bug 1517532] Re: FTBFS with -DMIR_PLATFORM=android

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  FTBFS with -DMIR_PLATFORM=android

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  
/home/alan/display_server/mir2/tests/unit-tests/graphics/test_platform_prober.cpp:107:25:
 error: ‘MockDRM’ is not a member of ‘mtd’
   ::testing::NiceMock mock_drm;
   ^
  
/home/alan/display_server/mir2/tests/unit-tests/graphics/test_platform_prober.cpp:107:25:
 error: ‘MockDRM’ is not a member of ‘mtd’
  
/home/alan/display_server/mir2/tests/unit-tests/graphics/test_platform_prober.cpp:107:37:
 error: template argument 1 is invalid
   ::testing::NiceMock mock_drm;

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

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

[Touch-packages] [Bug 1510778] Re: [regression] arm64/powerpc cross compile doesn't build any more

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] arm64/powerpc cross compile doesn't build any more

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] arm64 cross compile doesn't build any more.

  Support for generic architecture cross compilation (including arm64)
  was added in Mir 0.16. You can use it with:

 sudo apt-get install g++-aarch64-linux-gnu gcc-aarch64-linux-gnu
./cross-compile-chroot.sh -a arm64 -d wily

  However it's presently failing in lp:mir and lp:mir/0.17. Still works
  in lp:mir/0.16 though.

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

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

[Touch-packages] [Bug 1513225] Re: libmircookie1 package does not list libnettle as dependency

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  libmircookie1 package does not list libnettle as dependency

Status in Mir:
  Fix Released
Status in Mir 0.17 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  libmircookie1 package declaration is missing a shlibs:Depends entry on
  the Dependencies list.

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

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

[Touch-packages] [Bug 1497128] Re: mir_demo_server crashes with ERROR: Dynamic exception type: std::out_of_range - std::exception::what: map::at when an Xmir rootless app is closed by its File menu.

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_demo_server crashes with ERROR: Dynamic exception type:
  std::out_of_range - std::exception::what: map::at when an Xmir
  rootless app is closed by its File menu.

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  mir_demo_server crashes with:

     ERROR: Dynamic exception type: std::out_of_range
     std::exception::what: map::at

  when an Xmir rootless app is closed by its File menu.

  This does not happen in mir_demo_server_minimal or mir_proving_server.
  It might have something to do with child/parent surface relationships
  and the fact that closing an app (like gedit) involves having a menu
  open (which to Mir at least is a child of the app window).

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

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

[Touch-packages] [Bug 1511723] Re: unplugging external monitor causes nested server to throttle client

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  unplugging external monitor causes nested server to throttle client

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  On a vivid(ish) laptop with external monitor connected and active.

  Running trunk + the display reconfig fix in lp:~alan-griffiths/mir
  /cache-invalidation-for-nested-Display-active-config

  /1/ start a host server:

  $ sudo bin/mir_demo_server --shell-report log --window-manager
  system-compositor --display-config sidebyside --vt 1 --arw-file

  /2/ start a nested server:

  $ bin/mir_demo_server --shell-report log --host /tmp/mir_socket
  --display-config sidebyside --window-manager tiling

  /3/ start a client (one chosen that reports frame rate)

  $ bin/mir_demo_standalone_render_surfaces --no-file --host-socket
  /run/user/1000/mir_socket

  /4/ disconnect the external monitor

  Expected: FPS continues at 60
  Observed: FPS drops to around 10 until external monitor is reconnected.

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

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

[Touch-packages] [Bug 1489522] Re: mir fails to open the right mouse device in kvm/qemu

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir fails to open the right mouse device in kvm/qemu

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
   * setup kvm as in our wiki
   * launch mir_demo_server with a client
   * try to move the client windows window with the mouse

  -> mir does not react to move moves or clicks..

  Looking at the legacy input report mir opens event3 and event1 but not
  event2 which is the actual mouse. event3 claims to offer REL_X and
  REL_Y - but never emits those events. Maybe this is a regression in
  the VMWare input device drivers? Or somewhere from input driver to the
  host integration.

  Note the same happens for mir-0.15.0

  In 0.17 with the evdev platform there is a similar problem. The right
  device gets opened but the platform fails to provide proper movement
  events because the absolute coordinates are extremely scaled to a
  range of 0-65535, and get confined.

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

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

[Touch-packages] [Bug 1503317] Re: multibufferstreams use surface size instead of stream size

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  multibufferstreams use surface size instead of stream size

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  A bit of work is needed to sort out how multi-bufferstreams work with scaling.
  
http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/src/server/scene/basic_surface.cpp#L880
  Will set all the streams rendering size to the surface size, which is fine 
and sensible if there's on surface and scaling is in effect. If there are 
multiple streams in this surface though, it seems a bit less sensible.

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

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

[Touch-packages] [Bug 1513792] Re: mircookie requires nettle but libmircookie-dev doesn't depend on it

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mircookie requires nettle but libmircookie-dev doesn't depend on it

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I thought that bug #1513225 was fixing this but it wasn't.

  As long as you have Requires.private: nettle in mircookie's pcfile,
  libmircookie-dev package needs to Depend on it (since pkg-config will
  cry otherwise), like:

Package 'nettle', required by 'mircookie', not found

  We're getting this failure in gtk+ now.

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

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

[Touch-packages] [Bug 1504579] Re: CI failure on some 32-bit targets in ServerSignal.terminate_handler_is_called_for_SIGTERM and others

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  CI failure on some 32-bit targets in
  ServerSignal.terminate_handler_is_called_for_SIGTERM and others

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Running CI on certain 32-bit Wily targets fails a slew of tests with
  valgrind errors similar to the below.

  ==30124== Syscall param futex(timeout) points to unaddressable byte(s)
  ==30124==at 0x46CA5A7: syscall (syscall.S:30)
  ==30124==by 0x44CD335: 
std::__atomic_futex_unsigned_base::_M_futex_wait_until(unsigned int*, unsigned 
int, bool, std::chrono::duration >, 
std::chrono::duration >) (in 
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.21)
  ==30124==by 0x40C8076: _M_load_and_test_until (atomic_futex.h:104)
  ==30124==by 0x40C8076: _M_load_and_test (atomic_futex.h:122)
  ==30124==by 0x40C8076: _M_load_when_equal (atomic_futex.h:162)
  ==30124==by 0x40C8076: wait (future:322)
  ==30124==by 0x40C8076: std::__basic_future::wait() const 
(future:656)
  ==30124==by 0x40C7111: mir::input::DefaultInputManager::stop() 
(default_input_manager.cpp:139)
  ==30124==by 0x40A4A30: mir::DisplayServer::run() (display_server.cpp:205)
  ==30124==by 0x40A104B: mir::run_mir(mir::ServerConfiguration&, 
std::function, std::function const&) 
(run_mir.cpp:110)
  ==30124==by 0x40B8C84: mir::Server::run() (server.cpp:405)
  ==30124==by 0x84A8279: operator() (async_server_runner.cpp:88)
  ==30124==by 0x84A8279: _M_invoke<> (functional:1531)
  ==30124==by 0x84A8279: operator() (functional:1520)
  ==30124==by 0x84A8279: 
std::thread::_Impl >::_M_run() (thread:115)
  ==30124==by 0x44CF7ED: ??? (in 
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.21)
  ==30124==by 0x45CE1A9: start_thread (pthread_create.c:333)
  ==30124==by 0x46CEFDD: clone (clone.S:122)
  ==30124==  Address 0x18 is not stack'd, malloc'd or (recently) free'd

  The errors can be reproduced with hte following comand.

  valgrind --error-exitcode=1 --trace-children=yes --leak-check=full
  --show-leak-kinds=definite --errors-for-leak-kinds=definite --track-
  fds=yes --num-callers=128
  --suppressions=tools/valgrind_suppressions_generic
  --suppressions=tools/valgrind_suppressions_glibc_2.21 obj-i686-linux-
  gnu/bin/mir_acceptance_tests
  --gtest_filter=ServerSignal.terminate_handler_is_called_for_SIGTERM

  It turns out the problem is code in libstdc++-v3 not passing all
  required parameters to a syscall() on a futex.  We can probably assume
  the authors of that library know more about what they're doing with
  Linux kernel calls than we do, so I think adding a valgrind
  suppression for these errors should be all that's required to fix the
  CI failures.

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

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

[Touch-packages] [Bug 1515931] Re: [testsfail] RaiseSurfaces.motion_events_dont_prevent_raise

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [testsfail] RaiseSurfaces.motion_events_dont_prevent_raise

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  https://jenkins.qa.ubuntu.com/job/mir-wily-
  amd64-autolanding/673/consoleFull

  [ RUN ] RaiseSurfaces.motion_events_dont_prevent_raise
  [1447351409.612767] mirserver: Starting
  [1447351409.614462] mirserver: Selected driver: dummy (version 0.18.0)
  [1447351409.624771] mirserver: Initial display configuration:
  [1447351409.625978] mirserver: 1.1: VGA 0.0" 0x0mm
  [1447351409.626125] mirserver: Current mode 1600x1600 60.00Hz
  [1447351409.626256] mirserver: Preferred mode 1600x1600 60.00Hz
  [1447351409.626353] mirserver: Logical position +0+0
  [1447351409.631534] mirserver: Using software cursor
  [1447351409.633659] mirserver: Mir version 0.18.0
  
/tmp/buildd/mir-0.17.0+15.10.20151008.2bzr3098pkg0wily673/tests/acceptance-tests/test_surface_raise.cpp:127:
 Failure
  Value of: all_events
  Actual: false
  Expected: true
  [1447351413.983667] mirserver: Stopping
  [ FAILED ] RaiseSurfaces.motion_events_dont_prevent_raise (4399 ms)

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

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

[Touch-packages] [Bug 1423462] Re: DemoRenderer: GL_BLEND is really always enabled even when not required (also causes RGBX discolouration in mir_proving_server)

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  DemoRenderer: GL_BLEND is really always enabled even when not required
  (also causes RGBX discolouration in mir_proving_server)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  DemoRenderer: GL_BLEND is really always enabled, even when not
  required.

  This is because DemoRenderer turns it on for shadows etc during
  tessellation. And that ends up applying to the whole glDrawArrays(),
  which is all primitives.

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

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

[Touch-packages] [Bug 1526225] Re: [regression] Nested server fails to start if built with cmake -DMIR_ENABLE_TESTS=OFF - std::exception::what: Failed to find platform for current system

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

** Changed in: mir/0.18
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Nested server fails to start if built with cmake
  -DMIR_ENABLE_TESTS=OFF - std::exception::what: Failed to find platform
  for current system

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  Invalid

Bug description:
  Nested server fails to start if built with cmake
  -DMIR_ENABLE_TESTS=OFF

  [1450172551.555130] mirplatform: Found graphics driver: mesa-kms (version 
0.19.0)
  [1450172551.555172] mirplatform: Found graphics driver: android (version 
0.19.0)
  [1450172551.555183] mirplatform: Found graphics driver: mesa-x11 (version 
0.19.0)
  [1450172551.50] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [1450172551.90] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.7
  [1450172551.555814] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.7
  [1450172551.556168] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.7
  [1450172551.556442] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.4
  [1450172551.557704] mirplatform: Found graphics driver: mesa-kms (version 
0.19.0)
  [1450172551.557733] mirplatform: Found graphics driver: android (version 
0.19.0)
  [1450172551.557742] mirplatform: Found graphics driver: mesa-x11 (version 
0.19.0)
  ERROR: 
/home/dan/bzr/mir/fixmirout/src/platform/graphics/platform_probe.cpp(63): Throw 
in function std::shared_ptr 
mir::graphics::module_for_device(const 
std::vector&, const 
mir::options::ProgramOption&)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Failed to find platform for current system

  
  Bisection hint: Bug is present in r3170 but not in r3005.

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

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

[Touch-packages] [Bug 1463873] Re: Android uses mir_display_output_invalid_id (0) as an output id value

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Android uses mir_display_output_invalid_id (0) as an output id value

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Android uses mir_display_output_invalid_id (0) as an output id value,
  causing our code to misbehave (e.g. reject seemingly valid surface
  requests).

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

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

[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 & krillin)

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Backward frame jumps on mali (Nexus 10 & krillin)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Alexandros, Andreas, and I have noted at different points that we see
  frame skips on the nexus 10. The frames look like they move in a 1,3,2
  pattern, particularly when unlocking the device.

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

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

[Touch-packages] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

** Changed in: canonical-pocket-desktop
   Status: Fix Committed => Fix Released

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

Title:
  Severe graphical corruption (mostly horizontal streaks/lines) running
  software clients (including Xmir) on android

Status in canonical-pocket-desktop:
  Fix Released
Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I'm seeing severe graphical corruption running mir_demo_client_flicker
  on mako.

  Start a few instances of the client (or just one flicker and some
  other clients) and you'll see the mir_demo_client_flicker window
  contains significant corruption.

  I don't think it's an overlays issue. The problem occurs even without
  overlays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions

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

[Touch-packages] [Bug 1528670] [NEW] Incoming call when locked freezes the screen

[Pat McGowan]

Public bug reported:

I called into a phone that was suspended/screen off
Answered the call via the notification
the dialer appeared but did not update the caller info or the connection
I hung up from the calling side and the UI on the receiving side froze
Power button cleared it up

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

** Attachment added: "dialer.png"
   https://bugs.launchpad.net/bugs/1528670/+attachment/4539133/+files/dialer.png

** Summary changed:

- Incoming call when locked freezing the screen
+ Incoming call when locked freezes the screen

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

Title:
  Incoming call when locked freezes the screen

Status in dialer-app package in Ubuntu:
  New

Bug description:
  I called into a phone that was suspended/screen off
  Answered the call via the notification
  the dialer appeared but did not update the caller info or the connection
  I hung up from the calling side and the UI on the receiving side froze
  Power button cleared it up

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

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

[Touch-packages] [Bug 1291458] Re: [System Settings] Volume buttons change ringtone volume when suspended

[Pat McGowan]

** Tags added: volume

** Tags removed: apport-bug armhf hardware-related trusty

** Changed in: canonical-devices-system-image
Milestone: backlog => ww08-2016

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

Title:
  [System Settings] Volume buttons change ringtone volume when suspended

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  This is a rather bigger topic for user experience design, but one
  thing that should at least happen asap is volume buttons should be
  disabled when screen is off, otherwise your you-thought-silenced-phone
  suddenly blares a ring tone.

  Steps to repro:
  * suspend your phone
  * press volume buttons

  Expected result:
  * nothing happens

  Current result:
  * volume changes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity8 7.84+14.04.20140306-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: armhf
  Date: Wed Mar 12 13:14:37 2014
  InstallationDate: Installed on 2014-03-12 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

  -

  : "While a device is
  asleep, volume keys/buttons should be ignored."

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

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

[Touch-packages] [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

[David Favor]

I see this bug is tagged xenial. Please post a fix which can be added to
Wily, to escape the long shudown delay.

Thanks.

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

Title:
  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
  ufstype=old

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in os-prober package in Ubuntu:
  Confirmed

Bug description:
  [  556.734157] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  556.746268] JFS: nTxBlock = 8192, nTxLock = 65536
  [  556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE].
  [  556.792231] QNX4 filesystem 0.2.3 registered.
  [  557.922469] EXT4-fs (sda4): unable to read superblock
  [  557.925868] EXT4-fs (sda4): unable to read superblock
  [  557.928967] EXT4-fs (sda4): unable to read superblock
  [  557.931784] FAT-fs (sda4): bogus number of reserved sectors
  [  557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.946740] XFS (sda4): Invalid superblock magic number
  [  557.951904] FAT-fs (sda4): bogus number of reserved sectors
  [  557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.959099] MINIX-fs: unable to read superblock
  [  557.965712] attempt to access beyond end of device
  [  557.965721] sda4: rw=16, want=3, limit=2
  [  557.965725] hfsplus: unable to find HFS+ superblock
  [  557.968487] qnx4: no qnx4 filesystem (no root dir).
  [  557.971203] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  557.974459] hfs: can't find a HFS filesystem on dev sda4
  [  564.034208] EXT4-fs (sda4): unable to read superblock
  [  564.040322] EXT4-fs (sda4): unable to read superblock
  [  564.043485] EXT4-fs (sda4): unable to read superblock
  [  564.047076] FAT-fs (sda4): bogus number of reserved sectors
  [  564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.059578] XFS (sda4): Invalid superblock magic number
  [  564.064473] FAT-fs (sda4): bogus number of reserved sectors
  [  564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.072080] MINIX-fs: unable to read superblock
  [  564.074564] attempt to access beyond end of device
  [  564.074571] sda4: rw=16, want=3, limit=2
  [  564.074576] hfsplus: unable to find HFS+ superblock
  [  564.076688] qnx4: no qnx4 filesystem (no root dir).
  [  564.078847] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  564.080902] hfs: can't find a HFS filesystem on dev sda4
  [  570.554296] EXT4-fs (sda4): unable to read superblock
  [  570.557647] EXT4-fs (sda4): unable to read superblock
  [  570.560516] EXT4-fs (sda4): unable to read superblock
  [  570.563451] FAT-fs (sda4): bogus number of reserved sectors
  [  570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.574953] XFS (sda4): Invalid superblock magic number
  [  570.580796] FAT-fs (sda4): bogus number of reserved sectors
  [  570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.588340] MINIX-fs: unable to read superblock
  [  570.590983] attempt to access beyond end of device
  [  570.590993] sda4: rw=16, want=3, limit=2
  [  570.590999] hfsplus: unable to find HFS+ superblock
  [  570.593321] qnx4: no qnx4 filesystem (no root dir).
  [  570.595556] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  570.597775] hfs: can't find a HFS filesystem on dev sda4
  [  576.795014] EXT4-fs (sda4): unable to read superblock
  [  576.797554] EXT4-fs (sda4): unable to read superblock
  [  576.800063] EXT4-fs (sda4): unable to read superblock
  [  576.802647] FAT-fs (sda4): bogus number of reserved sectors
  [  576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  576.813305] XFS (sda4): Invalid superblock magic number
  [  576.820257] FAT-fs (sda4): bogus number of reserved sectors
  [  576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  576.830945] MINIX-fs: unable to read superblock
  [  576.834108] attempt to access beyond end of device
  [  576.834119] sda4: rw=16, want=3, limit=2
  [  576.834125] hfsplus: unable to find HFS+ superblock
  [  576.837264] qnx4: no qnx4 filesystem (no root dir).
  [  576.840408] You didn't specify the type of your ufs filesystem

  mount -t ufs -o 

[Touch-packages] [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

[David Favor]

This is a very ugly bug.

Sometimes this causes reboots to hang for long periods. Just timed it on
a Wily system with all upgrades installed.

Takes 157 seconds, to shutdown system.

Above comments only mention 3.19 (Vivid) kernels. This problem persists
in Wily...

net4-dev# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename:   wily

net4-dev# uname -a
Linux net4.bizcooker.com 4.2.0-22-generic #27-Ubuntu SMP Thu Dec 17 22:57:08 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is
  ufstype=old

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in os-prober package in Ubuntu:
  Confirmed

Bug description:
  [  556.734157] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
  [  556.746268] JFS: nTxBlock = 8192, nTxLock = 65536
  [  556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE].
  [  556.792231] QNX4 filesystem 0.2.3 registered.
  [  557.922469] EXT4-fs (sda4): unable to read superblock
  [  557.925868] EXT4-fs (sda4): unable to read superblock
  [  557.928967] EXT4-fs (sda4): unable to read superblock
  [  557.931784] FAT-fs (sda4): bogus number of reserved sectors
  [  557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.946740] XFS (sda4): Invalid superblock magic number
  [  557.951904] FAT-fs (sda4): bogus number of reserved sectors
  [  557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  557.959099] MINIX-fs: unable to read superblock
  [  557.965712] attempt to access beyond end of device
  [  557.965721] sda4: rw=16, want=3, limit=2
  [  557.965725] hfsplus: unable to find HFS+ superblock
  [  557.968487] qnx4: no qnx4 filesystem (no root dir).
  [  557.971203] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  557.974459] hfs: can't find a HFS filesystem on dev sda4
  [  564.034208] EXT4-fs (sda4): unable to read superblock
  [  564.040322] EXT4-fs (sda4): unable to read superblock
  [  564.043485] EXT4-fs (sda4): unable to read superblock
  [  564.047076] FAT-fs (sda4): bogus number of reserved sectors
  [  564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.059578] XFS (sda4): Invalid superblock magic number
  [  564.064473] FAT-fs (sda4): bogus number of reserved sectors
  [  564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  564.072080] MINIX-fs: unable to read superblock
  [  564.074564] attempt to access beyond end of device
  [  564.074571] sda4: rw=16, want=3, limit=2
  [  564.074576] hfsplus: unable to find HFS+ superblock
  [  564.076688] qnx4: no qnx4 filesystem (no root dir).
  [  564.078847] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  564.080902] hfs: can't find a HFS filesystem on dev sda4
  [  570.554296] EXT4-fs (sda4): unable to read superblock
  [  570.557647] EXT4-fs (sda4): unable to read superblock
  [  570.560516] EXT4-fs (sda4): unable to read superblock
  [  570.563451] FAT-fs (sda4): bogus number of reserved sectors
  [  570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.574953] XFS (sda4): Invalid superblock magic number
  [  570.580796] FAT-fs (sda4): bogus number of reserved sectors
  [  570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  570.588340] MINIX-fs: unable to read superblock
  [  570.590983] attempt to access beyond end of device
  [  570.590993] sda4: rw=16, want=3, limit=2
  [  570.590999] hfsplus: unable to find HFS+ superblock
  [  570.593321] qnx4: no qnx4 filesystem (no root dir).
  [  570.595556] You didn't specify the type of your ufs filesystem

  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep
  |nextstep-cd|openstep ...

  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is 
ufstype=old
  [  570.597775] hfs: can't find a HFS filesystem on dev sda4
  [  576.795014] EXT4-fs (sda4): unable to read superblock
  [  576.797554] EXT4-fs (sda4): unable to read superblock
  [  576.800063] EXT4-fs (sda4): unable to read superblock
  [  576.802647] FAT-fs (sda4): bogus number of reserved sectors
  [  576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem
  [  576.813305] XFS (sda4): Invalid superblock magic number
  [  576.820257] FAT-fs (sda4): bogus number of reserved sectors
  [  576.820276] FAT-fs (sda4): 

[Touch-packages] [Bug 1485522] Re: Volume obtained is 100% in multimedia sink for sounds from app

[Pat McGowan]

** Tags added: volume

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

Title:
  Volume obtained is 100% in multimedia sink for sounds from app

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed
Status in qtubuntu-media package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure 100% this is a bug but it is related to
  https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478506

  When the "Marron in trouble" games launches a sound the multimedia
  sink it's updated and when reading the volume it's always 100%.

  I'ts not 100% for other applications using the multimedia role, like
  the music app or other games/apps. The volume in that case is in sync
  with the volume that was previously set for it.

  This is the code from the indicator-sound where we get the 100%
  volume.

  var props_variant = yield _pconn.call 
("org.PulseAudio.Ext.StreamRestore1.RestoreEntry",
sink_input_objp, 
"org.freedesktop.DBus.Properties", "Get",
new Variant ("(ss)", 
"org.PulseAudio.Ext.StreamRestore1.RestoreEntry", "Volume"),
null, DBusCallFlags.NONE, -1);
Variant tmp;
props_variant.get ("(v)", out tmp);
uint32 type = 0, volume = 0;
VariantIter iter = tmp.iterator ();
iter.next ("(uu)", , );

  I did a workaround branch in the indicator-sound that reads the volume
  at initilaization for every role and stores any change When the sink
  is updated I read the volume in it that is already stored instead of
  reading the volume from pulse.

  I'm not convinced of that, and would like to know why I get 100%
  volume only for this particular game.

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

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

[Touch-packages] [Bug 1527166] Re: cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg: 'linux-headers..."

[Brian Murray]

** Changed in: python-apt (Ubuntu)
   Status: New => Triaged

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => Low

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

Title:
  cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg:
  'linux-headers..."

Status in python-apt package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  New

Bug description:
  Today I received the following messages from /etc/cron.daily/apt on my
  14.04 LTS server

  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73'
  MarkUpgrade() called on a non-upgrable pkg: 
'linux-image-extra-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-image-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73-generic'

  
  First of all I suppose  the message should read  non-upgradable
  non-upgrable is possibly incorrect and should be corrected.

  Secondly I have no clue, what this message means so the error message
  should be revised to give more details.

  I think this as a minor bug but messages should always be correct,
  precise and possibly helpful.

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

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

[Touch-packages] [Bug 1527166] Re: cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg: 'linux-headers..."

[Launchpad Bug Tracker]

** Branch linked: lp:~brian-murray/python-apt/typo-1527166

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

Title:
  cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg:
  'linux-headers..."

Status in python-apt package in Ubuntu:
  Triaged
Status in update-manager package in Ubuntu:
  New

Bug description:
  Today I received the following messages from /etc/cron.daily/apt on my
  14.04 LTS server

  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73'
  MarkUpgrade() called on a non-upgrable pkg: 
'linux-image-extra-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-image-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73-generic'

  
  First of all I suppose  the message should read  non-upgradable
  non-upgrable is possibly incorrect and should be corrected.

  Secondly I have no clue, what this message means so the error message
  should be revised to give more details.

  I think this as a minor bug but messages should always be correct,
  precise and possibly helpful.

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

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

[Touch-packages] [Bug 1527187] Re: Unable to hang up outgoing call

[Pat McGowan]

** Also 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 dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1527187

Title:
  Unable to hang up outgoing call

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  When I make an outgoing call, I am unable to hang up. I can do so only
  by changing to another app and then return to the dialer-ap.

  Step to reproduce:

  1.) Open the dialer-app
  2.) Start an outgoing call
  3.) Try to hang up by pushing the hang-up button

  Then the hang-up button is unresponsive.

  Further steps to workaround

  4.) Swipe from the right and switch to another application
  5.) A green panel appears on the top of the screen.
  6.) Click the green panel to return to the call
  7.) Now the hang up button works and you an hang up the call

  My System is the following: (I will translate some descriptions from german):
  - Hardware: BQ Aquaris 4.5 Ubuntu Version

  From Settings->Device Information-> Operating System :
  - OS-Build Number:  OTA-8.5
  - Ubuntu-Image-Part: 20151210
  - Ubuntu-Build-Description: Ubuntu 15.04 -armhf (20151210-005527)
  - Device-Image-Part: 20150821-736d127
  - Device-Builde-Description: KRILIN01A-S15A_BQ_L100EN_2028_151210
  - Adaption-Image-Part: 2015--36-46-vivid

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

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

[Touch-packages] [Bug 1416635] Re: NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()

[Christopher]

I found a fairly jenky work around. If while NetworkManager is off or
crashed I use the hardware key combo to turn off wifi it does so. Then
NetworkManager will start up. However it will attempt to enable wifi
itself. So the next move is while it's starting up right after
NetworkManager has turned the wifi chip back on you need to utilize the
key combo again to manually disable wifi.

Then if I wait for a bit I can turn on wifi via hardware chip and it
will crash in about a minute with the following in the logs:

```
Dec 22 13:21:03 nebraska NetworkManager[24469]:   WiFi hardware radio set 
enabled
Dec 22 13:21:03 nebraska NetworkManager[24469]:   WWAN hardware radio set 
disabled
Dec 22 13:21:03 nebraska NetworkManager[24469]:   WiFi now enabled by 
radio killswitch
Dec 22 13:21:03 nebraska NetworkManager[24469]:   (wlp2s0): supplicant 
interface state: starting -> ready
Dec 22 13:21:03 nebraska NetworkManager[24469]:   (wlp2s0): device state 
change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Dec 22 13:21:03 nebraska NetworkManager[24469]:   Device 'wlp2s0' has no 
connection; scheduling activate_check in 0 seconds.
Dec 22 13:21:19 nebraska NetworkManager[24469]:   WiFi now disabled by 
radio killswitch
Dec 22 13:21:19 nebraska NetworkManager[24469]:   (wlp2s0): device state 
change: disconnected -> unavailable (reason 'none') [30 20 0]
Dec 22 13:25:50 nebraska NetworkManager[24469]:   WiFi now enabled by 
radio killswitch
Dec 22 13:25:50 nebraska NetworkManager[24469]:   (wlp2s0): supplicant 
interface state: starting -> ready
Dec 22 13:25:50 nebraska NetworkManager[24469]:   (wlp2s0): device state 
change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Dec 22 13:25:50 nebraska NetworkManager[24469]:   Device 'wlp2s0' has no 
connection; scheduling activate_check in 0 seconds.
Dec 22 13:25:52 nebraska NetworkManager[24469]:   (wlp2s0): supplicant 
interface state: ready -> inactive
Dec 22 13:26:18 nebraska NetworkManager[24469]:   (wlp2s0): supplicant 
interface state: inactive -> scanning
Dec 22 13:26:50 nebraska systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=11/SEGV
Dec 22 13:26:50 nebraska systemd[1]: NetworkManager.service: Unit entered 
failed state.
Dec 22 13:26:50 nebraska systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
Dec 22 13:26:51 nebraska systemd[1]: NetworkManager.service: Service hold-off 
time over, scheduling restart.
Dec 22 13:26:51 nebraska systemd[1]: Stopped Network Manager.
Dec 22 13:26:51 nebraska systemd[1]: Starting Network Manager...
```

My first thought is that I might have a wireless chip that's
unsupported. However that doesn't seem to be the case given I'm running
a certified laptop. I'm still doing some investigation but now I seem to
be able to get NetworkManager to "stay up". Even if now I can't connect
to wifi.

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

Title:
  NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Crashing network-manager since latest upgrades of NetworkManager.
  See also bug 1415702

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  Date: Sat Jan 31 10:00:40 2015
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2011-07-14 (1296 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  IpRoute:
   default via 192.168.3.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.3.0/24 dev wlan0  proto kernel  scope link  src 192.168.3.182 
   192.168.3.0/24 dev eth0  proto kernel  scope link  src 192.168.3.101
  ProcCmdline: NetworkManager
  ProcEnviron:
   LANGUAGE=nl:en_AU:en
   TERM=linux
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
  Signal: 5
  SourcePackage: network-manager
  StacktraceTop:
   ASSERT_VALID_PATH_COMPONENT ()
   nm_utils_ip6_property_path ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()
  UpgradeStatus: Upgraded to vivid on 2015-01-20 (10 days ago)
  UserGroups:
   
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1416635/+subscriptions

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

[Touch-packages] [Bug 1283871] Re: Default mount points not suitable for photo import

[John McAleely]

". It just so happens it's only one of the few "well-known directories"
that Shotwell defines."

I'm surprised at this assumption. DCIM (and filename rules) are part of
now-ancient standards for digital cameras:

https://en.wikipedia.org/wiki/Design_rule_for_Camera_File_system

Mobile phones with cameras have by long convention also offered this
filesystem layout. My current iOS 9 device still does this, for example.

This is nothing to do with Shotwell's preferences.

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

** 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 mtp in Ubuntu.
https://bugs.launchpad.net/bugs/1283871

Title:
  Default mount points not suitable for photo import

Status in Canonical System Image:
  New
Status in mtp package in Ubuntu:
  Triaged
Status in shotwell package in Ubuntu:
  Invalid

Bug description:
  When I plug my Ubuntu Phone into my desktop I want to be able to
  import photos easily into my photo manager of choice (Shotwell in my
  case but others are available apparently). The photos should be
  available via a "DCIM" folder, but they're in "Photos" which Shotwell
  doesn't find. While I could use the "Import from folder" and navigate
  my way to Photos, I'd rather it Just Worked.

  Could we export photos over the "standard" DCIM folder to make this
  easier for everyone?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mtp-server 0.0.2+14.04.20131205-0ubuntu1
  Uname: Linux 3.4.0-4-mako armv7l
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: armhf
  Date: Mon Feb 24 01:01:39 2014
  InstallationDate: Installed on 2014-02-23 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf 
(20140223.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: mtp
  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/1283871/+subscriptions

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

[Touch-packages] [Bug 1416635] Re: NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()

[Christopher]

Wrong bug please ignore this comment.

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

Title:
  NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Crashing network-manager since latest upgrades of NetworkManager.
  See also bug 1415702

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu4
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  Date: Sat Jan 31 10:00:40 2015
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2011-07-14 (1296 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  IpRoute:
   default via 192.168.3.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.3.0/24 dev wlan0  proto kernel  scope link  src 192.168.3.182 
   192.168.3.0/24 dev eth0  proto kernel  scope link  src 192.168.3.101
  ProcCmdline: NetworkManager
  ProcEnviron:
   LANGUAGE=nl:en_AU:en
   TERM=linux
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
  Signal: 5
  SourcePackage: network-manager
  StacktraceTop:
   ASSERT_VALID_PATH_COMPONENT ()
   nm_utils_ip6_property_path ()
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()
  UpgradeStatus: Upgraded to vivid on 2015-01-20 (10 days ago)
  UserGroups:
   
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1416635/+subscriptions

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

[Touch-packages] [Bug 1527187] Re: Unable to hang up outgoing call

[Michał Sawicz]

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

** This bug has been marked a duplicate of bug 1528668
   [regression] Qt.application.active not working correctly

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

Title:
  Unable to hang up outgoing call

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  When I make an outgoing call, I am unable to hang up. I can do so only
  by changing to another app and then return to the dialer-ap.

  Step to reproduce:

  1.) Open the dialer-app
  2.) Start an outgoing call
  3.) Try to hang up by pushing the hang-up button

  Then the hang-up button is unresponsive.

  Further steps to workaround

  4.) Swipe from the right and switch to another application
  5.) A green panel appears on the top of the screen.
  6.) Click the green panel to return to the call
  7.) Now the hang up button works and you an hang up the call

  My System is the following: (I will translate some descriptions from german):
  - Hardware: BQ Aquaris 4.5 Ubuntu Version

  From Settings->Device Information-> Operating System :
  - OS-Build Number:  OTA-8.5
  - Ubuntu-Image-Part: 20151210
  - Ubuntu-Build-Description: Ubuntu 15.04 -armhf (20151210-005527)
  - Device-Image-Part: 20150821-736d127
  - Device-Builde-Description: KRILIN01A-S15A_BQ_L100EN_2028_151210
  - Adaption-Image-Part: 2015--36-46-vivid

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

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

[Touch-packages] [Bug 1528668] Re: [regression] Qt.application.active not working correctly

[Michał Sawicz]

Adding this code:

  Text {
text: "state: " + Qt.application.state + "\nactive: " + 
Qt.application.active
onTextChanged: console.debug(text)
  }

At the end of /usr/share/dialer-app/dialer-app.qml indeed does show
trouble, the application remains in "Inactive" state when in foreground
(and active remains false).

I'll be reverting that change for now.

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

Title:
  [regression] Qt.application.active not working correctly

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce:

  1) open dialer-app
  2) lock the screen
  3) unlock the screen

  Expected behavior:
  Qt.application.active == true

  Current behavior
  Qt.application.active == false until we manually switch the app to 
background/foreground again.

  Additional info:
  This is causing a bigger issue in the dialer-app functionality. It currently 
only refreshes the live call view when in foreground, so
  when dialer is in this state, calls are placed but the call controls don't 
work (like hangup or speaker mode).

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

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

[Touch-packages] [Bug 1528297] Re: libvpx FTBFS with gcc 5.3 on armhf

[Olivier Tilloy]

oxide 1.11.3-0ubuntu3 successfully built in silo 10, and tested that vp8 video 
playback works.
Will publish to xenial-proposed.

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

Title:
  libvpx FTBFS with gcc 5.3 on armhf

Status in firefox package in Ubuntu:
  New
Status in gcc-5 package in Ubuntu:
  New
Status in libvpx package in Ubuntu:
  New
Status in oxide-qt package in Ubuntu:
  In Progress

Bug description:
  (originally reported as bug #1527741)

  Trying to build libvpx from source in an up-to-date xenial arhmf
  environment, with gcc 5.3.1, fails with the following error:

  gcc  -marm -Wall -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -march=armv6 -DNDEBUG -O2 -fPIC -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=0 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall 
-Wdeclaration-after-statement -Wdisabled-optimization -Wpointer-arith 
-Wtype-limits -Wcast-qual -Wvla -Wimplicit-function-declaration -Wuninitialized 
-Wunused-variable -Wunused-but-set-variable -Wno-unused-function -I. 
-I"/tmp/libvpx-1.4.0" -c -o vp8/common/treecoder.c.o 
/tmp/libvpx-1.4.0/vp8/common/treecoder.c
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'tree2tok':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:9: error: invalid use of array 
with unspecified bounds
   const vp8_tree_index j = t[i++];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:34: warning: initialization makes 
integer from pointer without a cast [-Wint-conversion]
   const vp8_tree_index j = t[i++];
^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'branch_counts':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:13: error: invalid use of array 
with unspecified bounds
   i = tree[ i + b];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:15: warning: assignment makes 
integer from pointer without a cast [-Wint-conversion]
   i = tree[ i + b];
 ^
  Makefile:148: recipe for target 'vp8/common/treecoder.c.o' failed

  
  I’m attaching a full build log. This is reproducible both on a porter box and 
in a armhf chroot.

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

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

[Touch-packages] [Bug 1528279] Re: Spinner not shown

[Daniel van Vugt]

Fair enough. The fix is still landed in the 0.3 branch so Fix Committed
is accurate. Note it's still open (Triaged) in the Ubuntu task.

** Changed in: unity-system-compositor/0.3
   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-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1528279

Title:
  Spinner not shown

Status in Canonical System Image:
  In Progress
Status in Unity System Compositor:
  Fix Committed
Status in Unity System Compositor 0.3 series:
  Fix Committed
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  STEPS:
  1. install image 209
  2. Note not Ubutnu Logo on boot
  3. Once the system start enable developer mode
  4. adb shell
  5. `stop unity8`
  6. This will produce a crash for the spinner

  This blank logo happens on Arale and krillin for sure.

  EXPECTED:
  I always expect to see the logo

  ACTUAL:
  The logo is missing on boot and missing from the spinner on `stop unity8`


  The Ubuntu spinner is not shown.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity-system-compositor 0.2.0+15.04.20151216.1-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Mon Dec 21 17:19:32 2015
  ExecutablePath: /usr/bin/unity-system-compositor-spinner
  ExecutableTimestamp: 1450306669
  GraphicsCard:

  InstallationDate: Installed on 2015-12-21 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20151221-020303)
  ProcCmdline: /usr/bin/unity-system-compositor-spinner
  ProcCwd: /
  ProcEnviron:

  Signal: 11
  SourcePackage: unity-system-compositor
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  version.libdrm: libdrm2 2.4.60-2
  version.lightdm: lightdm 1.14.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1513565] Re: libpython2.7 uses the 3.x name for ConfigParser

[Andy Caldwell]

Agreed, latest packages on toolchain-r are working correctly.  Thanks!

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

Title:
  libpython2.7 uses the 3.x name for ConfigParser

Status in python-pip package in Ubuntu:
  Confirmed
Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Installing a minimal virtualenv on Trusty Tahr (using libpython-
  minimal 2.7.10-4~14.04), I ran into crashes because:

File "/usr/lib/python2.7/ssl.py", line 491, in inner
  import configparser
  ImportError: No module named configparser

  Looking at the code in ssl.py, it uses "import configparser" even
  though the package is called "ConfigParser" in Python 2.7 (it changed
  in 3.0), this means that a clean virtualenv cannot install any
  packages using easy_install (since they're served over an https
  connection which uses the code in ssl.py).

  As a workaround, you can `pip install configparser` to install the
  package under the 3.0 name or change the code to be `import
  ConfigParser as configparser` to import the correct package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1513565/+subscriptions

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

[Touch-packages] [Bug 1528735] [NEW] Suspend reboots every second time on Lenovo G50-45

[David Cameron Staples]

Public bug reported:

Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
Install detected UEFI, and installed in UEFI mode. (I have attempted to
change to legacy boot, and got it to a state where it was booting
without /sys/firmware/efi/ being present, but behaviour persisted.)

Suspending the laptop, whether by closing the lid, choosing the suspend
option from the menu, or directly typing "sudo pm-suspend" works
perfectly well... once.

The second attempt to suspend, whether immediately or hours later,
suspends the laptop (I can see the screen turn off, and hear the disk
and fans stop, but a moment later the screen shows bright yellow console
text declaring "Warning!!! Boot script table modified!!! Please contact
your vendor.", and then it hard reboots.

This appears to be a weird interaction between suspend and UEFI
protection, but others have reported that they have had working suspend
when installed alone (and presumably in legacy from the start), but this
behaviour appeared when reinstalled as dual-boot (when presumably UEFI
would have had to be on). (http://askubuntu.com/questions/675683
/suspend-does-not-work-more-than-once-after-reboot-ubuntu-15-04-dual-
boot/712232 and earlier http://askubuntu.com/questions/651481/boot-
script-table-modified-please-contact-vendor, from different people.)

Beyond the investigations I have done, I know next to nothing about
UEFI, or how Suspend might be interacting with it. Much less why it
appears to work perfectly exactly once.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pm-utils 1.4.1-13ubuntu0.1
ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Dec 23 13:27:11 2015
InstallationDate: Installed on 2015-12-19 (3 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  Suspend reboots every second time on Lenovo G50-45

Status in pm-utils package in Ubuntu:
  New

Bug description:
  Fresh install of Xubuntu 14.04.3, replacing existing OEM Windows 10.
  Install detected UEFI, and installed in UEFI mode. (I have attempted
  to change to legacy boot, and got it to a state where it was booting
  without /sys/firmware/efi/ being present, but behaviour persisted.)

  Suspending the laptop, whether by closing the lid, choosing the
  suspend option from the menu, or directly typing "sudo pm-suspend"
  works perfectly well... once.

  The second attempt to suspend, whether immediately or hours later,
  suspends the laptop (I can see the screen turn off, and hear the disk
  and fans stop, but a moment later the screen shows bright yellow
  console text declaring "Warning!!! Boot script table modified!!!
  Please contact your vendor.", and then it hard reboots.

  This appears to be a weird interaction between suspend and UEFI
  protection, but others have reported that they have had working
  suspend when installed alone (and presumably in legacy from the
  start), but this behaviour appeared when reinstalled as dual-boot
  (when presumably UEFI would have had to be on).
  (http://askubuntu.com/questions/675683/suspend-does-not-work-more-
  than-once-after-reboot-ubuntu-15-04-dual-boot/712232 and earlier
  http://askubuntu.com/questions/651481/boot-script-table-modified-
  please-contact-vendor, from different people.)

  Beyond the investigations I have done, I know next to nothing about
  UEFI, or how Suspend might be interacting with it. Much less why it
  appears to work perfectly exactly once.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27~14.04.1-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 23 13:27:11 2015
  InstallationDate: Installed on 2015-12-19 (3 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1528735/+subscriptions

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

[Touch-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode

[Tony Espy]

I'm able to reproduce it every time on a krillin running OTA8.5 ( bluez4
userspace ):

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 26
device name: mako
channel: ubuntu-touch/stable/ubuntu
last update: 2015-12-22 23:02:17
version version: 26
version ubuntu: 20151210
version tag: OTA-8.5
version device: 20150911
version custom: 20151210

Can't reproduce on mako running OTA8.5 ( bluez4 userspace ):

phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 26
device name: mako
channel: ubuntu-touch/stable/ubuntu
last update: 2015-12-22 23:02:17
version version: 26
version ubuntu: 20151210
version tag: OTA-8.5
version device: 20150911
version custom: 20151210

Can't reproduce on arale running OTA-8.5 ( stable/meizu.en #8 ); tested
both with and without a valid SIM card.

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

Title:
  Bluetooth initiated after quitting airplane mode

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in urfkill package in Ubuntu:
  Confirmed

Bug description:
  This happens despite bluetooth not being enabled when entering
  airplane mode.

  On Aquaris E5 OTA-5.

  Boot with bluetooth disabled
  Turn on flight mode
  turn off flight mode
  Bluetooth gets enabled

  See bug #1421249 for related symptoms

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

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

[Touch-packages] [Bug 1528734] Re: package python-pkg-resources 18.4-1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python-pkg-resources 18.4-1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  It will not let me open ubuntu software center

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: python-pkg-resources 18.4-1
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Wed Dec 23 01:45:00 2015
  Dependencies:
   
  DuplicateSignature: package:python-pkg-resources:18.4-1:subprocess new 
pre-removal script returned error exit status 127
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2015-12-21 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: python-setuptools
  Title: package python-pkg-resources 18.4-1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1528734/+subscriptions

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

[Touch-packages] [Bug 1528734] [NEW] package python-pkg-resources 18.4-1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127

[Steven]

Public bug reported:

It will not let me open ubuntu software center

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: python-pkg-resources 18.4-1
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Wed Dec 23 01:45:00 2015
Dependencies:
 
DuplicateSignature: package:python-pkg-resources:18.4-1:subprocess new 
pre-removal script returned error exit status 127
ErrorMessage: subprocess new pre-removal script returned error exit status 127
InstallationDate: Installed on 2015-12-21 (2 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: python-setuptools
Title: package python-pkg-resources 18.4-1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python-setuptools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package wily

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

Title:
  package python-pkg-resources 18.4-1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 127

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  It will not let me open ubuntu software center

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: python-pkg-resources 18.4-1
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Wed Dec 23 01:45:00 2015
  Dependencies:
   
  DuplicateSignature: package:python-pkg-resources:18.4-1:subprocess new 
pre-removal script returned error exit status 127
  ErrorMessage: subprocess new pre-removal script returned error exit status 127
  InstallationDate: Installed on 2015-12-21 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: python-setuptools
  Title: package python-pkg-resources 18.4-1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1528734/+subscriptions

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

[Touch-packages] [Bug 1526987] Re: package systemd 225-1ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package systemd 225-1ubuntu9 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  error on install

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  Date: Fri Dec 11 17:46:26 2015
  DuplicateSignature: package:systemd:225-1ubuntu9:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-02-08 (311 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=0f39d1b3-ff04-41d9-87fd-5bf70bd2f226 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: systemd
  Title: package systemd 225-1ubuntu9 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-12-12 (4 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Touch-packages] [Bug 1524414] Re: [regression] transparent indicator on mx4 with the 0.18 release silo (21)

[Daniel van Vugt]

mir (0.18.0+16.04.20151216.1-0ubuntu1) xenial; urgency=medium

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

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

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

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

Title:
  [regression] transparent indicator on mx4 with the 0.18 release silo
  (21)

Status in Mir:
  Fix Committed
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Indicators are transparent when they should be opaque on the mx4 after
  installing the release silo 21 containing the 0.18 release.

  marking critical, as its blocking 0.18 release

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

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

[Touch-packages] [Bug 1528406] Re: image provider test fails in CI train for arm64 (Vivid only)

[Michi Henning]

I worked around the problem by changing this:

QSignalSpy spy(response, ::finished);

to that:

QSignalSpy spy(response, SIGNAL(finished()));

Seeing this happens only on arm64 on Vivid and passes everywhere else,
I'd say this is a Qt problem of some kind?

** Also affects: qt-sdk (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  image provider test fails in CI train for arm64 (Vivid only)

Status in qt-sdk package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  The image provider test fails consistently on arm64 only, in CI train
  only (passes on Jenkins CI), and only on Vivid (passes on Xenial).

  https://launchpadlibrarian.net/230899583/buildlog_ubuntu-vivid-
  arm64.thumbnailer_2.3%2B15.04.20151222-0ubuntu1_BUILDING.txt.gz

  Note the "QSignalSpy: Not a valid signal: ''" messages.

  8: [ RUN  ] ProviderTest.thumbnail_image
  8: thumbnailer-service: [00:35:35.490] Initializing
  8: thumbnailer-service: [00:35:35.527] image cache: 0 entries, 0 bytes, 
hit rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
  8: thumbnailer-service: [00:35:35.527] thumbnail cache: 0 entries, 0 bytes, 
hit rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
  8: thumbnailer-service: [00:35:35.527] failure cache:   0 entries, 0 bytes, 
hit rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
  8: QSignalSpy: Not a valid signal: ''
  8: thumbnailer-service: [00:35:35.544] "thumbnail: 
/«BUILDDIR»/thumbnailer-2.3+15.04.20151222/tests/media/orientation-1.jpg 
(128,128): 0.011494 sec (MISS)"
  8: 
/«BUILDDIR»/thumbnailer-2.3+15.04.20151222/tests/image-providers/provider_test.cpp:84:
 Failure
  8: Value of: spy.wait(SIGNAL_WAIT_TIME)
  8:   Actual: false
  8: Expected: true
  8: thumbnailer-service: [00:35:45.704] Exiting
  8: [  FAILED  ] ProviderTest.thumbnail_image (10553 ms)
  8: [ RUN  ] ProviderTest.thumbnail_cancel
  8: thumbnailer-service: [00:35:46.041] Initializing
  8: thumbnailer-service: [00:35:46.073] image cache: 0 entries, 0 bytes, 
hit rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
  8: thumbnailer-service: [00:35:46.073] thumbnail cache: 0 entries, 0 bytes, 
hit rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
  8: thumbnailer-service: [00:35:46.073] failure cache:   0 entries, 0 bytes, 
hit rate 0.00 (0/0), avg hit run 0.00, avg miss run 0.00
  8: QSignalSpy: Not a valid signal: ''
  8: thumbnailer-service: [00:35:46.086] "thumbnail: 
/«BUILDDIR»/thumbnailer-2.3+15.04.20151222/tests/media/orientation-1.jpg 
(128,128): 0.010912 sec (MISS)"
  8: 
/«BUILDDIR»/thumbnailer-2.3+15.04.20151222/tests/image-providers/provider_test.cpp:84:
 Failure
  8: Value of: spy.wait(SIGNAL_WAIT_TIME)
  8:   Actual: false
  8: Expected: true
  8: thumbnailer-service: [00:35:55.713] Exiting
  8: [  FAILED  ] ProviderTest.thumbnail_cancel (10009 ms)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt-sdk/+bug/1528406/+subscriptions

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

[Touch-packages] [Bug 1528668] Re: Qt.application.active not working correctly

[Michał Sawicz]

As per http://doc.qt.io/qt-5/qml-qtqml-qt.html#application-prop

application.active  Deprecated, use Qt.application.state ==
Qt.ApplicationActive instead.

We should not have changed the behaviour of the .active property though.

** Summary changed:

- dialer-app not getting focused after screen unlock
+ Qt.application.active not working correctly

** Summary changed:

- Qt.application.active not working correctly
+ [regression] Qt.application.active not working correctly

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

Title:
  [regression] Qt.application.active not working correctly

Status in Canonical System Image:
  Triaged
Status in qtubuntu package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce:

  1) open dialer-app
  2) lock the screen
  3) unlock the screen

  Expected behavior:
  Qt.application.active == true

  Current behavior
  Qt.application.active == false until we manually switch the app to 
background/foreground again.

  Additional info:
  This is causing a bigger issue in the dialer-app functionality. It currently 
only refreshes the live call view when in foreground, so
  when dialer is in this state, calls are placed but the call controls don't 
work (like hangup or speaker mode).

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

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

[Touch-packages] [Bug 1528670] Re: Incoming call when locked freezes the screen

[Michał Sawicz]

Most likely dupe of bug #1528668

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

Title:
  Incoming call when locked freezes the screen

Status in dialer-app package in Ubuntu:
  New

Bug description:
  I called into a phone that was suspended/screen off
  Answered the call via the notification
  the dialer appeared but did not update the caller info or the connection
  I hung up from the calling side and the UI on the receiving side froze
  Power button cleared it up

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

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

[Touch-packages] [Bug 1528139] Re: serialize_profile_from_old_profile() crash if file contains multiple profiles

[Christian Boltz]

Which messages exactly?
(Please open a new bug for it, because that's totally unrelated to the crash 
reported here.)
(It can't be something with a strange log format, because aa-logprof 
understands your log in general.)

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

Title:
  serialize_profile_from_old_profile() crash if file contains multiple
  profiles

Status in AppArmor:
  New
Status in AppArmor 2.10 series:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  = Changed Local Profiles =

  The following local profiles were changed. Would you like to save
  them?

   [1 - /sbin/dhclient]
2 - /usr/sbin/nmbd 
3 - /usr/bin/snx 
4 - /usr/sbin/dnsmasq 
5 - /{usr/,}bin/ping 
6 - /usr/sbin/smbd 
7 - /usr/lib/telepathy/mission-control-5 
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2197, in 
do_logprof_pass
  save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2277, in 
save_profiles
  newprofile = serialize_profile_from_old_profile(aa[which], which, '')
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3961, in 
serialize_profile_from_old_profile
  if write_prof_data[hat]['network'].is_covered(network_obj, True, True):
  AttributeError: 'collections.defaultdict' object has no attribute 'is_covered'

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-v7wx9fu9.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

  When I pressed V button aa-logprof exits with error.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apparmor 2.10-0ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Dec 21 09:54:51 2015
  InstallationDate: Installed on 2014-04-19 (611 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-21-generic 
root=/dev/mapper/ubuntu-root ro splash elevator=cfq nomdmonddf nomdmonisw 
crashkernel=384M-:128M
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to wily on 2015-11-14 (36 days ago)

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

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

[Touch-packages] [Bug 1528639] Re: Network Manager Crashes Shortly after Starting

[Christopher]

I found a fairly jenky work around. If while NetworkManager is off or
crashed I use the hardware key combo to turn off wifi it does so. Then
NetworkManager will start up. However it will attempt to enable wifi
itself. So the next move is while it's starting up right after
NetworkManager has turned the wifi chip back on you need to utilize the
key combo again to manually disable wifi.

Then if I wait for a bit I can turn on wifi via hardware chip and it
will crash in about a minute with the following in the logs:

```
Dec 22 13:21:03 nebraska NetworkManager[24469]:  WiFi hardware radio set 
enabled
Dec 22 13:21:03 nebraska NetworkManager[24469]:  WWAN hardware radio set 
disabled
Dec 22 13:21:03 nebraska NetworkManager[24469]:  WiFi now enabled by 
radio killswitch
Dec 22 13:21:03 nebraska NetworkManager[24469]:  (wlp2s0): supplicant 
interface state: starting -> ready
Dec 22 13:21:03 nebraska NetworkManager[24469]:  (wlp2s0): device state 
change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Dec 22 13:21:03 nebraska NetworkManager[24469]:  Device 'wlp2s0' has no 
connection; scheduling activate_check in 0 seconds.
Dec 22 13:21:19 nebraska NetworkManager[24469]:  WiFi now disabled by 
radio killswitch
Dec 22 13:21:19 nebraska NetworkManager[24469]:  (wlp2s0): device state 
change: disconnected -> unavailable (reason 'none') [30 20 0]
Dec 22 13:25:50 nebraska NetworkManager[24469]:  WiFi now enabled by 
radio killswitch
Dec 22 13:25:50 nebraska NetworkManager[24469]:  (wlp2s0): supplicant 
interface state: starting -> ready
Dec 22 13:25:50 nebraska NetworkManager[24469]:  (wlp2s0): device state 
change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Dec 22 13:25:50 nebraska NetworkManager[24469]:  Device 'wlp2s0' has no 
connection; scheduling activate_check in 0 seconds.
Dec 22 13:25:52 nebraska NetworkManager[24469]:  (wlp2s0): supplicant 
interface state: ready -> inactive
Dec 22 13:26:18 nebraska NetworkManager[24469]:  (wlp2s0): supplicant 
interface state: inactive -> scanning
Dec 22 13:26:50 nebraska systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=11/SEGV
Dec 22 13:26:50 nebraska systemd[1]: NetworkManager.service: Unit entered 
failed state.
Dec 22 13:26:50 nebraska systemd[1]: NetworkManager.service: Failed with result 
'core-dump'.
Dec 22 13:26:51 nebraska systemd[1]: NetworkManager.service: Service hold-off 
time over, scheduling restart.
Dec 22 13:26:51 nebraska systemd[1]: Stopped Network Manager.
Dec 22 13:26:51 nebraska systemd[1]: Starting Network Manager...
```

My first thought is that I might have a wireless chip that's
unsupported. However that doesn't seem to be the case given I'm running
a certified laptop. I'm still doing some investigation but now I seem to
be able to get NetworkManager to "stay up". Even if now I can't connect
to wifi.

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

Title:
  Network Manager Crashes Shortly after Starting

Status in network-manager package in Ubuntu:
  New

Bug description:
  After starting Network Manager It attempts to start a few times and
  then crashes. Journalctl shows the following error:

  Dec 22 08:32:58 nebraska NetworkManager[12519]:   Writing DNS 
information to /sbin/resolvconf
  Dec 22 08:32:58 nebraska dnsmasq[11405]: setting upstream servers from DBus
  Dec 22 08:32:58 nebraska dnsmasq[11405]: using nameserver 139.49.202.10#53
  Dec 22 08:32:58 nebraska dnsmasq[11405]: using nameserver 139.49.202.11#53
  Dec 22 08:32:58 nebraska dnsmasq[11405]: using nameserver 10.240.137.51#53
  Dec 22 08:32:59 nebraska systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 22 08:32:59 nebraska systemd[1]: NetworkManager.service: Unit entered 
failed state.
  Dec 22 08:32:59 nebraska systemd[1]: NetworkManager.service: Failed with 
result 'core-dump'.
  Dec 22 08:32:59 nebraska systemd[1]: NetworkManager.service: Service hold-off 
time over, scheduling restart.
  Dec 22 08:32:59 nebraska systemd[1]: Stopped Network Manager.
  Dec 22 08:32:59 nebraska systemd[1]: NetworkManager.service: Start request 
repeated too quickly.
  Dec 22 08:32:59 nebraska systemd[1]: Failed to start Network Manager.
  Dec 22 08:32:59 nebraska systemd[1]: NetworkManager.service: Unit entered 
failed state.
  Dec 22 08:32:59 nebraska systemd[1]: NetworkManager.service: Failed with 
result 'start-limit'.

  Network Manager's Version is 1.0.4 and Ubuntu version is 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1528639/+subscriptions

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

[Touch-packages] [Bug 1396180] Re: package lsb-core 4.1+Debian11ubuntu6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package lsb-core 4.1+Debian11ubuntu6 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in lsb package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 14.04 problem when updated programs

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lsb-core 4.1+Debian11ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Tue Nov 25 15:22:53 2014
  DuplicateSignature: package:lsb-core:4.1+Debian11ubuntu6:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-08-22 (95 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: lsb
  Title: package lsb-core 4.1+Debian11ubuntu6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1526960] Re: on_ac_power doesn't notice usb powersupply

[Brian Murray]

** No longer affects: unattended-upgrades (Ubuntu)

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

Title:
  on_ac_power doesn't notice usb powersupply

Status in powermgmt-base package in Ubuntu:
  New

Bug description:
  Some ARM-Boards have more then one possible power-supply, for example you can 
power them also over USB. But /usr/bin/on_ac_power returns that there is no 
connected power-supply if its an usb power-supply.
  you can solve the Problem if you also allow an USB Device as a power-supply.
  This causes Problems like unattended-upgrades and other features are not 
working. 
  You can do this if you patch the /usr/bin/on_ac_power script with the 
attached patch.

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

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

[Touch-packages] [Bug 1528297] Re: libvpx FTBFS with gcc 5.3 on armhf

[Launchpad Bug Tracker]

** Branch linked: lp:~oxide-developers/oxide/packaging.xenial

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

Title:
  libvpx FTBFS with gcc 5.3 on armhf

Status in firefox package in Ubuntu:
  New
Status in gcc-5 package in Ubuntu:
  New
Status in libvpx package in Ubuntu:
  New
Status in oxide-qt package in Ubuntu:
  In Progress

Bug description:
  (originally reported as bug #1527741)

  Trying to build libvpx from source in an up-to-date xenial arhmf
  environment, with gcc 5.3.1, fails with the following error:

  gcc  -marm -Wall -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -march=armv6 -DNDEBUG -O2 -fPIC -U_FORTIFY_SOURCE 
-D_FORTIFY_SOURCE=0 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall 
-Wdeclaration-after-statement -Wdisabled-optimization -Wpointer-arith 
-Wtype-limits -Wcast-qual -Wvla -Wimplicit-function-declaration -Wuninitialized 
-Wunused-variable -Wunused-but-set-variable -Wno-unused-function -I. 
-I"/tmp/libvpx-1.4.0" -c -o vp8/common/treecoder.c.o 
/tmp/libvpx-1.4.0/vp8/common/treecoder.c
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'tree2tok':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:9: error: invalid use of array 
with unspecified bounds
   const vp8_tree_index j = t[i++];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:32:34: warning: initialization makes 
integer from pointer without a cast [-Wint-conversion]
   const vp8_tree_index j = t[i++];
^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c: In function 'branch_counts':
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:13: error: invalid use of array 
with unspecified bounds
   i = tree[ i + b];
   ^
  /tmp/libvpx-1.4.0/vp8/common/treecoder.c:96:15: warning: assignment makes 
integer from pointer without a cast [-Wint-conversion]
   i = tree[ i + b];
 ^
  Makefile:148: recipe for target 'vp8/common/treecoder.c.o' failed

  
  I’m attaching a full build log. This is reproducible both on a porter box and 
in a armhf chroot.

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

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

[Touch-packages] [Bug 1519999] Re: The callback given to mir_connection_create_buffer_stream may not be invoked in some cases

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  The callback given to mir_connection_create_buffer_stream may not be
  invoked in some cases

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  If the server fails to create a buffer stream, the callback given to
  mir_connection_create_buffer_stream is never invoked.

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

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

[Touch-packages] [Bug 1517133] Re: [regression] Mouse speed in Unity8 is much lower than elsewhere (to the point of useless)

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Mouse speed in Unity8 is much lower than elsewhere (to
  the point of useless)

Status in Mir:
  Fix Released
Status in QtMir:
  Incomplete
Status in mir package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Running unity8 as a session on the desktop.

  The mouse is so "slow" (i.e a movement in reality moves it very few
  pixels on screen) that i can't really use it since i need to lift it
  and restart the movement a few times if i want to go to the other side
  of the screen.

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

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

[Touch-packages] [Bug 1506331] Re: [regression] Resampled touch events are slightly less regular than they used to be

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Resampled touch events are slightly less regular than
  they used to be

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] Resampled touch events are slightly less regular than
  they used to be.

  I noticed after fixing the stuttery touch scrolling of bug 1486341
  that Mir still doesn't provide completely smooth touch events for
  scrolling. And we didn't notice in our most relevant test program
  `mir_demo_client_fingerpaint' because that is specifically designed to
  bypass input resampling.

  It appears Mir's resampled touch events became slightly less even in
  r2782. And reverting that revision makes them smoother.

  Screenshot attached, from:
  env MIR_CLIENT_INPUT_RATE=59 mir_demo_client_fingerpaint

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

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

[Touch-packages] [Bug 1514884] Re: There's something racy in NestedServer.display_orientation_changes_are_forwarded_to_host

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  There's something racy in
  NestedServer.display_orientation_changes_are_forwarded_to_host

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Leave this running a few minutes and come back to a hung process:

  while bin/mir_acceptance_tests
  --gtest_filter=NestedServer.display_orientation_changes_are_forwarded_to_host;
  do :; done

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

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

[Touch-packages] [Bug 1515515] Re: Shells that inject user input events need to agree with the system compositor on the clock to use

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Shells that inject user input events need to agree with the system
  compositor on the clock to use

Status in Mir:
  Fix Released
Status in QtMir:
  Invalid
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  If we try to change the input platforms to also use CLOCK_MONOTONIC
  (or std::chrono::steady_clock) in mir we also need to change unity8.
  Otherwise input resampling will get confused by the large difference
  in time stamps and long press calculation will fail.

  Mir should provide an interface to the clock used for user input event
  time stamps - both server and client side.

  Qtmir should ensure that it uses the same clock and that dispatch
  within the qtEvent loop does not cause a mix of used clocks..

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

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

[Touch-packages] [Bug 1521795] Re: BasicSurface::set_cursor_image can create references to null pointers

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  BasicSurface::set_cursor_image can create references to null pointers

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Creating references to null pointers is undefined behavior.

  This can happen if a client disables the cursor on a surface via:

   auto conf = mir_cursor_configuration_from_name(mir_disabled_cursor_name);
  mir_surface_configure_cursor(mir_surface, conf);

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

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

[Touch-packages] [Bug 1522105] Re: NestedServer.display_configuration_reset_when_application_exits segfaults

[Kevin DuBois]

** Changed in: mir/0.18
   Status: Fix Committed => Fix Released

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  NestedServer.display_configuration_reset_when_application_exits
  segfaults

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  NestedServer.display_configuration_reset_when_application_exits will
  intermittently segfault.

  One can reproduce with
  mir_acceptance_tests 
--gtest_filter=NestedServer.display_configuration_reset_when_application_exits 
--gtest_repeat=1000

  GDB bt:
  http://pastebin.ubuntu.com/13626488/

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

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

[Touch-packages] [Bug 1517990] Re: Test failure in NestedServer.display_configuration_reset_when_application_exits

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Test failure in
  NestedServer.display_configuration_reset_when_application_exits

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Repeating all tests (iteration 429) . . .

  Note: Google Test filter = 
NestedServer.display_configuration_reset_when_application_exits
  [==] Running 1 test from 1 test case.
  [--] Global test environment set-up.
  [--] 1 test from NestedServer
  [ RUN ] NestedServer.display_configuration_reset_when_application_exits
  
/home/alan/display_server/mir3/tests/acceptance-tests/test_nested_mir.cpp:755: 
Failure
  Value of: condition.woken()
Actual: false
  Expected: true

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

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

[Touch-packages] [Bug 1520217] Re: CI test failures due to memory errors during GLibMainLoop shutdown

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  CI test failures due to memory errors during GLibMainLoop shutdown

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  As seen in:

  https://jenkins.qa.ubuntu.com/job/mir-wily-amd64-ci/1814/consoleFull
  https://jenkins.qa.ubuntu.com/job/mir-xenial-amd64-ci/9/consoleFull

  13: ==30192== Invalid read of size 8
  13: ==30192== at 0x5FBFFE6: ??? (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4700.1)
  13: ==30192== by 0x5FC013B: ??? (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4700.1)
  13: ==30192== by 0x7B0F39: mir::GLibMainLoop::stop() (glib_main_loop.cpp:159)
  13: ==30192== by 0x91203C: mir_test_framework::ServerRunner::stop_server() 
(server_runner.cpp:77)
  ...
  13: ==30192== Address 0xd059460 is 80 bytes inside a block of size 176 free'd
  13: ==30192== at 0x4C2CE2B: free (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  13: ==30192== by 0x5FC0977: g_main_context_unref (in 
/lib/x86_64-linux-gnu/libglib-2.0.so.0.4700.1)
  13: ==30192== by 0x7B2AE8: mir::GLibMainLoop::~GLibMainLoop() 
(glib_main_loop.h:50)
  ...

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

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

[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse scrolling speed

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [enhancement] Ubuntu needs a way to set mouse scrolling speed

Status in gnome-control-center:
  Unknown
Status in GTK+:
  Unknown
Status in One Hundred Papercuts:
  Triaged
Status in Mir:
  Fix Released
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions

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

[Touch-packages] [Bug 1514391] Re: mircookie-dev is missing nettle-dev dependency

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mircookie-dev is missing nettle-dev dependency

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  mircookie.pc requires (privately) nettle.pc but the mircookie-dev
  package doesn't depend on nettle-dev to ensure nettle.pc is available.

  This causes builds that use pkg-config and depend on mircookie (even
  transitively, e.g., through mirclient, which practically means all
  builds) to fail.

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

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

[Touch-packages] [Bug 1511538] Re: 1/2 screen on external monitor

[Kevin DuBois]

** Changed in: canonical-pocket-desktop
   Status: Fix Committed => Fix Released

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  1/2 screen on external monitor

Status in canonical-pocket-desktop:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.17 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  using N7 latest PD image

  connect bt mouse and keyboard
  connected to monitor
  opened several apps (clock, msg, phone, browser, twitter, u-s-s, terminal, 
camera, gallery, calculator, pathwind) - did quite a bit of window moving, max, 
min, close, relaunch

  after a while, disconnected n7 from monitor, then reconnected
  only 1/2 the screen on the monitor was used
  disconnected, reconnected, still only 1/2 the screen used, possible low mem ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511538/+subscriptions

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

[Touch-packages] [Bug 1516670] Re: Nesting Mir servers with assorted display configs causes lockup

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Nesting Mir servers with assorted display configs causes lockup

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Using a mako, with external display attached, flashed with ubuntu-pd
  and Mir trunk + a few branches:

  lp:~alan-griffiths/mir/fix-1463873
  lp:~alan-griffiths/mir/fullscreen-sticks
  lp:~alan-griffiths/mir/name-nested-display-for-output
  lp:~alan-griffiths/mir/more-detailed-log-from-shell-report

  (The latter three are probably irrelevant, the first one is needed for
  the scenario to work well enough to see this error.)

  $ sudo stop lightdm
  $ cd mir/build
  $ bin/mir_demo_server --window-manager system-compositor --display-config 
sidebyside  --file /tmp/mir_socket

  (in a new ssh session)
  $ cd mir/build
  $ bin/mir_demo_server --host /tmp/mir_socket --display-config clone

  (in a new ssh session)
  $ cd mir/build
  $ bin/mir_demo_standalone_render_surfaces --no-file --display-config single 
--host /run/user/32011/mir_socket
  ^C
  (This last command can be repeated numerous times without problems 
manifesting)

  $ bin/mir_demo_client_egltriangle

  The triangle is displayed, but doesn't rotate.

  In the second (nested) session there's an error:

  [1447687623.835199]  MirBufferStream: Error processing incoming
  buffer error registering graphics buffer for client use

  Neither the client, not nested server respond to ^C until the host
  server is stopped with ^C.

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

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

[Touch-packages] [Bug 1517781] Re: CI test failures in various NesterServer tests

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  CI test failures in various NesterServer tests

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  When running the NestedServer tests repeatedly we get failures in
  various tests. The failures are of two sorts:

  1. Test hangs forever
  2. terminate called after throwing an instance of  
'boost::exception_detail::clone_impl'
   what(): Failed to trigger thread shutdown: Bad file descriptor

  Examples from CI:

  http://s-jenkins.ubuntu-ci:8080/job/mir-wily-amd64-ci/1739/consoleFull
  
http://s-jenkins.ubuntu-ci:8080/job/mir-clang-vivid-amd64-build/3822/consoleFull

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

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

[Touch-packages] [Bug 1522093] Re: SessionMediator::exchange_buffer can create references to null pointers

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  SessionMediator::exchange_buffer can create references to null
  pointers

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  A malformed BufferRequest can result in
  SessionMediator::exchange_buffer creating a reference to a null
  pointer which is undefined behavior.

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

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

[Touch-packages] [Bug 1522122] Re: [regression] Mir fails to build with -DMIR_PLATFORM=mesa-kms (e.g. ppc64el, powerpc, arm64)

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Mir fails to build with -DMIR_PLATFORM=mesa-kms (e.g.
  ppc64el, powerpc, arm64)

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  lp:mir/0.18 (and likely lp:mir) fails to build from source with the
  same error on ppc/arm64

  
/«BUILDDIR»/mir-0.18.0+16.04.20151202/tests/unit-tests/graphics/test_platform_prober.cpp:108:25:
 error: 'mtd' was not declared in this scope
   ::testing::NiceMock mock_drm;
   ^

  from: https://launchpadlibrarian.net/228193862/buildlog_ubuntu-xenial-
  ppc64el.mir_0.18.0%2B16.04.20151202-0ubuntu1_BUILDING.txt.gz

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

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

[Touch-packages] [Bug 1527187] Re: Unable to hang up outgoing call

[Tiago Salem Herrmann]

dialer-app only update existing calls in the live call screen when it is in 
foreground. (we unregister the telepathy observer when it's in background to 
avoid other problems).
If you lock the device with dialer-app open, then unlock it, it is still 
reported as inactive by Qt.application.active.
If we try to make a call in this state, the app won't be able to control it. 
(including the hangup button not working)
Once we swipe the app to background and then foreground again it works again, 
and Qt.application.active reports the right state.

Did we land any change to the dialer-app focus logic on unity recently?

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

Title:
  Unable to hang up outgoing call

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  When I make an outgoing call, I am unable to hang up. I can do so only
  by changing to another app and then return to the dialer-ap.

  Step to reproduce:

  1.) Open the dialer-app
  2.) Start an outgoing call
  3.) Try to hang up by pushing the hang-up button

  Then the hang-up button is unresponsive.

  Further steps to workaround

  4.) Swipe from the right and switch to another application
  5.) A green panel appears on the top of the screen.
  6.) Click the green panel to return to the call
  7.) Now the hang up button works and you an hang up the call

  My System is the following: (I will translate some descriptions from german):
  - Hardware: BQ Aquaris 4.5 Ubuntu Version

  From Settings->Device Information-> Operating System :
  - OS-Build Number:  OTA-8.5
  - Ubuntu-Image-Part: 20151210
  - Ubuntu-Build-Description: Ubuntu 15.04 -armhf (20151210-005527)
  - Device-Image-Part: 20150821-736d127
  - Device-Builde-Description: KRILIN01A-S15A_BQ_L100EN_2028_151210
  - Adaption-Image-Part: 2015--36-46-vivid

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

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

[Touch-packages] [Bug 1528655] [NEW] Wily/15.10 - systemd hangs reboot + shutdown for long periods of time

[David Favor]

Public bug reported:

Yet another horrible bug related to systemd which delays shutdowns by
minutes.

https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1374759
surfaces this problem + the bug I'm reporting here is a separate issue.

Neither reboot or shutdown -r now work sensibly any more. Both rely on
systemd, which appears to be the root of most Ubuntu instabilities now,
reading the many reported systemd bugs.

Both the reboot + shutdown -r now commands should do what the mean.
Shutdown + Reboot now...

Not 150-250 seconds after requested, which appears to be some arbitrary
systemd timeout.

Please fix this problem + update this ticket with some workaround to get
an instant reboot, till fix is available.

Thanks.

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

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

Title:
  Wily/15.10 - systemd hangs reboot + shutdown for long periods of time

Status in systemd package in Ubuntu:
  New

Bug description:
  Yet another horrible bug related to systemd which delays shutdowns by
  minutes.

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1374759
  surfaces this problem + the bug I'm reporting here is a separate
  issue.

  Neither reboot or shutdown -r now work sensibly any more. Both rely on
  systemd, which appears to be the root of most Ubuntu instabilities
  now, reading the many reported systemd bugs.

  Both the reboot + shutdown -r now commands should do what the mean.
  Shutdown + Reboot now...

  Not 150-250 seconds after requested, which appears to be some
  arbitrary systemd timeout.

  Please fix this problem + update this ticket with some workaround to
  get an instant reboot, till fix is available.

  Thanks.

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

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

[Touch-packages] [Bug 1527166] Re: cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg: 'linux-headers..."

[Brian Murray]

The message and typo comes from python-apt.

** Also affects: python-apt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cron.daily/apt reports MarkUpgrade() called on a non-upgrable pkg:
  'linux-headers..."

Status in python-apt package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Today I received the following messages from /etc/cron.daily/apt on my
  14.04 LTS server

  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73'
  MarkUpgrade() called on a non-upgrable pkg: 
'linux-image-extra-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-image-3.13.0-73-generic'
  MarkUpgrade() called on a non-upgrable pkg: 'linux-headers-3.13.0-73-generic'

  
  First of all I suppose  the message should read  non-upgradable
  non-upgrable is possibly incorrect and should be corrected.

  Secondly I have no clue, what this message means so the error message
  should be revised to give more details.

  I think this as a minor bug but messages should always be correct,
  precise and possibly helpful.

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

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

[Touch-packages] [Bug 1506846] Re: [multimonitor] nested server surface positioning incorrect

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [multimonitor] nested server surface positioning incorrect

Status in Mir:
  Fix Released
Status in Unity System Compositor:
  New
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Flo and Mir 0.17.

  For multimonitor, it appears USC often positions the 2 nested server surfaces 
on the same screen, as if noth surfaces are positioned at (0,0) in the virtual 
desktop space - and not side-by-side. This screenshot may not be the clearest:
  https://chinstrap.canonical.com/~gerboland/mm2.jpg
  but I got it through moving the egltriangle surface to the right, and it 
appeared on the left!

  Steps to repro:
  1. SSH into device and do: sudo stop lightdm
  2. You'll want your backllight back, mirbacklight didn't work for me, so I 
called this as root:
  echo 255 > 
/sys/devices/platform/msm_fb.591617/leds/lcd-backlight/brightness
  3. Run
  sudo unity-system-compositor --debug-without-dm --disable-inactivity-policy 
true --enable-hardware-cursor=true --debug-active-session-name=Test
  sudo chmod 777 /tmp/mir_socket
  4. Start nested server
  mir_demo_server --host /tmp/mir_socket --display-config sidebyside 
--launch-client /usr/bin/mir_demo_client_egltriangle
  You should see the spinny triangle.
  5. Now plug in the slimport cable. The display will flicker while the 
external display is being incorporated.
  6. Use 3 fingers, move the triangle surface to the right.

  Expected result:
  It should appear on the external display

  Actual result:
  It pops in on the left of the internal display. See screenshot above.

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

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

[Touch-packages] [Bug 1499039] Re: compositing never stops when external monitor is connected

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

** Changed in: canonical-pocket-desktop
   Status: Fix Committed => Fix Released

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

Title:
  compositing never stops when external monitor is connected

Status in canonical-pocket-desktop:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.17 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Start the following with no external display:

  sudo mir_demo_server --arw-file --display-config=sidebyside --window-manager 
system-compositor --hwc-report log
  mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir 
--display-config=sidebyside

  After hotplugging an external display, the compositor loop never stops
  compositing as evidenced by the root server hwc logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1499039/+subscriptions

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

[Touch-packages] [Bug 1505114] Re: [regression] Can't move/resize windows any more using Alt+left/middle buttons

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Can't move/resize windows any more using Alt+left/middle
  buttons

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  [regression] Can't move/resize windows any more using Alt+left/middle
  buttons

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

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

[Touch-packages] [Bug 1519276] Re: Unit test failures in Display.* on Android

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Unit test failures in Display.* on Android

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  As seen in

  
https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid-armhf/4951/consoleFull
  
https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-vivid-armhf/4952/consoleFull

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

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

[Touch-packages] [Bug 1526505] Re: [regression] u8 desktop session fails to start

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

** Changed in: mir/0.18
   Status: Fix Committed => Fix Released

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

Title:
  [regression] u8 desktop session fails to start

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  Invalid

Bug description:
  u8 desktop session fails to start, due to confusion surrounding platform 
selection (between mesa and kms). 
  The root cause seems to be that the nested server (as non-root) cannot become 
drm-master.

  This is somewhat related to lp: #1526209 in that this bug has to do with mesa 
platform selection, which changed in rev3089. 
  lp: #1526209 was about the client crashing though, and this bug is about the 
nested server not being able to start, so they seem to be a bit different.

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

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

[Touch-packages] [Bug 1506707] Re: [regression] Mir server command line options are unpredictable/nondeterministic (--vt is sometimes not recognised)

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

** Changed in: mir/0.18
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Mir server command line options are
  unpredictable/nondeterministic (--vt is sometimes not recognised)

Status in Mir:
  Fix Released
Status in Mir 0.18 series:
  Fix Released
Status in mir package in Ubuntu:
  New

Bug description:
  Mir server platform command line options are unpredictable/non-
  deterministic.

  I keep thinking I'm imagining things. Sometimes --vt works and
  sometimes it doesn't (from a Gnome Terminal). Well both are true. Now
  I have two separate wily machines with the same packages. One fails
  but the other works:

  FAILING MACHINE:

  $ sudo mir_proving_server --vt 1
  [1444966151.185585] mirplatform: Found graphics driver: mesa-x11
  [1444966151.187021] mirplatform: Found graphics driver: mesa-kms
  Unknown command line options: --vt 1
  $ dpkg -l | grep mir-demos
  ii  mir-demos 
0.16.0+15.10.20150921.1-0ubuntu1   amd64Display server for 
Ubuntu - demonstration programs

  WORKING MACHINE:

  $ sudo mir_proving_server --vt 1
  [1444965570.300933] mirplatform: Found graphics driver: mesa-kms
  [1444965570.302119] mirplatform: Found graphics driver: mesa-x11
  [1444965570.304409] mircommon: Loading modules from: 
/usr/lib/x86_64-linux-gnu/mir/server-platform
  [1444965570.304465] mircommon: Loading module: 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.5
  [1444965570.304486] mircommon: Loading module: 
/usr/lib/x86_64-linux-gnu/mir/server-platform/server-mesa-x11.so.5
  [1444965570.305801] mirplatform: Found graphics driver: mesa-kms
  [1444965570.306531] mirplatform: Found graphics driver: mesa-x11
  [1444965570.306617] mirserver: Selected driver: mesa-kms (version 0.16.0)
  ...
  $ dpkg -l | grep mir-demos
  ii  mir-demos
0.16.0+15.10.20150921.1-0ubuntu1  amd64Display 
server for Ubuntu - demonstration programs

  It appears the unpredictability might be arising from which driver it
  finds on the filesystem first.

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

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

[Touch-packages] [Bug 1513901] Re: Segmentation fault on server shutdown with mesa-kms

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  Segmentation fault on server shutdown with mesa-kms

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  When the server shuts down we get a crash in the
  DefaultEmergencyCleanup destructor:

  #0  0x70bca81e in ?? ()
  #1  0x763e8c7d in std::_Function_base::~_Function_base 
(this=0x7054d0, 
  __in_chrg=) at /usr/include/c++/5/functional:1830
  #2  0x763edef6 in std::function::~function() (this=0x7054d0, 
  __in_chrg=) at /usr/include/c++/5/functional:1974
  #3  0x76419714 in mir::DefaultEmergencyCleanup::ListItem::~ListItem 
(this=0x7054d0, 
  __in_chrg=) at 
/storage/work/mir/src/server/default_emergency_cleanup.h:38
  #4  0x7641973a in 
std::default_delete::operator() (
  this=0x63e738, __ptr=0x7054d0) at /usr/include/c++/5/bits/unique_ptr.h:76
  #5  0x76419553 in 
std::unique_ptr::~unique_ptr 
(this=0x63e738, __in_chrg=)
  at /usr/include/c++/5/bits/unique_ptr.h:236
  #6  0x76419708 in mir::DefaultEmergencyCleanup::ListItem::~ListItem 
(this=0x63e718, 
  __in_chrg=) at 
/storage/work/mir/src/server/default_emergency_cleanup.h:38
  #7  0x764198d8 in 
mir::DefaultEmergencyCleanup::~DefaultEmergencyCleanup (this=0x63e710, 
  __in_chrg=) at 
/storage/work/mir/src/server/default_emergency_cleanup.h:31
  #8  0x76404753 in 
__gnu_cxx::new_allocator::destroy
 (this=0x63e710, __p=0x63e710) at /usr/include/c++/5/ext/new_allocator.h:124
  #9  0x76404572 in 
std::allocator_traits::_S_destroy (__a=..., __p=0x63e710) at 
/usr/include/c++/5/bits/alloc_traits.h:285
  #10 0x76404245 in 
std::allocator_traits::destroy (__a=..., __p=0x63e710) at 
/usr/include/c++/5/bits/alloc_traits.h:414
  #11 0x76403417 in 
std::_Sp_counted_ptr_inplace::_M_dispose (this=0x63e700)
  at /usr/include/c++/5/bits/shared_ptr_base.h:531
  #12 0x763e92e0 in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release (this=0x63e700)
  at /usr/include/c++/5/bits/shared_ptr_base.h:150
  #13 0x763e8f83 in 
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count (
  this=0x7fffe228, __in_chrg=) at 
/usr/include/c++/5/bits/shared_ptr_base.h:659
  #14 0x763e8dfc in std::__shared_ptr::~__shared_ptr (this=0x7fffe220, 
__in_chrg=) at /usr/include/c++/5/bits/shared_ptr_base.h:925
  #15 0x763e8e18 in std::shared_ptr::~shared_ptr 
(this=0x7fffe220, 
  __in_chrg=) at /usr/include/c++/5/bits/shared_ptr.h:93
  #16 0x7641a6bc in mir::Server::run (this=0x7fffe290)
  at /storage/work/mir/src/server/server.cpp:382
  #17 0x76ad2993 in main (argc=1, argv=0x7fffe478)
  at /storage/work/mir/examples/server_example.cpp:110
  #18 0x0040106a in main (argc=1, argv=0x7fffe478)
  at /storage/work/mir/examples/mir_demo_server_loader.cpp:40

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

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

[Touch-packages] [Bug 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY

[Kevin DuBois]

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  mir_connection_get_egl_pixel_format() crashes if libEGL is loaded
  RTLD_LAZY

Status in Mir:
  Fix Released
Status in Mir 0.17 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  mir_connection_get_egl_pixel_format() crashes on Android (at least)
  when used in QtUbuntu. There might be some specific conditions
  triggering the issue there because I haven't been able to reproduce it
  in a standalone test [1] trying to follow the same initialisation
  process.

  This is strange because if I directly call
  "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, )"
  it works perfectly fine.

  Here's a QtUbuntu branch [2] using the function.

  [1] 
http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c
  [2] 
lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format

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

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

[Touch-packages] [Bug 1523407] Re: Playlist support in vivid+overlay and Xenial is different/non compatible

[Timo Jyrinki]

qtmultimedia-opensource-src (5.5.1-1ubuntu2) xenial; urgency=medium

  [ Timo Jyrinki ]
  * More patches from upstream to the playlist:
- debian/patches/Change-the-way-a-playlist-is-bound-to-a-media-object.patch
  (replaces earlier abandoned Sync-the-state... patch)
- debian/patches/Added-addItems-to-QML-Playlist-for-batch-adding-of-t.patch
- debian/patches/Added-insertItems-and-removeItems-to-QML-Playlist.patch
- debian/patches/Add-moveItem-from-to-to-QMediaPlaylist.patch

  [ Jim Hodapp ]
  * Related changes for compatibility reasons:
- debian/patches/backport_adjustments.patch

 -- Timo Jyrinki   Tue, 22 Dec 2015 13:57:22
+

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

Title:
  Playlist support in vivid+overlay and Xenial is different/non
  compatible

Status in Canonical System Image:
  Fix Committed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  qtmultimedia-opensource-
  src-5.4.1/debian/patches/add_qdeclarative_playlist.patch says

  +qmlRegisterType(uri, 5, 4, "Playlist");

  while qtmultimedia-opensource-src-5.5.1/debian/patches/Added-new-
  playlist-QML-type.patch (as per silo 12) says

  +qmlRegisterType(uri, 5, 6, "Playlist");

  This is not a good idea, we should keep the imports to the same level
  as we decide to support them, even if the support was not official
  doing this makes it harder to have a codebase that works fine in both
  vivid+overlay and xenial.

  Also the xenial patch seems to be missing some things like
  QDeclarativePlaylist::moveItem

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

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

[Touch-packages] [Bug 1511095] Re: unity-system-compositor crash, no interaction on windowed mode

[Kevin DuBois]

** Changed in: canonical-pocket-desktop
   Status: Fix Committed => Fix Released

** Changed in: mir
   Status: Fix Committed => Fix Released

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

Title:
  unity-system-compositor crash, no interaction on windowed mode

Status in canonical-pocket-desktop:
  Fix Released
Status in Mir:
  Fix Released
Status in Mir 0.17 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to 
say)
  but I regularly see N7 reboot with me having interacted with it

  I will have usually connected the BT mouse and have maybe u-s-s open as well 
as dash (i think i've even seen it do so after just being rebooted with me not 
touching it before the next reboot).
  the screen will be on or off from being idel, no interaction per se and the 
device will suddenly display the "spinner" screen which is actually ubuntu 
dot-dot-dots

  I have seen it enough to confirm there are no crash files
  generated/associated with it

  lastly, i have seen this mostly while i have added silo21 (unity8
  improvements) on top of the latest pd image.

  attached is a syslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+subscriptions

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