[Touch-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth

[Simon Fels]

What happens here is now pretty clear:

The car gets disconnected but the rfcomm/sco channels aren't. Due to
that the audio card is still kept in PulseAudio which in turn lets the
UI think it can still use it.

However what is not clear yet is why this happens. The attached syslog
sadly doesn't show the point where the device disconnection happen. This
could be a problem in bluetoothd itself failing to handle a rfcomm/sco
channel disconnection or the kernel never sending the right event for
this.

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

** Changed in: telephony-service (Ubuntu)
   Status: New => Invalid

** Tags added: bluetooth

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

Title:
  After disconnnecting from car bluetooth, audio is still routed to
  bluetooth

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  MX4 r96

  This has been happening fro a few weeks
  Phone automatically connects to the car, you don't have to make or receive a 
call
  Leave the car and disconnect
  Place a call
  The audio starts out using the phone as expected, after a few seconds the 
audio switches to bluetooth
  You can manually change the audio in the UI
  This happens until you reboot

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

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

[Touch-packages] [Bug 1494599] Re: package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig'

[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 qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1494599

Title:
  package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/x86_64
  -linux-gnu/qt4/bin/qtconfig' to '/usr/lib/x86_64-linux-
  gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file or stream

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Doing dist-upgrade on fresh ubuntu-mate15.04, get this error

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  Date: Fri Sep 11 00:54:33 2015
  DuplicateSignature: 
package:qt4-qtconfig:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1:cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: qt4-x11
  Title: package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1494599/+subscriptions

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

[Touch-packages] [Bug 1470784] Re: In the album turn to the phone to landscape mode then turn back , there is a blank page

[Relly]

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

Title:
  In the album turn to the phone to landscape mode then turn back ,there
  is a blank page

Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  current build number: 55
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-07-02 04:38:03
  version version: 55
  version ubuntu: 20150702
  version device: 20150529-8e13c5f
  version custom: 20150528-722-29-15-vivid

  Steps：
1.create a album with some pictures 
2.make sure the cover is the album is original black(if not ,enter into the 
album ,slide to the right until the black cover come out)
3.rotate your phone to landscape mode
4.press the album and look through it ,then slide left to the cover , press 
back key 
5.rotate your phone back

  Expectation:
there won't be any blank page appears after step 5

  Actual result:
there  is a blank page after step 5

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

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

[Touch-packages] [Bug 1494599] [NEW] package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig

[Alex Thomas]

Public bug reported:

Doing dist-upgrade on fresh ubuntu-mate15.04, get this error

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
Date: Fri Sep 11 00:54:33 2015
DuplicateSignature: 
package:qt4-qtconfig:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1:cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
InstallationDate: Installed on 2015-09-11 (0 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: qt4-x11
Title: package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package vivid

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

Title:
  package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/x86_64
  -linux-gnu/qt4/bin/qtconfig' to '/usr/lib/x86_64-linux-
  gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file or stream

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Doing dist-upgrade on fresh ubuntu-mate15.04, get this error

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  Date: Fri Sep 11 00:54:33 2015
  DuplicateSignature: 
package:qt4-qtconfig:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1:cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: qt4-x11
  Title: package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1494599/+subscriptions

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

[Touch-packages] [Bug 1494322] Re: Address book service log contains several warning messages related with vcard parse

[Timo Jyrinki]

https://codereview.qt-project.org/#/c/88707/

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

Title:
  Address book service log contains several warning messages related
  with vcard parse

Status in address-book-service package in Ubuntu:
  New
Status in qtpim-opensource-src package in Ubuntu:
  New

Bug description:
  Several messages of : 'Variant value is a QStringList but the
  property's value type is neither CompoundType or ListType' into the
  address-book-service log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1494322/+subscriptions

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

[Touch-packages] [Bug 1321958] Re: resize2fs does not start to actually grow an ext4

[TJ]

Increasing importance due to possible denial-of-service during a resize
of large 'complex' file-systems. In this case both reports using DM RAID
6.

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

** Changed in: e2fsprogs (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  resize2fs does not start to actually grow an ext4

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 14.04 LTS, all proposed updates done
  Kernel: 3.13.0-24-generic, 
  Package: e2fsprogs 1.42.9-3ubuntu1, 
  System: Haswell i7, 32GB RAM, LSI SAS 9207-8i HBA and LSI SAS 9211-8i HBA

  I tried to increse the size of an ext4 filesystem. Old size 20TB,
  wanted new size 28TB. I tried offline resize with "resize2fs -fp
  /dev/md2" and later online resize using "resize2fs -f /dev/md2". In
  both cases, after giving the command a rezise2fs process is created
  that uses nearly 100% cpu according to top, but it does not perform
  any actual resize. It only prints its version and date and then it
  does not finish for hours. I had it running for more than a day
  without finishing:

  root@marvin:~# resize2fs -f /dev/md2
  resize2fs 1.42.9 (4-Feb-2014)

  There is never more terminal output than that. It looks to me that
  resize2fs hangs in a endless calcualtion or loop or something similar.

  Some more info about the filesystem:

  root@marvin:~# tune2fs -l /dev/md2
  tune2fs 1.42.9 (4-Feb-2014)
  Filesystem volume name:   data
  Last mounted on:  /media/data01
  Filesystem UUID:  e3845e15-0336-47ae-8aec-df75acb217c5
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file 
uninit_bg dir_nlink extra_isize
  Filesystem flags: signed_directory_hash 
  Default mount options:user_xattr acl
  Filesystem state: clean
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  305225728
  Block count:  4883606400
  Reserved block count: 0
  Free blocks:  22919919
  Free inodes:  302894731
  First block:  0
  Block size:   4096
  Fragment size:4096
  Group descriptor size:64
  Reserved GDT blocks:  1024
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 2048
  Inode blocks per group:   128
  RAID stride:  128
  RAID stripe width:640
  Flex block group size:16
  Filesystem created:   Fri Sep 20 19:45:01 2013
  Last mount time:  Tue May 20 02:14:37 2014
  Last write time:  Tue May 20 02:14:37 2014
  Mount count:  3
  Maximum mount count:  -1
  Last checked: Tue May 20 01:34:05 2014
  Check interval:   0 ()
  Lifetime writes:  34 TB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  569ec5fc-4d5e-4639-bef3-42cde5fbe948
  Journal backup:   inode blocks

  
  I did also run an filesystem check:

  root@marvin:~# e2fsck -vfp /dev/md2
  
   2330890 inodes used (0.76%, out of 305225728)
 14882 non-contiguous files (0.6%)
   949 non-contiguous directories (0.0%)
   # of inodes with ind/dind/tind blocks: 0/0/0
   Extent depth histogram: 2317190/13041/651
4868171016 blocks used (99.68%, out of 4883606400)
 0 bad blocks
  1654 large files

   2273776 regular files
 57105 directories
 0 character device files
 0 block device files
 0 fifos
 0 links
 0 symbolic links (0 fast symbolic links)
 0 sockets
  
   2330881 files

  The underlying device is an mdadm RAID6 that was grown from 7 to 9
  disks. The growing finished without problems before I tried to
  increase the ext4 size.

  Solution:
  The solution for me was to downgrade to e2fsprogs 1.42.8. Then the resize did 
work and finished within a few minutes. I got the hint to do so in a forum from 
an user, who had the same problem and solved it with the older version. I have 
not tested the new 1.42.10.

  I think this must be 

[Touch-packages] [Bug 1472755] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted double-linked list: ADDR ***

[Michał Karnicki]

I believe I may have found the source of the problem. When the scope is 
aggregated, the author assumed they can access results[0], which may not be 
true if:
1) the user is signed in
2) but has no messages whatsoever

That'd mean the scope would crash for all users, who have set up
Telegram account, but not really used it.

Michi, if you have time, perhaps you could verify my finding. In the
mean time, I'm rewriting the scope source as the backing database schema
has changed (after we moved to making use of TelegramQML plugin).

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

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in
  `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted
  double-linked list: ADDR ***

Status in Canonical System Image:
  Confirmed
Status in libqtelegram package in Ubuntu:
  Triaged
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scope-mediascanner.  This problem was most recently
  seen with version 1.7.16, the problem page at
  https://errors.ubuntu.com/problem/21d9e7ddf91a26b21abfb2758315ad41fcfd3fa9
  contains more details.

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

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

[Touch-packages] [Bug 748539] Re: Multi-monitor - Panel and launcher visible on top of multimonitor non-focused fullscreen apps

[Bent Haase]

I can relate to #38, having exactly the same setup with the same hassle. Why 
not simply add the functionality to set the Unity top bar  in the screen 
settings. There is an option for the Launcher Position (either Screen A or B or 
both) why not the same for Unity?
I hope this will be fixed with Unity 8.

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

Title:
  Multi-monitor - Panel and launcher visible on top of multimonitor non-
  focused fullscreen apps

Status in Ayatana Design:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 6.0 series:
  Won't Fix
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: unity

  See the attached screenshot.

  When an app is fullscreen (fullscreen, not maximized) on a monitor,
  but another program is focused on the other monitor, then the unity
  panel is displayed at when it shoudn't be.

  I appreciate this probably isn't a priority, but for a future release
  it would be good seeing as it's the little details that matter.

  --
  Desired solution:

  - When an app is fullscreen (fullscreen, not maximized) on a monitor,
  but another program is focused on the other monitor, the unity menu
  bar should not be displayed on the monitor that is displaying the
  fullscreen app.

  - When fixing this bug, also look at bug #1065425

  WORKAROUND FOR THIS BUG:
  Turn "Always On Top" on via right-clicking the titlebar of your window, 
before making it go fullscreen.
  This will prevent the Unity panel from rendering on top of this 
fullscreen-window, when using the other screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/748539/+subscriptions

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

[Touch-packages] [Bug 1410190] Re: /usr/bin/ubuntu-location-serviced:*** Error in `/usr/bin/ubuntu-location-serviced': malloc(): memory corruption (fast): ADDR ***

[Jean-Baptiste Lallement]

Adding a CSI task, it happens frequently on production phones.

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

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

** Changed in: location-service (Ubuntu)
   Importance: Medium => High

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

Title:
  /usr/bin/ubuntu-location-serviced:*** Error in `/usr/bin/ubuntu-
  location-serviced': malloc(): memory corruption (fast): ADDR ***

Status in Canonical System Image:
  Confirmed
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding location-service.  This problem was most recently seen with
  version 2.1+15.04.20150106~rtm-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/284a0959d15e8ca7d2d39ec2dbb85d403132b356
  contains more details.

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS

[Alexandros Frantzis]

My take on the backtrace is that  the set_screen_power_mode request
hangs somewhere in Mir, and since it holds the lock, it blocks both
dimmer_alarm_notification and keep_display_on_temporarily (which is a
result of user input). If my assumption is correct, we need to find why
and where in Mir we block, so it would be great if we had debug symbols
for mir (and libstdc++ and libc) for the USC backtrace.

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

Title:
  Shell not responsive after an incoming SMS

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

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

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

[Touch-packages] [Bug 1488425] Re: [MIR] ubuntu-download-manager

[Jamie Strandboge]

I acknowledge the bad user experience but AIUI, Ubuntu Personal is not
the priority for 15.10 and I don't think that webbrowser-app is used as
the default browser any where else. I'm not saying that this won't
happen, I'm just trying to figure out priorities.

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

Title:
  [MIR] ubuntu-download-manager

Status in ubuntu-download-manager package in Ubuntu:
  Incomplete

Bug description:
  webbrowser-app (in main) currently has a non-explicit runtime dependency on 
ubuntu-download-manager, which is in universe.
  This has been working until now because the desktop version of the app 
doesn’t make use of the QML API for the download manager, only the version for 
touch devices does (and ubuntu-download-manager is part of the touch seed).
  With convergence in mind, the desktop version needs to start using that QML 
API, so the runtime dependency needs to be made explicit. Hence the need for 
ubuntu-download-manager to be included in main.
  It is likely that other applications will have the same kind of requirements 
in the near future too.

  ubuntu-download-manager is actively being developed and maintained,
  upstream tracks their bugs at
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/.

  All its build and runtime dependencies are already in main.

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

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

[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

Thank you for your reply Raymond, i am uncertain what you are asking me
do.

14.04, 14.10 and 15.04 sound settings output look like this:
https://www.dropbox.com/s/h38d1w4n16...%3A50.png?dl=0
and the associated alsa mixer controls e.g. speaker are missing

this is what 12.04 looked like and worked:
https://www.dropbox.com/s/0k376713gb...%3A05.png?dl=0

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1494770] Re: Scrolling inertia for webapps died on Meizu MX4 (stable channel)

[Oliver Grawert]

note that there is no real reciepe to reproduce it, it can take days til
it shows up, at least for me ... probably the OP has a way to reproduce
it more reliably ?

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

Title:
  Scrolling inertia for webapps died on Meizu MX4 (stable channel)

Status in Canonical System Image:
  New
Status in The Webapps-core project:
  New
Status in webapps-sprint:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Scrolling inertia for webapps died on Meizu MX4 (stable channel)

  testing with g+ and omgubuntu, no scrolling inertia. i can scroll but
  the context sticks to my finger.. 0 inertia

  if you have any idea how i can debug this, i'll be happy to do so

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

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

[Touch-packages] [Bug 1494770] Re: Scrolling inertia for webapps died on Meizu MX4 (stable channel)

[Oliver Grawert]

i see it on all webapps occasionally, even in the browser ... running
rc-proposed on MX4

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

Title:
  Scrolling inertia for webapps died on Meizu MX4 (stable channel)

Status in Canonical System Image:
  New
Status in The Webapps-core project:
  New
Status in webapps-sprint:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Scrolling inertia for webapps died on Meizu MX4 (stable channel)

  testing with g+ and omgubuntu, no scrolling inertia. i can scroll but
  the context sticks to my finger.. 0 inertia

  if you have any idea how i can debug this, i'll be happy to do so

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS or call notification

[Alexandros Frantzis]

> Note: the slide gesture doesn't always slide in the right direction, not sure 
> why, but in any case you can see some effect on 
screen

Increasing the first sleep in the script (sleep 2) to something longer
(e.g. sleep 3) seems to fix this, so probably it's just a matter of
trying to touch the screen too soon.

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also triggering the issue

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

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

[Touch-packages] [Bug 1438870] Re: Lock screen doesn't emit ActiveChanged signal

[Marc Deslauriers]

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

** Also affects: unity-settings-daemon (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: unity-settings-daemon (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: unity-settings-daemon (Ubuntu Trusty)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  Lock screen doesn't emit ActiveChanged signal

Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Released
Status in unity-settings-daemon source package in Trusty:
  Confirmed

Bug description:
  tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is
  locked/unlocked

  Long version:

  unity-settings-daemon's automount plugin has code to detect whether
  the screen is locked or not before automatically mounting a volume.
  This prevents someone from inserting a USB thumb drive when the screen
  is locked and exploiting a possible nautilus thumbnailer
  vulnerability. (See bug #714958 for original implementation details.)

  In Ubuntu 14.04, this code no longer works. Inserting a USB thumb
  drive while the screen is locked results in a Nautilus window opening
  underneath the lock screen, and the contents of the USB thumb drive
  being read.

  Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no
  longer emits the org.gnome.ScreenSaver ActiveChanged signal when the
  screen gets locked or unlocked.

  To test:

  1- in terminal, type:
  dbus-monitor 
"type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver'"
  2- Lock the screen
  3- Unlock the screen
  4- Notice that no signal was received

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150330-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Mar 31 15:15:48 2015
  InstallationDate: Installed on 2013-11-26 (489 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago)

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

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

[Touch-packages] [Bug 1318360] Re: Poor microphone quality (mako)

[Jamie Strandboge]

Actually, I went through the procedure in https://lists.launchpad.net
/ubuntu-phone/msg08514.html even though it said I had all the right
versions already. After flashing, I called someone and the volume was
ok. I was going to play with alsamixer, but didn't end up having to.

$ system-image-cli -i
current build number: 109
device name: mako
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-09-11 12:10:05
version version: 109
version ubuntu: 20150911
version device: 20150911
version custom: mako-1.1

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

Title:
  Poor microphone quality (mako)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

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

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

[Touch-packages] [Bug 1484932] Re: ipv6 dhcp client never started.

[Marcelo Zacarias da Silva]

Tried others distros (basead on debian testing) with newer network-manager 
(1.0.6) and the problem persists.

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

Title:
  ipv6 dhcp client never started.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm in a ipv6 network that sets ip number with dhcpv6 and not using
  the stateless protocol.

  but using ubuntu 15.04 there is never any dhclient started for ipv6
  and no way to change any configuration that I can find to start it.

  if I attach the cable and then manually start dhclient with "dhclient
  -6 -i eth3_109" I do get a ipv6 address and things works as intended.

  There has to be some way to star the dhclient software from network
  manager but I can't find it.

  There should be two dhclients started per network device one for ipv4
  and one for ipv6 only one is started for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  Uname: Linux 4.1.5-040105-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 14 14:32:06 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-04-09 (126 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  IpRoute:
   default via 10.10.1.254 dev eth3  proto static  metric 1024 
   10.10.1.0/24 dev eth3  proto kernel  scope link  src 10.10.1.156 
   10.10.6.0/24 dev eth3_109  proto kernel  scope link  src 10.10.6.14 
   169.254.0.0/16 dev eth3  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1484932/+subscriptions

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

[Touch-packages] [Bug 1494820] Re: /usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration

[kevin gunn]

this is #3 crash on bq rc-proposed channel in the last month

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

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

Title:
  
/usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration

Status in unity8 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1494770] Re: Scrolling inertia for webapps died on Meizu MX4 (stable channel)

[David Barth]

Trying on my MX4 with image 15.04/r4, I can't see that at first sight.
Tested with Google+ (the canonical app), and Facebook. I couldn't login
with ogra's G+ but the different UA seemed to introduce a different feel
to the public home screen. So that may be due to css code that thinks
it's on Chrome/Android.

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

Title:
  Scrolling inertia for webapps died on Meizu MX4 (stable channel)

Status in Canonical System Image:
  New
Status in The Webapps-core project:
  New
Status in webapps-sprint:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Scrolling inertia for webapps died on Meizu MX4 (stable channel)

  testing with g+ and omgubuntu, no scrolling inertia. i can scroll but
  the context sticks to my finger.. 0 inertia

  if you have any idea how i can debug this, i'll be happy to do so

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

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

[Touch-packages] [Bug 1494815] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-source-registry crashed with SIGABRT in
  g_assertion_message()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  happened in 15.10 upon login - please let me know if you need more
  info

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: evolution-data-server 3.16.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-10.10-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Fri Sep 11 10:44:58 2015
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2012-09-16 (1089 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_source_get_extension () from /usr/lib/libedataserver-1.2.so.20
   ?? () from /usr/lib/libebackend-1.2.so.10
  Title: evolution-source-registry crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom debian-tor dip libvirtd lpadmin plugdev 
sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1494815/+subscriptions

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

[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)

[Jamie Strandboge]

This appears to be fixed with the new bluetooth stack:
$ system-image-cli -i
current build number: 109
device name: mako
channel: ubuntu-touch/rc-proposed/bq-aquaris.en

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

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS or call notification

[kevin gunn]

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

** Changed in: mir
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

** Changed in: mir
   Importance: Undecided => Critical

** Changed in: mir
   Status: New => In Progress

** Changed in: unity-system-compositor (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: unity-system-compositor (Ubuntu)
 Assignee: (unassigned) => Alexandros Frantzis (afrantzis)

** Changed in: unity-system-compositor (Ubuntu)
   Importance: Undecided => Critical

** No longer affects: qtmir (Ubuntu)

** No longer affects: unity8 (Ubuntu)

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  In Progress

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also triggering the issue

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

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

[Touch-packages] [Bug 1494820] [NEW] /usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding unity8.  This problem was most recently seen with version
8.12+15.04.20150814-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/003f0e8f98fef2cbbb6f8c3800fd04241ededbed
contains more details.

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


** Tags: vivid

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

Title:
  
/usr/bin/unity8-dash:6:fprintf:qt_message_print:qt_message:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration

Status in unity8 package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS

[Alexandros Frantzis]

** Attachment added: "bug_1491566.sh"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4461418/+files/bug_1491566.sh

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also triggering the issue

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS

[Alexandros Frantzis]

I have been continuing my efforts to reproduce, but without any success
so far. I have created a script to automate the process which I am
sharing here in the hope that someone else will have more success with
it.

The script either uses simulated sms messages  (powerd receives the SMS
event and tells USC to turn the screen on) or talks directly to USC to
turn the screen on.  Just uncomment the line for the method you prefer
(and comment the other). For the simulated message approach to work you
need to setup the system properly, read:
https://wiki.ubuntu.com/Touch/Testing/PhoneAndMessagingSimulation .

The scripts include some reasonable sleeps to let things settle.
Increase them or decrease them to simulate different scenarios better.

I invoke the script with:

while true; do sh bug_1491566.sh; done

Note: the slide gesture doesn't always slide in the right direction, not
sure why, but in any case you can see some effect on screen

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also triggering the issue

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

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

[Touch-packages] [Bug 1447654] Re: installing policykit-1 hangs under systemd

[Pearj]

I'm doing the same thing as comment #18 - and getting the same errors.
Will try the workaround..

I know it's not productive, but I've spent days trying get this mini
build going - before that I spent 2 months trying to get a live build
going.. I've used Ubuntu for nearly 10 years and never had problems like
this. Most of my issues related to systemd, and keeping unity related
packages out.. Those two things turned a successful OS into a headache.
I understand a desktop for multiple interfaces - but give people options
that work, and don't release things without more through testing...
Please.

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

Title:
  installing policykit-1 hangs under systemd

Status in policykit-1 package in Ubuntu:
  Confirmed
Status in policykit-1 source package in Vivid:
  Confirmed

Bug description:
  I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 =
  6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting
  errors installing packages (such as lubuntu-core).

  Last few lines from apt-get:
  Processing triggers for systemd (219-7ubuntu3) ...
  Error getting authority: Error initializing authority: Error calling 
StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached 
(g-io-error-quark, 24)
  Failed to execute operation: Connection timed out
  dpkg: error processing package systemd (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ...
  Processing triggers for shared-mime-info (1.3-1) ...
  Processing triggers for mime-support (3.58ubuntu1) ...
  Processing triggers for udev (219-7ubuntu3) ...
  Processing triggers for dbus (1.8.12-1ubuntu5) ...
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I've done a second install using the server iso and lubuntu-core
  installs fine on that. The only thing different was my install media.

  SRU INFORMATION
  ===
  Test case:
  - Boot a minimal VM and purge "apport policykit-1", or do the above netboot 
installation.
  - sudo apt-get install policykit-1 apport
  - The above hangs on the systemd triggers and eventually fails in vivid 
final. It should succeed fine with this update.

  Regression potential: Very low: polkitd does not keep state, so one
  can restart it fine. The postinst shell modification is simple and
  obvious.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+subscriptions

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS

[Alexandros Frantzis]

** Attachment added: "slide_gesture.py"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4461417/+files/slide_gesture.py

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also triggering the issue

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

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

[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)

[Jamie Strandboge]

@Simon: yes, I was pleasantly surprised too. I had always heard that it
was a hardware issue so when I read that rc-proposed had the new
bluetooth kernel stack I thought maybe they worked around the issue in
some manner in the kernel. Initially after booting into r109 I used the
indicator and it all appeared to work properly (like on arale).
Satisfied, I went and looked at bug #1318360 again (unrelated to this
but...) then I updated the radio firmware as described in
https://lists.launchpad.net/ubuntu-phone/msg08514.html. Then I saw your
'really' comment and decided to try this bug for real in my car. I
enabled bluetooth via the indicator, it paired with the car. I played a
song with the music-app via bluetooth. I disabled bluetooth via the
indicator. It unpaired with the car. I enabled bluetooth via the
indicator and it paired and I played a song with the music-app via
bluetooth. All without rebooting.

I mention the updated radio firmware only because while I don't think it
had anything to do with fixing this bug, because I didn't test pairing
with the car prior to updating it, I'm not 100% sure it isn't needed.

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

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS or call notification

[Alexandros Frantzis]

Note: For the slide gesture to work you need the python3-evdev package.

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also triggering the issue

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS or call notification

[Pat McGowan]

** Summary changed:

- Shell not responsive after an incoming SMS
+ Shell not responsive after an incoming SMS or call notification

** Description changed:

  RC proposed MX4 r100
  
  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed
+ 
+ Adding incoming calls as also triggering the issue

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also triggering the issue

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

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

[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)

[Simon Fels]

@Jamie: really?

Will double check that on monday.

** Tags added: bluetooth bluez5

** Tags removed: bluez5
** Tags added: after-bluez5

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

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1484932] Re: ipv6 dhcp client never started.

[Launchpad Bug Tracker]

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

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

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

Title:
  ipv6 dhcp client never started.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm in a ipv6 network that sets ip number with dhcpv6 and not using
  the stateless protocol.

  but using ubuntu 15.04 there is never any dhclient started for ipv6
  and no way to change any configuration that I can find to start it.

  if I attach the cable and then manually start dhclient with "dhclient
  -6 -i eth3_109" I do get a ipv6 address and things works as intended.

  There has to be some way to star the dhclient software from network
  manager but I can't find it.

  There should be two dhclients started per network device one for ipv4
  and one for ipv6 only one is started for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  Uname: Linux 4.1.5-040105-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 14 14:32:06 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-04-09 (126 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  IpRoute:
   default via 10.10.1.254 dev eth3  proto static  metric 1024 
   10.10.1.0/24 dev eth3  proto kernel  scope link  src 10.10.1.156 
   10.10.6.0/24 dev eth3_109  proto kernel  scope link  src 10.10.6.14 
   169.254.0.0/16 dev eth3  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  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/1484932/+subscriptions

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

[Touch-packages] [Bug 893210] Re: [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

[Neil]

3rd time lucky
12.04
https://www.dropbox.com/s/0k376713gb0ptod/Screenshot%20from%202014-12-02%2013%3A34%3A05.png?dl=0

14.04
https://www.dropbox.com/s/h38d1w4n16etdyh/Screenshot%20from%202014-12-02%2013%3A40%3A50.png?dl=0

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

Title:
  [Dell OptiPlex GX620 - AD1981b, playback] No sound at all

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  fresh install of ubuntu studio and updates but internal speakers do
  not play. dell optiplex gx620 love ya

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'ICH7'/'Intel ICH7 with AD1981B at irq 23'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 28
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Device'/'C-Media Electronics Inc. USB Multimedia Audio Device at 
usb-:00:1d.7-4.1.4,'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0105'
 Controls  : 13
 Simple ctrls  : 6
  Date: Mon Nov 21 11:51:25 2011
  InstallationMedia: Ubuntu-Studio 11.10 "Oneiric Ocelot" - Release i386 
(20111011.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:ICH7 failed
  Symptom_Card: CM108 Audio Controller - USB Multimedia Audio Device
  Symptom_Type: No sound at all
  Title: [ICH4 - Intel ICH7, playback] No sound at all
  UpgradeStatus: Upgraded to oneiric on 2011-11-12 (8 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0F8101
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0F8101:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)

[Sam Bull]

"All without rebooting."

You need to reboot to reproduce the issue. Disable bluetooth, then
reboot. Then enable bluetooth and see if it works. The issue only occurs
(for me atleast) when booting the phone with bluetooth already disabled.

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

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1472755] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted double-linked list: ADDR ***

[Timo Jyrinki]

I definitely did have
https://errors.ubuntu.com/oops/0bb39a78-1c08-11e5-9c34-fa163e78b027 when
I already had Telegram discussions.

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in
  `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted
  double-linked list: ADDR ***

Status in Canonical System Image:
  Confirmed
Status in libqtelegram package in Ubuntu:
  Triaged
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scope-mediascanner.  This problem was most recently
  seen with version 1.7.16, the problem page at
  https://errors.ubuntu.com/problem/21d9e7ddf91a26b21abfb2758315ad41fcfd3fa9
  contains more details.

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

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

[Touch-packages] [Bug 1491542] Re: libunity ftbfs in wily

[Will Cooke]

** Changed in: libunity (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  libunity ftbfs in wily

Status in libunity:
  New
Status in libunity package in Ubuntu:
  New

Bug description:
  libunity seems to no longer be buildable in wily.  This is a problem
  because it must be rebuilt for Python 3.5, but it is failing for
  unrelated reasons.  Here's an excerpt of the build log from a local
  build using the current wily source package:

  /usr/bin/glib-compile-resources --sourcedir . --target=unity-tool-res.c 
--generate-source unity-tool-res.gresource.xml
  /usr/bin/valac -C --vapidir ../vapi --vapidir=../protocol --vapidir=../src 
--pkg config --pkg gtk+-3.0 --pkg gmodule-2.0 --pkg unity-internal --pkg 
unity-protocol --pkg glib-2.0 --pkg gmodule-2.0 --pkg gobject-2.0 --pkg gio-2.0 
--pkg gio-unix-2.0 --pkg dee-1.0 --pkg Dbusmenu-0.4  unity-tool.vala 
unity-tool-dbus-util.vala unity-tool-ui.vala preview-renderer.vala 
music-track-model-renderer.vala
  unity-tool-ui.vala:846.13-846.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore uimodel = null;
  ^
  unity-tool-ui.vala:847.13-847.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore ui_filter_model = null;
  ^
  unity-tool-ui.vala:848.13-848.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore scope_list_model = null;
  ^
  unity-tool-ui.vala:849.13-849.21: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  private ListStore ui_cat_model = null;
  ^
  unity-tool-ui.vala:43.62-43.70: error: `ListStore' is an ambiguous reference 
between `GLib.ListStore' and `Gtk.ListStore'
  uimodel = builder.get_object("results_model") as ListStore;
   ^
  unity-tool-ui.vala:44.70-44.78: error: `ListStore' is an ambiguous reference 
between `GLib.ListStore' and `Gtk.ListStore'
  ui_filter_model = builder.get_object("filters_model") as 
ListStore;
   ^
  unity-tool-ui.vala:45.70-45.78: error: `ListStore' is an ambiguous reference 
between `GLib.ListStore' and `Gtk.ListStore'
  ui_cat_model = builder.get_object("categories_model") as 
ListStore;
   ^
  unity-tool-ui.vala:158.74-158.82: error: `ListStore' is an ambiguous 
reference between `GLib.ListStore' and `Gtk.ListStore'
  scope_list_model = builder.get_object("scope_list_model") as 
ListStore;
   
^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  music-track-model-renderer.vala:30.12-30.20: error: `ListStore' is an 
ambiguous reference between `GLib.ListStore' and `Gtk.ListStore'
  public ListStore track_view_model { get; construct; }
 ^
  Compilation failed: 12 error(s), 0 warning(s)

  Seems like the same problem in all cases, and I'm not sure which
  ListStore is intended.  Full buildlog is available in the Python 3.5
  -as-default PPA:

  https://launchpadlibrarian.net/216183170/buildlog_ubuntu-wily-
  amd64.libunity_7.1.4%2B14.10.20140808-0ubuntu1_BUILDING.txt.gz

  This is blocking several other critical packages which need updating
  for Python 3.5.

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

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

[Touch-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled

[Didier 'Ptitjes']

@morphis Yep, I confirm the problem as described there by Marcel
Holtmann is correct. I tried his test fix and it does indeed make the
controller work. I was able to pair and use my keyboard and track-pad
without problem.

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

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  I get no Bluetooth icon in the status bar, and in System Settings >
  Bluetooth, everything is greyed out (i.e., can't turn it on).

  
  $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; 
lsmod | grep bluetooth; hciconfig -a; uname -a

  Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
  Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
  [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
  [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
  [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [ 34.866186] Bluetooth: Core ver 2.20
  [ 34.866205] Bluetooth: HCI device and connection manager initialized
  [ 34.866751] Bluetooth: HCI socket layer initialized
  [ 34.866754] Bluetooth: L2CAP socket layer initialized
  [ 34.866759] Bluetooth: SCO socket layer initialized
  [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
  [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-9b] only partially covers this bridge
  [ 35.003383] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
  [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 
08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  bluetooth 491520 1 btusb
  Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1490937] Re: Unavailable port selected by default

[David Henningsson]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => David Henningsson (diwic)

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

Title:
  Unavailable port selected by default

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Won't Fix
Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  In case one card has only unavailable ports, it might be still be
  selected as default, even though there are available ports on other
  cards.

  E g, on a HTPC which have only Headphone and HDMI outputs, and these
  two outputs are on separate cards, the headphone port might be
  selected even if the HDMI port is available and the headphone port is
  not.

  Probably PulseAudio's routing system needs to be rewritten to be more
  port based to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1490937/+subscriptions

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

[Touch-packages] [Bug 1494322] Re: Address book service log contains several warning messages related with vcard parse

[Timo Jyrinki]

Vivid-overlay: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-023

(Wily: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-031)

Please test and report back. Of the test plan
https://wiki.ubuntu.com/Process/Merges/TestPlan/qtpim - I can execute
the autopilot comparison and run UITK unit tests, but please do address
book app manual tests and whatever else you want to check.

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

Title:
  Address book service log contains several warning messages related
  with vcard parse

Status in address-book-service package in Ubuntu:
  New
Status in qtpim-opensource-src package in Ubuntu:
  New

Bug description:
  Several messages of : 'Variant value is a QStringList but the
  property's value type is neither CompoundType or ListType' into the
  address-book-service log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1494322/+subscriptions

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

[Touch-packages] [Bug 1472026] Re: Crashes when supplied with unknown type id

[Launchpad Bug Tracker]

This bug was fixed in the package content-hub -
0.0+15.10.20150909-0ubuntu1

---
content-hub (0.0+15.10.20150909-0ubuntu1) wily; urgency=medium

  [ Ken VanDine ]
  * Fixed crash when the service is passed an invalid type via dbus (LP:
#1472026)

  [ Michael Sheldon ]
  * Add an "Undefined" content type to QML bindings so we can avoid
making unnecessary peer look ups when the content type hasn't yet
been set now that peers can register for Unknown.

  [ Robert Ancell ]
  * Drop unused include that makes build fail unless Qt5Gui pkg-config
file is used.

 -- Ken VanDine   Wed, 09 Sep 2015 16:58:39
+

** Changed in: content-hub (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Crashes when supplied with unknown type id

Status in content-hub package in Ubuntu:
  Fix Released

Bug description:
  If you access the DBus interface methods KnownDestinationsForType,
  KnownSharesForType or KnownSourcesForType with an invalid type_id
  (e.g. '') the content hub service crashes. This is because it used the
  id as a GSettings key and it is considered a programmer error to look
  up a key that does not exist [1].

  [1] https://developer.gnome.org/gio/stable/GSettings.html#g-settings-
  get-value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1472026/+subscriptions

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

[Touch-packages] [Bug 1494322] Re: Address book service log contains several warning messages related with vcard parse

[Launchpad Bug Tracker]

** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtpim-
opensource-src

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

Title:
  Address book service log contains several warning messages related
  with vcard parse

Status in address-book-service package in Ubuntu:
  New
Status in qtpim-opensource-src package in Ubuntu:
  New

Bug description:
  Several messages of : 'Variant value is a QStringList but the
  property's value type is neither CompoundType or ListType' into the
  address-book-service log file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1494322/+subscriptions

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

[Touch-packages] [Bug 1484126] Re: [Indicators] Volume notification unnecessary when adjusting volume slider

[Lukáš Tinkl]

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

** No longer affects: indicator-sound (Ubuntu)

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

Title:
  [Indicators] Volume notification unnecessary when adjusting volume
  slider

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Committed

Bug description:
  Current situation:

  Go to Sound section of indicators, drag volume slider. The volume
  notification pops up, essentially replicating the slider below

  
  Desired solution:

  Let's remove the volume notification when sliding the the volume
  slider

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1484126/+subscriptions

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

[Touch-packages] [Bug 1472755] Re: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted double-linked list: ADDR ***

[Timo Jyrinki]

Some more recent that may be related (but are incomplete as reports):
https://errors.ubuntu.com/oops/72595200-5186-11e5-a598-fa163e5bb1a2
https://errors.ubuntu.com/oops/73424db6-5186-11e5-8e22-fa163e22e467

And a more recent full report:
https://errors.ubuntu.com/oops/8cea3adc-5567-11e5-a560-fa163e707a72

If it's about "no messages", it could be related to the fact that the
app shows "No messages" initially at times when it's launched, before it
populates with all the content there is.

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

Title:
  /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in
  `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted
  double-linked list: ADDR ***

Status in Canonical System Image:
  Confirmed
Status in libqtelegram package in Ubuntu:
  Triaged
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scope-mediascanner.  This problem was most recently
  seen with version 1.7.16, the problem page at
  https://errors.ubuntu.com/problem/21d9e7ddf91a26b21abfb2758315ad41fcfd3fa9
  contains more details.

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

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

[Touch-packages] [Bug 1494633] [NEW] alphabet slider does not work correctly

[Hans-Peter]

Public bug reported:

On an bq aquaris 4.5, stable channel, since September:
If you use the alphabet slider the first time, and you highlight, for example, 
'T',
the list scrolls to Contacts somewhere around 'E' . If you use the slider 
multiple
times, behaviour get better, but is not reliable.
Hans-Peter

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

Title:
  alphabet slider does not work correctly

Status in address-book-app package in Ubuntu:
  New

Bug description:
  On an bq aquaris 4.5, stable channel, since September:
  If you use the alphabet slider the first time, and you highlight, for 
example, 'T',
  the list scrolls to Contacts somewhere around 'E' . If you use the slider 
multiple
  times, behaviour get better, but is not reliable.
  Hans-Peter

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

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

[Touch-packages] [Bug 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4

[Daniel van Vugt]

** Tags added: xmir

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

Title:
  Xmir crashes immediately on startup using glamor on Nexus4

Status in libepoxy package in Ubuntu:
  In Progress
Status in libhybris package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Xmir crashes immediately on startup using glamor on Nexus4.

  glamor GL version: OpenGL ES 3.0 V@53.0 AU@  (CL@)
  ...
  glamor GLSL version: OpenGL ES GLSL ES 3.00
  (EE)
  (EE) Backtrace:
  (EE)
  (EE) Segmentation fault at address 0x0
  (EE)
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE)

  The stack trace is lost. However the problem appears to be the
  glGetStringi() function. This function is new in GLESv3 and libepoxy
  only uses it because the GLES version is 3.0 on mako. However,
  libhybris fails to implement glGetStringi() and forward it to the
  driver correctly. At least that seems to be the problem. Our hybris
  GLESv2 is missing the function but the Android GLESv2 on the device
  has it.

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

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

[Touch-packages] [Bug 1375215] Re: System runs out of memory - white screens frequently seen in web renderers

[Jean-Baptiste Lallement]

The browser's render process being killed by OOM is bug 1478853

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

Title:
  System runs out of memory - white screens frequently seen in web
  renderers

Status in Canonical System Image:
  Confirmed
Status in oxide-qt package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  [See latest comments for recent repro notes]

  krillin 14.09 #2 + all updates applied

  After running the system for a while (few minutes) the system runs out of 
memory and start killing processes.
  It is very visible with the webbrowser or webapps because it renders the page 
and displays a white page when oxide-render is killed. Although it is not 
specific to oxide, and any app are killed (address-book, system-settings, ...) 
You can clearly notice that other apps are being killed because when you switch 
to the app it's all blurry and take a while to reload, also it loses its state 
(for example, you lose the message you were writing in the messaging-app)

  There is no specific steps to reproduce. I have several scopes enabled
  (photos, nearby, news) You don't have to have tons of apps open to
  reproduce this. Launching the webbrowser or a webapps and navigating
  on the phone between the scopes and the open app seems enough for the
  system to start killing processes.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: liboxideqtcore0 1.2.0-0ubuntu1 [origin: Ubuntu RTM]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  Date: Mon Sep 29 12:51:34 2014
  InstallationDate: Installed on 2014-09-24 (5 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140924-030204)
  SourcePackage: oxide-qt
  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/1375215/+subscriptions

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

[Touch-packages] [Bug 1494613] Re: Some pictures downloaded from openclipart.org are shown as black in Gallery app

[Evan Wang]

** Attachment added: "Money-People-Silhouette.png"
   
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1494613/+attachment/4461187/+files/Money-People-Silhouette.png

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

Title:
  Some pictures downloaded from openclipart.org are shown as black in
  Gallery app

Status in gallery-app package in Ubuntu:
  New

Bug description:
  $ adb shell system-image-cli -i
  current build number: 121
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-09-11 06:22:16
  version version: 121
  version ubuntu: 20150911
  version device: 20150821-736d127
  version custom: 20150821-887-33-32-vivid

  Steps to reproduce:
  1. open up browser and go to openclipart.org
  2. scroll to the "New Clipart" section 
  3. long press on one thumbnail(refer to the pictures attached) select "Save 
image"
  4. select Gallery to Open with
  5. once a notification is displayed with "Download Complete" message" click 
on "Open" button
  6. the Gallery is displayed and the downloaded picture is shown in the Events 
view

  Expected results:
  The pictures downloaded are shown correctly

  Actual results:
  The pictures downloaded are shown as black
  not found more differences from other pictures except they are all 
black-white pictures.

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

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

[Touch-packages] [Bug 1494613] [NEW] Some pictures downloaded from openclipart.org are shown as black in Gallery app

[Evan Wang]

Public bug reported:

$ adb shell system-image-cli -i
current build number: 121
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-09-11 06:22:16
version version: 121
version ubuntu: 20150911
version device: 20150821-736d127
version custom: 20150821-887-33-32-vivid

Steps to reproduce:
1. open up browser and go to openclipart.org
2. scroll to the "New Clipart" section 
3. long press on one thumbnail(refer to the pictures attached) select "Save 
image"
4. select Gallery to Open with
5. once a notification is displayed with "Download Complete" message" click on 
"Open" button
6. the Gallery is displayed and the downloaded picture is shown in the Events 
view

Expected results:
The pictures downloaded are shown correctly

Actual results:
The pictures downloaded are shown as black
not found more differences from other pictures except they are all black-white 
pictures.

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

** Attachment added: "Shopping-Cart-Icon.png"
   
https://bugs.launchpad.net/bugs/1494613/+attachment/4461186/+files/Shopping-Cart-Icon.png

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

Title:
  Some pictures downloaded from openclipart.org are shown as black in
  Gallery app

Status in gallery-app package in Ubuntu:
  New

Bug description:
  $ adb shell system-image-cli -i
  current build number: 121
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-09-11 06:22:16
  version version: 121
  version ubuntu: 20150911
  version device: 20150821-736d127
  version custom: 20150821-887-33-32-vivid

  Steps to reproduce:
  1. open up browser and go to openclipart.org
  2. scroll to the "New Clipart" section 
  3. long press on one thumbnail(refer to the pictures attached) select "Save 
image"
  4. select Gallery to Open with
  5. once a notification is displayed with "Download Complete" message" click 
on "Open" button
  6. the Gallery is displayed and the downloaded picture is shown in the Events 
view

  Expected results:
  The pictures downloaded are shown correctly

  Actual results:
  The pictures downloaded are shown as black
  not found more differences from other pictures except they are all 
black-white pictures.

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

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

[Touch-packages] [Bug 1494155] Re: [mako] pulseaudio resample methos missing src-sinc-*

[David Henningsson]

According to Alexander Patrakov's evaluation, both speex-float-5 and
speex-float-10 are same or better than libsamplerate's highest quality.

So far we've trusted his word on that. If you want to challenge that, I
suggest you do so on the pulseaudio-discuss mailinglist.

For reference, here's a link to the first part of his evaluation,
including some graphs:
http://comments.gmane.org/gmane.comp.audio.pulseaudio.general/21051

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

Title:
  [mako] pulseaudio resample methos missing src-sinc-*

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  I tried to change the pulse resampling on my mako to src-sinc-best-
  quality and medium, to no avail.

  Later i found out that the pulse shipped with mako isnt capable of
  using these resampling methods.

  $ pulseaudio --dump-resample-methods
  trivial
  speex-float-0
  speex-float-1
  speex-float-2
  speex-float-3
  speex-float-4
  speex-float-5
  speex-float-6
  speex-float-7
  speex-float-8
  speex-float-9
  speex-float-10
  speex-fixed-0
  speex-fixed-1
  speex-fixed-2
  speex-fixed-3
  speex-fixed-4
  speex-fixed-5
  speex-fixed-6
  speex-fixed-7
  speex-fixed-8
  speex-fixed-9
  speex-fixed-10
  ffmpeg
  auto
  copy
  peaks

  while on an other system (non ubuntu touch) i get the correct
  resampling methods:

  $ pulseaudio --dump-resample-methods
  src-sinc-best-quality
  src-sinc-medium-quality
  src-sinc-fastest
  src-zero-order-hold
  src-linear
  trivial
  speex-float-0
  speex-float-1
  speex-float-2
  speex-float-3
  speex-float-4
  speex-float-5
  speex-float-6
  speex-float-7
  speex-float-8
  speex-float-9
  speex-float-10
  speex-fixed-0
  speex-fixed-1
  speex-fixed-2
  speex-fixed-3
  speex-fixed-4
  speex-fixed-5
  speex-fixed-6
  speex-fixed-7
  speex-fixed-8
  speex-fixed-9
  speex-fixed-10
  ffmpeg
  auto
  copy
  peaks

  
  ubuntu touch version:
  current build number: 23
  device name: mako
  channel: ubuntu-touch/stable/ubuntu
  last update: 2015-08-27 10:42:51
  version version: 23
  version ubuntu: 20150825.1
  version device: 20150819
  version custom: 20150825.1

  pulseaudio version:
  pulseaudio:
Installed: 1:6.0-0ubuntu9.2
Candidate: 1:6.0-0ubuntu9.2
Version table:
   *** 1:6.0-0ubuntu9.2 0
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1494626] [NEW] 12:04: resize2fs: Ignores size suffix

[TJ]

Public bug reported:

"man resize2fs" states "Optionally, the size parameter may be suffixed
by one of the following the units designators: 's', 'K', 'M', or 'G',
for 512 byte sectors, kilobytes, megabytes, or gigabytes, respectively."

In practice the suffix appears to be ignored.

$ sudo resize2fs /dev/fujiVG/home 10G
resize2fs 1.42 (29-Nov-2011)
resize2fs: New size smaller than minimum (5124061)

$ sudo dumpe2fs /dev/fujiVG/home | grep 'Block size'
dumpe2fs 1.42 (29-Nov-2011)
Block size:   4096

$ sudo resize2fs  -P /dev/fujiVG/home
resize2fs 1.42 (29-Nov-2011)
Estimated minimum size of the filesystem: 5124061

$ df /home
Filesystem  1K-blocksUsed Available Use% Mounted on
/dev/mapper/fujiVG-home  30963708 2438852  26952120   9% /home
$ df -B 4096 /home
Filesystem  4K-blocks   Used Available Use% Mounted on
/dev/mapper/fujiVG-home   7740927 609713   6738030   9% /home
$ df -B 512 /home
Filesystem  512B-blocksUsed Available Use% Mounted on
/dev/mapper/fujiVG-home61927416 4877704  53904240   9% /home

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

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

Title:
  12:04:  resize2fs: Ignores size suffix

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  "man resize2fs" states "Optionally, the size parameter may be suffixed
  by one of the following the units designators: 's', 'K', 'M', or 'G',
  for 512 byte sectors, kilobytes, megabytes, or gigabytes,
  respectively."

  In practice the suffix appears to be ignored.

  $ sudo resize2fs /dev/fujiVG/home 10G
  resize2fs 1.42 (29-Nov-2011)
  resize2fs: New size smaller than minimum (5124061)

  $ sudo dumpe2fs /dev/fujiVG/home | grep 'Block size'
  dumpe2fs 1.42 (29-Nov-2011)
  Block size:   4096

  $ sudo resize2fs  -P /dev/fujiVG/home
  resize2fs 1.42 (29-Nov-2011)
  Estimated minimum size of the filesystem: 5124061

  $ df /home
  Filesystem  1K-blocksUsed Available Use% Mounted on
  /dev/mapper/fujiVG-home  30963708 2438852  26952120   9% /home
  $ df -B 4096 /home
  Filesystem  4K-blocks   Used Available Use% Mounted on
  /dev/mapper/fujiVG-home   7740927 609713   6738030   9% /home
  $ df -B 512 /home
  Filesystem  512B-blocksUsed Available Use% Mounted on
  /dev/mapper/fujiVG-home61927416 4877704  53904240   9% /home

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

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

[Touch-packages] [Bug 1494599] Re: package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig'

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: qt4-x11 (Ubuntu)
   Status: New => Invalid

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

Title:
  package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/x86_64
  -linux-gnu/qt4/bin/qtconfig' to '/usr/lib/x86_64-linux-
  gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file or stream

Status in qt4-x11 package in Ubuntu:
  Invalid

Bug description:
  Doing dist-upgrade on fresh ubuntu-mate15.04, get this error

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  Date: Fri Sep 11 00:54:33 2015
  DuplicateSignature: 
package:qt4-qtconfig:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1:cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: qt4-x11
  Title: package qt4-qtconfig 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig' to 
'/usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1494599/+subscriptions

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

[Touch-packages] [Bug 1494630] [NEW] app crashes when selecting a contact from favourites

[Hans-Peter]

Public bug reported:

On a bq aquaris 4.5, stable channel, since September:
When selecting a contact from 'Favourites', the app crashes every time.
When selecting the same person from 'All', everyhing is fine.
Regards

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

Title:
  app crashes when selecting a contact from favourites

Status in messaging-app package in Ubuntu:
  New

Bug description:
  On a bq aquaris 4.5, stable channel, since September:
  When selecting a contact from 'Favourites', the app crashes every time.
  When selecting the same person from 'All', everyhing is fine.
  Regards

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

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

[Touch-packages] [Bug 1481330] Re: Xmir crashes when client closes display

[Daniel van Vugt]

For me I found much improved stability on client disconnection after
this fix:

https://git.launchpad.net/~xmir-team/xorg-
server/+git/xmir/commit/?id=9287786b58a90cf376c05692fe4d6d0712946337

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

Title:
  Xmir crashes when client closes display

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Xmir crashes when a client loses its connection to Xmir, either
  through XCloseDisplay, or by normal program termination. This affects
  xprop and GTK applications (they temporarily open a connection to the
  X server to obtain the value of the AT_SPI_BUS property on the root
  window).

  This is what is printed in application's upstart log:

  (EE)
  Fatal server error:
  (EE) Failed to connect to Mir: Failed to process connect response: 
/build/mir-3eDTxk/mir-0.14.0+15.10.20150723.1/src/client/probing_client_platform_factory.cpp(37):
 Throw in function virtual std::shared_ptr 
mir::client::ProbingClientPlatformFactory::create_client_platform(mir::client::ClientContext*)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error
  std::exception::what: No appropriate client platform module found

  (EE)

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

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

[Touch-packages] [Bug 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4

[Daniel van Vugt]

** Tags added: mako

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

Title:
  Xmir crashes immediately on startup using glamor on Nexus4

Status in libepoxy package in Ubuntu:
  In Progress
Status in libhybris package in Ubuntu:
  Won't Fix
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Xmir crashes immediately on startup using glamor on Nexus4.

  glamor GL version: OpenGL ES 3.0 V@53.0 AU@  (CL@)
  ...
  glamor GLSL version: OpenGL ES GLSL ES 3.00
  (EE)
  (EE) Backtrace:
  (EE)
  (EE) Segmentation fault at address 0x0
  (EE)
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE)

  The stack trace is lost. However the problem appears to be the
  glGetStringi() function. This function is new in GLESv3 and libepoxy
  only uses it because the GLES version is 3.0 on mako. However,
  libhybris fails to implement glGetStringi() and forward it to the
  driver correctly. At least that seems to be the problem. Our hybris
  GLESv2 is missing the function but the Android GLESv2 on the device
  has it.

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

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

[Touch-packages] [Bug 1494641] [NEW] sending messages from today scope is clumsy

[Hans-Peter]

Public bug reported:

On a bq aquaris 4.5, stable channel.
It is very  cumbersome to send a message to a fav contact from  the today 
scope. Actually, not sending the message, that works ok (ok, you have to hit 
[more] to get to it). But when the message is sent, the work begins. The back 
arrow (if you decide not to send the message) doesn't bring you back to the 
contact details but brings you back (why back, I haven't been there before) to 
the list of conversations. From there you can swipe (from the right) back to 
the contact details, which are not of interest anymore, and another back arrow 
brings you back to the today scope where you can choose another fav contact. 
That is so clumsy!
Regards,
Hans-Peter

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

** Description changed:

  On a bq aquaris 4.5, stable channel.
- It is very  cumbersome to send a message to a fav contact from  the today 
scope. Actually, not sending the message, that works ok (ok, you have to hit 
[more] to get to it). But when the message is sent, the work begins. The back 
error (if you decide not to send the message) doesn't bring you back to the 
contact details but brings you back (why back, I haven't been there before) to 
the list of conversations. From there you can swipe (from the right) back to 
the contact details, which are not of interest anymore, and another back arrow 
brings you back to the today scope where you can choose another fav contact. 
That is so clumsy!
+ It is very  cumbersome to send a message to a fav contact from  the today 
scope. Actually, not sending the message, that works ok (ok, you have to hit 
[more] to get to it). But when the message is sent, the work begins. The back 
arrow (if you decide not to send the message) doesn't bring you back to the 
contact details but brings you back (why back, I haven't been there before) to 
the list of conversations. From there you can swipe (from the right) back to 
the contact details, which are not of interest anymore, and another back arrow 
brings you back to the today scope where you can choose another fav contact. 
That is so clumsy!
  Regards,
  Hans-Peter

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

Title:
  sending messages from today scope is clumsy

Status in address-book-app package in Ubuntu:
  New

Bug description:
  On a bq aquaris 4.5, stable channel.
  It is very  cumbersome to send a message to a fav contact from  the today 
scope. Actually, not sending the message, that works ok (ok, you have to hit 
[more] to get to it). But when the message is sent, the work begins. The back 
arrow (if you decide not to send the message) doesn't bring you back to the 
contact details but brings you back (why back, I haven't been there before) to 
the list of conversations. From there you can swipe (from the right) back to 
the contact details, which are not of interest anymore, and another back arrow 
brings you back to the today scope where you can choose another fav contact. 
That is so clumsy!
  Regards,
  Hans-Peter

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

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

[Touch-packages] [Bug 1494442] Re: Turn whoopsie reporting off by default for phone on stable channel

[Jean-Baptiste Lallement]

I think it is not whoopsie that needs to be disabled but apport which is
responsible of generating the crash file and is the source of the load
on the device when a crash occurs. If the crash file is not uploaded
then there is no need to generate it at all on a retail phone.

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

Title:
  Turn whoopsie reporting off by default for phone on stable channel

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  To avoid UI freezes and perceptions of slowness, we would like to turn
  this option off by default for consumers, but leave it on for
  developers and in the proposed channels.

  Once bug #1437633 is fixed, we can put "manual" in the
  whoopsie.override file

  Not sure how to do this conditionally just for stable

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

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

[Touch-packages] [Bug 1413818] [NEW] Notification sounds aren't being played back on E4.5

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This affects mostly the push notifications based alerts, SMS et.al. work
fine.

With export PULSE_PROP='media.role=alert'

This has no audible output: paplay 
/usr/share/sounds/ubuntu/notifications/Slick.ogg
This does:  paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg

$ system-image-cli -i
current build number: 14
device name: mako
channel: ubuntu-touch/stable
alias: ubuntu-touch/ubuntu-rtm/14.09
last update: 2015-01-16 13:12:29
version version: 14
version ubuntu: 20150116
version device: 20141119
version custom: mako-1.1

The hunch is some buffering going on on the android side for short sound
bytes.

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: John McAleely (john.mcaleely)
 Status: Confirmed

** Affects: pulseaudio (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: bq
-- 
Notification sounds aren't being played back on E4.5
https://bugs.launchpad.net/bugs/1413818
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1438486] Re: Turning off sound in Pathwind mutes other apps too

[John McAleely]

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

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

Title:
   Turning off sound in Pathwind mutes other apps too

Status in Canonical System Image:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu RTM:
  Invalid
Status in ubuntu-touch-session package in Ubuntu RTM:
  Fix Released

Bug description:
  current build number: 260
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-03-30 18:17:44
  version version: 260
  version ubuntu: 20150330
  version device: 20150327-f7072d0
  version custom: 20150216-561-29-186

  In Pathwind (part of the custom tarball installed with newer flashes but also 
in the store) one can toggle sound on/off.
  If set to off sound won't be heard in youtube playbacks in the browser, cut 
the rope, media player. It still works for keyboard press sounds if enabled, 
and ringtones work as well.
  This may be intentional, but at least on one occasion it persisted even after 
pathwind quit, and sound did not work in the rest of the apps.

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

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

[Touch-packages] [Bug 1185784] Re: Multi-monitor configuration with different vertical resolution

[Martin Goth]

Maybe this can split into several bug reports, since there could be
several  causes for the single points.

Personally I can confirm point 3). I will further explain the problem.

My setup is a one portrait monitor (1920x1080) and one landscape
(1080x1920). My desktop background is 1920x1920 so in zoom & center
setting both monitors are filled without the background being zoomed.
However after relogin or reboot the secondary landscape monitor's
background is either zoomed by 1.7x (1920/1080) or cropped to 1080x1080
leaving black bars left and right, whether the setting was zoom or
center. Switching between zoom and center in the setting then returns
the original mode.

Steps to reproduce:
1. Have two fullhd monitors, primary in portrait, other in landscape mode.
2. Set a 1920x1920 image as desktop background
3. Set center or zoom mode
4. Log out and log in again

** Attachment added: "Screenshots of the two error modes and how it should be"
   
https://bugs.launchpad.net/unity/+bug/1185784/+attachment/4461221/+files/screenshots.tgz

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

Title:
  Multi-monitor configuration with different vertical resolution

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  I observe this bug for a long time in all versions of Ubuntu.
  Bug is simple: ubuntu doesn't work correctly with 2 or more monitors that 
have different vertical resolution.
  This bug starts at login screen, where monitors works as mirrors, and ends in 
Unity with different bugs with background, windows position and so on.

  Now I'm using Ubuntu 13.04 and radeon driver.
  I have 2 monitors with resolution 2560x1440, they are connected to 2 video 
cards (tried HD5450+HD5450 and HD6570+HD5450).
  In this case configuration with two horizontal monitors works good enough, 
but when I rotate monitors - several bugs occurred at the same place:
  1) It is not possible to rotate any monitor, that is connected to not primary 
video card (primary means installed in the first PCI-E slot), because xserver 
crashes, and I see login screen
  2) If I rotate primary screen - I see large degradation in performance 
(comparing to horizontal position)
  3)  After reboot primary (rotated) monitor is cropped to height of horizontal 
monitor (and performance is the same as in horizontal position of both 
monitors), and only opening monitors settings window and applying current 
settings without any changes (after this desktop background is not displayed 
correctly [scale mode], but returns if choose any other displaying mode, and 
then switch to scale)
  4) At login screen only primary monitor works and in default (unrotated) 
position

  This all was tested on Ubuntu 13.04 and 13.10 with stock and compiled
  by myself kernels 3.8-3.10-rc3 and with different stock and testing
  versions of radeon driver, mesa, and other stuff from xorg-edgers.

  Sorry if something is not understandable, I'm pretty sure all this is
  simply reproducible and can repeat any steps again with any necessary
  logs to solve this problem as fast as it is possible.

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

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

[Touch-packages] [Bug 1441849] Re: Update force_release for Dell Latitudes

[Pali]

Ok, and can you look at version for Ubuntu Precise?

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

Title:
  Update force_release for Dell Latitudes

Status in systemd package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in udev source package in Precise:
  Triaged
Status in systemd source package in Trusty:
  In Progress
Status in systemd source package in Vivid:
  Fix Released

Bug description:
  Wireless HW switch on Dell Latitude notebooks generate key press event
  via AT Translated Set 2 keyboard, but does *not* generate release key
  event. This means that operating systems and applications see key
  still pressed.

  Scan code of that problematic key is 136 (0x88).

  Fixing this problem can be done via force_release option of atkbd
  kernel driver (by adding 136 scan code to list)

  Kernel developers told me that now only userspace (udev package)
  maintains list of those problematic scan codes and so udev needs to be
  extended/patched to add new values to atkbd kernel driver at runtime.
  See: https://lkml.org/lkml/2015/4/5/157

  Currenly there is file /lib/udev/keymaps/force-release/dell-touchpad
  which contains some force_release scan code for all dell latitude
  notebooks handled by file /lib/udev/rules.d/95-keyboard-force-
  release.rules by rule:

  ENV{DMI_VENDOR}=="Dell Inc.",
  ATTR{[dmi/id]product_name}=="*Latitude*|*Precision*", RUN+="keyboard-
  force-release.sh $devpath dell-touchpad"

  Can you extend either /lib/udev/keymaps/force-release/dell-touchpad or
  /lib/udev/rules.d/95-keyboard-force-release.rules to include also scan
  code 136 (0x88)? Because without is there are problems with HW
  wireless switch!

  This problem was tested on Ubuntu 12.04.5 LTS Precise release.

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

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

[Touch-packages] [Bug 1494442] Re: Turn whoopsie reporting off by default for phone on stable channel

[Oliver Grawert]

also the foundation team had some very strong opinions about turning off
bug reporting by default, please involve them in the discussion.

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

Title:
  Turn whoopsie reporting off by default for phone on stable channel

Status in Canonical System Image:
  Confirmed
Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  To avoid UI freezes and perceptions of slowness, we would like to turn
  this option off by default for consumers, but leave it on for
  developers and in the proposed channels.

  Once bug #1437633 is fixed, we can put "manual" in the
  whoopsie.override file

  Not sure how to do this conditionally just for stable

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

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

[Touch-packages] [Bug 1446081] Re: Incorrect scaling of launcher icons

[Gobinath]

Sample problem here.

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

Title:
  Incorrect scaling of launcher icons

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Launcher icons shown w/o issues only on this sizes of launcher: 16,
  24, 32, 48, 64.

  Screenshot attached. Look at Sublime, Chrome and Skype icons. There
  was no such issue before vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Apr 20 00:26:44 2015
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-03-27 (23 days ago)

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

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

[Touch-packages] [Bug 1494620] Re: Allow turning alarm off directly in the indicator

[Nekhelesh Ramananthan]

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

** No longer affects: ubuntu-clock-app

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

Title:
  Allow turning alarm off directly in the indicator

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Hello,
  since I switched from Android to Ubuntu full-time I've been among other 
things using my Ubuntu phone as my alarm. However, I mostly wake up a few 
minutes before the alarm actually starts and in that case I no longer want it 
to make any noises once I am already up.
  On Android I could kill the alarm directly from the "indicator" but here I 
have to go to the indicator, hit the alarm listed there, an app opens, I have 
to slide from the bottom to reveal all alarms and then I can kill it. It is too 
much complicated to do such an easy task.
  I know this is not really a bug, just an idea, and I would very much 
appreciate it to be implemented :), would save me some tome each morning :).

  I suggest to implement slide left/right to kill it or maybe better
  just a simple "delete" button :).

  Thank you very much for considering this and supplying some more
  thoughts on this topic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1494620/+subscriptions

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

[Touch-packages] [Bug 1494625] [NEW] 12:04: resize2fs: unclear/incorrect units in size report

[TJ]

Public bug reported:

'man resize2fs' claims "If no units are specified, the units of the size
parameter shall  be the filesystem blocksize of the filesystem" but
makes no mention of the units used in the minimum size report. The tool
itself makes no mention of units.

Many users would assume the value was in bytes, or possibly KB.

Despite the fact that the operating deals in file-system block-size
units the output appears to be in units of 512-byte sectors.

$ sudo dumpe2fs /dev/fujiVG/home | grep 'Block size'
dumpe2fs 1.42 (29-Nov-2011)
Block size:   4096

$ sudo resize2fs  -P /dev/fujiVG/home
resize2fs 1.42 (29-Nov-2011)
Estimated minimum size of the filesystem: 5124061

$ df /home
Filesystem  1K-blocksUsed Available Use% Mounted on
/dev/mapper/fujiVG-home  30963708 2438852  26952120   9% /home
$ df -B 4096 /home
Filesystem  4K-blocks   Used Available Use% Mounted on
/dev/mapper/fujiVG-home   7740927 609713   6738030   9% /home
$ df -B 512 /home
Filesystem  512B-blocksUsed Available Use% Mounted on
/dev/mapper/fujiVG-home61927416 4877704  53904240   9% /home

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

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

Title:
  12:04: resize2fs: unclear/incorrect units in size report

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  'man resize2fs' claims "If no units are specified, the units of the
  size parameter shall  be the filesystem blocksize of the filesystem"
  but makes no mention of the units used in the minimum size report. The
  tool itself makes no mention of units.

  Many users would assume the value was in bytes, or possibly KB.

  Despite the fact that the operating deals in file-system block-size
  units the output appears to be in units of 512-byte sectors.

  $ sudo dumpe2fs /dev/fujiVG/home | grep 'Block size'
  dumpe2fs 1.42 (29-Nov-2011)
  Block size:   4096

  $ sudo resize2fs  -P /dev/fujiVG/home
  resize2fs 1.42 (29-Nov-2011)
  Estimated minimum size of the filesystem: 5124061

  $ df /home
  Filesystem  1K-blocksUsed Available Use% Mounted on
  /dev/mapper/fujiVG-home  30963708 2438852  26952120   9% /home
  $ df -B 4096 /home
  Filesystem  4K-blocks   Used Available Use% Mounted on
  /dev/mapper/fujiVG-home   7740927 609713   6738030   9% /home
  $ df -B 512 /home
  Filesystem  512B-blocksUsed Available Use% Mounted on
  /dev/mapper/fujiVG-home61927416 4877704  53904240   9% /home

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

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

[Touch-packages] [Bug 1413818] Re: Notification sounds aren't being played back on E4.5

[John McAleely]

** Package changed: pulseaudio (Ubuntu RTM) => pulseaudio (Ubuntu)

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

Title:
  Notification sounds aren't being played back on E4.5

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This affects mostly the push notifications based alerts, SMS et.al.
  work fine.

  With export PULSE_PROP='media.role=alert'

  This has no audible output: paplay 
/usr/share/sounds/ubuntu/notifications/Slick.ogg
  This does:  paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg

  $ system-image-cli -i
  current build number: 14
  device name: mako
  channel: ubuntu-touch/stable
  alias: ubuntu-touch/ubuntu-rtm/14.09
  last update: 2015-01-16 13:12:29
  version version: 14
  version ubuntu: 20150116
  version device: 20141119
  version custom: mako-1.1

  The hunch is some buffering going on on the android side for short
  sound bytes.

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

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

[Touch-packages] [Bug 1494680] [NEW] dialer app laggy since September OTA

[Hans-Peter]

Public bug reported:

Since the September OTA, dialer app is laggy on a bq aquaris 4.5.
If you hit the number keys, the numbers will be displayed with delay. The delay 
varies, but is mostly there and substantial.
This is even if dialer ist the only active app and the cpu is idling.
Regards,
Hans-Peter

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

Title:
  dialer app laggy since September OTA

Status in dialer-app package in Ubuntu:
  New

Bug description:
  Since the September OTA, dialer app is laggy on a bq aquaris 4.5.
  If you hit the number keys, the numbers will be displayed with delay. The 
delay varies, but is mostly there and substantial.
  This is even if dialer ist the only active app and the cpu is idling.
  Regards,
  Hans-Peter

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

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

[Touch-packages] [Bug 1328975] Re: libc6: getaddrinfo() sends DNS queries to random file descriptors

[stevenschlansker]

Additionally, attempting to bring in utopic libc to fix the bug causes
dependency resolution problems down the road.  Both the trusty python3
and Xamarin Mono repositories then start to fail with messages like:

The following packages have unmet dependencies:
nuget : Depends: libnuget-core-cil (= 2.8.7+md510+dhx1-0xamarin1) but it is not 
going to be installed
Depends: libmono-corlib4.5-cil (>= 4.0.0~alpha1) but 3.2.8+dfsg-4ubuntu1 is to 
be installed
Depends: libmono-microsoft-build-framework4.0-cil (>= 3.6.0) but 
3.2.8+dfsg-4ubuntu1 is to be installed
Depends: libmono-microsoft-build4.0-cil (>= 3.6.0) but 3.2.8+dfsg-4ubuntu1 is 
to be installed
Depends: libmono-system-core4.0-cil (>= 4.0.0~alpha1) but 3.2.8+dfsg-4ubuntu1 
is to be installed
Depends: libmono-system4.0-cil (>= 4.0.0~alpha1) but 3.2.8+dfsg-4ubuntu1 is to 
be installed
[91mE: Unable to correct problems, you have held broken packages. [0m [91m

This is an extremely frustrating situation to be in, our application is
crashing almost daily due to this issue, and we seem to have no
supported path forward.

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

Title:
  libc6: getaddrinfo() sends DNS queries to random file descriptors

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid

Bug description:
  There is an upstream report for debian here https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=722075 which has been fixed in eglibc
  2.19.1 which is now in debian jessie/sid.  See that upstream report
  for a short program which replicates the bug.  I was able to replicate
  the bug on Ubuntu 14.04 using that test script.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Jun 11 16:32:43 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  Ec2AMI: ami-30837058
  Ec2AMIManifest: 
ubuntu-us-east-1/images/ubuntu-trusty-14.04-amd64-server-20140607.1.manifest.xml
  Ec2AvailabilityZone: us-east-1a
  Ec2InstanceType: c3.2xlarge
  Ec2Kernel: aki-919dcaf8
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eglibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1493590] Re: package login 1:4.1.5.1-1.1ubuntu4.1 failed to install/upgrade: package login is not ready for configuration cannot configure (current status `half-installed')

[Brian Murray]

** Tags added: bot-stop-nagging

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

Title:
  package login 1:4.1.5.1-1.1ubuntu4.1 failed to install/upgrade:
  package login is not ready for configuration  cannot configure
  (current status `half-installed')

Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  I think I first got this error when trying to install software through
  the App Store and also through the terminal. Then I ran "sudo-apt-get
  upgrade -Y" and my installation went smoothly. However, I got this
  error again when I restarted my system.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: login 1:4.1.5.1-1.1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  Date: Wed Sep  9 00:33:09 2015
  DpkgTerminalLog:
   dpkg: error processing package login (--configure):
package login is not ready for configuration
cannot configure (current status `half-installed')
  DuplicateSignature: package:login:1:4.1.5.1-1.1ubuntu4.1:package login is not 
ready for configuration  cannot configure (current status `half-installed')
  ErrorMessage: package login is not ready for configuration  cannot configure 
(current status `half-installed')
  InstallationDate: Installed on 2014-06-09 (456 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: shadow
  Title: package login 1:4.1.5.1-1.1ubuntu4.1 failed to install/upgrade: 
package login is not ready for configuration  cannot configure (current status 
`half-installed')
  UpgradeStatus: Upgraded to vivid on 2015-04-28 (133 days ago)

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

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

[Touch-packages] [Bug 1328975] Re: libc6: getaddrinfo() sends DNS queries to random file descriptors

[stevenschlansker]

It looks like the bug may actually be fixed in trusty-security eglibc
2.19-0ubuntu6.6

eglibc (2.19-0ubuntu6.6) trusty-security; urgency=medium

  * SECURITY UPDATE: getaddrinfo writes to random file descriptors under
high load
- debian/patches/any/cvs-resolv-reuse-fd.diff: reload file descriptor
  after calling reopen in resolv/res_send.c.
- CVE-2013-7423

So this bug status is misleading; the issue should be fixed against
Trusty I believe.

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

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

Title:
  libc6: getaddrinfo() sends DNS queries to random file descriptors

Status in eglibc package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Trusty:
  Confirmed
Status in glibc source package in Trusty:
  Invalid

Bug description:
  There is an upstream report for debian here https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=722075 which has been fixed in eglibc
  2.19.1 which is now in debian jessie/sid.  See that upstream report
  for a short program which replicates the bug.  I was able to replicate
  the bug on Ubuntu 14.04 using that test script.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Jun 11 16:32:43 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  Ec2AMI: ami-30837058
  Ec2AMIManifest: 
ubuntu-us-east-1/images/ubuntu-trusty-14.04-amd64-server-20140607.1.manifest.xml
  Ec2AvailabilityZone: us-east-1a
  Ec2InstanceType: c3.2xlarge
  Ec2Kernel: aki-919dcaf8
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: eglibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1494909] Re: package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to stat `./usr/share/doc/libuuid1/copyright' (which I was about to install): Input/output error

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to
  stat `./usr/share/doc/libuuid1/copyright' (which I was about to
  install): Input/output error

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  SO linux ubuntu 15.4 64-bit

  Não sei a real causa de erro mas sei que o ubuntu mostrou varis
  mensagem de erros diferente e eu não consigo reparar o erros do
  netbeans 8.0.2 que esta tendo problema com o java 8 e o
  GlassFish_Server também não esta funcionado corretamente.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libuuid1 2.25.2-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  Date: Fri Sep 11 12:51:08 2015
  DuplicateSignature: package:libuuid1:2.25.2-4ubuntu3:unable to stat 
`./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
  ErrorMessage: unable to stat `./usr/share/doc/libuuid1/copyright' (which I 
was about to install): Input/output error
  InstallationDate: Installed on 2015-08-17 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: util-linux
  Title: package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to 
stat `./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1494885] [NEW] package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Fabio Monteverde]

Public bug reported:

any

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1.4
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportLog:
 
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CrashReports: 600:0:118:116823:2015-09-11 16:07:24.816389799 +0200:2015-09-11 
16:07:25.816389799 +0200:/var/crash/apport.0.crash
Date: Fri Sep 11 16:07:25 2015
DuplicateSignature: package:apport:2.17.2-0ubuntu1.4: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-08-30 (12 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: apport
Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

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

Title:
  package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  any

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.4
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportLog:
   
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CrashReports: 600:0:118:116823:2015-09-11 16:07:24.816389799 +0200:2015-09-11 
16:07:25.816389799 +0200:/var/crash/apport.0.crash
  Date: Fri Sep 11 16:07:25 2015
  DuplicateSignature: package:apport:2.17.2-0ubuntu1.4: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-08-30 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: apport
  Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1435324] Re: qtbase5-dev not installable on Ubuntu 14.04 LTS

[Nicholas Skaggs]

For those who might come across this issue, I was able to workaround it
and install things by manually specifying all the needed dependencies.

sudo apt-get install libgles2-mesa-dev libegl1-mesa-dev libwayland-dev
qtbase5-dev

Should this occur in the future, you  likely can build a similar string
of depends that apt isn't picking up on and install them together.

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

Title:
  qtbase5-dev not installable on Ubuntu 14.04 LTS

Status in apt package in Ubuntu:
  Confirmed
Status in mesa-lts-vivid package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  I discovered the problem when I tried to compile a Qt5 QML program firstly.
  I have an Ubuntu 14.04.2 LTS with all updates, no significant PPAs (only 
nodejs and owncloud, not affecting this problem here) and with all the 
-lts-utopic upgrade packages installed.

  With that system, I tried to install qtbase5-dev, and apt told me:

  [...]
  The following packages have unmet dependencies:
   qtbase5-dev : Depends: libgles2-mesa-dev or
  libgles2-dev but it is not installable
   unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not 
going to be installed
  Depends: libcheese7 (>= 3.0.1) but it is not going to 
be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  So this package seems to be not installable. This tried in synaptic,
  it tries to uninstall all -lts-utopic packages (inclusive all
  xserver*.deb) and install the "old" ones instead of them.

  So the problem somewhere lies within the new lts packages that seem
  not to be compatible with qtbase5-dev (and its dependency: libgles2
  -mesa-dev - but I am not able to find out further.

  The problem is: Qt5 development on an Ubuntu 14.04.2 LTS machine is
  NOT possible without a fix. The make process always complains about
  not finding gl libraries.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: qtbase5-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 14:01:20 2015
  InstallationDate: Installed on 2015-02-25 (26 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1475749] [shadow/vivid] possible regression found

[Ubuntu Foundations Team Bug Bot]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of shadow from vivid-proposed
was performed and bug 1493590 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed"
tag from this bug report and tag 1493590 "bot-stop-nagging". Thanks!

** Tags added: verification-failed

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

Title:
  usermod --add-subuids fails for users not in /etc/passwd

Status in Canonical System Image:
  New
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Vivid:
  Fix Committed

Bug description:
  [SRU justification]
  The (distro patched) subuid/subgid support in the shadow 'usermod' command 
only works with users present in /etc/passwd.  As /etc/subuid and /etc/subgid 
are separate databases that do not require modification of /etc/passwd, this is 
an unnecessary restriction that appears to be due to a simple logic bug in the 
patch and not as a deliberate design decision.  As Ubuntu Touch and Ubuntu 
Snappy systems will as a class have users in different NSS backends from 
/etc/passwd, and lxc should be supported for these users with uid namespacing, 
this bug warrants fixing.

  [Test case]
  1. Install the libnss-extrausers package
  2. Enable it by running "sudo sed -i -e'/passwd:/ s/$/ extrausers/' 
/etc/nsswitch.conf"
  3. Create a test user by running "echo 
'testuser:x:2000:2000::/nonexistent:/bin/false' | sudo tee 
/var/lib/extrausers/passwd"
  4. Attempt to add subuids for this user by running "sudo usermod 
--add-subuids 1-12000 testuser"
  5. Confirm that this fails with the error message "usermod: user 'testuser' 
does not exist in /etc/passwd"
  6. Install the new version of the 'passwd' package
  7. Repeat the test from step 4
  8. Confirm that the command now succeeds, and the user's entry has been added 
to /etc/subuid
  9. Clean up by running 'sudo usermod --del-subuids 1-12000 testuser" and 
removing the /var/lib/extrausers/passwd file

  [Regression potential]
  This is a targeted bugfix in the behavior of usermod, and users are unlikely 
to be relying on the usermod command failing for non-local users.

  [Original report]
  currently we have need to utilize lxc on vivid+stable overlay which requires 
adding subuser & subgroup ids.
  unfortunately, usermod currently fails since phablet password is readonly

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

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

[Touch-packages] [Bug 1450747] Re: Native overlay scrollbars aren't themed

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/wily-proposed/ubuntu-themes

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

Title:
  Native overlay scrollbars aren't themed

Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  In 3.16 (from ppa:ubuntu-desktop/ww + overlay-scrollbar from this
  PPA), applications have native overlay scrollbars provided by GTK. We
  want to use these in Ubuntu, but currently they are not themed so look
  a bit incongruous. I think we want to theme them to fit in with
  Ambiance/Radiance.

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

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

[Touch-packages] [Bug 1494885] Re: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1494885

Title:
  package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in apport package in Ubuntu:
  New

Bug description:
  any

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.4
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportLog:
   
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CrashReports: 600:0:118:116823:2015-09-11 16:07:24.816389799 +0200:2015-09-11 
16:07:25.816389799 +0200:/var/crash/apport.0.crash
  Date: Fri Sep 11 16:07:25 2015
  DuplicateSignature: package:apport:2.17.2-0ubuntu1.4: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-08-30 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: apport
  Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1494620] Re: Allow turning alarm off directly in the indicator

[zub]

For repeated alarms, it would be nice to have a "skip this time" option.
(Exactly for the case that I'm actually awake. But if it's periodic
alarm, I might not want to turn the alarm off as I might want it next
time.)

But getting this right in the UI sounds non-trivial.

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

Title:
  Allow turning alarm off directly in the indicator

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Hello,
  since I switched from Android to Ubuntu full-time I've been among other 
things using my Ubuntu phone as my alarm. However, I mostly wake up a few 
minutes before the alarm actually starts and in that case I no longer want it 
to make any noises once I am already up.
  On Android I could kill the alarm directly from the "indicator" but here I 
have to go to the indicator, hit the alarm listed there, an app opens, I have 
to slide from the bottom to reveal all alarms and then I can kill it. It is too 
much complicated to do such an easy task.
  I know this is not really a bug, just an idea, and I would very much 
appreciate it to be implemented :), would save me some tome each morning :).

  I suggest to implement slide left/right to kill it or maybe better
  just a simple "delete" button :).

  Thank you very much for considering this and supplying some more
  thoughts on this topic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1494620/+subscriptions

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

[Touch-packages] [Bug 1420554] Re: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: triggers looping, abandoned

[jerrylamos]

Wily apt-get update, apt-get dist-upgrade Sept 11, 2015
rebooted got this bug

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu Wily Werewolf (development branch)"
Linux Aspire-5253 4.2.0-7-generic #7-Ubuntu SMP Tue Sep 1 16:43:10 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
model name  : AMD E-350 Processor
model name  : AMD E-350 Processor
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Wrestler [Radeon HD 6310]

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

Title:
  package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: triggers
  looping, abandoned

Status in fontconfig package in Ubuntu:
  Won't Fix

Bug description:
  Failed on update

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fontconfig 2.11.1-0ubuntu6
  Uname: Linux 3.18.3-031803-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Tue Feb 10 18:51:02 2015
  DuplicateSignature: package:fontconfig:2.11.1-0ubuntu6:triggers looping, 
abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-01-24 (17 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150124)
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1491732] Re: AalMediaPlaylistProvider::mediaCount locked UI over a dbus call

[Jim Hodapp]

Give silo 47 a try. I have what should be a fix but I wasn't ever able
to reproduce the issue directly. I refactored mediaCount() to no longer
make a dbus call to retrieve the value so that's why I'm confident this
should fix the issue. Also, make sure that call playlist.clear() when
you start playing a new album in the new music scope. The background
playlist does not have the right context to know when to do this.

** Changed in: qtubuntu-media (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  AalMediaPlaylistProvider::mediaCount locked UI over a dbus call

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Invalid
Status in qtubuntu-media package in Ubuntu:
  Fix Committed

Bug description:
  I was testing with silo 4 playing songs after other songs.

  At some stage the UI froze, backtrace says

  #0  0xb614b4e2 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb5ae3ea0 in socket_do_iteration (transport=0x2be4600, flags=6, 
timeout_milliseconds=) at ../../dbus/dbus-transport-socket.c:1149
  #2  0xb5ae3422 in _dbus_transport_do_iteration (transport=0x2be4600, flags=6, 
timeout_milliseconds=29998) at ../../dbus/dbus-transport.c:1001
  #3  0xb5ad29c8 in _dbus_connection_do_iteration_unlocked 
(connection=0x2e33390, pending=, flags=6, 
timeout_milliseconds=29998) at ../../dbus/dbus-connection.c:1227
  #4  0xb5ad3154 in _dbus_connection_block_pending_call 
(pending=pending@entry=0x3426518) at ../../dbus/dbus-connection.c:2527
  #5  0xb5adf10e in dbus_pending_call_block (pending=pending@entry=0x3426518) 
at ../../dbus/dbus-pending-call.c:741
  #6  0xb5ad34d4 in dbus_connection_send_with_reply_and_block 
(connection=0x2e33390, message=0x97297b80, timeout_milliseconds=3, 
error=0x38484b8) at ../../dbus/dbus-connection.c:3575
  #7  0xb3aca8cc in 
core::dbus::Bus::send_with_reply_and_block_for_at_most(std::shared_ptr
 const&, std::chrono::duration > const&) () 
from /usr/lib/arm-linux-gnueabihf/libdbus-cpp.so.4
  #8  0x99d7093c in 
core::dbus::Object::invoke_method_synchronously >, std::string, std::string> (this=)
  at /usr/include/core/dbus/impl/object.h:82
  #9  0x99d70aee in 
core::dbus::Property::get 
(this=0x2b11fd0) at /usr/include/core/dbus/impl/property.h:31
  #10 0x99dcc6a6 in operator-> (this=0x2b11fd0) at 
/usr/include/core/property.h:110
  #11 AalMediaPlaylistProvider::mediaCount (this=) at 
aalmediaplaylistprovider.cpp:58
  #12 0x99dcd8ce in AalMediaPlaylistProvider::media (this=0x2cc08f8, index=7) 
at aalmediaplaylistprovider.cpp:68
  #13 0xae6eef50 in QMediaPlaylist::currentMedia() const () from 
/usr/lib/arm-linux-gnueabihf/libQt5Multimedia.so.5
  #14 0xae7439d6 in QDeclarativePlaylist::currentSource 
(this=this@entry=0x32d2130) at qdeclarativeplaylist.cpp:259
  #15 0xae7449ce in QDeclarativePlaylist::qt_metacall (this=0x32d2130, 
_c=, _id=1, _a=0xbeb0423c) at 
.moc/moc_qdeclarativeplaylist_p.cpp:577
  #16 0xb6ac6f28 in QV4::QObjectWrapper::getProperty(QObject*, 
QV4::ExecutionContext*, QQmlPropertyData*, bool) () from 
/usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
  #17 0xb6ac716c in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionContext*, 
QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) 
() from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
  #18 0xb6ac72ca in QV4::QObjectWrapper::get(QV4::Managed*, QV4::String*, 
bool*) () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5
  #19 0xb6ad0b3e in QV4::Runtime::getProperty(QV4::ExecutionContext*, 
QV4::ValueRef, QV4::String*) () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5

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

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

[Touch-packages] [Bug 1421249] Re: bluetooth can not be enabled sometimes (when booting with flight mode on being one case)

[Jamie Strandboge]

@Sam, that wasn't how I remembered it, but I tried as you said. Disabled
bluetooth, reboot. Enable bluetooth. It worked. I then disabled and
enabled again and it works.

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

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1278780] Re: apport takes too long to write crash report, appears to lock up phone

[Launchpad Bug Tracker]

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

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

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

Title:
  apport takes too long to write crash report, appears to lock up phone

Status in Apport:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in apport package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed

Bug description:
  I can trigger a crash easily on my phone via bug 1262711. Other bugs
  are available.

  When that happens my phone appears to freeze. I am unable to do
  anything for approximately 1 to 1.5 minutes. As a user my initial gut
  reaction is to reboot the phone, thus losing the crash report, and
  wasting my time.

  Having the phone lock up for 1.5 minutes is a terrible user
  experience. Can we fix/mitigate/workaround that?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.13.2-0ubuntu2
  Uname: Linux 3.4.0-3-mako armv7l
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: armhf
  CrashReports:
   664:32011:110:10083:2014-02-10 15:41:18.152893384 +:2014-02-10 
15:11:09.169231740 
+:/var/crash/_usr_lib_arm-linux-gnueabihf_upstart-app-launch_desktop-hook.32011.crash
   640:0:110:1681527:2014-02-10 15:12:10.985193887 +:2014-02-10 
15:12:05.639489630 +:/var/crash/_usr_bin_powerd.0.crash
   640:0:110:21384:2014-02-11 07:58:44.876281991 +:2014-02-11 
07:58:44.876281991 +:/var/crash/_usr_sbin_system-image-dbus.0.crash
   640:32011:110:17122318:2014-02-11 09:19:49.915478726 +:2014-02-11 
09:18:20.850439824 +:/var/crash/_usr_bin_unity8.32011.crash
  Date: Tue Feb 11 09:20:15 2014
  InstallationDate: Installed on 2014-02-11 (0 days ago)
  InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140211)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS or call notification

[Pat McGowan]

** Description changed:

  RC proposed MX4 r100
  
  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed
  
- Adding incoming calls as also triggering the issue
+ Adding incoming calls as also suspected to be triggering the issue
+ 
+ Note this has been impossible to reproduce, and in use only happens very
+ rarely

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

Title:
  Shell not responsive after an incoming SMS or call notification

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  In Progress

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

  Adding incoming calls as also suspected to be triggering the issue

  Note this has been impossible to reproduce, and in use only happens
  very rarely

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

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

[Touch-packages] [Bug 1494909] Re: package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to stat `./usr/share/doc/libuuid1/copyright' (which I was about to install): Input/output error

[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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1494909

Title:
  package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to
  stat `./usr/share/doc/libuuid1/copyright' (which I was about to
  install): Input/output error

