[Touch-packages] [Bug 1434396] Re: Xserver does not start on boot (low-graphics mode)

2015-04-09 Thread professordes
Interesting - another Thinkpad X240 _wasn't_ fixed by today's update,
but when I checked the configuration it also had sddm installed (thought
it wasn't using it as the default login display manager). Removing sddm,
which still allows the kubuntu desktop package to remain, gives a
functioning systemd+lightdm.

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

Title:
  Xserver does not start on boot (low-graphics mode)

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  After upgrading to (32bit) vivid I hadn't got any problem, but since a
  day (daily upgraded) booting results in a dialog saying low graphics
  mode and a dialog window about this. Choosing running in default mode
  causes to boot splash to be shown forever. if I choose exit to
  console, log in then service stop then start for lightdm, it works
  then though. Maybe is not Xserver bug, but the new init system
  (systemd) race condition of starting things, or such?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu3
  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
  CurrentDesktop: Unity
  Date: Fri Mar 20 07:35:37 2015
  DistUpgraded: 2014-10-24 18:45:04,038 DEBUG enabling apt cron job
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.26, 3.19.0-9-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21dd]
  InstallationDate: Installed on 2012-03-03 ( days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  MachineType: LENOVO 5016NW6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=8df578aa-47e3-483f-b694-bf7effd24b7d ro i915.semaphores=0 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to vivid on 2014-10-24 (146 days ago)
  dmi.bios.date: 11/04/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET38WW (1.15 )
  dmi.board.name: 5016NW6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET38WW(1.15):bd11/04/2011:svnLENOVO:pn5016NW6:pvrThinkPadL520:rvnLENOVO:rn5016NW6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 5016NW6
  dmi.product.version: ThinkPad L520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  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.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Fri Mar 20 07:25:51 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9196 
   vendor AUO
  xserver.version: 2:1.17.1-0ubuntu3

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

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


[Touch-packages] [Bug 1441914] Re: lua:socket settimeout does not work

2015-04-09 Thread Stephen M. Webb
** Package changed: unity (Ubuntu) = luasocket (Ubuntu)

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

Title:
  lua:socket settimeout does not work

Status in luasocket package in Ubuntu:
  New

Bug description:
  Ubuntu Version:  Ubuntu 14.04.2 LTS
  package lua-socket:i386 3.0~rc1-3

  On Ubuntu 14.04, lua socket settimeout does not work as expected.  On a tcp 
socket, it causes the next receive to close the connection immediately.
  It works correctly on Ubuntu 12.04 and debian 7.

  To reproduce:
  install packages lua5.1 and lua-socket
  Take the echo server example from the introduction to luasocket:
  http://w3.impa.br/~diego/software/luasocket/introduction.html
  Put it in a file echo.lua and run it with lua echo.lua
  From another window, use telnet localhost {port} to connect to the echo server
  Result:  Immediately after connecting, the server closes the connection.
  Expected Result:  The server should wait 10 seconds for input, then close the 
connection.

  
  package version that works correctly in debian 7:  lua-socket:i386 2.0.2-8

  
  -
  A copy of the example (echo.lua):

  -- load namespace
  local socket = require(socket)
  -- create a TCP socket and bind it to the local host, at any port
  local server = assert(socket.bind(*, 0))
  -- find out which port the OS chose for us
  local ip, port = server:getsockname()
  -- print a message informing what's up
  print(Please telnet to localhost on port  .. port)
  print(After connecting, you have 10s to enter a line to be echoed)
  -- loop forever waiting for clients
  while 1 do
-- wait for a connection from any client
local client = server:accept()
-- make sure we don't block waiting for this client's line
client:settimeout(10)
-- receive the line
local line, err = client:receive()
-- if there was no error, send it back to the client
if not err then client:send(line .. \n) end
-- done with client, close the object
client:close()
  end

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

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


[Touch-packages] [Bug 1439793] Re: deb-systemd-helper crashes while removing packages with unusual (but legal) Alias in unit config

2015-04-09 Thread Martin Pitt
Simple reproducer:

$ cat /lib/systemd/system/selfalias.service
[Unit]
Description=alias to self

[Service]
ExecStart=/bin/true

[Install]
WantedBy=multi-user.target
Alias=selfalias.service

$ sudo DPKG_MAINTSCRIPT_PACKAGE=1 deb-systemd-helper enable selfalias.service
$ sudo mv /lib/systemd/system/selfalias.service{,.removed}
$ sudo _DEB_SYSTEMD_HELPER_DEBUG=1 DPKG_MAINTSCRIPT_PACKAGE=1 
deb-systemd-helper mask selfalias.service


** Changed in: init-system-helpers (Ubuntu)
   Status: New = Triaged

** Changed in: init-system-helpers (Ubuntu)
   Importance: Undecided = Medium

** Changed in: init-system-helpers (Ubuntu)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  deb-systemd-helper crashes while removing packages with unusual (but
  legal) Alias in unit config

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

Bug description:
  While working on mysql-5.6 package we met unusual (maybe even partially 
incorrect) Alias option in systemd unit config:
  Alias=mysql.service
  It is unusual because mysql.service is the original name of the service which 
can be found inside /lib/systemd/system/... This Alias option doesn't make 
any sense (mysql service will be accessible as mysql.service even without this 
alias) and my assumption is that it was created because the author was not sure 
if it's okay not to have any aliases at all or you need at least one. Anyhow 
this seems to be legal to do that (i was not able to find any documents which 
state that this is incorrect) even if it's something useless.

  Installation went well and the following alias symlink has been created:
  /etc/systemd/system/mysq.service -- /lib/systemd/system/mysql.service
  Service was accessible via systemctl and everything was fine.

  When you try to remove/purge the package you get the following error:
  /usr/bin/deb-systemd-helper: error: unable to link 
/etc/systemd/system/mysql.service to /dev/null: File exists
  This happens because deb-systemd-helper tries to 'mask' service the following 
way:

  sub mask_service {
  my ($scriptname, $service_path) = @_;

  my $mask_link = '/etc/systemd/system/' . basename($service_path);

  if (-e $mask_link) {
  # If the link already exists, don’t do anything.
  return if -l $mask_link  readlink($mask_link) eq '/dev/null';

  debug $mask_link already exists, not masking.;
  return;
  }

  make_path(dirname($mask_link));
  symlink('/dev/null', $mask_link) or
  error(unable to link $mask_link to /dev/null: $!);
  ...
  }

  Check for '-e $mask_link' FAILS because symlink's TARGET
  (/lib/systemd/system/mysql.service) doesn't exists while doing postrm
  and '-e' FOLLOWS symlinks. That's why we go to symlink(...) call
  directly which fails because symlink already exists.

  WORKAROUND: If apt-get remove/purge crashes with the error mentioned
  above you need to manually remove symlink inside /etc/systemd/system
  (/etc/systemd/system/mysql.service in our case) and rerun apt-get
  remove/purge.

  I'm not sure if we want to fix that.
  On one hand, this situation is pretty rare.
  On other hand though, such Alias=original-name situation is somewhat legal 
and we may want to handle it correctly.

  This issue with Alias= has been fixed (by removing this useless Alias)
  in mysql-5.6 so that's not a blocker for us.

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

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


[Touch-packages] [Bug 1442340] [NEW] telephony-service-indicator crash on an incoming sms

2015-04-09 Thread Pat McGowan
Public bug reported:

Sent an sms
phone was awake and sitting in the messaging app
I heard something to make me look at the phone but not a notification sound, 
maybe vibration
unity restarted and when it came back up there was an SMS notification
Crash file created at that time

mako running rtm build 219
Rick has reported this occurring on Vivid arale as well

** Affects: telephony-service (Ubuntu)
 Importance: High
 Status: New

** Attachment added: _usr_bin_telephony-service-indicator.32011.crash
   
https://bugs.launchpad.net/bugs/1442340/+attachment/4370846/+files/_usr_bin_telephony-service-indicator.32011.crash

** Description changed:

  Sent an sms
  phone was awake and sitting in the messaging app
  I heard something to make me look at the phone but not a notification sound, 
maybe vibration
  unity restarted and when it came back up there was an SMS notification
  Crash file created at that time
  
+ mako running rtm build 219
  Rick has reported this occurring on Vivid arale as well

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

Title:
  telephony-service-indicator crash on an incoming sms

Status in telephony-service package in Ubuntu:
  New

Bug description:
  Sent an sms
  phone was awake and sitting in the messaging app
  I heard something to make me look at the phone but not a notification sound, 
maybe vibration
  unity restarted and when it came back up there was an SMS notification
  Crash file created at that time

  mako running rtm build 219
  Rick has reported this occurring on Vivid arale as well

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

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


[Touch-packages] [Bug 1442159] [NEW] Add a configuration option to keep terminals opened by apport opened

2015-04-09 Thread Karl-Philipp Richter
Public bug reported:

`gnome-terminals` which are opened by `apport` to monitor the
installation of necessary deb packages for local investigation,
production of `gdb` backtraces, etc. are closed immediately after
success, but after failure as well (e.g. if `apt-get` can't get its
global lock, or another issue occurs). For debugging `apport` it'd be
very useful to have a configuration option which allows the terminals
opened by `apport` to stay opened after a failure.

Some details and workarounds have been discussed at (this askubuntu.com
question)[http://askubuntu.com/questions/600875/how-to-keep-terminal-
for-installation-of-debugging-symbols-of-apports-local-inv].

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17-0ubuntu1
Uname: Linux 4.0.0-04rc7-generic x86_64
NonfreeKernelModules: nvidia
ApportLog:
 
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr  9 15:24:55 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-04-02 (6 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  Add a configuration option to keep terminals opened by apport opened

Status in apport package in Ubuntu:
  New

Bug description:
  `gnome-terminals` which are opened by `apport` to monitor the
  installation of necessary deb packages for local investigation,
  production of `gdb` backtraces, etc. are closed immediately after
  success, but after failure as well (e.g. if `apt-get` can't get its
  global lock, or another issue occurs). For debugging `apport` it'd be
  very useful to have a configuration option which allows the terminals
  opened by `apport` to stay opened after a failure.

  Some details and workarounds have been discussed at (this
  askubuntu.com question)[http://askubuntu.com/questions/600875/how-to-
  keep-terminal-for-installation-of-debugging-symbols-of-apports-local-
  inv].

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17-0ubuntu1
  Uname: Linux 4.0.0-04rc7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  9 15:24:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-02 (6 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1437006] Re: [browser] bottom edge gesture graphic should have a numeric representation of the number of open tabs

2015-04-09 Thread John Lea
** Changed in: ubuntu-ux
 Assignee: Jouni Helminen (jounihelminen) = Benjamin Keyser (bjkeyser)

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

Title:
  [browser] bottom edge gesture graphic should have a numeric
  representation of the number of open tabs

Status in Ubuntu UX bugs:
  Triaged
Status in Web Browser App:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  This is a UX issue.
  Currently, the bottom edge graphic is a squat caret. Aside from the caret, it 
would be nice to have a numeric display of the number of open tabs. Today while 
trying to use a website, my actions resulted in the opening of multiple tabs, 
but there was no change in the browser that would suggest any tabs were opened.

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

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


[Touch-packages] [Bug 1442345] Re: unity-scope-home crashed with SIGSEGV in g_main_context_dispatch()

2015-04-09 Thread Apport retracing service
*** This bug is a duplicate of bug 1292349 ***
https://bugs.launchpad.net/bugs/1292349

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

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1442345/+attachment/4370871/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1442345/+attachment/4370873/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1442345/+attachment/4370876/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1442345/+attachment/4370877/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1442345/+attachment/4370878/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1442345/+attachment/4370879/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1442345/+attachment/4370880/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-scope-home crashed with SIGSEGV in g_main_context_dispatch()

Status in unity-scope-home package in Ubuntu:
  New

Bug description:
  Suddenly appeared this error when i tried to set up my privacy from
  settings

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity-scope-home 6.8.2+15.04.20150311.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  9 22:58:07 2015
  ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home
  InstallationDate: Installed on 2014-01-08 (455 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home
  SegvAnalysis:
   Segfault happened at: 0x42265b:  mov(%rbx),%rdi
   PC (0x0042265b) ok
   source (%rbx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-scope-home
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: unity-scope-home crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-home/+bug/1442345/+subscriptions

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


[Touch-packages] [Bug 1403600] Re: [phone-app] Numeric keyboard doesn't work properly when you press quickly

2015-04-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [phone-app] Numeric keyboard doesn't work properly when you press
  quickly

Status in the base for Ubuntu mobile products:
  New
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed
Status in dialer-app package in Ubuntu RTM:
  New

Bug description:
  Enviroment

  Product: Krillin bq Aquaris E4.5 Ubuntu Edition
  FW version: Ubuntu 14.10 (r5)
  HW version: MP
  Material:

  Description

  Steps to Reproduce:

  1. Opens default phone call application.
  2. Press quickly the numbers that you want.
  3. It does not sound with each touch properly.

  Actual Result:

  It doesn´t sound a beep with each touch. It sounds one beep for two
  touches about.

  Expected Result:

  It must sound a beep with each touch.

  Reproducibility: 100%

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

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


[Touch-packages] [Bug 1440070] Re: openssh-server attempts to connect to upstart and the connection is refused

2015-04-09 Thread Launchpad Bug Tracker
This bug was fixed in the package openssh - 1:6.7p1-5ubuntu1

---
openssh (1:6.7p1-5ubuntu1) vivid; urgency=medium

  * openssh-server.postinst: Quiesce Unable to connect to Upstart error
message from initctl if upstart is installed, but not the current init
system. (LP: #1440070)
  * openssh-server.postinst: Fix version comparisons of upgrade adjustments to
not apply to fresh installs.
 -- Martin Pitt martin.p...@ubuntu.com   Thu, 09 Apr 2015 09:20:36 +0200

** Changed in: openssh (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  openssh-server attempts to connect to upstart and the connection is
  refused

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh package in Debian:
  Unknown

Bug description:
  lsb_release -rd:
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  pkg-name:
  christian@Moustachio:~/Code$ apt-cache policy openssh-server
  openssh-server:
Installed: 1:6.7p1-5
Candidate: 1:6.7p1-5
Version table:
   *** 1:6.7p1-5 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  
  On Ubuntu 15.04 (Vivid Ververt) the installation of the package 
openssh-server displays the following error message:

  initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused

  Running 'systemctl status ssh' shows that systemd knows about the
  service:

  christian@Moustachio:~/Code$ ubuntu-bug openssh-server
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:12244): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  christian@Moustachio:~/Code$ systemctl status ssh
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: active (running) since Fri 2015-04-03 07:43:01 MDT; 4min 41s ago
   Main PID: 11689 (sshd)
 CGroup: /system.slice/ssh.service
 └─11689 /usr/sbin/sshd -D

  Apr 03 07:43:01 Moustachio systemd[1]: Started OpenBSD Secure Shell server.
  Apr 03 07:43:01 Moustachio systemd[1]: Starting OpenBSD Secure Shell server...
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on 0.0.0.0 port 22.
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on :: port 22.

  It appears that sshd is attempting to register with upstart and with
  systemd. SInce Ubuntu 15.04 upstart has been replaced with systemd. I
  expected openssh-server on Ubuntu 15.04 to not want to use upstart. It
  does properly use systemd, it just prints an error about trying to
  tallk to upstart.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssh-server 1:6.7p1-5
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  3 07:45:13 2015
  InstallationDate: Installed on 2015-03-23 (11 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150322)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1431128] Re: screen remains blank after waking up from suspend

2015-04-09 Thread Ara Pulido
** No longer affects: oem-priority/trusty

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

Title:
  screen remains blank after waking up from suspend

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Trusty:
  New

Bug description:
  Steps:
  1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here)
  2. Press any key on the keyboard or the Power button to wake the device up

  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.

  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

  Additional information:

  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.

  - Please note that this problem does NOT happen when suspending from
  the User Menu or using the Power button and selecting Suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1439955] Re: nfs root script breaks with absolute /sbin/init symlinks

2015-04-09 Thread Martin Pitt
** Changed in: initramfs-tools (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  nfs root script breaks with absolute /sbin/init symlinks

Status in initramfs-tools package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Debian:
  Unknown

Bug description:
  The initramfs boot script try to mount the root filesystem into /root
  and look for a /sbin/init file inside that folder. systemd installs
  /sbin/init as a link to /lib/systemd/systemd, which the initramfs
  scripts can't find (because the link is an absolute path and the root
  is mounted under /root).

  Making that link a relative path fixes the problem (i.e. making it
  ../lib/systemd/systemd).

  Please, see /usr/share/initramfs-tools/scripts/nfs for the affected
  script.

  
  I believe this should be fixed before the release of 15.04, as it breaks all 
nfs root installs.

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

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


[Touch-packages] [Bug 1437305] Re: Wrong date day icon display and one day before events day in month view

2015-04-09 Thread Alexander Dobetsberger
** Changed in: ubuntu-calendar-app
   Status: New = Incomplete

** Changed in: ubuntu-calendar-app
   Status: Incomplete = Confirmed

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

Title:
  Wrong date day icon display and one day before events day in month
  view

Status in Calendar application for Ubuntu devices:
  Confirmed
Status in qtorganizer5-eds package in Ubuntu:
  Confirmed

Bug description:
  All day events display one day too early in month view.

  Create an all day event on 27th March 2015, move month view and the
  dot is against 26th March.  Can be corrected by changing all day event
  to span 27th to 28th March but now event displays over two days on day
  view. Icon displays wrong date: next day date

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

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


[Touch-packages] [Bug 1429135] Re: webbrowser-app crashed with SIGSEGV in XQueryExtension()

2015-04-09 Thread Chris Coulson
WONTFIX for 1.5 as there's not likely to be another release from that
branch now. This will be in the 1.6 release instead

** Changed in: oxide/1.6
Milestone: 1.6.1 = 1.6.2

** Changed in: oxide/1.5
   Status: Triaged = Won't Fix

** Changed in: oxide/1.5
Milestone: 1.5.6 = None

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

Title:
  webbrowser-app crashed with SIGSEGV in XQueryExtension()

Status in Oxide Webview:
  Fix Released
Status in Oxide 1.5 series:
  Won't Fix
Status in Oxide 1.6 series:
  Triaged
Status in oxide-qt package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  This occurs when starting the webbrowser app in a Unity 8 desktop
  session.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webbrowser-app 0.23+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  Date: Thu Mar  5 10:41:06 2015
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2013-03-18 (717 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XInitExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XextAddDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
  Title: webbrowser-app crashed with SIGSEGV in XQueryExtension()
  UpgradeStatus: Upgraded to vivid on 2014-10-20 (136 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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


[Touch-packages] [Bug 1441975] Re: have not shadows

2015-04-09 Thread Launchpad Bug Tracker
** Branch linked: lp:~laney/ubuntu-themes/menu-shadows

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

Title:
  have not shadows

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  nautilus and desktop have not shadows on context menus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  9 08:54:22 2015
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2015-03-05 (34 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2015-03-05T22:46:49.143864

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

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


[Touch-packages] [Bug 1432030] Re: improper simultaneity of fscks

2015-04-09 Thread gregrwm
quite unlike mountall, systemd does a good job of scheduling exactly as
many simultaneous FSCKs as i have spindles.

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

Title:
  improper simultaneity of fscks

Status in mountall package in Ubuntu:
  Triaged

Bug description:
  all fscks are scheduled and run simultaneously.  for those on
  different spindles, that would be great.  for those sharing a spindle,
  this is terribly inefficient.  checking all filesystems on this box
  simultaneously spends nearly a half hour.  when sorted out so that
  simultaneity is only across different spindles, it's done within a few
  minutes.  that's the way it used to be, and still is on other distros.

  i can certainly imagine mountall might be intending to have an
  algorithm that sorts simultaneity by spindles.  if it intends it, it
  doesn't work.

  even if such an algorithm usually worked well, fstab should still be
  interpreted such that if the fsck column specifies values greater than
  2, then the simultaneity specified in fstab should be followed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: mountall 2.54ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Fri Mar 13 14:54:37 2015
  InstallationDate: Installed on 2015-01-16 (56 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150114)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz ro 
root=UUID=5116dd42-c618-49a4-885e-84c697b53abd panic=30
  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/1432030/+subscriptions

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


[Touch-packages] [Bug 1434712] Re: Can't swipe from the right in the setup at first launch

2015-04-09 Thread Michael Terry
Indeed, wizard-has-run will not stop the tutorial.  That's only for the
welcome wizard on first boot.

The correct workaround for the tutorial is the dbus-send line above.

But we have a real fix waiting to land in vivid that will skip the
troublesome pages of the tutorial in desktop mode.

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

Title:
  Can't swipe from the right in the setup at first launch

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 15.04 on a desktop pc with a mouse. Version
  8.02+15.04.20150318-0ubuntu1 of the unity8 package.

  The initial setup when first launching is stuck. Swiping the app
  launcher from the left works fine, but swiping the app switcher from
  the right won't work. It's stuck at the screen that says To view open
  apps Long swipe from the right edge. with an unresponsive wobbly
  switcher to the right.

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

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


[Touch-packages] [Bug 1441154] Re: Built in Apport-Like Bug and Suggestion Reporting Tool Needed

2015-04-09 Thread Michał Sawicz
It will probably be a separate app altogether.

** Changed in: unity8 (Ubuntu)
   Status: New = Opinion

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

Title:
  Built in Apport-Like Bug and Suggestion Reporting Tool Needed

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  I suggest building into the OS itself a tool like Apport that
  automatically reports crashes to developpers.  In addition to this
  tool, it would be excellent if an app or part of the phone could be
  dedicated to user suggestions.  it is highly inconvenient to have to
  run to another machine to report a bug and I am convinced that Ubuntu
  would become amazing fast with a quick 'suggestion reporting app'
  built right into the phone.  Us non programmers would love to give
  'real world' suggestions

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

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


[Touch-packages] [Bug 1441985] [NEW] do not know

2015-04-09 Thread david
Public bug reported:

i have no knowledge

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.8
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: Thu Apr  9 09:48:59 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3977]
InstallationDate: Installed on 2015-01-19 (79 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
MachineType: LENOVO 20236
ProcEnviron:
 LANGUAGE=he
 PATH=(custom, no user)
 LANG=he_IL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=UUID=eb384e24-f1e8-40f7-9069-73c8a49c1e6b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/19/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 78CN25WW(V2.03)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G500
dmi.modalias: 
dmi:bvnLENOVO:bvr78CN25WW(V2.03):bd11/19/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500:
dmi.product.name: 20236
dmi.product.version: Lenovo G500
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
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.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Apr  9 09:47:33 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8428 
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2.7

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


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

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

Title:
  do not know

Status in xorg package in Ubuntu:
  New

Bug description:
  i have no knowledge

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  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: Thu Apr  9 09:48:59 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2015-01-19 (79 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  MachineType: LENOVO 20236
  ProcEnviron:
   LANGUAGE=he
   PATH=(custom, no user)
   LANG=he_IL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=UUID=eb384e24-f1e8-40f7-9069-73c8a49c1e6b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 78CN25WW(V2.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G500
  dmi.modalias: 

[Touch-packages] [Bug 1357713] Re: Use essential init package to ensure that an init system is present

2015-04-09 Thread Martin Pitt
This is the case now in vivid, init is essential and ensures that
systemd-sysv or upstart-sysv is installed.

** Changed in: init-system-helpers (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Use essential init package to ensure that an init system is present

Status in ifupdown package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu 14.10 dev with ifupdown 0.7.48.1ubuntu4 and upstart
  1.13.1-0ubuntu3 and currently it is possible to remove ifupdown and
  upstart as they are not essential packages or any essential/manual
  package does depend on them. Here is the output:

  root@ubuntu:/# apt-get remove ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
ifupdown upstart
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
  After this operation, 895 kB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  
  As I know Ubuntu wants to change from upstart to systemd in the future so 
removing upstart may be fine but I'm wondering why ifupdown can be removed 
(wouldn't this remove the ability to create a network connection?).

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

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


[Touch-packages] [Bug 1442340] Re: telephony-service-indicator crash on an incoming sms

2015-04-09 Thread Rick Spencer
** Attachment added: _usr_bin_messaging-app.32011.crash
   
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1442340/+attachment/4370882/+files/_usr_bin_messaging-app.32011.crash

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

Title:
  telephony-service-indicator crash on an incoming sms

Status in telephony-service package in Ubuntu:
  New

Bug description:
  Sent an sms
  phone was awake and sitting in the messaging app
  I heard something to make me look at the phone but not a notification sound, 
maybe vibration
  unity restarted and when it came back up there was an SMS notification
  Crash file created at that time

  mako running rtm build 219
  Rick has reported this occurring on Vivid arale as well

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

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


[Touch-packages] [Bug 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

2015-04-09 Thread Steve Langasek
The last piece of this is cloud-init, which has been uploaded and is
awaiting freeze review.

** Changed in: snappy-ubuntu
   Status: New = In Progress

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

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

Status in Snappy Ubuntu:
  Fix Committed
Status in cloud-init package in Ubuntu:
  New
Status in ifupdown package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Core provides no console login prompt if network is
  unavailable.

  If I plug ethernet in, it boots to the login prompt fine.

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

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


[Touch-packages] [Bug 1403600] Re: [phone-app] Numeric keyboard doesn't work properly when you press quickly

2015-04-09 Thread Buzea Bogdan
I am on BQ Ubuntu Phone version 20 and this bug is stil present.

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

Title:
  [phone-app] Numeric keyboard doesn't work properly when you press
  quickly

Status in the base for Ubuntu mobile products:
  New
Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Confirmed
Status in dialer-app package in Ubuntu RTM:
  New

Bug description:
  Enviroment

  Product: Krillin bq Aquaris E4.5 Ubuntu Edition
  FW version: Ubuntu 14.10 (r5)
  HW version: MP
  Material:

  Description

  Steps to Reproduce:

  1. Opens default phone call application.
  2. Press quickly the numbers that you want.
  3. It does not sound with each touch properly.

  Actual Result:

  It doesn´t sound a beep with each touch. It sounds one beep for two
  touches about.

  Expected Result:

  It must sound a beep with each touch.

  Reproducibility: 100%

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

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


[Touch-packages] [Bug 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out

2015-04-09 Thread Leo Arias
sorry, scratch that last comment. It should have been:

I could connect to the N network on utopic, so this is a regression.

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

Title:
  Can't connect to my wi-fi N network on vivid: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Touch-packages] [Bug 1441070] Re: lxc-start on default vivid container fails on apparmor violation

2015-04-09 Thread Martin Pitt
Whatever it was, it's working on current vivid now. Sorry for the noise.

** Changed in: lxc (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  lxc-start on default vivid container fails on apparmor violation

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  With latest vivid's LXC, starting a vivid container now fails on
  mounting the cgroups:

  $ sudo lxc-create --name=v -t ubuntu -- -r vivid
  $ sudo lxc-start -n v -F
  Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission denied
  systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR 
+SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP 
+BLKID -ELFUTILS +KMOD -IDN)
  Detected virtualization lxc.
  Detected architecture x86-64.

  Welcome to Ubuntu Vivid Vervet (development branch)!

  Set hostname to v.
  Failed to install release agent, ignoring: No such file or directory
  Failed to create root cgroup hierarchy: No such file or directory
  Failed to allocate manager object: No such file or directory

  This is due to an apparmor violation:

  $ dmesg 
  [17921.831035] kvm [26603]: vcpu0 disabled perfctr wrmsr: 0xc1 data 0x
  [17945.611375] device vethWK88T5 entered promiscuous mode
  [17945.611487] IPv6: ADDRCONF(NETDEV_UP): vethWK88T5: link is not ready
  [17945.651954] eth0: renamed from vethB6ASGB
  [17945.692029] IPv6: ADDRCONF(NETDEV_CHANGE): vethWK88T5: link becomes ready
  [17945.692104] lxcbr0: port 1(vethWK88T5) entered forwarding state
  [17945.692116] lxcbr0: port 1(vethWK88T5) entered forwarding state
  [17945.730478] audit: type=1400 audit(1428400530.895:113): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/systemd/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.730505] audit: type=1400 audit(1428400530.895:114): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/systemd/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.730931] audit: type=1400 audit(1428400530.895:115): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/devices/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.730963] audit: type=1400 audit(1428400530.895:116): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/net_cls,net_prio/ 
pid=28447 comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, 
nodev, noexec
  [17945.730993] audit: type=1400 audit(1428400530.895:117): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/perf_event/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.731020] audit: type=1400 audit(1428400530.895:118): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/hugetlb/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.731049] audit: type=1400 audit(1428400530.895:119): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/cpuset/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.731077] audit: type=1400 audit(1428400530.895:120): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/freezer/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.731106] audit: type=1400 audit(1428400530.895:121): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/cpu,cpuacct/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec
  [17945.731133] audit: type=1400 audit(1428400530.895:122): apparmor=DENIED 
operation=mount info=failed type match error=-13 
profile=lxc-container-default name=/sys/fs/cgroup/memory/ pid=28447 
comm=systemd fstype=cgroup srcname=cgroup flags=rw, nosuid, nodev, 
noexec

  The workaround is to change the container config to use
  lxc.aa_profile = unconfined, but I suppose we actually want the
  default profile to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 11:55:09 2015
  EcryptfsInUse: Yes
  KernLog:
   
  SourcePackage: lxc
  

[Touch-packages] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

2015-04-09 Thread Didier Roche
Done, now xdiagnose only triggers if an installed display manager is
configured as default but couldn't start. This should fix your boot
issue.

We won't fail graphical.target anymore if the only available dm was
uninstalled, however, I do recommend you set then your default target to
multi-user.target (case on a server system for instance).

The lightdm part would be interesting to ensure /e/X/d-d-m is empty, but
not required.

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

Title:
  15.04 Vivid Vervet won't boot after uninstalling lightdm

Status in lightdm package in Ubuntu:
  Triaged
Status in xdiagnose package in Ubuntu:
  Triaged

Bug description:
  We've been trying to figure out how to disable the login screen on
  15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall
  lightdm. If we do this on 15.04, however, the system won't boot. :(
  The main error seems to be: Failed to isolate default target,
  freezing. (I have a picture of this, if there is a way to upload
  one.)

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

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


[Touch-packages] [Bug 1442076] [NEW] util-linux FTBFS: cannot find -lmount

2015-04-09 Thread themusicgod1
Public bug reported:

libtool: install: /usr/bin/install -c kill /bin/kill
 /bin/mkdir -p '/usr/lib/python2.7/dist-packages/libmount'
 /bin/bash ./libtool   --mode=install /usr/bin/install -c   pylibmount.la 
'/usr/lib/python2.7/dist-packages/libmount'
libtool: install: warning: relinking `pylibmount.la'
libtool: install: (cd /home/themusicgod1/ddd/util-linux-2.25.2; /bin/bash 
/home/themusicgod1/ddd/util-linux-2.25.2/libtool  --silent --tag CC 
--mode=relink gcc -std=gnu99 -fsigned-char -fno-common -Wall 
-Werror=sequence-point -Wextra -Wmissing-declarations -Wmissing-parameter-type 
-Wmissing-prototypes -Wno-missing-field-initializers -Wredundant-decls 
-Wsign-compare -Wtype-limits -Wuninitialized -Wunused-but-set-parameter 
-Wunused-but-set-variable -Wunused-parameter -Wunused-result -Wunused-variable 
-Wnested-externs -Wpointer-arith -Wstrict-prototypes -Wformat-security 
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7 
-I./libmount/src -fno-strict-aliasing -g -O2 -avoid-version -module -shared 
-export-dynamic -o pylibmount.la -rpath 
/usr/lib/python2.7/dist-packages/libmount 
libmount/python/pylibmount_la-pylibmount.lo libmount/python/pylibmount_la-fs.lo 
libmount/python/pylibmount_la-tab.lo libmount/python/pylibmount_la-context.lo 
libmount.la -lpython2.7 )
/usr/bin/ld: cannot find -lmount
collect2: error: ld returned 1 exit status
libtool: install: error: relink `pylibmount.la' with the above command before 
installing it
Makefile:4436: recipe for target 'install-pylibmountexecLTLIBRARIES' failed
make[3]: *** [install-pylibmountexecLTLIBRARIES] Error 1
make[3]: Leaving directory '/home/themusicgod1/ddd/util-linux-2.25.2'
Makefile:10522: recipe for target 'install-am' failed
make[2]: *** [install-am] Error 2
make[2]: Leaving directory '/home/themusicgod1/ddd/util-linux-2.25.2'
Makefile:10058: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/home/themusicgod1/ddd/util-linux-2.25.2'
Makefile:10516: recipe for target 'install' failed
make: *** [install] Error 2

Ubuntu: 15.04
util-linux: 2.25.2-4ubuntu2
linux: Linux Hedy 3.19.0-12-generic #12-Ubuntu SMP Fri Apr 3 04:03:26 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
python:
  Installed: 2.7.9-1
  Candidate: 2.7.9-1

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: util-linux 2.25.2-4ubuntu2 [modified: bin/dmesg bin/lsblk bin/more 
bin/wdctl]
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Apr  9 06:35:14 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-09 (273 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140708)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

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

Title:
  util-linux FTBFS: cannot find -lmount

Status in util-linux package in Ubuntu:
  New

Bug description:
  libtool: install: /usr/bin/install -c kill /bin/kill
   /bin/mkdir -p '/usr/lib/python2.7/dist-packages/libmount'
   /bin/bash ./libtool   --mode=install /usr/bin/install -c   pylibmount.la 
'/usr/lib/python2.7/dist-packages/libmount'
  libtool: install: warning: relinking `pylibmount.la'
  libtool: install: (cd /home/themusicgod1/ddd/util-linux-2.25.2; /bin/bash 
/home/themusicgod1/ddd/util-linux-2.25.2/libtool  --silent --tag CC 
--mode=relink gcc -std=gnu99 -fsigned-char -fno-common -Wall 
-Werror=sequence-point -Wextra -Wmissing-declarations -Wmissing-parameter-type 
-Wmissing-prototypes -Wno-missing-field-initializers -Wredundant-decls 
-Wsign-compare -Wtype-limits -Wuninitialized -Wunused-but-set-parameter 
-Wunused-but-set-variable -Wunused-parameter -Wunused-result -Wunused-variable 
-Wnested-externs -Wpointer-arith -Wstrict-prototypes -Wformat-security 
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7 
-I./libmount/src -fno-strict-aliasing -g -O2 -avoid-version -module -shared 
-export-dynamic -o pylibmount.la -rpath 
/usr/lib/python2.7/dist-packages/libmount 
libmount/python/pylibmount_la-pylibmount.lo libmount/python/pylibmount_la-fs.lo 
libmount/python/pylibmount_la-tab.lo libmount/python/pylibmount_la-context.lo 
libmount.la -lpython2.7 )
  /usr/bin/ld: cannot find -lmount
  collect2: error: ld returned 1 exit status
  libtool: install: error: relink `pylibmount.la' with the above command before 
installing it
  Makefile:4436: recipe for target 'install-pylibmountexecLTLIBRARIES' failed
  make[3]: *** [install-pylibmountexecLTLIBRARIES] Error 1
  make[3]: Leaving directory '/home/themusicgod1/ddd/util-linux-2.25.2'
  Makefile:10522: recipe for target 'install-am' 

[Touch-packages] [Bug 1434712] Re: Can't swipe from the right in the setup at first launch

2015-04-09 Thread Gizmo Chicken
At least for me, under the circumstances described below, the presence
of an empty file named wizard-has-run in .config/ubuntu-system-
settings/ does NOT prevent the tutorial from starting.

I installed Ubuntu Next fresh from the 08-Apr-2015 daily build from
http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/   Upon
first boot into the freshly installed system, I got the tutorial.  Upon
rebooting using the installation disk, and selecting the try ubuntu
option, I can find that that an empty file named wizard-has-run is
already present in .config/ubuntu-system-settings/ on the system disk.
But even though the empty file named wizard-has-run is already present
on the system disk, upon booting again into the freshly installed
system, I still get the tutorial.

Perhaps the situation would be different if I had added the empty file
named wizard-has-run immediately after installation of, but before
first boot into, the system.  I don't know.  I haven't tried that.  But
again, I can confirm that, at least for me, under the circumstances
described above, the presence of an empty file named wizard-has-run in
.config/ubuntu-system-settings/ does NOT prevent the tutorial from
starting.

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

Title:
  Can't swipe from the right in the setup at first launch

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 15.04 on a desktop pc with a mouse. Version
  8.02+15.04.20150318-0ubuntu1 of the unity8 package.

  The initial setup when first launching is stuck. Swiping the app
  launcher from the left works fine, but swiping the app switcher from
  the right won't work. It's stuck at the screen that says To view open
  apps Long swipe from the right edge. with an unresponsive wobbly
  switcher to the right.

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

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


[Touch-packages] [Bug 1441961] Re: dataChanged signal cannot be used on ARM under certain conditions

2015-04-09 Thread Nathan Osman
The old connection syntax appears to work fine. Also, I finally managed
to get Utopic up and running on the device and surprisingly, the problem
with my example has disappeared. However, it appears to be a compile-
time issue since anything compiled with Qt 5.2.1 in Trusty still fails
to work when run in Utopic. It must be recompiled in Utopic.

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

Title:
  dataChanged signal cannot be used on ARM under certain conditions

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is probably the strangest bug I have ever observed, but it is
  completely reproducible. When running the attached Qt application, I
  receive the following error:

  QObject::connect: signal not found in Test

  This error is 100% reproducible on my Raspberry Pi 2 running Ubuntu
  14.04.2 (Trusty). This device has an ARMv7 CPU (Broadcom BCM2836). I
  cannot reproduce this error on any other hardware (x86 and amd64 have
  been tested). This does not appear to be a compiler bug since both g++
  and Clang produce an executable that prints the above error.

  Here's the thing that really confuses me: the error disappears (and
  everything works correctly) if I comment out the dataChanged(...)
  line in test.cpp. This is completely bizarre because the line is never
  executed by any code.

  I've tried digging through Qt's headers and buried myself neck-deep in
  macros, templates, and MOC-generated files. I can't make any sense out
  of this. Therefore I am reporting it as a bug. To compile the example,
  enter the source directory, run qmake, and then run make to build
  the executable. Remember, the bug only manifests itself on an ARM CPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1441961/+subscriptions

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


[Touch-packages] [Bug 1430357] Re: Gallery cannot create thumbnail for video in preview

2015-04-09 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/gallery-app

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

Title:
  Gallery cannot create thumbnail for video in preview

Status in Camera App:
  New
Status in the base for Ubuntu mobile products:
  In Progress
Status in Gallery App:
  In Progress
Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  I downloaded this from the browser

  http://trailers.divx.com/divx_prod/profiles/Helicopter_DivXHT_ASP.divx

  and then opened it with gallery when offered to on download
  completion. I can see a thumbnail in the Events screen, but when I
  press it,  a spinner starts looping while trying to obtain a thumbnail
  for the full screen and does not ever stop. If you press the play
  button  while you see the spinner, mediaplayer-app plays the video.

  So, the bug is gallery-app not obtaining a thumbnail in the video-
  preview screen, where the thumbnail fills the display. Finally

  /usr/lib/arm-linux-gnueabihf/thumbnailer/vs-thumb
  Videos/Helicopter_DivXHT_ASP.divx helicopter.jpg

  produces a valid jpeg file.

  Reproduced in mako, vivid-proposed image 127

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

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


[Touch-packages] [Bug 1433739] Re: videos recorded with camera-app show up in wrong day

2015-04-09 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/gallery-app

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

Title:
  videos recorded with camera-app show up in wrong day

Status in Gallery App:
  In Progress
Status in gallery-app package in Ubuntu:
  Fix Released

Bug description:
  It appears the timestamp used for videos taken with the camera-app
  uses UTC instead of Local Time. This causes them to show up in the
  next day sometimes.

  Steps to reproduce:
  1) Set timezone to Boston (UTC - 4) or some other timezone behind UTC
  2) Record a video with the camera-app when the local time is  20:00

  Expected results:
  video should show up in the current day's Event in the event view

  Actual results:
  video shows up in the next day in the Event view

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

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


[Touch-packages] [Bug 1243932] Re: aa-logprof: Log contains unknown mode senw

2015-04-09 Thread Paweł Krawczyk
The fix I implemented in my system was to add the following check to
/usr/lib/python2.7/dist-packages/apparmor/logparser.py, in lines 124:

if rmask and rmask not in [ 'send', 'receive', 'send receive' ]:

Originally it was:

if rmask:

The same in line 130 for dmask. This file comes from python-apparmor
package 2.9.2~2886-0ubuntu0.14.04.41 installed from the PPA.

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

Title:
  aa-logprof:  Log contains unknown mode senw

Status in AppArmor Linux application security framework:
  Confirmed
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  * aa-logprof does not work when dbus rule denials are present in the
  logs

  [Automated Test Case]

  * test_lp1243932_send, test_lp1243932_receive, and test_lp1243932_bind
  have been added to QRT's test-apparmor.py test script

  [Manual Test Case]

  * Load a profile that does not grant D-Bus access and create a D-Bus denial. 
Then,
    test aa-logprof.

    $ echo profile lp1243932 { file, } | sudo apparmor_parser -rq
    $ aa-exec -p lp1243932 -- dbus-send --print-reply --system \
    --dest=org.freedesktop.DBus /org/freedesktop/DBus 
org.freedesktop.DBus.ListNames
    Failed to open connection to system message bus: An AppArmor policy 
prevents this
    sender from sending this message to this recipient, 0 matched rules;
    type=method_call, sender=(null) (inactive) 
interface=org.freedesktop.DBus
    member=Hello error name=(unset) requested_reply=0
    destination=org.freedesktop.DBus (bus)
    $ aa-logprof -f /dev/null
    Reading log entries from /dev/null.
    Updating AppArmor profiles in /etc/apparmor.d.

  An unpatched aa-logprof will print similar output followed by:

    Log contains unknown mode senw.

  [Regression Potential]

  * The regression potential is low since aa-logprof currently refuses to work 
when D-Bus
    denials are present. The fix is minimal and has been reviewed by upstream.

  [Original Bug Report]

  since saucy aa-logprof does not work anymore:

  $ aa-logprof
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.

  Log contains unknown mode senw.

  the issues seem to be caused by dbus send denies:

  Oct 23 19:52:56 ubuntu dbus[2594]: apparmor=DENIED
  operation=dbus_method_call  bus=session
  path=/org/freedesktop/DBus interface=org.freedesktop.DBus
  member=Hello mask=send name=org.freedesktop.DBus pid=3552
  profile=/usr/bin/smuxi-frontend-gnome peer_profile=unconfined

  23:16 tyhicks my guess is the denial of a dbus send
  23:16 tyhicks senw is awful close to send
  23:17 tyhicks parse_event() in AppArmor.pm does this:
  23:18 tyhicks $rmask =~ s/d/w/g;
  23:18 tyhicks followed by:
  23:18 tyhicks fatal_error(sprintf(gettext('Log contains unknown mode %s.'), 
$rmask));

  ubuntu 13.10 amd64.

  apparmor-utils:
    Installed: 2.8.0-0ubuntu31
    Candidate: 2.8.0-0ubuntu31
    Version table:
   *** 2.8.0-0ubuntu31 0
  500 http://de.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

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

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


[Touch-packages] [Bug 1291455] Re: Screen and input should be disabled with proximity sensor when on greeter

2015-04-09 Thread kevin gunn
Sounds like we need a design decision here.
a) do we keep the current design, where on alerts  the proximity sensor is 
covered we still light the screen ? or do we keep the screen blanked until the 
sensor is uncovered ? (see bfiller's #1 above)

b) if we keep our current design around proximity sensor, should we
alter the message quick reply (see bfiller's #4 above)

** Changed in: powerd (Ubuntu)
   Status: Confirmed = Incomplete

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  Screen and input should be disabled with proximity sensor when on
  greeter

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Ubuntu UX bugs:
  New
Status in powerd package in Ubuntu:
  Incomplete
Status in telepathy-ofono package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  * suspend your device
  * cover the proximity sensor (top left on mako)
  * call the phone

  Expecte result:
  * screen does not light up until you uncover the proximity sensor

  Current result:
  * screen lights up and you can answer the call

  This results in butt/pocket calls...

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

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

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


[Touch-packages] [Bug 1434712] Re: Can't swipe from the right in the setup at first launch

2015-04-09 Thread Michał Sawicz
The wizard-has-run file only impacts the first-setup wizard, not the
edge tutorial.

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

Title:
  Can't swipe from the right in the setup at first launch

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 15.04 on a desktop pc with a mouse. Version
  8.02+15.04.20150318-0ubuntu1 of the unity8 package.

  The initial setup when first launching is stuck. Swiping the app
  launcher from the left works fine, but swiping the app switcher from
  the right won't work. It's stuck at the screen that says To view open
  apps Long swipe from the right edge. with an unresponsive wobbly
  switcher to the right.

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

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


[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work

2015-04-09 Thread Alexander Skiba
I've patched the packages for Precise, Trusty and Debian Wheezy.
Although it's been done in a very ugly and quite sloppy way I can
provide the patches.

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

Title:
  Unattended-Upgrade::Remove-Unused-Dependencies does not work

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies true;'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies true;

  but nothing happens (note the line Packages that are auto removed: ''
  :

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: 'Version: package:'accountsservice' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libaccountsservice0' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libdrm-intel1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-nouveau1a' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-radeon1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm2' 
version:'2.4.43-0ubuntu0.0.3''
  Checking: bc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub2-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: iproute ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: landscape-common ([Origin component:'main' 
archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' 
site:'gb.archive.ubuntu.com' isTrusted:True])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found that can be upgraded unattended

  
  
  

[Touch-packages] [Bug 1442166] [NEW] Calendar alarms rings forever if Low Battery dialog visible

2015-04-09 Thread Bill Filler
Public bug reported:

I'm on rtm build 258 on krillin

Steps to reproduce:
- let battery run down on phone (was sitting unplugged for 1 or 2 days)
- in the morning, a calendar alarm starting ringing/vibrating and would not stop
- when I looked at the phone, the screen was on and I see the Low Battery dialog
- after dismissing the dialog, then I see the notification for the alarm, and 
only after 5-10 more seconds does the ringing stop

Seems like while the Low Battery dialog is displayed it keeps the alarm
ringing forever

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

** Affects: indicator-datetime (Ubuntu)
 Importance: High
 Assignee: Charles Kerr (charlesk)
 Status: New

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) = Charles Kerr (charlesk)

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None = ww15-2015

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

Title:
  Calendar alarms rings forever if Low Battery dialog visible

Status in the base for Ubuntu mobile products:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  I'm on rtm build 258 on krillin

  Steps to reproduce:
  - let battery run down on phone (was sitting unplugged for 1 or 2 days)
  - in the morning, a calendar alarm starting ringing/vibrating and would not 
stop
  - when I looked at the phone, the screen was on and I see the Low Battery 
dialog
  - after dismissing the dialog, then I see the notification for the alarm, and 
only after 5-10 more seconds does the ringing stop

  Seems like while the Low Battery dialog is displayed it keeps the
  alarm ringing forever

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

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


[Touch-packages] [Bug 1442164] [NEW] Segfault in tests when calling subsearch() with MockScope

2015-04-09 Thread Pawel Stolowski
Public bug reported:

Getting crash with the below stacktrace. After a quick look I think this
is because the method that checks for loops does this:

auto scope_impl = dynamic_pointer_castScopeImpl(scope);
auto logger = scope_impl-runtime()-logger();

without checking if scope_impl is not null (which is the case for
MockScope according to the comment in the code above). And I remember
myself commenting about this is the MP for this change ;)

Program received signal SIGSEGV, Segmentation fault.
unity::scopes::internal::ScopeImpl::runtime (this=0x0) at 
/src/unity-scopes-api/unity-scopes-api/src/scopes/internal/ScopeImpl.cpp:60
60  return runtime_;
(gdb) bt
#0  unity::scopes::internal::ScopeImpl::runtime (this=0x0) at 
/src/unity-scopes-api/unity-scopes-api/src/scopes/internal/ScopeImpl.cpp:60
#1  0x77acbe17 in 
unity::scopes::internal::SearchQueryBaseImpl::check_for_query_loop 
(this=0x7fffbd20, scope=warning: RTTI symbol not found for class 
'std::_Sp_counted_ptrunity::scopes::testing::MockScope*, 
(__gnu_cxx::_Lock_policy)2'
warning: RTTI symbol not found for class 
'std::_Sp_counted_ptrunity::scopes::testing::MockScope*, 
(__gnu_cxx::_Lock_policy)2'
std::shared_ptr (count 5, weak 0) 0x8aeb20, reply=
std::shared_ptr (count 9133936, weak -1) 0x862d10 vtable for 
BufferedResultForwarder+16) at 
/src/unity-scopes-api/unity-scopes-api/src/scopes/internal/SearchQueryBaseImpl.cpp:186
#2  0x77ace00f in 
unity::scopes::internal::SearchQueryBaseImpl::subsearch (this=0x8affd0, 
scope=warning: RTTI symbol not found for class 
'std::_Sp_counted_ptrunity::scopes::testing::MockScope*, 
(__gnu_cxx::_Lock_policy)2'
warning: RTTI symbol not found for class 
'std::_Sp_counted_ptrunity::scopes::testing::MockScope*, 
(__gnu_cxx::_Lock_policy)2'
Python Exception class 'ValueError' Cannot find type const 
std::setstd::basic_stringchar, std::char_traitschar, std::allocatorchar 
, std::lessstd::basic_stringchar, std::char_traitschar, 
std::allocatorchar  , std::allocatorstd::basic_stringchar, 
std::char_traitschar, std::allocatorchar   ::_Rep_type: 
std::shared_ptr (count 5, weak 0) 0x8aeb20, keywords=std::set with 0 elements, 
query_string=test, 
department_id=aggregated:musicaggregator, filter_state=..., metadata=..., 
reply=warning: RTTI symbol not found for class 
'std::_Sp_counted_ptr_inplaceBufferedResultForwarder, 
std::allocatorBufferedResultForwarder, (__gnu_cxx::_Lock_policy)2'
warning: RTTI symbol not found for class 
'std::_Sp_counted_ptr_inplaceBufferedResultForwarder, 
std::allocatorBufferedResultForwarder, (__gnu_cxx::_Lock_policy)2'
std::shared_ptr (count 3, weak 0) 0x8b1f70)
at 
/src/unity-scopes-api/unity-scopes-api/src/scopes/internal/SearchQueryBaseImpl.cpp:79
#3  0x77b1c872 in unity::scopes::SearchQueryBase::subsearch 
(this=0x7fffd670, scope=..., query_string=test, 
department_id=aggregated:musicaggregator, filter_state=..., hints=..., 
reply=warning: RTTI symbol not found for class 
'std::_Sp_counted_ptr_inplaceBufferedResultForwarder, 
std::allocatorBufferedResultForwarder, (__gnu_cxx::_Lock_policy)2'
warning: RTTI symbol not found for class 
'std::_Sp_counted_ptr_inplaceBufferedResultForwarder, 
std::allocatorBufferedResultForwarder, (__gnu_cxx::_Lock_policy)2'

std::shared_ptr (count 3, weak 0) 0x8b1f70) at 
/src/unity-scopes-api/unity-scopes-api/src/scopes/SearchQueryBase.cpp:117
#4  0x005b4e9b in 
MusicAggregatorQuery::run(std::shared_ptrunity::scopes::SearchReply const) ()
#5  0x00564e4e in 
TestMusicAgregator_TestSpecificSearch_Test::TestBody() ()
#6  0x005e8500 in void 
testing::internal::HandleSehExceptionsInMethodIfSupportedtesting::Test, 
void(testing::Test*, void (testing::Test::*)(), char const*) ()
#7  0x005e3a3f in void 
testing::internal::HandleExceptionsInMethodIfSupportedtesting::Test, 
void(testing::Test*, void (testing::Test::*)(), char const*) ()
#8  0x005ca52b in testing::Test::Run() ()
#9  0x005cad35 in testing::TestInfo::Run() ()
#10 0x005cb382 in testing::TestCase::Run() ()
#11 0x005d1dc4 in testing::internal::UnitTestImpl::RunAllTests() ()
#12 0x005e9411 in bool 
testing::internal::HandleSehExceptionsInMethodIfSupportedtesting::internal::UnitTestImpl,
 bool(testing::internal::UnitTestImpl*, bool 
(testing::internal::UnitTestImpl::*)(), char const*) ()
#13 0x005e48c9 in bool 
testing::internal::HandleExceptionsInMethodIfSupportedtesting::internal::UnitTestImpl,
 bool(testing::internal::UnitTestImpl*, bool 
(testing::internal::UnitTestImpl::*)(), char const*) ()
#14 0x005d0a54 in testing::UnitTest::Run() ()
#15 0x00567986 in RUN_ALL_TESTS() ()
#16 0x005662ff in main ()

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- Segfault in tests when calling subsearch() when identity is empty in MockScope
+ Segfault in tests when calling subsearch() with 

[Touch-packages] [Bug 1441986] [NEW] NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher garbled after resuming from suspend

2015-04-09 Thread Yung Shen
Public bug reported:

Launcher does not display correctly after suspend, there is other
different corruption in different application scenario, most of them can
be recover by switch between VT.

Steps to reproduce:

1. suspend the system in the middle of using
2. resume from suspend

Expected result:

Desktop screen display correctly.

Actual result:

Some parts of the screen corrupted.

Workaround:
Switching from X to VT may temporary fix these corruptions.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Apr  9 02:09:23 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:079c]
InstallationDate: Installed on 2015-04-02 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP Z820 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=UUID=d8280bec-e0b3-4b37-8f6b-aa899731f110 ro rootdelay=60 quiet splash 
initcall_debug
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J63 v03.69
dmi.board.asset.tag: 2UA4242K12
dmi.board.name: 158B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.01
dmi.chassis.asset.tag: 2UA4242K12
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z820 Workstation
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
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.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Apr  8 09:39:05 2015
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-bug compiz-0.9 corruption trusty ubuntu

