[Touch-packages] [Bug 1090570] Re: When starting blender screen goes black and login returns

2016-05-05 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  When starting blender screen goes black and login returns

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Blender seems to kill Xorg.

  Extra attachments coming. I have added xsession-errors already though
  it doesn't seem to have anything useful.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: blender 2.63a-1ubuntu5
  ProcVersionSignature: Ubuntu 3.7.0-5.4-lowlatency 3.7.0-rc8
  Uname: Linux 3.7.0-5-lowlatency i686
  ApportVersion: 2.7-0ubuntu2
  Architecture: i386
  Date: Fri Dec 14 13:42:06 2012
  InstallationDate: Installed on 2012-12-13 (0 days ago)
  InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Alpha i386 
(20121213)
  MarkForUpload: True
  SourcePackage: blender
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1550846] Re: package identification is awful

2016-05-05 Thread Launchpad Bug Tracker
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apport (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package identification is awful

Status in apport package in Ubuntu:
  Expired

Bug description:
  Recently I reported a bug against the kernel - apport made this very
  difficult.

  The instructions at 
  clearly state that the correct thing to do is to report kernel bugs
  against the package "linux".  That does not work.

  "ubuntu-bug linux" reports that linux is not installed!

  After some head-scratching I tried "ubuntu-bug linux-image", that also
  failed.  It did finally work with "ubuntu-bug linux-image-generic",
  but that is not an obvious choice *and it is contrary to the
  instructions*.  The obvious choice was "ubuntu-bug kernel" (which I
  tried first) that also failed.

  So, I tried to report a bug against ubuntu-bug with "ubuntu-bug
  ubuntu-bug", not installed!  According to the web site
   ubuntu-bug does not belong to
  any package!  OK it is a link.  Try again with the real binary name;
  apport-bug is not installed either!

  If you want feedback from ordinary users, bugs in the bug reporting
  system are serious.

  When apport is given a name that is not a package name it could follow a few 
simple steps to at lest provide hints to user; 
  "ls -l $(which ubuntu-bug)" shows that it is a link, 
  "ls -l --dereference $(which ubuntu-bug)" shows what it links to, and
  "dpkg-query --search $(ls  --dereference $(which ubuntu-bug))" even reports 
"apport: /usr/bin/ubuntu-bug".  
  That would be a useful clue to most users.  Note, "dpkg-query --search 
ubuntu-bug" is less useful.  

  As for kernel bugs, it should at least behave as documented.  Please
  add an extra line of code so that as a special case both "ubuntu-bug
  linux" and "ubuntu-bug kernel" work.

  There have been many times that apport has stated that a bug could not
  be reported and I had believed that it was because there were non-
  standard packages installed, now I am not so sure.

  TIA

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.19.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb 28 13:06:32 2016
  InstallationDate: Installed on 2016-02-03 (24 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160202)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1578907] [NEW] pulseaudio fills my logs

2016-05-05 Thread Seth Arnold
Public bug reported:

I have a few hundred thousand of these entries in my /var/log/syslog:

May  5 18:05:34 hunt pulseaudio[15247]: [pulseaudio] main.c: Module load failed.
May  5 18:05:34 hunt pulseaudio[15247]: [pulseaudio] main.c: Failed to 
initialize daemon.
May  5 18:05:34 hunt pulseaudio[15244]: [pulseaudio] main.c: Daemon startup 
failed.
May  5 18:05:35 hunt pulseaudio[15251]: [pulseaudio] module-udev-detect.c: 
Failed to scan for devices.
May  5 18:05:35 hunt pulseaudio[15251]: [pulseaudio] module.c: Failed to load 
module "module-udev-detect" (argument: ""): initialization failed.

