date:20151014

** Attachment added: "lspci-vv"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494447/+files/lspci-vv

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

Title:
  Unreadable display

Status in xorg package in Ubuntu:
  New

Bug description:
  It appears the Xserver version in wily is older than the version in
  Debian Jessie and is buggy.

  Given how hard it is to read, iI'll post further comment after I
  reboot this old dual bot laptop into Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 14 09:03:50 2015
  InstallationDate: Installed on 2014-08-28 (412 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago)

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

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

[Touch-packages] [Bug 1270639] Re: time stays in 12 hr display in 12.04

Could you try with a newest version to see if that's still an issue?

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Low

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Incomplete

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

Title:
  time stays in 12 hr display in 12.04

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  I use ubuntu 12.04 and the display in the tool-bar stays on 12 hr
  (am/pm) notation after I change it in the settings (right click on
  clock and open the time settings)

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

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

[Touch-packages] [Bug 1506045] Re: FTBFS on amd64, armhf and i386 due to missing headers

2015-10-14 Thread Łukasz Zemczak

Ok, checking the changelog and changes in 0.16.1+15.10.20150930.1 it
seems there's only 2 bugfixes inside - one for the build failure and one
for a bug. I would recommend we copy-package this to the wily archive,
possibly as a binary-copy (since I think mir deps in overlay should be
the same as in the archive).

For interested, here's the changeset of 0.16.1+15.10.20150930.1:
http://bazaar.launchpad.net/~mir-team/mir/ubuntu/revision/1245

Could anyone copy mir 0.16.1+15.10.20150930.1 from https://launchpad.net
/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay to the
archive? Thanks!

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

Title:
  FTBFS on amd64, armhf and i386 due to missing headers

Status in Mir:
  New
Status in mir package in Ubuntu:
  In Progress

Bug description:
  As per the test-rebuild of wily [1] the mir package seems to fail on
  amd64, armhf and i386 due to the following error:

  [ 14%] Building CXX object 
src/platforms/mesa/server/kms/CMakeFiles/mirplatformgraphicsmesakmsobjects.dir/linux_virtual_terminal.cpp.o
  cd 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/obj-x86_64-linux-gnu/src/platforms/mesa/server/kms
 && /usr/bin/x86_64-linux-gnu-g++   -DLOG_NDEBUG=1 -DMESA_EGL_NO_X11_HEADERS 
-DMIR_VERSION_MAJOR=0 -DMIR_VERSION_MICRO=0 -DMIR_VERSION_MINOR=16 -D__GBM__ -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing  
-Wnon-virtual-dtor -Wextra -fPIC 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/common 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platforms/mesa 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platform 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/renderers/gl 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/include/common 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/include/platform 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/mesa/server/common 
-I/usr/include/libdrm-o 
CMakeFiles/mirplatformgraphicsmesakmsobjects.dir/linux_virtual_terminal.cpp.o 
-c 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp
  In file included from /usr/include/EGL/egl.h:39:0,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platform/mir/graphics/platform.h:24,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/android/server/platform.h:22,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/android/server/platform.cpp:20:
  /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: 
