[Touch-packages] [Bug 1394063] Re: Inspiron 3137 brightness keys aren't recognized

[Martin Pitt]

Thanks, so as the KEY_BRIGHTNESS{UP/DOWN} evdev events are correctly
generated this isn't an udev regression.  Thus reassigning to settings-
daemon for now, as this is the component that is supposed to react to
these keys. This might likely be fallout from the upower 0.9 → 0.99
transition.

** Package changed: systemd (Ubuntu) => unity-settings-daemon (Ubuntu)

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

Title:
  [vivid regression] brightness keys aren't recognized

Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1394063/+subscriptions

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

[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

[Vsevolod Velichko]

Affects me too.

I have Unity and 14.10 upgraded from 14.04,  Dell E7240 notebook with Core 
i7-4600U and integrated Intel Haswell-ULT video.
First the problem seemed to appear after upgrade when I decided to try unity8 
and installed it packages (the graphics remained slow even when I was in 
classic Unity session), and everything disappeared, when I removed unity8.
Now the problem reappeared, and I found unity8 installed again. So I removed it 
with all the stuff depended on it and the is likely went away again.
WARNING: if anyone would try my method, it removes indicator-network. I myself 
prefer nm-applet, it requires network-manager-gnome to be installed.

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

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics

  After upgrading from 14.04 to 14.10 there are a lot of places where
  the graphics are working much slower than they were before:

  - Gnome Shell Interface is very sluggish, visible "chops" (redrawing)
  when pressing the [Super] key.

  - Selecting text in Gedit takes a full second pr. line

  Experiences some subjective improvement when I booted kernel 3.13.0-37
  instead of 3.16.0-23, but that may be my imagination as the problem
  persists.

  I've searched google, forums, found a couple of relevant links that
  point to the issue being the Intel drivers.

  http://askubuntu.com/questions/53962...E2%86%92-14-10
  http://www.webupd8.org/2014/10/ubunt...ent-1652086424

  But the drivers currently in 14.10 should be newer than those supplied
  by Intel to 14.04 so that doesn't make sense to me. As one Intel
  developer wrote:

  "I would like to point out that since what we do is bring more ecent
  versions of the software to the target distributions than they ship
  with, a 14.04 targeted installer is unlikely to bring much to a 14.10
  installation, which most likely has the same or more recent versions
  already anyway."

  Source: https://01.org/linuxgraphics/node/375

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 28 15:24:30 2014
  DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-06-14 (135 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Oct 28 13:44:57 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

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

[Touch-packages] [Bug 1393915] Re: uuidgen --random requires an argument

[Martin Pitt]

This indeed happens in 14.04 LTS, but is fixed with util-linux 2.25 in
Ubuntu 14.10 and vivid.

** Changed in: util-linux (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  uuidgen --random requires an argument

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  The man page of 'uuidgen' reports the options -r and --random as
  equivalent:

 -r, --random
Generate a random-based UUID.  This method creates a UUID 
consisting  mostly  of  random
bits.   It  requires that the operating system have a high 
quality random number genera‐
tor, such as /dev/random.

  But --random requires an argument:

  kurt@rodin:~$ uuidgen -r
  4aca676a-a3f1-4217-a35d-031c376c6274
  kurt@rodin:~$ uuidgen --random
  uuidgen: option '--random' requires an argument

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

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

[Touch-packages] [Bug 1341539] Re: Dell XPS L502x Ubuntu 14.04 freeze sometimes

[Christopher M. Penalver]

sdia, thank you for your comment. So your hardware and problem may be tracked, 
could you please file a new report with Ubuntu by executing the following in a 
terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: 
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: 
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: 
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug
report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

Title:
  Dell XPS L502x Ubuntu 14.04 freeze sometimes

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  When I'm using Ubuntu 14.4 the system sometimes freeze, I can unfreeze
  entering into console mode and then going out from this mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 14 13:24:44 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationDate: Installed on 2014-05-08 (66 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1341539] Re: Dell XPS L502x Ubuntu 14.04 freeze sometimes

[sdia]

I am facing the same problem but more frequently. I did not have this
freezing problem with  Ubuntu 12.04 on my Dell XPS L502x. Once I
installed 14.04 this freezing problem started. Sometimes to unfreeze
entering into console mode and then going out works else need to reboot
the system.

I have been looking for a solution for quite a while now and have not
found a fix. I am contemplating going back to 12.04!

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

Title:
  Dell XPS L502x Ubuntu 14.04 freeze sometimes

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  When I'm using Ubuntu 14.4 the system sometimes freeze, I can unfreeze
  entering into console mode and then going out from this mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 14 13:24:44 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationDate: Installed on 2014-05-08 (66 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone

[Timo Jyrinki]

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => 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/1384776

Title:
  Occasional hang in unity 8 dash on the phone

Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Opinion
Status in “unity8” package in Ubuntu RTM:
  Opinion

Bug description:
  The dash is sometimes hanging on the phone.

  See the attached backtrace.

  The issue is as follows: we are maintaining a client-side tree of all
  NetworkManager devices.  When we see that a new device has been added,
  we query its properties in order to build our local proxy.  Doing this
  means that we are making QtDBus calls from a signal handler.  Due to a
  bug in QtDBus this is not safe.

  libdbus-1 has a recursive lock on its DBusConnection.  When the signal
  arrives, the lock is acquired and the sginal handler is run.  The
  signal handler can make DBus calls (which also require the lock)
  because the lock is recursive.  QtDBus also has a lock that is always
  acquired before the libdbus-1 connection lock is acquired.

  Unfortuntaely, the QtDBus lock is not acquired in the case of the
  incoming call from DBus -- only the DBus lock is.

  
  If another thread tries to do an unrelated DBus call meanwhile, it will 
acquire the QtDBus lock first and then the DBus lock (which is held because of 
the signal that arrived).  Once the signal handler gets to the point of wanting 
to make a DBus call (in order to query the properties of the just-added network 
device) it will attempt to acquire the QtDBus lock.  This is a lock-inversion 
deadlock.

  There are at least three bugs here:

  1) QtDBus should be fixed in order to avoid this sort of lock
  inversion problem.  Even if we fix this one situation, it seems quite
  likely that issues like this will arise again.

  2) QNetworkManager should avoid the issue in QtDBus until such a time
  as it is fixed.  This could be done by dispatching to a worker thread
  on receipt of signals so that the queries are done in a fresh call
  stack (without the libdbus-1 lock held).

  3) Apparently the only reason we are using NetworkManager at all is in
  order to know if we are on a 3G connection or not (in order to avoid
  too much data charges).  This would be much easier to do if
  NetworkManager provided a property that we could watch directly
  instead of bringing up an entire tree of objects in order to answer a
  very simple question.  To that end I've filed
  https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can
  hopefully get addressed relatively quickly.

  
  I consider 3) to be the real fix as far as we are concerned, but we should 
probably ensure that the Qt people know about 1) and 2).  Either of those could 
function as a workaround for us in the meantime, but the idea that we are 
creating this complex object tree to answer a simple question is ridiculous, so 
we should really fix that directly.

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

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

[Touch-packages] [Bug 1394080] Re: ScopesWatcher behavior doesn't agree with Registry test

[Michi Henning]

Full console log attached.

** Attachment added: "Full console log"
   
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394080/+attachment/4263478/+files/failed-registry-test.html

** Description changed:

  Just had a failure on Arm on Jenkins. It looks like we are emitting two
  "uninstalled" events in some cases, even though only one scope is
  removed. This is reproducable locally.
  
  There is also an issue around install. Locally, we get one event for
  testscopeC being installed but, on Jenkins, the trace shows two events.
  In turn, the test doesn't expect that.
  
  Something is fishy here, and it looks like the ScopesWatcher could do
  with some refactoring.
  
- Failed test below. Line numbers are consistent with r531 of devel.
- 
- 63: Test command: 
/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/Registry_test
- 63: Test timeout computed to be: 1500
- 63: load average: 0.69 1.80 1.91
- 63: [==] Running 6 tests from 1 test case.
- 63: [--] Global test environment set-up.
- 63: [--] 6 tests from Registry
- 63: [ RUN  ] Registry.metadata
- 63: scoperegistry [Registry test]: unity::FileException: cannot open scope 
installation directory "/unused": No such file or directory (errno = 2)
- 63: scoperegistry [Registry test]: could not open OEM installation directory, 
ignoring OEM scopes
- 63: scoperegistry [Registry test]: unity::FileException: cannot open scope 
installation directory 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/click":
 No such file or directory (errno = 2)
- 63: scoperegistry [Registry test]: could not open Click installation 
directory, ignoring Click scopes
- 63: scoperegistry [Registry test]: no remote registry configured, only local 
scopes will be available
- 63: [   OK ] Registry.metadata (166 ms)
- 63: [ RUN  ] Registry.scope_state_notify
- 63: RegistryObject::ScopeProcess::exec(): Process for scope: "testscopeA" 
started
- 63: RegistryObject::ScopeProcess::exec(): Process for scope: "testscopeB" 
started
- 63: RegistryObject::ScopeProcess::on_process_death(): Process for scope: 
"testscopeB" exited
- 63: [   OK ] Registry.scope_state_notify (2235 ms)
- 63: [ RUN  ] Registry.no_idle_timeout_in_debug_mode
- 63: ScopesWatcher: scope: "testscopeC" installed to: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: ScopesWatcher: scope: "testscopeC" installed to: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: ScopesWatcher: scope: "testscopeC" installed to: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: RegistryObject::ScopeProcess::exec(): Process for scope: "testscopeC" 
started
- 63: RegistryObject::ScopeProcess::on_process_death(): Process for scope: 
"testscopeC" exited
- 63: ScopesWatcher: scope: "testscopeC" uninstalled from: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: ScopesWatcher: scope: "testscopeC" uninstalled from: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: [   OK ] Registry.no_idle_timeout_in_debug_mode (5215 ms)
- 63: [ RUN  ] Registry.manually_started_scope
- 63: ScopesWatcher: scope: "testscopeC" installed to: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: RegistryObject::ScopeProcess: Process for scope: "testscopeC" started 
manually
- 63: RegistryObject::ScopeProcess: Manually started process for scope: 
"testscopeC" exited
- 63: ScopesWatcher: scope: "testscopeC" uninstalled from: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: ScopesWatcher: scope: "testscopeC" uninstalled from: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/scopes/testscopeC"
- 63: [   OK ] Registry.manually_started_scope (1145 ms)
- 63: [ RUN  ] Registry.list_update_notify_before_click_folder_exists
- 63: Create click folder: 
/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/click
- 63: Make a symlink to testscopeC in the scopes folder
- 63: ScopesWatcher: scope: "testscopeC" installed to: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/click/testscopeC"
- 63: ScopesWatcher: scope: "testscopeC" installed to: 
"/tmp/buildd/unity-scopes-api-0.6.8bzr531pkg0vivid27/obj-arm-linux-gnueabihf/test/gtest/scopes/Registry/click/testscopeC"
- 63: Remove click folder
- 63: Sco

[Touch-packages] [Bug 1394081] [NEW] Add manual options for administrators

[HeinMueck]

Public bug reported:


Currently - trusty LTS - there is no way to turn off the regeneration of 
/etc/resolv.conf that would survive a package upgrade. 

- you cannot remove resolvconf as it is needed by minimal
- you cannot disable-upgrades as this flag is removed by reboots
- if you disable the resolvconf job in upstart package upgrade will reset the 
disable-upgrade flags
- if you hack the scripts - it will only last until the next upgrade

There are two ways to ensure that admins willing to turn it off can do
so:

First solution: add a run=no to /etc/default/resolvconf and bail out if
it is set.

The second solution is more subtile. In /etc/network/if-
up.d/000resolvconf you will find this line:

[ -x /sbin/resolvconf ] || exit 0

While in /etc/dhcp/dhclient-enter-hooks.d/resolvconf it says

if [ -x /sbin/resolvconf ] && [ -L /etc/resolv.conf ]; then

Way more clever! So if you do not want to implement the default option,
why not check if its a link all the way? So at least a conf gets not
overwritten once the admin wrote his own.

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

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

Title:
  Add manual options for administrators

Status in “resolvconf” package in Ubuntu:
  New

Bug description:
  
  Currently - trusty LTS - there is no way to turn off the regeneration of 
/etc/resolv.conf that would survive a package upgrade. 

  - you cannot remove resolvconf as it is needed by minimal
  - you cannot disable-upgrades as this flag is removed by reboots
  - if you disable the resolvconf job in upstart package upgrade will reset the 
disable-upgrade flags
  - if you hack the scripts - it will only last until the next upgrade

  There are two ways to ensure that admins willing to turn it off can do
  so:

  First solution: add a run=no to /etc/default/resolvconf and bail out
  if it is set.

  The second solution is more subtile. In /etc/network/if-
  up.d/000resolvconf you will find this line:

  [ -x /sbin/resolvconf ] || exit 0

  While in /etc/dhcp/dhclient-enter-hooks.d/resolvconf it says

  if [ -x /sbin/resolvconf ] && [ -L /etc/resolv.conf ]; then

  Way more clever! So if you do not want to implement the default
  option, why not check if its a link all the way? So at least a conf
  gets not overwritten once the admin wrote his own.

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

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

[Touch-packages] [Bug 1394080] [NEW] ScopesWatcher behavior doesn't agree with Registry test

[Michi Henning]

Public bug reported:

Just had a failure on Arm on Jenkins. It looks like we are emitting two
"uninstalled" events in some cases, even though only one scope is
removed. This is reproducable locally.

There is also an issue around install. Locally, we get one event for
testscopeC being installed but, on Jenkins, the trace shows two events.
In turn, the test doesn't expect that.

Something is fishy here, and it looks like the ScopesWatcher could do
with some refactoring.

Console log attached. Line numbers are consistent with r531 of devel.

** Affects: unity-scopes-api (Ubuntu)
 Importance: High
 Assignee: Michi Henning (michihenning)
 Status: Confirmed

** Changed in: unity-scopes-api (Ubuntu)
   Importance: Undecided => High

** Changed in: unity-scopes-api (Ubuntu)
 Assignee: (unassigned) => Michi Henning (michihenning)

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

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

Title:
  ScopesWatcher behavior doesn't agree with Registry test

Status in “unity-scopes-api” package in Ubuntu:
  Confirmed

Bug description:
  Just had a failure on Arm on Jenkins. It looks like we are emitting
  two "uninstalled" events in some cases, even though only one scope is
  removed. This is reproducable locally.

  There is also an issue around install. Locally, we get one event for
  testscopeC being installed but, on Jenkins, the trace shows two
  events. In turn, the test doesn't expect that.

  Something is fishy here, and it looks like the ScopesWatcher could do
  with some refactoring.

  Console log attached. Line numbers are consistent with r531 of devel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1394080/+subscriptions

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

[Touch-packages] [Bug 1237045] Re: Ubuntu UI Toolkit no longer builds on precise, quantal and raring

[Zoltan Balogh]

The listed series are not targets fro the UITK anymore

** Changed in: ubuntu-ui-toolkit
   Status: Confirmed => Won't Fix

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

Title:
  Ubuntu UI Toolkit no longer builds on precise, quantal and raring

Status in Thumbnail generator for all kinds of files:
  Fix Released
Status in Ubuntu UI Toolkit:
  Won't Fix