** Attachment added: Launcher Garbled.png
   
https://bugs.launchpad.net/bugs/1441986/+attachment/4370135/+files/Launcher%20garbled%202%20-%20Screenshot%20from%202015-04-07%2004%3A29%3A57.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/1441986

Title:
  NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher
  garbled after resuming from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Launcher does not display correctly after suspend, there is other
  different corruption in different application scenario, most of them
  can be recover by switch between VT.

  Steps to reproduce:

  1. suspend the system in the middle of using
  2. resume from suspend

  Expected result:

  Desktop screen display correctly.

  Actual result:

  Some parts of the screen corrupted.

  Workaround:
  Switching from X to VT may temporary fix these corruptions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] 

[Touch-packages] [Bug 1430828] Re: scopes dont load pictures

2015-04-09 Thread Alfonso Sanchez-Beato
My comment #23 is probably a red herring, as it looks like in the end
all DNS servers are registered in dnsmasq, and it sends queries to all
available servers. So I am hiding it.

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

Title:
  scopes dont load pictures

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  The phone (krillin) is clearly connected and you can retrive text data
  but pictures do not updated see, attached pictures.

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

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


[Touch-packages] [Bug 1440501] Re: Can not load mysql-akonadi apparmor profile

2015-04-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: akonadi (Ubuntu)
   Status: New = Confirmed

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