Status in util-linux package in Ubuntu:
  New

Bug description:
  SO linux ubuntu 15.4 64-bit

  Não sei a real causa de erro mas sei que o ubuntu mostrou varis
  mensagem de erros diferente e eu não consigo reparar o erros do
  netbeans 8.0.2 que esta tendo problema com o java 8 e o
  GlassFish_Server também não esta funcionado corretamente.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libuuid1 2.25.2-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  Date: Fri Sep 11 12:51:08 2015
  DuplicateSignature: package:libuuid1:2.25.2-4ubuntu3:unable to stat 
`./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
  ErrorMessage: unable to stat `./usr/share/doc/libuuid1/copyright' (which I 
was about to install): Input/output error
  InstallationDate: Installed on 2015-08-17 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: util-linux
  Title: package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to 
stat `./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1494909] [NEW] package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to stat `./usr/share/doc/libuuid1/copyright' (which I was about to install): Input/output error

[Santiago]

Public bug reported:

SO linux ubuntu 15.4 64-bit

Não sei a real causa de erro mas sei que o ubuntu mostrou varis mensagem
de erros diferente e eu não consigo reparar o erros do netbeans 8.0.2
que esta tendo problema com o java 8 e o GlassFish_Server também não
esta funcionado corretamente.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libuuid1 2.25.2-4ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
Date: Fri Sep 11 12:51:08 2015
DuplicateSignature: package:libuuid1:2.25.2-4ubuntu3:unable to stat 
`./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
ErrorMessage: unable to stat `./usr/share/doc/libuuid1/copyright' (which I was 
about to install): Input/output error
InstallationDate: Installed on 2015-08-17 (24 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: util-linux
Title: package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to 
stat `./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

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

Title:
  package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to
  stat `./usr/share/doc/libuuid1/copyright' (which I was about to
  install): Input/output error