Status in “thumbnailer” package in Ubuntu:
  Fix Released

Bug description:
  If you take a look at ppa:ubuntu-sdk-team/ppa, you'll find that
  ubuntu-ui-toolkit no longer builds for raring, quantal and precise.
  Which means developers would have to use saucy to use the sdk.

  The issue is libthumbnailer, which also doesn't build on those same
  architectures (thumbnailer is also in the same PPA).

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

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

[Touch-packages] [Bug 1194916] Re: Copyright files need to license assets separately from code

[Zoltan Balogh]

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

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

Title:
  Copyright files need to license assets separately from code

Status in Address Book App:
  Fix Released
Status in Camera App:
  Fix Released
Status in Gallery App:
  Fix Released
Status in Media Player App:
  In Progress
Status in Notes App:
  Confirmed
Status in Ubuntu UI Toolkit:
  Fix Released
Status in Web Browser App:
  Fix Released
Status in “camera-app” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “mediaplayer-app” package in Ubuntu:
  Fix Released
Status in “notes-app” package in Ubuntu:
  Confirmed
Status in “share-app” package in Ubuntu:
  Invalid
Status in “webbrowser-app” package in Ubuntu:
  Fix Released
Status in “mediaplayer-app” package in Ubuntu RTM:
  Fix Released