Title:
  Can not load mysql-akonadi apparmor profile

Status in akonadi package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Apparmor fails to start witch exit code 123, because it can not load
  the mysql-akonadi profile:

  % sudo systemctl status apparmor -l  
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor)
 Active: failed (Result: exit-code) since So 2015-04-05 12:29:33 CEST; 55s 
ago
   Docs: man:systemd-sysv-generator(8)
Process: 13906 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=123)

  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.mysqld-akonadi in 
/etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 
'local/usr.sbin.mysqld-akonadi'
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.mysqld-akonadi in 
/etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 
'local/usr.sbin.mysqld-akonadi'
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: ...fail!
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service: control process 
exited, code=exited status=123
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: Unit apparmor.service entered 
failed state.
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service failed.

  However Apparmor loaded successfully:

  % sudo aa-status
  apparmor module is loaded.
  17 profiles are loaded.
  17 profiles are in enforce mode.
 /sbin/dhclient
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/lib/cups/backend/cups-pdf
 /usr/lib/libvirt/virt-aa-helper
 /usr/lib/telepathy/mission-control-5
 /usr/lib/telepathy/telepathy-*
 /usr/lib/telepathy/telepathy-*//pxgsettings
 /usr/lib/telepathy/telepathy-*//sanitized_helper
 /usr/lib/telepathy/telepathy-ofono
 /usr/sbin/cups-browsed
 /usr/sbin/cupsd
 /usr/sbin/cupsd//third_party
 /usr/sbin/libvirtd
 /usr/sbin/tcpdump
 docker-default
  0 profiles are in complain mode.
  5 processes have profiles defined.
  5 processes are in enforce mode.
 /sbin/dhclient (11821) 
 /usr/lib/telepathy/mission-control-5 (2008) 
 /usr/sbin/cups-browsed (840) 
 /usr/sbin/cupsd (12783) 
 /usr/sbin/libvirtd (971) 
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  It is really necessary to set Apparmor as failed if one profile could
  not be loaded?

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

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