Status in util-linux package in Ubuntu:
  New

Bug description:
  SO linux ubuntu 15.4 64-bit

  Não sei a real causa de erro mas sei que o ubuntu mostrou varis
  mensagem de erros diferente e eu não consigo reparar o erros do
  netbeans 8.0.2 que esta tendo problema com o java 8 e o
  GlassFish_Server também não esta funcionado corretamente.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: libuuid1 2.25.2-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  Date: Fri Sep 11 12:51:08 2015
  DuplicateSignature: package:libuuid1:2.25.2-4ubuntu3:unable to stat 
`./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
  ErrorMessage: unable to stat `./usr/share/doc/libuuid1/copyright' (which I 
was about to install): Input/output error
  InstallationDate: Installed on 2015-08-17 (24 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: util-linux
  Title: package libuuid1 2.25.2-4ubuntu3 failed to install/upgrade: unable to 
stat `./usr/share/doc/libuuid1/copyright' (which I was about to install): 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1421249] bluetooth can not be enabled sometimes (whenbooting with flight mode on being one case)

[Sam Bull]

That's excellent news. Looking forward to this landing in an OTA.

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

Title:
  bluetooth can not be enabled sometimes (when booting with flight mode
  on being one case)

Status in Canonical System Image:
  New
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  The bluetooth indicator and the bluetooth page in system settings
  sometimes won't turn on bluetooth until after a reboot. What I expect
  to happen is that if bluetooth is off in the indicator/system settings
  and I tap the switch, the switch will go green and in a moment the
  bluetooth indicator will show up and bluetooth is enabled. When
  bluetooth is on, I expect to go into the indicator/system settings and
  turn the switch off, the switch will go gray and the bluetooth
  indicator will hide and bluetooth is disabled. I expect this to work
  whenever I want while the phone is on.

  Sometimes, this does not work. For example, yesterday I disabled
  bluetooth at some point in the evening and later I went to sleep. When
  I woke up, I tried to turn it on via the indicator and also system
  settings and it wouldn't turn on. In the indicator, the switch moves
  to the green position briefly, then moves back to gray (the bluetooth
  indicator remains hidden and bluetooth is disabled). In system
  settings, the switch will stay green, but the bluetooth indicator
  remains hidden and bluetooth is disabled. If I leave system settings
  and come back, the the switch is now in the off position.

  /var/lib/urfkill/saved-states has:
  [BLUETOOTH]
  soft=false
  prev-soft=false

  bluetoothd is confirmed to be running before and after using the
  indicator and system settings when bluetooth cannot be enabled.

  Workaround: reboot the phone and bluetooth will be enabled.

  Note: this is not new behavior-- I'm only reporting it now (partly
  because I thought it was fixed for a while, but that might have been
  because I was rebooting a lot at the time)

  $ system-image-cli -i
  current build number: 194
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-11 15:34:27
  version version: 194
  version ubuntu: 20150211.1
  version device: 20150116
  version custom: mako-1.1

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

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

[Touch-packages] [Bug 1494942] [NEW] package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Majestyx]

Public bug reported:

i only make updates via synaptic

Description:Ubuntu 15.04
Release:15.04

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1.4
ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
Uname: Linux 3.19.0-28-generic x86_64
ApportLog:
 
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CrashReports: 600:0:118:97542:2015-09-11 23:15:07.408001422 +0200:2015-09-11 
23:15:08.408001422 +0200:/var/crash/apport.0.crash
Date: Fri Sep 11 23:15:08 2015
DuplicateSignature: package:apport:2.17.2-0ubuntu1.4:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
InstallationDate: Installed on 2015-08-15 (27 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: apport
Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

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

Title:
  package apport 2.17.2-0ubuntu1.4 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in apport package in Ubuntu:
  New

Bug description:
  i only make updates via synaptic

  Description:  Ubuntu 15.04
  Release:  15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.4
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportLog:
   
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CrashReports: 600:0:118:97542:2015-09-11 23:15:07.408001422 +0200:2015-09-11 
23:15:08.408001422 +0200:/var/crash/apport.0.crash
  Date: Fri Sep 11 23:15:08 2015
  DuplicateSignature: package:apport:2.17.2-0ubuntu1.4:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2015-08-15 (27 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: apport
  Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1494946] [NEW] systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()

[Till Kamppeter]

Public bug reported:

Happens only on QEMU-based virtual machine.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 11 07:48:25 2015
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2015-03-25 (170 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-journald
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 __libc_start_main (main=0x55c6561b0440, argc=1, argv=0x7ffd11e0af48, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd11e0af38) at libc-start.c:289
 ?? ()
Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.7.5-20150306_163512-brownie
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-utopic
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-utopic
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-crash need-amd64-retrace wily

** Information type changed from Private to Public

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

Title:
  systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  Happens only on QEMU-based virtual machine.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Sep 11 07:48:25 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-03-25 (170 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x55c6561b0440, argc=1, argv=0x7ffd11e0af48, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd11e0af38) at libc-start.c:289
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __epoll_wait_nocancel()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20150306_163512-brownie
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-utopic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-utopic
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1494942] Re: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1494942

Title:
  package apport 2.17.2-0ubuntu1.4 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in apport package in Ubuntu:
  New

Bug description:
  i only make updates via synaptic

  Description:  Ubuntu 15.04
  Release:  15.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.4
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportLog:
   
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  CrashReports: 600:0:118:97542:2015-09-11 23:15:07.408001422 +0200:2015-09-11 
23:15:08.408001422 +0200:/var/crash/apport.0.crash
  Date: Fri Sep 11 23:15:08 2015
  DuplicateSignature: package:apport:2.17.2-0ubuntu1.4:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2015-08-15 (27 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: apport
  Title: package apport 2.17.2-0ubuntu1.4 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1494954] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Till Kamppeter]

Public bug reported:

Only occurs on QEMU-based virtual machine.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: udev 225-1ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CustomUdevRuleFiles: 80-net-setup-link.rules
Date: Fri Sep 11 16:25:31 2015
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2015-03-25 (170 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcCmdline: /lib/systemd/systemd-udevd
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x5624e58a7870, argc=1, argv=0x7ffdb7ca9ef8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdb7ca9ee8) at libc-start.c:289
Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.7.5-20150306_163512-brownie
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-utopic
dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-utopic
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-crash need-amd64-retrace wily

** Information type changed from Private to Public

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  Only occurs on QEMU-based virtual machine.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: udev 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Fri Sep 11 16:25:31 2015
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-03-25 (170 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5624e58a7870, argc=1, argv=0x7ffdb7ca9ef8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdb7ca9ee8) at libc-start.c:289
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20150306_163512-brownie
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-utopic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-utopic
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1494965] Re: add-apt-repository crashed with IndexError in mangle_ppa_shortcut(): string index out of range

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

Title:
  add-apt-repository crashed with IndexError in mangle_ppa_shortcut():
  string index out of range

Status in software-properties package in Ubuntu:
  New

Bug description:
  error appears immeditely after login

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: software-properties-common 0.96.10
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 11 22:58:18 2015
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository 
ppa::synapse-core/ppa
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   LANGUAGE=it
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa::synapse-core/ppa']
  SourcePackage: software-properties
  Title: add-apt-repository crashed with IndexError in mangle_ppa_shortcut(): 
string index out of range
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1494965/+subscriptions

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

[Touch-packages] [Bug 1494965] [NEW] add-apt-repository crashed with IndexError in mangle_ppa_shortcut(): string index out of range

[g. pellegrino]

Public bug reported:

error appears immeditely after login

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: software-properties-common 0.96.10
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Fri Sep 11 22:58:18 2015
ExecutablePath: /usr/bin/add-apt-repository
InstallationDate: Installed on 2015-09-11 (0 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
InterpreterPath: /usr/bin/python3.4
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa::synapse-core/ppa
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 LANGUAGE=it
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/add-apt-repository', 'ppa::synapse-core/ppa']
SourcePackage: software-properties
Title: add-apt-repository crashed with IndexError in mangle_ppa_shortcut(): 
string index out of range
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash wily

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with IndexError in mangle_ppa_shortcut():
  string index out of range

Status in software-properties package in Ubuntu:
  New

Bug description:
  error appears immeditely after login

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: software-properties-common 0.96.10
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 11 22:58:18 2015
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  InterpreterPath: /usr/bin/python3.4
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository 
ppa::synapse-core/ppa
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   LANGUAGE=it
   SHELL=/bin/bash
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa::synapse-core/ppa']
  SourcePackage: software-properties
  Title: add-apt-repository crashed with IndexError in mangle_ppa_shortcut(): 
string index out of range
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1494965/+subscriptions

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

[Touch-packages] [Bug 1460626] Re: Unity Lockscreen still shows unlocked desktop while shutting down

[Launchpad Bug Tracker]

This bug was fixed in the package unity -
7.3.2+15.10.20150910.1-0ubuntu1

---
unity (7.3.2+15.10.20150910.1-0ubuntu1) wily; urgency=medium

  [ Andrea Azzarone andrea.azzar...@canonical.com ]
  * Add unit tests for unity::lockscreen::DBusManager.
  * Add/Update tests for gnome session manager.
  * Do not allow shutdown when screen is locked. (LP: #1460626)
  * Make sure we update the maximized window when "show
desktop"/"restore desktop". (LP: #1485559)
  * Merge patch from https://launchpadlibrarian.net/216192448/llvm-
fix.patch (LP: #1491555)
  * Merge patch from https://launchpadlibrarian.net/216276242/low-gfx-
override.patch (LP: #1491913)

  [ Andrea Azzarone azzaro...@gmail.com ]
  * Properly hide decorations when on "Show Desktop" mode. (LP:
#1485073)

  [ Marco Trevisan (Treviño) ]
  * UnityScreen: force shell to be on top when there's a window
fullscreen and we've a menu open. (LP: #591189)

 -- Marco Trevisan (Treviño)   Thu, 10 Sep 2015 15:37:46
+

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

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

Title:
  Unity Lockscreen still shows unlocked desktop while shutting down

Status in Unity:
  In Progress
Status in indicator-session package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  This was reported and supposedly fixed in
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370017, but the
  bug is still present in the current Unity version in Trusty.  I've
  reported it in that bug already, but got ignored, so I'm opening a new
  bug about it.

  [Impact and Test Case]

  Steps to reproduce:
  1 - Log into Unity
  2 - Open a terminal.
  3 - Lock the screen
  4 - From the lockscreen, tell the computer to shut down / restart

  Expected behavior:
  * Session programs are closed while the screen is still locked
  * During shutdown, no user interaction is possible

  Observed behavior:
  * The lockscreen is gone immediately, with the rest of compiz (e.g. window 
decorations are not present)
  * But it's possible to interact with programs that are still running in the 
session for about 3 seconds

  Observed on an updated Trusty machine, running unity version
  7.2.5+14.04.20150521.1-0ubuntu1

  This bug is a security vulnerability because during those 3 seconds it
  could be possible to access and interact with sensitive information.
  Yes, it's short, but you could take a picture or even rm -rf / if
  there happened to be a root console available.

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

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

[Touch-packages] [Bug 1486008] Re: [sdk] leading actions width is too small making it very difficult to press

[Michael Sheldon]

I think I've tracked down the problem here, the size change is
misleading, whether pressing a leading/trailing action is successful or
not is actually determined by the speed with which you press and release
it.

This is because the hiding animation starts when the area is pressed,
but the action is only triggered on release. Due to a quirk in QML's
mouse areas release event don't get emitted if the finger is no longer
inside the relevant mouse area when the release happens (in this case
caused to the mouse area having been moved by the hiding animation). So
the release event is never emitted and the action isn't triggered.

The size only has an effect in that a larger area gives you a slightly
longer duration in which you can release your finger and have it
register.

I did a quick test to confirm this by triggering the action based on the
pressed property changing and the leading/trailing action buttons became
instantly much more usable. I think the correct solution however would
be to have the hide animation start when the user releases their finger
instead of on the initial press event (but I'm not familiar enough with
the ListItemStyle implementation to do that quickly myself)

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

Title:
  [sdk] leading actions width is too small making it very difficult to
  press

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

Bug description:
  Since a recent update to the ListItem leading actions in
  Ubuntu.Components 1.2, where the width of the action was clamped, the
  width is too small to press comfortably on a phone resulting in it
  missing 9 out of 10 tries. It affects the usability of the action and
  may be become a release blocker for apps that have recently switched
  over to the new list items.

  Sample App

  import QtQuick 2.4
  import Ubuntu.Components 1.2

  MainView {
  applicationName: "testdelete.nik90"
  width: units.gu(100)
  height: units.gu(75)

  Page {
  title: "Swipe to Delete"
  ListItem {
  id: listItem
  anchors.top: parent.top

  Label {
  text: "Swipe me right to delete this listitem"
  wrapMode: Text.WordWrap
  anchors { left: parent.left; leftMargin: units.gu(2); right: 
parent.right; verticalCenter: parent.verticalCenter }
  }

  leadingActions: ListItemActions {
  actions: [
  Action {
  iconName: "delete"
  onTriggered: listItem.destroy()
  }
  ]
  }
  }
  }
  }

  With trailing actions, tapping the trailingActions first causes the
  ListItem to jump/scroll all the way to the left instead of actually
  activating the action. Only a second tap actually activates them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1486008/+subscriptions

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

[Touch-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)

[Christian Pointner]

** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic-
mute

** Branch unlinked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-
mic-mute

** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic-
mute

** Branch unlinked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-
mic-mute

** Branch linked: lp:~equinox-i/xfce4-volumed-pulse/add-support-for-mic-
mute

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

Title:
  Does not handle microphone mute button (KEY_MICMUTE)

Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in OEM Priority Project raring series:
  Won't Fix
Status in xkeyboard-config:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in libx11 package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Fix Released
Status in x11proto-core package in Ubuntu:
  New
Status in xfce4-volumed package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Won't Fix
Status in gnome-settings-daemon source package in Precise:
  Fix Released
Status in libx11 source package in Precise:
  Fix Released
Status in udev source package in Precise:
  Fix Released
Status in x11proto-core source package in Precise:
  Fix Released
Status in xfce4-volumed source package in Precise:
  New
Status in xkeyboard-config source package in Precise:
  Fix Released
Status in xserver-xorg-input-evdev source package in Precise:
  Won't Fix
Status in x11proto-core source package in Raring:
  Won't Fix
Status in xserver-xorg-input-evdev source package in Raring:
  Won't Fix

Bug description:
  [Impact] 
   * People buying thinkpad hardware are not able to use a mic mute key, that 
comes with 
 their machine

  [Test Case]

   * Press mic mute key
   * Observe that nothing happens

  [Regression Potential]

   * Very low. This is very isolated code. All it does is add functionality. In 
fact there 
 are very few deletions in the diffs.

   * There is an existing acpi solution, that's already been mentioned in this 
bug. I'm 
 not sure how these users would be affected once the upgrade hits, but it 
was never 
 released as an official fix.

  [Original Report]

  Pressing the new microphone mute button does not do anything.  It
  should toggle the mute on the current capture device and toggle an led
  that is part of the button.

  acpi_listen output:

  ibm/hotkey HKEY 0080 101b

  xev output:

  MappingNotify event, serial 34, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 248

  MappingNotify event, serial 34, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 247

  KeyPress event, serial 34, synthetic NO, window 0x341,
  root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 34, synthetic NO, window 0x341,
  root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions

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

[Touch-packages] [Bug 1494952] StacktraceSource.txt

[Apport retracing service]

** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1494952/+attachment/4461790/+files/StacktraceSource.txt

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

Title:
  systemd-timesyncd crashed with SIGABRT in epoll_wait()

Status in systemd package in Ubuntu:
  New

Bug description:
  Only occurs on QEMU-based virtual machine.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 10 22:52:55 2015
  ExecutablePath: /lib/systemd/systemd-timesyncd
  InstallationDate: Installed on 2015-03-25 (170 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-timesyncd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   epoll_wait () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x55b565b91f70, argc=1, argv=0x7ffd518bfc98, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd518bfc88) at libc-start.c:289
   ?? ()
  Title: systemd-timesyncd crashed with SIGABRT in epoll_wait()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20150306_163512-brownie
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-utopic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-utopic
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1494952] Stacktrace.txt

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1494952/+attachment/4461789/+files/Stacktrace.txt

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

Title:
  systemd-timesyncd crashed with SIGABRT in epoll_wait()

Status in systemd package in Ubuntu:
  New

Bug description:
  Only occurs on QEMU-based virtual machine.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 10 22:52:55 2015
  ExecutablePath: /lib/systemd/systemd-timesyncd
  InstallationDate: Installed on 2015-03-25 (170 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-timesyncd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   epoll_wait () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x55b565b91f70, argc=1, argv=0x7ffd518bfc98, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd518bfc88) at libc-start.c:289
   ?? ()
  Title: systemd-timesyncd crashed with SIGABRT in epoll_wait()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20150306_163512-brownie
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-utopic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-utopic
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1494952] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1494952/+attachment/4461791/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

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

Title:
  systemd-timesyncd crashed with SIGABRT in epoll_wait()

Status in systemd package in Ubuntu:
  New

Bug description:
  Only occurs on QEMU-based virtual machine.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 10 22:52:55 2015
  ExecutablePath: /lib/systemd/systemd-timesyncd
  InstallationDate: Installed on 2015-03-25 (170 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-timesyncd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   epoll_wait () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x55b565b91f70, argc=1, argv=0x7ffd518bfc98, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd518bfc88) at libc-start.c:289
   ?? ()
  Title: systemd-timesyncd crashed with SIGABRT in epoll_wait()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20150306_163512-brownie
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-utopic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-utopic
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1494986] [NEW] /usr/bin/messaging-app:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadInteg

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding messaging-app.  This problem was most recently seen with
version 0.1+15.10.20150818-0ubuntu1messagingframework2, the problem page
at
https://errors.ubuntu.com/problem/2583cf9112440eb9288a9557ccf91d88d2acd551
contains more details.

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


** Tags: utopic vivid wily

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

Title:
  /usr/bin/messaging-
  
app:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration

Status in messaging-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding messaging-app.  This problem was most recently seen with
  version 0.1+15.10.20150818-0ubuntu1messagingframework2, the problem
  page at
  https://errors.ubuntu.com/problem/2583cf9112440eb9288a9557ccf91d88d2acd551
  contains more details.

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

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

[Touch-packages] [Bug 1494929] Re: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame()

Status in tracker package in Ubuntu:
  New

Bug description:
  New install gnome beta ubuntu.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: tracker-extract 1.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Sep 11 09:02:53 2015
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-09-09 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 
(20150826.1)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f97d837156d:mov%r13,0x48(%rax)
   PC (0x7f97d837156d) ok
   source "%r13" ok
   destination "0x48(%rax)" (0x0048) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from 
/usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0
  Title: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1494954]

[Apport retracing service]

StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
 sd_event_wait (e=e@entry=0x5624e5cbcc90, 
timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:2373
 sd_event_run (timeout=18446744073709551615, e=0x5624e5cbcc90) at 
../src/libsystemd/sd-event/sd-event.c:2496
 sd_event_loop (e=0x5624e5cbcc90) at ../src/libsystemd/sd-event/sd-event.c:2520
 run (cgroup=, fd_uevent=, fd_ctrl=) at ../src/udev/udevd.c:1625

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

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  Only occurs on QEMU-based virtual machine.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: udev 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Fri Sep 11 16:25:31 2015
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2015-03-25 (170 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5624e58a7870, argc=1, argv=0x7ffdb7ca9ef8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdb7ca9ee8) at libc-start.c:289
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.7.5-20150306_163512-brownie
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-utopic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.7.5-20150306_163512-brownie:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-utopic:cvnQEMU:ct1:cvrpc-i440fx-utopic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-utopic
  dmi.sys.vendor: QEMU

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

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