No such file or directory
  compilation terminated.

  [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
  rebuild-20151001-wily.html#core

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

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

[Touch-packages] [Bug 1302004] Re: Indicator-datetime doesn't list in-progress events

@Charles, is the patch there still something that needs review?

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

Title:
  Indicator-datetime doesn't list in-progress events

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  This bug is related to this bug: Bug #1293646 (Which is marked as fix
  released)

  With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it
  lists all events for all past selected dates properly (which was fixed
  in bug Bug #1293646) except today's date. When I click on any past
  date in calendar it shows:

  1. all all-day events for the day.
  2. all events with time for the day
  3. upcoming (future) all-day events
  4. upcoming (future) events with time

  But when I click on today's date it only shows:

  1. future all day events
  2. future events with time

  I still have to click on previous day's date to find out all all-day
  events for today.

  The behavior (showing all events for a day) should be same for any
  date, including today's date.

  : "If there are more
  than five, the events shown should be, in order of priority, * any
  events that start or end (a) for today, after the current minute, or
  (b) for any other date, at any time on that date, * any full-day
  events that span all of the selected date..."

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

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

[Touch-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe

2015-10-14 Thread Mathieu Trudel-Lapierre

Just committed the patch in the NM packaging branch; will upload
soonish.

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

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

Title:
  network-manager configured to use /usr/sbin/pppoe but does not
  recommend pppoe

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager package in Debian:
  New

Bug description:
  networkmanager switched from using ppp to using pppoe binary for
  dsl/pppoe connections, I am using pppoe and I can't connect to the
  Internet unless I install "pppoe" package.

  From:
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10=7955806a02db64b20079267743056d7d9d45af3b

  "for now, work around this by using the userland pppoe client rather
  than the kernel code"

  One way to fix it is to include pppoe
  Another way is to configure --with-pppoe=/usr/sbin/pppd.

  I think this is urgent as pppoe/dsl on all vivid machines will be
  broken out-of-the-box.

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

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

[Touch-packages] [Bug 1308037] Re: No results from application scope

2015-10-14 Thread Iain Lane

I'm unduping this - bug #1295908 says that there are two ways to fix
(try again or check 'applications' in the filters list). This bug is
about being in a state where neither of these cases work - apps are
never returned until unity is restarted.

I got it once again a couple of weeks ago but I forgot to try that apps
lens (comment #6), sorry - will try to remember next time.

** This bug is no longer a duplicate of bug 1295908
   Sometimes applications stop showing up in the Dash

** Summary changed:

- No results from application scope
+ No results from application scope until Unity is restarted

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

Title:
  No results from application scope until Unity is restarted

Status in libunity:
  Invalid
Status in Unity:
  Confirmed
Status in unity-lens-applications:
  Invalid
Status in libunity package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Unity is in a state where I don't get any results from the
  applications lens. This sometimes happens for one search but either
  re-entering the search or toggling the lens has always fixed it in the
  past for me. This time neither of these steps work.

  I'm attaching a bustle log of the problem in case that's helpful. I
  searched for "spotify", which I've got installed, and got 0 results.

  The only way to fix the issue is to log out and back in.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 13:29:40 2014
  InstallationDate: Installed on 2012-10-07 (554 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago)

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

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

[Touch-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe

2015-10-14 Thread Mathieu Trudel-Lapierre

Triaged/High; since this affects some users who connect directly through
PPPoE. While this may be a relatively low number of people, it's
crippling if they cannot retrieve pppoe after the fact due to no
network...

This simply needs a cherry-pick of
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=6fdfb03107138e96e641d12a7c4df5ecfacb5406,
which reverts changes that unfortunately landed in vivid too; so should
be SRU'd.

As an added benefit, with this patch it is unnecessary to install the
pppoe package, everything is handled directly by pppd.


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

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

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

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

Title:
  network-manager configured to use /usr/sbin/pppoe but does not
  recommend pppoe

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager package in Debian:
  New

Bug description:
  networkmanager switched from using ppp to using pppoe binary for
  dsl/pppoe connections, I am using pppoe and I can't connect to the
  Internet unless I install "pppoe" package.

  From:
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10=7955806a02db64b20079267743056d7d9d45af3b

  "for now, work around this by using the userland pppoe client rather
  than the kernel code"

  One way to fix it is to include pppoe
  Another way is to configure --with-pppoe=/usr/sbin/pppd.

  I think this is urgent as pppoe/dsl on all vivid machines will be
  broken out-of-the-box.

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

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

[Touch-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"

2015-10-14 Thread A

And then this happened today...

apb@orange:~$ sudo apt-get upgrade
[sudo] password for apb: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  adobe-flash-properties-gtk adobe-flashplugin gir1.2-gdkpixbuf-2.0
  google-chrome-stable libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0:i386
  libgdk-pixbuf2.0-common
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 57.5 MB of archives.
After this operation, 2,476 kB disk space will be freed.
Do you want to continue? [Y/n] 
Get:1 http://dl.google.com/linux/chrome/deb/ stable/main google-chrome-stable 
amd64 46.0.2490.71-1 [47.0 MB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main 
libgdk-pixbuf2.0-0 amd64 2.30.7-0ubuntu1.2 [160 kB]
Get:3 http://archive.canonical.com/ubuntu/ trusty/partner 
adobe-flash-properties-gtk amd64 1:20151013.1-0trusty1 [113 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main 
libgdk-pixbuf2.0-0 i386 2.30.7-0ubuntu1.2 [156 kB]
Get:5 http://archive.canonical.com/ubuntu/ trusty/partner adobe-flashplugin 
amd64 1:20151013.1-0trusty1 [10.1 MB]
Get:6 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main 
libgdk-pixbuf2.0-common all 2.30.7-0ubuntu1.2 [8,826 B]
Get:7 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main 
gir1.2-gdkpixbuf-2.0 amd64 2.30.7-0ubuntu1.2 [7,964 B]
Fetched 57.5 MB in 33s (1,715 kB/s)
(Reading database ... 170352 files and directories currently installed.)
Preparing to unpack .../libgdk-pixbuf2.0-0_2.30.7-0ubuntu1.2_i386.deb ...
De-configuring libgdk-pixbuf2.0-0:amd64 (2.30.7-0ubuntu1.1) ...
Unpacking libgdk-pixbuf2.0-0:i386 (2.30.7-0ubuntu1.2) over (2.30.7-0ubuntu1.1) 
...
Preparing to unpack .../libgdk-pixbuf2.0-0_2.30.7-0ubuntu1.2_amd64.deb ...
Unpacking libgdk-pixbuf2.0-0:amd64 (2.30.7-0ubuntu1.2) over (2.30.7-0ubuntu1.1) 
...
Preparing to unpack .../libgdk-pixbuf2.0-common_2.30.7-0ubuntu1.2_all.deb ...
Unpacking libgdk-pixbuf2.0-common (2.30.7-0ubuntu1.2) over (2.30.7-0ubuntu1.1) 
...
Preparing to unpack .../google-chrome-stable_46.0.2490.71-1_amd64.deb ...
Unpacking google-chrome-stable (46.0.2490.71-1) over (45.0.2454.101-1) ...
Preparing to unpack 
.../adobe-flash-properties-gtk_1%3a20151013.1-0trusty1_amd64.deb ...
Unpacking adobe-flash-properties-gtk (1:20151013.1-0trusty1) over 
(1:20150921.1-0trusty1) ...
Preparing to unpack .../adobe-flashplugin_1%3a20151013.1-0trusty1_amd64.deb ...
Unpacking adobe-flashplugin (1:20151013.1-0trusty1) over 
(1:20150921.1-0trusty1) ...
Preparing to unpack .../gir1.2-gdkpixbuf-2.0_2.30.7-0ubuntu1.2_amd64.deb ...
Unpacking gir1.2-gdkpixbuf-2.0 (2.30.7-0ubuntu1.2) over (2.30.7-0ubuntu1.1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.13-1) ...

(gtk-update-icon-cache-3.0:14008): GdkPixbuf-WARNING **: Cannot open
pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
Setting up libgdk-pixbuf2.0-common (2.30.7-0ubuntu1.2) ...
Setting up libgdk-pixbuf2.0-0:amd64 (2.30.7-0ubuntu1.2) ...
Setting up libgdk-pixbuf2.0-0:i386 (2.30.7-0ubuntu1.2) ...
Setting up google-chrome-stable (46.0.2490.71-1) ...
Setting up adobe-flashplugin (1:20151013.1-0trusty1) ...
update-alternatives: using /usr/lib/adobe-flashplugin/libflashplayer.so to 
provide /usr/lib/mozilla/plugins/flashplugin-alternative.so 
(mozilla-flashplugin) in auto mode
Setting up adobe-flash-properties-gtk (1:20151013.1-0trusty1) ...
Setting up gir1.2-gdkpixbuf-2.0 (2.30.7-0ubuntu1.2) ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
apb@orange:~$ gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission 
denied
apb@orange:~$ sudo !!
sudo gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission 
denied
apb@orange:~$ ll /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
-rw-r--r-- 1 root root 4317 Oct 14 07:08 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
apb@orange:~$ date
Wed Oct 14 07:09:38 PDT 2015
apb@orange:~$ sudo gdk-pixbuf-query-loaders
sudo: gdk-pixbuf-query-loaders: command not found
apb@orange:~$ 
apb@orange:~$ lsb_release
LSB Version:

[Touch-packages] [Bug 1498474] Re: Incorrect MTU on VPN connect

2015-10-14 Thread Mathieu Trudel-Lapierre

Already committed to the n-m packaging branch, will upload shortly.

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Incorrect MTU on VPN connect

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  On update to wily, vpnc vpn connects, but MTU is incorrectly set to
  1500, instead of default value which is 1412.  This results in
  connectivity issues (packet loss).

  Gnomezilla bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=754781

  I have attached the included patch from above for convenience, and
  tested that this indeed resolves the issue for me.

  It might be worth mentioning that I had to disable the built in tests
  (--enable-tests=no), or pakage generation with "debuild -us -uc -b"
  fails on 2 of the tests relating to ipv6.

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

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

[Touch-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe

** Branch linked: lp:~network-manager/network-manager/ubuntu

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

Title:
  network-manager configured to use /usr/sbin/pppoe but does not
  recommend pppoe

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager package in Debian:
  New

Bug description:
  networkmanager switched from using ppp to using pppoe binary for
  dsl/pppoe connections, I am using pppoe and I can't connect to the
  Internet unless I install "pppoe" package.

  From:
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10=7955806a02db64b20079267743056d7d9d45af3b

  "for now, work around this by using the userland pppoe client rather
  than the kernel code"

  One way to fix it is to include pppoe
  Another way is to configure --with-pppoe=/usr/sbin/pppd.

  I think this is urgent as pppoe/dsl on all vivid machines will be
  broken out-of-the-box.

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

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

[Touch-packages] [Bug 1410975] Re: alarm sometimes won't go off untill I turn on the screen

Should be fixed, please open a new bug if you still have issues

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  alarm sometimes won't go off untill I turn on the screen

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Im on a N4 on the RTM devel r13
  I had already noticed that the snooze time, what I set on 5 min, varied 
between 5 and 10 minutes.
  But this morning my alarm should have gone off at 7:22 AM but only went of 
after I woke up and took my phone to check it.
  That was at 8AM

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

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

[Touch-packages] [Bug 1357897] Re: Wrong date abbreviating in Date Indicator

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

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

Title:
  Wrong date abbreviating in Date Indicator

Status in Wingpanel Date & Time Indicator:
  New

Bug description:
  In French with local fr_CH (Switzerland), "août" (august) should not
  be abbreviating. Also, abbreviating must be ended with a dot.

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

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

[Touch-packages] [Bug 1408958] Re: Calendar alarm notifications have no buttons, on screen for short while

** Package changed: indicator-datetime (Ubuntu) => unity8 (Ubuntu)

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

Title:
  Calendar alarm notifications have no buttons, on screen for short
  while

Status in unity8 package in Ubuntu:
  New

Bug description:
  Using krillin #186 from ubuntu-touch/ubuntu-rtm/14.09-proposed
  notifications of calendar events are broken.

  Previously a calendar event with reminder would trigger a notification
  with OK / Snooze buttons, but those buttons are no longer there. In
  addition the notification is very short, so getting a screenshot for
  this bug was challenging!

  Steps to reproduce

  1. Flash krillin with 186
  2. Install Calendar app
  3. Add a calendar entry for sometime soon with a reminder
  4. Wait for the notification

  Expected behaviour

  Notification appears until some arbitrary time out or user clicks a
  button

  Actual behaviour

  Notification appears without buttons, and only for a brief period.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-datetime 13.10.0+15.04.20141210~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Jan  9 09:41:35 2015
  InstallationDate: Installed on 2015-01-08 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150108-030204)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1407997] Re: [calendar] Should be possible to disable reminders per-calendar

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [calendar] Should be possible to disable reminders per-calendar

Status in Ubuntu Calendar App:
  Triaged
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  It is often the case that you want to add a calendar to view it on
  your device, but for it not to trigger reminder events. It might be
  someone else's calendar, for example.

  
  --- --- --- ---
  UX Comment:

  I agree that Kunal's suggestion  to 'add add check box and flag in
  collection to indicate if reminder is enabled for particular calendar
  or not' should be implemented.

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

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

[Touch-packages] [Bug 1432871] Re: `df` shows bind mounts instead of real mounts.

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

** Also affects: coreutils (Ubuntu Vivid)
Importance: Undecided
Status: New

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

Title:
`df` shows bind mounts instead of real mounts.

Status in coreutils package in Ubuntu:
In Progress
Status in coreutils source package in Trusty:
New
Status in coreutils source package in Vivid:
New
Status in coreutils source package in Wily:
In Progress

Bug description:
[Impact]

* df displays bind mounts instead of "real" mounts if the bind mount
is mounted to a shorter directory.

* justification - When trusty moved to using /proc/mounts this
changed behavior from precise. Additionally it doesn't make sense
that a bind mount should show up in df over a real root mount.

* Explanation - These patches change behavior of df to rely on
/proc/self/mountinfo which has more complete info than /proc/mounts.
Such as what directory of the filesystem was used as the source of the
mount. Additionally given this new information there is a patch on df
itself to make use of this new information.

[Test Case]

* $ mount

192.168.1.2:/raid on /raid type nfs
/dev/sdc5 on /data type ext4 (rw)

/data/a on /a type none (rw,bind)
/raid/temp on /b type none (rw,bind)

$df
Filesystem 1K-blocks Used Available Use% Mounted on

/data/a 449830616 229975284 196982196 54% /a
/raid/temp 7752072192 5581343744 1780023296 76% /b

I'd expect to see the real mount prioritized over the bind mount. Like so.
$df
Filesystem 1K-blocks Used Available Use% Mounted on

/dev/sdc5449830616 229975284 196982196 54% /data
192.168.1.2:/raid 7752072192 5581438976 1779929088 76% /raid

[Regression Potential]

* Patch is upstreamed.

* df command now relies on /proc/self/mountinfo

[Other Info]

* The behavior of df, mount and similar number of other commands has
changed going forward. Previously these commands all processed
/etc/mtab which was maintained by the mount command. Going forward
they still process /etc/mtab, but this is simply a symlink to
/proc/mounts now which is maintained by the kernel and slightly more
accurate. Unlike the mount command, the kernel makes no distinction
between bind mounts and normal mounts. This is evident by the fact
that you can mount a device, bind mount from that device, and then
unmount the original mount. The default behavior of df in this case
is to simply pick the mounted directory for a device that is the
shortest since it has no other information to go on from /proc/mounts.
Moving to using /proc/self/mountinfo resolves this issue, and is what
upstream is doing moving forward.

* In order to solve this issue, I have written patches and got them
integrated upstream.
gnulib commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=c6148bca89e9465fd6ba3a10d273ec4cb58c2dbe
and
coreutils commit:
http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=3babaf83875ceac896c8dd3a64248e955dfecef9
have been authored by me.

While attempting to push these patches into Ubuntu, it became apparent
that our version of coreutils does not contain the requisite patches
to correctly support /proc/self/mountinfo. /proc/self/mountinfo gives
more complete information than /proc/self/mounts which /etc/mtab now
points to. Using /proc/self/mountinfo is the upstream way of doing
things, and it allows us to resolve this specific bug.

Patches required in order to support /proc/self/mountinfo are.
Origin: upstream, gnulib - http://git.savannah.gnu.org/gitweb/?p=gnulib.git
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=3ea43e02541ece750ffc6cd1dfe34195421b4ef3
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=2768ceb7994506e2cfba88be3b6bd13ef5440a90
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=de1cbdd48244c66c51a3e2bc1594ac3ad32ce038
commit:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=3fb6e360363744462ce15c381f0b116c6fc4ce82

Origin: upstream, coreutils -
http://git.savannah.gnu.org/gitweb/?p=coreutils.git
commit:
http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=1b1c40e1d6f8cf30b6c7c9d31bbddbc3d5cc72e6
Original bug.

Depending on mount path length df sometimes prioritizes showing bind mounts
over real mounts

for example.
$ mount

192.168.1.2:/raid on /raid type nfs
(rw,nosuid,nodev,noexec,vers=4,addr=192.168.1.2,clientaddr=192.168.1.3)
/dev/sdc5 on /data type ext4 (rw)

/data/a on /a type none (rw,bind)
/raid/temp on /b type none

[Touch-packages] [Bug 1348954] Re: update Python3 for trusty

2015-10-14 Thread Matthias Klose

** Description changed:

  update Python3 for trusty.
  
  Rationale: the LTS was released with 3.4.0, the first 3.4 release which
  certainly had some issues. The idea is to update the python3.4 packages
  to the version found in 15.04 (vivid), which currently doesn't have any
  outstanding issues.  A test rebuild of the trusty main component was
  done without showing any regressions during the package builds.
  
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html
  
  To validate this SRU, I'm proposing to use the results from the test
  rebuild, plus evaluating the testsuite results of the python3.4 package
  itself.
+ 
+ To test the python3 behaviour for certificate verification, use
+ urllib.request.urlopen. requests does it's own certificate verification.
+ 
+ import urllib.request
+ sites = [
+ 'https://expired.badssl.com/',
+ 'https://wrong.host.badssl.com/',
+ 'https://self-signed.badssl.com/'
+ ]
+ 
+ for site in sites:
+ try:
+ urllib.request.urlopen(site)
+ print("OK", site)
+ except:
+ print("FAIL", site)
+ 
+ Edit /etc/python3.4/cert-verification.conf to test both behaviours

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

Title:
  update Python3 for trusty

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions source package in Trusty:
  Fix Released
Status in python3.4 source package in Trusty:
  Triaged

Bug description:
  update Python3 for trusty.

  Rationale: the LTS was released with 3.4.0, the first 3.4 release
  which certainly had some issues. The idea is to update the python3.4
  packages to the version found in 15.04 (vivid), which currently
  doesn't have any outstanding issues.  A test rebuild of the trusty
  main component was done without showing any regressions during the
  package builds.

  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html

  To validate this SRU, I'm proposing to use the results from the test
  rebuild, plus evaluating the testsuite results of the python3.4
  package itself.

  To test the python3 behaviour for certificate verification, use
  urllib.request.urlopen. requests does it's own certificate
  verification.

  import urllib.request
  sites = [
  'https://expired.badssl.com/',
  'https://wrong.host.badssl.com/',
  'https://self-signed.badssl.com/'
  ]

  for site in sites:
  try:
  urllib.request.urlopen(site)
  print("OK", site)
  except:
  print("FAIL", site)

  Edit /etc/python3.4/cert-verification.conf to test both behaviours

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

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

[Touch-packages] [Bug 1468602] Re: Time format is wrong on clock when seconds are added

** No longer affects: indicator-datetime

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

Title:
  Time format is wrong on clock when seconds are added

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  When enabling seconds in the top right corner on Ubuntu 14.04 the
  format goes from 01:23 to 01.23.45 when it should probably be
  01:23:45(colon, not period). Language is set to Norwegian.

  
  I am also seeing an increase in load on "compiz" when seconds are enabled, 
this is also found by someone else in bug #1242229.

  Would appreciate it if someone would replace the two periods with
  colons.

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

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

[Touch-packages] [Bug 1411055] Re: ubuntu-phone recurring alarm gets disabled after 1st event

Thanks for the bug report, could you try if that's still an issue?
Similar bug have been resolved since and it should work now...

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu-phone recurring alarm gets disabled after 1st event

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  This started some weeks before christmass (not sure exact image).

  Currently running vivid image #61 on Mako and the issue is still
  present.

  To reproduce:

  1. Create an alarm that has to be set for Week-days (Most probably any
  recurring setup should work)

  Observed Behavior:

  The alarm indicator icon will show up until the first alarm event is reached, 
then the alarm indicator disappears and the alarm will no longer be triggered.
  If the user tries to re-enable the alarm, it stays enabled for a second, then 
gets automatically disabled.
  Only way to set the alarm again is to delete it and create a new one that 
will also sound only once.

  Expected Behavior:

  The alarm indicator must persist until the alarm is manually disabled
  by the user or no more events are programmed to occur.

  Let me know if more information is needed.

  Thanks,
  Felipe.

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

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

[Touch-packages] [Bug 1481648] Re: [Indicators] WorldCity timezone should be shown in the datetime indicator

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [Indicators] WorldCity timezone should be shown in the datetime
  indicator

Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  It is far easier and quicker to check the world city timezones if it
  were shown in the datetime indicator than from the clock app which
  takes a few seconds and open. Ubuntu Touch uses the indicators and
  scopes for quickly exposing information and the timezone info
  satisfies that criteria.

  Datetime indicator should show all the worldcity timezones that have
  been added in the clock app.

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

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

[Touch-packages] [Bug 1354146] Re: indicator-datetime ignores 12/24 setting for other locations

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

** This bug has been marked a duplicate of bug 1319195
   indicator-datetime set for 24 hours does not show 24 hour clock for "Other 
Locations"

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

Title:
  indicator-datetime ignores 12/24 setting for other locations

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  indicator-datetime shows "auto-detected locations" and "other
  locations" in 12h format, regardless of 12/24 setting. See attached
  image that clearly shows time as 24h in the top panel and and as 12h
  alternate locations. (Time zone setting is UTC in the screenshot, but
  the symptom occurs for other timezones.)

  I've used 24h and alternate locations for years and I would have
  thought I'd have noticed previously.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140415.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  7 19:55:03 2014
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2012-10-09 (666 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (107 days ago)

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

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

[Touch-packages] [Bug 1477161] Re: "Time in other locations" doesn't respect 24-hour time setting

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

** This bug has been marked a duplicate of bug 1319195
   indicator-datetime set for 24 hours does not show 24 hour clock for "Other 
Locations"

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

Title:
  "Time in other locations" doesn't respect 24-hour time setting

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Hi,

  I have my clock set to 24-hour time. I also list time in other
  locations. Unfortunately the time in other locations doesn't respect
  the 24 hour time format. See attached screenshot for detail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20150406-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: ksplice_8174kgv5_vmlinux_new ksplice_8174kgv5 
ksplice_izqae6qt_drm_new ksplice_izqae6qt ksplice_j7tn3bjg 
ksplice_iud6ddnm_vmlinux_new ksplice_iud6ddnm ksplice_931k7rjv ksplice_omu3488j 
ksplice_zl2qw3x8_vmlinux_new ksplice_zl2qw3x8 ksplice_4uyi4z2f ksplice_9minh0rh 
ksplice_cvilzwbf_vmlinux_new ksplice_cvilzwbf ksplice_n2cjjqxn 
ksplice_zay4c782_btrfs_new ksplice_zay4c782 ksplice_fltpg4jk_btrfs_new 
ksplice_fltpg4jk ksplice_mxi2bfpt_btrfs_new ksplice_mxi2bfpt 
ksplice_fo8bf2v8_vmlinux_new ksplice_fo8bf2v8 ksplice_dc7q7cw3_vmlinux_new 
ksplice_dc7q7cw3 ksplice_6klxhfam_vmlinux_new ksplice_6klxhfam 
ksplice_g3dge67c_vmlinux_new ksplice_g3dge67c ksplice_ko1k681d_vmlinux_new 
ksplice_ko1k681d
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 22 09:37:07 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-26 (875 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130226)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to vivid on 2015-04-06 (107 days ago)

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

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

[Touch-packages] [Bug 1506109] Re: systemd-logind crashed with SIGSEGV in strlen()

2015-10-14 Thread Apport retracing service

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

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 #1495178, 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/1506109/+attachment/4494500/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1495178
   Failed to set wall message, ignoring: Message recipient disconnected from 
message bus without replying

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

Title:
  systemd-logind crashed with SIGSEGV in strlen()

Status in systemd package in Ubuntu:
  New

Bug description:
  happen after login

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Oct 14 01:24:37 2015
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2013-11-15 (698 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Vostro1310
  ProcCmdline: /lib/systemd/systemd-logind
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=c508c4ae-ef50-4989-b330-f175b5df7b5d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f9b5af296fa :movdqu (%rax),%xmm12
   PC (0x7f9b5af296fa) ok
   source "(%rax)" (0x558c8a00) not located in a known VMA region (needed 
readable region)!
   destination "%xmm12" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   strlen () at ../sysdeps/x86_64/strlen.S:106
   __GI___strdup (s=0x558c8a00 ) at strdup.c:41
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-logind crashed with SIGSEGV in strlen()
  UpgradeStatus: Upgraded to wily on 2015-10-05 (9 days ago)
  UserGroups:
   
  dmi.bios.date: 03/18/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0H528C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1310:pvrNull:rvnDellInc.:rn0H528C:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro1310
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1506045] Re: FTBFS on amd64, armhf and i386 due to missing headers

2015-10-14 Thread Łukasz Zemczak

Actually, looks like seb was already looking into that (there was no bug
so I didn't know). The new mir will be copied over soon.

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

** Changed in: mir (Ubuntu)
 Assignee: Łukasz Zemczak (sil2100) => Sebastien Bacher (seb128)

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

Title:
  FTBFS on amd64, armhf and i386 due to missing headers

Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  In Progress

Bug description:
  As per the test-rebuild of wily [1] the mir package seems to fail on
  amd64, armhf and i386 due to the following error:

  [ 14%] Building CXX object 
src/platforms/mesa/server/kms/CMakeFiles/mirplatformgraphicsmesakmsobjects.dir/linux_virtual_terminal.cpp.o
  cd 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/obj-x86_64-linux-gnu/src/platforms/mesa/server/kms
 && /usr/bin/x86_64-linux-gnu-g++   -DLOG_NDEBUG=1 -DMESA_EGL_NO_X11_HEADERS 
-DMIR_VERSION_MAJOR=0 -DMIR_VERSION_MICRO=0 -DMIR_VERSION_MINOR=16 -D__GBM__ -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing  
-Wnon-virtual-dtor -Wextra -fPIC 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/common 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platforms/mesa 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platform 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/renderers/gl 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/include/common 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/include/platform 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/mesa/server/common 
-I/usr/include/libdrm-o 
CMakeFiles/mirplatformgraphicsmesakmsobjects.dir/linux_virtual_terminal.cpp.o 
-c 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp
  In file included from /usr/include/EGL/egl.h:39:0,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platform/mir/graphics/platform.h:24,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/android/server/platform.h:22,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/android/server/platform.cpp:20:
  /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: 
No such file or directory
  compilation terminated.

  [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
  rebuild-20151001-wily.html#core

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

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

[Touch-packages] [Bug 996853] Re: Ubuntu 12.04. "Time in other locations" - There are two cities called "Nobosibirsk". One shoud be deleted.

** No longer affects: indicator-datetime

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

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

Title:
  Ubuntu 12.04. "Time in other locations" - There are two cities called
  "Nobosibirsk". One shoud be deleted.

Status in indicator-datetime package in Ubuntu:
  Invalid
Status in tzdata package in Ubuntu:
  New

Bug description:
  Ubuntu 12.04 64 bits.
  Unfortunately, I don't know the name of the package which shows Time and Date 
on the top menu.

  I was adding a city "Novosibirsk" in All Settings -> Time & Date ->
  "Time in other locations" and noticed that there are two of them:
  "Novosibirsk" and "novosiBIRSK". Last one should be deleted.

  Screenshot is attached.

  Thanks.

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Branch linked: lp:lightdm

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Branch linked: lp:lightdm/1.14

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Changed in: lightdm/1.16
   Status: Triaged => Fix Committed

** Changed in: lightdm/1.16
Milestone: None => 1.16.5

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1342400] Re: avahi-daemon constantly reporting "Invalid response packet from host"

2015-10-14 Thread Miguel Rubio-Roy

I confirm that the patch in https://github.com/lathiat/avahi/issues/10
solves the problem and returns calm to our logs.

apt-get source libavahi-core7
cd avahi-0.6.31
change avahi-core/server.c according to patch
apt-get build-dep libavahi-core7
debuild -b -uc -us
cd ..
dpkg -i libavahi-core7_0.6.31-4ubuntu4_amd64.deb
systemctl restart avahi-daemon

Please include this in any future update. It is very annoying.

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

Title:
  avahi-daemon constantly reporting "Invalid response packet from host"

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 14.04 (Release: 14.04) and looking for other
  information in /var/log/syslog, I see that syslog is being flooded by
  "Invalid response packet from host" messages from avahi-daemon.

  I searched around to see why this might be and ran across the following avahi 
mailing list post along with a patch to fix it:
  http://lists.freedesktop.org/archives/avahi/2012-July/002171.html

  >>>
  I would say you can safely ignore it, since any machine on your
  network running a recent OSX version will cause these messages.
  Here's a patch with what we change to avoid these messages flooding
  syslog.

  -Justin
  <<<

  The patch which fixes this is here:
  
http://lists.freedesktop.org/archives/avahi/attachments/20120719/1e71846e/attachment.obj

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

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

[Touch-packages] [Bug 1506085] [NEW] apport-bug's -w option isn't documented in manpage

2015-10-14 Thread Karl-Philipp Richter

Public bug reported:

apport-bug's -w option isn't documented in manpage.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1.5
Uname: Linux 4.2.3-040203-generic x86_64
ApportLog:
 ERROR: apport (pid 6679) Wed Oct 14 15:45:33 2015: called for pid 6573, signal 
5, core limit 0
 ERROR: apport (pid 6679) Wed Oct 14 15:45:33 2015: executable: 
/usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism (command line 
"/usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism")
 ERROR: apport (pid 6679) Wed Oct 14 15:45:33 2015: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
 ERROR: apport (pid 6679) Wed Oct 14 15:45:34 2015: wrote report 
/var/crash/_usr_lib_x86_64-linux-gnu_cups-pk-helper-mechanism.0.crash
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 14 16:18:08 2015
InstallationDate: Installed on 2015-09-14 (29 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug 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/1506085

Title:
  apport-bug's -w option isn't documented in manpage

Status in apport package in Ubuntu:
  New

Bug description:
  apport-bug's -w option isn't documented in manpage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  Uname: Linux 4.2.3-040203-generic x86_64
  ApportLog:
   ERROR: apport (pid 6679) Wed Oct 14 15:45:33 2015: called for pid 6573, 
signal 5, core limit 0
   ERROR: apport (pid 6679) Wed Oct 14 15:45:33 2015: executable: 
/usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism (command line 
"/usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism")
   ERROR: apport (pid 6679) Wed Oct 14 15:45:33 2015: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 6679) Wed Oct 14 15:45:34 2015: wrote report 
/var/crash/_usr_lib_x86_64-linux-gnu_cups-pk-helper-mechanism.0.crash
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 14 16:18:08 2015
  InstallationDate: Installed on 2015-09-14 (29 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1506045] Re: FTBFS on amd64, armhf and i386 due to missing headers

2015-10-14 Thread Łukasz Zemczak

It looks like this got fixed in the next mir release that landed in the
overlay PPA (mir 0.16.1+15.10.20150930.1). Will have to see if we can
safely copy-package this version, or maybe we'll just distro-patch it
quickly to fix the build failure.

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

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

Title:
  FTBFS on amd64, armhf and i386 due to missing headers

Status in Mir:
  New
Status in mir package in Ubuntu:
  In Progress

Bug description:
  As per the test-rebuild of wily [1] the mir package seems to fail on
  amd64, armhf and i386 due to the following error:

  [ 14%] Building CXX object 
src/platforms/mesa/server/kms/CMakeFiles/mirplatformgraphicsmesakmsobjects.dir/linux_virtual_terminal.cpp.o
  cd 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/obj-x86_64-linux-gnu/src/platforms/mesa/server/kms
 && /usr/bin/x86_64-linux-gnu-g++   -DLOG_NDEBUG=1 -DMESA_EGL_NO_X11_HEADERS 
-DMIR_VERSION_MAJOR=0 -DMIR_VERSION_MICRO=0 -DMIR_VERSION_MINOR=16 -D__GBM__ -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2  -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing  
-Wnon-virtual-dtor -Wextra -fPIC 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/common 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platforms/mesa 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platform 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/renderers/gl 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/include/common 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/include/platform 
-I/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/mesa/server/common 
-I/usr/include/libdrm-o 
CMakeFiles/mirplatformgraphicsmesakmsobjects.dir/linux_virtual_terminal.cpp.o 
-c 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp
  In file included from /usr/include/EGL/egl.h:39:0,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/include/platform/mir/graphics/platform.h:24,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/android/server/platform.h:22,
   from 
/«BUILDDIR»/mir-0.16.0+15.10.20150921.1/src/platforms/android/server/platform.cpp:20:
  /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: 
No such file or directory
  compilation terminated.

  [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
  rebuild-20151001-wily.html#core

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Changed in: lightdm/1.14
Milestone: None => 1.14.3

** Changed in: lightdm/1.10
Milestone: None => 1.10.6

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1505368] Re: Bug reports after segmentation fault are never generated

2015-10-14 Thread Karl-Philipp Richter

"Manual"/"Explicit" bug reporting with `ubuntu-bug` or `apport-bug`
works as expected (browser window is opened and data is processed
remotely after collecting it locally). The issue concerns issues which
have been detected by `apport` automatically (e.g. after segmentation
fault) only.

** Description changed:

  After `apport` recognizes a segmentation fault it displays a dialog
  which allows to close or restart the application and contains a checkbox
  which offers the option to file a bug online. Even if the box is checked
- no online form to open a new bug report is opened in the browser.
+ no online form to open a new bug report is opened in the browser (as
+ described on https://wiki.ubuntu.com/Apport).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 21:29:18 2015
  InstallationDate: Installed on 2015-09-14 (27 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Bug reports after segmentation fault are never generated

Status in apport package in Ubuntu:
  New

Bug description:
  After `apport` recognizes a segmentation fault it displays a dialog
  which allows to close or restart the application and contains a
  checkbox which offers the option to file a bug online. Even if the box
  is checked no online form to open a new bug report is opened in the
  browser (as described on https://wiki.ubuntu.com/Apport).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 21:29:18 2015
  InstallationDate: Installed on 2015-09-14 (27 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1506059] Re: Unreadable display

** Attachment added: "lshw"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494477/+files/lshw

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

Title:
  Unreadable display

Status in xorg package in Ubuntu:
  New

Bug description:
  It appears the Xserver version in wily is older than the version in
  Debian Jessie and is buggy.

  Given how hard it is to read, iI'll post further comment after I
  reboot this old dual bot laptop into Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 14 09:03:50 2015
  InstallationDate: Installed on 2014-08-28 (412 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago)

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

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

[Touch-packages] [Bug 1506059] Re: Unreadable display

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494478/+files/Xorg.0.log

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

Title:
  Unreadable display

Status in xorg package in Ubuntu:
  New

Bug description:
  It appears the Xserver version in wily is older than the version in
  Debian Jessie and is buggy.

  Given how hard it is to read, iI'll post further comment after I
  reboot this old dual bot laptop into Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 14 09:03:50 2015
  InstallationDate: Installed on 2014-08-28 (412 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago)

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

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

[Touch-packages] [Bug 1506059] Re: Unreadable display

** Attachment added: "debian-Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494446/+files/debian-Xorg.0.log

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

Title:
  Unreadable display

Status in xorg package in Ubuntu:
  New

Bug description:
  It appears the Xserver version in wily is older than the version in
  Debian Jessie and is buggy.

  Given how hard it is to read, iI'll post further comment after I
  reboot this old dual bot laptop into Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 14 09:03:50 2015
  InstallationDate: Installed on 2014-08-28 (412 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago)

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

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

[Touch-packages] [Bug 1506059] Re: Unreadable display

** Attachment added: "Xorg.0.log-with-xorg.conf"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494479/+files/Xorg.0.log-with-xorg.conf

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

Title:
  Unreadable display

Status in xorg package in Ubuntu:
  New

Bug description:
  It appears the Xserver version in wily is older than the version in
  Debian Jessie and is buggy.

  Given how hard it is to read, iI'll post further comment after I
  reboot this old dual bot laptop into Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 14 09:03:50 2015
  InstallationDate: Installed on 2014-08-28 (412 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago)

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

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

[Touch-packages] [Bug 1506059] Re: Unreadable display

The version of Lubuntu is wily.  This old laptop was upgrade from 14.04
which had a working display until I updated it recently.

The screenshot does not show how the display actually looks, if required
I can try to take a picture of the laptop...

Debian Jessie display is fine!

Attached are the following files:
xorg.conf used on Debian and earlier version of Ubuntu (14.04) and tried on 
wily.
Xorg.0.log without an xorg.conf file on wily. 
Xorg.0.log-with-xorg.conf
debian-Xorg.0.log working display on Debian Jessie.
lspci-vv is output of lspci -vv
lshw is output of lshw

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

Title:
  Unreadable display

Status in xorg package in Ubuntu:
  New

Bug description:
  It appears the Xserver version in wily is older than the version in
  Debian Jessie and is buggy.

  Given how hard it is to read, iI'll post further comment after I
  reboot this old dual bot laptop into Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 14 09:03:50 2015
  InstallationDate: Installed on 2014-08-28 (412 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago)

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

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

[Touch-packages] [Bug 1506059] Re: Unreadable display

** Attachment added: "xorg.conf"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506059/+attachment/4494480/+files/xorg.conf

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

Title:
  Unreadable display

Status in xorg package in Ubuntu:
  New

Bug description:
  It appears the Xserver version in wily is older than the version in
  Debian Jessie and is buggy.

  Given how hard it is to read, iI'll post further comment after I
  reboot this old dual bot laptop into Debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Oct 14 09:03:50 2015
  InstallationDate: Installed on 2014-08-28 (412 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140823)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (2 days ago)

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

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

[Touch-packages] [Bug 1490298] Re: Lowercase months in Portuguese language

that's part of the locale

** Package changed: indicator-datetime (Ubuntu) => langpack-locales
(Ubuntu)

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

Title:
  Lowercase months in Portuguese language

Status in langpack-locales package in Ubuntu:
  New

Bug description:
  Hi,

  Due to some modifications made to our mother language back in 2012.
  The months passed to be written with lowercase.

  Example:

  Quarta-feira, 29 de Julho de 2015 (before 2012)

  quarta-feira, 29 de julho de 2015 (since 2012)

  Where we can (translator community) fix this? We've been searching,
  but we can't deal with it.

  This is one bug we can't fix or solve for the ubuntu touch.

  Please, gives us some additional information on this subject.

  Thanks!
  Ivo Xavier - Ubuntu Portuguese Translators

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

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

[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

2015-10-14 Thread oshunluvr

For what it's worth, it seems it might be HOW the script is being
called. Testing the apt-auto-removal script here (Kubuntu 15.04) with
kernels 3.19.0-29-generic,  3.19.0-30-generic, and 3.19.0-31-generic
installed and after a reboot to load -31:

1) Noticed the call to autoremove 3.19.0-30-generic.
2) Read /etc/apt/apt.conf.d/01autoremovekernels and saw -29 and -31 listed as 
"NeverAutoRemove"
3) Manually removed 3.19.0-29-generic.
4) Ran "sudo /etc/kernel/postinst.d/apt-auto-removal"
5) Re-read /etc/apt/apt.conf.d/01autoremovekernels and saw only  -31 listed as 
"NeverAutoRemove"
6) Ran "sudo /etc/kernel/postinst.d/apt-auto-removal 3.19.0-31-generic"
7) Re-read /etc/apt/apt.conf.d/01autoremovekernels and saw -30 and -31 listed 
as "NeverAutoRemove"

So it worked when called properly in that case. I thought it possible
that part of the problem is it's being called with the wrong kernel
version.

I re-installed -25 and -21 along with -30 and -31. This resulted in -25 and -31 
in the never remove list. 
But again: When apt-auto-removal is re-run with -31, the never remove list 
changes to -30 and -31.

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1044353] Re: indicator-datetime-session has 100% cpu use with geoclue-geonames

that are no recent report of that issue, likely resolved

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Low

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

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

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

Title:
  indicator-datetime-session has 100% cpu use with geoclue-geonames

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  I had geoclue-geonames installed and not geoclue-ubuntu-geoip. I don't
  know why, probably happend at a random point during the quantal dist-
  upgrades. This caused indicator datetime to spinn 100% cpu.

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Also affects: lightdm/1.16
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.2
   Importance: Undecided
   Status: New

** Also affects: lightdm/1.14
   Importance: Undecided
   Status: New

** Changed in: lightdm/1.2
   Status: New => Won't Fix

** Changed in: lightdm/1.2
   Importance: Undecided => Low

** Changed in: lightdm/1.14
   Status: New => Triaged

** Changed in: lightdm/1.16
   Status: New => Triaged

** Changed in: lightdm/1.14
   Importance: Undecided => Medium

** Changed in: lightdm/1.16
   Importance: Undecided => Medium

** Changed in: lightdm
Milestone: None => 1.17.0

** Changed in: lightdm/1.10
   Importance: Undecided => Low

** Changed in: lightdm/1.10
   Status: New => Triaged

** Changed in: lightdm
   Status: Triaged => Fix Committed

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1487414] Re: recordmydesktop should be a dependency of ubuntu-ui-toolkit-autopilot

Either this, or disable recording when recordmydesktop is not found (but
add it to Suggested dependencies).

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

Title:
  recordmydesktop should be a dependency of ubuntu-ui-toolkit-autopilot

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

Bug description:
  Attempting to debug an issue with local test runs I removed
  recordmydesktop (as it was spiking at 100% CPU and tests got stuck)
  and it turns out I could no longer run tests - yet it's not a
  dependency of ubuntu-ui-toolkit-autopilot.

  Error: The application 'recordmydesktop' needs to be installed to
  record failing jobs.

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

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

[Touch-packages] [Bug 1500039] Re: Ubuntu Phone is not getting a mobile network cell triangulation position

2015-10-14 Thread Sergi Quiles Pérez

I have experienced this issue:

If I have my bq Aquaris Ubuntu Edition connected only to a 3g network it
lasts a lot to obtain GPS positions. But if I connect via hotspot an
Android phone to my bq with Ubuntu Touch the Android one gets GPS
positions instantly. So I thing Ubuntu Touch has this bug.

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

Title:
  Ubuntu Phone is not getting a mobile network cell triangulation
  position

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

Bug description:
  Hi!

  I think that the mobile network cell triangulation position is not
  working in Ubuntu Phone OS.

  The position should be really fast (~1 - 5") and I'm thinking that
  Ubuntu Phone is waiting for a real GPS position every time.

  A good test could be this:
  - Go to a room, way out of a sky to avoid a real GPS signal.
  - Set WiFi service OFF.
  - Set GPS service ON.
  - Set data connection ON.
  - Go to this website via webbrowser-app: 
http://leafletjs.com/examples/mobile-example.html The website will ask you to 
allow access to the current location.
  - Make sure to not have a GPS position cached.

  In a PC or *any* Android you'll see your position immediately.
  Bug: In Ubuntu Phone an error will appears. This error is because the 
geoposition 
(https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation)
 is not working with the cell triangulation network data.

  You can try a lot of apps like Google Maps, OSMTouch, HERE map, uNAV... and a 
fast position from data connection is not happening, unless you be with a WIFI 
connection.
  If you try Google Maps in Android, the position will be really fast just with 
data connection.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1500050] Re: [indicators] No way to stop an alarm that has been snoozed

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [indicators] No way to stop an alarm that has been snoozed

Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Once a user snoozes an alarm, there is no way to stop the alarm
  without having to wait for the snooze period to be over. The indicator
  datetime should provide options to completely stop the alarm like
  Android does. This pattern can already been seen in the messaging
  indicator where users can reply to messages. Another example is a
  missed call where users can either call back or message them via the
  action buttons show in the indicator.

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

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

[Touch-packages] [Bug 1440549] Re: please convert python scripts to python3

2015-10-14 Thread Matthias Klose

please use dh_python3 --shebang=/usr/bin/python3 explicitly

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

Title:
  please convert python scripts to python3

Status in gconf package in Ubuntu:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. Please convert the two python scripts installed
  with the gconf2 package to Python3.

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

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

[Touch-packages] [Bug 1505791] Re: Prefilled text / focus issue for text field

2015-10-14 Thread Olivier Tilloy

Okay, I just saw it after opening another tab and browsing to
gatherer.wizards.com. The search box didn’t initially appear to have
focus, as there was no blinking caret in it, but typing text showed that
it did have focus, as characters were entered, after the placeholder
text, instead of replacing it. It looks like it could be a focus issue:
if I press e.g. Ctrl+L to focus the address bar, then the placeholder
text disappears, and the caret appears.

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

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

** Tags added: focus

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

Title:
  Prefilled text / focus issue for text field

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I wasn't sure how to title this, please adjust as you see fit.

  1) Visit http://gatherer.wizards.com/
  2) Click on the text field that says "Search terms..."
  3) Notice how the text "Search terms..." doesn't go away and instead, you are 