[Touch-packages] [Bug 1440501] Re: Can not load mysql-akonadi apparmor profile

2015-04-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apparmor (Ubuntu)
   Status: New = Confirmed

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

Title:
  Can not load mysql-akonadi apparmor profile

Status in akonadi package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Apparmor fails to start witch exit code 123, because it can not load
  the mysql-akonadi profile:

  % sudo systemctl status apparmor -l  
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor)
 Active: failed (Result: exit-code) since So 2015-04-05 12:29:33 CEST; 55s 
ago
   Docs: man:systemd-sysv-generator(8)
Process: 13906 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=123)

  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.mysqld-akonadi in 
/etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 
'local/usr.sbin.mysqld-akonadi'
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.mysqld-akonadi in 
/etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 
'local/usr.sbin.mysqld-akonadi'
  Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: ...fail!
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service: control process 
exited, code=exited status=123
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor 
initialization.
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: Unit apparmor.service entered 
failed state.
  Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service failed.

  However Apparmor loaded successfully:

  % sudo aa-status
  apparmor module is loaded.
  17 profiles are loaded.
  17 profiles are in enforce mode.
 /sbin/dhclient
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/lib/cups/backend/cups-pdf
 /usr/lib/libvirt/virt-aa-helper
 /usr/lib/telepathy/mission-control-5
 /usr/lib/telepathy/telepathy-*
 /usr/lib/telepathy/telepathy-*//pxgsettings
 /usr/lib/telepathy/telepathy-*//sanitized_helper
 /usr/lib/telepathy/telepathy-ofono
 /usr/sbin/cups-browsed
 /usr/sbin/cupsd
 /usr/sbin/cupsd//third_party
 /usr/sbin/libvirtd
 /usr/sbin/tcpdump
 docker-default
  0 profiles are in complain mode.
  5 processes have profiles defined.
  5 processes are in enforce mode.
 /sbin/dhclient (11821) 
 /usr/lib/telepathy/mission-control-5 (2008) 
 /usr/sbin/cups-browsed (840) 
 /usr/sbin/cupsd (12783) 
 /usr/sbin/libvirtd (971) 
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  It is really necessary to set Apparmor as failed if one profile could
  not be loaded?

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

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


[Touch-packages] [Bug 1441322] Re: The Description-en field isn't correct

2015-04-09 Thread Sworddragon
But your text does mention a number: three available init systems in
Ubuntu (systemd or upstart)

** Changed in: init-system-helpers (Ubuntu)
   Status: Incomplete = New

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

Title:
  The Description-en field isn't correct

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

Bug description:
  I'm using Ubuntu 15.04 dev with init 1.22ubuntu8 and on executing
  apt-cache show init I'm seeing that the Description-en field says
  that there are 3 available init systems while it lists only 2.

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

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


[Touch-packages] [Bug 1442228] Re: lxc fails to start inside vivid container

2015-04-09 Thread Serge Hallyn
** Attachment added: Proposed running-in-container script to put into 
init-system-helpers
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1442228/+attachment/4370823/+files/running-in-container

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

Title:
  lxc fails to start inside vivid container

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  When installing lxc, the lxc.postinst tries to install apparmor profiles.
  Inside a vivid container on an upstart-based host, the profile loading
  script will test /bin//running-in-container and see that it is in a container
  and exit 0.  On a systemd host, /bin/running-in-container doesn't work, so
  the profile loading script exits with error, failing the postinst.

  /bin/running-in-container needs to be generalized to work with
  systemd.

  Unlike upstart, systemd leaves its environment showing in /proc/1/environ,
  so we can in fact simply check for grep -q container=lxc /proc/1/environ,
  which we couldn't do with upstart.  However, to keep things more similar
  between upstart and systemd, and to handle all cases, it would probably be
  best to have a systemd unit starting at boot which does the same thing as
  the /etc/init/container-detect.conf does.

  Then move /bin/running-in-container from upstart into init-system-
  helpers.

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

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


[Touch-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X

2015-04-09 Thread Igor Lopez
Unfortunately has this problem just reappeared.
I need help on how to troubleshot.

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

** Information type changed from Private to Public

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

Title:
  Synaptic Touchpad xevents are hijacked under X

Status in xorg package in Ubuntu:
  New

Bug description:
  Synaptic Touchpad xevents are hijacked under X11.

  I have a problem with the synaptic touch-pad on my Acer Aspire that started 
around a week ago.
  The problem can be described as that there is a massive amount of xevents 
being generated and appearing to originate from the touch-pad even though the 
touch-pad is not used.
  I have tested the HW which seems to work fine.
  The test performed is to start a terminal session (Ctrl + Alt + 2) before the 
fault occurs and check the xevents by running
   ~$ sudo evtest /dev/input/eventX
  where the X to use is found in /proc/bus/input/devices and found by running
   ~$ cat /proc/bus/input/devices |grep mouse
  No matter how much the touch-pad is used will the console show the 
corresponding events which indicates that HW and driver works OK as long it is 
not under X

  When the problem has occurred (in Desktop mode) is it easy (but inconvenient) 
to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then 
turn on again.
  And more, one can get unlucky in the sense that the generated events could 
click somewhere one do not want to click.
  During the problem is it impossible to use the mouse since it flies around 
(mostly going in a bottom to top of screen direction) but one can check the 
generated events using evtest again.

  How can I help troubleshooting the problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Mar 15 19:51:13 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0933]
  InstallationDate: Installed on 2015-02-21 (22 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: Acer Aspire E3-112
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E3-112
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Mar 15 18:59:07 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1576 
   vendor BOE
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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


[Touch-packages] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

2015-04-09 Thread Martin Pitt
This is due to xdiagnose's

Requires=display-manager.service
OnFailure=failsafe-graphical.target


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

** Changed in: xdiagnose (Ubuntu)
   Status: New = Triaged

** Tags added: systemd-boot

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

Title:
  15.04 Vivid Vervet won't boot after uninstalling lightdm

Status in lightdm package in Ubuntu:
  Triaged
Status in xdiagnose package in Ubuntu:
  Triaged

Bug description:
  We've been trying to figure out how to disable the login screen on
  15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall
  lightdm. If we do this on 15.04, however, the system won't boot. :(
  The main error seems to be: Failed to isolate default target,
  freezing. (I have a picture of this, if there is a way to upload
  one.)

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

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


[Touch-packages] [Bug 1385709] Re: network-manager service doesn't start at boot time

2015-04-09 Thread Romain Lebreton
I may have another look at the problem.
I was experiencing the same waiting for network configuration issue after 
installing sendmail. I looked at my /var/log/upstart/network-interface-lo.log 
and network-manager.log log files and I found this.
   /etc/network/if-up.d/sendmail: 44: .: Can't open 
/usr/share/sendmail/dynamic
   run-parts: /etc/network/if-up.d/sendmail exited with return code 2
Indeed, the line 44 of the script /etc/network/if-up.d/sendmail calls another 
script  /usr/share/sendmail/dynamic that does not exists. 
My (bad) patch was to comment line 44 of /etc/network/if-up.d/sendmail which 
solved the  waiting for network configuration issue at startup.
Hope it helps !

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

Title:
  network-manager service doesn't start at boot time

Status in network-manager package in Ubuntu:
  Confirmed
Status in sendmail package in Ubuntu:
  Confirmed

Bug description:
  I just completed the upgrade from Kubuntu 14.04 to 14.10. Haven't had
  any network trouble before the upgrade. After the upgrade, the
  network-manager service does not start when the computer boots up -
  the Kubuntu splash screen says 'waiting for network configuration',
  then 'waiting another 60 seconds for network configuration' (or
  something like that), then finally boots up without a network
  connection. Also the Network Management tray icon tooltip says that
  the network-manager service is not running. However if I then manually
  open the terminal and run 'sudo service network-manager start', then
  it starts ok and the network connects within a few seconds and
  everything works ok until the next reboot. I'm on a desktop PC with a
  wired LAN connection and no wifi adapter. network-manager version is
  0.9.8.8-0ubuntu28.

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

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


[Touch-packages] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

2015-04-09 Thread Martin Pitt
Didier kindly offered to work on the xdiagnose part. It's not yet clear
whether we also need to change lightdm.

** Changed in: xdiagnose (Ubuntu)
 Assignee: (unassigned) = Didier Roche (didrocks)

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

Title:
  15.04 Vivid Vervet won't boot after uninstalling lightdm

Status in lightdm package in Ubuntu:
  Triaged
Status in xdiagnose package in Ubuntu:
  Triaged

Bug description:
  We've been trying to figure out how to disable the login screen on
  15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall
  lightdm. If we do this on 15.04, however, the system won't boot. :(
  The main error seems to be: Failed to isolate default target,
  freezing. (I have a picture of this, if there is a way to upload
  one.)

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

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


[Touch-packages] [Bug 1441210] Re: Roboto fonts make printer crash (fonts-android)

2015-04-09 Thread Gunnar Hjalmarsson
I have built a trusty version of fonts-android in my PPA with the newer
versions of the Roboto fonts:

https://launchpad.net/~gunnarhj/+archive/ubuntu/roboto-test

So, Jean-Sebastien, before I propose it for the 14.04 archive, it would
be great if you could install fonts-roboto 1:4.3-3ubuntu1.2~ppa and let
us know if it fixes the issue.

** Changed in: fonts-android (Ubuntu)
   Status: Triaged = In Progress

** Changed in: fonts-android (Ubuntu)
 Assignee: (unassigned) = Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Roboto fonts make printer crash (fonts-android)

Status in fonts-android package in Ubuntu:
  In Progress
Status in fonts-android package in Debian:
  New

Bug description:
  As per https://code.google.com/p/android/issues/detail?id=38383, there
  has been issues with the Roboto font family regarding printing. These
  issues seem to have been resolved in the new version of the fonts made
  available by Google in 2014 here
  http://developer.android.com/design/style/typography.html.

  My setup:

  1) Release: Ubuntu 14.04 LTS
  2) Package: fonts-roboto 1:4.3-3ubuntu1.1
  3) Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), 