Bug description:
  The visual assets included with the applications and sdk should use
  the Creative Commons Attribution-ShareAlike 3.0 license. The specific
  folders containing the images will be called out. In some cases
  */assets/* will suffice but not in all.

  The attached file is for the camera-app as an example of the proper
  format.

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

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

[Touch-packages] [Bug 1186381] Re: Can not paste into web forms

[Mitchell]

Yep, this is a massive and major oversite - love the concept of webapps,
however I'm forced to use chromium instead. This just sucks. Are there
any fixes in progess?

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

Title:
  Can not paste into web forms

Status in Web Browser App:
  Confirmed
Status in “webbrowser-app” package in Ubuntu:
  Confirmed

Bug description:
  I can copy text from one app, and paste it into the URL field of the
  browser, but I don't get a "Paste" option for input fields in the
  webpage itself.

  I found this when trying to log into an internal website, where SSO
  prompted me to perform 2-factor authentication.  I generated the one
  time password using CanonicalAuth, and was able to copy it into the
  clipboard.  However, I was unable to paste it into the 2fa field in
  the web browser.

  I could paste it into the URL field, so I know it was in the
  clipboard.  When long-pressing on the web form input field, I was
  given a menu with "Share", "Save" and "Copy", but not "Paste".

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

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

[Touch-packages] [Bug 1331707] Re: db5.3-util package contains the wrong version of the manual pages

[Launchpad Bug Tracker]

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

** Changed in: db5.3 (Ubuntu Utopic)
   Status: New => Confirmed

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

Title:
  db5.3-util package contains the wrong version of the manual pages

Status in “db5.3” package in Ubuntu:
  Confirmed
Status in “db5.3” source package in Trusty:
  Confirmed
Status in “db5.3” source package in Utopic:
  Confirmed

Bug description:
  PRETTY_NAME="Ubuntu 14.04 LTS"
  VERSION="14.04, Trusty Tahr"

  Package: db5.3-util
  Section: database
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Source: db5.3
  Version: 5.3.28-3ubuntu3

  The package db5.3-util contains the wrong version of the manual pages.

  /usr/share/man/man1
  /usr/share/man/man1/db5.2_recover.1.gz
  /usr/share/man/man1/db5.2_hotbackup.1.gz
  /usr/share/man/man1/db5.2_upgrade.1.gz
  /usr/share/man/man1/db5.2_stat.1.gz
  /usr/share/man/man1/db5.2_load.1.gz
  /usr/share/man/man1/db5.2_codegen.1.gz
  /usr/share/man/man1/berkeley_db5.2_svc.1.gz
  /usr/share/man/man1/db5.2_dump.1.gz
  /usr/share/man/man1/db5.2_deadlock.1.gz
  /usr/share/man/man1/db5.2_printlog.1.gz
  /usr/share/man/man1/db5.2_archive.1.gz
  /usr/share/man/man1/db5.2_checkpoint.1.gz
  /usr/share/man/man1/db5.2_verify.1.gz

  This results in dangling symbolic links in /usr/share/man/man1

  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_archive.1.gz -> 
db5.3_archive.1.gz
  0 lrwxrwxrwx 1 root root 21 2013-11-28 01:25 db_checkpoint.1.gz -> 
db5.3_checkpoint.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_codegen.1.gz -> 
db5.3_codegen.1.gz
  0 lrwxrwxrwx 1 root root 19 2013-11-28 01:25 db_deadlock.1.gz -> 
db5.3_deadlock.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_dump.1.gz -> db5.3_dump.1.gz
  0 lrwxrwxrwx 1 root root 20 2013-11-28 01:25 db_hotbackup.1.gz -> 
db5.3_hotbackup.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_load.1.gz -> db5.3_load.1.gz
  0 lrwxrwxrwx 1 root root 19 2013-11-28 01:25 db_printlog.1.gz -> 
db5.3_printlog.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_recover.1.gz -> 
db5.3_recover.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_stat.1.gz -> db5.3_stat.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_upgrade.1.gz -> 
db5.3_upgrade.1.gz
  0 lrwxrwxrwx 1 root root 17 2013-11-28 01:25 db_verify.1.gz -> 
db5.3_verify.1.gz

  Please include the manual pages for db5.3 and not those of db5.2 in
  package db5.3-util.

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

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

[Touch-packages] [Bug 1302706] Re: The gallery_app tests started failing because the toolbar is closed by the time we try to click the button

[Zoltan Balogh]

** Changed in: ubuntu-ui-toolkit
   Status: Won't Fix => Fix Released

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

Title:
  The gallery_app tests started failing because the toolbar is closed by
  the time we try to click the button

Status in Gallery App:
  In Progress
Status in Ubuntu UI Toolkit:
  Fix Released
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  We started seeing some failures on the gallery app

  http://pastebin.ubuntu.com/7203598/

  It seems that we try to click the button when the toolbar is opened,
  but by the time we have selected the autopilot button the toolbar it's
  already closed. Autopilot takes just a few milliseconds to select the
  button, so the window for the app to get this error is really small.
  But anyway, we can make the window smaller by making the check before
  selecting the button.

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

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

[Touch-packages] [Bug 1354812] Re: Header actions text is cut off

[Zoltan Balogh]

** Changed in: ubuntu-ui-toolkit
   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/1354812

Title:
  Header actions text is cut off

Status in Ubuntu UI Toolkit:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  See the attached screenshot.

  - Expected: actions drop-down expands to fit the contained text. 
Alternatively, the documentation warns about a maximum character size. 
Alternatively, text is ellipsized.
  - Actual: text longer than a given size (which?) is cut off

  This will affect translations for system and core apps in particular,
  where the English text might fit, but translations that are longer
  will be cut off.

  It corresponds to header actions for the following code snippet:

  head.actions: [
  Action {
  text: i18n.tr("Settings")
  iconName: "settings"
  onTriggered: pageStack.push(settingsPage)
  },
  Action {
  objectName: "hidepanelaction"
  iconName: "edit-clear"
  text: i18n.tr("Hide all key panels")
  onTriggered: pgTerm.showExtraPanel(0)
  },
  Action {
  objectName: "controlkeysaction"
  text: i18n.tr("Show control keys panel")
  onTriggered: pgTerm.showExtraPanel(1)
  },
  Action {
  objectName: "functionkeysaction"
  text: i18n.tr("Show function keys panel")
  onTriggered: pgTerm.showExtraPanel(2)
  },
  Action {
  objectName: "textkeysaction"
  text: i18n.tr("Show arrow keys panel")
  onTriggered: pgTerm.showExtraPanel(3)
  }
  ]
  }

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

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

[Touch-packages] [Bug 1331707] Re: db5.3-util package contains the wrong version of the manual pages

[Launchpad Bug Tracker]

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

** Changed in: db5.3 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  db5.3-util package contains the wrong version of the manual pages

Status in “db5.3” package in Ubuntu:
  Confirmed
Status in “db5.3” source package in Trusty:
  Confirmed
Status in “db5.3” source package in Utopic:
  Confirmed

Bug description:
  PRETTY_NAME="Ubuntu 14.04 LTS"
  VERSION="14.04, Trusty Tahr"

  Package: db5.3-util
  Section: database
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Source: db5.3
  Version: 5.3.28-3ubuntu3

  The package db5.3-util contains the wrong version of the manual pages.

  /usr/share/man/man1
  /usr/share/man/man1/db5.2_recover.1.gz
  /usr/share/man/man1/db5.2_hotbackup.1.gz
  /usr/share/man/man1/db5.2_upgrade.1.gz
  /usr/share/man/man1/db5.2_stat.1.gz
  /usr/share/man/man1/db5.2_load.1.gz
  /usr/share/man/man1/db5.2_codegen.1.gz
  /usr/share/man/man1/berkeley_db5.2_svc.1.gz
  /usr/share/man/man1/db5.2_dump.1.gz
  /usr/share/man/man1/db5.2_deadlock.1.gz
  /usr/share/man/man1/db5.2_printlog.1.gz
  /usr/share/man/man1/db5.2_archive.1.gz
  /usr/share/man/man1/db5.2_checkpoint.1.gz
  /usr/share/man/man1/db5.2_verify.1.gz

  This results in dangling symbolic links in /usr/share/man/man1

  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_archive.1.gz -> 
db5.3_archive.1.gz
  0 lrwxrwxrwx 1 root root 21 2013-11-28 01:25 db_checkpoint.1.gz -> 
db5.3_checkpoint.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_codegen.1.gz -> 
db5.3_codegen.1.gz
  0 lrwxrwxrwx 1 root root 19 2013-11-28 01:25 db_deadlock.1.gz -> 
db5.3_deadlock.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_dump.1.gz -> db5.3_dump.1.gz
  0 lrwxrwxrwx 1 root root 20 2013-11-28 01:25 db_hotbackup.1.gz -> 
db5.3_hotbackup.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_load.1.gz -> db5.3_load.1.gz
  0 lrwxrwxrwx 1 root root 19 2013-11-28 01:25 db_printlog.1.gz -> 
db5.3_printlog.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_recover.1.gz -> 
db5.3_recover.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_stat.1.gz -> db5.3_stat.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_upgrade.1.gz -> 
db5.3_upgrade.1.gz
  0 lrwxrwxrwx 1 root root 17 2013-11-28 01:25 db_verify.1.gz -> 
db5.3_verify.1.gz

  Please include the manual pages for db5.3 and not those of db5.2 in
  package db5.3-util.

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

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

[Touch-packages] [Bug 1288730] Re: [Patterns] Please reduce the height of the Tabbar

[Zoltan Balogh]

** Changed in: ubuntu-ui-toolkit
   Status: Won't Fix => 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/1288730

Title:
  [Patterns] Please reduce the height of the Tabbar

Status in Ubuntu UI Toolkit:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  The height of the tabbar is too much, feels like it waste a lot of
  screen space. Can we please reduce it to a more usable value ?

  Also it seems the height of the tabbar in the Dash is less than what
  we have in Apps.

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

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

[Touch-packages] [Bug 1331707] Re: db5.3-util package contains the wrong version of the manual pages

[Launchpad Bug Tracker]

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

** Changed in: db5.3 (Ubuntu)
   Status: New => Confirmed

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

Title:
  db5.3-util package contains the wrong version of the manual pages

Status in “db5.3” package in Ubuntu:
  Confirmed
Status in “db5.3” source package in Trusty:
  Confirmed
Status in “db5.3” source package in Utopic:
  Confirmed

Bug description:
  PRETTY_NAME="Ubuntu 14.04 LTS"
  VERSION="14.04, Trusty Tahr"

  Package: db5.3-util
  Section: database
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Source: db5.3
  Version: 5.3.28-3ubuntu3

  The package db5.3-util contains the wrong version of the manual pages.

  /usr/share/man/man1
  /usr/share/man/man1/db5.2_recover.1.gz
  /usr/share/man/man1/db5.2_hotbackup.1.gz
  /usr/share/man/man1/db5.2_upgrade.1.gz
  /usr/share/man/man1/db5.2_stat.1.gz
  /usr/share/man/man1/db5.2_load.1.gz
  /usr/share/man/man1/db5.2_codegen.1.gz
  /usr/share/man/man1/berkeley_db5.2_svc.1.gz
  /usr/share/man/man1/db5.2_dump.1.gz
  /usr/share/man/man1/db5.2_deadlock.1.gz
  /usr/share/man/man1/db5.2_printlog.1.gz
  /usr/share/man/man1/db5.2_archive.1.gz
  /usr/share/man/man1/db5.2_checkpoint.1.gz
  /usr/share/man/man1/db5.2_verify.1.gz

  This results in dangling symbolic links in /usr/share/man/man1

  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_archive.1.gz -> 
db5.3_archive.1.gz
  0 lrwxrwxrwx 1 root root 21 2013-11-28 01:25 db_checkpoint.1.gz -> 
db5.3_checkpoint.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_codegen.1.gz -> 
db5.3_codegen.1.gz
  0 lrwxrwxrwx 1 root root 19 2013-11-28 01:25 db_deadlock.1.gz -> 
db5.3_deadlock.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_dump.1.gz -> db5.3_dump.1.gz
  0 lrwxrwxrwx 1 root root 20 2013-11-28 01:25 db_hotbackup.1.gz -> 
db5.3_hotbackup.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_load.1.gz -> db5.3_load.1.gz
  0 lrwxrwxrwx 1 root root 19 2013-11-28 01:25 db_printlog.1.gz -> 
db5.3_printlog.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_recover.1.gz -> 
db5.3_recover.1.gz
  0 lrwxrwxrwx 1 root root 15 2013-11-28 01:25 db_stat.1.gz -> db5.3_stat.1.gz
  0 lrwxrwxrwx 1 root root 18 2013-11-28 01:25 db_upgrade.1.gz -> 
db5.3_upgrade.1.gz
  0 lrwxrwxrwx 1 root root 17 2013-11-28 01:25 db_verify.1.gz -> 
db5.3_verify.1.gz

  Please include the manual pages for db5.3 and not those of db5.2 in
  package db5.3-util.

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

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

[Touch-packages] [Bug 1321920] Re: Ctrl-V doesn't work

[Mitchell]

Until todayI thought the webbrowser (and ALL the webapps) on Ubuntu
14.10 desktop were unusable - copy and paste is essential. Have found a
workaround by right clicking on the web page, and the touch dialogue
comes up for paste. This is a major functionality issue, and should be
fixed - ctrl +v is standard on all systems. This should be backported to
14.10.

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

Title:
  Ctrl-V doesn't work

Status in “webbrowser-app” package in Ubuntu:
  Confirmed

Bug description:
  (It is possible to paste text using Ctrl-V from the clipboard into the
  address bar.)

  It is not possible to paste text using Ctrl-V from the clipboard into
  text fields on the web page itself.

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

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

[Touch-packages] [Bug 1368492] Re: crash opening image file

[Zoltan Balogh]

** Changed in: ubuntu-ui-toolkit
   Status: In Progress => Fix Released

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

Title:
  crash opening image file

Status in Ubuntu UI Toolkit:
  Fix Released
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “thumbnailer” package in Ubuntu:
  Invalid
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released
Status in “gallery-app” package in Ubuntu RTM:
  Fix Released
Status in “ubuntu-ui-toolkit” package in Ubuntu RTM:
  Fix Released

Bug description:
  krillin image 25
  libthumbailer version 1.2+14.10.20140814-0ubuntu1

  - take a picture with the camera
  - open the gallery app
  - click on the thumbnail of the photo just taken
  - boom, crash happens

  Here is the stack trace. Core file and picture used are attached

  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
  Core was generated by `./gallery-app'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0xb5b2201c in std::string::assign(std::string const&) ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  (gdb) bt
  #0  0xb5b2201c in std::string::assign(std::string const&) ()
 from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #1  0xacebe712 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #2  0xacebec62 in ?? () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #3  0xacebff34 in Thumbnailer::get_thumbnail(std::string const&, 
ThumbnailSize, ThumbnailPolicy) () from 
/usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #4  0xacec00ae in Thumbnailer::get_thumbnail(std::string const&, 
ThumbnailSize)
  () from /usr/lib/arm-linux-gnueabihf/libthumbnailer.so.0
  #5  0xacf7b70e in ThumbnailGenerator::requestImage(QString const&, QSize*, 
QSize const&) ()
 from 
/usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so
  #6  0xb640acfa in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

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

[Touch-packages] [Bug 1371205] Re: [SDK] When in insert mode, the handle is blinking and the square is not centre-aligned

[Zoltan Balogh]

** Changed in: ubuntu-ui-toolkit
   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/1371205

Title:
  [SDK] When in insert mode, the handle is blinking and the square is
  not centre-aligned

Status in Ubuntu UI Toolkit:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  Fix Released

Bug description:
  When in insert mode, the cursor is blinking and the handle is not
  centre-aligned.

  Desired behaviour
  - Handle persistent (it's not a cursor)
  - Square should be centre-aligned

  UX Spec:
  
https://docs.google.com/a/canonical.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#bookmark=kix.x877v0jqsn42

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

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

[Touch-packages] [Bug 1381743] Re: Please consider backporting a p11-kit deadlock fix

[Scott Kitterman]

We'd need the information in
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template -
including a test case.  Did you look at how cleanly the upstream patch
applies?

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

Title:
  Please consider backporting a p11-kit deadlock fix

Status in “p11-kit” package in Ubuntu:
  New

Bug description:
  Linking against p11-kit or gnutls (especially the outdated gnutls in
  Trusty) can cause fork() to deadlock randomly.  Please consider
  backporting the stable fix here:

  
http://cgit.freedesktop.org/p11-glue/p11-kit/commit/?h=stable&id=0ecc141f372b375ddd2087a8ca406797976f03bf

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

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

[Touch-packages] [Bug 1393923] Re: postfix (2.11.0-1) does not LDAP table lookup since libp11-kit0 (0.20.2-2ubuntu2)

[Scott Kitterman]

Reading the upstream bug associated with #1381743, I wonder if it might
be related?

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

Title:
  postfix (2.11.0-1) does not LDAP table lookup since libp11-kit0
  (0.20.2-2ubuntu2)

Status in “gnutls26” package in Ubuntu:
  New
Status in “openldap” package in Ubuntu:
  New
Status in “p11-kit” package in Ubuntu:
  New
Status in “postfix” package in Ubuntu:
  New

Bug description:
  Versions:

  Ubuntu14.04.1 LTS
  postfix:amd64 2.11.0-1
  postfix-ldap:amd642.11.0-1
  libldap-2.4-2:amd64   2.4.31-1+nmu2ubuntu8
  libgnutls26:amd64 2.12.23-12ubuntu2.1

  libp11-kit0:amd64 0.18.3-2ubuntu1 (works)
  libp11-kit0:amd64 0.20.2-2ubuntu2 (does not work)

  
  Problem:

  When receiving email, postfix does not do LDAP lookup for transport
  tables any more.

  
  With libp11-kit0 0.18.3-2ubuntu1 everything works fine. At a certain point 
postfix starts LDAP lookup and continues until it finds the needed LDAP item.

  snippet from /var/log/mail.log:

  ...
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: In 
dict_ldap_lookup
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: No 
existing connection for LDAP source /etc/postfix/ldap-mda.cf, reopening
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: 
Connecting to server ldaps://db.itec.int ldaps://db1.itec.int 
ldaps://db2.itec.int
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: Actual 
Protocol version used is 3.
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: Binding 
to server ldaps://db.itec.int ldaps://db1.itec.int ldaps://db2.itec.int with dn 
uid=mta,ou=computers,dc=itec,dc=int
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: 
Successful bind to server ldaps://db.itec.int ldaps://db1.itec.int 
ldaps://db2.itec.int with dn uid=mta,ou=computers,dc=itec,dc=int
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: Cached 
connection handle for LDAP source /etc/postfix/ldap-mda.cf
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: 
/etc/postfix/ldap-mda.cf: Searching with filter 
(&(objectClass=inetLocalMailRecipient)(&(mailRoutingAddress=\2A)(mailHost=mta.itec.int)))
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_get_values[1]: 
Search found 0 match(es)
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_get_values[1]: 
Leaving dict_ldap_get_values
  Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: Search 
returned nothing
  ...

  
  With libp11-kit0 0.20.2-2ubuntu2 postfix does not start LDAP lookup. Instead 
it gets killed by signal.

  snippet from /var/log/mail.log:

  ...
  Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_lookup: In 
dict_ldap_lookup
  Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_lookup: No 
existing connection for LDAP source /etc/postfix/ldap-mda.cf, reopening
  Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_connect: 
Connecting to server ldaps://db.itec.int ldaps://db1.itec.int 
ldaps://db2.itec.int
  Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_connect: Actual 
Protocol version used is 3.
  Nov 18 19:07:11 mta postfix/master[11997]: warning: process 
/usr/lib/postfix/trivial-rewrite pid 12032 killed by signal 11
  Nov 18 19:07:11 mta postfix/master[11997]: warning: 
/usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
  Nov 18 19:07:42 mta postfix/pickup[12000]: trigger_server_accept_local: 
trigger arrived
  Nov 18 19:07:42 mta postfix/pickup[12000]: master_notify: status 0
  Nov 18 19:07:42 mta postfix/pickup[12000]: master_notify: status 1
  ...

  --> I am not able to upgrade to the current (trusty) version of
  libp11-kit0. Instead I have to run an outdated (saucy) version of
  libp11-kit0.

  What can I do to get the current version running?

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

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

[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

[Cyrus Harmon]

Any chance of seeing a fix for utopic for this?

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “nfs-utils” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Confirmed
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “upstart” source package in Utopic:
  Confirmed
Status in “nfs-utils” source package in Vivid:
  Fix Released
Status in “upstart” source package in Vivid:
  Confirmed

Bug description:
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

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

[Touch-packages] [Bug 1366018] Re: Not clear in "Wi-Fi" settings whether you are connected

[Launchpad Bug Tracker]

[Expired for ubuntu-system-settings (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Not clear in "Wi-Fi" settings whether you are connected

Status in “indicator-network” package in Ubuntu:
  Expired
Status in “ubuntu-system-settings” package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.10 r22

  1. Go somewhere that many Wi-Fi networks are nearby.
  2. Navigate to System Settings > "Wi-Fi".
  3. Try to tell whether you are connected.

  What happens: The network you are connected to might be so far down
  the list that it's off-screen.

  What should happen: The network you are connected to is always at the
  top.

  : "Whenever Wi-Fi is
  on and a network *is* connected, 'Available networks:' should instead
  be 'Other available networks:', because it should be preceded by a
  'Connected to:' section listing the connected network."

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

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

[Touch-packages] [Bug 1366018] Re: Not clear in "Wi-Fi" settings whether you are connected

[Launchpad Bug Tracker]

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

** Changed in: indicator-network (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Not clear in "Wi-Fi" settings whether you are connected

Status in “indicator-network” package in Ubuntu:
  Expired
Status in “ubuntu-system-settings” package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.10 r22

  1. Go somewhere that many Wi-Fi networks are nearby.
  2. Navigate to System Settings > "Wi-Fi".
  3. Try to tell whether you are connected.

  What happens: The network you are connected to might be so far down
  the list that it's off-screen.

  What should happen: The network you are connected to is always at the
  top.

  : "Whenever Wi-Fi is
  on and a network *is* connected, 'Available networks:' should instead
  be 'Other available networks:', because it should be preceded by a
  'Connected to:' section listing the connected network."

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

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

[Touch-packages] [Bug 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work

[Shih-Yuan Lee]

I have verified systemd 204-5ubuntu20.9 and it does fix the problem.

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

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

Title:
  [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not
  work

Status in HWE Next Project:
  Fix Released
Status in HWE Next trusty series:
  In Progress
Status in HWE Next utopic series:
  Fix Released
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  In Progress
Status in “linux” package in Ubuntu:
  Fix Released
Status in “systemd” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Won't Fix
Status in “systemd” source package in Trusty:
  Fix Committed

Bug description:
  CID: 201402-14663 Dell Latitude 12 Rugged Extreme

  The microphone mute key does not work on this system, so as its LED

  Steps:
  1. Install 14.04 + update (3.13.0-30), boot to desktop
  2. Try to mute the microphone with the hotkey (fn+F4)

  Expected results:
  * Mic mute key should work, its LED should be lit and the "Mute" option for 
input device should be ticked after you press the mic mute key.

  Actual result:
  * Nothing happened.

  Debugging information:
  ubuntu@201402-14663:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 248 press
  keycode 248 release
  keycode 248 press
  keycode 248 release
  keycode 248 press
  keycode 248 release
  keycode  29 press
  ^Ccaught signal 2, cleaning up...

  xev cannot detect any microphone mute key event

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1501 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1501 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Wed Jul  9 23:57:11 2014
  HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734
  InstallationDate: Installed on 2014-07-10 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed 
root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0TH1GJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 12 Rugged Extreme (7204)
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1339998/+subscriptions

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

[Touch-packages] [Bug 1304873] Re: mir_unit_tests.MesaBufferAllocatorTest.* test fails under sbuild

[Daniel van Vugt]

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

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

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

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

Title:
  mir_unit_tests.MesaBufferAllocatorTest.* test fails under sbuild

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Mir FTBFS under sbuild, excerpts from the test results below, full log
  attached.

  ⟫ bzr bd --builder="sbuild -j9"

  Start 104: mir_unit_tests.MesaBufferAllocatorTest.*
  104/178 Test #104: mir_unit_tests.MesaBufferAllocatorTest.* 
...***Failed0.09 sec

  [ RUN  ] MesaBufferAllocatorTest.software_buffers_dont_bypass
  unknown file: Failure
  C++ exception with description "Failed to create file" thrown in the test 
body.
  [  FAILED  ] MesaBufferAllocatorTest.software_buffers_dont_bypass (4 ms)

  [ RUN  ] MesaBufferAllocatorTest.creates_software_rendering_buffer
  unknown file: Failure
  C++ exception with description "Failed to create file" thrown in the test 
body.
  [  FAILED  ] MesaBufferAllocatorTest.creates_software_rendering_buffer (4 ms)

  [--] Global test environment tear-down
  [==] 18 tests from 1 test case ran. (77 ms total)
  [  PASSED  ] 16 tests.
  [  FAILED  ] 2 tests, listed below:
  [  FAILED  ] MesaBufferAllocatorTest.software_buffers_dont_bypass
  [  FAILED  ] MesaBufferAllocatorTest.creates_software_rendering_buffer

   2 FAILED TESTS

  The following tests FAILED:
104 - mir_unit_tests.MesaBufferAllocatorTest.* (Failed)

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

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

[Touch-packages] [Bug 1346633] Re: [enhancement] Autopilot testing needs to know screen coordinates of widgets on screen

[Daniel van Vugt]

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

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

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

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

Title:
  [enhancement] Autopilot testing needs to know screen coordinates of
  widgets on screen

Status in Autopilot:
  Won't Fix
Status in Mir:
  Fix Committed
Status in Qt integration with the Mir display server:
  Confirmed
Status in “mir” package in Ubuntu:
  Triaged
Status in “qtubuntu” package in Ubuntu:
  Fix Released

Bug description:
  On phablet devices, Autopilot needs to determine the absolute
  coordinates of any item on screen, in order to generate input events
  to interact with those items.

  Most toolkits give AP the ability to calculate the coordinates of an
  item inside the surface, i.e. relative to the surface top-left corner,
  and then obtain the position of the window from the display server
  (X11 usually) to calculate the absolute position.

  However Mir does not have an API to let its clients find the surface
  position relative to the screen. There is also a desire from the Mir
  team not to supply this information.

  We need to discuss how to solve this problem in a way everyone is
  happy

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

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

[Touch-packages] [Bug 1378740] Re: Mir server aborts when an exception is thrown from the main thread

[Daniel van Vugt]

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

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

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

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

Title:
  Mir server aborts when an exception is thrown from the main thread

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  The Mir server aborts when an exception is thrown from the main
  thread. The expected behavior is for the server to clean up gracefully
  and propagate the exception to the caller.

  The backtrace from bug 134 is probably an instance of this
  problem.

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

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

[Touch-packages] [Bug 1375211] Re: [regression] unit_tests AndroidInputReceiverSetup.* takes excessive time

[Daniel van Vugt]

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

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

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

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

Title:
  [regression] unit_tests AndroidInputReceiverSetup.* takes excessive
  time

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  #77: mir_unit_tests.AndroidInputReceiverSetup.*
     Passed   10.36 sec

  Unit tests should take milliseconds, not decaseconds.

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

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

[Touch-packages] [Bug 1378995] Re: "citrain upgrade-device" fails to upgrade mir properly (Mesa driver installed instead of Android makes the phone unbootable).

[Daniel van Vugt]

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

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

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

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

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

Title:
  "citrain upgrade-device" fails to upgrade mir properly (Mesa driver
  installed instead of Android makes the phone unbootable).

Status in Mir:
  Fix Committed
Status in Mir 0.8 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “mir” package in Ubuntu RTM:
  Triaged

Bug description:
  When testing a silo, QA folks use the following command :

  citrain upgrade-device  

  However Mir fails to be upgraded properly. Specifically Mesa libs are
  picked up instead of android libs. Details can be found in the
  following log :

  https://pastebin.canonical.com/118445/

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

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

[Touch-packages] [Bug 1378706] Re: [regression] demo-shell bypass is not used on fullscreen surfaces if there are windowed surfaces behind

[Daniel van Vugt]

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

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

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

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

Title:
  [regression] demo-shell bypass is not used on fullscreen surfaces if
  there are windowed surfaces behind

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  [regression] Bypass is not used on fullscreen surfaces if there are
  windowed surfaces behind.

  Test case:
1. mir_demo_server_shell --compositor-report=log
2. mir_demo_client_egltriangle -q &
3. mir_demo_client_egltriangle -f

  Expected: Compositor report shows bypass on, and 100%.
  Observed: Compositor report shows bypass off.

  The problem is #2 - the windows client in the background. If you
  remove that then bypass is enabled correctly.

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

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

[Touch-packages] [Bug 1378326] Re: [krillin] overlays are not displayed onscreen in some positions

[Daniel van Vugt]

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

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

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

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

Title:
  [krillin] overlays are not displayed onscreen in some positions

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Some positioning of overlays causes the driver to accept the layer as
  an overlay, and then not display it onscreen. This only affects the
  "'stable device'", and seems to be a driver problem.

  How to reproduce:
  1) Position a 500x500 window at 0,0
  2) Position a 400x400 window at 0,0

  The appearance of the smaller window will cause the first to
  disappear, when on other devices, both are displayed with the smaller
  window on top of the larger window. The driver accepts one of the
  layers as an overlay, and then fails to display it.

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

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

[Touch-packages] [Bug 1303817] Re: demo-shell goes to sleep unexpectedly when tapping ThinkPad "Fn" key

[Daniel van Vugt]

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

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

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

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

Title:
  demo-shell goes to sleep unexpectedly when tapping ThinkPad "Fn" key

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  demo-shell goes to sleep when tapping ThinkPad "Fn" key. It's somehow
  mistaking that for the device power button.

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

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

[Touch-packages] [Bug 1377968] Re: a prompt session with an invalid application pid should be an error

[Daniel van Vugt]

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

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

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

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

Title:
  a prompt session with an invalid application pid should be an error

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Calling mir_connection_create_prompt_session_sync() with an
  "application pid" that doesn't correspond to an existing session leads
  to a "valid" prompt session being created without the (non-existent)
  application session being added to the prompt session.

  An error should be reported by the server so that the result of
  mir_prompt_session_is_valid() will be false.

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

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

[Touch-packages] [Bug 1388802] Re: intermittent acceptance test bug in TestClientInput

[Daniel van Vugt]

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

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

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

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

Title:
  intermittent acceptance test bug in TestClientInput

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  https://jenkins.qa.ubuntu.com/job/mir-clang-utopic-
  amd64-build/2344/console

  Start  34: mir_acceptance_tests.TestClientInput.*
   34/246 Test  #34: mir_acceptance_tests.TestClientInput.* 
***Failed   15.85 sec

  Similar to lp: 1196744 but that was closed a year ago. (So I'm
  assuming it hasn't been seen all this time and we have a new cause.)

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

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

[Touch-packages] [Bug 1391923] Re: [regression] mir_demo_server_basic does not start

[Daniel van Vugt]

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

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

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

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

Title:
  [regression] mir_demo_server_basic does not start

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  root@ubuntu-phablet:/home/phablet# ./mir_demo_server_basic 
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_12bad_any_castE
  std::exception::what: boost::bad_any_cast: failed conversion using 
boost::any_cast

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

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

[Touch-packages] [Bug 1390312] Re: unit-tests:ApplicationSession are noisy (lots of GMOCK WARNING)

[Daniel van Vugt]

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

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

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

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

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

Title:
  unit-tests:ApplicationSession are noisy (lots of GMOCK WARNING)

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  unit-tests:ApplicationSession are noisy (lots of GMOCK WARNING) ...

  $ bin/mir_unit_tests --gtest_filter="ApplicationSession.*"
  Running main() from command_line_server_configuration.cpp
  Note: Google Test filter = ApplicationSession.*
  [==] Running 13 tests from 1 test case.
  [--] Global test environment set-up.
  [--] 13 tests from ApplicationSession
  [ RUN  ] ApplicationSession.create_and_destroy_surface

  GMOCK WARNING:
  Uninteresting mock function call - returning directly.
  Function call: add_observer(@0x7fff473d0200 16-byte object )
  Stack trace:

  GMOCK WARNING:
  Uninteresting mock function call - returning directly.
  Function call: remove_surface(@0x7fff473d0200 16-byte object )
  Stack trace:
  [   OK ] ApplicationSession.create_and_destroy_surface (1 ms)
  [ RUN  ] 
ApplicationSession.listener_notified_of_surface_destruction_on_session_destruction

  GMOCK WARNING:
  Uninteresting mock function call - returning directly.
  Function call: add_observer(@0x7fff473d01f0 16-byte object <70-0D C3-03 
00-00 00-00 60-0D C3-03 00-00 00-00>)
  Stack trace:

  GMOCK WARNING:
  Uninteresting mock function call - returning directly.
  Function call: remove_surface(@0x7fff473d01f0 16-byte object )
  Stack trace:

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

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

[Touch-packages] [Bug 1382162] Re: [mako] Initial wizard crashes multiple times

[Daniel van Vugt]

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

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

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

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

Title:
  [mako] Initial wizard crashes multiple times

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  The setup wizard crashes on my mako multiple times. Only after a few
  crashes (in some cases after a reboot) I am able to complete the
  wizard and start my phone.

  I have attached the log. Probably something to do with Mir/Driver ?

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: ubuntu-system-settings-wizard 0.3+14.10.20141013-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: armhf
  Date: Thu Oct 16 23:27:21 2014
  InstallationDate: Installed on 2014-10-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141016-162207)
  SourcePackage: ubuntu-system-settings
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.ubuntu-system-settings-wizard-cleanup.log: 
ubuntu-system-settings-wizard start/post-stop, process 5409

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

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

[Touch-packages] [Bug 1387501] Re: CMake outputs lots of "policy" warnings building Mir on vivid

[Daniel van Vugt]

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

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

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

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

Title:
  CMake outputs lots of "policy" warnings building Mir on vivid

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  CMake outputs lots of "policy" warnings building Mir on vivid...

  CMake Warning (dev) at cmake/ABICheck.cmake:43 (get_property):
Policy CMP0026 is not set: Disallow use of the LOCATION target property.
Run "cmake --help-policy CMP0026" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.

The LOCATION property should not be read from target "mirclient".  Use the
target name directly with add_custom_command, or use the generator
expression $, as appropriate.

  Call Stack (most recent call first):
cmake/ABICheck.cmake:61 (make_lib_descriptor)
CMakeLists.txt:233 (include)
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at cmake/ABICheck.cmake:43 (get_property):
Policy CMP0026 is not set: Disallow use of the LOCATION target property.
Run "cmake --help-policy CMP0026" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.

The LOCATION property should not be read from target "mirserver".  Use the
target name directly with add_custom_command, or use the generator
expression $, as appropriate.

  Call Stack (most recent call first):
cmake/ABICheck.cmake:62 (make_lib_descriptor)
CMakeLists.txt:233 (include)
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at cmake/ABICheck.cmake:43 (get_property):
Policy CMP0026 is not set: Disallow use of the LOCATION target property.
Run "cmake --help-policy CMP0026" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.

The LOCATION property should not be read from target "mircommon".  Use the
target name directly with add_custom_command, or use the generator
expression $, as appropriate.

  Call Stack (most recent call first):
cmake/ABICheck.cmake:63 (make_lib_descriptor)
CMakeLists.txt:233 (include)
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at cmake/ABICheck.cmake:43 (get_property):
Policy CMP0026 is not set: Disallow use of the LOCATION target property.
Run "cmake --help-policy CMP0026" for policy details.  Use the cmake_policy
command to set the policy and suppress this warning.

The LOCATION property should not be read from target "mirplatform".  Use
the target name directly with add_custom_command, or use the generator
expression $, as appropriate.

  Call Stack (most recent call first):
cmake/ABICheck.cmake:64 (make_lib_descriptor)
CMakeLists.txt:233 (include)
  This warning is for project developers.  Use -Wno-dev to suppress it.

  -- Configuring done
  CMake Warning (dev) at benchmarks/CMakeLists.txt:14 (add_dependencies):
Policy CMP0046 is not set: Error on non-existent dependency in
add_dependencies.  Run "cmake --help-policy CMP0046" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

The dependency target "frame_uniformity" of target "benchmarks" does not
exist.
  This warning is for project developers.  Use -Wno-dev to suppress it.

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

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

[Touch-packages] [Bug 1386185] Re: Clients that don't register a lifecycle handler get SIGHUP when disconnecting

[Daniel van Vugt]

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

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

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

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

Title:
  Clients that don't register a lifecycle handler get SIGHUP when
  disconnecting

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  A client that is not handling lifecycle events shouldn't need to
  register a handler.

  Take mir_demo_client_basic for an example:

  it should output:

  Starting
  Connected
  Surface created
  Surface released
  Connection released

  It actually outputs

  Starting
  Connected
  Surface created
  Surface released
  Hangup  <<===

  Because SIGHUP is raised during (and as a consequence) of the
  mir_connection_release() call.

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

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

[Touch-packages] [Bug 1388539] Re: [regression] Mir fails to build with MIR_ENABLE_TESTS=OFF

[Daniel van Vugt]

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

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

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

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

Title:
  [regression] Mir fails to build with MIR_ENABLE_TESTS=OFF

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  [regression] Mir fails to build with MIR_ENABLE_TESTS=OFF

  Linking CXX executable ../../bin/frame_uniformity_test_client
  /usr/bin/ld: cannot find -lmir-test
  /usr/bin/ld: cannot find -lmir-test-framework
  /usr/bin/ld: cannot find -lmir-test-doubles
  /usr/bin/ld: cannot find -lmir-test-doubles-platform
  collect2: error: ld returned 1 exit status
  
benchmarks/frame-uniformity/CMakeFiles/frame_uniformity_test_client.dir/build.make:237:
 recipe for target 'bin/frame_uniformity_test_client' failed
  make[2]: *** [bin/frame_uniformity_test_client] Error 1
  CMakeFiles/Makefile2:3966: recipe for target 
'benchmarks/frame-uniformity/CMakeFiles/frame_uniformity_test_client.dir/all' 
failed
  make[1]: *** 
[benchmarks/frame-uniformity/CMakeFiles/frame_uniformity_test_client.dir/all] 
Error 2
  Makefile:127: recipe for target 'all' failed

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

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

[Touch-packages] [Bug 1386646] Re: [testsfail] DemoPrivateProtobuf hang in CI

[Daniel van Vugt]

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

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

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

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

Title:
  [testsfail] DemoPrivateProtobuf hang in CI

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  > [--] 4 tests from DemoPrivateProtobuf
  > [ RUN  ] DemoPrivateProtobuf.client_calls_server
  > ==25754== 
  > ==25754== HEAP SUMMARY:
  > ==25754== in use at exit: 212,035 bytes in 3,425 blocks
  > ==25754==   total heap usage: 9,051 allocs, 5,626 frees, 599,694 bytes 
allocated
  > ==25754== 
  > ==25754== LEAK SUMMARY:
  > ==25754==definitely lost: 0 bytes in 0 blocks
  > ==25754==indirectly lost: 0 bytes in 0 blocks
  > ==25754==  possibly lost: 52,274 bytes in 942 blocks
  > ==25754==still reachable: 159,761 bytes in 2,483 blocks
  > ==25754== suppressed: 0 bytes in 0 blocks
  > ==25754== Reachable blocks (those to which a pointer was found) are not 
shown.
  > ==25754== To see them, rerun with: --leak-check=full --show-leak-kinds=all
  > ==25754== 
  > ==25754== For counts of detected and suppressed errors, rerun with: -v
  > ==25754== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
  > 
  > test 11

  https://jenkins.qa.ubuntu.com/job/mir-utopic-
  amd64-autolanding/63/consoleText

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

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

[Touch-packages] [Bug 1381925] Re: AsioMainLoopAlarmTest.alarm_callback_cannot_deadlock hang in CI

[Daniel van Vugt]

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

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

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

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

Title:
  AsioMainLoopAlarmTest.alarm_callback_cannot_deadlock  hang in CI

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  Seen in CI [1]:

  8: [ RUN  ] AsioMainLoopAlarmTest.alarm_callback_cannot_deadlock
  Build timed out (after 240 minutes). Marking the build as failed.

  [1] https://jenkins.qa.ubuntu.com/job/mir-mediumtests-builder-utopic-
  armhf/1020/console

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

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

[Touch-packages] [Bug 1390388] Re: [testfail] StaleFrames.are_dropped_when_restarting_compositor in CI

[Daniel van Vugt]

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

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

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

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

Title:
  [testfail] StaleFrames.are_dropped_when_restarting_compositor in CI

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

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

  [ RUN ] StaleFrames.are_dropped_when_restarting_compositor
  
/tmp/buildd/mir-0.8.0+14.10.20141010bzr2039pkg0vivid4+autopilot0/tests/integration-tests/test_stale_frames.cpp:203:
 Failure
  Expected: (stale_buffer_id1) != (stale_buffer_id2), actual: 3 vs 3
  
/tmp/buildd/mir-0.8.0+14.10.20141010bzr2039pkg0vivid4+autopilot0/tests/integration-tests/test_stale_frames.cpp:204:
 Failure
  Expected: (stale_buffer_id2) != (buffer_id3), actual: 3 vs 3
  
/tmp/buildd/mir-0.8.0+14.10.20141010bzr2039pkg0vivid4+autopilot0/tests/integration-tests/test_stale_frames.cpp:209:
 Failure
  Value of: new_buffers[0]
  Actual: 40
  Expected: buffer_id3
  Which is: 3
  [ FAILED ] StaleFrames.are_dropped_when_restarting_compositor (221 
ms)

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

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

[Touch-packages] [Bug 1384390] Re: mir examples/progressbar.c uses internal C define (can't build on other distros)

[Daniel van Vugt]

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

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

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

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

Title:
  mir examples/progressbar.c uses internal C define (can't build on
  other distros)

Status in Mir:
  Fix Committed
Status in “mir” package in Ubuntu:
  Triaged

Bug description:
  This example program does #define __USE_BSD 1 but the __USE_BSD macro
  is an internal private define for use by the C library itself.  This
  causes problems with newer versions of glibc.

  The correct solution here is to use _BSD_SOURCE but apparently this is
  deprecated in newer versions of glibc for favour of _DEFAULT_SOURCE.

  In order to work with both old and new we should define both as
  explained here:

  /* _BSD_SOURCE and _SVID_SOURCE are deprecated aliases for
 _DEFAULT_SOURCE.  If _DEFAULT_SOURCE is present we do not
 issue a warning; the expectation is that the source is being
 transitioned to use the new macro.  */
  #if (defined _BSD_SOURCE || defined _SVID_SOURCE) \
  && !defined _DEFAULT_SOURCE
  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
  # undef  _DEFAULT_SOURCE
  # define _DEFAULT_SOURCE1
  #endif

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

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