editing it

  On other browsers, the page starts with that text field focused.  And
  though when you click away, you do see the "Search terms..." text,
  clicking on the text field clears the text.

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

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

[Touch-packages] [Bug 1502896] Re: CI segfault in mir-mediumtests-runner-mako in client tests

2015-10-14 Thread Andreas Pokorny

Another recent example now with the mir_client_basic:
https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-
touch/7015/console

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

Title:
  CI segfault in mir-mediumtests-runner-mako in client tests

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  New

Bug description:
  https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-
  mako/6883/consoleFull:

  /bin/bash: line 1: 6408 Segmentation fault mir_demo_server --test-
  client /usr/bin/mir_demo_client_fingerpaint

  Other recent CI failures that could be related:

  https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-
  mako/6874/console

  [0;32m[ RUN ] [mGLMark2Test.benchmark_fullscreen_default
  [1444017567.936891] mirplatform: Found graphics driver: android
  [1444017567.937715] mirplatform: Found graphics driver: mesa-kms
  [1444017567.937867] mirplatform: Found graphics driver: mesa-x11
  [1444017567.938630] mirplatform: Found graphics driver: dummy
  /bin/bash: line 1: 5759 Segmentation fault (core dumped) umockdev-run -- 
mir_performance_tests

  And also:

  https://bugs.launchpad.net/mir/+bug/1502782

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

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

[Touch-packages] [Bug 1264554] Re: python3.4 autopkg test failures

Hello Matthias, or anyone else affected,

Accepted python3.4 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.4/3.4.3-1ubuntu1~14.04.2 in
a few hours, and then in the -proposed repository.

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

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

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

** Changed in: python3.4 (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  python3.4 autopkg test failures

Status in python3.3 package in Ubuntu:
  Won't Fix
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.4 source package in Trusty:
  Fix Committed

Bug description:
  see
  
https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-python3.4/24/

  disabled these in the autopkg tests for now. need some investigation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1264554/+subscriptions

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Branch linked: lp:lightdm/1.16

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1319195] Re: indicator-datetime set for 24 hours does not show 24 hour clock for "Other Locations"

** Tags added: rls-w-incoming

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

Title:
  indicator-datetime set for 24 hours does not show 24 hour clock for
  "Other Locations"

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I configured the clock format to be 24-hour. This takes affect in the
  system clock, however "other locations" are unaffected and still show
  12-hour clock. See screenshot.

  This is Ubuntu Trusty

  indicator-datetime: 13.10.0+14.04.20140415.3-0ubuntu1

  I expect the Other Locations to also be 24 hour display.

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

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

[Touch-packages] [Bug 1408958] Re: Calendar alarm notifications have no buttons, on screen for short while

2015-10-14 Thread Michał Sawicz

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

** This bug has been marked a duplicate of bug 1401802
   [Scopes] Calendar reminder notifications became queued, non-interactive and 
easy to miss

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

Title:
  Calendar alarm notifications have no buttons, on screen for short
  while

Status in unity8 package in Ubuntu:
  New

Bug description:
  Using krillin #186 from ubuntu-touch/ubuntu-rtm/14.09-proposed
  notifications of calendar events are broken.

  Previously a calendar event with reminder would trigger a notification
  with OK / Snooze buttons, but those buttons are no longer there. In
  addition the notification is very short, so getting a screenshot for
  this bug was challenging!

  Steps to reproduce

  1. Flash krillin with 186
  2. Install Calendar app
  3. Add a calendar entry for sometime soon with a reminder
  4. Wait for the notification

  Expected behaviour

  Notification appears until some arbitrary time out or user clicks a
  button

  Actual behaviour

  Notification appears without buttons, and only for a brief period.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-datetime 13.10.0+15.04.20141210~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Jan  9 09:41:35 2015
  InstallationDate: Installed on 2015-01-08 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150108-030204)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

2015-10-14 Thread John Johansen

yes,
  UBUNTU: SAUCE: (no-up) apparmor: fix mount not handling disconnected 
paths 

is causing the regression. However reverting this fix will cause issues
for Bug 1496430, which was blocking a fix for a CVE.

The correct solution is to update the profile.

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New
Status in lxc source package in Trusty:
  New

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

[Touch-packages] [Bug 1411055] Re: ubuntu-phone recurring alarm gets disabled after 1st event

2015-10-14 Thread Felipe De la Puente

Hi Sebastien,

The bug has been fixed. Apparently it was not marked as duplicate of the
other bugs. I marked it as Fix released now, however I don't remember in
which image the fix was actually released.

Thanks,
Felipe.

** Changed in: indicator-datetime (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  ubuntu-phone recurring alarm gets disabled after 1st event

Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  This started some weeks before christmass (not sure exact image).

  Currently running vivid image #61 on Mako and the issue is still
  present.

  To reproduce:

  1. Create an alarm that has to be set for Week-days (Most probably any
  recurring setup should work)

  Observed Behavior:

  The alarm indicator icon will show up until the first alarm event is reached, 
then the alarm indicator disappears and the alarm will no longer be triggered.
  If the user tries to re-enable the alarm, it stays enabled for a second, then 
gets automatically disabled.
  Only way to set the alarm again is to delete it and create a new one that 
will also sound only once.

  Expected Behavior:

  The alarm indicator must persist until the alarm is manually disabled
  by the user or no more events are programmed to occur.

  Let me know if more information is needed.

  Thanks,
  Felipe.

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

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

[Touch-packages] [Bug 198523] Re: Optical Audio Out Plays At Wrong Speed..

2015-10-14 Thread Mikael Thurberg

Its because its not synced the frequency between the output and input..

In other words, if you play a 96 kHz audio (or 48 kHz audio) via a 44.1
kHz output, it gets faster "trying to squeeze everything in the 44.1 kHz
stream"..

It could be a problem at your digital input (yamaha), but I dont think
it is there because they sense what kHz is beeing used and adapts the
input accordingly.


The error is somewhere between the kHz of what you are trying to play, what the 
soundcard is sonfigured to play up sounds at, and at the digital output at the 
card.

Its a missmatch between the kHz of what is beeing played and the
configuration of the mixer.. there lies the problem.

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

Title:
  Optical Audio Out Plays At Wrong Speed..

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  I have my 'Hard Heron' Alpha 5 Desktop computer hooked up to my Yamaha 
receiver through a Fiber-Optic Audio Cable.
  If I set my 'Sound' settings to go through 'Intel ICH5 - IEC958' I can get it 
to play sounds, but the sounds play at a faster speed than regular.  So when I 
listen to music the music seems to be at double speed..  I have looked around 
on the net for this problem and could not find anything..

  Help would be much appreciated! :)

  P.S. the sound through this cable works perfectly fine in Windows XP.

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

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

[Touch-packages] [Bug 1425221] Re: [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] tinny sound

2015-10-14 Thread Raymond

http://git.alsa-project.org/?p=alsa-
tools.git;a=tree;f=hdajacksensetest;hb=HEAD

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

Title:
  [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] tinny sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound equalization is normal when using jack in front of computer, but
  is "tinny" (i.e., low/nonexistent bass and midtones) when using rear
  output jack  with simple two channel headphones.

  Jack sense is working correctly because the internal speaker cuts out
  when a cable is plugged into the rear jack (or front jack, for that
  matter).

  Note Dell's website says this computer has a Realtek ALC3220, as
  opposed to the ALC280 which is detected by linux.  This is a clean
  install of 14.04, so I unfortunately I can't boot into Windows to
  observe its behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 12:31:49 2015
  InstallationDate: Installed on 2015-01-30 (25 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] Background noise 
or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 835297] Re: sometimes /etc/timezone is not being created