I should be able to print the document.
  4) Current Results: Roboto fonts make the printer crash instead of printing. 
The printer I am using is a HP-Laser Jet P2055. 

  Steps to reproduce:

  Install fonts-roboto package from Ubuntu Software Center. Produce a
  document in Libre Office with Roboto font and send to printer. Printer
  is crashing, need hard reboot.

  Workaround:

  (1) Remove fonts-roboto package from Ubuntu Software Center. 
  (2) Download new version of the fonts made available by Google and save them 
in the .fonts folder in home directory.
  (3) Produce a new document with Roboto font and send to printer.
  (4) Document is printing.

  Basically, I think this package just need to be updated to use the
  latest fonts issued by Google.

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

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


[Touch-packages] [Bug 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.

2015-04-09 Thread Boris Hollas
So what can I do to fix this problem on 14.04?

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

Title:
  [pulseaudio] module.c: Failed to load module module-echo-cancel
  (argument: aec_method=webrtc): initia lization failed.

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Hello! 
  13.10.
  Trying to load module-echo-cancel with webrtc and get:

  [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: 
aec_method=webrtc): initia
  lization failed.

  I guess this is wrong...

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

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


[Touch-packages] [Bug 1442085] Re: Overlapping labels

2015-04-09 Thread Niklas Wenzel
** Attachment added: screenshot20154409_124445254.png
   
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1442085/+attachment/4370406/+files/screenshot20154409_124445254.png

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

Title:
  Overlapping labels

Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  Check out the screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1442085/+subscriptions

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


[Touch-packages] [Bug 1441961] Re: dataChanged signal cannot be used on ARM under certain conditions

2015-04-09 Thread Dmitry Shachnev
Can you try to use the old connection syntax? The new syntax is known to
be unreliable on some architectures.

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

Title:
  dataChanged signal cannot be used on ARM under certain conditions

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is probably the strangest bug I have ever observed, but it is
  completely reproducible. When running the attached Qt application, I
  receive the following error:

  QObject::connect: signal not found in Test

  This error is 100% reproducible on my Raspberry Pi 2 running Ubuntu
  14.04.2 (Trusty). This device has an ARMv7 CPU (Broadcom BCM2836). I
  cannot reproduce this error on any other hardware (x86 and amd64 have
  been tested). This does not appear to be a compiler bug since both g++
  and Clang produce an executable that prints the above error.

  Here's the thing that really confuses me: the error disappears (and
  everything works correctly) if I comment out the dataChanged(...)
  line in test.cpp. This is completely bizarre because the line is never
  executed by any code.

  I've tried digging through Qt's headers and buried myself neck-deep in
  macros, templates, and MOC-generated files. I can't make any sense out
  of this. Therefore I am reporting it as a bug. To compile the example,
  enter the source directory, run qmake, and then run make to build
  the executable. Remember, the bug only manifests itself on an ARM CPU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1441961/+subscriptions

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


[Touch-packages] [Bug 1441975] [NEW] have not shadows

2015-04-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

nautilus and desktop have not shadows on context menus

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: nautilus 1:3.14.2-0ubuntu8
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr  9 08:54:22 2015
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
InstallationDate: Installed on 2015-03-05 (34 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2015-03-05T22:46:49.143864

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug third-party-packages vivid
-- 
have not shadows
https://bugs.launchpad.net/bugs/1441975
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes in Ubuntu.

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


[Touch-packages] [Bug 1442169] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

2015-04-09 Thread Till Kamppeter
** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in cups package in Ubuntu:
  New

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Error: [Errno 2] File o directory non esistente: 
'/proc/version_signature'
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CupsErrorLog: W [09/Apr/2015:15:58:06 +0200] CreateProfile failed: 
org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
  Date: Sat Apr  4 11:48:06 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2014-10-23 (167 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat:
   device for Canon-LBP-5975: socket://192.168.1.130
   device for EPSON-Epson-Stylus-Photo-P50: 
usb://EPSON/Stylus%20Photo%20P50?serial=4C43514B3031353929
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   EPSON-Epson-Stylus-Photo-P50: Epson Stylus Photo P50 - CUPS+Gutenprint 
v5.2.10
   Canon-LBP-5975: Canon LBP-3460 Foomatic/pxlmono (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fca89173984 avahi_entry_group_free+4: cmpq   
$0x0,(%rdi)
   PC (0x7fca89173984) ok
   source $0x0 ok
   destination (%rdi) (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to vivid on 2015-03-31 (8 days ago)
  UserGroups:
   
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0307
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0307:bd05/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Touch-packages] [Bug 1123578] Re: [USB-Audio - Jabra PRO 930, recording] Recording problem

2015-04-09 Thread Tanguy
Hello ,
I've a jabra pro 930 on my computer Ubuntu 14.10 

Same problem as description

i use a sflphone for information

hope it's better on 15.04   :-)


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

Title:
  [USB-Audio - Jabra PRO 930, recording] Recording problem

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am having a problem with my Jabra PRO 930 USB headset working with
  Ubuntu. I thought there might be issues when under Sound Settings, the
  headset is listed under the Output Tab but is not listed under the
  Input tab. See attached pictures.

  However, the headset does seem to work briefly, as long as audio is
  being played out. I have noticed that as long as the other side is
  talking or audio is coming in for at least 5 secs, the headset works
  perfectly. But if the other side mutes or stops talking (like
  listening to me talk), the headset cuts off completely until audio is
  detected again.

  This is not a problem with the headset. My wife bought the same
  headset and is using it with her Windows 7 system. I swapped headsets
  and the problem persisted on my Ubuntu 12.10 system.

  I use Google Talk, Google+ Hangouts and Skype and have the issue with
  all applications.

  Please let me know if there is anything else I can do to help or what
  information I can provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2464 F pulseaudio
   /dev/snd/pcmC0D0p:   bob2464 F...m pulseaudio
   /dev/snd/controlC1:  bob2464 F pulseaudio
  Date: Tue Feb 12 18:21:46 2013
  InstallationDate: Installed on 2011-11-25 (445 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:J930 successful
  Symptom_Card: Jabra PRO 930 - Jabra PRO 930
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:J930 failed
  Symptom_Type: Only some of inputs are working
  Title: [USB-Audio - Jabra PRO 930, recording] Recording problem
  UpgradeStatus: Upgraded to quantal on 2012-10-27 (108 days ago)
  dmi.bios.date: 11/29/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.2D
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.B6
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.2D:bd11/29/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.2D:rvnCompal:rn30F4:rvr99.B6:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.2D
  dmi.sys.vendor: Hewlett-Packard

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

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


[Touch-packages] [Bug 1131385] Re: Always on top prevents application spread from working

2015-04-09 Thread Christopher Townsend
** Changed in: unity
 Assignee: Taihsiang Ho (taihsiangho) = Christopher Townsend (townsend)

** Changed in: unity (Ubuntu)
 Assignee: Taihsiang Ho (taihsiangho) = Christopher Townsend (townsend)

** Changed in: unity (Ubuntu)
   Importance: Undecided = Low

** Tags removed: needs-design

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

Title:
  Always on top prevents application spread from working

Status in Ayatana Design:
  Invalid
Status in Compiz:
  Invalid
Status in Unity:
  In Progress
Status in unity package in Ubuntu:
  In Progress

Bug description:
  Consider you have many windows of the same type open. One method of switching 
between them is clicking the launcher icon which reveals the application 
spread. Now you can choose between the windows. This is how it should be. 
  However, the design idea was, if the windows are marked Always on Top there 
is no need for an application spread, as they are always on top. This is a bug 
and needs to be changed, because it does not consider minimized windows and 
therefore prevents switching to those windows. 
  If you have windows of the same application open, some of them minimized and 
ALL non-minimized windows are marked as Always on top, the application spread 
does not work anymore, clicking the launcher does nothing.  Whether the 
minimized windows are marked always on top or not does not matter. 
  So the simplest way to reproduce  this bug would be:
  1.) Open two windows of the same application.
  2.) Minimize one and mark the other (non-minimized) as Always on top. 
  3.) Try to switch to the minimized window using application spread

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

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


[Touch-packages] [Bug 1441893] Re: Can't connect to my wi-fi N network: authentication timed out

2015-04-09 Thread Leo Arias
I switched the network back to G, and I can connect.

** Summary changed:

- Can't connect to my wi-fi: authentication timed out
+ Can't connect to my wi-fi N network: authentication timed out

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

Title:
  Can't connect to my wi-fi N network: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Touch-packages] [Bug 1377194] Re: [browser] Various issues with security UI's

2015-04-09 Thread Rae Shambrook
** Changed in: ubuntu-ux
   Status: Fix Committed = Fix Released

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

Title:
  [browser] Various issues with security UI's

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Ubuntu UX bugs:
  Fix Released
Status in Web Browser App:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu RTM:
  Fix Released

Bug description:
  I've not done a proper review on this yet, but there are a few issues
  I've noticed just from using the browser:

  - The certificate error UI is displayed for all errors, but it should
  only be displayed for main frame document errors
  (CertificateError.isMainFrame  !CertificateError.isSubresource). You
  can't override other errors anyway, and for subframes and subresources
  it is fine to just block the content (this is how Chrome and Firefox
  behave).

  - When accepting an error, the certificate fingerprint seems to be
  whitelisted by the browser. This is not safe - what happens if the
  user navigates to a genuinely malicious site that happens to use the
  same certificate? If you want to whitelist them, you must also record
  the domain that the error originated from and the error code, and only
  automatically allow the error if the domain + error code +
  fingerprints match

  - When accepting an error, there is no visual cue in the header bar
  that you're on a site with security errors.

  - If you press the stop icon in the addressbar whilst the certificate
  error UI is displayed, the pending navigation is cancelled (returning
  to the previous committed navigation), but the certificate error UI is
  not removed. There is a CertificateError.cancelled signal for this
  purpose - I'm not sure if you're using it or not

  - There doesn't seem to be any indicator when you go to a site that
  has an EV certificate

  --- UX Comment ---
  Additional wireframe for top bar displaying warning when certificate identity 
is not verified
  
https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3503834cf_01

  For EV certificate, just display EV information in the pop-over

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

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


[Touch-packages] [Bug 1442228] [NEW] lxc fails to start inside vivid container

2015-04-09 Thread Serge Hallyn
Public bug reported:

When installing lxc, the lxc.postinst tries to install apparmor profiles.
Inside a vivid container on an upstart-based host, the profile loading
script will test /bin//running-in-container and see that it is in a container
and exit 0.  On a systemd host, /bin/running-in-container doesn't work, so
the profile loading script exits with error, failing the postinst.

/bin/running-in-container needs to be generalized to work with systemd.

Unlike upstart, systemd leaves its environment showing in /proc/1/environ,
so we can in fact simply check for grep -q container=lxc /proc/1/environ,
which we couldn't do with upstart.  However, to keep things more similar
between upstart and systemd, and to handle all cases, it would probably be
best to have a systemd unit starting at boot which does the same thing as
the /etc/init/container-detect.conf does.

Then move /bin/running-in-container from upstart into init-system-
helpers.

** Affects: lxc (Ubuntu)
 Importance: Critical
 Status: Triaged

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

Title:
  lxc fails to start inside vivid container

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  When installing lxc, the lxc.postinst tries to install apparmor profiles.
  Inside a vivid container on an upstart-based host, the profile loading
  script will test /bin//running-in-container and see that it is in a container
  and exit 0.  On a systemd host, /bin/running-in-container doesn't work, so
  the profile loading script exits with error, failing the postinst.

  /bin/running-in-container needs to be generalized to work with
  systemd.

  Unlike upstart, systemd leaves its environment showing in /proc/1/environ,
  so we can in fact simply check for grep -q container=lxc /proc/1/environ,
  which we couldn't do with upstart.  However, to keep things more similar
  between upstart and systemd, and to handle all cases, it would probably be
  best to have a systemd unit starting at boot which does the same thing as
  the /etc/init/container-detect.conf does.

  Then move /bin/running-in-container from upstart into init-system-
  helpers.

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

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


[Touch-packages] [Bug 1442283] [NEW] double mouse cursor

2015-04-09 Thread Pedro
*** This bug is a security vulnerability ***

Private security bug reported:

These posts describe my problem:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361
But in my case, only when using multiple monitors it happens. I use one monitor 
rotated and one not. Like: https://bugs.freedesktop.org/show_bug.cgi?id=81886

The only way I've found to remove the extra mouse cursor is to drag an image in 
Chrome (?). It doesn't work with an image in Firefox nor in another program.
Anyway, the extra mouse coursor appears again at any time, so I have no 
solution for this.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Apr  9 13:53:03 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0552]
 NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell Device [1028:0552]
InstallationDate: Installed on 2015-03-21 (18 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: Alienware M14xR2
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic 
root=UUID=2c30fb16-00b6-47fa-b592-c1f1a4fc163c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2012
dmi.bios.vendor: Alienware
dmi.bios.version: A03
dmi.board.name: M14xR2
dmi.board.vendor: Alienware
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A03
dmi.modalias: 
dmi:bvnAlienware:bvrA03:bd03/07/2012:svnAlienware:pnM14xR2:pvrA03:rvnAlienware:rnM14xR2:rvrA03:cvnAlienware:ct8:cvrA03:
dmi.product.name: M14xR2
dmi.product.version: A03
dmi.sys.vendor: Alienware
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Apr  9 11:48:50 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


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

** Information type changed from Public to Private Security

** Description changed:

  These posts describe my problem:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1393169
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1396361
+ But in my case, only when using multiple monitors it happens.
  
- The only way I've found to remove the extra mouse cursor is to drag an image 
in Chrome (?). It doesn't work with an image in Firefox nor in another program. 
+ The only way I've found to remove the extra mouse cursor is to drag an image 
in Chrome (?). It doesn't work with an image in Firefox nor in another program.
  Anyway, the extra mouse coursor appears again at any time, so I have no 
solution for this.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  9 13:53:03 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:0552]
-  NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Dell Device [1028:0552]
+  

[Touch-packages] [Bug 1419248] Re: udev-204-5ubuntu20.10 breakes usb_modeswitch

2015-04-09 Thread ramakrishna
usb-modeswitch 2.2.1 is not supported by udev (204-5ubuntu20.10) few
dongles from huawei {model : EC159} and some other.

By downgrading to udev {204-5ubuntu20.9} its working with those dongles.

Kernel version used : 3.14.19
Ubuntu version : 14.04.2 LTS

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

Title:
  udev-204-5ubuntu20.10 breakes usb_modeswitch

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  usb_modeswitch doesn't work after upgrade from udev-204-5ubuntu20.9 to
  udev-204-5ubuntu20.10. Downgrading to udev-204-5ubuntu20.9 solves the
  problem.

  
  Kernel:
  Linux localhost 3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:37:48 UTC 2015 
i686 i686 i686 GNU/Linux

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

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