This is likely to be related to my 14.04 LTS to 16.04 LTS upgrade, which I did 
a few days ago:
$ ls -lh sys*
-rw-r- 1 syslog adm   35M May  5 21:00 syslog
-rw-r- 1 syslog adm   61M May  5 07:35 syslog.1
-rw-r- 1 syslog adm  3.2M May  4 07:35 syslog.2.gz
-rw-r- 1 syslog adm  3.1M May  3 07:35 syslog.3.gz
-rw-r- 1 syslog adm  2.8M May  2 07:35 syslog.4.gz
-rw-r- 1 syslog adm  3.5M May  1 07:35 syslog.5.gz
-rw-r- 1 syslog adm   77K Apr 30 01:04 syslog.6.gz
-rw-r- 1 syslog adm   11K Apr 29 07:57 syslog.7.gz

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Thu May  5 20:58:43 2016
InstallationDate: Installed on 2012-10-18 (1295 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-04-30 (5 days ago)
dmi.bios.date: 09/13/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G4ET62WW (2.04 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2359CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG4ET62WW(2.04):bd09/13/2012:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2359CTO
dmi.product.version: ThinkPad T530
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug xenial

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

Title:
  pulseaudio fills my logs

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a few hundred thousand of these entries in my /var/log/syslog:

  May  5 18:05:34 hunt pulseaudio[15247]: [pulseaudio] main.c: Module load 
failed.
  May  5 18:05:34 hunt pulseaudio[15247]: [pulseaudio] main.c: Failed to 
initialize daemon.
  May  5 18:05:34 hunt pulseaudio[15244]: [pulseaudio] main.c: Daemon startup 
failed.
  May  5 18:05:35 hunt pulseaudio[15251]: [pulseaudio] module-udev-detect.c: 
Failed to scan for devices.
  May  5 18:05:35 hunt pulseaudio[15251]: [pulseaudio] module.c: Failed to load 
module "module-udev-detect" (argument: ""): initialization failed.

  This is likely to be related to my 14.04 LTS to 16.04 LTS upgrade, which I 
did a few days ago:
  $ ls -lh sys*
  -rw-r- 1 syslog adm   35M May  5 21:00 syslog
  -rw-r- 1 syslog adm   61M May  5 07:35 syslog.1
  -rw-r- 1 syslog adm  3.2M May  4 07:35 syslog.2.gz
  -rw-r- 1 syslog adm  3.1M May  3 07:35 syslog.3.gz
  -rw-r- 1 syslog adm  2.8M May  2 07:35 syslog.4.gz
  -rw-r- 1 syslog adm  3.5M May  1 07:35 syslog.5.gz
  -rw-r- 1 syslog adm   77K Apr 30 01:04 syslog.6.gz
  -rw-r- 1 syslog adm   11K Apr 29 07:57 syslog.7.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu May  5 20:58:43 2016
  InstallationDate: Installed on 2012-10-18 (1295 days ago)
  InstallationMedia: 

[Touch-packages] [Bug 1575572] Re: apache2 fails to start if installed via cloud config (on Xenial)

2016-05-05 Thread Martin Pitt
systemd upstream report: https://github.com/systemd/systemd/issues/3177

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => Triaged

** Changed in: systemd (Ubuntu)
   Importance: High => Low

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

Title:
  apache2 fails to start if installed via cloud config (on Xenial)

Status in init-system-helpers package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Triaged
Status in init-system-helpers source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Won't Fix
Status in systemd package in Debian:
  Confirmed

Bug description:
  Using the following cloud config, apache2 will fail to start on
  installation on Xenial:

  #cloud-config
  packages:
  - apache2

  See for example:

  $ gcloud compute instances create xenial-$(date +%y%m%d-%H%M) --image 
ubuntu-1604-xenial-v20160420c --image-project ubuntu-os-cloud 
--metadata-from-file user-data=cloud-config
  NAMEZONEMACHINE_TYPE   PREEMPTIBLE  INTERNAL_IP  
EXTERNAL_IPSTATUS
  xenial-160427-1050  europe-west1-d  n1-standard-1   10.240.0.7   
104.155.86.94  RUNNING

  $ ssh ubuntu@104.155.86.94 systemctl status apache2.service
  ● apache2.service - LSB: Apache2 web server
     Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
    Drop-In: /lib/systemd/system/apache2.service.d
     └─apache2-systemd.conf
     Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)

  Related Bugs:
   * bug 1576692: [cloud-init] fully support package installation in systemd

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

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


[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

2016-05-05 Thread Martin Pitt
> "* On shutdown, unmount /tmp before disabling swap. (Closes: #788303)"

This fix is in xenial-proposed now, for the record.

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This bug is resolved.  Do not follow up to this bug.  Shutdown bugs
  are specific to the software installed and its configuration.  If you
  are experiencing a shutdown hang, please file a separate bug report
  and follow the debugging instructions described in the "Debugging
  boot/shutdown problems" section of
  /usr/share/doc/systemd/README.Debian.gz to check if there are any
  hanging jobs at shutdown. Capturing a screen photo of "journalctl -b"
  in the rescue shell might be enlightening.

  [Original report]
  I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth 
shutdown screen.  Hitting esc to reveal the console showed a normal set of 
shutdown messages, ending with 'Reached target Shutdown' (paraphrased from 
memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

2016-05-05 Thread vik
Unfortunately the sticker has rubbed off; why would it be any different
to the DMI data?

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

Title:
  Laptop sometimes doesn't detect external monitor when docked

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when
  docked with a Onelink Pro dock. Problem has also occurred on a non-Pro
  OneLink dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
  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: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
  InstallationDate: Installed on 2015-12-02 (153 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20C0S1CWAU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
  dmi.bios.date: 01/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET48WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S1CWAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S1CWAU
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 08:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Touch-packages] [Bug 1572004] Re: pcscd consumes 100% CPU

2016-05-05 Thread Luke Faraone
*** This bug is a duplicate of bug 1551897 ***
https://bugs.launchpad.net/bugs/1551897

** This bug has been marked a duplicate of bug 1551897
   Excessive CPU utilization

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

Title:
  pcscd consumes 100% CPU

Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-lite package in Debian:
  Fix Released

Bug description:
  After upgrading to 16.04, pcscd process is stuck at using 100% CPU.

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

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


[Touch-packages] [Bug 1507190] Re: Disconnect Smartcard reader from USB causes pscd to crash

2016-05-05 Thread Luke Faraone
** 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 pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1507190

Title:
  Disconnect Smartcard reader from USB causes pscd to crash

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  PCSC works corectly with Reiner SCT cardreader and Moneyplex. Regular
  crashes however when application is shutdown or cardreader unplugged,

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: pcscd 1.8.14-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/sbin/pcscd': free(): corrupted unsorted 
chunks: 0x014d59a0 ***
  Date: Thu Oct 15 14:46:33 2015
  ExecutablePath: /usr/sbin/pcscd
  InstallationDate: Installed on 2012-08-21 (1152 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdline: /usr/sbin/pcscd --foreground --auto-exit
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: pcsc-lite
  StacktraceTop:
   select () at ../sysdeps/unix/syscall-template.S:81
   ?? ()
   ?? ()
   __libc_start_main (main=0x402f60, argc=3, argv=0x7ffc375ce0b8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc375ce0a8) at libc-start.c:289
   _start ()
  Title: pcscd assert failure: *** Error in `/usr/sbin/pcscd': free(): 
corrupted unsorted chunks: 0x014d59a0 ***
  UpgradeStatus: Upgraded to wily on 2015-10-03 (14 days ago)
  UserGroups:

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

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


[Touch-packages] [Bug 1554570] Re: package libpcsclite1 1.8.14-1ubuntu1 [modified: usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc

2016-05-05 Thread Luke Faraone
** Changed in: pcsc-lite (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libpcsclite1 1.8.14-1ubuntu1 [modified:
  usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different
  from other instances of package libpcsclite1:i386

Status in pcsc-lite package in Ubuntu:
  Incomplete

Bug description:
  I was trying to install a smart card reader to a digital certificate.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libpcsclite1 1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   libpcsclite1: Install
   libpcsclite1: Configure
   libpcsclite1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Mar  8 12:13:18 2016
  Dependencies:
   gcc-5-base 5.2.1-22ubuntu2
   libc6 2.21-0ubuntu4.1
   libgcc1 1:5.2.1-22ubuntu2
  DpkgTerminalLog:
   Preparing to unpack .../libpcsclite1_1.8.14-1ubuntu1_i386.deb ...
   Unpacking libpcsclite1:i386 (1.8.14-1ubuntu1) over (1.8.5-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libpcsclite1_1.8.14-1ubuntu1_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
  DuplicateSignature: package:libpcsclite1:1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from 
other instances of package libpcsclite1:i386
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: pcsc-lite
  Title: package libpcsclite1 1.8.14-1ubuntu1 [modified: 
usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', 
which is different from other instances of package libpcsclite1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1578884] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()

2016-05-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1544627 ***
https://bugs.launchpad.net/bugs/1544627

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 #1544627, 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/1578884/+attachment/4656803/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1544627
   systemd-udevd crashed with SIGABRT in __open_nocancel()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-udevd crashed with SIGABRT in __open_nocancel()

Status in systemd package in Ubuntu:
  New

Bug description:
  When you finish recording a boot disk with the utility of ubuntu crash

  Al terminar de grabar un disco de arranque con la utilidad de ubuntu
  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 21:14:04 2016
  ExecutablePath: /lib/systemd/systemd-udevd
  MachineType: Gigabyte Technology Co., Ltd. Z97MX-Gaming 5
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=es_EC.UTF-8
   LANGUAGE=es_EC:es
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=0adadaa4-4c91-4bce-bf61-8fc9d8905284 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __open_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-udevd crashed with SIGABRT in __open_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97MX-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97MX-Gaming5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97MX-Gaming 5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1578334] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from 14.04.4 to 16.04 LTS failed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed May  4 11:51:36 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-11-12 (173 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-05-04 (0 days ago)

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

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


[Touch-packages] [Bug 1250109] Re: Please use dpkg-triggers

2016-05-05 Thread Phillip Susi
It seems that there were other changes to grub that require the fix to
be adjusted to apply properly, and nobody has done so yet ( I've been
rather busy at work and with second child lately, but still hope to
update this soon ).

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

Title:
  Please use dpkg-triggers

Status in grub2 package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

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

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


[Touch-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

2016-05-05 Thread kevin gunn
** Changed in: canonical-devices-system-image
Milestone: 11 => backlog

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

Title:
  libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  Duplicate bug reports now show Unity8 is another such client suffering
  from this crash. It's occurring on phones in the wild.

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

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


[Touch-packages] [Bug 1556763] Re: [regression] [OTA-10] Touch scrolling the dash is stuttery again, and lag throughout Unity8 higher than it was in OTA-9

2016-05-05 Thread Daniel van Vugt
Note the fix is not in Ubuntu proper yet. It's only in PPAs right now...

https://launchpad.net/ubuntu/+source/unity8

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

Title:
  [regression] [OTA-10] Touch scrolling the dash is stuttery again, and
  lag throughout Unity8 higher than it was in OTA-9

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

Bug description:
  Regression in OTA-10: Touch scrolling the dash is stuttery again, and
  lag higher than it was.

  Test case 1: Scroll the dash smoothly with a finger.
  Expected: Dash scrolls smoothly.
  Observed: Dash often jumps abruptly.

  Test case 2: Pull down/up the notification bar quickly with a finger.
  Expected: It closely matches the finger position.
  Observed: It's a long way behind.

  These issues are so familiar, it's rather obviously a regression of
  bug 1486341. And I can see the required QML_NO_TOUCH_COMPRESSION=1 has
  gone missing too.

  $ system-image-cli -i
  current build number: 387
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2016-03-14 06:38:12
  version version: 387
  version ubuntu: 20160312
  version device: 20160304.2
  version custom: 20160312

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

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


[Touch-packages] [Bug 1578469] Re: Crashes in unity8 cause infinite restarts and/or a permanently black screen

2016-05-05 Thread Daniel van Vugt
I know we want Unity8 to respawn on occasional/rare crashes. But we need
a different plan for immediate start-up crashes... For those you need to
soon fall back to something else that will at least display a picture
(USC I guess).

Obeying a respawn limit of 10 or so would be a nice compromise I think.

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

Title:
  Crashes in unity8 cause infinite restarts and/or a permanently black
  screen

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Crashes in unity8 cause infinite restarts and/or a permanently black
  screen.

  As experienced in bug 1578462.

  I guess the problem is the 'respawn' keyword in:
 /usr/share/upstart/sessions/unity8.conf
  [http://upstart.ubuntu.com/cookbook/#respawn]

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

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


[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame

2016-05-05 Thread Daniel van Vugt
Brandon: This actually only happens once or twice a week or so for the
rest of us. If your branch hits it more often that might indicate that
branch needs fixing.

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

Title:
  CI failure in TestClientInput.receives_one_touch_event_per_frame

Status in Mir:
  Triaged
Status in mir package in Ubuntu:
  Invalid

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull

  02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
  02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
  02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy 
(version 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
  02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display 
configuration:
  02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
  02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 
60.00Hz
  02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
  02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: 
mir:stub-input (version: 0.22.0)
  02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:44 11: Stack trace:
  02:44:44 11: 
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
 Failure
  02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 
0.2400953674316, which exceeds 0.2f, where
  02:44:44 11: 1.0f evaluates to 1,
  02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, 
and
  02:44:44 11: 0.2f evaluates to 0.2000298023224.
  02:44:44 11: 
  02:44:44 11: GMOCK WARNING:
  02:44:44 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: 
  02:44:45 11: GMOCK WARNING:
  02:44:45 11: Uninteresting mock function call - returning directly.
  02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, 
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
  02:44:45 11: Stack trace:
  02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
  02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame 
(4083 ms)

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

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


[Touch-packages] [Bug 1206164] Re: /etc/network/if-up.d/ntpdate does not detach correctly

2016-05-05 Thread Bug Watch Updater
** Changed in: ntp
   Status: Unknown => New

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

Title:
  /etc/network/if-up.d/ntpdate does not detach correctly

Status in NTP:
  New
Status in ntp package in Ubuntu:
  Triaged

Bug description:
  It seems that the intent of /etc/network/if-up.d/ntpdate is to
  background itself, as it creates a subshell with &.

  As reported in bug 1202758, this doesn't seem to work correctly.  That
  doesn't close the file descriptors.  As a result, if something is
  waiting on the output of 'ifup', it will sit and wait until ntpdate is
  finished.

  Example:
  $ time sudo sh -c 'o=$(sh -c "ifdown eth0 ; ifup eth0" 2>&1) ; echo $o'

  If we change the way it detaches itself to close stdout, stdderr, and
  stdin, then we're fine.

  I'm reporting this, but I'm not sure how much of a real problem it is.  As if 
th
  e command sends stdin and stdout to /dev/null, then debugging its output 
would b
  e more difficult.

  Example diff:
  $ diff -u /etc/network/if-up.d/ntpdate.dist /etc/network/if-up.d/ntpdate
  --- /etc/network/if-up.d/ntpdate.dist  2013-07-29 15:47:54.242781947 +
  +++ /etc/network/if-up.d/ntpdate 2013-07-29 15:48:06.946781947 +
  @@ -56,4 +56,4 @@
 lockfile-remove $LOCKFILE
   fi

  -) &
  +) /dev/null 2>&1 &

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ntpdate 1:4.2.6.p5+dfsg-2ubuntu2
  ProcVersionSignature: User Name 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Mon Jul 29 15:32:30 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.network.if.up.d.ntpdate: 2013-07-29T15:32:03.567775

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

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


[Touch-packages] [Bug 1577760] Re: Screen Display 'Apply' fails

2016-05-05 Thread Christopher M. Penalver
** Tags added: bios-outdated-1.21

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

Title:
  Screen Display 'Apply' fails

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When I click on the 'Apply' button of the 'Screen Display' utility
  (without setting anything), I get an error dialog :

  "Failed to apply configuration: %s
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.gnome.SettingsDaemon.XRANDR_2' on object at path 
/org/gnome/SettingsDaemon/XRANDR"

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  It is the 'Screen Display' utility on the 'System Settings' tool - I
  don't know how to find out what binary that is or the package it is
  in.

  3) What you expected to happen

  I expect to be able to configure multiple monitors - though it fails
  even when I have none connected.

  4) What happened instead

  I get the above error message any time I press 'Apply'.

  I've had this ever since upgrading to 16.04.

  In case this is useful :

  [~]$ lspci
  00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated 
Graphics (rev 09)
  00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
  00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI 
Controller (rev 03)
  00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI 
Controller #1 (rev 03)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) 
I218-LM (rev 03)
  00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#6 (rev e3)
  00:1c.1 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port 
#3 (rev e3)
  00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI 
Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller 
[AHCI Mode] (rev 03)
  00:1f.3 SMBus: Intel Corporation Wildcat Point-LP SMBus Controller (rev 03)
  00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP 
Thermal Management Controller (rev 03)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
  [~]$ 

  It is a Lenovo X250 with a docking station (though it doesn't make any
  difference if the docking station is used or not).

  IMO, this isn't related to graphics specifically...more to do with
  some DBus service...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Tue May  3 13:20:37 2016
  DistUpgraded: 2016-04-22 10:05:12,580 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2226]
  InstallationDate: Installed on 2015-05-20 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20CM001QUK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (11 days ago)
  dmi.bios.date: 04/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET33W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CM001QUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET33W(1.12):bd04/06/2015:svnLENOVO:pn20CM001QUK:pvrThinkPadX250:rvnLENOVO:rn20CM001QUK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CM001QUK
  dmi.product.version: ThinkPad X250
  

[Touch-packages] [Bug 1578877] [NEW] Multitude of issues after upgrading to 16.04

2016-05-05 Thread Steve Par
Public bug reported:

Ever since upgrading to 16.04, Rhythmbox GUI fails to open.  Also, if I
open User accounts under System Settings nothing opens, but after I
can't close the System Settings window..

And here's a sample of auth.log entries:

May  6 07:32:03 steven-OptiPlex-7020 lightdm: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
May  6 07:32:03 steven-OptiPlex-7020 lightdm: PAM adding faulty module: 
pam_kwallet.so
May  6 07:32:03 steven-OptiPlex-7020 lightdm: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
May  6 07:32:03 steven-OptiPlex-7020 lightdm: PAM adding faulty module: 
pam_kwallet5.so
May  6 07:32:03 steven-OptiPlex-7020 lightdm: 
pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
May  6 07:32:03 steven-OptiPlex-7020 systemd-logind[1004]: New session c1 of 
user lightdm.
May  6 07:32:03 steven-OptiPlex-7020 systemd: pam_unix(systemd-user:session): 
session opened for user lightdm by (uid=0)
May  6 07:32:03 steven-OptiPlex-7020 lightdm: 
pam_ck_connector(lightdm-greeter:session): nox11 mode, ignoring PAM_TTY :0
May  6 07:32:05 steven-OptiPlex-7020 lightdm: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
May  6 07:32:05 steven-OptiPlex-7020 lightdm: PAM adding faulty module: 
pam_kwallet.so
May  6 07:32:05 steven-OptiPlex-7020 lightdm: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
May  6 07:32:05 steven-OptiPlex-7020 lightdm: PAM adding faulty module: 
pam_kwallet5.so
May  6 07:32:05 steven-OptiPlex-7020 lightdm: pam_succeed_if(lightdm:auth): 
requirement "user ingroup nopasswdlogin" not met by user "steven"
May  6 07:32:15 steven-OptiPlex-7020 lightdm: 
pam_unix(lightdm-greeter:session): session closed for user lightdm
May  6 07:32:15 steven-OptiPlex-7020 lightdm: pam_unix(lightdm:session): 
session opened for user steven by (uid=0)
May  6 07:32:15 steven-OptiPlex-7020 systemd-logind[1004]: New session c2 of 
user steven.
May  6 07:32:15 steven-OptiPlex-7020 systemd: pam_unix(systemd-user:session): 
session opened for user steven by (uid=0)
May  6 07:32:15 steven-OptiPlex-7020 lightdm: 
pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0
May  6 07:32:18 steven-OptiPlex-7020 gnome-keyring-daemon[1887]: The PKCS#11 
component was already initialized
May  6 07:32:18 steven-OptiPlex-7020 gnome-keyring-daemon[1887]: The Secret 
Service was already initialized
May  6 07:32:18 steven-OptiPlex-7020 gnome-keyring-daemon[1887]: The SSH agent 
was already initialized
May  6 07:32:19 steven-OptiPlex-7020 polkitd(authority=local): Registered 
Authentication Agent for unix-session:c2 (system bus name :1.79 
[/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path 
/org/gnome/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8)
May  6 07:32:31 steven-OptiPlex-7020 dbus[949]: [system] Failed to activate 
service 'org.bluez': timed out
May  6 07:34:01 steven-OptiPlex-7020 dbus[949]: [system] Failed to activate 
service 'org.bluez': timed out
May  6 07:34:03 steven-OptiPlex-7020 systemd-logind[1004]: Removed session c1.
May  6 07:34:04 steven-OptiPlex-7020 systemd: pam_unix(systemd-user:session): 
session closed for user lightdm

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May  6 08:00:07 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-02-06 (89 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: lightdm
UpgradeStatus: Upgraded to xenial on 2016-04-21 (14 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Multitude of issues after upgrading to 16.04

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ever since upgrading to 16.04, Rhythmbox GUI fails to open.  Also, if
  I open User accounts under System Settings nothing opens, but after I
  can't close the System Settings window..

  And here's a sample of auth.log entries:

  May  6 07:32:03 steven-OptiPlex-7020 lightdm: PAM unable to 
dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object 
file: No such file or directory
  May  6 07:32:03 steven-OptiPlex-7020 lightdm: PAM adding faulty module: 
pam_kwallet.so
  May  6 07:32:03 steven-OptiPlex-7020 lightdm: PAM unable to 
dlopen(pam_kwallet5.so): 

[Touch-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

2016-05-05 Thread Christopher M. Penalver
vik, thank you for reporting this and helping make Ubuntu better.

Could you please provide the full computer serial number and MTM as
noted on the sticker of the computer itself (not from the Bug
Description)?

** Description changed:

- Clone of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
- intel/+bug/1552040
- 
- Lenovo Thinkpad Yoga S1, with a Onelink Pro dock (problem has also
- occurred on a OneLink (non-Pro) dock).
+ Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when
+ docked with a Onelink Pro dock. Problem has also occurred on a non-Pro
+ OneLink dock.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks
  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: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
-  virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
+  virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
+  virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
  InstallationDate: Installed on 2015-12-02 (153 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20C0S1CWAU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
  dmi.bios.date: 01/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET48WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S1CWAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S1CWAU
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 08:27:55 2016
  xserver.configfile: default
  xserver.errors:
-  Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
-  Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
-  Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
+  Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
+  Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
+  Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id1079 
-  vendor LGD
+  product id1079
+  vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Laptop sometimes doesn't detect external monitor when docked

Status in xorg package in Ubuntu:
  

[Touch-packages] [Bug 1531622] Re: default config still using a legacy keyword: KLogPermitNonKernelFacility

2016-05-05 Thread SunBear
I can confirm this also happens in my Ubuntu 16.04 LTS install.

May  6 08:20:41 Eliot rsyslogd-: command
'KLogPermitNonKernelFacility' is currently not permitted - did you
already set it via a RainerScript command (v6+ config)? [v8.16.0 try
http://www.rsyslog.com/e/ ]

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

Title:
  default config still using a legacy keyword:
  KLogPermitNonKernelFacility

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  /etc/rsyslog.conf contains:

$KLogPermitNonKernelFacility on

  But this no longer supported and trigger this log message:

   Jan  5 08:56:16 simon-laptop rsyslogd-: command
  'KLogPermitNonKernelFacility' is currently not permitted - did you
  already set it via a RainerScript command (v6+ config)? [v8.14.0 try
  http://www.rsyslog.com/e/ ]

  Error  is described as "legacy parameter no longer permitted".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.14.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan  6 15:47:15 2016
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

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

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


[Touch-packages] [Bug 1578868] [NEW] /usr/bin/online-accounts-ui:11:QWeakPointer:QPointer:QPointer:Accounts::AccountService::account:OnlineAccounts::AccountServiceModel::data

2016-05-05 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding ubuntu-system-settings-online-accounts.  This problem was most
recently seen with version 0.7+16.04.20151126-0ubuntu1, the problem page
at
https://errors.ubuntu.com/problem/43654dc3f73a8340d340d895bff384f5111cb7a4
contains more details.

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid xenial

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

Title:
  /usr/bin/online-accounts-
  
ui:11:QWeakPointer:QPointer:QPointer:Accounts::AccountService::account:OnlineAccounts::AccountServiceModel::data

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-system-settings-online-accounts.  This problem was
  most recently seen with version 0.7+16.04.20151126-0ubuntu1, the
  problem page at
  https://errors.ubuntu.com/problem/43654dc3f73a8340d340d895bff384f5111cb7a4
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1578868/+subscriptions

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


Re: [Touch-packages] [Bug 1577733] Re: packagelibvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки1

2016-05-05 Thread Vladimir Gorelov
Moving didn't help untill reboot.
Now main apt command executed fine.
Thanks!
6 мая 2016 г. 5:05 AM пользователь "Serge Hallyn" <
1577...@bugs.launchpad.net> написал:

> Hi,
>
> does 'sudo lsof' show any results for those files?
>
> If not, I guess try simply moving them:
>
> sudo mv /etc/group+ /etc/group+.bak
> sudo mv /etc/group- /etc/group-.bak
> sudo mv /etc/gshadow- /etc/gshadow-.bak
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577733
>
> Title:
>   package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade:
>   подпроцесс установлен сценарий post-installation возвратил код ошибки
>   1
>
> Status in libvirt package in Ubuntu:
>   Incomplete
> Status in shadow package in Ubuntu:
>   Incomplete
>
> Bug description:
>   sudo apt-get install gnome-boxes then oops
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 14.04
>   Package: libvirt-bin 1.2.2-0ubuntu13.1.17
>   ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
>   Uname: Linux 3.13.0-85-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.14.1-0ubuntu3.19
>   Architecture: amd64
>   Date: Tue May  3 16:58:15 2016
>   ErrorMessage: подпроцесс установлен сценарий post-installation возвратил
> код ошибки 1
>   InstallationDate: Installed on 2014-09-01 (609 days ago)
>   InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64
> (20140417)
>   ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic.efi.signed
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
>   SourcePackage: libvirt
>   Title: package libvirt-bin 1.2.2-0ubuntu13.1.17 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/libvirt/+bug/1577733/+subscriptions
>

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

Title:
  package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in libvirt package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install gnome-boxes then oops

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libvirt-bin 1.2.2-0ubuntu13.1.17
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue May  3 16:58:15 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2014-09-01 (609 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.2.2-0ubuntu13.1.17 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/libvirt/+bug/1577733/+subscriptions

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


[Touch-packages] [Bug 1519120] Re: Xenial: VLAN interfaces don't work until after a reboot

2016-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Xenial: VLAN interfaces don't work until after a reboot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I tried to use the network manager UI to define a VLAN interface, and
  nothing happened. There are a few bugs here:

  (1) When creating a VLAN interface through the UI, the "vlan interface
  name" must be filled in. This should just default to ., rather than being a required field. (I typed in "vlan100"
  to get the "Save" button to activate.)

  (2) After creating my VLAN interface, nothing happened. No new
  interface appeared. I then realized that I had not installed the
  "vlan" package, and assumed that NetworkManager therefore could not
  complete configuration of the interface.

  (3) After installing the 'vlan' package (and then telling
  NetworkManager to disconnect and reconnect my Ethernet interface from
  the UI, just for good measure), still no VLAN interfaces were present
  on my system.

  I also tried editing the VLAN interface in the UI, and specifying
  "enp4s0f1.100", but still no VLAN interface came online.

  # apt-cache policy network-manager
  network-manager:
Installed: 1.0.4-0ubuntu6
Candidate: 1.0.4-0ubuntu6
Version table:
   *** 1.0.4-0ubuntu6 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy vlan
  vlan:
Installed: 1.9-3.2ubuntu1
Candidate: 1.9-3.2ubuntu1
Version table:
   *** 1.9-3.2ubuntu1 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Touch-packages] [Bug 1578865] [NEW] Xorg freeze

2016-05-05 Thread Ahmed Noor Kader Mustajir Md Eusoff
Public bug reported:

during usage, the screen freeze and need to hard reboot. before it
happen, the system busy with the application running

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
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: Fri May  6 07:49:52 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: This is the first time
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] [1043:83a4]
InstallationDate: Installed on 2016-05-05 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 002 Device 002: ID 1a2c:0027 China Resource Semico Co., Ltd 
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/12/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1004
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4N68T-M
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.:bvr1004:bd06/12/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri May  6 07:16:51 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB USB Keykoard KEYBOARD, id 8
 inputUSB USB Keykoard KEYBOARD, id 9
 inputLogitech USB Optical Mouse MOUSE, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  during usage, the screen freeze and need to hard reboot. before it
  happen, the system busy with the application running

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Fri May  6 07:49:52 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 

[Touch-packages] [Bug 1578861] [NEW] /usr/bin/messaging-app:11:std::string::_Rep::_S_empty_rep_storage:mir::client::make_protobuf_object:mir::client::rpc::MirProtobufRpcChannel::on_data_available:oper

2016-05-05 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding messaging-app.  This problem was most recently seen with
version 0.1+15.04.20160504-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/a3fdd0aba9c8aba52905db42b196db60f3bf8e25
contains more details.

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


** Tags: vivid

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

Title:
  /usr/bin/messaging-
  
app:11:std::string::_Rep::_S_empty_rep_storage:mir::client::make_protobuf_object:mir::client::rpc::MirProtobufRpcChannel::on_data_available:operator:_M_invoke

Status in messaging-app package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding messaging-app.  This problem was most recently seen with
  version 0.1+15.04.20160504-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/a3fdd0aba9c8aba52905db42b196db60f3bf8e25
  contains more details.

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

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


[Touch-packages] [Bug 1313732] Re: Impossible to report a bug about samba-tool without answering inadequate questions

2016-05-05 Thread Travisgevans
I hit this today, and it absolutely infuriates me. Indeed, the questions
have either no valid answers or ask things I could not possibly know.
And I consider myself a reasonably experienced user. All I know is that
I tried to apply security updates and it told me something happened. It
withheld all the details until I gave up on the questions and cancelled,
and the whole thing closed **without once giving me a single clue what
the problem was**. I still have no idea what issue it was trying to
report or whether Samba is now usable, etc.

I really hate useless messages that say “an error occurred” with no
details, but refusing to give any information at all while
simultaneously demanding it from the user takes the cake. I am amazed to
find something so user-hostile in a bug-reporting tool. This isn't a
good way to get bug reports, and it probably isn't a very good way to
encourage users *not* to simply give up and permanently disable the bug
reporter *and* system updates altogether!

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

Title:
  Impossible to report a bug about samba-tool without answering
  inadequate questions

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Trying to report a bug about samba I am first asked about if:
  *** How would you best describe your setup?
  Auswahl:
1: I am running a Windows File Server.
2: I am connecting to a Windows File Server.
A: Abbruch
  Bitte wählen Sie (1/2/A):

  What shall I answer? 1 - isn't right, 2 - isn't either. A? Bailing out
  because it isn't thought of other possibilities??!

  
  I choose 1, because if all answers are wrong it seems not to matter how wrong 
they are! Next question:
  *** Did this used to work properly with a previous release?
  Was möchten Sie tun? Ihre Möglichkeiten sind:
Y: Yes
N: No
A: Abbruch
  Bitte wählen Sie (Y/N/A):

  Wow! I do not konw if it did work or not - simply because I did not
  use it before! Fine. Just assume Yes and answer "Y"

  
  Next question:
  *** Which clients are failing to connect?
  Auswahl:
1: Windows
2: Ubuntu
3: Both
4: Other
A: Abbruch
  Bitte wählen Sie (1/2/3/4/A):

  I do not connect a client! So what?? Since I learned "A" isn't good
  trying "4".

  *** The contents of your /etc/samba/smb.conf file may help developers 
diagnose your bug more quickly. However, it may contain sensitive information.  
Do you want to include it in your bug report?
  Was möchten Sie tun? Ihre Möglichkeiten sind:
Y: Yes
N: No
A: Abbruch
  Bitte wählen Sie (Y/N/A):

  Wow! The first question being concrete. I dislike to include this file
  without changing certain parts ... so 'N'.

  *** The contents of your /var/log/samba/log.smbd and /var/log/samba/log.nmbd 
may help developers diagnose your bug more quickly. However, it may contain 
sensitive information. Do you want to include it in your bug report?
  Was möchten Sie tun? Ihre Möglichkeiten sind:
Y: Yes
N: No
A: Abbruch
  Bitte wählen Sie (Y/N/A):

  Same for the logs. Again 'N'.

  These questions are only helpful if there are connection problems, but
  they are not if there are other problems like not working samba-tool
  commands or else.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:106:101243:2014-04-25 09:55:06.734537444 +0200:2014-04-25 
11:11:09.272081356 +0200:/var/crash/_usr_sbin_samba_dnsupdate.0.crash
  Date: Mon Apr 28 12:05:46 2014
  InstallationDate: Installed on 2012-12-12 (501 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (440 days ago)

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

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


[Touch-packages] [Bug 1578032] Re: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-05-05 Thread toanGa
may i delete file user.rules in the folder /etc/ufw

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

Title:
  package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  when i start my computer,it happens the report problem,then i click it
  ,it show that

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue May  3 23:34:43 2016
  DpkgHistoryLog:
   Start-Date: 2016-05-03  23:34:26
   Commandline: aptdaemon role='role-commit-packages' sender=':1.107'
   Upgrade: google-chrome-stable:amd64 (50.0.2661.86-1, 50.0.2661.94-1), 
ubuntu-core-launcher:amd64 (1.0.27, 1.0.27.1)
  DuplicateSignature:
   Setting up ufw (0.35-0ubuntu2) ...
   mv: '/lib/ufw/user.rules' and '/etc/ufw/user.rules' are the same file
   dpkg: error processing package ufw (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-30 (186 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: ufw
  Title: package ufw 0.35-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (12 days ago)
  mtime.conffile..etc.rsyslog.d.20-ufw.conf: 2015-09-09T03:01:36

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

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


[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install

2016-05-05 Thread snerge
glad it worked for you both as it did for me !

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

Title:
  Totem can't play H264 on fresh 16.04 beta install

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Totem can't play neither find the correct codec to play H264 *.mp4
  video in last 16.04 beta.

  Terminal says :

  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile)
  decoder|decoder-video/x-h264, stream-format=(string)avc,
  alignment=(string)au, level=(string)4, profile=(string)main, max-
  input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile)
  decoder)

  
  Totem tries to find the correct codec but fails, see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 15:51:47 2016
  InstallationDate: Installed on 2016-03-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1562875/+subscriptions

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


[Touch-packages] [Bug 1313732] Re: Impossible to report a bug about samba-tool without answering inadequate questions

2016-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Impossible to report a bug about samba-tool without answering
  inadequate questions

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Trying to report a bug about samba I am first asked about if:
  *** How would you best describe your setup?
  Auswahl:
1: I am running a Windows File Server.
2: I am connecting to a Windows File Server.
A: Abbruch
  Bitte wählen Sie (1/2/A):

  What shall I answer? 1 - isn't right, 2 - isn't either. A? Bailing out
  because it isn't thought of other possibilities??!

  
  I choose 1, because if all answers are wrong it seems not to matter how wrong 
they are! Next question:
  *** Did this used to work properly with a previous release?
  Was möchten Sie tun? Ihre Möglichkeiten sind:
Y: Yes
N: No
A: Abbruch
  Bitte wählen Sie (Y/N/A):

  Wow! I do not konw if it did work or not - simply because I did not
  use it before! Fine. Just assume Yes and answer "Y"

  
  Next question:
  *** Which clients are failing to connect?
  Auswahl:
1: Windows
2: Ubuntu
3: Both
4: Other
A: Abbruch
  Bitte wählen Sie (1/2/3/4/A):

  I do not connect a client! So what?? Since I learned "A" isn't good
  trying "4".

  *** The contents of your /etc/samba/smb.conf file may help developers 
diagnose your bug more quickly. However, it may contain sensitive information.  
Do you want to include it in your bug report?
  Was möchten Sie tun? Ihre Möglichkeiten sind:
Y: Yes
N: No
A: Abbruch
  Bitte wählen Sie (Y/N/A):

  Wow! The first question being concrete. I dislike to include this file
  without changing certain parts ... so 'N'.

  *** The contents of your /var/log/samba/log.smbd and /var/log/samba/log.nmbd 
may help developers diagnose your bug more quickly. However, it may contain 
sensitive information. Do you want to include it in your bug report?
  Was möchten Sie tun? Ihre Möglichkeiten sind:
Y: Yes
N: No
A: Abbruch
  Bitte wählen Sie (Y/N/A):

  Same for the logs. Again 'N'.

  These questions are only helpful if there are connection problems, but
  they are not if there are other problems like not working samba-tool
  commands or else.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CrashReports: 640:0:106:101243:2014-04-25 09:55:06.734537444 +0200:2014-04-25 
11:11:09.272081356 +0200:/var/crash/_usr_sbin_samba_dnsupdate.0.crash
  Date: Mon Apr 28 12:05:46 2014
  InstallationDate: Installed on 2012-12-12 (501 days ago)
  InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release 
amd64 (20120817.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2013-02-11 (440 days ago)

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

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


Re: [Touch-packages] [Bug 1577733] Re: packagelibvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки1

2016-05-05 Thread Serge Hallyn
Hi,

does 'sudo lsof' show any results for those files?

If not, I guess try simply moving them:

sudo mv /etc/group+ /etc/group+.bak
sudo mv /etc/group- /etc/group-.bak
sudo mv /etc/gshadow- /etc/gshadow-.bak

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

Title:
  package libvirt-bin 1.2.2-0ubuntu13.1.17 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in libvirt package in Ubuntu:
  Incomplete
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  sudo apt-get install gnome-boxes then oops

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libvirt-bin 1.2.2-0ubuntu13.1.17
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  Uname: Linux 3.13.0-85-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue May  3 16:58:15 2016
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2014-09-01 (609 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-85-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: libvirt
  Title: package libvirt-bin 1.2.2-0ubuntu13.1.17 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/libvirt/+bug/1577733/+subscriptions

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


[Touch-packages] [Bug 1578807] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-05-05 Thread Martin Pitt
*** This bug is a duplicate of bug 1560797 ***
https://bugs.launchpad.net/bugs/1560797

** This bug has been marked a duplicate of bug 1560797
   apt does not configure Pre-Depends: before depending package

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

Title:
  package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  System update failling.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Apr 26 12:22:51 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-12-05 (152 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (9 days ago)

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

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


[Touch-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2016-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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


[Touch-packages] [Bug 1578461] Re: Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']

2016-05-05 Thread Michał Sawicz
Fix coming in https://requests.ci-train.ubuntu.com/#/ticket/1370

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

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

Title:
  Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*)
  all crash on start-up in libhybris [linker.c:27: android_dlopen:
  Assertion `0' failed.']

Status in Mir:
  New
Status in Mir 0.22 series:
  New
Status in Mir 0.23 series:
  New
Status in libhybris package in Ubuntu:
  In Progress
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Having mir-graphics-drivers-android9:amd64 installed prevents unity-
  system-compositor starting:

  [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.22.0)
  android_dlopen called but not implemented!
  unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed.

  which was caused by:

  sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay

  WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7
  FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11

  WORKAROUNDS:
   * Remove ppa:ci-train-ppa-service/stable-phone-overlay from your system to 
completely solve the problem; or
   * Don't use Unity8 -- other Mir servers will work after you remove package 
mir-graphics-drivers-android9:amd64 which is their last remaining dependency on 
libhybris.

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

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


[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install

2016-05-05 Thread Hamidreza Hanafi
@Snerge
Thanks. Now everything is working. please set it as solved.

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

Title:
  Totem can't play H264 on fresh 16.04 beta install

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Totem can't play neither find the correct codec to play H264 *.mp4
  video in last 16.04 beta.

  Terminal says :

  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile)
  decoder|decoder-video/x-h264, stream-format=(string)avc,
  alignment=(string)au, level=(string)4, profile=(string)main, max-
  input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile)
  decoder)

  
  Totem tries to find the correct codec but fails, see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 15:51:47 2016
  InstallationDate: Installed on 2016-03-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1562875/+subscriptions

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


[Touch-packages] [Bug 1578832] [NEW] package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-05-05 Thread Marcus
Public bug reported:

Tried to install ssh.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu May  5 23:29:32 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-05-01 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  Tried to install ssh.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May  5 23:29:32 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-01 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 75347] Re: ntp script steps time