is that still an issue?

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  sometimes /etc/timezone is not being created

Status in Indicator Date and Time:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  I'm not convinced this isn't already reported or is genuinely in unity
  but I can't think of a search query that will track it down.

  Since upgrading to Oneiric I'm no longer seeing the clock, simply the
  word "Time". I really can't explain it very well so screenshot
  attached.

  I didn't use Unity pre-Oneiric although I did boot into it on at east
  one occassion and think I would have noticed the missing clock. I've
  been through a full set of video drivers for other reasons (nv,
  nouveau, vesa, nvidia-current) without any effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.8.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 
PDT 2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-7ubuntu1)
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sat Aug 27 09:04:30 2011
  DistUpgraded: Log time: 2011-08-21 09:12:55.859993
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-current, 280.13, 3.0.0-9-generic, x86_64: installed
   vboxhost, 4.0.12, 3.0.0-9-generic, x86_64: installed
  GraphicsCard:
   nVidia Corporation G98 [GeForce 8400 GS] [10de:06e4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: nVidia Corporation Device [10de:050f]
  MachineType: System manufacturer M2NS-NVM
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=d70f0f0c-60c0-45e9-acf0-250be6dcd21e ro quiet 
splash nomodeset
  SourcePackage: unity
  UpgradeStatus: Upgraded to oneiric on 2011-08-21 (5 days ago)
  dmi.bios.date: 09/28/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2NS-NVM ACPI BIOS Revision 0401
  dmi.board.name: M2NS-NVM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2NS-NVMACPIBIOSRevision0401:bd09/28/2006:svnSystemmanufacturer:pnM2NS-NVM:pvr1.XX:rvnASUSTeKComputerINC.:rnM2NS-NVM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M2NS-NVM
  dmi.product.version: 1.XX
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu16
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1412916] Re: evince: Bad PDF rendering: invalid font scale