[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work

2015-04-09 Thread Jamie
P.s. How is this bug not classed as a security risk? When /boot is full
no more security updates can be installed (when the owner of the machine
is lead to believe they are still being installed)

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

Title:
  Unattended-Upgrade::Remove-Unused-Dependencies does not work

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies true;'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies true;

  but nothing happens (note the line Packages that are auto removed: ''
  :

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: 'Version: package:'accountsservice' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libaccountsservice0' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libdrm-intel1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-nouveau1a' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-radeon1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm2' 
version:'2.4.43-0ubuntu0.0.3''
  Checking: bc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub2-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: iproute ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: landscape-common ([Origin component:'main' 
archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' 
site:'gb.archive.ubuntu.com' isTrusted:True])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found 

[Touch-packages] [Bug 1442079] [NEW] Registry/ChildScopesRepository failures if some paths don't exist

2015-04-09 Thread Pawel Stolowski
Public bug reported:

I'm developing some tests in a clean linux container (much like a
chroot), where I've never run a desktop session or our scopes. Because
of that I've no ~/.local/share/applications directory, nor ~/.config
/unity-scopes. This causes errors when scope registry attempts to create
.desktop files and child scopes repository tries to store child-
scopes.json.

NB, it would be great if tests were not messing up with home directory
contents; can it already be achieved with XDG_DATA_DIRS?

scoperegistry [musicaggregator test]: ignoring scope mediascanner-music: 
cannot create metadata: unity::SyscallException: 
RegistryObject::create_desktop_file: unable to create desktop file: 
/home/vivid/.local/share/applications/mediascanner-music.desktop (errno = 2)
scoperegistry [musicaggregator test]: ignoring scope mediascanner-video: 
cannot create metadata: unity::SyscallException: 
RegistryObject::create_desktop_file: unable to create desktop file: 
/home/vivid/.local/share/applications/mediascanner-video.desktop (errno = 2)
scoperegistry [musicaggregator test]: ignoring scope musicaggregator: cannot 
create metadata: unity::SyscallException: RegistryObject::create_desktop_file: 
unable to create desktop file: 
/home/vivid/.local/share/applications/musicaggregator.desktop (errno = 2)
scoperegistry [musicaggregator test]: ignoring scope videoaggregator: cannot 
create metadata: unity::SyscallException: RegistryObject::create_desktop_file: 
unable to create desktop file: 
/home/vivid/.local/share/applications/videoaggregator.desktop (errno = 2)
scoperegistry [musicaggregator test]: no remote registry configured, only local 
scopes will be available
scoperegistry [musicaggregator test]: ignoring installed scope 
musicaggregator: cannot create metadata: unity::SyscallException: 
RegistryObject::create_desktop_file: unable to create desktop file: 
/home/vivid/.local/share/applications/musicaggregator.desktop (errno = 2)
[2015-04-09 12:31:20.129446] INFO: RegistryTest: ScopesWatcher: scope: 
musicaggregator installed to: 
/home/vivid/keywords/tests/data/../../src/musicaggregator
scoperegistry [musicaggregator test]: ignoring installed scope 
mediascanner-music: cannot create metadata: unity::SyscallException: 
RegistryObject::create_desktop_file: unable to create desktop file: 
/home/vivid/.local/share/applications/mediascanner-music.desktop (errno = 2)
[2015-04-09 12:31:20.130857] INFO: RegistryTest: ScopesWatcher: scope: 
mediascanner-music installed to: 
/home/vivid/keywords/tests/data/../../src/mymusic
scoperegistry [musicaggregator test]: ignoring installed scope 
mediascanner-video: cannot create metadata: unity::SyscallException: 
RegistryObject::create_desktop_file: unable to create desktop file: 
/home/vivid/.local/share/applications/mediascanner-video.desktop (errno = 2)
[2015-04-09 12:31:20.131932] INFO: RegistryTest: ScopesWatcher: scope: 
mediascanner-video installed to: 
/home/vivid/keywords/tests/data/../../src/myvideos
scoperegistry [musicaggregator test]: ignoring installed scope 
videoaggregator: cannot create metadata: unity::SyscallException: 
RegistryObject::create_desktop_file: unable to create desktop file: 
/home/vivid/.local/share/applications/videoaggregator.desktop (errno = 2)
[2015-04-09 12:31:20.133096] INFO: RegistryTest: ScopesWatcher: scope: 
videoaggregator installed to: 
/home/vivid/keywords/tests/data/../../src/videoaggregator
[2015-04-09 12:31:20.193758] INFO: RegistryTest: 
RegistryObject::ScopeProcess::exec(): Process for scope: musicaggregator 
started
[2015-04-09 12:31:20.197118] INFO: musicaggregator: 
ChildScopesRepository::read_repo(): Failed to open file: 
/home/vivid/.config/unity-scopes/musicaggregator/child-scopes.json
[2015-04-09 12:31:20.197171] ERROR: musicaggregator: 
ChildScopesRepository::write_repo(): Failed to open file: 
/home/vivid/.config/unity-scopes/musicaggregator/child-scopes.json
scoperunner: unity::ResourceException: Scope mediascanner-music: exception from 
start():
unable to open database file

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

- I'm developing some tests in a clean linux container (much a like
+ I'm developing some tests in a clean linux container (much like a
  chroot), where I've never run a desktop session or our scopes. Because
  of that I've no ~/.local/share/applications directory, nor ~/.config
  /unity-scopes. This cause errors when scope registry attempts to create
  .desktop files and child scopes repository tries to store child-
  scopes.json.
  
  NB, it would be great if tests were not messing up with home directory
  contents; can it be already achieved with XDG_DATA_DIRS?
  
  scoperegistry [musicaggregator test]: ignoring scope mediascanner-music: 
cannot create metadata: unity::SyscallException: 
RegistryObject::create_desktop_file: unable to create desktop file: 
/home/vivid/.local/share/applications/mediascanner-music.desktop (errno = 2)
 