2016-05-05 Thread ChristianEhrhardt
*** This bug is a duplicate of bug 1206164 ***
https://bugs.launchpad.net/bugs/1206164

Chasing down more bugs I came by recently there is a lot of pro/con
about this.

The Summary related to this bug is:
The general behavior is depending on the time difference.  If the time 
differences off a lot it (has to) step time, otherwise (which should be what 
happens) it drifts. It is considered valid configured time sources that a new 
change should not cause a huge new diff.

For environments where this "considered to be normal" case does not
apply we will provide an option to disable the auto-update. I'll dup
this (be aware that on recent releases one has to care about timedatectl
separately if that is used instead of ntpdate).

** This bug has been marked a duplicate of bug 1206164
   /etc/network/if-up.d/ntpdate does not detach correctly

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

Title:
  ntp script steps time

Status in ntp package in Ubuntu:
  Triaged

Bug description:
  Distro Release: Dapper
  Package: ntp

  Description:
  The clock of one of my routers running Dapper had bogus time (something that 
ntpd was slowly but steadily working on).  Then I added an interface and boom! 
the time was stepped.  OSPF went into an retarded state, loosing random routes 
and everything was going crazy.

  After the ordeal was over I found the /etc/network/if-up.d/ntpdate
  script, where time is stepped _every_ time interfaces go up/down.
  This is probably okay on a laptop or something, but it's madness to do
  so on a server.  I sure know OSPF isn't the only service that gets
  really confused when the clock leaps.

  There's actually a reason why the manual page of ntpdate says the
  following about the -b option:  «This option should be used when
  called from a startup file at boot time.»

  I've now deinstalled ntpdate (it served no purpose anyway since I have
  ntpd), but really, this package should not be part of the default
  server installation with this behaviour.

  DESIRED FIX:
  In my humble opinion use of the «-b» option should be dropped from server 