[Touch-packages] [Bug 1394063] Re: Inspiron 3137 brightness keys aren't recognized

[Nicholas Skaggs]

Ahh, that's https://bugs.launchpad.net/ubuntu/+source/apport/+bug/788936

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

[Nicholas Skaggs]

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263448/+files/dmesg.log

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1394063] Re: Inspiron 3137 brightness keys aren't recognized

[Nicholas Skaggs]

Looks like potentially another bug, as apport things I upgraded on my
original install date;

UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

[Nicholas Skaggs]

** Attachment added: "xkbmap.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263451/+files/xkbmap.txt

** Summary changed:

- intel_backlight brightness keys fail 
+ Inspiron 3137 brightness keys aren't recognized

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

[Nicholas Skaggs]

** Attachment added: "xkbcomp.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263450/+files/xkbcomp.txt

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1394063] Re: intel_backlight brightness keys fail

[Nicholas Skaggs]

** Attachment added: "lsinput.log"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1394063/+attachment/4263449/+files/lsinput.log

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

Title:
  Inspiron 3137 brightness keys aren't recognized

Status in “systemd” package in Ubuntu:
  New

Bug description:
  Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
   works properly. This worked properly in vivid and has been broken since 
upgrade.

  Xev doesn't show a keypress event. Scan codes from evtest are shown
  below:

  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1394063] [NEW] Inspiron 3137 brightness keys aren't recognized