[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness

2015-04-09 Thread Pat McGowan
in device tarball

** Changed in: canonical-devices-system-image
   Status: In Progress = Fix Released

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

Title:
  brigtness slider should not allow total darkness

Status in the base for Ubuntu mobile products:
  Fix Released
Status in indicator-power package in Ubuntu:
  Invalid

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively bricks the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

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

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


[Touch-packages] [Bug 1441232] Re: [FFe] Settings page in the browser application

2015-04-09 Thread Timo Jyrinki
Released as https://launchpad.net/ubuntu/+source/webbrowser-
app/0.23+15.04.20150408-0ubuntu1

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

  [ CI Train Bot ]
  * New rebuild forced.
  * Resync trunk.

  [ Olivier Tilloy ]
  * Add a Clear Cache entry under the privacy settings. (LP: #1296364,
#1260014)
  * Add settings page, per design specification. This adds qml-module-
qt-labs-folderlistmodel and qml-module-qt-labs-settings as runtime
dependencies for webbrowser-app. (LP: #1351183)
  * Autopilot tests for the settings UI. added:
tests/autopilot/webbrowser_app/tests/test_settings.py

  [ Riccardo Padovani ]
  * Add settings page, per design specification. This adds qml-module-
qt-labs-folderlistmodel and qml-module-qt-labs-settings as runtime
dependencies for webbrowser-app. (LP: #1351183)
  * Add settings page, per design specification. This adds qml-module-
qt-labs-folderlistmodel and qml-module-qt-labs-settings as runtime
dependencies for webbrowser-app. (LP: #1351183)
 -- CI Train Bot ci-train-...@canonical.com   Wed, 08 Apr 2015 14:09:36 +

** Changed in: webbrowser-app (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  [FFe] Settings page in the browser application

Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  This bug is to request a feature freeze exception in order to land the
  work done to add a settings page to webbrowser-app.

  It adds a Settings entry to the drawer menu in the chrome, which
  opens a separate page.

  The UX specification is available at
  https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-
  fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3ddd7bb9c_00.

  The visual design specification is available at
  
https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_021.

  A subset of the specification is implemented (the settings that are
  actually wired in the browser as of today).

  Note that this doesn’t affect at all the webapp container.

  The relevant merge requests are:
   - 
https://code.launchpad.net/~osomon/webbrowser-app/qt-labs-settings/+merge/253889
   - 
https://code.launchpad.net/~rpadovani/webbrowser-app/settings-page/+merge/253975
   - 
https://code.launchpad.net/~osomon/webbrowser-app/settings-page-ap-tests/+merge/254788
   - https://code.launchpad.net/~osomon/webbrowser-app/clearCache/+merge/255361

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

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


[Touch-packages] [Bug 1425376] Re: Ubuntu Core provides no console login prompt if network is unavailable

2015-04-09 Thread Steve Langasek
Ok, don't know how this ended up with the wrong bug number in the
changelog, but cloud-init has been uploaded and accepted into vivid.

cloud-init (0.7.7~bzr1088-0ubuntu3) vivid; urgency=medium

  * systemd/*.service: don't declare a Wants/Requires on network.target; this
is a passive target that should only be pulled in by implementors of the
networking service.  The requirement for network needs to be
expressed as a dependency on network-online.target.  LP: #1440180.


** Changed in: cloud-init (Ubuntu)
   Status: New = Fix Released

** Changed in: snappy-ubuntu
   Status: Fix Committed = Fix Released

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

Title:
  Ubuntu Core provides no console login prompt if network is unavailable

Status in Snappy Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in ifupdown package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Core provides no console login prompt if network is
  unavailable.

  If I plug ethernet in, it boots to the login prompt fine.

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

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


[Touch-packages] [Bug 1404672] Re: Kit creation fails because schroot isn't installed as a dependency

2015-04-09 Thread Timo Jyrinki
The error message is also wrongly shown in case of bug #1436835

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

Title:
  Kit creation fails because schroot isn't installed as a dependency

Status in click package in Ubuntu:
  Confirmed
Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of Utopic using the Ubuntu SDK from the SDK team
  ppa the initial click kit creation fails with the error:

  click chroot: error: schroot not installed and configured; install
  click-dev and schroot

  Presumably schroot should be added as a dependency for either the
  qtcreator-plugin-ubuntu or ubuntu-sdk package so that users aren't
  faced with errors when first attempting to create kits. (Despite the
  error message click-dev is already installed, this has schroot as a
  recommended package, but not a dependency).

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

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


[Touch-packages] [Bug 1441958] Re: Screen is shaking after installing 14.01

2015-04-09 Thread Tyler Hicks
** Information type changed from Private Security to Public

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

Title:
  Screen is shaking after installing 14.01

Status in xorg package in Ubuntu:
  New

Bug description:
  I just installed 14.01 and had installed all updates and doing a
  backup half way through everything froze. when I rebooted the mouse
  pointer was flashing and everthing was shaking, there was no internet
  conection or side/top bars. I'm using a usb boot for now. Any Idea's
  on how to fix this bug???

  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
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CasperVersion: 1.340
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr  9 04:28:15 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:0102]
  LiveMediaBuild: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper only-ubiquity quiet splash 
oem-config/enable=true --
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.60
  dmi.board.name: H61M-HVS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd12/09/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-HVS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  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.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Apr  9 03:07:53 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id6642 
   vendor ACI
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Touch-packages] [Bug 1439793] Re: deb-systemd-helper crashes while removing packages with unusual (but legal) Alias in unit config

2015-04-09 Thread Martin Pitt
I added a couple of test cases for existing functionality, and now added
a test and a fix for this bug:

  http://anonscm.debian.org/cgit/collab-maint/init-system-
helpers.git/commit/?id=19802a7555904

** Changed in: init-system-helpers (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  deb-systemd-helper crashes while removing packages with unusual (but
  legal) Alias in unit config

Status in init-system-helpers package in Ubuntu:
  Fix Committed

Bug description:
  While working on mysql-5.6 package we met unusual (maybe even partially 
incorrect) Alias option in systemd unit config:
  Alias=mysql.service
  It is unusual because mysql.service is the original name of the service which 
can be found inside /lib/systemd/system/... This Alias option doesn't make 
any sense (mysql service will be accessible as mysql.service even without this 
alias) and my assumption is that it was created because the author was not sure 
if it's okay not to have any aliases at all or you need at least one. Anyhow 
this seems to be legal to do that (i was not able to find any documents which 
state that this is incorrect) even if it's something useless.

  Installation went well and the following alias symlink has been created:
  /etc/systemd/system/mysq.service -- /lib/systemd/system/mysql.service
  Service was accessible via systemctl and everything was fine.

  When you try to remove/purge the package you get the following error:
  /usr/bin/deb-systemd-helper: error: unable to link 
/etc/systemd/system/mysql.service to /dev/null: File exists
  This happens because deb-systemd-helper tries to 'mask' service the following 
way:

  sub mask_service {
  my ($scriptname, $service_path) = @_;

  my $mask_link = '/etc/systemd/system/' . basename($service_path);

  if (-e $mask_link) {
  # If the link already exists, don’t do anything.
  return if -l $mask_link  readlink($mask_link) eq '/dev/null';

  debug $mask_link already exists, not masking.;
  return;
  }

  make_path(dirname($mask_link));
  symlink('/dev/null', $mask_link) or
  error(unable to link $mask_link to /dev/null: $!);
  ...
  }

  Check for '-e $mask_link' FAILS because symlink's TARGET
  (/lib/systemd/system/mysql.service) doesn't exists while doing postrm
  and '-e' FOLLOWS symlinks. That's why we go to symlink(...) call
  directly which fails because symlink already exists.

  WORKAROUND: If apt-get remove/purge crashes with the error mentioned
  above you need to manually remove symlink inside /etc/systemd/system
  (/etc/systemd/system/mysql.service in our case) and rerun apt-get
  remove/purge.

  I'm not sure if we want to fix that.
  On one hand, this situation is pretty rare.
  On other hand though, such Alias=original-name situation is somewhat legal 
and we may want to handle it correctly.

  This issue with Alias= has been fixed (by removing this useless Alias)
  in mysql-5.6 so that's not a blocker for us.

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

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


[Touch-packages] [Bug 1442033] Re: package click 0.4.21.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2015-04-09 Thread Tyler Hicks
** Information type changed from Private Security to Public

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

Title:
  package click 0.4.21.1 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in click package in Ubuntu:
  New

Bug description:
  the problem occurs after you install unity8

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: click 0.4.21.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Wed Apr  8 15:00:30 2015
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  SourcePackage: click
  Title: package click 0.4.21.1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1415029] Re: Not yet available but configured providers should be added as soon as they become available

2015-04-09 Thread Ken VanDine
** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: Ken VanDine (ken-vandine) = (unassigned)

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

Title:
  Not yet available but configured providers should be added as soon as
  they become available

Status in the base for Ubuntu mobile products:
  In Progress
Status in location-service package in Ubuntu:
  In Progress
Status in ubuntu-location-provider-here package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in ubuntu-location-provider-here package in Ubuntu RTM:
  Confirmed

Bug description:
  Right now, the location service tries to instantiate configured
  providers at startup. In specific corner cases, some of the configured
  sensors might not be available and the service should be able to be
  notified when those providers become available.

  In particular, this affects the wizard running on first boot, and
  subsequent login to the user session.

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

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


[Touch-packages] [Bug 1384357] Re: Current composition is not canceled when a text input field is cleared programmatically

2015-04-09 Thread Olivier Tilloy
** Description changed:

- Using rtm 122
- - start the webbrowser
- - go on google.com
- - type ubuntu in the google page text entry
- - tap the x symbol at the right of the entry
+ Steps to reproduce:
  
- - the entry is cleared and then the text is restored
+  1) on a touch device, browse to http://mikeasoft.com/~mike/oxide-clear.html
+  2) focus the text field and type any word in it (e.g. Ubuntu)
+  3) tap the X below the text field, this clears it
+  4) press backspace on the OSK
  
- once you hit that issue, you can also hit another bug
- - type the delete key until emptying the entry, then another time
+ Expected result: nothing happens
  
- - the text is restored and the delete key loop over the content
+ Current result: the previous preedit is restored and backspace deletes
+ the last letter (in that example, the text field now contains Ubunt)

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

Title:
  Current composition is not canceled when a text input field is cleared
  programmatically

Status in Oxide Webview:
  In Progress
Status in Ubuntu Keyboard:
  Invalid
Status in Web Browser App:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

   1) on a touch device, browse to http://mikeasoft.com/~mike/oxide-clear.html
   2) focus the text field and type any word in it (e.g. Ubuntu)
   3) tap the X below the text field, this clears it
   4) press backspace on the OSK

  Expected result: nothing happens

  Current result: the previous preedit is restored and backspace deletes
  the last letter (in that example, the text field now contains Ubunt)

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

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


[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch

2015-04-09 Thread Buzea Bogdan
** Attachment added: screenshot20150509_140524670.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+attachment/4370422/+files/screenshot20150509_140524670.png

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in indicator-location package in Ubuntu:
  New

Bug description:
  Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
  from BQ (I am on  update 20), but the app dont detect my location. I
  have to mention that I check Here terms  Condition and GPS and
  location are checked.

  I attached some screenshot from what I did.

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

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


[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch

2015-04-09 Thread Buzea Bogdan
** Attachment added: screenshot20150409_140421347.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+attachment/4370420/+files/screenshot20150409_140421347.png

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in indicator-location package in Ubuntu:
  New

Bug description:
  Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
  from BQ (I am on  update 20), but the app dont detect my location. I
  have to mention that I check Here terms  Condition and GPS and
  location are checked.

  I attached some screenshot from what I did.

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

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


[Touch-packages] [Bug 1440070] Re: openssh-server attempts to connect to upstart and the connection is refused

2015-04-09 Thread Martin Pitt
** Bug watch added: Debian Bug tracker #782191
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782191

** Also affects: openssh (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782191
   Importance: Unknown
   Status: Unknown

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

Title:
  openssh-server attempts to connect to upstart and the connection is
  refused

Status in openssh package in Ubuntu:
  Fix Committed
Status in openssh package in Debian:
  Unknown

Bug description:
  lsb_release -rd:
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  pkg-name:
  christian@Moustachio:~/Code$ apt-cache policy openssh-server
  openssh-server:
Installed: 1:6.7p1-5
Candidate: 1:6.7p1-5
Version table:
   *** 1:6.7p1-5 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  
  On Ubuntu 15.04 (Vivid Ververt) the installation of the package 
openssh-server displays the following error message:

  initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused

  Running 'systemctl status ssh' shows that systemd knows about the
  service:

  christian@Moustachio:~/Code$ ubuntu-bug openssh-server
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:12244): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  christian@Moustachio:~/Code$ systemctl status ssh
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: active (running) since Fri 2015-04-03 07:43:01 MDT; 4min 41s ago
   Main PID: 11689 (sshd)
 CGroup: /system.slice/ssh.service
 └─11689 /usr/sbin/sshd -D

  Apr 03 07:43:01 Moustachio systemd[1]: Started OpenBSD Secure Shell server.
  Apr 03 07:43:01 Moustachio systemd[1]: Starting OpenBSD Secure Shell server...
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on 0.0.0.0 port 22.
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on :: port 22.

  It appears that sshd is attempting to register with upstart and with
  systemd. SInce Ubuntu 15.04 upstart has been replaced with systemd. I
  expected openssh-server on Ubuntu 15.04 to not want to use upstart. It
  does properly use systemd, it just prints an error about trying to
  tallk to upstart.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssh-server 1:6.7p1-5
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  3 07:45:13 2015
  InstallationDate: Installed on 2015-03-23 (11 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150322)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1429687] Re: Cannot import two files with the same name to ContentStore.App

2015-04-09 Thread Ken VanDine
@rschroll: correct, it'll abort the transfer, for now.  In the future,
we'll be implementing an error API so we can send it to an error state
with a defined reason for the error.

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

Title:
  Cannot import two files with the same name to ContentStore.App

Status in Content sharing/picking infrastructure and service:
  Fix Released
Status in content-hub package in Ubuntu:
  Fix Released

Bug description:
  When you import a file using a ContentScope and ContentStore.App, it
  gets copied to ~/.local/share/appid/content-type/filename.  If
  you try to import another file with the same name and content type,
  the existing file will be left in place and the new file not copied
  over.  However, you get a ContentItem returned with the a URL pointing
  to the old imported file.

  My expectation is that the new file should be copied to file(1) or
  similar.  Perhaps this should only happen if the files are distinct.
  Failing this, ContentHub should throw an error and not let me think
  that the import succeeded.

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

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


[Touch-packages] [Bug 1442095] [NEW] Network-manager network information display does not show SLAAC addresses

2015-04-09 Thread wdesmet
Public bug reported:

I have a network where my IPv6 address is auto-configured using SLAAC
(with privacy extensions). Everything works fine, but when I check the
Information panel from network-manager, it only includes the IPv4
addresses. Apparently IPv6 addresses were never picked up on? All it
shows is IPv6 and then the dialog window ends.

The network info (partially redacted):

2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether [...]
inet 192.168.1.6/24 brd 192.168.1.255 scope global eth0
   valid_lft forever preferred_lft forever
inet6 2a02:[...]/64 scope global temporary dynamic 
   valid_lft 185909sec preferred_lft 71172sec
inet6 2a02:[...]/64 scope global mngtmpaddr dynamic 
   valid_lft 185909sec preferred_lft 185909sec

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

** Attachment added: screenshot of the info window
   
https://bugs.launchpad.net/bugs/1442095/+attachment/4370418/+files/Screenshot%20from%202015-04-09%2013%3A05%3A32.png

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

Title:
  Network-manager network information display does not show SLAAC
  addresses

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a network where my IPv6 address is auto-configured using SLAAC
  (with privacy extensions). Everything works fine, but when I check the
  Information panel from network-manager, it only includes the IPv4
  addresses. Apparently IPv6 addresses were never picked up on? All it
  shows is IPv6 and then the dialog window ends.

  The network info (partially redacted):

  2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
  link/ether [...]
  inet 192.168.1.6/24 brd 192.168.1.255 scope global eth0
 valid_lft forever preferred_lft forever
  inet6 2a02:[...]/64 scope global temporary dynamic 
 valid_lft 185909sec preferred_lft 71172sec
  inet6 2a02:[...]/64 scope global mngtmpaddr dynamic 
 valid_lft 185909sec preferred_lft 185909sec

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

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


[Touch-packages] [Bug 1442044] Re: Ordering processes: networkmanager should wait for kernel'module been activated first before starting

2015-04-09 Thread dino99
@Martin

what i'm reporting is only about the boot logic: if a process needs
first a kernel'module activation, then it might be checked, even if it
'come  go' like networkmanager.

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

Title:
  Ordering processes: networkmanager should wait for kernel'module been
  activated first before starting

Status in network-manager package in Ubuntu:
  New

Bug description:
  Get that journalctl log showing networkmanager starting before the
  related kernel'module been ready:

  systemd[1]: Starting Network.
  systemd[1]: Starting /etc/rc.local Compatibility...
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (lo): link connected
  NetworkManager[724]: info (lo): carrier is ON
  NetworkManager[724]: info (lo): new Generic device (driver: 'unknown' 
ifindex: 1)
  NetworkManager[724]: info (lo): exported as 
/org/freedesktop/NetworkManager/Devices/0
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (eth0): carrier is OFF
  NetworkManager[724]: info (eth0): new Ethernet device (driver: 'sky2' 
ifindex: 2)
  NetworkManager[724]: info (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/1
  NetworkManager[724]: info (eth0): device state change: unmanaged - 
unavailable (reason 'managed') [10 20 2]
  NetworkManager[724]: info (eth0): preparing device
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (eth1): carrier is OFF
  NetworkManager[724]: info (eth1): new Ethernet device (driver: 'sky2' 
ifindex: 3)
  NetworkManager[724]: info (eth1): exported as 
/org/freedesktop/NetworkManager/Devices/2
  NetworkManager[724]: info (eth1): device state change: unmanaged - 
unavailable (reason 'managed') [10 20 2]
  kernel: sky2 :04:00.0 eth0: enabling interface
  kernel: sky2 :03:00.0 eth1: enabling interface
  NetworkManager[724]: info (eth1): preparing device
  NetworkManager[724]: info urfkill disappeared from the bus

  that mobo have eth0  eth1 ports, but only eth1 is used. As the last
  lines logged, networworkmanager is able to be loaded when the module
  sky2 is enabled.

  network-manager 0.9.10.0-4ubuntu13

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:41:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2015-04-09 Thread Martin Pitt
** Package changed: systemd (Ubuntu) = colord (Ubuntu)

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  New

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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


[Touch-packages] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

2015-04-09 Thread Joyce
Wow, that was fast! Thank you!

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

Title:
  15.04 Vivid Vervet won't boot after uninstalling lightdm

Status in lightdm package in Ubuntu:
  Triaged
Status in xdiagnose package in Ubuntu:
  Fix Released

Bug description:
  We've been trying to figure out how to disable the login screen on
  15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall
  lightdm. If we do this on 15.04, however, the system won't boot. :(
  The main error seems to be: Failed to isolate default target,
  freezing. (I have a picture of this, if there is a way to upload
  one.)

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

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


[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work

2015-04-09 Thread Nils Toedtmann
Each day this bug breaks more Ubuntu servers that do unattended-
upgrades, in particular cloud servers with 100GB rootfs. I alone have
a few dozens affected machines.

And it's not totally trivial for Admin Average to diagnose the inode
shortage, realize it's flooded with linux-headers packages, and to
convince apt-get (potentially stuck in 'broken dependancies') to clean
up.

I think this is more impartant than medium, at least for Precise/LTS.

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

Title:
  Unattended-Upgrade::Remove-Unused-Dependencies does not work

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies true;'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies true;

  but nothing happens (note the line Packages that are auto removed: ''
  :

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: 'Version: package:'accountsservice' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libaccountsservice0' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libdrm-intel1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-nouveau1a' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-radeon1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm2' 
version:'2.4.43-0ubuntu0.0.3''
  Checking: bc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub2-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: iproute ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: landscape-common ([Origin component:'main' 
archive:'precise-updates' origin:'Ubuntu' label:'Ubuntu' 
site:'gb.archive.ubuntu.com' isTrusted:True])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s)   

[Touch-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

2015-04-09 Thread Tony Espy
** Changed in: indicator-network (Ubuntu)
   Status: New = Confirmed

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New = Confirmed

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

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Confirmed

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

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

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


[Touch-packages] [Bug 1267059] Re: Unattended-Upgrade::Remove-Unused-Dependencies does not work

2015-04-09 Thread Jamie
This is ridiculous, why has this not been fixed yet?

I manage around 100 VM's and this problem is causing me serious
headaches. I simply haven't got time to go round manually autoremoving
old kernals and it would be foolish not to leave unattended security
updates on.

Just because there are only ~34 people who have bothered to write on
this thread does not mean that others with 13.04 or greater are not
affected, I think most will be eventually.

It is correct to say that the documentation is wrong; Unattended-Upgrade
::Remove-Unused-Dependencies true;  is not currently equivalent to
apt-get autoremove but that is the expected behaviour (I imagine most
people who install ubuntu don't want to have to consider how to remove
old kernals so this should be the default behaviour)

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

Title:
  Unattended-Upgrade::Remove-Unused-Dependencies does not work

Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies true;'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies true;

  but nothing happens (note the line Packages that are auto removed: ''
  :

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: 'Version: package:'accountsservice' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libaccountsservice0' 
version:'0.6.15-2ubuntu9.6.1''
  adjusting candidate version: 'Version: package:'libdrm-intel1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-nouveau1a' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm-radeon1' 
version:'2.4.43-0ubuntu0.0.3''
  adjusting candidate version: 'Version: package:'libdrm2' 
version:'2.4.43-0ubuntu0.0.3''
  Checking: bc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub-pc-bin ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: grub2-common ([Origin component:'main' archive:'precise-updates' 
origin:'Ubuntu' label:'Ubuntu' site:'gb.archive.ubuntu.com' isTrusted:True])
  Checking: iproute ([Origin component:'main' 

[Touch-packages] [Bug 1441822] Re: unity8 consuming excessive cpu in a preview page

2015-04-09 Thread Pat McGowan
Can you take a look to see if we regressed something here, remember
happens on rtm and vivid

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) = Zsombor Egri (zsombi)

** Changed in: canonical-devices-system-image
 Assignee: kevin gunn (kgunn72) = Zoltan Balogh (bzoltan)

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

Title:
  unity8 consuming excessive cpu in a preview page

Status in the base for Ubuntu mobile products:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  krillin running vivid 175

  Opened a youtube video preview from the Video scope and did not interact with 
it
  Running top I see unity8 between 22 and 32 % and unity-8 dash between 15 and 
20
  Same with music preview

  On mako running rtm 219 its over 80% combined with  unity8-dash using the 
majority
  When the screen turns off it continues to use over 20% cpu

  The CPU is still used when the scope is in the background

  Does not happen in a news or nearby scope preview
  Does happen with youtube ad 7digital previews

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

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


[Touch-packages] [Bug 1441883] Re: 15.04 Vivid Vervet won't boot after uninstalling lightdm

2015-04-09 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/xdiagnose

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

Title:
  15.04 Vivid Vervet won't boot after uninstalling lightdm

Status in lightdm package in Ubuntu:
  Triaged
Status in xdiagnose package in Ubuntu:
  Fix Committed

Bug description:
  We've been trying to figure out how to disable the login screen on
  15.04 Vivid Vervet. Our method of doing this on 14.04 was to uninstall
  lightdm. If we do this on 15.04, however, the system won't boot. :(
  The main error seems to be: Failed to isolate default target,
  freezing. (I have a picture of this, if there is a way to upload
  one.)

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

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


[Touch-packages] [Bug 1442044] [NEW] Ordering processes: networkmanager should wait for kernel'module activated first before starting

2015-04-09 Thread dino99
Public bug reported:

Get that journalctl log showing networkmanager starting before the
related kernel'module been ready:


systemd[1]: Starting Network.
systemd[1]: Starting /etc/rc.local Compatibility...
NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' 
failed
NetworkManager[724]: info (lo): link connected
NetworkManager[724]: info (lo): carrier is ON
NetworkManager[724]: info (lo): new Generic device (driver: 'unknown' 
ifindex: 1)
NetworkManager[724]: info (lo): exported as 
/org/freedesktop/NetworkManager/Devices/0
NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' 
failed
NetworkManager[724]: info (eth0): carrier is OFF
NetworkManager[724]: info (eth0): new Ethernet device (driver: 'sky2' 
ifindex: 2)
NetworkManager[724]: info (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/1
NetworkManager[724]: info (eth0): device state change: unmanaged - 
unavailable (reason 'managed') [10 20 2]
NetworkManager[724]: info (eth0): preparing device
NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' 
failed
NetworkManager[724]: info (eth1): carrier is OFF
NetworkManager[724]: info (eth1): new Ethernet device (driver: 'sky2' 
ifindex: 3)
NetworkManager[724]: info (eth1): exported as 
/org/freedesktop/NetworkManager/Devices/2
NetworkManager[724]: info (eth1): device state change: unmanaged - 
unavailable (reason 'managed') [10 20 2]
kernel: sky2 :04:00.0 eth0: enabling interface
kernel: sky2 :03:00.0 eth1: enabling interface
NetworkManager[724]: info (eth1): preparing device
NetworkManager[724]: info urfkill disappeared from the bus

that mobo have eth0  eth1 ports, but only eth1 is used. As the last
lines logged, networworkmanager is able to be loaded when the module
sky2 is enabled.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-6ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.17-0ubuntu1
Architecture: i386
CurrentDesktop: GNOME
Date: Thu Apr  9 11:41:02 2015
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

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


** Tags: apport-bug i386 package-from-proposed vivid

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

Title:
  Ordering processes: networkmanager should wait for kernel'module
  activated first before starting

Status in systemd package in Ubuntu:
  New

Bug description:
  Get that journalctl log showing networkmanager starting before the
  related kernel'module been ready:

  
  systemd[1]: Starting Network.
  systemd[1]: Starting /etc/rc.local Compatibility...
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (lo): link connected
  NetworkManager[724]: info (lo): carrier is ON
  NetworkManager[724]: info (lo): new Generic device (driver: 'unknown' 
ifindex: 1)
  NetworkManager[724]: info (lo): exported as 
/org/freedesktop/NetworkManager/Devices/0
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (eth0): carrier is OFF
  NetworkManager[724]: info (eth0): new Ethernet device (driver: 'sky2' 
ifindex: 2)
  NetworkManager[724]: info (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/1
  NetworkManager[724]: info (eth0): device state change: unmanaged - 
unavailable (reason 'managed') [10 20 2]
  NetworkManager[724]: info (eth0): preparing device
  NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE 
(self)' failed
  NetworkManager[724]: info (eth1): carrier is OFF
  

[Touch-packages] [Bug 1441154] Re: Built in Apport-Like Bug and Suggestion Reporting Tool Needed

2015-04-09 Thread wayneoutthere
Excellent. No other mobile OS cares what the users think nor gives them
a quick way to give feedback so the potential of Ubuntu becoming the
best by a long shot, in my opinion, depends on this feature and the
ability to have users give, for free, their real-world opinions and bug
reports.  Thansk for not trashing the idea!

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

Title:
  Built in Apport-Like Bug and Suggestion Reporting Tool Needed

Status in Ubuntu UX bugs:
  Triaged
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  I suggest building into the OS itself a tool like Apport that
  automatically reports crashes to developpers.  In addition to this
  tool, it would be excellent if an app or part of the phone could be
  dedicated to user suggestions.  it is highly inconvenient to have to
  run to another machine to report a bug and I am convinced that Ubuntu
  would become amazing fast with a quick 'suggestion reporting app'
  built right into the phone.  Us non programmers would love to give
  'real world' suggestions

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

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


[Touch-packages] [Bug 1432636] Re: Scopes with a helper app show up as apps in the store

2015-04-09 Thread Martin Albisetti
That is indeed the plan of record.

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

Title:
  Scopes with a helper app show up as apps in the store

Status in Click Package metadata search service:
  New
Status in Ubuntu UX bugs:
  Triaged
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Click packages that have both a main scope and a helper app don't show
  up as Scopes in the app store, but instead they show up as apps. Eg:
  untappd scope.

  Also, after installation they show the Open button to start the
  helper app, instead of the Search button to show the scope.

  The ML thread that started this: https://lists.launchpad.net/ubuntu-
  phone/msg11459.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/click-package-index/+bug/1432636/+subscriptions

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


[Touch-packages] [Bug 1442085] Re: Overlapping labels in table widgets on previews

2015-04-09 Thread Albert Astals Cid
** Changed in: unity8 (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/1442085

Title:
  Overlapping labels in table widgets on previews

Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Check out the screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1442085/+subscriptions

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


[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts

2015-04-09 Thread Charles Kerr
IMO solving this at the ui-toolkit level is not correct, as that still
leaves the problem for system services e.g. indicator-datetime.

seb128, looks to me like a lot of this traffic is coming from system-
settings. src/accountsservice.cpp AccountsService::setUpInterface() is
the source of the FindUserById() call, and the Get calls are coming from
when the code pulls the properties for IncomingMessageVibrate,
IncomingMessageVibrateSilentMode, OtherVibrate, DialpadSoundsEnabled,
IncomingCallVibrate, IncomingCallVibrateSilentMode.

Two suggestions:

1. It's not clear to me why these are being stored in AccountsService
instead of in gsettings-ubuntu-touch-schemas. The latter seems the more
logical place for it and would be easy to implement; e.g. if the
properties mentioned above were simple properties in
com.ubuntu.touch.sound. Indeed, it looks like there's already some
overlap, as there's a silent-mode property both there and on
AccountsService. I'd be happy to write g-u-t-s and u-s-s patches for
these if everyone's agreeable on this being moved to touch-schemas.
(This would benefit indicator-datetime too :-)

2. For client applications, I agree with mdeslaur, that it would be good
to have a service handle this instead of relying on client apps to
monitor the setting and do the right thing; e.g. adding an intent
argument to usensord's VibratePattern method specifying whether the
vibration is due to an incoming call, a received message, or other. That
still wouldn't solve the problem for system-settings, which still has to
get/set the fields.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor=DENIED 
operation=dbus_method_call  bus=system path=/org/freedesktop/Accounts 
interface=org.freedesktop.DBus.Introspectable member=Introspect mask=send 
name=org.freedesktop.Accounts pid=2632 
profile=com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26 
peer_pid=1596 peer_profile=unconfined
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor=DENIED 
operation=dbus_method_call  bus=system path=/org/freedesktop/Accounts 
interface=org.freedesktop.Accounts member=FindUserById mask=send 
name=org.freedesktop.Accounts pid=2632 
profile=com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26 
peer_pid=1596 peer_profile=unconfined

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor=DENIED 
operation=dbus_method_call  bus=system path=/org/freedesktop/Accounts 
interface=org.freedesktop.DBus.Introspectable member=Introspect mask=send 
name=org.freedesktop.Accounts pid=3377 
profile=com.ubuntu.calculator_calculator_1.3.339 peer_pid=1596 
peer_profile=unconfined
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor=DENIED 
operation=dbus_method_call  bus=system path=/org/freedesktop/Accounts 
interface=org.freedesktop.Accounts member=FindUserById mask=send 
name=org.freedesktop.Accounts pid=3377 
profile=com.ubuntu.calculator_calculator_1.3.339 peer_pid=1596 
peer_profile=unconfined

  The following rules allow the requested access:
dbus (send)
 bus=system
 path=/org/freedesktop/Accounts
 interface=org.freedesktop.DBus.{Introspectable,Properties}
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path=/org/freedesktop/Accounts
 interface=org.freedesktop.Accounts
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path=/org/freedesktop/Accounts/User[0-9]*
 interface=org.freedesktop.DBus.Properties
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
 

[Touch-packages] [Bug 1441822] Re: unity8 consuming excessive cpu in a preview page

2015-04-09 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: New = Triaged

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Albert Astals Cid (aacid)

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

Title:
  unity8 consuming excessive cpu in a preview page

Status in the base for Ubuntu mobile products:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  krillin running vivid 175

  Opened a youtube video preview from the Video scope and did not interact with 
it
  Running top I see unity8 between 22 and 32 % and unity-8 dash between 15 and 
20
  Same with music preview

  On mako running rtm 219 its over 80% combined with  unity8-dash using the 
majority
  When the screen turns off it continues to use over 20% cpu

  The CPU is still used when the scope is in the background

  Does not happen in a news or nearby scope preview
  Does happen with youtube ad 7digital previews

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

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


[Touch-packages] [Bug 1441975] Re: have not shadows

2015-04-09 Thread Iain Lane
** Package changed: nautilus (Ubuntu) = ubuntu-themes (Ubuntu)

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

Title:
  have not shadows

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  nautilus and desktop have not shadows on context menus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr  9 08:54:22 2015
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2015-03-05 (34 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2015-03-05T22:46:49.143864

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

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


[Touch-packages] [Bug 1441449] Re: [HP Z820] external microphone does not work, only records noises

2015-04-09 Thread Yung Shen
** Tags added: 201407-15335 taipei-lab

** Tags added: blocks-hwcert

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

Title:
  [HP Z820] external microphone does not work, only records noises

Status in HWE Next Project:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Records with a lot noises, barely can heard the sound.

  Step to reproduce:

  1. plug your microphone to the front/rear micrphone jack
  2. turn up the microphone volume in the system  sound settings
  3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt 
when you finish

  Expected result:

  when playing the recordings it should plays recognizable sound.

  Actual results:

  A lot noise in the recordings.

  
  Additional information:
  In the attached recording file, you should hear, Testing, One, Two, Three, 
Four, Five .

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1696 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1696 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr  8 01:32:46 2015
  InstallationDate: Installed on 2015-04-02 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J63 v03.69
  dmi.board.asset.tag: 2UA4242K12
  dmi.board.name: 158B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: 2UA4242K12
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z820 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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


[Touch-packages] [Bug 1442105] [NEW] GPS not working on my BQ Ubuntu Touch

2015-04-09 Thread Buzea Bogdan
Public bug reported:

Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from
BQ (I am on  update 20), but the app dont detect my location. I have to
mention that I check Here terms  Condition and GPS and location are
checked.

I attached some screenshot from what I did.

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


** Tags: bq gps

** Attachment added: screenshot20150409_140417842.png
   
https://bugs.launchpad.net/bugs/1442105/+attachment/4370419/+files/screenshot20150409_140417842.png

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in indicator-location package in Ubuntu:
  New

Bug description:
  Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
  from BQ (I am on  update 20), but the app dont detect my location. I
  have to mention that I check Here terms  Condition and GPS and
  location are checked.

  I attached some screenshot from what I did.

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

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


[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch

2015-04-09 Thread Buzea Bogdan
** Attachment added: screenshot20150409_140431669.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+attachment/4370421/+files/screenshot20150409_140431669.png

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in indicator-location package in Ubuntu:
  New

Bug description:
  Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
  from BQ (I am on  update 20), but the app dont detect my location. I
  have to mention that I check Here terms  Condition and GPS and
  location are checked.

  I attached some screenshot from what I did.

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

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


[Touch-packages] [Bug 1442105] Re: GPS not working on my BQ Ubuntu Touch

2015-04-09 Thread Buzea Bogdan
Please tell me if I need to sent you some info about this.

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in indicator-location package in Ubuntu:
  New

Bug description:
  Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
  from BQ (I am on  update 20), but the app dont detect my location. I
  have to mention that I check Here terms  Condition and GPS and
  location are checked.

  I attached some screenshot from what I did.

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

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


[Touch-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

2015-04-09 Thread Launchpad Bug Tracker
** Branch linked: lp:~mathieu-tl/network-manager/scanlist-pruning

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

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Confirmed

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

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

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


[Touch-packages] [Bug 1436982] Re: Unity freezes for a few seconds when 'clear all' is tapped in Notifications

2015-04-09 Thread Launchpad Bug Tracker
** Branch linked: lp:~nick-dedekind/unity8/1436982.message-freeze

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

Title:
  Unity freezes for a few seconds when 'clear all' is tapped in
  Notifications

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  1. Create a missed call or sms.
  2. Open Notification from top.
  3. press the 'clear all' label
  4. try to close the Notification menu by dragging it from bottom

  What happens:
  Nothing happens, unity seem to freeze for 2 seconds.

  This issue does not exist in RTM branch.

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

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


[Touch-packages] [Bug 1441986] Re: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher garbled after resuming from suspend

2015-04-09 Thread Yung Shen
** Tags added: 201407-15335 taipei-lab

** Tags added: blocks-hwcert

** Description changed:

  Launcher does not display correctly after suspend, there is other
  different corruption in different application scenario, most of them can
  be recover by switch between VT.
  
  Steps to reproduce:
  
  1. suspend the system in the middle of using
  2. resume from suspend
  
  Expected result:
  
  Desktop screen display correctly.
  
  Actual result:
  
  Some parts of the screen corrupted.
  
  Workaround:
  Switching from X to VT may temporary fix these corruptions.
  
+ 
+ Additional information:
+ Installing driver downloading from nvidia.com the screen garbled/corruption 
does not happen again.
+ version: NVIDIA-Linux-x86_64-346.59.run
+ 
+ 
+ 
+ -
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17
  Uname: Linux 3.13.0-49-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
-  GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.113  Mon Dec  1 21:08:13 
PST 2014
+  GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  9 02:09:23 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:079c]
+  NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:079c]
  InstallationDate: Installed on 2015-04-02 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Z820 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic 
root=UUID=d8280bec-e0b3-4b37-8f6b-aa899731f110 ro rootdelay=60 quiet splash 
initcall_debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J63 v03.69
  dmi.board.asset.tag: 2UA4242K12
  dmi.board.name: 158B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: 2UA4242K12
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Z820 Workstation
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr  8 09:39:05 2015
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.15.1-0ubuntu2.7

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

Title:
  NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] Desktop launcher
  garbled after resuming from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Launcher does not display correctly after suspend, there is other
  different corruption in different application scenario, most of them
  can be recover by switch between VT.

  Steps to reproduce:

  1. suspend the system in the middle of using
  2. resume from suspend

  Expected result:

  Desktop screen 

[Touch-packages] [Bug 1440070] Re: openssh-server attempts to connect to upstart and the connection is refused

2015-04-09 Thread Martin Pitt
** Changed in: openssh (Ubuntu)
   Status: Triaged = Fix Committed

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  openssh-server attempts to connect to upstart and the connection is
  refused

Status in openssh package in Ubuntu:
  Fix Committed

Bug description:
  lsb_release -rd:
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  pkg-name:
  christian@Moustachio:~/Code$ apt-cache policy openssh-server
  openssh-server:
Installed: 1:6.7p1-5
Candidate: 1:6.7p1-5
Version table:
   *** 1:6.7p1-5 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  
  On Ubuntu 15.04 (Vivid Ververt) the installation of the package 
openssh-server displays the following error message:

  initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused

  Running 'systemctl status ssh' shows that systemd knows about the
  service:

  christian@Moustachio:~/Code$ ubuntu-bug openssh-server
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:12244): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  christian@Moustachio:~/Code$ systemctl status ssh
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: active (running) since Fri 2015-04-03 07:43:01 MDT; 4min 41s ago
   Main PID: 11689 (sshd)
 CGroup: /system.slice/ssh.service
 └─11689 /usr/sbin/sshd -D

  Apr 03 07:43:01 Moustachio systemd[1]: Started OpenBSD Secure Shell server.
  Apr 03 07:43:01 Moustachio systemd[1]: Starting OpenBSD Secure Shell server...
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on 0.0.0.0 port 22.
  Apr 03 07:43:01 Moustachio sshd[11689]: Server listening on :: port 22.

  It appears that sshd is attempting to register with upstart and with
  systemd. SInce Ubuntu 15.04 upstart has been replaced with systemd. I
  expected openssh-server on Ubuntu 15.04 to not want to use upstart. It
  does properly use systemd, it just prints an error about trying to
  tallk to upstart.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openssh-server 1:6.7p1-5
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  3 07:45:13 2015
  InstallationDate: Installed on 2015-03-23 (11 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150322)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1439793] Re: deb-systemd-helper crashes while removing packages with unusual (but legal) Alias in unit config

2015-04-09 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/init-system-helpers

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

Title:
  deb-systemd-helper crashes while removing packages with unusual (but
  legal) Alias in unit config

Status in init-system-helpers package in Ubuntu:
  Fix Committed

Bug description:
  While working on mysql-5.6 package we met unusual (maybe even partially 
incorrect) Alias option in systemd unit config:
  Alias=mysql.service
  It is unusual because mysql.service is the original name of the service which 
can be found inside /lib/systemd/system/... This Alias option doesn't make 
any sense (mysql service will be accessible as mysql.service even without this 
alias) and my assumption is that it was created because the author was not sure 
if it's okay not to have any aliases at all or you need at least one. Anyhow 
this seems to be legal to do that (i was not able to find any documents which 
state that this is incorrect) even if it's something useless.

  Installation went well and the following alias symlink has been created:
  /etc/systemd/system/mysq.service -- /lib/systemd/system/mysql.service
  Service was accessible via systemctl and everything was fine.

  When you try to remove/purge the package you get the following error:
  /usr/bin/deb-systemd-helper: error: unable to link 
/etc/systemd/system/mysql.service to /dev/null: File exists
  This happens because deb-systemd-helper tries to 'mask' service the following 
way:

  sub mask_service {
  my ($scriptname, $service_path) = @_;

  my $mask_link = '/etc/systemd/system/' . basename($service_path);

  if (-e $mask_link) {
  # If the link already exists, don’t do anything.
  return if -l $mask_link  readlink($mask_link) eq '/dev/null';

  debug $mask_link already exists, not masking.;
  return;
  }

  make_path(dirname($mask_link));
  symlink('/dev/null', $mask_link) or
  error(unable to link $mask_link to /dev/null: $!);
  ...
  }

  Check for '-e $mask_link' FAILS because symlink's TARGET
  (/lib/systemd/system/mysql.service) doesn't exists while doing postrm
  and '-e' FOLLOWS symlinks. That's why we go to symlink(...) call
  directly which fails because symlink already exists.

  WORKAROUND: If apt-get remove/purge crashes with the error mentioned
  above you need to manually remove symlink inside /etc/systemd/system
  (/etc/systemd/system/mysql.service in our case) and rerun apt-get
  remove/purge.

  I'm not sure if we want to fix that.
  On one hand, this situation is pretty rare.
  On other hand though, such Alias=original-name situation is somewhat legal 
and we may want to handle it correctly.

  This issue with Alias= has been fixed (by removing this useless Alias)
  in mysql-5.6 so that's not a blocker for us.

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

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


[Touch-packages] [Bug 1439955] Re: nfs root script breaks with absolute /sbin/init symlinks

2015-04-09 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.103ubuntu14

---
initramfs-tools (0.103ubuntu14) vivid; urgency=medium

  * scripts/nfs: Fix nfs mount check for absolute /sbin/init symlink, to make
root NFS work again. Cherry-picked from Debian (commit 7bc24f829f).
(LP: #1439955)
 -- Martin Pitt martin.p...@ubuntu.com   Thu, 09 Apr 2015 10:03:26 +0200

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  nfs root script breaks with absolute /sbin/init symlinks

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  The initramfs boot script try to mount the root filesystem into /root
  and look for a /sbin/init file inside that folder. systemd installs
  /sbin/init as a link to /lib/systemd/systemd, which the initramfs
  scripts can't find (because the link is an absolute path and the root
  is mounted under /root).

  Making that link a relative path fixes the problem (i.e. making it
  ../lib/systemd/systemd).

  Please, see /usr/share/initramfs-tools/scripts/nfs for the affected
  script.

  
  I believe this should be fixed before the release of 15.04, as it breaks all 
nfs root installs.

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

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


  1   2   3   >