installs, or (even better) ntpdate should be run only as part of the bootup 
sequence, leaving clock synch to ntpd afterwards.

  Tore

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

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


[Touch-packages] [Bug 1558531] Re: Set up VPN page breaks navigation pattern

2016-05-05 Thread Selene Scriven
I personally don't care which style is used, but at the moment it's
still not consistent.  Here are the VPN and APN config screens.

** Attachment added: "vpn-apn-ui.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1558531/+attachment/4656648/+files/vpn-apn-ui.png

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

Title:
  Set up VPN page breaks navigation pattern

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Every page that I have come across in Ubuntu Touch apps, use a back
  header button to exit the page. The "Set up VPN" places the "Cancel"
  and "Ok" buttons at the bottom of the page which makes it confusing
  and undiscoverable for a user. To compound the issue, if the user
  panics and just closes the system settings app at that point, a VPN
  connection is still created (bug 1558530).

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

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


[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards

2016-05-05 Thread Paul M. Bendixen
Just another quick test
It seems when I use xinput (through gvim, the only way I can run commands in 
libertine)  The AltGr key registers as a normal alt key and doesn't get 
released for some reason.
Will post again when I have done a QML test

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

   - PC: Everything works perfect.
   - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú).

  Extra info:

  - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 
(http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2)
  - Ubuntu Desktop: 12.04
  - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305)

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

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


[Touch-packages] [Bug 1440373] Re: please build a python3-zeitgeist package and let zeitgeist depend on it

2016-05-05 Thread Khurshid Alam
How did this resolve this issue?
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1199221/comments/3

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

Title:
  please build a python3-zeitgeist package and let zeitgeist depend on
  it

Status in Zeitgeist Framework:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build a python3-zeitgeist package and let
  zeitgeist depend on it

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

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


[Touch-packages] [Bug 1199221] Re: Package zeitgeist-python for python3 aka make package python3-zeitgeist

2016-05-05 Thread Khurshid Alam
@fossfreedom How did you resolve the issue? It is marked as "fix-
released" but still reproducible under 16.04.

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

Title:
  Package zeitgeist-python for python3 aka make package
  python3-zeitgeist

Status in Zeitgeist Framework:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released

Bug description:
  At the moment the package python-zeitgeist installs in python2.7
  location and does not have a python3.x installation which makes
  python3 migration tougher.

  Expectation: Have a second package python3-zeitgeist which installs in
  python3.x location

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

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


[Touch-packages] [Bug 1578789] Re: No sim card selected