Hello Charles, or anyone else affected,

Accepted poppler into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/poppler/0.24.5-2ubuntu4.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: poppler (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Trusty:
  Fix Committed

Bug description:
  (SRU info on comment #11)

  Evince in ubuntu 14.04 (3.10.3-0ubuntu10.1) suffers from this bug:
  https://www.libreoffice.org/bugzilla/show_bug.cgi?id=78042

  The test case which is attached to the upstream bug demonstrates the
  problem with Evince in Ubuntu.

  Hopefully, the patch attached to the upstream bug report would fix the
  problem in ubuntu.

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

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

[Touch-packages] [Bug 1348954] Re: update Python3 for trusty

Hello Matthias, or anyone else affected,

Accepted python3.4 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.4/3.4.3-1ubuntu1~14.04.2 in
a few hours, and then in the -proposed repository.

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

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

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

** Changed in: python3.4 (Ubuntu Trusty)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  update Python3 for trusty

Status in python3-defaults package in Ubuntu:
  New
Status in python3-stdlib-extensions source package in Trusty:
  Fix Released
Status in python3.4 source package in Trusty:
  Fix Committed

Bug description:
  update Python3 for trusty.

  Rationale: the LTS was released with 3.4.0, the first 3.4 release
  which certainly had some issues. The idea is to update the python3.4
  packages to the version found in 15.04 (vivid), which currently
  doesn't have any outstanding issues.  A test rebuild of the trusty
  main component was done without showing any regressions during the
  package builds.

  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html
  
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html

  To validate this SRU, I'm proposing to use the results from the test
  rebuild, plus evaluating the testsuite results of the python3.4
  package itself.

  To test the python3 behaviour for certificate verification, use
  urllib.request.urlopen. requests does it's own certificate
  verification.

  import urllib.request
  sites = [
  'https://expired.badssl.com/',
  'https://wrong.host.badssl.com/',
  'https://self-signed.badssl.com/'
  ]

  for site in sites:
  try:
  urllib.request.urlopen(site)
  print("OK", site)
  except:
  print("FAIL", site)

  Edit /etc/python3.4/cert-verification.conf to test both behaviours

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

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

[Touch-packages] [Bug 1425221] Re: [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] tinny sound

2015-10-14 Thread Raymond

http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/modules/alsa/mixer/paths
/analog-output.conf.common

[Element PCM] is common to all paths

you need the above patch to change the name of volume control and switch
to Speaker+LO

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

Title:
  [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] tinny sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound equalization is normal when using jack in front of computer, but
  is "tinny" (i.e., low/nonexistent bass and midtones) when using rear
  output jack  with simple two channel headphones.

  Jack sense is working correctly because the internal speaker cuts out
  when a cable is plugged into the rear jack (or front jack, for that
  matter).

  Note Dell's website says this computer has a Realtek ALC3220, as
  opposed to the ALC280 which is detected by linux.  This is a clean
  install of 14.04, so I unfortunately I can't boot into Windows to
  observe its behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 24 12:31:49 2015
  InstallationDate: Installed on 2015-01-30 (25 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [OptiPlex 9020, Realtek ALC280, Green Line Out, Rear] Background noise 
or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06X1TJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/20/2014:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn06X1TJ:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1504170] Re: [Indicators] Some icons in messaging-menu disappear when list items are selected

the indicator doesn't deal with the UI, it's just a backend

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

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

Title:
  [Indicators] Some icons in messaging-menu disappear when list items
  are selected

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Triaged
Status in indicator-messages package in Ubuntu:
  Invalid
Status in messaging-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) receive a message from a MMS group
  2) open messaging-menu
  3) verify the group icon is displayed
  4) tap the message to reply
  5) verify the icon disappears because it has the same color as the selection.

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Changed in: lightdm/1.14
   Status: Triaged => Fix Committed

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1350893] Re: [sdk] Allow header background customization per page

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/40-PageWithHeader

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

Title:
  [sdk] Allow header background customization per page

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Each Page should have the ability to customize a few things about the
  look of the header, these changes should take affect when the page
  becomes the top page in a PageStack or the current tab in Tabs.

  headerColor: Set the background color of the Header
  headerGradient: Same as headerColor, only using a Gradient object instead of 
a single color
  headerImage: Set a background Image on the Header, resized to fit based on 
fillMode
  headerBorderImage: Same as headerImage, but using a BorderImage

  follow-up of this bug: https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1315884 which I changed to only include header foreground
  color customization.

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

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

[Touch-packages] [Bug 1248898] Re: No documentation for how to hide MainView's header

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/40-PageWithHeader

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

Title:
  No documentation for how to hide MainView's header