[Nicholas Skaggs]

Public bug reported:

Hardware keys on an inspirion 3137 for brightness don't work. Manually setting 
the backlight via /sys/class/backlight/intel_backlight/brightness
 works properly. This worked properly in vivid and has been broken since 
upgrade.

Xev doesn't show a keypress event. Scan codes from evtest are shown
below:

Event: time 1416367751.898584, -- EV_SYN 
Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
Event: time 1416367754.952917, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), 
value 1
Event: time 1416367754.952917, -- EV_SYN 
Event: time 1416367754.952946, type 1 (EV_KEY), code 224 (KEY_BRIGHTNESSDOWN), 
value 0
Event: time 1416367754.952946, -- EV_SYN 
Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
Event: time 1416367756.898936, -- EV_SYN 
Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 215-5ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Nov 18 22:16:25 2014
InstallationDate: Installed on 2014-06-04 (167 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 3137
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
dmi.bios.date: 12/25/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0PRDX0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Inspiron 3137
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug vivid

** Attachment added: "udev-db.txt"
   
https://bugs.launchpad.net/bugs/1394063/+attachment/4263436/+files/udev-db.txt

** Description changed:

- Hardware keys on an inspirion 3138 for brightness don't work. Xev
- doesn't show a keypress event.
+ Hardware keys on an inspirion 3137 for brightness don't work. Manually 
setting the backlight via /sys/class/backlight/intel_backlight/brightness
+  works properly. This worked properly in vivid and has been broken since 
upgrade.
  
- Scan codes from evtest are shown below
+ Xev doesn't show a keypress event. Scan codes from evtest are shown
+ below:
  
  Event: time 1416367751.898584, -- EV_SYN 
  Event: time 1416367754.952917, type 4 (EV_MSC), code 4 (MSC_SCAN), value 85
  Event: time 1416367754.952917, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 1
  Event: time 1416367754.952917, -- EV_SYN 
  Event: time 1416367754.952946, type 1 (EV_KEY), code 224 
(KEY_BRIGHTNESSDOWN), value 0
  Event: time 1416367754.952946, -- EV_SYN 
  Event: time 1416367756.898936, type 4 (EV_MSC), code 4 (MSC_SCAN), value 86
  Event: time 1416367756.898936, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 1
  Event: time 1416367756.898936, -- EV_SYN 
  Event: time 1416367756.898968, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), 
value 0
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 215-5ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 18 22:16:25 2014
  InstallationDate: Installed on 2014-06-04 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 3137
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed 
root=UUID=0e352344-90e9-4cbe-acde-376a88cf5b47 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-06-04 (167 days ago)
  dmi.bios.date: 12/25/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PRDX0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Inspiron 3137
  dmi.sys.vendor: Dell Inc.

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

[Touch-packages] [Bug 1392590] Re: package whoopsie 0.2.39ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100

[john paul asonio]

no, this pops up on fresh installation, btw i installed this on toshiba
chromebook

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

Title:
  package whoopsie 0.2.39ubuntu0.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 100

Status in “whoopsie” package in Ubuntu:
  Incomplete

Bug description:
  Skowing system down

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: whoopsie 0.2.39ubuntu0.1
  Uname: Linux 3.4.0 x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Fri Nov 14 04:13:26 2014
  Df:
   
  DuplicateSignature: package:whoopsie:0.2.39ubuntu0.1:subprocess installed 
post-installation script returned error exit status 100
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 100
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.39ubuntu0.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 100
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu

[Lorn Potter]

I did more testing of the generic plugin, and it's not as bad as I
thought, in that it does signal when interfaces become the default
route.

But my comment still stands that without these patches (in the least,
the patch to QNAM itself is especially needed) the defaultConfiguration
internal to QNAM will not switch, which _will_ cause people to wonder
why their mobile data is being used while the indicator shows that they
are connected to wifi, and _will_ cause people to use up their expensive
mobile data.

I question the removal of this from TOPBLOCKER's and rtm.

QtBearer is not just about starting and stopping the connections, QNAM
uses it internally for every get()  request.

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

Title:
  QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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

[Touch-packages] [Bug 1367883] Re: [SRU] Add Microsoft-owned MAC address to 75-persistent-net-generator.rules

[Hui Wang]

@Martin Pitt,

Got it, thanks.

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

Title:
  [SRU] Add Microsoft-owned MAC address to 75-persistent-net-
  generator.rules

Status in “systemd” package in Ubuntu:
  Fix Released
Status in “udev” package in Ubuntu:
  Invalid
Status in “udev” source package in Precise:
  In Progress
Status in “systemd” source package in Trusty:
  Fix Released

Bug description:
  Impact: As Microsoft expands its public cloud offering it may need to
  utilize additional MAC address prefixes.  If a user launches a Cloud
  instance when the MAC address is from a Microsoft-owned MAC address
  that is not in the exclusion list, eth0 is persistently named for the
  first NIC seen. If a user rebundles, or the machines has its MAC
  address changed (e.g. VM resize or VM is moved to another host), it
  will lose network connectivity.

  Fix:  Please add the following Microsoft-owned MAC address to the 75
  -persistent-net-generator.rules file:

   00:25:ae  Microsoft Corporation

  Test Case :
   - Launch Hyper-V VM with MAC address with prefix 00:25:ae
   - Install updated Udev/systemd
   - Delete any existing udev rule
   - Reboot and confirm that no new UDEV rule was added

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

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