2016-05-05 Thread Pat McGowan
** Also affects: messaging-app (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No sim card selected

Status in Canonical System Image:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  Every time I try to send sms I get an pop up saying that no sim card
  was selected(mx4 so just one sim card) but this only hapens when I'm
  sending a new message, if I'm responding to one that I already
  received this doesn't happen, so I think the problem is with the pull
  up to send new sms.

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

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


[Touch-packages] [Bug 706011] Re: gpg --key-gen doesn't have enough entropy and rng-tools install/start fails

2016-05-05 Thread Yoha
First, this is a critical flaw for usability. Second, usability flaws translate
into security issues.

For instance, the widespread myth of “high entropy password” using mixed-cased
letters, digits and “special characters” is a disaster. Sure, having complex
passwords does theoretically allows for high entropy but, in practice, it
means:

* users will not use passwords chosen uniformly at random (famously “123456”,
  “password” and “qwerty”, see [1] for more)
* users will forget them (which lead to “security” questions and numerous
  compromises [2]; see demo [3])
* users will write them down in obvious places (pentester presentation at
  Defcon [4])

On the other hand, if you get people to use easy-to-remember passwords actually
chosen uniformly at random [5], you can mitigate these situations. Note also
that even just *two* actually random words would already be quite better than
the current situation.

[1] https://wpengine.com/unmasked/
[2] http://www.wired.com/2012/08/apple-amazon-mat-honan-hacking/
[3] https://www.youtube.com/watch?v=opRMrEfAIiI
[4] https://www.youtube.com/watch?v=4-qnYaw7VGo=28m58s
[5] https://xkcd.com/936/

---

Now, regarding GnuPG, there are multiple usability flaws. This bug focuses on
one.

Obviously, if you want to use it for yourself or in a highly tech-literate
community, that should not be to much of a problem. However, many of us are
trying to get common people to embrace some decent security.

First, in most cases, the difference between /dev/random and /dev/urandom do
not even really matter. The only I can think of right now are (feel free to
suggest others):

* fresh install
* generating many keys in a row that are all going to be security relevant
  (i.e. n-1 tests and 1 real does not count)

This is the reason for proposals for having /dev/random stop blocking once
enough entropy have been gathered [1].

Second, attacks are few and far between and still very theoretical. One dates
from 2006 and does not do much [2] (slides at [3]). Note the comments,
especially zooko [4] highlighting the importance of usability and unruh [5] who
already complains about the poor man page [6]. Another one is [7] which does
look somewhat more interesting but still does not go very far.

Third, GnuPG requests an absurdly high amount of entropy. It seems to want more
than 2352 bits of entropy, even though security will only be a few hundred bits
at best. Even without considering /dev/urandom, it does mean that GnuPG is
running ten times too slow. I suspect the prime number generator naively eat
more entropy for each new random number it needs, rather than using a CSPRNG.

All this results in a critical usability flaw for no good reason. I want to
underline that, for many users, we are not debating “extremely high security”
(/dev/random) versus “very high security” (/dev/urandom) but “no security” (not
using GnuPG) versus “very high security” (using GnuPG).

Of course, [8] is a very good read, as have been before. I would add [9]
(which is mentioned in [8]).

In my opinion, the best course of action would be to make `/dev/urandom`
opt-out (situation actually requiring `/dev/random` might opt-in). At the very
least, there should be an option to opt-in `/dev/urandom`.

[1] 
http://www.philandstuff.com/2013/03/14/why-does-gpg-need-so-much-entropy.html
[2] https://lwn.net/Articles/184925/
[3] https://www.blackhat.com/presentations/bh-usa-06/BH-US-06-Gutterman.pdf
[4] https://lwn.net/Articles/185209/
[5] https://lwn.net/Articles/190070/
[6] `man 4 random` or http://man7.org/linux/man-pages/man4/random.4.html
[7] https://www.schneier.com/blog/archives/2013/10/insecurities_in.html
[8] http://www.2uo.de/myths-about-urandom/
[9] 
https://security.stackexchange.com/questions/3936/is-a-rand-from-dev-urandom-secure-for-a-login-key

---

Since I am at at, I will answer texadactyl regarding improvement of the user
interface.

Basically, GnuPG needs to find a number (well two) with a nice property (being
prime). We virtually have no better way than just picking a number at random
and testing whether it does match the property.

It works like for lottery probabilities: even after losing numerous times, you
are no more likely to win. With GnuPG, say you expect the key generation to
take roughly 2 minutes ; if after 2 minutes you sill have found no such number,
the expected remaining time is *still* 2 minutes.

If you look at the output of `openssl genrsa 4096 > /dev/null`, you will see
one like for each of those prime numbers. A dot `.` represents a candidate and
a double plus `++` indicates a find. GnuPG creates two RSA pairs by default
(primary and encryption), which means four prime numbers, or four lines of
output; it prints fives pluses `+` for a find.

Remark: each plus `+` actually represents a probabilistic test of primality;
using deterministic testing would take much more time

---

**tl;dr:** please, allow common people to use /dev/urandom

-- 
You received this bug notification because you 

[Touch-packages] [Bug 624316] Re: No sound using HDA Intel onboard sound - Lenovo ThinkCentre M58

2016-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  No sound using HDA Intel onboard sound - Lenovo ThinkCentre M58

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Out of the box the sound card is not detected by ordinary users in
  Ubuntu 10.04 with kernel 2.6.32-24-generic 32 bit. Running 'alsamixer'
  returns a "Device not found" error and 'aplay -l' does not detect
  anything either. Running the same commands as root return information
  about the card. The card is detected in lspci and lshw and according
  to lsmod the snd-hda-intel module appears to be loaded correctly.
  Adding users to the audio group allows them to run alsamixer and
  aplay, including (supposed) playing sound, but no sound is produced.
  I've checked the alsamixer settings and everything seems to be okay
  there, i.e. nothing is muted. I've also tried installing linux-
  backports-modules-alsa-lucid-generic but that hasn't helped either.

  Please see attached output from 'ubuntu-bug alsa-base', 'dmesg' and
  'lspci -vvv'. If you need further information let me know.

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

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


[Touch-packages] [Bug 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out

2016-05-05 Thread Krzysztof Burliński
I'm also affected by this bug.

Started happening just after update to xenial.

Before that, I never had 'connect' button grayed 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/1542733

Title:
  Connect to Hidden Wi-Fi Network, "Connect" grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  1. Create a static, connection to hidden Wi-Fi connection using 
nm-connection-editor

  2. click nm-applet icon
  click "Connect to Hidden Wi-Fi Network"
  click pre-existing connection
  "Connect" is grayed out

  Work around is using terminal.
  nmcli c up id 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb  6 15:58:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.55  
metric 600
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7c22db8e-2026-413b-86cd-0c796f177dd5  
802-3-ethernet   1454790964  Sat 06 Feb 2016 02:36:04 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/1  no  
--  -- -- 
   jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
802-11-wireless  1454795858  Sat 06 Feb 2016 03:57:38 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes 
wlp2s0  activated  /org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp1s0  ethernet  unavailable  /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/1542733/+subscriptions

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


[Touch-packages] [Bug 1228532] Re: [Ubuntu Touch] bluetooth indicator does not dissapear when bluetooth is turned off

2016-05-05 Thread Rüdiger Kupper
Hi Carla,
I don't. You would'nt expect the network indicator to disappear from the status 
bar when you select "disable network". So why should the bluetooth indicator do 
so?
Instead, we should expect the indiactor to change appearance, just like the 
network indicator does when network is disabled.

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

Title:
  [Ubuntu Touch] bluetooth indicator does not dissapear when bluetooth
  is turned off

Status in Bluetooth Menu:
  In Progress
Status in indicator-bluetooth package in Ubuntu:
  In Progress

Bug description:
  When you swipe down from the top to show the indicators, select
  bluetooth tab,  touch "Bluetooth" switch button to  disable bluetooth,
  I expect the bluetooth indicator to dissapear from the status bar.

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

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


[Touch-packages] [Bug 1551122] Re: Crash on screen power save

2016-05-05 Thread Mike Butash
I'm currently on 5.5.1+dfsg-16ubuntu7, which should be newer and include
these, no?

I found this digging into why xenial's kde5 plasma shell and all kde
apps keep freaking when my 4k displays go away.  Like others, I use big
4k tv's (3x of them) that give no signal when they power down, so the
displays go away entirely with variable results.

Harassing the kwin guys led me here as deeper qt bugs, but still seems
present as of stated version.

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

Title:
  Crash on screen power save

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Continuation to bug #1548766 to consider another upstream fix from
  https://codereview.qt-project.org/#/c/138681/

  The fix could affect both monitor power saving or attaching/detaching
  cycles.

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

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


[Touch-packages] [Bug 1322655] Re: bluetooth indicator doesn't work properly after hibernate

2016-05-05 Thread Rüdiger Kupper
Confirmed. It does also happen after sleep/resume, not only hibernate.

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

Title:
  bluetooth indicator doesn't work properly after hibernate

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  If I shut down the computer and restart it the bluetooth-indicator
  works fine

  However if I hibernate the computer and start it again, the ON-OFF
  switch in the bluetooth-indicator does not change the icon (so if the
  switch is changed to "ON" the indicator stays greyed out).

  If I go to control-center Bluetooth, and change the state there the
  indicator starts to work again

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

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


[Touch-packages] [Bug 1514659] Re: After Bluetooth was re-enabled, the indicator shows it's still disabled

2016-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  After Bluetooth was re-enabled, the indicator shows it's still
  disabled

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  CID: 201409-15477 Dell Latitude 3450

  Disable and re-enable the wireless / Bluetooth with the wireless key,
  even if the Bluetooth is working, the indicator still shows it's not.

  Steps:
  1. Install 14.04.3 + update (3.19.0-31)
  2. Disable the wireless network with the wireless hotkey, and re-enable it
  3. Check whether the Bluetooth is working or not with rfkill list and 
hciconfig
  4. Check the indicator status.

  Expected result:
  * The Bluetooth indicator correctly reflects the status of the Bluetooth

  Actual result:
  * Indicator shows that it's disabled, but actually it's working.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20150825-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  9 21:06:30 2015
  InstallationDate: Installed on 2015-10-27 (13 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: unity-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity-settings-daemon.log: (gnome-terminal:2422): GLib-GIO-CRITICAL 
**: g_settings_get: the format string may not contain '&' (key 
'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call 
will probably stop working with a future version of glib.

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

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


[Touch-packages] [Bug 1524400] Re: Use default keymap on creation of surface

2016-05-05 Thread Rüdiger Kupper
This bug is still present for the "instant reply" feature of the messaging 
indicator:
When you receive a message and display it via the system indicator, you can tap 
the message and instantly type a reply, without having to start up the 
messaging app. The text box or this instant reply does not use the right 
keyboard layout when a bluetooth keboard is connected.

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

Title:
  Use default keymap on creation of surface

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  Fix Released
Status in Canonical Pocket Desktop:
  Fix Committed
Status in qtmir package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Keymaps should be configurable pr surface or for all surfaces. This
  bug tracks implementation of the latter.

  Determining what keymap to use
  Input sources (InputSources) is an array of dicts on the 
org.freedesktop.Accounts.User interface, which is on the system bus. This holds 
all the user chosen keymaps. If empty, it indicates en_us. It is on the system 
bus so that the greeter can determine what keymap to use.

  If keymaps > 1, the default keymap for all surfaces will be the first
  applicable keymap.

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

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


[Touch-packages] [Bug 1574792] Re: sound devices disappear from sound settings

2016-05-05 Thread Bruno Nova
This is happening several times per day and is becoming annoying (I lose
sound).

"pulseaudio --kill" fixes the sound ("pulseaudio --start" is not
needed).

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

Title:
  sound devices disappear from sound settings

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sound devices disappear from the sound settings however sound is still 
working.
  pulseaudio --kill pulse audio --start restore them back to the sound 
settings. In rear cases, it cannot be started "daemon startup failed".
  This can happen at any time without a reason, also sometimes happen when 
plugging headphones or connecting bluetooth speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr 26 01:02:04 2016
  InstallationDate: Installed on 2016-04-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.0-6588-g4acd8ea-dirty
  dmi.board.name: Peppy
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr4.0-6588-g4acd8ea-dirty:bd09/04/2014:svnGOOGLE:pnPeppy:pvr1.0:rvnGOOGLE:rnPeppy:rvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Peppy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Touch-packages] [Bug 1578807] [NEW] package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-05-05 Thread Ambarish Kumar Singh
Public bug reported:

System update failling.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd-sysv 229-4ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Tue Apr 26 12:22:51 2016
ErrorMessage: pre-dependency problem - not installing systemd-sysv
InstallationDate: Installed on 2015-12-05 (152 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: systemd
Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
UpgradeStatus: Upgraded to xenial on 2016-04-26 (9 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  System update failling.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Apr 26 12:22:51 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-12-05 (152 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (9 days ago)

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

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


[Touch-packages] [Bug 1578807] Re: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-05-05 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  System update failling.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Apr 26 12:22:51 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2015-12-05 (152 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (9 days ago)

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

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


[Touch-packages] [Bug 1577778] Re: lightdm crashes when running java build

2016-05-05 Thread Fodder
latest release of openjdk 1.8 seems to have resolved the issue

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

Title:
  lightdm crashes when running java build

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Part way through a java build, the display manager crashes and
  restarts.  This seems to happen when console applications which
  generate a lot of output run.

  
  fully up to date system
  stock install of openjdk 1.8, maven git
  crashes the display manager regardless of whether I log in on vt7/X or log in 
on vt1/console

  run the following commands
  git clone http://git.apache.org/gora.git/
  cd gora
  mvn package

  
  The following showed on the console for ubuntu-bug
  ** (apport-gtk:11985): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-ZcrOeQWcWb: Connection refused
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  cat: /etc/lightdm/lightdm.conf: No such file or directory

  
  release info:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  
  Package info:
  lightdm:
Installed: 1.18.1-0ubuntu1
Candidate: 1.18.1-0ubuntu1
Version table:
   *** 1.18.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  default-jdk:
Installed: 2:1.8-56ubuntu2
Candidate: 2:1.8-56ubuntu2
Version table:
   *** 2:1.8-56ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  default-jdk-headless:
Installed: 2:1.8-56ubuntu2
Candidate: 2:1.8-56ubuntu2
Version table:
   *** 2:1.8-56ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jdk:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jdk-headless:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jre:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jre-headless:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-source:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status
  git:
Installed: 1:2.7.4-0ubuntu1
Candidate: 1:2.7.4-0ubuntu1
Version table:
   *** 1:2.7.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  git-man:
Installed: 1:2.7.4-0ubuntu1
Candidate: 1:2.7.4-0ubuntu1
Version table:
   *** 1:2.7.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status
  git-svn:
Installed: 1:2.7.4-0ubuntu1
Candidate: 1:2.7.4-0ubuntu1
Version table:
   *** 1:2.7.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
  100 /var/lib/dpkg/status
  maven:
Installed: 3.3.9-3
Candidate: 3.3.9-3
Version table:
   *** 3.3.9-3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue May  3 09:03:23 2016
  

[Touch-packages] [Bug 1577778] Re: lightdm crashes when running java build

2016-05-05 Thread Fodder
latest openjdk 1.8 update resolves the issue

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

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

Title:
  lightdm crashes when running java build

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Part way through a java build, the display manager crashes and
  restarts.  This seems to happen when console applications which
  generate a lot of output run.

  
  fully up to date system
  stock install of openjdk 1.8, maven git
  crashes the display manager regardless of whether I log in on vt7/X or log in 
on vt1/console

  run the following commands
  git clone http://git.apache.org/gora.git/
  cd gora
  mvn package

  
  The following showed on the console for ubuntu-bug
  ** (apport-gtk:11985): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-ZcrOeQWcWb: Connection refused
  /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  cat: /etc/lightdm/lightdm.conf: No such file or directory

  
  release info:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  
  Package info:
  lightdm:
Installed: 1.18.1-0ubuntu1
Candidate: 1.18.1-0ubuntu1
Version table:
   *** 1.18.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  default-jdk:
Installed: 2:1.8-56ubuntu2
Candidate: 2:1.8-56ubuntu2
Version table:
   *** 2:1.8-56ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  default-jdk-headless:
Installed: 2:1.8-56ubuntu2
Candidate: 2:1.8-56ubuntu2
Version table:
   *** 2:1.8-56ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jdk:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jdk-headless:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jre:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-jre-headless:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  openjdk-8-source:
Installed: 8u77-b03-3ubuntu3
Candidate: 8u77-b03-3ubuntu3
Version table:
   *** 8u77-b03-3ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status
  git:
Installed: 1:2.7.4-0ubuntu1
Candidate: 1:2.7.4-0ubuntu1
Version table:
   *** 1:2.7.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  git-man:
Installed: 1:2.7.4-0ubuntu1
Candidate: 1:2.7.4-0ubuntu1
Version table:
   *** 1:2.7.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status
  git-svn:
Installed: 1:2.7.4-0ubuntu1
Candidate: 1:2.7.4-0ubuntu1
Version table:
   *** 1:2.7.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
  100 /var/lib/dpkg/status
  maven:
Installed: 3.3.9-3
Candidate: 3.3.9-3
Version table:
   *** 3.3.9-3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: 

[Touch-packages] [Bug 1545802] Re: activeFocus not being forwarded to TextInput inside TextField

2016-05-05 Thread Olivier Tilloy
The call to forceActiveFocus() that triggers the problem is there:
https://bazaar.launchpad.net/~osomon/webbrowser-
app/browserpage/view/head:/src/app/webbrowser/HistoryViewWide.qml#L168.

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

Title:
  activeFocus not being forwarded to TextInput inside TextField

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Haven’t managed to reproduce with a standalone example yet, but I can
  reliably reproduce the following issue with the browser app on a
  tablet with a bluetooth keyboard connected (this needs to be on a
  tablet so that the wide layout of the app is used, for example with a
  Nexus 7 (flo) in landscape orientation):

   1) launch the browser app with a bluetooth keyboard attached and ensure that 
the current tab is not a new tab
   2) press Ctrl+T to open a new tab

  Expected result: the address bar gets active focus so that the user
  can start entering a URL right away

  Current result: the address bar gets active focus for a fraction of a
  second, then looses it. When that happens, pressing Ctrl+L (which
  forces focus on the address bar) doesn’t fix it.

  
  I added some debugging to the browser (printing Window.activeFocusItem 
whenever it changes), and it appears that when initially forcing active focus 
on the address bar the QQuickTextInput inside it gets active focus, then looses 
it. At that point the activeFocusItem is the TextField, but it doesn’t forward 
it to QQuickTextInput inside itself.

  That situation can be remedied by using a bluetooth mouse to click on
  the address bar, which restores active focus on the QQuickTextInput.

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

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


[Touch-packages] [Bug 1545802] Re: activeFocus not being forwarded to TextInput inside TextField

2016-05-05 Thread Olivier Tilloy
Another occurrence of the issue just happened when running the QML unit
tests for this branch: lp:~osomon/webbrowser-app/browserpage.

That’s with a different TextField (the search field in the history view,
not the address bar), but the symptom is similar: at some point the code
calls forceActiveFocus() on the field, and the TextField component gets
active focus, but it doesn’t forward it to the QQuickTextInput inside
it.

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

Title:
  activeFocus not being forwarded to TextInput inside TextField

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  Haven’t managed to reproduce with a standalone example yet, but I can
  reliably reproduce the following issue with the browser app on a
  tablet with a bluetooth keyboard connected (this needs to be on a
  tablet so that the wide layout of the app is used, for example with a
  Nexus 7 (flo) in landscape orientation):

   1) launch the browser app with a bluetooth keyboard attached and ensure that 
the current tab is not a new tab
   2) press Ctrl+T to open a new tab

  Expected result: the address bar gets active focus so that the user
  can start entering a URL right away

  Current result: the address bar gets active focus for a fraction of a
  second, then looses it. When that happens, pressing Ctrl+L (which
  forces focus on the address bar) doesn’t fix it.

  
  I added some debugging to the browser (printing Window.activeFocusItem 
whenever it changes), and it appears that when initially forcing active focus 
on the address bar the QQuickTextInput inside it gets active focus, then looses 
it. At that point the activeFocusItem is the TextField, but it doesn’t forward 
it to QQuickTextInput inside itself.

  That situation can be remedied by using a bluetooth mouse to click on
  the address bar, which restores active focus on the QQuickTextInput.

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

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


[Touch-packages] [Bug 1573494] Re: winbind 4.3.8 has an ntlm_auth that breaks evolution-ews

2016-05-05 Thread Mathew Hodson
** Project changed: ubuntu-gnome => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  winbind 4.3.8 has an ntlm_auth that breaks evolution-ews

Status in libsoup:
  Fix Released
Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Trusty:
  Fix Released
Status in libsoup2.4 source package in Wily:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Fix Released

Bug description:
  See https://bugzilla.redhat.com/show_bug.cgi?id=1327072 and
  https://bugzilla.gnome.org/show_bug.cgi?id=765106 for the fix to
  libsoup.

  I think evolution-ews also might need a rebuild.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: winbind 2:4.3.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 22 02:34:28 2016
  InstallationDate: Installed on 2016-04-15 (7 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   nautilus 1:3.20.0-0ubuntu1~xenial2
   gvfs 1.28.1-1ubuntu1
  SambaClientRegression: Yes
  SourcePackage: samba
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago)

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

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


[Touch-packages] [Bug 1565567] Re: segv in sudo_getgrgid

2016-05-05 Thread Rafael David Tinoco
I just verified that sudo fix seems good within yakkety. Marking it as
verification-done.

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

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

Title:
  segv in sudo_getgrgid

Status in sudo:
  Unknown
Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  In certain environments, for example when using LDAP, users can end up
  in a group with no name. When that happens, sudo crashes when
  attempting to look up the group name for the debug log.

  Upstream has commited a simple fix for this issue, it has been
  commited to Yakkety, and uploaded to Xenial.

  [Test Case]

  I currently don't know an easy way to reproduce this, it is
  environment-specific. A package containing the fix was successfully
  tested in the problematic environment.

  [Regression Potential]

  A regression in the patch would prevent users from using sudo. The
  risk of regression is low since the patch only changes the debug log.


  Original report:

  If the user is in a group with no name (because libnss-db got removed
  and the group was defined there, for example...) then:

  the call to sudo_debug_printf in sudo_getgrgid
  (plugins/sudoers/pwutil.c, line 462) causes a SEGV when trying to get
  item->d.gr->gr_name (since item->d.gr is NULL).

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

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


[Touch-packages] [Bug 1576565] Re: HDMI Sound drops out after screen blank/suspend (must use pacmd to reset0

2016-05-05 Thread Zalan
** Also affects: alsa-driver
   Importance: Undecided
   Status: New

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

Title:
  HDMI Sound drops out after screen blank/suspend (must use pacmd to
  reset0

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound is outputted through HDMI. Upon suspend/resume or resume from
  screen blank, output switches to analog and HDMI is not an available
  option from the GUI although still listed using "aplay-l". Sound
  returns after resetting HDMI as default using the following command:
  pacmd set-card-profile 1 output:hdmi-stereo-extra1+input:analog-stereo

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 29 09:52:09 2016
  InstallationDate: Installed on 2015-12-15 (135 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Sound works for a while, then breaks
  Title: [, Intel CougarPoint HDMI, Digital Out, HDMI] fails after a while
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (6 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67GD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10206-210
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67GD:rvrAAG10206-210:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1578663] Re: create DHCP exit hook for setting NTP servers

2016-05-05 Thread Martin Pitt
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=77d020de

** Changed in: systemd (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  create DHCP exit hook for setting NTP servers

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Yakkety:
  Fix Committed

Bug description:
  Similar to /etc/dhcp/dhclient-exit-hooks.d/ntpdate, we should ship a
  DHCP exit hook for timesyncd to update the timesyncd configuration in
  /run/systemd/timesyncd.conf.d/01-dhclient.conf to set the picked up
  NTP servers, and restart timesyncd.

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

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


[Touch-packages] [Bug 1576711] Re: [xenial] Enable arm64 build

2016-05-05 Thread Jim Hodapp
** Changed in: qtubuntu-media (Ubuntu)
 Assignee: (unassigned) => Jim Hodapp (jhodapp)

** Changed in: qtubuntu-media (Ubuntu)
   Status: Confirmed => Fix Committed

** Branch linked: lp:~phablet-team/qtubuntu-media/fix-1538703

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

Title:
  [xenial] Enable arm64 build

Status in Canonical System Image:
  Confirmed
Status in initramfs-tools-ubuntu-touch package in Ubuntu:
  New
Status in libhybris package in Ubuntu:
  New
Status in qtubuntu-camera package in Ubuntu:
  New
Status in qtubuntu-gles package in Ubuntu:
  New
Status in qtubuntu-media package in Ubuntu:
  Fix Committed
Status in qtubuntu-sensors package in Ubuntu:
  New
Status in ubuntu-touch-meta package in Ubuntu:
  New
Status in unity-scope-click package in Ubuntu:
  New

Bug description:
  Tracking bug for touch packages without arm64 enabled on xenial

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

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


[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection

2016-05-05 Thread kevin gunn
just coming back to this, looks like the mir patch is landed and in 
stable-phoine-overlay for some time.
i'm guessing sdk is just the remaining bit?
handing over to zoltan

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

** Changed in: canonical-devices-system-image
 Assignee: kevin gunn (kgunn72) => Zoltan Balogh (bzoltan)

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

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

Title:
   "BottomEdge" component does not support automatic mouse detection

Status in Canonical System Image:
  In Progress
Status in mir package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  BottomEdge component does not work property with mouse unless you set
  the:

  QuickUtils.mouseAttached  = true

  
  This should be done automatically by SDK.

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

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


[Touch-packages] [Bug 1206164] Re: /etc/network/if-up.d/ntpdate does not detach correctly

2016-05-05 Thread ChristianEhrhardt
added the Debian bug I reported the patch

** Bug watch added: Debian Bug tracker #823533
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823533

** Also affects: ntp via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823533
   Importance: Unknown
   Status: Unknown

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

Title:
  /etc/network/if-up.d/ntpdate does not detach correctly

Status in NTP:
  Unknown
Status in ntp package in Ubuntu:
  Triaged

Bug description:
  It seems that the intent of /etc/network/if-up.d/ntpdate is to
  background itself, as it creates a subshell with &.

  As reported in bug 1202758, this doesn't seem to work correctly.  That
  doesn't close the file descriptors.  As a result, if something is
  waiting on the output of 'ifup', it will sit and wait until ntpdate is
  finished.

  Example:
  $ time sudo sh -c 'o=$(sh -c "ifdown eth0 ; ifup eth0" 2>&1) ; echo $o'

  If we change the way it detaches itself to close stdout, stdderr, and
  stdin, then we're fine.

  I'm reporting this, but I'm not sure how much of a real problem it is.  As if 
th
  e command sends stdin and stdout to /dev/null, then debugging its output 
would b
  e more difficult.

  Example diff:
  $ diff -u /etc/network/if-up.d/ntpdate.dist /etc/network/if-up.d/ntpdate
  --- /etc/network/if-up.d/ntpdate.dist  2013-07-29 15:47:54.242781947 +
  +++ /etc/network/if-up.d/ntpdate 2013-07-29 15:48:06.946781947 +
  @@ -56,4 +56,4 @@
 lockfile-remove $LOCKFILE
   fi

  -) &
  +) /dev/null 2>&1 &

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ntpdate 1:4.2.6.p5+dfsg-2ubuntu2
  ProcVersionSignature: User Name 3.10.0-5.15-generic 3.10.2
  Uname: Linux 3.10.0-5-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Mon Jul 29 15:32:30 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.network.if.up.d.ntpdate: 2013-07-29T15:32:03.567775

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

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


[Touch-packages] [Bug 1578169] Re: trace if no sources.list.d directory

2016-05-05 Thread Brian Murray
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  trace if no sources.list.d directory

Status in software-properties package in Ubuntu:
  New

Bug description:
  If no /etc/apt/sources.list.d directory exist, add-apt-repository
  traces:

   sudo add-apt-repository ppa:pjbroad/ppa
   
   More info: https://launchpad.net/~pjbroad/+archive/ubuntu/ppa
  Press [ENTER] to continue or ctrl-c to cancel adding it

  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 168, in 
  if not sp.add_source_from_shortcut(shortcut, options.enable_source):
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
752, in add_source_from_shortcut
  self.set_modified_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
484, in set_modified_sourceslist
  self.save_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
650, in save_sourceslist
  self.sourceslist.save()
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 413, 
in save
  files[source.file] = open(source.file, "w")
  FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/apt/sources.list.d/pjbroad-ubuntu-ppa-xenial.list'
  gpg: keyring `/tmp/tmpjea6zt0y/secring.gpg' created
  gpg: keyring `/tmp/tmpjea6zt0y/pubring.gpg' created
  gpg: requesting key DF90C47A from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmpjea6zt0y/trustdb.gpg: trustdb created
  gpg: key DF90C47A: public key "Launchpad PPA for Paul Broadhead" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.20
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed May  4 14:37:48 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1019 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (187 days ago)

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

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


[Touch-packages] [Bug 1578762] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-05-05 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  but i know no further about initramfs, i'm sure it pertains to ram
  drive creation, well..best guess anyhow

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   iucode-tool: Install
   intel-microcode: Install
   iucode-tool: Configure
   intel-microcode: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu May  5 18:13:46 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1578531] Re: Evolution menus not localized after updating ubuntu

2016-05-05 Thread Matthias Bläsing
Ok - thanks for the hint  - but why is the status invalid? The bug is
there and you confirmed it - it may be fixed in head, but invalid
implies it does not exist.

Could you please give an estimation when said update will hit the ubuntu
archives?

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

Title:
  Evolution menus not localized after updating ubuntu

Status in language-pack-gnome-de-base package in Ubuntu:
  Invalid

Bug description:
  After updating ubuntu to 16.04 evolution lost its localization. I
  checked nautilus and gedit, both show the correct german translations
  of the menus, just evolution shows english menus.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: language-pack-gnome-de-base 1:16.04+20160415
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu May  5 10:09:46 2016
  InstallationDate: Installed on 2013-12-15 (871 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  SourcePackage: language-pack-gnome-de-base
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-de-base/+bug/1578531/+subscriptions

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


[Touch-packages] [Bug 1522675] Re: /root/.synaptic/ not created due to locking status

2016-05-05 Thread jean-christophe manciot
After exiting from Synaptic, is it expected for the file
/var/cache/apt/archives/lock to be still there?

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

Title:
  /root/.synaptic/ not created due to locking status

Status in apt package in Ubuntu:
  Invalid
Status in synaptic package in Ubuntu:
  Confirmed
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1578762] [NEW] package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-05-05 Thread Jason Cravens
Public bug reported:

but i know no further about initramfs, i'm sure it pertains to ram drive
creation, well..best guess anyhow

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
AptOrdering:
 iucode-tool: Install
 intel-microcode: Install
 iucode-tool: Configure
 intel-microcode: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu May  5 18:13:46 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  but i know no further about initramfs, i'm sure it pertains to ram
  drive creation, well..best guess anyhow

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  AptOrdering:
   iucode-tool: Install
   intel-microcode: Install
   iucode-tool: Configure
   intel-microcode: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu May  5 18:13:46 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1499419] Re: webbrowser-app: ../../nouveau/pushbuf.c:726: nouveau_pushbuf_data: Assertion `kref' failed.

2016-05-05 Thread Olivier Tilloy
** Package changed: webbrowser-app (Ubuntu) => oxide

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

Title:
  webbrowser-app: ../../nouveau/pushbuf.c:726: nouveau_pushbuf_data:
  Assertion `kref' failed.

Status in Oxide:
  Confirmed

Bug description:
  webbrowser-app on Wily/unity8/mir/nouveau driver
  the browser crashes with webbrowser-app: ../../nouveau/pushbuf.c:726: 
nouveau_pushbuf_data: Assertion `kref' failed.

  nouveau: kernel rejected pushbuf: No such file or directory

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

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


[Touch-packages] [Bug 1572943] Re: Token::isValid() returns true on invalid tokens

2016-05-05 Thread Rodney Dawes
** Changed in: ubuntuone-credentials (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntuone-credentials (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: ubuntuone-credentials (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Token::isValid() returns true on invalid tokens

Status in ubuntuone-credentials package in Ubuntu:
  In Progress

Bug description:
  Token token(QString(), QString(), QString(), QString());
  token.isValid(); // prints true

  This is something which can obviously being worked around in the
  client code, but I think it would be nicer if Token would consider
  empty strings as missing data.

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

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


[Touch-packages] [Bug 1574347] Re: WiFi network list disappears from network manager applet

2016-05-05 Thread Bug Watch Updater
** Changed in: network-manager
   Status: Unknown => Fix Released

** Changed in: network-manager
   Importance: Unknown => Medium

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

Title:
  WiFi network list disappears from network manager applet

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Issue is in Ubuntu 16.04 LTS amd64 version.

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  
  Temporary Workaround:-
  Log out and again log back in.

  Please solve this issue asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 23:15:34 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp18s0  proto static  metric 600 
   169.254.0.0/16 dev wlp18s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp18s0  proto kernel  scope link  src 192.168.1.99  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE   STATE  ACTIVE-PATH
   Airtel-201  d263b201-9281-427e-94e2-762fa620813c  802-11-wireless  
1461519922  Sunday 24 April 2016 11:15:22 PM IST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes wlp18s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8 
   Wired connection 1  142942d4-d247-4880-9bab-1eeafc29ca86  802-3-ethernet   
1461508904  Sunday 24 April 2016 08:11:44 PM IST  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/2  no  --   --  
   --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp18s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Airtel-201  d263b201-9281-427e-94e2-762fa620813c  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   enp19s0  ethernet  unavailable  /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/network-manager/+bug/1574347/+subscriptions

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


[Touch-packages] [Bug 1489643] Re: [pay UI] Paypal login cannot be assured to be from paypal

2016-05-05 Thread Rodney Dawes
@sil I don't think there will ever be any way to guarantee that. Any UI
that appears on the screen can be replicated, so there is no way we can
place something in that UI itself, which could not be replicated. Not
even 2FA will protect against that, as any 'fake' UI could also just as
easily respond to a 2FA request and have you enter the code.

I guess we should close this as invalid, or mark it as a duplicate of
bug #1402725 for the EV cert handling?


** Changed in: pay-service (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  [pay UI] Paypal login cannot be assured to be from paypal

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in pay-service package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When paying for an app with Paypal, the Paypal login screen is
  presented in an Ubuntu wrapper. There is no indication on this page
  that I'm actually looking at paypal.com rather than being phished or
  that some bad DNS has pointed me to a wrong site. The padlock in the
  top corner doesn't indicate anything I'm inclined to believe -- is it
  showing that the connection is https? Has it verified that I'm really
  talking to Paypal? How can I know that? This is encouraging people to
  type their Paypal password into phishing sites. The previous step in
  the purchase process, where I'm choosing which payment system to use,
  also displays a padlock, and that hasn't connected to any payment site
  at all.

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

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


[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

2016-05-05 Thread Scarlett Clark
LOL the whole point of the patches and this mess was to avoid that as our users 
(Kubuntu) will end up bringing in all of Unity. That is NOT an option. I was 
under the impression this patch was suppose to fix all of this?
Perhaps something else needs a rebuild. I will absolutely not put a dep on 
online-accounts

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in meta-telepathy:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Confirmed
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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


[Touch-packages] [Bug 1574004] Re: package udev 229-4ubuntu4 failed to install/upgrade: /var/log/udev is a directory

2016-05-05 Thread Brian Murray
Hello Erich, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu5
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  package udev 229-4ubuntu4 failed to install/upgrade: /var/log/udev is
  a directory

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  upgrade to 16.04 failed

  SRU INFORMATION
  ---
  Fix: 
http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=d133b04

  Test case: Install trusty, remove the /var/log/udev file, and make it
  a directory (sudo mkdir -p /var/log/udev). Upgrade to 16.04 (at least
  udev). This will fail on this error with the xenial version, but
  should succeed with this fix.

  Regression potential: practically zero. This only ignores errors on
  the rm of the old log file.

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 14:34:45 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-16 (281 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 4174P5G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-36-generic 
root=UUID=6d33134c-01af-4ee9-ad9e-afe117f0cff4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  Title: package udev 229-4ubuntu4 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)
  dmi.bios.date: 04/11/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8CET57WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4174P5G
  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:bvr8CET57WW(1.37):bd04/11/2013:svnLENOVO:pn4174P5G:pvrThinkPadT420s:rvnLENOVO:rn4174P5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4174P5G
  dmi.product.version: ThinkPad T420s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1539137] Re: Results model updates performance is poor with hundreds of results

2016-05-05 Thread Michał Sawicz
** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Results model updates performance is poor with hundreds of results

Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  The implementation of incremental result model updates have some
  bottlenecks and doesn't scale well when number of results increases.
  This is not visible with the number of results we currently have on
  the phone, but it gets really bad if scope pushes hundreds of them.

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

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


[Touch-packages] [Bug 1545866] Re: First scope results only load after unlock

2016-05-05 Thread Michał Sawicz
** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  First scope results only load after unlock

Status in Canonical System Image:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Results in the first scope only load after you unlock the device
  instead of being already there when you unlock.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160212-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Mon Feb 15 22:58:19 2016
  InstallationDate: Installed on 2016-02-13 (2 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160213-020304)
  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/1545866/+subscriptions

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


[Touch-packages] [Bug 1574483] Re: assigns MAC-based names for devices with locally administered MAC address

2016-05-05 Thread Brian Murray
Hello Martin, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu5
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  assigns MAC-based names for devices with locally administered MAC
  address

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Originally from https://bugs.debian.org/812575: Our current
  /lib/systemd/network/90-mac-for-usb.link assigns MAC-based names to
  all USB devices. However, this is wrong and pointless for locally
  administered MAC addresses (with the second bit set to '1', see
  https://en.wikipedia.org/wiki/MAC_address#Address_details).

  The old 75-persistent-net generator had this rule:

     ENV{MATCHADDR}=="?[2367abef]:*",ENV{MATCHADDR}=""

  which ignored these devices. We need to adjust 90-mac-for-usb.link to
  do the same, and only apply to universally administered MAC addresses
  (at least until https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-April/039302.html gets concluded).

  We should simply fall through the default policy of assigning location
  based names. The kernel assigned ones have no meaning whatsoever, so
  this at least provides name stability for use cases where you can rely
  on plugging the device into the same port.

  SRU INFORMATION:
  
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=ec7e332

  Test case:
   - Plug in an Android phone and enable USB tethering, or a different USB 
device which uses locally administered MAC addresses, i. e. they change after 
every reboot of the device. The first byte of the MAC address must have the 
second bit set, i. e. the hex number matches ?[2367abef].
   - Check "ip a". With current xenial version the interface name is MAC based, 
like "enx12345678", and it changes after rebooting the device.
   - With this fix, the name is location based, like "enp0s1u2", and it remains 
stable as long as you use the same USB port.

  Regression potential: This only affects naming USB network devices. It
  should be tested that devices with universally administered MACs (i.
  e. stable, second bit is zero) keep MAC based names to avoid changing
  existing stable names. For devices with locally administered MACs (i.
  e. random ones) the name currently changes all the time anyway, so any
  /etc/network/interfaces or firewall script that refers to them is
  already broken and there cannot be further regressions there. Also,
  the updated policy is only applied after a computer reboot or
  replugging the device, the name does not change while the device is
  already plugged in.

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

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


[Touch-packages] [Bug 1537112] Re: Preview widgets may not get displayed if scope makes a mistake in layout definition

2016-05-05 Thread Michał Sawicz
** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Preview widgets may not get displayed if scope makes a mistake in
  layout definition

Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  From a quick look at PreviewModel::addWidgetToColumnModel method it
  seems like the implementation is prone to errors in column layout
  definitions: if scope pushes more widgets than defined in the layout,
  they are likely to be ignored and not inserted into the widget model.
  I think the proper strategy would be to append them at the bottom of
  the first column.

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

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


[Touch-packages] [Bug 1363946] Re: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale

2016-05-05 Thread Michał Sawicz
** Changed in: unity-scopes-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect
  locale

Status in unity-scopes-api package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  unity8-dash gets into a respawn loop when the selected locale is
  unavailable. While it's understood that incorrect locale might result
  in unexpected behaviour, but aborting feels excessive.

  .log file mentions:

  ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for 
client, config file: :
  unity::scopes::MiddlewareException: cannot initialize zmq middleware for 
scope c-17178aae:
  locale::facet::_S_create_c_locale name not

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity8 8.00+14.10.20140828.1-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Mon Sep  1 11:55:15 2014
  ExecutablePath: /usr/bin/unity8-dash
  ExecutableTimestamp: 1409258182
  InstallationDate: Installed on 2014-09-01 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140901-020204)
  LocalLibraries: /android/system/lib/libGLES_trace.so 
/android/system/lib/libstlport.so /android/system/lib/libgccdemangle.so 
/android/system/lib/libm.so /android/system/lib/libcorkscrew.so 
/android/system/lib/liblog.so /android/system/lib/libstdc++.so 
/android/system/lib/libutils.so /android/system/lib/libc.so 
/android/system/lib/libcutils.so /android/system/lib/libGLESv2.so 
/android/system/lib/libEGL.so /android/system/lib/libdsyscalls.so
  ProcCmdline: unity8-dash 
--desktop_file_hint=/usr/share/applications/unity8-dash.desktop
  ProcCwd: /home/phablet
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   raise () from /lib/arm-linux-gnueabihf/libc.so.6
   abort () from /lib/arm-linux-gnueabihf/libc.so.6
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
   ?? () from 
/usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  Title: unity8-dash crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip plugdev sudo tty video

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

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


[Touch-packages] [Bug 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box

2016-05-05 Thread Brian Murray
Hello Dimitri, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu5
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  [udev] FIDO u2f security keys should be supported out of the box

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users plugin U2F key and it does not work in Google Chrome

  [Test Case]

   * Have stock ubuntu install, without custom U2F rules or libu2f-host0
  installed

   * Use U2F factor authentication website e.g. google apps, github,
  yubico, etc.

   * Pluging in the key, should just work and complete U2F
  authentication instead of timing out

  [Regression Potential]

   * Should not conflict with libu2f-host0 udev rules which is where
  these are currently shipped

  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

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

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


[Touch-packages] [Bug 1485887] Re: ClickStore preview refreshes completely when pressing Install or the installation finishes

2016-05-05 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ClickStore preview refreshes completely when pressing Install or the
  installation finishes

Status in unity-scope-click:
  New
Status in unity-scopes-shell package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Right now, when you install an app, the complete screen refreshes when
  you press the install button. The same when the installation completes
  and the progress bar becomes a button again.

  It should only update the button instead of destroying and recreating
  the whole model.

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

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


[Touch-packages] [Bug 1567429] Re: Scope::settings() is too slow

2016-05-05 Thread Michał Sawicz
** Changed in: unity-scopes-shell (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Scope::settings() is too slow

Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  Evaluating

  settingsEnabled: scopeView.scope && scopeView.scope.settings &&
  scopeView.scope.settings.count > 0 || false

  in GenericScopeView.qml takes around 300 ms when running on the phone,
  which basically feels like an eternity if you're trying to use the
  phone to scroll, change to another scope, etc

  If this needs heavy calculation this should be either pre-calculated
  and cached or calculated in a separate thread and then signalled with
  a signal.

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

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


[Touch-packages] [Bug 1576409] Re: calling init.d script with "status" invokes pager

2016-05-05 Thread Brian Murray
Hello Martin, or anyone else affected,

Accepted systemd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu5
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  calling init.d script with "status" invokes pager

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Committed

Bug description:
  Running e. g. "/etc/init.d/networking status" runs a pager (less by
  default). This is unexpected from an init.d script, and potentially
  breaks scripts or CLI programs that do this operation, as this then
  hangs eternally in the interactive pager process until the user quits
  it. This reportedly happens with "vagrant up" (see original Debian bug
  https://bugs.debian.org/765175).

  SRU INFORMATION:
  Test case:
   Run "/etc/init.d/networking status". In current xenial this invokes less 
which you need to quit. With the proposed fix this should return to the shell 
immediately without a pager.

  Regression potential:  very low. The main visible change is the
  interactive usage of "/etc/init.d/foo status", but nothing in Ubuntu
  (nor hopefully anywhere else) *relies* on the fact that systemctl
  invokes a pager, particularly as this is not always done (it depends
  on whether stdout is a terminal and how many lines are written).

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

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


[Touch-packages] [Bug 1578748] [NEW] Magi Mouse crashes device

2016-05-05 Thread Markus Svensson
Public bug reported:

When connecting an Apple Magic Mouse via bt  to my M10 tablet, the
device hangs. It will eventually reboot if left alone.

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

** Attachment added: "last_kmsg"
   https://bugs.launchpad.net/bugs/1578748/+attachment/4656564/+files/last_kmsg

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

Title:
  Magi Mouse crashes device

Status in bluez package in Ubuntu:
  New

Bug description:
  When connecting an Apple Magic Mouse via bt  to my M10 tablet, the
  device hangs. It will eventually reboot if left alone.

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

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


[Touch-packages] [Bug 1578612] Re: [UX] Poor contrast in new dialog buttons

2016-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [UX] Poor contrast in new dialog buttons

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  The new color for dialog buttons has very poor contrast that make them
  almost impossible to distinguish from the white background. Attached a
  picture of the wifi dialog.

  current build number: 32
  device name: krillin
  channel: ubuntu-touch/stable/bq-aquaris.en

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

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


[Touch-packages] [Bug 1576741] Re: Upcoming alarm ETA going out of sync

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

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

Title:
  Upcoming alarm ETA going out of sync

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

Bug description:
  Similar to Bug #1557571, but for alarms.

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

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


[Touch-packages] [Bug 1561924] Re: can't scroll to bottom of wifi list in wizard

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

Title:
  can't scroll to bottom of wifi list in wizard

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

Bug description:
  On today's phone image (arale rc-proposed 286), I can't connect to my
  access point in the OOBE wizard because the WAP name starts with a 'w'
  and I can't get the wifi list to scroll all the way to the bottom.

  Any time I get it near the bottom, the list re-shuffles itself and
  scrolls back up.

  Taochen reports seeing the same on a krillin.

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

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


[Touch-packages] [Bug 1542075] Re: viewfinder should re-size to fit window

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

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

Title:
  viewfinder should re-size to fit window

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

Bug description:
  in windowed mode, the viewfinder is currently fills the screen in the
  vertical orientation. If the window is made smaller the controls
  incorrectly rotate like the app thinks it's in landscape mode and
  bottom edge moves to the right.

  Lets discuss what to do here, but some options:

  1) resizing the window shouldn't change where the controls are located or the 
orientation
  2) resizing should make the viewfinder fill the available space. Should it 
use the largest vertical or horizontal dimension, or be fixed to the physical 
orientation of the phone?
  3) Should we not allow window resizing and instead lock the window size to 
the actual size of the viewfinder?
  4) If the phone is rotated, should the window size automatically change to 
reflect the phone orientation?

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

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


[Touch-packages] [Bug 1577147] Re: SIM PIN screen has a white overlay instead of a dark one

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

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

Title:
  SIM PIN screen has a white overlay instead of a dark one

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

Bug description:
  Likely due to r2345 [1] we now have a lightening layer instead of a
  darkening one on the SIM PIN screen - see attachment.

  [1] https://bazaar.launchpad.net/~unity-
  team/unity8/trunk/changes/2354?start_revid=2374

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.12+15.04.20160427.3-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Sun May  1 14:02:18 2016
  InstallationDate: Installed on 2016-04-29 (2 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160429-020305)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.unity8.log:
   [DD 2016-05-01 12:02:07.121200] [player_stub.cpp:184@operator()] 
PlaybackStatusChanged signal arrived via the bus (status: 
PlaybackStatus::stopped)
   Attempted to unregister path (path[0] = core path[1] = ubuntu) which isn't 
registered

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

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


[Touch-packages] [Bug 1533781] Re: trust prompt should hide the OSK

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

Title:
  trust prompt should hide the OSK

Status in Canonical System Image:
  Triaged
Status in trust-store package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  In messaging-app we have a problem that we can't hide the osk while the trust 
prompt is being displayed.
  I assume that's because the main thread of the app gets blocked until the 
trust prompt is closed.

  I believe trust-prompt should hide the keyboard itself as other apps
  will hit the very same problem.

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

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


[Touch-packages] [Bug 1565103] Re: bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => backlog

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

Title:
  bottom edge first time wizard is being incorrectly displayed on
  dialer-app and messaging-app

Status in Canonical System Image:
  Triaged
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.

  Steps to reproduce:

  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

  Another case is when launching messaging-app or dialer-app in a dual
  sim environment. We have a first time dialog that appears behind the
  wizard. Not sure if that's expected, but seems to cause a bad user
  experience to me.

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

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


[Touch-packages] [Bug 1542395] Re: Screen.orientation and or Screen.primaryOrientation depend on the size of the app window

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

Title:
  Screen.orientation and or Screen.primaryOrientation depend on the size
  of the app window

Status in Canonical System Image:
  Confirmed
Status in QtMir:
  Confirmed
Status in qtubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  When the user resizes an app window the value returned by
  Screen.angleBetween(Screen.primaryOrientation, Screen.orientation)
  changes depending on the aspect ratio of the window. If the window has
  a landscape aspect ratio, one value is returned, otherwise another one
  is returned.

  Screen orientation and app window size should be independent.

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

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


[Touch-packages] [Bug 1573153] Re: M10 tablet does not respect the orientation specified in .desktop file

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

Title:
  M10 tablet does not respect the orientation specified in .desktop file

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

Bug description:
  Developers can restrict apps orientation by using
  X-Ubuntu-Supported-Orientations=portrait
  in .desktop file. Unfortunately it does not work in the new M10 tablet. You 
can see such app both in portrait and in landscape.

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

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


[Touch-packages] [Bug 1475678] Re: Unity8 not informing clients that they are not visible and thus can stop rendering

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => 12

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

Title:
  Unity8 not informing clients that they are not visible and thus can
  stop rendering

Status in Canonical System Image:
  In Progress
Status in QtMir:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Currently on the phone, apps stop rendering when shell hides them,
  because shell also lifecycle stops the app. App isn't actually told it
  should stop rendering, we just SIGSTOP its process.

  But some apps are not lifecycle stopped, e.g. music. So we should have
  unity8 tell the app to stop rendering.

  
  This will be a multi-step process:
  1. Qtubuntu
  Mir has a attribute to set on surfaces to tell them they are 
visible/occluded: (see mir/include/common/mir_toolkit/common.h)
  mir_surface_attrib_visibility - part of the MirSurfaceAttrib enum. 

  This indicates these possible values:
  typedef enum MirSurfaceVisibility
  {
  mir_surface_visibility_occluded = 0,
  mir_surface_visibility_exposed
  } MirSurfaceVisibility;

  On the client side (qtubuntu), you need to listen for this attribute change, 
and connect it to QWindowSystemInterface::handleExposeEvent() which tells Qt 
how much of a QWindow is being drawn.
  Note there is also a QWindowSystemInterface::handleWindowStateChanged() 
handler, which use use to explicitly set QWindow show/hide, but Qt tends to 
release its GL context on hide, which we may not desire. It may not hurt, worth 
a look.

  2. QtMir
  There are methods on mir::scene::Surface to set and get the MirSurfaceAttrib 
attributes. I think it would make sense to use the pre-existing 
MirSurfaceItem::visible property, so that if a surface is marked visible=false, 
then that will dispatch the mir_surface_visibility_occluded event to the 
client, so it will stop drawing.

  3. Unity8
  Correctly set visible=false when an application surface is occluded, and true 
when visible. QML has no automatic way of doing that (i.e. occlusion detection)

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

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


[Touch-packages] [Bug 1567685] Re: Preview horizontal swiping removed in OTA-10

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => backlog

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

Title:
  Preview horizontal swiping removed in OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Sorry I not sure if this is the correct place to report this. My hardware is 
the MX4 with OTA-10 update.
  I am a little disappointed with the OTA-10 update, one of the best scope 
features "swipe left and right through cashed (second level down)  more 
detailed articles" such as used on the softpedia and news scopes,  has been 
removed. This feature was very easy to use and did not require you to keep 
using the back button to the top level scope items to select the next text to 
read. This function  was on all scopes (I think), upto OTA-9.1, some such 
Softpeadia and the news scope used it to great effect. I was hoping this would 
become more commonly used giving less need to go to the website. Can you please 
consider adding this excellent feature back in or OTA-11. 

  Please see examples scope 2nd level swipe to the right showing the
  first article and moving to the next (OTA 9.1). You cant do this on
  OTA-10, real same. I also think it looked so cool that it was a real
  selling point for the software.

  Thanks for your support and hard work, love Ubuntu Touch and have
  already placed an order for the BQ M10 tablet,

  Best regards

  Dave H

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

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


[Touch-packages] [Bug 1578673] Re: [Touch] Volume level is not maintained per output device

2016-05-05 Thread Anupam
** Description changed:

  If I'm not mistaken this issue was not present before OTA-10. I usually
  like to keep the volume at around 80% on speaker and around 50% on
  earphones. Previously the device used to remember these choices and
  adjust them accordingly. But now it only remembers the previously set
  volume level and hence I have to adjust manually all the time while
  switching output devices.
+ 
+ Device: bq E5, OTA-10.1

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

Title:
  [Touch] Volume level is not maintained per output device

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

Bug description:
  If I'm not mistaken this issue was not present before OTA-10. I
  usually like to keep the volume at around 80% on speaker and around
  50% on earphones. Previously the device used to remember these choices
  and adjust them accordingly. But now it only remembers the previously
  set volume level and hence I have to adjust manually all the time
  while switching output devices.

  Device: bq E5, OTA-10.1

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

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


[Touch-packages] [Bug 1563572] Re: Greeter password entry cut/paste widget in portrait mode

2016-05-05 Thread Michał Sawicz
** Changed in: canonical-devices-system-image
Milestone: 11 => backlog

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

Title:
  Greeter password entry cut/paste widget in portrait mode

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  This feels pretty minor in the scheme of things but on avila.

  TEST CASE
  1.  Unlock device, device greeter appears
  2.  Tap on Password entry
  3.  Long-press on cursor in Password entry
  EXPECTED
  Selection pop-up appears in landscape mode
  ACTUAL
  Selection pop-up appears in portrait mode

  Happy to furnish a screenshot.  Meanwhile I don't know what I'm
  expecting to do with the cut/paste selection tool here, maybe it
  doesn't apply here?

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

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


[Touch-packages] [Bug 1578601] Re: Crash when choosing "yes" to some popups

2016-05-05 Thread Renato Araujo Oliveira Filho
** Changed in: sync-monitor (Ubuntu)
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

Title:
  Crash when choosing "yes" to some popups

Status in sync-monitor package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Every so often I get a popup on my krillin rc proposed telling me my
  google account credentials have expired, and asking me if I want to
  fix it. I usually click "no" because I'll do it later. Today i clicked
  "yes" while my phone was locked. Unity8 crashed.

  
  Have your phone configured to sync calendars
  Let your credentials become stale / expire
  Wait
  Eventually when sync-monitor is checking for calendar entries it will popup a 
notification which asks if you want to fix the issue.
  Select "no" and it goes away - don't do this.
  Select "yes" 

  Expected behaviour:-

  It should ask you to unlock the phone and then take you to system
  settings

  Actual behaviour:-

  Unity8 dies.

  Crash file attached.

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

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


[Touch-packages] [Bug 1578737] [NEW] /usr/lib/accountsservice/accounts-daemon:5:ik_source_read_some_events:ik_source_read_all_the_events:ik_source_dispatch:g_main_dispatch:g_main_context_dispatch

2016-05-05 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding accountsservice.  This problem was most recently seen with
version 0.6.40-2ubuntu10, the problem page at
https://errors.ubuntu.com/problem/fa13dbbd326c674d72805cb6f3f9cf14c526a237
contains more details.

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


** Tags: wily xenial

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

Title:
  /usr/lib/accountsservice/accounts-
  
daemon:5:ik_source_read_some_events:ik_source_read_all_the_events:ik_source_dispatch:g_main_dispatch:g_main_context_dispatch

Status in accountsservice package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding accountsservice.  This problem was most recently seen with
  version 0.6.40-2ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/fa13dbbd326c674d72805cb6f3f9cf14c526a237
  contains more details.

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

-- 
Mailing list: https://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   >