Status in Ubuntu UI Toolkit:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  All Ubuntu applications should have a MainView, even if you want the
  app to be fullscreen and not contain the "Ubuntu header" (for example
  a game). The way to do this, currently, is to have a Header and a
  Page, and set the Page's title to the empty string, "". This will hide
  the header. This is, however, undocumented, and even if documented is
  a bit crufty (what happens if you have more than one page and one of
  them has a blank title? Does the header appear only on some pages?
  That would mean that you can switch between pages until you get to a
  headerless one and then you're stuck there.) Perhaps there should be a
  hideHeader boolean property on MainView or similar: it would do the
  same thing as setting the current Page's title to "", but would be a
  property of the header rather than the page: it would also make it
  easier to discover this feature from reading the documentation,
  because there would be an explicit property to do what's required
  rather than a magic value of an existing property.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1248898/+subscriptions

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

[Touch-packages] [Bug 1445016] Re: Having access to the page header component would be useful

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/40-PageWithHeader

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

Title:
  Having access to the page header component would be useful

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

Bug description:
  Using vivid, currently the pagestack/page try to be smart with the
  header and adjust margins as needed, but that doesn't always work and
  it would be nice to have access to the header component to be able to
  e.g anchor on header.bottom

  small testcase example attached, the intend is to center the label but
  it's not easy to do (you can do it by tweaking the topMargin though)

  (note that the code is inspired from the system settings updates panel
  and bug #1429280)

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

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

[Touch-packages] [Bug 1492328] Re: header icon color should match title label color when backgroundColor is set

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/40-PageWithHeader

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

Title:
  header icon color should match title label color when backgroundColor
  is set

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

Bug description:
  If I set a custom background color on a MainView, the color of the
  title label in the header is computed to make the title readable, but
  the color of the header icons isn’t, and it may be difficult to see
  them.

  See the attached standalone reproducer, where the background color is
  green, the title is white (white on green is fairly readable), but the
  header icon is the default light grey, which makes it very hard to
  view on the green background. I would expect the icon to be white too.

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

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

[Touch-packages] [Bug 1408015] Re: [sdk][UX] Confirmation in the header bar confusing

New designs are coming which makes this more clear.

** Changed in: ubuntu-ux
Status: Fix Committed => In Progress

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

Title:
[sdk][UX] Confirmation in the header bar confusing

Status in Quick Memo:
New
Status in Ubuntu Calendar App:
New
Status in Ubuntu Clock App:
Fix Released
Status in Ubuntu UX:
In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed

Bug description:
Imagine a form of some sort, you fill a few fields of data top-down,
and at the end of it you need to tap in the header at the top to
save/confirm.

Pair that with the header going off-screen to leave more screen for
the content, you have to pull the header in first (and you need to
know that's where the button will be).

An example of this behaviour is the calendar app when adding/editing
an event. One other example (although that could be improved easily by
auto-saving the new note as soon as it's edited) is the Quick Memo
app, where when you create a note in the first place you need to tap
the ✓ icon, but when you're editing, it's all auto-saved and you need
to tap 〈 to go back to the list of notes.

I feel like we need to at least come up with clear guidance on what
belongs in the header, and where a footer with buttons should be used
(we have a way to stick something on top of the keyboard after all¹).

http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView
/#anchorToKeyboard-prop

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: qtdeclarative5-ubuntu-ui-toolkit-plugin
1.1.1364+15.04.20141209-0ubuntu2
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.15-0ubuntu3
Architecture: armhf
Date: Tue Jan 6 17:03:54 2015
InstallationDate: Installed on 2014-12-17 (20 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf
(20141217-020204)
SourcePackage: ubuntu-ui-toolkit
UpgradeStatus: No upgrade log present (probably fresh install)

--- UX comment & resolution --

The back button in the header should never be used as a confirmation but can
mean CANCEL and not just BACK.
If an action or any alterations within the content/screen have to be
confirmed/saved then it requires a visible call to action. This call to action
sits by default in the header unless differently specified by
designer/developer.

In all here described cases the UX can be improved easily by adding
clarity to the UI and sometimes just adding a call to action.

The header can be fixed or can go off-screen the specification for
that lies with the designer/developer. This means if I have an
important action in the header which I want to present to the user all
the time, then the header stays fixed, even if the content is
scrolled.

Clock app:
When creating a new alarm by swiping from the bottom of the screen, the tick
(confirmation) icon should be disabled. Only after interacting with the screen,
by changing one of the parameters for example, the tick should be enabled. This
will signal to user that there was a change and this needs to be confirmed.
Even more informative is a simple word instead of the tick: SAVE. The SAVE
option is a new addition to the header and wasn't available so far.
This concept is already documented in the UI - Toolkit spec which is at the
bottom of this post. If user taps back before saving then the alarm won't be
created. Additionally there can be visual feedback by adding the "feedback
bubble" to the UI.
If the user taps back before saving the feedback bubble states, e.g. "Alarm
not saved". If the tick icon is tapped, it can state "Alarm saved" (see
Notification spec).
In the Repeat section the select all icon has to move one to the left and a
tick or "save added". The behaviour will then follow as described above.

Note app:
There is nothing wrong with the note app approach but it is a custom made
behaviour which is up to the developer. This person decided not to use our
pattern and include a tick or SAVE into the header. There are many note taking
apps on iOS which are not using their patterns either. This doesn't mean they
are bad, they just work differently.

While it is ok to use a "Send Order" or a NEXT at the end of a form,
for some instances and apps it won't be efficient. This means <
CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it
is not possible to control apps which don't want to user out UI-
Toolkit, hence the other solutions will exist too.

We are constantly improving the UI-Toolit and I will add the
footer/toolbar idea to potential new projects for design.

Please see for reference the notification spec:

https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1#

Please see for reference the

[Touch-packages] [Bug 1505302] Re: core_pattern is incorrect on boot with crash reporting enabled

2015-10-14 Thread Jean-Baptiste Lallement

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

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

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  core_pattern is incorrect on boot with crash reporting enabled

Status in Canonical System Image:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  current build number: 136
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
  $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern

  Instead of:
  |/usr/share/apport/apport %p %s %c %P

  and crash reporting is disabled while it should be enabled.

  According to the apport.log attached, core_pattern should be set
  correctly.

  If the user disables/enables crash reporting the pattern is correct.

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

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

[Touch-packages] [Bug 1466526] Re: devel-proposed r227 for Flo is stuck in landscape mode

2015-10-14 Thread jezra

If this ticket is valid, then the tablet UX  is intentionally broken.

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

Title:
  devel-proposed r227 for Flo is stuck in landscape mode

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Upon reboot after updating to r227, the screen was stuck in landscape
  mode.

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

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

[Touch-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

2015-10-14 Thread Cavsfan

I also found a work around: once the new kernel is installed and it's
wanting to reboot, delete the 3rd oldest kernel or autoremove it before
rebooting and then the /etc/apt/apt.conf.d/01autoremovekernels file will
contain the 3 kernels, which is better than having one.

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1437671] Re: package bluetooth-touch 0.3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-10-14 Thread christian c

Still waiting for a fix! Hope on 15.10!

After the installation failed, I noticed that WiFi doesn't work anymore
after reboot/suspend. Some of the files were already installed on the
system, untill the fail-message was displayed. So I had to make a
complete uninstall of bluetooth-touch, in order to make WiFi work again.

Maybe an additional Bug on bluetooth-touch?!

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

Title:
  package bluetooth-touch 0.3.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluetooth-touch package in Ubuntu:
  Confirmed

Bug description:
  Trying out ubuntu-next from a ubuntu-desktop installation - didnt work
  - so I have reverted back.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: bluetooth-touch 0.3.1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  Date: Sat Mar 28 14:43:25 2015
  DuplicateSignature: package:bluetooth-touch:0.3.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-07-09 (627 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
   dpkg 1.17.24ubuntu1
   apt  1.0.9.7ubuntu3
  SourcePackage: bluetooth-touch
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Title: package bluetooth-touch 0.3.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to vivid on 2015-03-28 (0 days ago)

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

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

[Touch-packages] [Bug 1244578] Re: lightdm-session runs xrdb with -nocpp option

** Changed in: lightdm (Ubuntu Utopic)
   Status: Fix Committed => Won't Fix

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

Title:
  lightdm-session runs xrdb with -nocpp option

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Utopic:
  Won't Fix
Status in lightdm source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  lightdm-session runs xrdb for .Xresources file with the -nocpp option
  (Line 37 and 43), which prevents the xrdb from preprocessing the
  .Xresources file. Many configurations like the popular solarized color
  theme (https://github.com/solarized/xresources/blob/master/solarized)
  use this and you find some complaints about in on the internet

  https://bbs.archlinux.org/viewtopic.php?id=164108
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163129
  
http://superuser.com/questions/655857/urxvt-uses-pink-instead-of-solarized-until-i-run-xrdb-xresources/656213

  I don't see a reason for not using the preprocessor and so did the
  editor of Xsession (the option is not used in
  /etc/X11/Xsession.d/30x11-common_xresources)

  [Test Case]

   - Install solarized theme
  https://github.com/solarized/xresources/blob/master/solarized

  - Load default Xresources file (xrdb < .XDefaults )

  - Now every macro supported by CPP will not work.

  
  [Regression Potential] 

  * No regression potential advised, small (0.001%) load average increase
  on startup time because of enabling Cpp.

  [Solution]

  Backport default wily session to older releases.

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

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

[Touch-packages] [Bug 1244578] Re: lightdm-session runs xrdb with -nocpp option

This bug was fixed in the package lightdm - 1.14.2-0ubuntu1.1

---
lightdm (1.14.2-0ubuntu1.1) vivid; urgency=medium

  * debian/lightdm-session: Enable the C preprocessor
when loading X resources. (LP: #1244578).

 -- Jorge Niedbalski   Mon, 15 Jun 2015
11:39:09 -0500

** Changed in: lightdm (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  lightdm-session runs xrdb with -nocpp option

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Utopic:
  Won't Fix
Status in lightdm source package in Vivid:
  Fix Released

Bug description:
  [Impact]

  lightdm-session runs xrdb for .Xresources file with the -nocpp option
  (Line 37 and 43), which prevents the xrdb from preprocessing the
  .Xresources file. Many configurations like the popular solarized color
  theme (https://github.com/solarized/xresources/blob/master/solarized)
  use this and you find some complaints about in on the internet

  https://bbs.archlinux.org/viewtopic.php?id=164108
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163129
  
http://superuser.com/questions/655857/urxvt-uses-pink-instead-of-solarized-until-i-run-xrdb-xresources/656213

  I don't see a reason for not using the preprocessor and so did the
  editor of Xsession (the option is not used in
  /etc/X11/Xsession.d/30x11-common_xresources)

  [Test Case]

   - Install solarized theme
  https://github.com/solarized/xresources/blob/master/solarized

  - Load default Xresources file (xrdb < .XDefaults )

  - Now every macro supported by CPP will not work.

  
  [Regression Potential] 

  * No regression potential advised, small (0.001%) load average increase
  on startup time because of enabling Cpp.

  [Solution]

  Backport default wily session to older releases.

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

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

[Touch-packages] [Bug 878836] Re: [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions

** Tags added: rls-w-incoming

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

Title:
  [FFe] Unity Greeter - Use Unity Greeter to fulfil lock screen as well
  as login functions

Status in Ayatana Design:
  Fix Committed
Status in Session Menu:
  Fix Released
Status in Light Display Manager:
  Triaged
Status in Unity:
  Fix Released
Status in gnome-screensaver package in Ubuntu:
  Fix Released
Status in indicator-session package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Triaged
Status in indicator-session source package in Precise:
  Fix Released

Bug description:
  Use Unity Greeter to fulfil lock screen as well as login functions.

  Desired Solution:
  - Replace the current lock screen with the Unity Greeter
  - perhaps use 'light locker', see 
http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html
  - also see https://plus.google.com/u/0/106086509626546157534/posts/5hQVYARYCkh

  [FFe]
  This is a FFe to implement in unity a lockscreen that looks like 
unity-greeter inside unity.

  The code for unity was ready before FF, but to improve PAM support we had to 
delay it
  See more at 
https://code.launchpad.net/~andyrock/unity/lockscreen/+merge/206291

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Branch linked: lp:lightdm/1.10

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

** Changed in: lightdm/1.10
   Status: Triaged => Fix Committed

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Committed
Status in Light Display Manager 1.16 series:
  Fix Committed
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Touch-packages] [Bug 1466526] Re: devel-proposed r227 for Flo is stuck in landscape mode

2015-10-14 Thread Alan Pope 

This is known and currently intentional until we come back to work on
the tablet form factor and side stage interactions. Until then you can
probably undo this change on your own device by modifying /etc/ubuntu-
touch-session.d/flo.conf and rebooting, but if it breaks you get to keep
the pieces. We don't support that change.

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

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

Title:
  devel-proposed r227 for Flo is stuck in landscape mode

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Upon reboot after updating to r227, the screen was stuck in landscape
  mode.

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

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

[Touch-packages] [Bug 1506159] Re: systemd-logind crashed with SIGSEGV in strlen()

2015-10-14 Thread Apport retracing service

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

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 #1495178, 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/1506159/+attachment/4494676/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1495178
   Failed to set wall message, ignoring: Message recipient disconnected from 
message bus without replying

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

Title:
  systemd-logind crashed with SIGSEGV in strlen()

Status in systemd package in Ubuntu:
  New

Bug description:
  [   19.339471] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
ips_enabled (expected 1, found 0)
  [   19.339476] [ cut here ]
  [   19.339493] WARNING: CPU: 0 PID: 249 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c
  [   19.339494] pipe state doesn't match!
  [   19.339495] Modules linked in: nls_iso8859_1 intel_rapl iosf_mbi 
x86_pkg_temp_thermal intel_powerclamp coret
  [   19.339533]  acpi_als kfifo_buf industrialio parport_pc ppdev lp parport 
autofs4 hid_generic usbhid uas usb_
  [   19.339551] CPU: 0 PID: 249 Comm: plymouthd Tainted: P   OE   
4.2.0-16-generic #19-Ubuntu
  [   19.339553] Hardware name: Hewlett-Packard 300-016d/2B38, BIOS 80.03 
12/15/2014
  [   19.339554]   2594191b 880078dcf7c8 
817e8c09
  [   19.339557]   880078dcf820 880078dcf808 
8107b3c6
  [   19.339559]  880078dcf848 880078dcf8b0 88003f61a000 
0001
  [   19.339562] Call Trace:
  [   19.339567]  [] dump_stack+0x45/0x57
  [   19.339572]  [] warn_slowpath_common+0x86/0xc0
  [   19.339574]  [] warn_slowpath_fmt+0x55/0x70
  [   19.339589]  [] ? intel_pipe_config_compare+0xb31/0xc60 
[i915]
  [   19.339602]  [] check_crtc_state+0x2c5/0x440 [i915]
  [   19.339619]  [] intel_modeset_check_state+0x21d/0x6d0 
[i915]
  [   19.339633]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [   19.339647]  [] ? drm_mode_create+0x25/0x60 [drm]
  [   19.339659]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [   19.339671]  [] drm_mode_setcrtc+0x3e9/0x500 [drm]
  [   19.339679]  [] drm_ioctl+0x125/0x610 [drm]
  [   19.339691]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
  [   19.339695]  [] do_vfs_ioctl+0x295/0x480
  [   19.339698]  [] SyS_ioctl+0x79/0x90
  [   19.339702]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [   19.339704] ---[ end trace 4719f8339f6fd57b ]---

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu7 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 15 00:38:10 2015
  ExecutablePath: /lib/systemd/systemd-logind
  MachineType: Hewlett-Packard 300-016d
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=df51fde7-e62f-4a58-ad79-37ef6ab816a8 ro splash quiet vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f537155e6fa :movdqu (%rax),%xmm12
   PC (0x7f537155e6fa) ok
   source "(%rax)" (0x55a3ad00) not located in a known VMA region (needed 
readable region)!
   destination "%xmm12" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:

[Touch-packages] [Bug 1502145] Re: Apps can keep screen lit permanently

2015-10-14 Thread Alexandros Frantzis

I have found a way to deterministically reproduce the issue with
webbrowser-app. Perhaps there are other scenarios that are problematic,
but hopefully this will at least provide some hints. Below are the steps
and between them the USC logs I get for each step, which give some
insight into what is going wrong.

[TL;DR]

The problem seems to be that, for some reason, if after the screen is
turned on and logging in the webbrowser is in focus and playing a video
(which means that the user previously turned off the screen with the
power button while playing a video in the browser) the webbrowser app
leaks (doesn't eventually release) two keepDisplayOn requests ids. This
causes the screen to stay on even when focusing away from it.

[Detailed analysis]

1.  Start browser, start watching a youtube video. The browser requests
keepDisplayOn twice from two different dbus connections, which is
strange, but OK.

[1444841076.023016] usc::UnityScreenService: Received request with serial 3 
from :1.300 : keepDisplayOn 
[1444841076.023390] usc::UnityScreenService: Sending reply for serial 3 to 
:1.300 id: 9 
[1444841077.052913] usc::UnityScreenService: Received request with serial 3 
from :1.301 : keepDisplayOn 
[1444841077.053164] usc::UnityScreenService: Sending reply for serial 3 to 
:1.301 id: 10

2. Turn off screen with power key. Everything is normal the
keepDisplayOn requests are released.

[1444841087.268477] usc::UnityScreenService: Received request with serial 4 
from :1.300 : removeDisplayOnRequest id: 9 
[1444841087.274530] usc::UnityScreenService: Received request with serial 4 
from :1.301 : removeDisplayOnRequest id: 10 

3.  Turn on screen with power key, log in, video should resume. Strange
things happen here, note the extra keepDisplayOn requests this time (4
vs 2 before, and they are all from webbrowser-app)

[1444841106.885474] usc::UnityScreenService: Received request with serial 3 
from :1.302 : keepDisplayOn 
[1444841106.885997] usc::UnityScreenService: Sending reply for serial 3 to 
:1.302 id: 11 
[1444841106.889124] usc::UnityScreenService: Received request with serial 3 
from :1.303 : keepDisplayOn 
[1444841106.889333] usc::UnityScreenService: Sending reply for serial 3 to 
:1.303 id: 12 
[1444841106.895151] usc::UnityScreenService: Received request with serial 3 
from :1.304 : keepDisplayOn 
[1444841106.895258] usc::UnityScreenService: Sending reply for serial 3 to 
:1.304 id: 13 
[1444841106.900406] usc::UnityScreenService: Received request with serial 3 
from :1.305 : keepDisplayOn 
[1444841106.900471] usc::UnityScreenService: Sending reply for serial 3 to 
:1.305 id: 14

4. Focus away from webbrowser (e.g. go to scopes). webbrowser-app
requested 4 keepDisplayOn ids but releases only 2, which causes the
screen to stay on.

[1444841117.298103] usc::UnityScreenService: Received request with serial 4 
from :1.304 : removeDisplayOnRequest id: 13 
[1444841117.307436] usc::UnityScreenService: Received request with serial 4 
from :1.305 : removeDisplayOnRequest id: 14

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

Title:
  Apps can keep screen lit permanently

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  rc-proposed, r140, krillin

  There are times when it seems the display blanking policy stops
  working and the display stays on until I press the power button.

  Steps to reproduce:
  * install and start Siete
  * put it in background

  Expected outcome:
  * the display is switched off after a predetermined amount of time

  Actual outcome:
  * the display stays on forever

  ==

  Now that apps can request the screen to stay on, they can do so
  regardless of whether they're focused/visible or not.

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

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

[Touch-packages] [Bug 1229295] Re: A4 Right margin cut off with HP Deskjet 5550

2015-10-14 Thread TJ

This still affects Okular in 15.10 Wily.

Printing an 84 A5 page PDF duplex  onto A4 every page has extended left
and bottom margins, cropped right and top edges, and also scales
(magnifies) the content.

Using the identical printer settings with Evince ( Document Viewer) the
document prints with correct margins, no scaling, and centred on the
page.

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

Title:
  A4 Right margin cut off with HP Deskjet 5550

Status in cups package in Ubuntu:
  Invalid
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  Here is the example pdf file attached and also two photos of the printed page.
  I used RTL because it demonstrates better the edge that is cut off - the 
right edge.

  This is supposed to be an A4 PDF (the file is attached so you can check).
  And this is supposed to be an A4 (210x297) printout (the printer settings are 
that).

  Blessings,
  Shahar

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Sep 23 19:46:01 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-12 (1077 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Lpstat: device for deskjet_5550: hp:/usb/deskjet_5550?serial=MY28A1R5B42L
  MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3
  MarkForUpload: True
  Papersize: letter
  PpdFiles: deskjet_5550: HP Deskjet 5550, hpcups 3.13.8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic 
root=/dev/mapper/ssd-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash 
vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (138 days ago)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4c
  dmi.board.name: GA-880GMA-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd12/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GMA-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

Hello Andy, or anyone else affected,

Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.7-0ubuntu0.8
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: lxc (Ubuntu Trusty)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

[Touch-packages] [Bug 1506146] Re: package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2015-10-14 Thread 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/1506146

Title:
  package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: uuid-runtime 2.25.2-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  Date: Wed Oct 14 16:06:55 2015
  DuplicateSignature: package:uuid-runtime:2.25.2-4ubuntu3:sub-processo script 
post-installation instalado retornou estado de saída de erro 1
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2015-10-14 (0 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 uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  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/1506146/+subscriptions

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

[Touch-packages] [Bug 1506146] [NEW] package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

2015-10-14 Thread Jose Henrique A Gomes

Public bug reported:

package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: sub-
processo script post-installation instalado retornou estado de saída de
erro 1

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: uuid-runtime 2.25.2-4ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
Date: Wed Oct 14 16:06:55 2015
DuplicateSignature: package:uuid-runtime:2.25.2-4ubuntu3:sub-processo script 
post-installation instalado retornou estado de saída de erro 1
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
InstallationDate: Installed on 2015-10-14 (0 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 uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
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/1506146

Title:
  package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  package uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: uuid-runtime 2.25.2-4ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  Date: Wed Oct 14 16:06:55 2015
  DuplicateSignature: package:uuid-runtime:2.25.2-4ubuntu3:sub-processo script 
post-installation instalado retornou estado de saída de erro 1
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2015-10-14 (0 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 uuid-runtime 2.25.2-4ubuntu3 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  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/1506146/+subscriptions

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

[Touch-packages] [Bug 1500483] Re: [sdk] animate header component when app comes back to the foreground

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

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

Title:
  [sdk] animate header component when app comes back to the foreground

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

Bug description:
  When the header is hidden by scrolling it out of the view in an app,
  and the user switches between apps, when an app comes back to the
  foreground, the header instantly appears again. This means when going
  back to a previous app, the app is not in exactly the same state as
  where the user left it.

  Example:
  - Open gallery-app
  - Scroll down to hide the header (you need to have enough photos in the 
gallery to scroll down).
  - Long left/right edge swipe to hide send the gallery-app to the background
  - Re-open the gallery app

  Result:
  The gallery-app re-opens with the header visible.

  This can be confusing for the user.
  Two possible solutions:
  1. Show the header when re-opening the app, but animate it so the user knows 
what is happening
  2. Don't do anything. Header stays hidden and the user can show it as they 
normally would.

  After discussing with Olga, we decided to go for solution 1. The
  header will show, but it must animate.

  
  -- UX comment -

  As described above: 
  The header should animate once user navigates back to the app.

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

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

[Touch-packages] [Bug 1421923] Re: No notifications for new mails

2015-10-14 Thread Pat McGowan

** Tags added: default

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

Title:
  No notifications for new mails

Status in Online Accounts: Account plugins:
  New
Status in Dekko:
  Triaged
Status in account-plugins package in Ubuntu:
  In Progress
Status in account-polld package in Ubuntu:
  In Progress

Bug description:
  Hi!

  In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new
  mails.

  Testing (by example)
  1. Kill Dekko.
  2. Send you an email.
  3. Open Dekko.
  4. Change quickly to another app before Dekko starts.
  5. Bug: No notification
  6. Go to Dekko: You'll see your new mail.

  FYI as improvement, for me, in Dekko is not clear if Dekko checks the
  mail after X minutes or is a push notification.

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1421923/+subscriptions

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

[Touch-packages] [Bug 1062155] Re: Preview buttons don't adapt to the text size

2015-10-14 Thread Alex Baggott

As part of the big bug review for 16.04 LTS, I have tested this on 15.10
and the bug is still there.

** Tags added: desktop-bugscrub-triaged

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

Title:
  Preview buttons don't adapt to the text size

Status in Unity:
  Confirmed
Status in Unity Videos Lens:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-lens-video package in Ubuntu:
  Confirmed

Bug description:
  Preview buttons should stretch to adapt to the text inside.
  For me, in French, I only notice this problem in the video lens.
  Doing a preview on the very same file in the home lens displays big enough 
buttons (please see the attached screenshots).

  However, the problem may occur on other lenses too with longer
  translations (I did not test).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity-lens-video 0.3.12-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  5 11:36:32 2012
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121004)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-lens-video
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 603415] Re: Unity should have a screen magnifier

** Changed in: unity
   Importance: Undecided => High

** Changed in: unity (Ubuntu)
   Importance: Wishlist => High

** Changed in: unity
 Assignee: (unassigned) => Eleni Maria Stea (hikiko)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Eleni Maria Stea (hikiko)

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

** Changed in: nux
   Status: New => Triaged

** Changed in: nux
   Importance: Undecided => High

** Changed in: nux
 Assignee: (unassigned) => Eleni Maria Stea (hikiko)

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

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

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

** Changed in: nux (Ubuntu)
 Assignee: (unassigned) => Eleni Maria Stea (hikiko)

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

** Changed in: compiz
   Importance: Undecided => High

** Changed in: compiz
 Assignee: (unassigned) => Eleni Maria Stea (hikiko)

** Tags added: rls-w-incoming

** Branch linked: lp:~hikiko/unity/unity.new-ezoom

** Branch linked: lp:~hikiko/nux/nux.allow-custom-transformations-in-
drawing-functions

** Branch linked: lp:~hikiko/unity/unity.allow-compiz-transforms-in-nux-
stack

** Branch linked: lp:~hikiko/compiz/compiz.shared-transform-ezoom

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

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

** Changed in: compiz (Ubuntu)
 Assignee: (unassigned) => Eleni Maria Stea (hikiko)

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

Title:
  Unity should have a screen magnifier

Status in Compiz:
  In Progress
Status in Nux:
  Triaged
Status in Unity:
  Triaged
Status in compiz package in Ubuntu:
  In Progress
Status in nux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-control-center

  In gnome-keybindings-properties, in the Accessibility section, there
  are three entries by default: toggle magnifier, toggle screen reader,
  and toggle on-screen keyboard. None of these work, whether or not
  Assistive Technologies is currently running and whether or not orca is
  currently running.

  WHAT I EXPECT TO HAPPEN: I should be able to configure a shortcut to
  any of these actions, such as Ctrl-Alt-A to the Toggle magnifier
  action. Then, pressing, Ctrl-Alt-A will start the magnifier.

  WHAT ACTUALLY HAPPENS: I am able to modify the entry in the gnome-
  keybindings-properties window, but pressing the designated key does
  not perform any action. That is, the magnifier does not open. Changing
  the hotkeys for other actions works okay.

  WHY THIS IS BAD: This is confusing and misleading behavior, and can be
  especially damaging for people who need the accessibility features.
  Ideally, the keybindings should be fixed, but otherwise they should be
  removed from the dialog.

  This is true under up-to-date Lucid 10.04 tested on several systems.

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

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

[Touch-packages] [Bug 1489816] Re: gstreamer/rhythmbox submits invalid Disc IDs to MusicBrainz (Trusty Tahr)

2015-10-14 Thread Michael Terry

** No longer affects: rhythmbox (Ubuntu)

** Also affects: gst-plugins-base1.0 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: gst-plugins-base1.0 (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: gst-plugins-base1.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gstreamer/rhythmbox submits invalid Disc IDs to MusicBrainz (Trusty
  Tahr)

Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 source package in Trusty:
  Confirmed

Bug description:
  Gstreamer calculates an ID for Audio CDs and optionally submits it to 
MusicBrainz.
  This enables programs to find the corresponding metadata for a CD on 
MusicBrainz.

  Gstreamer < 1.3.1 doesn't do this correctly for CDs with data tracks,
  leading to invalid Disc IDs being submitted to the MusicBrainz
  database.

  This is reported upstream in https://bugzilla.gnome.org/show_bug.cgi?id=708991
  and fixed in gstreamer 1.3.1. The corresponding patch is supplied as an 
attachment here.
  Trusty Tahr is using 1.2.x and there is no new release on that branch.
  Trusty Tahr is still supported until 2019. It would be really nice if that 
can be fixed.

  The bug surfaces as a problem in Rhythmbox because starting with 2.97
  this uses gstreamer for MusicBrainz Disc ID handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1489816/+subscriptions

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

[Touch-packages] [Bug 1432871] Re: `df` shows bind mounts instead of real mounts.

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

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

Title:
`df` shows bind mounts instead of real mounts.

Bug description:
[Impact]

* df displays bind mounts instead of "real" mounts if the bind mount
is mounted to a shorter directory.

* justification - When trusty moved to using /proc/mounts this
changed behavior from precise. Additionally it doesn't make sense
that a bind mount should show up in df over a real root mount.

[Test Case]

* $ mount

192.168.1.2:/raid on /raid type nfs
/dev/sdc5 on /data type ext4 (rw)

/data/a on /a type none (rw,bind)
/raid/temp on /b type none (rw,bind)

$df
Filesystem 1K-blocks Used Available Use% Mounted on

/data/a 449830616 229975284 196982196 54% /a
/raid/temp 7752072192 5581343744 1780023296 76% /b

I'd expect to see the real mount prioritized over the bind mount. Like so.
$df
Filesystem 1K-blocks Used Available Use% Mounted on

/dev/sdc5449830616 229975284 196982196 54% /data
192.168.1.2:/raid 7752072192 5581438976 1779929088 76% /raid

[Regression Potential]

* Patch is upstreamed.

* df command now relies on /proc/self/mountinfo

[Other Info]

Depending on mount path length df sometimes prioritizes showing bind mounts
over real mounts

for example.
$ mount

192.168.1.2:/raid on /raid type nfs
(rw,nosuid,nodev,noexec,vers=4,addr=192.168.1.2,clientaddr=192.168.1.3)
/dev/sdc5 on /data type ext4 (rw)

/data/a on /a type none (rw,bind)
/raid/temp on /b type none (rw,bind)

$df
Filesystem 1K-blocks Used Available Use% Mounted on

/data/a 449830616

[Touch-packages] [Bug 992697] Re: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken

** Tags added: rls-w-incoming

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

Title:
  Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window
  placement shortcuts are broken

Status in Autopilot:
  Fix Released
Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Released
Status in Compiz 0.9.10 series:
  Fix Released
Status in Unity:
  Fix Released
Status in autopilot package in Ubuntu:
  Fix Released
Status in compiz package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  The "Ctrl + Alt + numpad 4" and "Ctrl + Alt + numpad 6" keyboard
  shortcuts are not working in 13.04.

  See bug #878820 for the full specification of the numpad window
  placement shortcuts. Quoting from this bug:

  "Ctrl-Alt-Numpad 4 - Place window on the left side of the screen in
  *semi-maximised* state (it is important that the window is actually
  semi-maximised, not just the same size and position as a semi-
  maximised window) Pressing a second time does nothing.

  Ctrl-Alt-Numpad 6 - Place window on the right side of the screen (it
  is important that the window is actually semi-maximised, not just the
  same size and position as a semi-maximised window). Pressing a second
  time does nothing."

  HOWTO:

  The solution we want here are additional shortcuts to semi-maximize
  windows vertically and move them to left/right half of the screen...

  The best way to achieve that:

  1. Remove the changing of the standard shortcuts by 
debian/patches/ubuntu-config.patch, so the original ones will work again.
  2. Add 2 quasi-duplicated shortcuts with the functions to semi-maximize 
windows vertically and move them to left/right half of the screen to Grid and 
make those functions use "Ctrl + Super + Cursor Left or Right" on Ubuntu.

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

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

[Touch-packages] [Bug 959323] Re: compiz crashed with SIGSEGV in af_face_globals_is_digit() from af_loader_load_g() from af_loader_load_glyph() from af_autofitter_load_glyph() from FT_Load_Glyph() fro

** Tags added: rls-w-incoming

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

Title:
  compiz crashed with SIGSEGV in af_face_globals_is_digit() from
  af_loader_load_g() from af_loader_load_glyph() from
  af_autofitter_load_glyph() from FT_Load_Glyph() from
  _cairo_ft_scaled_glyph_init() from ... from nux::TextEntry::DrawText()

Status in Nux:
  Invalid
Status in Unity:
  Invalid
Status in Unity 5.0 series:
  Invalid
Status in nux package in Ubuntu:
  Invalid

Bug description:
  While starting up the system, hit Super key and started typing in
  'liferea'. Got as far as 'life'

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: libnux-2.0-0 2.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
  Uname: Linux 3.2.0-19-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Mar 19 10:22:37 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcCmdline: compiz
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f3b3e1438a3:cmp0x8(%rdx),%rax
   PC (0x7f3b3e1438a3) ok
   source "0x8(%rdx)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nux
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: compiz crashed with SIGSEGV in FT_Load_Glyph()
  UpgradeStatus: Upgraded to precise on 2012-03-10 (8 days ago)
  UserGroups: adm cdrom dip lpadmin mythtv plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1495943] Re: gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

2015-10-14 Thread Bug Watch Updater

** Changed in: glib
   Status: Incomplete => Fix Released

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

Title:
  gvfs-trash doesn't add "trash::" attrs to file which is moved to Trash

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed
Status in glib2.0 package in Debian:
  Confirmed

Bug description:
  [System]

  Ubuntu MATE 15.10, fully updated.

  [Steps to reproduce]

  1. Create an empty file: touch ~/test
  2. Move it to trash: gvfs-trash ~/test
  3. Launch some file manager, browse Trash folder and try to restore the file. 
I've tested it with the following file managers: Caja, Nemo, Nautilus and 
Thunar.

  [Expected result]

  The file should be restored to its original location.

  [What happens instead]

  The file manager complains that it can't determine the original
  location of the file, and so doesn't restore it.

  [Details]

  When moving file to Trash, gvfs-trash does not add trash::orig-path
  and trash::deletion-date attributes to it. Without that the file
  manager can't determine the original location of the file, and hence
  can't restore it.

  You can check the file attributes by printing the moved file's info:
  gvfs-info trash:///test

  [Regression description]

  Restoring the files has been working fine in Ubuntu 14.04 and 15.04.
  This bug appeared only in 15.10, so it's a regression.

  You can see the gvfs-info output from 15.04 and 15.10 in the
  attachments below.

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

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

[Touch-packages] [Bug 1505302] Re: core_pattern is incorrect on boot with crash reporting enabled

2015-10-14 Thread Ken VanDine

** Changed in: apport (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  core_pattern is incorrect on boot with crash reporting enabled

Status in Canonical System Image:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  current build number: 136
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  On rc-proposed with crash reporting enabled core_pattern is incorrect on boot:
  $ cat /proc/sys/kernel/core_pattern
  /bad_core_pattern

  Instead of:
  |/usr/share/apport/apport %p %s %c %P

  and crash reporting is disabled while it should be enabled.

  According to the apport.log attached, core_pattern should be set
  correctly.

  If the user disables/enables crash reporting the pattern is correct.

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

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

[Touch-packages] [Bug 1229295] Re: A4 Right margin cut off with HP Deskjet 5550

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

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

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

Title:
  A4 Right margin cut off with HP Deskjet 5550

Status in cups package in Ubuntu:
  Invalid
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  Here is the example pdf file attached and also two photos of the printed page.
  I used RTL because it demonstrates better the edge that is cut off - the 
right edge.

  This is supposed to be an A4 PDF (the file is attached so you can check).
  And this is supposed to be an A4 (210x297) printout (the printer settings are 
that).

  Blessings,
  Shahar

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Sep 23 19:46:01 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-10-12 (1077 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  Lpstat: device for deskjet_5550: hp:/usb/deskjet_5550?serial=MY28A1R5B42L
  MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3
  MarkForUpload: True
  Papersize: letter
  PpdFiles: deskjet_5550: HP Deskjet 5550, hpcups 3.13.8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-8-generic 
root=/dev/mapper/ssd-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash 
vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (138 days ago)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4c
  dmi.board.name: GA-880GMA-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd12/06/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GMA-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1506159] Re: systemd-logind crashed with SIGSEGV in strlen()

2015-10-14 Thread Thomas Christensen

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

** Description changed:

+ I've got this feeling that it happens because I boot on HDMI display.
+ 
+ When booting with screen of it doesn't show the below, but as soon as
+ the screen is on and I log in it happens.
+ 
+ Likely related is that I cannot set a wallpaper.
+ 
  [   19.339471] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in 
ips_enabled (expected 1, found 0)
  [   19.339476] [ cut here ]
  [   19.339493] WARNING: CPU: 0 PID: 249 at 
/build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c
  [   19.339494] pipe state doesn't match!
  [   19.339495] Modules linked in: nls_iso8859_1 intel_rapl iosf_mbi 
x86_pkg_temp_thermal intel_powerclamp coret
  [   19.339533]  acpi_als kfifo_buf industrialio parport_pc ppdev lp parport 
autofs4 hid_generic usbhid uas usb_
  [   19.339551] CPU: 0 PID: 249 Comm: plymouthd Tainted: P   OE   
4.2.0-16-generic #19-Ubuntu
  [   19.339553] Hardware name: Hewlett-Packard 300-016d/2B38, BIOS 80.03 
12/15/2014
  [   19.339554]   2594191b 880078dcf7c8 
817e8c09
  [   19.339557]   880078dcf820 880078dcf808 
8107b3c6
  [   19.339559]  880078dcf848 880078dcf8b0 88003f61a000 
0001
  [   19.339562] Call Trace:
  [   19.339567]  [] dump_stack+0x45/0x57
  [   19.339572]  [] warn_slowpath_common+0x86/0xc0
  [   19.339574]  [] warn_slowpath_fmt+0x55/0x70
  [   19.339589]  [] ? intel_pipe_config_compare+0xb31/0xc60 
[i915]
  [   19.339602]  [] check_crtc_state+0x2c5/0x440 [i915]
  [   19.339619]  [] intel_modeset_check_state+0x21d/0x6d0 
[i915]
  [   19.339633]  [] intel_crtc_set_config+0x4c7/0x580 [i915]
  [   19.339647]  [] ? drm_mode_create+0x25/0x60 [drm]
  [   19.339659]  [] drm_mode_set_config_internal+0x66/0x100 
[drm]
  [   19.339671]  [] drm_mode_setcrtc+0x3e9/0x500 [drm]
  [   19.339679]  [] drm_ioctl+0x125/0x610 [drm]
  [   19.339691]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
  [   19.339695]  [] do_vfs_ioctl+0x295/0x480
  [   19.339698]  [] SyS_ioctl+0x79/0x90
  [   19.339702]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [   19.339704] ---[ end trace 4719f8339f6fd57b ]---
  
  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu7 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Thu Oct 15 00:38:10 2015
  ExecutablePath: /lib/systemd/systemd-logind
  MachineType: Hewlett-Packard 300-016d
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=df51fde7-e62f-4a58-ad79-37ef6ab816a8 ro splash quiet vt.handoff=7
  SegvAnalysis:
-  Segfault happened at: 0x7f537155e6fa :movdqu (%rax),%xmm12
-  PC (0x7f537155e6fa) ok
-  source "(%rax)" (0x55a3ad00) not located in a known VMA region (needed 
readable region)!
-  destination "%xmm12" ok
+  Segfault happened at: 0x7f537155e6fa :movdqu (%rax),%xmm12
+  PC (0x7f537155e6fa) ok
+  source "(%rax)" (0x55a3ad00) not located in a known VMA region (needed 
readable region)!
+  destination "%xmm12" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
-  strlen () at ../sysdeps/x86_64/strlen.S:106
-  __GI___strdup (s=0x55a3ad00 ) at strdup.c:41
-  ?? ()
-  ?? ()
-  ?? ()
+  strlen () at ../sysdeps/x86_64/strlen.S:106
+  __GI___strdup (s=0x55a3ad00 ) at strdup.c:41
+  ?? ()
+  ?? ()
+  ?? ()
  Title: systemd-logind crashed with SIGSEGV in strlen()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-06 (8 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 12/15/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.03
  dmi.board.asset.tag: 3CR51306RT
  dmi.board.name: 2B38
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: 3CR51306RT
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.03:bd12/15/2014:svnHewlett-Packard:pn300-016d:pvr:rvnHewlett-Packard:rn2B38:rvr1.02:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 300-016d
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  systemd-logind crashed with SIGSEGV in strlen()

Status in systemd package in Ubuntu:
  New

Bug description:
  I've got this feeling that it happens because I boot on HDMI display.

  When booting with screen of it doesn't show the below,

[Touch-packages] [Bug 1495408] Re: Black square in header

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

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

Title:
  Black square in header

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

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

  Same on latest arale

  There is a black square in the header in several applications
  (address-book, messaging, dialler, cf screenshots)

  To display the black square:
  - dialler: open 'Recent calls'
  - messaging: tap on a message and go back
  - contact: tap on a contact

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

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

[Touch-packages] [Bug 1498863] Re: Scenarios in ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page fail with autopilot.exceptions.StateNotFoundError

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

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

Title:
  Scenarios in
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page
  fail with autopilot.exceptions.StateNotFoundError

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

Bug description:
  Some of the scenarios
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page
  in fail with the following error:

  autopilot.exceptions.StateNotFoundError: Object not found with name
  '*' and properties {'objectName': 'header_title_label', 'text':
  'Pickers'}

  As can be seen in all of these cases the page is being selected but
  only rendered with considerable delay, causing AutoPilot to try
  selecting the object too early.

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

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

[Touch-packages] [Bug 1402195] Re: Newer version of adb needed for nexus 5

2015-10-14 Thread H.-Dirk Schmitt

** Bug watch added: Debian Bug tracker #798305
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798305

** Also affects: android-tools (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798305
   Importance: Unknown
   Status: Unknown

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

Title:
  Newer version of adb needed for nexus 5

Status in android-tools package in Ubuntu:
  Triaged
Status in android-tools source package in Vivid:
  Won't Fix
Status in android-tools package in Debian:
  Unknown

Bug description:
  When adb sideloading 5.0.0 -> 5.0.1, the recovery on a nexus 5
  requires at least adb 1.0.32

  $ adb version
  Android Debug Bridge version 1.0.31

  :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: android-tools-adb 4.2.2+git20130218-3ubuntu36
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 13 14:47:38 2014
  InstallationDate: Installed on 2014-02-07 (308 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: android-tools
  UpgradeStatus: Upgraded to utopic on 2014-11-08 (34 days ago)

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

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

[Touch-packages] [Bug 1406641] Re: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

This bug was fixed in the package gconf - 3.2.6-3ubuntu4

---
gconf (3.2.6-3ubuntu4) wily; urgency=medium

  * update-gconf-defaults, gconf-schemas: encode and decode from UTF-8
to avoid postinst failing when schemas contain non ascii chars.
(LP: #1504442, #1406641)

 -- Didier Roche   Wed, 14 Oct 2015 10:09:59 +0100

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

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

Title:
  package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in gconf package in Ubuntu:
  Fix Released

Bug description:
  Used command : sudo apt-get install gconf-editor

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gconf2 3.2.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  AptOrdering:
   gconf-defaults-service: Install
   gconf-editor: Install
   gconf-defaults-service: Configure
   gconf-editor: Configure
  Architecture: amd64
  Date: Tue Dec 30 21:09:48 2014
  DuplicateSignature: package:gconf2:3.2.6-0ubuntu2:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2014-02-10 (322 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gconf
  Title: package gconf2 3.2.6-0ubuntu2 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: Upgraded to trusty on 2014-11-08 (52 days ago)

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

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

[Touch-packages] [Bug 1504442] Re: gconf-schemas crashed with UnicodeDecodeError in decode(): 'ascii' codec can't decode byte 0xc4 in position 5548: ordinal not in range(128)