[Touch-packages] [Bug 1356680] Re: [IdeaPad Z360, Realtek ALC272, Mic, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [IdeaPad Z360, Realtek ALC272, Mic, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Internal microphone doesn't work instead edit alsa conf including
  options snd-hda-intel model=dell-headset-multi, nor ideapad, asus,
  asus-mode1, asus-mode2, asus-mode3... asus-mode8 models.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
  Uname: Linux 3.2.0-51-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dalton 3918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf080 irq 43'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0272,17aa400a,0011 
HDA:80862804,80860101,0010'
 Controls  : 27
 Simple ctrls  : 12
  Date: Wed Aug 13 23:39:39 2014
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Áudio interno - HDA Intel
  Symptom_DevicesInUse:
   3918  daltonF pulseaudio
   PID ACCESS COMMAND
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [IdeaPad Z360, Realtek ALC272, Mic, Internal] No sound at all
  UpgradeStatus: Upgraded to precise on 2012-08-28 (715 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 35CN22WW
  dmi.board.name: LL1
  dmi.board.vendor: Lenovo
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr35CN22WW:bd11/19/2010:svnLENOVO:pnIdeaPadZ360:pvrRev1.0:rvnLenovo:rnLL1:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: IdeaPad Z360
  dmi.product.version: Rev 1.0
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-08-13T23:38:02.468765

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

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

[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

[Launchpad Bug Tracker]

This bug was fixed in the package nfs-utils - 1:1.2.8-9ubuntu2

---
nfs-utils (1:1.2.8-9ubuntu2) vivid; urgency=medium

  * debian/nfs-common.statd.upstart: wait for rpcbind job instead of
relying on portmap compatibility event. (LP: #1391296)
 -- Marc DeslauriersTue, 18 Nov 2014 19:07:15 
-0500

** Changed in: nfs-utils (Ubuntu Vivid)
   Status: Confirmed => Fix Released

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “nfs-utils” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Confirmed
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “upstart” source package in Utopic:
  Confirmed
Status in “nfs-utils” source package in Vivid:
  Fix Released
Status in “upstart” source package in Vivid:
  Confirmed

Bug description:
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

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

[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/nfs-utils

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “upstart” source package in Utopic:
  Confirmed
Status in “nfs-utils” source package in Vivid:
  Confirmed
Status in “upstart” source package in Vivid:
  Confirmed

Bug description:
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

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

[Touch-packages] [Bug 1354841] Re: Screen corruption (characters are drawn as black squares)

[M]

Dear Christopher,

Thank you for checking the BIOS version, I haven't thought about that. I
have already done several BIOS upgrades on this machine, so it shouldn't
be a problem. I will update the bug report accordingly once it is done

Thank you
Matthieu

PS: I have at this very moment the "white" variant of the bug, cf
attached screenshot


** Attachment added: "white_squares.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354841/+attachment/4263368/+files/white_squares.png

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

Title:
  Screen corruption (characters are drawn as black squares)

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Sometimes, the characters are rendered as black squares (cf attachment). I 
couldn't find any event in the systems logs that could explain that.
  I can "stop" the bug by changing the anti-aliasing options in the system 
settings (enabled / disabled, level of hinting) and restarting the 
applications, but the squares can come back later on, and I have to repeat the 
operation.

  The bug almost exclusively happens with firefox and thunderbird,
  though krunner is also affected (but not other kde apps). I'm not
  using many GTK applications, but I can also see the bug with unison.

  It used to happen in 13.10 as well, and upgrading to 14.04.1 hasn't
  improved the situation

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  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: KDE
  Date: Sun Aug 10 14:03:25 2014
  InstallationDate: Installed on 2011-01-10 (1307 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-08-06 (3 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  CurrentDesktop: KDE
  DistUpgraded: 2014-08-06 14:32:56,683 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 4.3.10, 3.13.0-40-generic, x86_64: installed
   virtualbox-guest, 4.3.10, 3.13.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0428]
  InstallationDate: Installed on 2011-01-10 (1407 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Dell Inc. Latitude E5510
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=851d627f-547c-4a28-94e7-778e3a396d65 ro loop.max_part=63 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags:  trusty kubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-08-06 (103 days ago)
  UserGroups: adm admin audio cdrom condor dialout disk fuse lpadmin mysql 
plugdev sambashare video
  _MarkForUpload: True
  dmi.bios.date: 04/21/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd04/21/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Nov 15 13:25:39 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21579 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu

[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

[Marc Deslauriers]

** Also affects: nfs-utils (Ubuntu Vivid)
   Importance: Undecided
   Status: Confirmed

** Also affects: upstart (Ubuntu Vivid)
   Importance: Undecided
   Status: Confirmed

** Also affects: nfs-utils (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

** Changed in: nfs-utils (Ubuntu Utopic)
   Status: New => Confirmed

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

** Changed in: nfs-utils (Ubuntu Utopic)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: nfs-utils (Ubuntu Vivid)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed
Status in “nfs-utils” source package in Utopic:
  Confirmed
Status in “upstart” source package in Utopic:
  Confirmed
Status in “nfs-utils” source package in Vivid:
  Confirmed
Status in “upstart” source package in Vivid:
  Confirmed

Bug description:
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

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

[Touch-packages] [Bug 1394021] [NEW] problem

[skitarro]

Public bug reported:

problem

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 19 01:04:41 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
   Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
InstallationDate: Installed on 2014-11-17 (1 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
MachineType: ASUSTeK Computer INC. 1000H
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=062ba9ea-44e7-44de-846b-4c5990970a9c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2204
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1000H
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2204:bd10/21/2009:svnASUSTeKComputerINC.:pn1000H:pvrx.x:rvnASUSTeKComputerINC.:rn1000H:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1000H
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Wed Nov 19 00:39:08 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4128 
 vendor AUO
xserver.version: 2:1.16.0-1ubuntu1

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


** Tags: apport-bug compiz-0.9 i386 ubuntu utopic

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

Title:
  problem

Status in “xorg” package in Ubuntu:
  New

Bug description:
  problem

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 19 01:04:41 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8340]
  InstallationDate: Installed on 2014-11-17 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  MachineType: ASUSTeK Computer INC. 1000H
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=062ba9ea-44e7-44de-846b-4c5990970a9c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2204
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1000H
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTek Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanM

[Touch-packages] [Bug 1353855] Re: Explicit g++ 4.9 dependency breaks cross-building

[Alberto Aguirre]

** Changed in: mir
Milestone: 0.9.0 => 0.10.0

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

Title:
  Explicit g++ 4.9 dependency breaks cross-building

Status in Mir:
  In Progress
Status in “mir” package in Ubuntu:
  Confirmed
Status in “qtmir” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  With the new explicit g++ 4.9 dependency apt falls over when trying to
  install cross-dependencies for e.g. Mir:

  The following packages have unmet dependencies:
   g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not 
going to be installed
  E: Build-dependencies for sbuild-build-depends-mir-dummy could not be 
satisfied.

  This means cross-building doesn't work for any packages that have that
  dependency added. We were told it's going to be fine due to 4.9
  becoming default, but it is now, and the situation remains.

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

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

[Touch-packages] [Bug 1377872] Re: Double-buffered compositing performance is very poor (30 FPS)

[Alberto Aguirre]

** Changed in: mir
Milestone: 0.9.0 => 0.10.0

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

Title:
  Double-buffered compositing performance is very poor (30 FPS)

Status in Mesa:
  Confirmed
Status in Mir:
  In Progress
Status in “mesa” package in Ubuntu:
  New

Bug description:
  Double-buffered compositing performance is poor.

  Fortunately we don't use double-buffering in our default compositor
  (mostly), and Ubuntu touch does not use the default compositor either.
  However, if you make the compositor double-buffered, then it quickly
  drops down to 30 FPS while not consuming any significant CPU or render
  time.

  Test case A:
  Convert your compositor to double buffering by the code change suggested in 
bug 1350725.

  Test case B (different bug?):
  Switch all clients to double-buffering using this branch:  
lp:~vanvugt/mir/double
  and then start a nested server.

  Now start a bunch of clients, and you will find they slow down to 30
  FPS after only starting a few. This does not happen with the default
  triple buffered compositor.

  I've been ignoring this issue for a little while [1] thinking I had simply 
run out of power, although suspected that can't be right as this is a powerful 
quad-core i7 and it's slowing down with only 10 clients.
  [1] https://bugs.launchpad.net/mir/+bug/1350725/comments/1

  Now today test case B has revealed (via MIR_CLIENT_PERF_REPORT) that
  the slowdown happens without using any significant render time (less
  than 2 ms) and without using any significant CPU (less than 20% of one
  out of four cores).

  So the conclusion is our default compositor is probably holding
  buffers for a little too long somewhere. Because that's the only
  sensible reason I can think of for my system to bog down to 30 FPS
  without stressing the CPU or GPU. We've got poor parallelism in our
  code somewhere. And once that's solved, we'll be able to make further
  improvements such as resolving bug 1350725.

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

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

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

[Alberto Aguirre]

** Changed in: mir
Milestone: 0.9.0 => 0.10.0

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

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

Status in Mir:
  Confirmed
Status in “mir” package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)

[Oliver S.]

Confirmed fixed for me, nice work!

http://packages.ubuntu.com/vivid/libblkid1

** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Does not detect hotplugged storage device (exfat)

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  It used to work then stopped for some reason.

  Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7c367968

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdb1  63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

  
  exfatfsck /dev/sdb1 finds no error

  mount -t exfat works, it's just auto-mounting that doesn't. 
  '-t' is required though, not sure if that's normal:
  mount: /dev/sdb1: more filesystems detected. This should not happen,
 use -t  to explicitly specify the filesystem type or
 use wipefs(8) to clean up the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  4 00:39:03 2014
  HotplugNewDevices: /dev/sdb1 /dev/sdb
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago)

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

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

[Touch-packages] [Bug 1393151] Re: mkfs.ext3 causes kernel panic on new WD 6 TB drive

[Andrew Sabot]

Ted, it was indeed a memory issue which only occurred once the buffers
were filled to a certain degree. Memtest was getting red all over the
screen. Thanks again, and status set to invalid.

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

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

Title:
  mkfs.ext3 causes kernel panic on new WD 6 TB drive

Status in “e2fsprogs” package in Ubuntu:
  Invalid

Bug description:
  mkfs.ext3 always causes a kernel panic on both of my WD 6 TB drives
  while writing the inode tables. Both drives were initialised using
  parted with a GPT and a single partition (mkpart primary 2048s 100%)

  sdc  8:32   0   5.5T  0 disk
  └─sdc1   8:33   0   5.5T  0 part
  sdd  8:48   0   5.5T  0 disk
  └─sdd1   8:49   0   5.5T  0 part

  mkfs.ext3 /dev/sdc1
  mke2fs 1.42.10 (18-May-2014)
  Creating filesystem with 1465130240 4k blocks and 18318 inodes
  Filesystem UUID: 1a6458a3-908d-48a0-a532-e9cbc1eb5ca4
  Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
   4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968,
   10240, 214990848, 51200, 550731776, 644972544

  Allocating group tables: done
  Writing inode tables:  4937/44713
  <-- KP occurs here -->

  mkfs.ext3 /dev/sdd1
  mke2fs 1.42.10 (18-May-2014)
  Creating filesystem with 1465130240 4k blocks and 18318 inodes
  Filesystem UUID: 3d6537ee-78f6-4a68-a833-e5dda4b69028
  Superblock backups stored on blocks:
   32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
   4096000, 7962624, 11239424, 2048, 23887872, 71663616, 78675968,
   10240, 214990848, 51200, 550731776, 644972544

  Allocating group tables: done
  Writing inode tables:  4997/44713
  <-- KP occurs here -->

  I'll have to try to take a photo of the KP since it's not being
  logged, I'm just seeing it on the screen.

  Creating an ext4 partition works fine but the crash just happens later
  after writing files to the partition. Disks seems to be fine smart-
  wise. It's unlikely that both disks are damaged in almost the same
  area without S.M.A.R.T. noticing it.

  --

  apt-cache policy e2fslibs:amd64
  e2fslibs:
    Installed: 1.42.9-3ubuntu1
    Candidate: 1.42.9-3ubuntu1
    Version table:
   *** 1.42.9-3ubuntu1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  --

  smartctl -H /dev/sdc
  smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build)
  Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

  smartctl -H /dev/sdc
  smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build)
  Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART overall-health self-assessment test result: PASSED

   smartctl -H /dev/sdd
  smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-39-generic] (local build)
  Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART overall-health self-assessment test result: PASSED

  --

   lshw -short
  H/W path   Device Class  Description
  
system H97N-WIFI (To be filled by O.E.M.)
  /0busH97N-WIFI
  /0/0  memory 64KiB BIOS
  /0/3d processor  Intel(R) Core(TM) i3-4160 CPU @ 
3.60GHz
  /0/3d/3e  memory 128KiB L1 cache
  /0/3d/3f  memory 512KiB L2 cache
  /0/3d/40  memory 3MiB L3 cache
  /0/42 memory 8GiB System Memory
  /0/42/0   memory 4GiB DIMM DDR3 Synchronous 1600 MHz 
(0.6 ns)
  /0/42/1   memory DIMM [empty]
  /0/42/2   memory 4GiB DIMM DDR3 Synchronous 1600 MHz 
(0.6 ns)
  /0/42/3   memory DIMM [empty]
  /0/100bridge 4th Gen Core Processor DRAM 
Controller
  /0/100/2  display4th Generation Core Processor Family 
Integrated Graphics Controller
  /0/100/3  multimedia Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller
  /0/100/14 bus9 Series Chipset Family USB xHCI 
Controller
  /0/100/16 communication  9 Seri

[Touch-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)

[Doug McMahon]

Fixed in 15.04 > 2.25.2-2ubuntu1 (2.25.2-1 source) so should be marked
"Fix Released"

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

Title:
  Does not detect hotplugged storage device (exfat)

Status in “util-linux” package in Ubuntu:
  Confirmed

Bug description:
  It used to work then stopped for some reason.

  Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7c367968

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdb1  63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

  
  exfatfsck /dev/sdb1 finds no error

  mount -t exfat works, it's just auto-mounting that doesn't. 
  '-t' is required though, not sure if that's normal:
  mount: /dev/sdb1: more filesystems detected. This should not happen,
 use -t  to explicitly specify the filesystem type or
 use wipefs(8) to clean up the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  4 00:39:03 2014
  HotplugNewDevices: /dev/sdb1 /dev/sdb
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago)

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

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

[Touch-packages] [Bug 1387734] Re: Location service uses the cached authorization, even if the user denied location access to an app

[Thomas Voß]

** Changed in: trust-store
   Status: Confirmed => In Progress

** Changed in: trust-store (Ubuntu Utopic)
   Status: Confirmed => In Progress

** Changed in: trust-store (Ubuntu Vivid)
   Status: Confirmed => In Progress

** Changed in: trust-store (Ubuntu RTM)
   Status: Confirmed => In Progress

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

Title:
  Location service uses the cached authorization, even if the user
  denied location access to an app

Status in trust-store:
  In Progress
Status in “location-service” package in Ubuntu:
  Invalid
Status in “trust-store” package in Ubuntu:
  In Progress
Status in “location-service” source package in Utopic:
  Invalid
Status in “trust-store” source package in Utopic:
  In Progress
Status in “location-service” source package in Vivid:
  Invalid
Status in “trust-store” source package in Vivid:
  In Progress
Status in “trust-store” package in Ubuntu RTM:
  In Progress

Bug description:
  The bug occurs after removing location access authorization to an
  application. The location is still available to the application,
  despite the user having revoked access from within USS > Privacy >
  Location.

  To reproduce:

  1. Open a map application, like Here map
  2. Allow access to location
  3. Switch to System Settings > Privacy > Location
  4. Disable location access for Maps
  5. Kill Here map, and restart it

  What should happen: you should not have access anymore (and should not see a 
prompt)
  What happens instead: the app still has access to your location, as shown in 
the logs:

  I1030 16:15:38.167752  3100 cached_agent_glog_reporter.cpp:32]
  CachedAgent::authenticate_request_with_parameters: Application pid:
  27975 Application uid: 32011 Application id:  com.nokia.heremaps_here
  Cached request:   Request(from: com.nokia.heremaps_here, feature: 0,
  when: 1414682114882519283, answer: granted)

  I confirmed that the trust store had recorded the authorization change
  as in:

  phablet@ubuntu-phablet:~$ sqlite3 
~/.local/share/UbuntuLocationService/trust.db "select * from requests"
  1|unconfined|0|1414098093331252474|1
  2|com.nokia.heremaps_here|0|1414682114882519283|1
  3|com.nokia.heremaps_here|0|1414682131206341515|0

  From a user's perspective: Despite having explicitly rejected trust to
  an application, the app would still be able to access services.

To manage notifications about this bug go to:
https://bugs.launchpad.net/trust-store/+bug/1387734/+subscriptions

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

[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop

[Chris Johnston]

I'm unable to reproduce this in vivid.. Could someone else please give
it a try in vivid and see if they are able to reproduce?

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE="de_DE.UTF-8"
  LC_NUMERIC="de_DE.UTF-8"
  LC_TIME="de_DE.UTF-8"
  LC_COLLATE="de_DE.UTF-8"
  LC_MONETARY="de_DE.UTF-8"
  LC_MESSAGES="de_DE.UTF-8"
  LC_PAPER="de_DE.UTF-8"
  LC_NAME="de_DE.UTF-8"
  LC_ADDRESS="de_DE.UTF-8"
  LC_TELEPHONE="de_DE.UTF-8"
  LC_MEASUREMENT="de_DE.UTF-8"
  LC_IDENTIFICATION="de_DE.UTF-8"
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL="pc105"
  XKBLAYOUT="de"
  XKBVARIANT=""
  XKBOPTIONS=""

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

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

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

[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

[Marc Deslauriers]

Ok, I've investigated this, and it turns out:

statd-mounting.conf intercepts nfs mounts and waits for the statd daemon to be 
run
statd.conf starts on (virtual-filesystems and started portmap ON_BOOT=y)
rpcbind.conf is what emits the started portmap event:

# For compatibility with older upstart jobs in Ubuntu
post-start exec initctl emit --no-wait started JOB=portmap ON_BOOT=$ON_BOOT
pre-stop exec initctl emit --no-wait stopping JOB=portmap

But, to actually work with upstart in 14.10, the INSTANCE variable has to be 
added, like so:
# For compatibility with older upstart jobs in Ubuntu
post-start exec initctl emit --no-wait started JOB=portmap INSTANCE='' 
ON_BOOT=$ON_BOOT
pre-stop exec initctl emit --no-wait stopping JOB=portmap INSTANCE=''


** This bug is no longer a duplicate of bug 1384502
   fstab entry for nfs /home fails to mount on boot

** Package changed: mountall (Ubuntu) => upstart (Ubuntu)

** Also affects: nfs-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nfs-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

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

[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

[Marc Deslauriers]

Upstart shouldn't require an INSTANCE variable for that to work, and
nfs-utils shouldn't be waiting on the portmap job, as that is for legacy
compatibility only.

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “nfs-utils” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

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

[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

[Marc Deslauriers]

Please disregard the last comment, that was unfortunately for a
different bug that affects 14.10 only.

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  Triaged

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1389164] Re: Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in /etc/fstab

[Marc Deslauriers]

** This bug is no longer a duplicate of bug 1384502
   fstab entry for nfs /home fails to mount on boot

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

Title:
  Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in
  /etc/fstab

Status in “mountall” package in Ubuntu:
  New

Bug description:
  Problem Description
  
  It seems the remote mounts in my /etc/fstab file are not being automatically 
mounted at bootup with ppc64le Ubuntu 14.10. This leads to some of my upstart 
scripts not running because they require certain mounts being available. I can 
give access to the machine via SSH key or password. Using mount -a or any other 
mount command works just fine after bootup. I don't personally notice a problem 
in logs with mounts.

  The machine is a VM hosted on a Power8 PowerKVM system running:
  # uname -a
  Linux kvm10d724t.rtp.raleigh.ibm.com 3.10.23-1700.pkvm2_1.2.ppc64 #1 SMP Mon 
Jun 2 20:14:25 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux
  # cat /etc/base-release
  IBM_PowerKVM release 2.1.0 build 18 Service (pkvm2_1)

  VM details:
  # uname -a
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.10
  DISTRIB_CODENAME=utopic
  DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)"

  If I recall correctly, we installed the 141002 daily build of Utopic
  Unicorn (14.10).

  I have implemented a workaround for now. I updated /etc/fstab to use
  IP addresses instead of names, put "mount -a" as the first non-
  commented line in /etc/init.d/mountnfs.sh and updated the crontab to
  run the jobs I had in the upstart configs. This works until the
  problem is fixed.

  ---uname output---
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ppc64le 
   
  Steps to Reproduce
  =
   Without the workaround implemented and NFS mounts in your /etc/fstab, boot 
up the machine. It should be evident the mount points aren't there with df -h.

  == Comment: #3 - Breno Henrique Leitao  -  ==
  I was able to reproduce this problem.
  NFS is not mounted automatically, but it is when you run 'mount -a'. 
  I also toggled ASYNCMOUNTNFS in /etc/defaults/rcS and no luck.

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

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

[Touch-packages] [Bug 1384502] Re: fstab entry for nfs /home fails to mount on boot

[Marc Deslauriers]

Ok, I've investigated this, and it turn out:

statd-mounting.conf intercepts nfs mounts and waits for the statd daemon to be 
run
statd.conf starts on (virtual-filesystems and started portmap ON_BOOT=y)
rpcbind.conf is what emits the started portmap event:

# For compatibility with older upstart jobs in Ubuntu
post-start exec initctl emit --no-wait started JOB=portmap ON_BOOT=$ON_BOOT
pre-stop exec initctl emit --no-wait stopping JOB=portmap

But, to actually work with upstart in 14.10, the INSTANCE variable has to be 
added, like so:
# For compatibility with older upstart jobs in Ubuntu
post-start exec initctl emit --no-wait started JOB=portmap INSTANCE='' 
ON_BOOT=$ON_BOOT
pre-stop exec initctl emit --no-wait stopping JOB=portmap INSTANCE=''

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

Title:
  fstab entry for nfs /home fails to mount on boot

Status in “mountall” package in Ubuntu:
  Triaged

Bug description:
  i'm uncertain exactly when this issue started as we use cfengine
  (verifies all expected mounts in place, manually mounts those that are
  not).  from a note i have i believe it goes back as far as lucid.

  the symptom is that an /etc/fstab entry for an nfs-mounted /home is
  not mounted during the system boot. once the system is network-
  accessible, manually running `mount -tnfs -av` as root (or using
  cfengine or any number of other solutions) is sufficient.

  per lp#836533 i added "--verbose" to /etc/init/mountall.conf and will attach 
the resulting /var/log/upstart/mountall.log and /etc/network/interfaces. the 
smoking gun appears to be:
  mount.nfs: Failed to resolve server nfs-home: Temporary failure in name 
resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mountall 2.53
  ProcVersionSignature: Ubuntu 3.13.0-38.65.lp1383921-generic 3.13.11.8
  Uname: Linux 3.13.0-38.65-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Oct 22 16:35:47 2014
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38.65-generic 
root=/dev/md0 ro consoleblank=0 console=tty0 console=ttyS2,115200n8 nomdmonddf 
nomdmonisw bootdegraded=true
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Touch-packages] [Bug 1390724] Re: Cups + cups-bsd not providing command line functionality

[Vittorio Beggi]

I cannot check. I need more precise specifications of the packages (deb) 
you want tested.
All I can say is that  the bug appeared after upgrading (with reinstall) 
from ubuntu 12.04 to 14.04.
I have some Debian "wheezy" installed in several different phisical 
computers and "virtual-boxes" where there isn't that problem.


Il 09/11/2014 00:07, Till Kamppeter ha scritto:
> Can you please check whether 1.7.2-0ubuntu1.2 already causes this
> problem? Or is the cause definitely the transition from -0ubuntu1.2 to
> -0ubuntu1.3?
>
> ** Changed in: cups (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Cups + cups-bsd not providing command line  functionality

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  lp does not connecto to any printer queue
  lpq does not show any queue, does not  manage anything

  cups installed, default printer assigned, cups-bsd installed.

  lpstat working but useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups-bsd 1.7.2-0ubuntu1.3
  ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov  8 12:50:14 2014
  InstallationDate: Installed on 2014-10-25 (13 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  Lpstat:
   device for Deskjet_F4100: hp:/usb/Deskjet_F4100_series?serial=CN79N5W41404TJ
   device for Hewlett-Packard-HP-LaserJet-1018: 
hp:/usb/HP_LaserJet_1018?serial=KP04ARL
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596
  Papersize: a4
  PpdFiles:
   Hewlett-Packard-HP-LaserJet-1018: HP LaserJet 1018 Foomatic/foo2zjs-z1 
(recommended)
   Deskjet_F4100: HP Deskjet f4100 Series, hpcups 3.14.10
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=5fa122db-cf90-4501-9d18-11ad242f9acc ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 785GM-E51 (MS-7596)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/09/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7596:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rn785GM-E51(MS-7596):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-7596
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

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

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

[Touch-packages] [Bug 1392744] Re: mako/vivid does not show install progress

[Alejandro J. Cura]

** Changed in: ubuntu-download-manager (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: unity-scope-click (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  mako/vivid does not show install progress

Status in “ubuntu-download-manager” package in Ubuntu:
  Invalid
Status in “unity-scope-click” package in Ubuntu:
  In Progress

Bug description:
  I use a n4 with the vivid channel and I'm on image #20. When I go to a
  app in the store and click on "Install" I see now change in the UI,
  i.e. no download progress, no change in the button etc. But I do see
  activity in the u-d-m download logs and eventually the screen will
  refresh (or at least turn blank) and the app is installed.

  The log also shows me some "download_db.cpp:285] Parameter count
  mismatch" errors.

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

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

[Touch-packages] [Bug 1389164] Re: Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in /etc/fstab

[Marc Deslauriers]

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

** This bug has been marked a duplicate of bug 1384502
   fstab entry for nfs /home fails to mount on boot

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

Title:
  Ubuntu 14.10 ppc64le not automatically mounting NFS mounts in
  /etc/fstab

Status in “mountall” package in Ubuntu:
  New

Bug description:
  Problem Description
  
  It seems the remote mounts in my /etc/fstab file are not being automatically 
mounted at bootup with ppc64le Ubuntu 14.10. This leads to some of my upstart 
scripts not running because they require certain mounts being available. I can 
give access to the machine via SSH key or password. Using mount -a or any other 
mount command works just fine after bootup. I don't personally notice a problem 
in logs with mounts.

  The machine is a VM hosted on a Power8 PowerKVM system running:
  # uname -a
  Linux kvm10d724t.rtp.raleigh.ibm.com 3.10.23-1700.pkvm2_1.2.ppc64 #1 SMP Mon 
Jun 2 20:14:25 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux
  # cat /etc/base-release
  IBM_PowerKVM release 2.1.0 build 18 Service (pkvm2_1)

  VM details:
  # uname -a
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.10
  DISTRIB_CODENAME=utopic
  DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)"

  If I recall correctly, we installed the 141002 daily build of Utopic
  Unicorn (14.10).

  I have implemented a workaround for now. I updated /etc/fstab to use
  IP addresses instead of names, put "mount -a" as the first non-
  commented line in /etc/init.d/mountnfs.sh and updated the crontab to
  run the jobs I had in the upstart configs. This works until the
  problem is fixed.

  ---uname output---
  Linux cit607 3.16.0-20-generic #27-Ubuntu SMP Wed Oct 1 17:24:38 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ppc64le 
   
  Steps to Reproduce
  =
   Without the workaround implemented and NFS mounts in your /etc/fstab, boot 
up the machine. It should be evident the mount points aren't there with df -h.

  == Comment: #3 - Breno Henrique Leitao  -  ==
  I was able to reproduce this problem.
  NFS is not mounted automatically, but it is when you run 'mount -a'. 
  I also toggled ASYNCMOUNTNFS in /etc/defaults/rcS and no luck.

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

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

[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically

[Marc Deslauriers]

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

** This bug has been marked a duplicate of bug 1384502
   fstab entry for nfs /home fails to mount on boot

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

Title:
  14.10: NFS drives in fstab not mounted automatically

Status in “mountall” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 14.10 (fresh install) my NFS drive does no longer
  mounts automatically at boot when the network is up and running.
  Manually running mount -a mounts the drive as expected and hacking a
  mount -a command into mountall-net.conf makes my system function
  normally again. Trying to manually to killall -USR1 mountall does not
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mountall 2.54build1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 10 20:37:39 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161

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

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

[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu

[Lorn Potter]

Has that network-manager fix hit ubuntu-rtm/devel yet? Because without
these qtbearer/qnam patches, I'm still seeing images loading issues.

The problem is not manually disabling the AP, but when moving (roaming)
from one to another, i.e. moving from wlan coverage to 3g coverage, or
from 3g to wlan

If you set up a Wlan AP, connect the phone to it, and then pull the
power plug on it so that AP disappears (or walk outside), the 3g
connection will become default, but  the old non patched QNAM is still
holding on to the now non invalid wlan configuration. Refreshing to
scopes will result in nothing being downloaded. The generic plugin does
not know when something is actually connected or just the interface is
'up'. It does not generate the needed signals for QNAM to continue
functioning without tearing down the QNAM object.

Even worse, if you bootup with 3g connected, walk into wlan coverage,
the QNAM get() request will be going through the still connected 3g
connection.

The tests mentioned at
https://wiki.ubuntu.com/Process/Merges/TestPlans/Qt#Testing_networking_code_in_Qt_base
do not cover "roaming" from one connected technology to another.

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

Title:
  QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  Invalid
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “ofono” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress
Status in “qtbase-opensource-src” package in Ubuntu RTM:
  New

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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

[Touch-packages] [Bug 1392744] Re: mako/vivid does not show install progress

[Rodney Dawes]

So this looks like it is very likely an issue with u-d-m having been
rebuilt when copied to vivid, while unity-scope-click was a binary copy,
and a change in perhaps Qt resulted in a binary incompatibility which
causes this crash, and a simple rebuild fixes it. As there is a change
to the scope in process of landing to vivid already, this issue should
be resolved when that lands and the scope is rebuilt and published.

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

Title:
  mako/vivid does not show install progress

Status in “ubuntu-download-manager” package in Ubuntu:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  I use a n4 with the vivid channel and I'm on image #20. When I go to a
  app in the store and click on "Install" I see now change in the UI,
  i.e. no download progress, no change in the button etc. But I do see
  activity in the u-d-m download logs and eventually the screen will
  refresh (or at least turn blank) and the app is installed.

  The log also shows me some "download_db.cpp:285] Parameter count
  mismatch" errors.

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

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

[Touch-packages] [Bug 668987] Re: New sound indicator only restores Rhythmbox on the desktop it was closed on.

[Stephen M. Webb]

Definitely not happening in Ubuntu 14.04 or later.

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

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

Title:
  New sound indicator only restores Rhythmbox on the desktop it was
  closed on.

Status in Compiz:
  Invalid
Status in “indicator-sound” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: rhythmbox

  Rhythmbox just got functionality back of minimizing to indicator on
  close (kind of) but restoring on the currently used desktop is broken.
  It restores on the same desktop it was closed on, forcing the user to
  switch back to that desktop again in order to use it.

  See the video for an example.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: rhythmbox 0.13.1-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Oct 31 00:19:17 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: rhythmbox

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

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

[Touch-packages] [Bug 1393281] Re: Print settings window reports "Print service is unavailable - Bad file descriptor" until cups is restarted

[Launchpad Bug Tracker]

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

** Changed in: cups (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/1393281

Title:
  Print settings window reports "Print service is unavailable - Bad file
  descriptor" until cups is restarted

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  In the KDE Print Settings window, there are no settings (as expected) but a 
message reading "Print service is unavailable - Bad file descriptor": 
  http://wstaw.org/m/2014/11/17/plasma-desktopKB2526.png

  When I restart the cups service, all is well and I can see print
  settings.

  Kubuntu 14.10

  $ apt-cache policy cups
  cups:
Installed: 1.7.5-3ubuntu2
Candidate: 1.7.5-3ubuntu2
Version table:
   *** 1.7.5-3ubuntu2 0
  500 http://mirror.cc.columbia.edu/pub/linux/ubuntu/archive/ 
utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1392744] Re: mako/vivid does not show install progress

[Ricardo Salveti]

** Attachment added: "downloads.db after reproducing the issue."
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1392744/+attachment/4263251/+files/downloads.db

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

Title:
  mako/vivid does not show install progress

Status in “ubuntu-download-manager” package in Ubuntu:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  I use a n4 with the vivid channel and I'm on image #20. When I go to a
  app in the store and click on "Install" I see now change in the UI,
  i.e. no download progress, no change in the button etc. But I do see
  activity in the u-d-m download logs and eventually the screen will
  refresh (or at least turn blank) and the app is installed.

  The log also shows me some "download_db.cpp:285] Parameter count
  mismatch" errors.

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

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

[Touch-packages] [Bug 1392744] Re: mako/vivid does not show install progress

[Alejandro J. Cura]

I'm not able to reproduce this any longer (mako, vivid #25), but some
people are experiencing this with the same configuration.

The code that uses the downloads.db has not been touched in ~6 months,
so it sounds likely that this problem is due to a broken file. I'll try
asking for the database from some affected user.

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

Title:
  mako/vivid does not show install progress

Status in “ubuntu-download-manager” package in Ubuntu:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  I use a n4 with the vivid channel and I'm on image #20. When I go to a
  app in the store and click on "Install" I see now change in the UI,
  i.e. no download progress, no change in the button etc. But I do see
  activity in the u-d-m download logs and eventually the screen will
  refresh (or at least turn blank) and the app is installed.

  The log also shows me some "download_db.cpp:285] Parameter count
  mismatch" errors.

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

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

[Touch-packages] [Bug 1369575] Re: Regression/Trusty: Ultron un-1 most keys no longer recognized

[Launchpad Bug Tracker]

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

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

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

Title:
  Regression/Trusty: Ultron un-1 most keys no longer recognized

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  Device: Ultron un-1 (USB Calculator/numerical keypad) [0603:0002]

  The keypad was working on 12.04 (Precise) but on 14.04 (Trusty) most
  keys do not work under Unity. They do work in the password dialog of
  lightdm and when switching to VT console. I am attaching input-events
  output from a shell window under Unity and running from the VT.

  It appears to me like the device tries to enforce num-lock status on
  each keypress and on the console this causes a led event as feedback.
  This seems to be missing when doing the same under Unity for some
  reason.

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

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

[Touch-packages] [Bug 89853] Re: [regression] 7.2 broke vesa: "No matching modes found"

[Bug Watch Updater]

Launchpad has imported 17 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=10238.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2007-03-09T15:09:04+00:00 Diego Sánchez Román wrote:

Hi, I have a ATI x1400 graphic card. Since xorg 7.2, I can't go into
graphic mode because X fails to start. It gives me the following error
"Vesa (0): No modes found". I got this problem with both Fedora Core 7
Test 2 and Ubuntu Feisty Daily CD (09/03/07). I can't use ati driver
either. It doesn't support x1000 series. I hope this to be solved so
that I can use these distros. Thanks

More Hardware Info:
  AMILO PI 1536:
  Intel Core2 7200 2Ghz
  2 GB RAM
  120 GB HD
  ATI x1400 128 MB

Please, ask me if you need more info.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/12


On 2007-03-11T18:16:07+00:00 Ajax-a wrote:

test2 had a broken vesa driver.  this should be working in test3, or
just update the vesa driver to the one in rawhide.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/24


On 2007-03-13T02:33:37+00:00 Sbrewer-k wrote:

I have this exact bug as well.  Is the Fedora fix going to be merged
back into the vesa driver?  If not, then the bug should not be closed
just yet.

This bug is affecting ubuntu as well:

https://launchpad.net/ubuntu/+source/xorg/+bug/89853


Reply at: 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/89853/comments/25


On 2007-03-13T06:32:01+00:00 Timo Aaltonen wrote:

Reopening since this is not fixed upstream, and affects other distros as
well.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/26


On 2007-04-16T22:30:50+00:00 Timo Aaltonen wrote:

the driver fails with:

(EE) VESA(0): No matching modes
(EE) Screen(s) found, but none have a usable configuration.

and it seems to affect at least some other r5xx-cards as well

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/42


On 2007-05-21T13:46:50+00:00 William Cattey wrote:

I am wondering if this is the same bug that is killing Red Hat 5, Ubuntu 7.04, 
and SuSE 10.1 on
the ATI Radeon X1300 card.

I will attach Xorg.0.log files from RHEL 4 which successfully configures the X 
server,
and RHEL 5 which says it gets a successful DDC read but which has no actual 
data from the display
with which to configure itself.

Is this due to the alleged i2c timeout issue reported in bug 6886?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/116


On 2007-05-21T13:55:27+00:00 William Cattey wrote:

Created attachment 10062
Successful DDC transfer.  X version 6.8.2. RHEL 4.5

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/117


On 2007-05-21T13:56:42+00:00 William Cattey wrote:

Created attachment 10064
Failed DDC transfer.  X version 7.1.1. RHEL 5.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/118


On 2007-05-21T13:57:46+00:00 William Cattey wrote:

Created attachment 10065
Failed DDC transfer.  X version 7.2.0. Ubuntu 7.04.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/119


On 2007-05-21T13:59:11+00:00 William Cattey wrote:

Created attachment 10066
Successful DDC transfer.  X version 7.1.1 with ATI proprietery driver.  Ubuntu 
6.10.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/89853/comments/120


On 2007-05-28T12:08:20+00:00 William Cattey wrote:

A friend and I have dug into the X server sources of RHEL 5, and understand the 
problem much better.  We've put details into the Red Hat buzilla bug 236416
at: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236416

There we provide a patch and various Xorg.0.log output and a detailed analysis.
For the convenience of people looking at the issue from this bug, we attach the 
patch here.

The patch adds printing of a hex dump of the EDID BIOS fetch, and a
sleep (2) which seems to enable 

[Touch-packages] [Bug 1393438] Re: "Enable location data" string displays untranslated

[Michi Henning]

Right you are! Sorry, I forgot about the special status of the
LocationDataNeeded, which is automagically added by the shell.

This is actually not a scopes-api issue, it's the shell that's not
translating this.

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

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

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

Title:
  "Enable location data" string displays untranslated

Status in “unity-scopes-api” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Using rtm 162 on krillin, several of the dash screens have a "enable
  location data" option, that strings seems to not be translatable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1393438/+subscriptions

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

[Touch-packages] [Bug 1393915] Re: uuidgen --random requires an argument

[Phillip Susi]

Works fine here.  What version of util-linux do you have?


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

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

Title:
  uuidgen --random requires an argument

Status in “util-linux” package in Ubuntu:
  Incomplete

Bug description:
  The man page of 'uuidgen' reports the options -r and --random as
  equivalent:

 -r, --random
Generate a random-based UUID.  This method creates a UUID 
consisting  mostly  of  random
bits.   It  requires that the operating system have a high 
quality random number genera‐
tor, such as /dev/random.

  But --random requires an argument:

  kurt@rodin:~$ uuidgen -r
  4aca676a-a3f1-4217-a35d-031c376c6274
  kurt@rodin:~$ uuidgen --random
  uuidgen: option '--random' requires an argument

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

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

[Touch-packages] [Bug 1393470] Re: Service cache doesn't update as services change

[Robert Schroll]

Note that this can cause confusion for apps that ship with a .service
file.  A fix may not take effect, or a breakage may not be noticed,
since the old, working configuration persisted.  (This latter case bit
me.)

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

Title:
  Service cache doesn't update as services change

Status in “libaccounts-glib” package in Ubuntu:
  Confirmed

Bug description:
  libaccounts-glib caches the list of current services inside its SQLite 
database, along with some basic information about the service (including the 
provider ID).
  However, if a .service file changes its  element, libaccounts-glib 
does not detect the change and still keeps the outdated information in its DB.

  One possible solution for this is to add a function like
  ag_account_manager_rebuild_cache() which re-reads all the .service
  files, and invoke this function from our "account-service" hook
  program.

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

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

[Touch-packages] [Bug 1390557] Re: [oobe] passcode screen continues after 3 visible dots to confirmation screen

[Launchpad Bug Tracker]

** Branch linked: lp:~ken-vandine/ubuntu-system-settings/rtm-1390557

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

Title:
  [oobe] passcode screen continues after 3 visible dots to confirmation
  screen

Status in Ubuntu UX bugs:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Invalid
Status in “ubuntu-system-settings” package in Ubuntu RTM:
  New

Bug description:
  krillin
  build 143

  Steps to reproduce in the initial set up wizard
  1. after selecting your language and  setting up wifi continue to the 
passcode set up screen
  2. type in your 4 digit passcode and pay attention to the dots representing 
the digits

  Expected result: all 4 dots are visible before screen moves on to
  confirm your passcode

  Actual result: only 3 dots are visible and it looks like you only
  picked a 3 digit passcode

  It would be great to have a slight delay and show user the last dot
  before screen moves on to the next step as we currently have when
  unlocking your device after swiping away the greeter.

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

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

[Touch-packages] [Bug 1385882] Re: Unable to mount iPad with IOS 8

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to mount iPad with IOS 8

Status in “libimobiledevice” package in Ubuntu:
  Confirmed

Bug description:
  I can't mount my iPad after I upgraded to IOS 8. After plugging in I
  get a series of error messages, also my iPad keep asking wether I
  trust my computer.

  I get messages like:
  Unable to mount ...'s iPad: Location is already mounted  - (it's not)
  Unable to mount iPhone: Unhandled lockdown error (-3) (also sometimes -20)

  If I remember correctly this happened last year after I upgraded to
  iOS 7.

  The problem exists in Utopic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 26 14:36:14 2014
  InstallationDate: Installed on 2014-01-10 (288 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: libimobiledevice
  UpgradeStatus: Upgraded to trusty on 2014-04-10 (198 days ago)

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

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

[Touch-packages] [Bug 1393923] [NEW] postfix (2.11.0-1) does not LDAP table lookup since libp11-kit0 (0.20.2-2ubuntu2)

[ITec]

Public bug reported:

Versions:

Ubuntu  14.04.1 LTS
postfix:amd64   2.11.0-1
postfix-ldap:amd64  2.11.0-1
libldap-2.4-2:amd64 2.4.31-1+nmu2ubuntu8
libgnutls26:amd64   2.12.23-12ubuntu2.1

libp11-kit0:amd64   0.18.3-2ubuntu1 (works)
libp11-kit0:amd64   0.20.2-2ubuntu2 (does not work)


Problem:

When receiving email, postfix does not do LDAP lookup for transport
tables any more.


With libp11-kit0 0.18.3-2ubuntu1 everything works fine. At a certain point 
postfix starts LDAP lookup and continues until it finds the needed LDAP item.

snippet from /var/log/mail.log:

...
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: In 
dict_ldap_lookup
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: No 
existing connection for LDAP source /etc/postfix/ldap-mda.cf, reopening
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: 
Connecting to server ldaps://db.itec.int ldaps://db1.itec.int 
ldaps://db2.itec.int
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: Actual 
Protocol version used is 3.
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: Binding 
to server ldaps://db.itec.int ldaps://db1.itec.int ldaps://db2.itec.int with dn 
uid=mta,ou=computers,dc=itec,dc=int
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: 
Successful bind to server ldaps://db.itec.int ldaps://db1.itec.int 
ldaps://db2.itec.int with dn uid=mta,ou=computers,dc=itec,dc=int
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_connect: Cached 
connection handle for LDAP source /etc/postfix/ldap-mda.cf
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: 
/etc/postfix/ldap-mda.cf: Searching with filter 
(&(objectClass=inetLocalMailRecipient)(&(mailRoutingAddress=\2A)(mailHost=mta.itec.int)))
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_get_values[1]: 
Search found 0 match(es)
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_get_values[1]: 
Leaving dict_ldap_get_values
Nov 18 17:27:47 mta postfix/trivial-rewrite[8879]: dict_ldap_lookup: Search 
returned nothing
...


With libp11-kit0 0.20.2-2ubuntu2 postfix does not start LDAP lookup. Instead it 
gets killed by signal.

snippet from /var/log/mail.log:

...
Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_lookup: In 
dict_ldap_lookup
Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_lookup: No 
existing connection for LDAP source /etc/postfix/ldap-mda.cf, reopening
Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_connect: 
Connecting to server ldaps://db.itec.int ldaps://db1.itec.int 
ldaps://db2.itec.int
Nov 18 19:07:11 mta postfix/trivial-rewrite[12032]: dict_ldap_connect: Actual 
Protocol version used is 3.
Nov 18 19:07:11 mta postfix/master[11997]: warning: process 
/usr/lib/postfix/trivial-rewrite pid 12032 killed by signal 11
Nov 18 19:07:11 mta postfix/master[11997]: warning: 
/usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
Nov 18 19:07:42 mta postfix/pickup[12000]: trigger_server_accept_local: trigger 
arrived
Nov 18 19:07:42 mta postfix/pickup[12000]: master_notify: status 0
Nov 18 19:07:42 mta postfix/pickup[12000]: master_notify: status 1
...

--> I am not able to upgrade to the current (trusty) version of
libp11-kit0. Instead I have to run an outdated (saucy) version of
libp11-kit0.

What can I do to get the current version running?

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

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

** Affects: p11-kit (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: p11-kit (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  postfix (2.11.0-1) does not LDAP table lookup since libp11-kit0
  (0.20.2-2ubuntu2)

Status in “gnutls26” package in Ubuntu:
  New
Status in “openldap” package in Ubuntu:
  New
Status in “p11-kit” package in Ubuntu:
  New
Status in “postfix” package in Ubuntu:
  New

Bug description:
  Versions:

  Ubuntu14.04.1 LTS
  postfix:amd64 2.11.0-1
  postfix-ldap:amd642.11.0-1
  libldap-2.4-2:amd64   2.4.31-1+nmu2ubuntu8
  libgnutls26:amd64 2.12.23-12ubuntu2.1

  libp11-kit0:amd64 0.18.3-2ubuntu1 (works)
  libp11-kit0:amd64 0.20.2-2ubuntu2 (does not work)

  
  Problem:

  When receiving email, postfix does not do LDAP lookup for transport
  tables any more.

  
  With libp11-kit0 0.18.3-2ubuntu1 everything works fine. At a cer

[Touch-packages] [Bug 1377286] Re: Update Indicator Title Strings

[Launchpad Bug Tracker]

** Branch linked: lp:~ken-vandine/ubuntu-system-settings/rtm-1377286

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

Title:
  Update Indicator Title Strings

Status in Bluetooth Menu:
  Invalid
Status in The Date and Time Indicator:
  Fix Released
Status in Display Indicator:
  Fix Released
Status in Indicator Location:
  Invalid
Status in The Messaging Menu:
  Fix Released
Status in Network Menu:
  Invalid
Status in The Power Indicator:
  Invalid
Status in Sound Menu:
  Invalid
Status in Transfer Indicator:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  Fix Released
Status in “indicator-display” package in Ubuntu:
  Fix Released
Status in “indicator-messages” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu:
  Fix Released
Status in “ubuntu-system-settings” package in Ubuntu RTM:
  New

Bug description:
  Design change

  The space available for the title has changed, so the strings need to
  as well:

  Transfer: "Files"
  Location: "Location"
  Bluetooth: "Bluetooth"
  Network: "Network"
  Messaging: "Notifications" (also in System Settings > "Notifications")
  Power: "Battery"
  Datetime: "Time & Date"
  Sound: "Sound"
  Display: "Rotation"

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

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

[Touch-packages] [Bug 1393915] [NEW] uuidgen --random requires an argument

[Kurt Huwig]

Public bug reported:

The man page of 'uuidgen' reports the options -r and --random as
equivalent:

   -r, --random
  Generate a random-based UUID.  This method creates a UUID 
consisting  mostly  of  random
  bits.   It  requires that the operating system have a high 
quality random number genera‐
  tor, such as /dev/random.

But --random requires an argument:

kurt@rodin:~$ uuidgen -r
4aca676a-a3f1-4217-a35d-031c376c6274
kurt@rodin:~$ uuidgen --random
uuidgen: option '--random' requires an argument

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  uuidgen --random requires an argument

Status in “util-linux” package in Ubuntu:
  New

Bug description:
  The man page of 'uuidgen' reports the options -r and --random as
  equivalent:

 -r, --random
Generate a random-based UUID.  This method creates a UUID 
consisting  mostly  of  random
bits.   It  requires that the operating system have a high 
quality random number genera‐
tor, such as /dev/random.

  But --random requires an argument:

  kurt@rodin:~$ uuidgen -r
  4aca676a-a3f1-4217-a35d-031c376c6274
  kurt@rodin:~$ uuidgen --random
  uuidgen: option '--random' requires an argument

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

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

[Touch-packages] [Bug 1393410] Re: [TOPBLOCKER] Apps with prices are not shown by default

[Launchpad Bug Tracker]

This bug was fixed in the package unity-scope-click -
0.1.1+15.04.20141117~rtm-0ubuntu1

---
unity-scope-click (0.1.1+15.04.20141117~rtm-0ubuntu1) 14.09; urgency=low

  [ Alejandro J. Cura ]
  * Enable purchases by default (LP: #1393410)
 -- Ubuntu daily releaseMon, 17 Nov 2014 
17:25:46 +

** Changed in: unity-scope-click (Ubuntu RTM)
   Status: In Progress => Fix Released

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

Title:
  [TOPBLOCKER] Apps with prices are not shown by default

Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  Fix Released

Bug description:
  The current default in the scope is to not show apps with prices, and
  they are only shown after running a special script. This was done like
  that so the payments feature could be tested in a more controlled
  environment.

  Now it needs to be enabled so the default is to show apps with prices
  to everybody.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1393410/+subscriptions

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

[Touch-packages] [Bug 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/initramfs-tools-ubuntu-touch

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

Title:
  [TOPBLOCKER] file corruption on touch images in rw portions of the
  filesystem

Status in “android” package in Ubuntu:
  Fix Released
Status in “android-tools” package in Ubuntu:
  In Progress
Status in “initramfs-tools-ubuntu-touch” package in Ubuntu:
  Fix Released
Status in “linux-mako” package in Ubuntu:
  New
Status in “android” package in Ubuntu RTM:
  In Progress
Status in “android-tools” package in Ubuntu RTM:
  In Progress
Status in “initramfs-tools-ubuntu-touch” package in Ubuntu RTM:
  In Progress
Status in “linux-mako” package in Ubuntu RTM:
  New

Bug description:
  Symptoms are that cache files in /var/cache/apparmor and profiles in
  /var/lib/apparmor/profiles are sometimes corrupted after a reboot.
  We've already fixed several bugs in the apparmor and click-apparmor
  and made both more robust in the face of corruption and we've reduced
  the impact when there is a corrupted profile, but we've still not
  found the cause of the corruption. This corruption can still affect
  real-world devices: if a profile in /var/lib/apparmor/profiles is
  corrupted and the cache file is out of date, then the profile won't
  compile and that app/scope won't start.

  Workaround: remove the affected profile and then run 'sudo aa-
  clickhook'. This obviously is not viable on an end-user device.

  The investigation is ongoing and this may not be a problem with the
  kernel at all, so this bug may be retargeted to another project.

  The security team and the kernel team have discussed this a lot and
  Colin King is currently looking at this. This bug is just so it can be
  tracked. Here is an excerpt from my latest email to Colin:

  "I believe I have conclusively ruled out apparmor_parser and aa-
  clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the
  test output:

  http://paste.ubuntu.com/8648109/

  Specifically, home/bug/test-with-true.sh changes the interesting parts
  of the algorithm to:

  1. wait for unity8 to start (this ensures the apparmor upstart job is 
finished)
  2. restore apparmor_parser and aa-clickhook, if needed
  3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles...
     /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser
     and aa-clickhook were /bin/true during boot so they could not have changed
     /var/lib/apparmor/profiles)
  4. verify the profiles, exit with error if they do not
  5. alternately upgrade/downgrade the packages
  6. verify the profiles, exit with error if they do not
  7. copy the known good profiles in the previous step to /home/bug/profiles...
  8. have apparmor_parser and aa-clickhook point to /bin/true
  9. reboot
  10. go to step 1

  In the paste you'll notice that in step 6 the profiles were
  successfully created by the installation of the packages, then
  verified, then copied aside, then apparmor_parser and aa-clickhook
  diverted, then rebooted, only to have the profiles in
  /var/lib/apparmor/profiles be different than what was copied aside. It
  would be nice to verify on your device as well (I reproduced several
  times here) and verify the reproducer algorithm. I think this suggests
  this is a kernel issue and not userspace.

  IMPORTANT: you will want to update the reproducer and refollow all of these 
steps (ie, I updated the scripts, the debs, the sudoers file, etc):
  $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz
  $ tar -zxvf ./aa-corruption.tar.gz
  ...

  $ adb push ./aa-corruption.tar.gz /tmp
  $ adb shell
  phablet@ubuntu-phablet:~$ cd /tmp
  phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz
  phablet@ubuntu-phablet:~$ sudo mount -o remount,rw /
  phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
  /etc/sudoers.d/
  phablet@ubuntu-phablet:~$ sudo mount -o remount,ro /
  phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home
  phablet@ubuntu-phablet:~$ exit
  $ cd ./aa-corruption
  $ ./test-from-host.sh
  ...

  The old script is still in place. Simply adjust ./test-from-host.sh to have:
  testscript=/home/bug/test.sh
  #testscript=/home/bug/test-with-true.sh"

  The kernel team has verified the above reproducer and symptoms.

  Related bugs:
  * bug 1371771
  * bug 1371765
  * bug 1377338

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

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

[Touch-packages] [Bug 1392744] Re: mako/vivid does not show install progress

[Launchpad Bug Tracker]

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

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

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

Title:
  mako/vivid does not show install progress

Status in “ubuntu-download-manager” package in Ubuntu:
  Confirmed
Status in “unity-scope-click” package in Ubuntu:
  Triaged

Bug description:
  I use a n4 with the vivid channel and I'm on image #20. When I go to a
  app in the store and click on "Install" I see now change in the UI,
  i.e. no download progress, no change in the button etc. But I do see
  activity in the u-d-m download logs and eventually the screen will
  refresh (or at least turn blank) and the app is installed.

  The log also shows me some "download_db.cpp:285] Parameter count
  mismatch" errors.

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

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

[Touch-packages] [Bug 1393901] Re: No feedback when installing apps on vivid 25/mako

[Alejandro J. Cura]

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

** This bug has been marked a duplicate of bug 1392744
   mako/vivid does not show install progress

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

Title:
  No feedback when installing apps on vivid 25/mako

Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  current build number: 25
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2014-11-18 16:48:43
  version version: 25
  version ubuntu: 20141118
  version device: 20141117.1
  version custom: 20141118

  No feedback at all from the ubuntu store after pressing 'Install' to
  install a new application.

  The app gets installed though, but only shows up at Ubuntu Store
  scopes after opening it again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1393901/+subscriptions

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