date:20151111

** Changed in: ubiquity (Ubuntu Trusty)
Milestone: ubuntu-14.04.3 => ubuntu-14.04.4

** Changed in: ecryptfs-utils (Ubuntu Trusty)
Milestone: None => ubuntu-14.04.4

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

Title:
  Encrypted swap no longer mounted at bootup

Status in eCryptfs:
  Fix Released
Status in systemd:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ecryptfs-utils source package in Trusty:
  Triaged
Status in ubiquity source package in Trusty:
  Triaged
Status in ecryptfs-utils source package in Vivid:
  Fix Released
Status in systemd source package in Vivid:
  Fix Released
Status in ubiquity source package in Vivid:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  SUMMARY
  ===
  During installation with "encrypt my home folder" mode, a broken 
/etc/crypttab gets created which defines a non-existing swap device (usually 
"cryptswap1") with a UUID. This will also be put into /etc/fstab. As after 
installation the UUID does not exist, such systems don't have any actual swap.

  UPGRADE FIX
  ===
  An upgrade to Ubuntu 15.04 ("vivid") will detect and comment out these broken 
swap devices from /etc/fstab and /etc/crypttab. If you actually want  to use 
those, do these steps:

   - Find the swap device that was meant to be used in "sudo fdisk -l" (it 
should say "Linux swap" in the last column), remember the device name 
(something like "/dev/sda5")
   - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=)
   - Run "sudo mkswap -U 1234... /dev/sda5", replacing "1234" with the above 
UUID, and /dev/sda5 with the device name from step 1.
   - Edit /etc/crypttab to append ",offset=1024" in the fourth (last) column of 
the cryptswap1 line; ensure that there is *no space* between the 
"cipher=aes-cbc-essiv:sha256" and the appended option. If there is a leading 
"#" in the file, remove that too.
   - If there is a leading "#" in /etc/fstab in the line starting with 
/dev/mapper/cryptswap1 line, remove that.
   - Run "sudo update-initramfs -u".

  
  ORIGINAL REPORT
  ===

  Clean install of 12.04 and with encrypted home for my user. Did all
  updates and now the bootup hangs waiting for swap to become available
  and it never seems to ever finish. The 200GB SSD below is my boot
  drive and root filesystem.

  alan@mesh:~$ sudo swapon -a
  [sudo] password for alan:
  swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory

  alan@mesh:~$ grep swap /etc/fstab
  # swap was on /dev/sdg5 during installation
  #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 
 0   0
  /dev/mapper/cryptswap1 none swap sw 0 0

  alan@mesh:~$ sudo fdisk -l

  Disk /dev/sda: 115.0 GB, 115033153536 bytes
  255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x000ba2ed

     Device Boot  Start End  Blocks   Id  System
  /dev/sda1   *2048  206847  1024007  HPFS/NTFS/exFAT
  /dev/sda2  206848   224671743   1122324487  HPFS/NTFS/exFAT

  Disk /dev/sdb: 200.0 GB, 200049647616 bytes
  255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disk identifier: 0xf0fa0806

     Device Boot  Start End  Blocks   Id  System
  /dev/sdb12048   349304831   1746513927  HPFS/NTFS/exFAT
  /dev/sdb2   374722558   390721535 79994895  Extended
  /dev/sdb3   *   349304832   37472051112707840   83  Linux
  /dev/sdb5   374722560   390721535 7999488   82  Linux swap / Solaris

  Partition table entries are not in disk order

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libecryptfs0 96-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 13 09:56:56 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120215)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ecryptfs-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.l

[Touch-packages] [Bug 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group

2015-11-11 Thread Serge Hallyn

So the problem is indeed that the cgroups are deleted using the
cgroupfs, and fuse doesn't get that information.  The fuse kernel module
is caching the information for one second before re-querying userspace.

I've pushed a patch to lxcfs to drop the caching to a half second.  I'm
posting a patch to lxc-devel to sleep for half a second during reboot.
This reliably fixes the race in my tests.

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

Title:
  rebooting container with systemd >= 226 fails to create /lxc/adt-
  xenial/init.scope control group

Status in lxc package in Ubuntu:
  In Progress

Bug description:
  Even after fixing bug 1497420 rebooting containers with systemd >= 226
  (i. e. with supporting unified cgroups) does not work. Build a
  standard xenial container (using the ubuntu template; e. g. "adt-
  build-lxc ubuntu xenial"), start it:

sudo lxc-start -n adt-xenial -F

  then log in and run "sudo reboot". It shuts down, but reboot fails
  with

  Rebooting.
  systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR 
+SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP 
+BLKID -ELFUTILS +KMOD -IDN)
  Detected virtualization lxc.
  Detected architecture x86-64.

  Welcome to Ubuntu 16.04!

  Set hostname to .
  Failed to install release agent, ignoring: No such file or directory
  Failed to create /lxc/adt-xenial/init.scope control group: No such file or 
directory
  Failed to allocate manager object: No such file or directory
  [!!] Failed to allocate manager object, freezing.
  Freezing execution.

  During that time, I get the following errors:

  Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path 
/run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file 
or directory)
  Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_children_main: Could 
not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope)
  Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path 
/run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file 
or directory)
  Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_keys_main: Could not 
determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope)
  Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager 
method call org.linuxcontainers.cgmanager0_0.ListChildren failed: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use 
G_DBUS_DEBUG=message for more info.
  Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager 
method call org.linuxcontainers.cgmanager0_0.ListKeys failed: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use 
G_DBUS_DEBUG=message for more info.h

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lxc 1.1.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 10 06:30:28 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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

[Touch-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink

2015-11-11 Thread Hannes Bochmann

Only one monitor is plugged into the DisplayLink docking station so I
think the limitation of two monitors is not the problem. If I deactivate
the internal laptop monitor or the monitor plugged directly into the
laptop nothing changes. The mouse keeps flickering on the monitor that
is not connected to the docking station.

Thanks for the advice using the support forum of DisplayLink. The bug
was already reported
(http://www.displaylink.org/forum/showthread.php?p=79054#post79054). The
only "solution" they came up with is switching from Unity to another
desktop environment like gnome or metacity. As I like the Unity Dock
Launcher this is not a real option for me.

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1485682

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  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:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782 
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1387643] Re: Pruning of probably stale sessions should be less aggressive

2015-11-11 Thread Thomas Voß

** Changed in: location-service (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Pruning of probably stale sessions should be less aggressive

Status in Canonical System Image:
  Fix Committed
Status in location-service package in Ubuntu:
  Fix Committed

Bug description:
  Right now, after 10 non-successful attempts to deliver location
  updates to clients, the service considers the client to be hanging or
  dead and prunes the session from the service's cache. With that, if
  the app wakes up again, it does not receive updates for the same
  session anymore. A restart of the app fixes the issue.

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

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

[Touch-packages] [Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops

2015-11-11 Thread Thomas Voß

** Changed in: location-service (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [Ubuntu Phone] With WIFI = ON the GPS stops

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  New
Status in ubuntu-system-settings:
  New
Status in location-service package in Ubuntu:
  Fix Committed

Bug description:
  Hi!

  Steps: 
  1. Enable WIFI = ON on phone.
  2. Run one of these apps: GPS Navigation, HERE maps, Sensor Status.
  3. Drive.
  4. When you'll be into a WIFI area as a town or city, I'm thinking the WIFI 
will try to search WIFIs and then the GPS will stop, the GPS apps will not 
receive more new positions from the GPS.

  Extra info1: If you had GPS Navigation & Sensor running, both of them
  will not receive new GPS positions from the device. If you restart for
  example GPS Navigation, GPS Navigation will receive new positions, but
  Sensor Status not, until you restart it too.

  Extra info2: When the GPS stops the icon in the status disappears, but
  it you kill and relaunch the app, the icon will appear again.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1212360] Re: Cannot import OpenVPN profiles

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

Title:
  Cannot import OpenVPN profiles

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 12.10 / Intel / ASUS Zenbook
  Package: network-manager

  1. receive an OpenVPN profile (ovpn and crt files) by email or download.
  2. open Network Manager
  3. look in vain for an "import" button or link.

  What should have happened instead:

  3. there should be an "import OpenVPN profile" button on the "new VPN"
  dialog

  Prior to Unity, the gnome network manager had an "import VPN" button
  which allowed importing configuration files for OpenVPN and Cisco.
  The new Unity network manager has removed that button and not replaced
  it with anything.  The only workaround is to install the old Gnome
  network manager, launch it from the command line, and use it to import
  the VPN profile.

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

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

[Touch-packages] [Bug 1363046] Re: No message/call notification tone plays through Bluetooth headset

** Changed in: bluez (Ubuntu Utopic)
Milestone: ubuntu-14.09 => None

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

Title:
  No message/call notification tone plays through Bluetooth headset

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Utopic:
  Fix Released

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez  4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth headset (Sony SBH50, Motorola S10-HD) is connected to 
krillin and a call/sms is received, no notification tone is played through the 
headset. Instead it plays normally through the device loud speakers.

  We have seen on some other versions of headset (Jawbone ERA, BQ Avrha
  Strauss) where a new sms notification tone is played through the
  headset, but not the call ringer tone.

  STEPS:
  1) Pair and connect the Bluetooth headset
  2) Receive an incoming sms
  3) Receive an incoming call

  EXPECTED RESULT:
  The notification tones should play through the Bluetooth headset

  ACTUAL RESULT:
  There is no notification tone played through the Bluetooth headset

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

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

[Touch-packages] [Bug 1370572] Re: Unknown libmtp error when copying content from internal storage to SD card using MTP

** Changed in: mtp (Ubuntu)
Milestone: ubuntu-14.09 => None

** Tags added: trusty utopic

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

Title:
  Unknown libmtp error when copying content from internal storage to SD
  card using MTP

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09 build 1
  Desktop: Ubuntu 14.04/14.10

  SUMMARY:
  Unknown libmtp error when copying content from internal storage to SD card 
using MTP.

  This might be the case for someone who has a new memory card and they
  want to copy/move content to it from device's internal storage.

  STEPS:
  1) Connect Ubuntu device to Ubuntu host PC over USB
  2) Attempt to copy/move some music content directly from device's internal 
storage to device's SD card using MTP

  EXPECTED RESULT:
  The content should be copied/moved successfully.

  ACTUAL RESULT:
  The following error is displayed on desktop:
  "libmtp error: Unknown error".

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

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

[Touch-packages] [Bug 1369651] Re: "libmtp error: Could not send object info" when copying content to root MTP folder

** Changed in: mtp (Ubuntu)
Milestone: ubuntu-14.09 => None

** Tags added: utopic

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

Title:
  "libmtp error: Could not send object info" when copying content to
  root MTP folder

Status in mtp package in Ubuntu:
  Confirmed

Bug description:
  ENVIRONMENT:
  Ubuntu device: ubuntu-rtm/14.09-proposed build 40
  Desktop: Ubuntu 14.10

  SUMMARY:
  "libmtp error: Could not send object info" when copying content to root MTP 
folder

  STEPS:
  1) Connect Ubuntu MTP device over USB
  2) Attempt to copy some content to the root of the MTP folder

  EXPECTED RESULT:
  The copy operation should succeed. (This is the Android behaviour).

  ACTUAL RESULT:
  An error message is presented on desktop: "libmtp error: Could not send 
object info"

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

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

[Touch-packages] [Bug 1512608] Re: No thumbnails generated for OGG audio

2015-11-11 Thread Fred Vkigg

Thanks for the feedback. Sorry to respond so slowly.

I'm still still seeing a slow increase in thumbnails. I suspect it will
not converge to a complete coverage!

I need to further analyse the logs. One possibility is that I see a lot of OOM 
killer activity when Music app is open. I need to check the memory usage of the 
associated processes when Music is running. 
The BQ 5 seems chronicly short of RAM for the current touch releases!

I will wait to see if the retry changes in thumbnailer in OTA-8 effect
the results. If still bad I can post an SD card.

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

Title:
  No thumbnails generated for OGG audio

Status in thumbnailer package in Ubuntu:
  New

Bug description:
  Setup:
Core Music app 
BQ HD5
OTA-7 15.04 r6
Large collection of audio files in .ogg and .mp3 format on SD card
Audio files tagged with Artist, Album titile, Track title etc.

  Expected result:
Album covers and Artist images are displayed in Music app

  Actual result:
Only mp3 audio files generate thumbnails. No Album of Artist thumbnails are 
generated for any OGG files

  To test the situation I have
  a) Cleared the thumbnailer failure cache
  b) removed the whole thumbnail cache directory
  c) Removed and reinsterted the SD card
  d) Uninstallled and reinstalled the core Music app

  Before the OTA-7 upgrade the thumbnails were shown for .ogg and .mp3
  files

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

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

[Touch-packages] [Bug 1039792] Re: [needs-packaging] [MIR] ubuntu-default-settings

** Package changed: baltix => ubuntu

** No longer affects: ubuntu

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

Title:
  [needs-packaging] [MIR] ubuntu-default-settings

Status in ubuntu-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu has customized several GNOME packages with gsettings overrides.
  Moving these overrides to a separate package, recommended by ubuntu-
  desktop would have these advantages:

  1. Reduce our diff with Debian
  2. Make it easier for those who want a pure/custom GNOME experience to get it
  3. Give the GNOMEbuntu project more independence to ship a purer GNOME, or 
possibly tweak GNOME defaults without needing to affect the flagship Ubuntu 
desktop.

  This was discussed at UDS:
  http://summit.ubuntu.com/uds-q/meeting/20832/desktop-q-gnome-flavor/

  And "reducing the delta with Debian" is a recurring UDS discussion.
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-gnome-plans-review

  Code is temporarily at https://code.launchpad.net/~ubuntu-
  desktop/+junk/ubuntu-default-settings and will be uploaded shortly.

  This will also need to be promoted to main. However since it only
  contains copies of gsettings overrides (most of which are already in
  main), there's not really any code to review.

  There's also an ubuntu-artwork package which maybe should be merged
  into this one.

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

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

[Touch-packages] [Bug 1039792] Re: [needs-packaging] [MIR] ubuntu-default-settings

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

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  [needs-packaging] [MIR] ubuntu-default-settings

Status in ubuntu-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu has customized several GNOME packages with gsettings overrides.
  Moving these overrides to a separate package, recommended by ubuntu-
  desktop would have these advantages:

  1. Reduce our diff with Debian
  2. Make it easier for those who want a pure/custom GNOME experience to get it
  3. Give the GNOMEbuntu project more independence to ship a purer GNOME, or 
possibly tweak GNOME defaults without needing to affect the flagship Ubuntu 
desktop.

  This was discussed at UDS:
  http://summit.ubuntu.com/uds-q/meeting/20832/desktop-q-gnome-flavor/

  And "reducing the delta with Debian" is a recurring UDS discussion.
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-gnome-plans-review

  Code is temporarily at https://code.launchpad.net/~ubuntu-
  desktop/+junk/ubuntu-default-settings and will be uploaded shortly.

  This will also need to be promoted to main. However since it only
  contains copies of gsettings overrides (most of which are already in
  main), there's not really any code to review.

  There's also an ubuntu-artwork package which maybe should be merged
  into this one.

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

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

[Touch-packages] [Bug 1369632] Re: After disconnecting and reconnecting device to MTP host it is not possible to delete a folder using MTP

** No longer affects: mtp (Ubuntu)

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

Title:
  After disconnecting and reconnecting device to MTP host it is not
  possible to delete a folder using MTP

Status in gvfs package in Ubuntu:
  New

Bug description:
  ENVIRONMENT:
  Device: ubuntu-rtm/14.09-proposed build 40
  Desktop: Windows 8.1 / Ubuntu

  SUMMARY:
  After disconnecting and reconnecting device to MTP host it is not possible to 
delete a folder using MTP

  STEPS:
  1) Connect Ubuntu device to host PC over USB
  2) Copy some music content to the music folder on MTP device including some 
folder structure
  3) Eject the Ubuntu device's USB connection
  4) Re-insert Ubuntu device USB
  5) Browse to MTP Music folder on device
  6) Try to delete some of the music folders that were just added

  EXPECTED RESULT:

  The content should be deleted successfully.

  ACTUAL RESULT:

  After a delay of about 30 seconds Ubuntu presents error:
  "libmtp error: could not delete object".
  It is then not possible to copy any content to or from the device.

  Windows also fails to delete the content with error stating that
  device has been disconnected.

  Note that it is possible to delete files when the device is re-
  connected. It is when deleting a parent folder that the problem
  occurs.

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

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

[Touch-packages] [Bug 1315060] Re: Allow --confdir to look for system jobs in more than one directory

** Changed in: upstart (Ubuntu Utopic)
Milestone: ubuntu-14.06 => None

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

Title:
  Allow --confdir to look for system jobs in more than one directory

Status in The Savilerow project:
  Fix Released
Status in upstart :
  Fix Released
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Utopic:
  Fix Released

Bug description:
  A requirement from OEMs/Carriers for customization is to allow for
  customized upstart jobs/overrides.  It seems that the best way to do
  this would be to allow --confdir to take multiple directories, so that
  we can include a directory under /custom.

  As for session jobs, I assume we can just set /custom as an
  XDG_CONFIG_DIR, and have /custom/upstart with jobs there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May  1 12:30:09 2014
  InstallationDate: Installed on 2013-04-26 (370 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=610268d4-9acd-4bf8-a1a1-95c88b3ccf59 ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-11-23 (158 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)

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

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

[Touch-packages] [Bug 1303843] Re: Window is distorted when it lays out on a size change

** No longer affects: webbrowser-app (Ubuntu)

** Project changed: webbrowser-app => ubuntu

** No longer affects: ubuntu

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

Title:
  Window is distorted when it lays out on a size change

Status in Oxide:
  Fix Released
Status in Oxide 1.0 series:
  Fix Released

Bug description:
  This is most easily seen on the phone but also is present on the desktop. 
  On the phone get the OSK to appear and disappear. On desktop change the 
height of the window.
  The rendering is quite jumpy, it scales the text and images before changing 
the layout itself.

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

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

[Touch-packages] [Bug 1184006] Re: wrong conffile prompt for /etc/default/rcS when UTC=no

** Changed in: sysvinit (Ubuntu)
Milestone: ubuntu-14.04 => None

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

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

Title:
  wrong conffile prompt for /etc/default/rcS when UTC=no

Status in clock-setup package in Ubuntu:
  Confirmed
Status in sysvinit package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in clock-setup source package in Saucy:
  Won't Fix
Status in sysvinit source package in Saucy:
  Won't Fix
Status in ubiquity source package in Saucy:
  Won't Fix

Bug description:
  Because we're not following Debian on the use of /etc/adjtime for UTC
  settings and instead keeping it in /etc/default/rcS, users who have
  the non-default setting of UTC=no will get inappropriate conffile
  prompts on upgrade to saucy.

  We need to deal with this by either reverting /etc/default/rcS's
  conffile status, or moving this UTC setting out of /etc/default/rcS
  (options: /etc/default/hwclock, /etc/init/hwclock{,-save}.override).

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

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

[Touch-packages] [Bug 1499845] Re: Expose whether an app has a visible BottomEdge

It is way easier to detect on an app whether it is the first run or not
than on shell. Shell would need to keep track about each app on how many
times it has been launched, and that is just not its task.

I mentioned Tutorial component simply because I do see this whole logic being 
tracked by it:
- is this the first launch
- show the required information over a given point with a given animation full 
screen

I definitely see this should be all on the app's hand and not on the
system. Apps know whether they have bottom edge and they should handle
the tutorial. No reason to do extra communication and slow the UI
interaction with that even more than we have to. Toolkit can provide the
building blocks to get this handled without extra burden for the apps.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Opinion

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Expose whether an app has a visible BottomEdge

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

Bug description:
  == The Design ==

  The edge tutorial that is shown during the first-boot is getting a
  redesign [1].

  As part of it, the bottom edge tutorial screen is intended to only
  appear after a certain amount of time and only if a user is opening or
  switching to an app with a bottom edge to drag up.

  When that happens, a page appears covering the whole screen, pointing
  to the bottom and saying "Swipe from the bottom edge to manage the
  app".  Then when the user does swipe up, it fades out as the bottom is
  swiped.   I've attached a screenshot of an early mockup for this (back
  when it was designed for the App scope, not an actual app).

  Since it must cover the entire screen (and turn off the launcher and
  panel during it), it should probably be rendered by the shell (which
  is rendering the rest of the tutorial anyway).  So we have to
  coordinate between the app and the shell.

  There are two main technical difficulties in implementing this, the
  way I see it.  Detecting if the current page has a valid BottomEdge
  and synchronizing the fade-out with the bottom-edge drag.

  [1] https://docs.google.com/document/d/1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s

  == Detecting BottomEdge ==

  We need:
  1) A BottomEdge SDK component
  2) That is enabled
  3) That is attached to the bottom edge of the app
  4) That is currently being rendered (might be in a Page that isn't on top 
right now)
  5) That isn't obscured by some other widget or MouseArea

  #5 is going to be hard to detect in the wild west of apps from the
  store.  But one thing we could do restrict this to known-well-behaved
  apps that are shipped by default anyway.  The user is most likely to
  be in one of those early on in their phone experience anyway.

  Once the SDK can detect this situation, it needs to signal it somehow.
  Maybe the "valid-bottom-edge" state can bubble up to qtmir's
  ApplicationManager and then the shell.  Any ideas on the best way to
  do that?

  == Synchronizing fade transition ==

  I'm thinking there are two ways:

  1) Communicate from the app to the shell how far the bottom edge has
  been dragged, as it is being dragged.  Presumably via the same channel
  as we communicate that there is a valid bottom edge in the first
  place.

  2) Fake it and have the shell track the drag itself.  It then needs to
  mirror the input to the app so that it also receives the drag.

  #2 is probably easier.  Slightly brittle in case for whatever reason
  the app interferes with the drag or does something on its own that
  would desynchronize the animation.  But again, if we limit this to
  well-known apps, we can avoid that.

  == Open tasks ==

  1) Get general feedback on these ideas
  2) Determine how feasible it is for the SDK to detect a valid BottomEdge
  3) Determine the best way to signal that state from the SDK up to the shell
  4) Implement it

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

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

[Touch-packages] [Bug 1499872] Re: Right swipe showing running apps, some apps are grayed out

This is not a toolkit bug, rather Unity8.

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

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

Title:
  Right swipe showing running apps, some apps are grayed out

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

Bug description:
  I am using the Meizu MX4 with the latest updates(15.04 r4). Sometimes
  when I look at my running apps with a right swipe, some of the running
  apps are greyed out (transparent). If I then select the app it opens
  after a few seconds. On checking the running apps again I can now see
  the running app as normal. Please see picture attached.

  Thanks for your hard work,

  Regards

  Dave H

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

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

[Touch-packages] [Bug 1290514] Re: LibreOffice KDE4 backend crashes in Qt4 recursive paint events

** Changed in: qt4-x11 (Ubuntu Precise)
   Status: Fix Committed => Confirmed

** Changed in: qt4-x11 (Ubuntu)
Milestone: ubuntu-14.04 => None

** Changed in: qt4-x11 (Ubuntu)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Quantal)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: qt4-x11 (Ubuntu Saucy)
   Importance: Undecided => High

** Tags added: precise

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

Title:
  LibreOffice KDE4 backend crashes in Qt4 recursive paint events

Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in qt4-x11 source package in Precise:
  Confirmed
Status in qt4-x11 source package in Quantal:
  Won't Fix
Status in qt4-x11 source package in Saucy:
  Won't Fix
Status in qt4-x11 source package in Trusty:
  Fix Released

Bug description:
  Distribution: Kubuntu 12.04
  Package: qt4-x11 4:4.8.1-0ubuntu4.6
  Program: LibreOffice 4.3 (current master build).

  This bugs origin is a crash when using KDE4 native file picker dialogs
  from within LibreOffice [1].

  There are several similar ones in all distributions.

  In the backtrace you can see, that LO calls the Qt event dispatcher,
  which processes a draw event, which - at some point - waits for the
  clipboard using the Qt / LO event loop, which processes another (now
  nested) draw event -> crash.

  This happens, because LO sets
    qApp->clipboard()->setProperty( "useEventLoopWhenWaiting", true );
  because the X11 event processing in clipboardWaitForEvents would interfere 
with the LO X11 handling / locking.

  QX11Data::clipboardWaitForEvents (gui/kernel/qclipboard_x11.cpp:520)
  actually installs the correct clipboard event filter in the qapp,
  which should just handle Clipboard events.

  But actually the Qt internal glib event loop doesn't honor the
  QEventLoop::ExcludeSocketNotifiers (see
  src/corelib/kernel/qeventdispatcher_glib.cpp).

  Originally I opened [2], because I didn't want to deep dive into the
  Qt codebase. Since I didn't get any usable replies and all my
  implemented workarounds in LibreOffice didn't work I tried to
  understand the backtrace from [2] and realized the missing
  QEventLoop::ExcludeSocketNotifiers handling in the Qt glib code. I
  opened [3] and pushed a patch for Qt review as [4].

  [1] https://bugs.freedesktop.org/show_bug.cgi?id=69002
  [2] https://bugreports.qt-project.org/browse/QTBUG-34614
  [3] https://bugreports.qt-project.org/browse/QTBUG-37380
  [4] https://codereview.qt-project.org/#change,80528

  [IMPACT]
  The patch fixes the glib event loop to pass a currently failing testcase in 
the Qt4 library (processEventsExcludeSocket in 
tests/auto/qeventloop/tst_qeventloop.cpp). The flag was never handled in the 
glib eventloop.

  [TEST CASE]
  LibreOffice uses a very rarely used Qt codepath to poll the X11 clipboard 
(using the event loop), which needs this patch. Otherwise it crashes very often 
with the KDE 4 backend when polling the clipboard. There is no other codepath.
  Test by using LibreOffice with the KDE theme until it crashes.  After the 
patch is applied it will no longer crash.

  [REGRESSION POTENTIAL]
  I can't imagine a program out there which relies on this brokeness.
  If the patch was really broken to invert the behaviour, the impact would be 
immediately visible, as no socket events would be processed, including X11 
events.

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

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

[Touch-packages] [Bug 1501397] Re: Can't use Action id's in ActionList

First, when you declare a list, you can only initialise it with objects,
not with their IDs. Seems we have this limitation on that. See Object
component implementation how its data is implemented.

Second, Page.head.actions is a list, not an object. You are trying to
assign an object to a list.

Better start with reading the docs carefully.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

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

Title:
  Can't use Action id's in ActionList

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

Bug description:
  Latest rc-proposed, UbuntuComponents 1.3

  I can't use Action id's to compile an ActionList in order to re-use
  those actions elsewhere.

  Please see example: http://paste.ubuntu.com/12625111/

  You may want to reference ActionSelectionPopover documentation here:
  
https://developer.ubuntu.com/api/devel/ubuntu-12.04/qml/ui-toolkit/qml-ubuntu-components-popups0-actionselectionpopover.html

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

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

[Touch-packages] [Bug 1512180] Re: [datetime] Standard alarms are not work correctly for Timers, after timezone/DST change

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Incomplete

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

Title:
  [datetime] Standard alarms are not work correctly for Timers, after
  timezone/DST change

Status in Canonical System Image:
  Incomplete
Status in Timer:
  Confirmed
Status in Ubuntu Clock App:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Standard alarms will not work correctly after changing timezone and
  during DST change.

  Steps to reproduce:
  1. Install Timer from Store: https://uappexplorer.com/app/timer.mivoligo
  2. Set timer to 5 minutes
  3. Open Clock app. Look for alarm, and notice that alarm is correctly set
  3. Switch to System Settings -> Time & Date -> Time zone:
  4.  Change Time zone to something different (eg. New York). (Or wait for DST 
change: https://en.wikipedia.org/wiki/Daylight_saving_time)

  Expected behaviour:
  - timer ringing as expected after timezone/DST change

  Current behaviour:
  - alarm is not ringing. (you could check active alarms in "Ubuntu Clock app)

  Proposal solution:
  - introduce new type of alarms, which is based on UTC 
(https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and independent from 
time zones.
  - This alatms will not be visible in applications which is using standard 
alarms (Ubuntu Clock, Ubuntu Calendar etc.)

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

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

[Touch-packages] [Bug 1513449] Re: 1.3 DraggingArea reference error MathUtils is not defined

This should pop up only if you use Panel in your app. Do you happen to
have that?

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Incomplete

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

Title:
  1.3 DraggingArea reference error MathUtils is not defined

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

Bug description:
  This shows up in the log:
  - when resizing the app window on desktop (15.04 with phone overlay installed)
  - occasionally on the phone

  I think the error is pretty obvious, so probably the bug report need
  to be super detailed.

  file:///usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/1.3/DraggingArea.qml:27: ReferenceError:
  MathUtils is not defined

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

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

[Touch-packages] [Bug 1513642] Re: [sdk] Change "Back button" to simple right-swipe from the center of the screen.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [sdk] Change "Back button" to simple right-swipe from the center of
  the screen.

Status in Ubuntu UX:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Back button is located in left-upper corner.
  Stretching the thumb to that corner is not easy (regardless left- or 
right-hand usage).
  More natural will be using horisontal swipe from the middle of the screen, 
the same way as it's done for shuffling scopes back.
  I think it will work almost everywhere, making interface experience more 
streamlined.

   UX comment ---

  While swiping left and right in the center of the screen for navigational 
purposes works for scopes, it would lead to issues in many other places.
  As stated below, list items have the ability being swiped to the left and to 
the right, which would interfere with the navigation. An other example is the 
camera app, where user access their camera roll/last picture shot.

  This is why the proposed interaction is not suitable navigating
  between applications.

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

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

[Touch-packages] [Bug 1514841] Re: [Ubuntu phone] Text in text entry is cut at the bottom (TextArea with autoSize=true)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Ubuntu  phone] Text in text entry is cut at the bottom (TextArea with
  autoSize=true)

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  When I get a text message and try to answer from the notification text
  entry, the text I write is cut at the bottom. Also the scrollbar is
  visible. Please see attached screenshot. The text reads: „Hej zgadza
  się”.

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

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

[Touch-packages] [Bug 1226329] Re: [TextField] The placeholderText does not apper when inputMask is setted

Christian, not sure whether is this still valid.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana)

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

Title:
  [TextField] The placeholderText does not apper when inputMask  is
  setted

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

Bug description:
  The inputMask makes the placehorlderText invisible even when the text
  property is empty.

  Example:
  TextInputDetail {
  height: units.gu(4)

  // this will never appears
  placeholderText: i18n.tr("Date of birth")
  inputMask: "09/09/"
  }

  
  WORKAROUND:
  TextInputDetail {
  height: units.gu(4)

  // this will never appears
  placeholderText: i18n.tr("Date of birth")
  inputMask: activeFocus ? "09/09/" : ""
  }

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

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

[Touch-packages] [Bug 1259876] Re: No support for colourizing ListItems.Standard Icon.

No changes will be done for ListItems submodule, the new ListItemLayout
gives the freedom to include anything in the slots and thus you can
colorise in whichever way you like.

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

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

Title:
  No support for colourizing ListItems.Standard Icon.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  Previously we could override the icon and supply our own icon which
  could be coloured. This has now been deprecated for
  iconSource/iconName.

  Use case: 
  The date indicator appointments use colour coding for the calendar. The 
alarm/calendar icon should be keyed in with the specified calendar colour. Want 
to be able to use ListItems.Standard for the event list item.

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

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

[Touch-packages] [Bug 1289433] Re: "No accounts" doesn't use the list placeholder font style

This can be achieved with simple Label within an Item, no need for
special toolkit component.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  "No accounts" doesn't use the list placeholder font style

Status in Online Accounts setup for Ubuntu Touch:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Trusty r188

  1. Flash the phone or remove any existing online accounts.
  2. Go to System Settings > "Accounts".

  What you see: "No accounts" in the normal label font style.

  What you should see: "No accounts" in the standard list placeholder
  font style, large and semi-transparent.

  : "If you have none,
  the list of accounts should have 'No accounts' placeholder text..."

  Exactly the same style should be used for "Software is up to date" in
  the Updates screen. If that style is not implemented in the toolkit,
  that should be done first.

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

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

[Touch-packages] [Bug 1427995] Re: lscpu -p is showing wrong values for Node component

** No longer affects: util-linux (Ubuntu)

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

Title:
  lscpu -p is showing wrong values for Node component

Status in util-linux source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Any user of lscpu on systems with multiple NUMA nodes.

  [Test case]
  On a POWER8 system:
  1) Run 'lscpu'; take note of the values for "NUMA node# CPU(s)".
  2) Run 'lscpu -p'.

  The values on the fourth column in lscpu -p output should match the
  node for which the CPU (first column) is listed (or contained in the
  displayed range). For example:

  $ lscpu
  [...]
  NUMA node0 CPU(s): 0-12,14-39
  [...]
  NUMA node3 CPU(s): 13,40-79
  [...]
  $ lscpu -p
  [...]
  12,1,0,0,,1,1,1,1
  13,1,0,3,,1,1,1,1
  [...]
  39,4,0,0,,4,4,4,4
  40,5,1,3,,5,5,5,5
  [..]

  The fourth column for CPU 12 and 39 is "0", which matches the "node0" range 
of 0-12,14-39.
  The fourth column for CPU 13 and 40 is "3", which matches the "node3" range 
13,40-79.

  [Regression potential]
  This change is limited to the output of a command that can be parsed; so any 
regression would be erroneous values for node "names" or numbers, which may 
throw off data retrieved by parsing the output of lscpu.

  This particular bug constitutes the fix to a regression in a previous
  SRU (ubuntu7.4), which included changes to support discontinuous NUMA
  nodes, and introduced the code this SRU changes, so the regression
  potential is minimal (this particular feature of lscpu is already
  broken).

  ---

  ---Problem Description---
  lscpu -p is showing wrong values for Node component

  ---uname output---
  Linux ubuntu 3.16.0-25-generic #14-Ubuntu ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = P8

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
  Install a P8 machine with Ubuntu 14.04.02 ISO image in Power NV mode.
  Then execute the below test scenario.

  root@ubuntu-daily:~# lscpu -p
  # The following is the parsable format, which can be fed to other
  # programs. Each different item in every column has an unique ID
  # starting from zero.
  # CPU,Core,Socket,Node,,L1d,L1i,L2,L3
  0,0,0,0,,0,0,0,0
  1,0,0,1,,0,0,0,0
  2,0,0,16,,0,0,0,0
  3,0,0,17,,0,0,0,0
  4,0,0,0,,0,0,0,0
  5,0,0,0,,0,0,0,0
  6,0,0,33,,0,0,0,0
  7,0,0,0,,0,0,0,0
  8,1,0,0,,1,1,1,1
  9,1,0,0,,1,1,1,1
  10,1,0,-1429431768,,1,1,1,1
  11,1,0,16383,,1,1,1,1
  12,1,0,1852125029,,1,1,1,1
  13,1,0,777213279,,1,1,1,1
  14,1,0,81,,1,1,1,1
  15,1,0,0,,1,1,1,1
  16,2,0,1920169263,,2,2,2,2
  17,2,0,1634235183,,2,2,2,2
  18,2,0,1815045490,,2,2,2,2
  19,2,0,1818321775,,2,2,2,2
  20,2,0,1852125029,,2,2,2,2
  21,2,0,777213279,,2,2,2,2
  22,2,0,759583829,,2,2,2,2
  23,2,0,1953836600,,2,2,2,2
  24,3,0,1278163046,,3,3,3,3
  25,3,0,1162698563,,3,3,3,3
  26,3,0,1195463507,,3,3,3,3
  27,3,0,1966035781,,3,3,3,3
  28,3,0,762079604,,3,3,3,3
  29,3,0,1970170220,,3,3,3,3
  30,3,0,1869426296,,3,3,3,3
  31,3,0,0,,3,3,3,3
  32,4,1,0,,4,4,4,4
  33,4,1,0,,4,4,4,4
  34,4,1,177,,4,4,4,4
  35,4,1,0,,4,4,4,4
  36,4,1,269092192,,4,4,4,4
  37,4,1,256,,4,4,4,4
  38,4,1,1,,4,4,4,4
  39,4,1,16383,,4,4,4,4
  40,5,1,0,,5,5,5,5
  41,5,1,0,,5,5,5,5
  42,5,1,269096544,,5,5,5,5
  43,5,1,256,,5,5,5,5
  44,5,1,269092512,,5,5,5,5
  45,5,1,256,,5,5,5,5
  46,5,1,269097536,,5,5,5,5
  47,5,1,256,,5,5,5,5
  48,6,1,269092688,,6,6,6,6
  49,6,1,256,,6,6,6,6
  50,6,1,269098208,,6,6,6,6
  51,6,1,256,,6,6,6,6
  52,6,1,269096960,,6,6,6,6
  53,6,1,256,,6,6,6,6
  54,6,1,269097456,,6,6,6,6
  55,6,1,256,,6,6,6,6
  56,7,1,269096544,,7,7,7,7
  57,7,1,256,,7,7,7,7
  58,7,1,269098592,,7,7,7,7
  59,7,1,256,,7,7,7,7
  60,7,1,269097344,,7,7,7,7
  61,7,1,256,,7,7,7,7
  62,7,1,269098016,,7,7,7,7
  63,7,1,256,,7,7,7,7
  64,8,2,269096880,,8,8,8,8
  65,8,2,256,,8,8,8,8
  66,8,2,269098400,,8,8,8,8
  67,8,2,256,,8,8,8,8
  68,8,2,269097184,,8,8,8,8
  69,8,2,256,,8,8,8,8
  70,8,2,269097856,,8,8,8,8
  71,8,2,256,,8,8,8,8
  72,9,2,269096672,,9,9,9,9
  73,9,2,256,,9,9,9,9
  74,9,2,0,,9,9,9,9
  75,9,2,0,,9,9,9,9
  76,9,2,0,,9,9,9,9
  77,9,2,0,,9,9,9,9
  78,9,2,65,,9,9,9,9
  79,9,2,0,,9,9,9,9
  80,10,2,1920169263,,10,10,10,10
  81,10,2,1634235183,,10,10,10,10
  82,10,2,1815045490,,10,10,10,10
  83,10,2,1818321775,,10,10,10,10
  84,10,2,1852125029,,10,10,10,10
  85,10,2,777213279,,10,10,10,10
  86,10,2,759583829,,10,10,10,10
  87,10,2,1129066296,,10,10,10,10
  88,11,2,1397050719,,11,11,11,11
  89,11,2,1162297683,,11,11,11,11
  90,11,2,1953836883,,11,11,11,11
  91,11,2,1814916201,,11,11,11,11
  92,11,2,2020961897,,11,11,11,11
  93,11,2,7302446,,11,11,11,11
  94,11,2,113,,11,11,11,11
  95,11,2,0,,11,11,11,11
  96,12,3,269092448,,12,12,12,12
  97,12,3,256,,12,12,12,12
  98,12,3,1,,12,12,12,12
  99,12,3,16383,,12,12,12,12
  100,12,3,0,,12,12,12,12
  101,12,3,0,,12,12,12,12
  102,12,3,269092272,,12,12,12,12
  103,12,3,256,,12,12,12,12
  104,13

[Touch-packages] [Bug 1195353] Re: SDK should provide support to rearrange items in a ListView

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
   Status: New => 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/1195353

Title:
  SDK should provide support to rearrange items in a ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
  Fix Released

Bug description:
  For the clock core app, as per design, it is required to implement
  ListView where the user can drag and drop to rearrange the items in
  the ListView. You can see the official wireframe designs at
  http://design.canonical.com/wp-content/uploads/clock_add_city-
  1024x8901.png to see what I meant.

  It would be best if the SDK can provide support to implement this
  since it may also be useful to other apps.

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

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

[Touch-packages] [Bug 1513958] Re: arm64: failure with small objects passed on stack

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

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

Title:
  arm64: failure with small objects passed on stack

Status in libffi package in Ubuntu:
  Fix Released
Status in libffi source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  It isn't possible to build newer versions of python-cffi on trusty/arm64 
because it's test cases will fail due to this bug. The thing that's biting me 
is that cloud-archive:liberty is incomplete on arm64, making key packages 
uninstallable on arm64 (e.g. nova-compute).

  Additionally, libffi is used by several languages in Ubuntu (python,
  ruby, haskell, etc), so this may also be causing issues in the closed
  set of Ubuntu/trusty packages. I don't have evidence either way.

  [TestCase]
  Build python-cffi_1.1.2-1ubuntu2 from wily on trusty/arm64. With unfixed 
libffi, the build will fail during dh_auto_test in the
  "TestFFI.test_struct_by_value" test case.

  [Regression Risk]
  The fix is in the aarch64-specific code, so there's a negligible risk of 
regression on other platforms. This exact fix was included in vivid and wily 
and no regressions have been triaged to libffi in those releases.

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

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

[Touch-packages] [Bug 147216] Re: LVM filesystems not mounted at boot

2015-11-11 Thread Anthony Kamau

Being that I'm still having this issue on Ubuntu 15.10, I can only
conclude that this appears to be a design philosophy at Canonical rather
than a bug.  Logical volumes that are not necessary for system boot
and/or are not on the primary disk where the OS is installed are not
made available / mounted on (re)boot!

It is much better that the system comes up rather than waiting for a
user input at (re)boot.

Case closed, at least for me!

ak.

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

Title:
  LVM filesystems not mounted at boot

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  My system has a root filesystem in an LVM logical volume, backed up by
  two MD RAID-1 arrays.  It fails to boot propertly after upgrading to
  kubuntu gutsy gibbon prerelease (latest packages as of today).  In
  order to boot it, I have to specify the break=mount boot option, then
  subsequently run

  lvm vgscan
  lvm vgchange -a y

  to manually enable the LVM volumes.  I should note that the MD arrays
  are started successfully.

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

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

[Touch-packages] [Bug 1429140] Re: lxc-net upstart script fails on nonexistent iptables rules

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

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

Title:
  lxc-net upstart script fails on nonexistent iptables rules

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  Hello,

  On Trusty, the stop of lxc-net fails if the iptables rules are not
  present.

  I added “exec >> /tmp/lxc-net.log 2>&1” at the beginning of pre-start
  and post-stop and get:

  iptables: Bad rule (does a matching rule exist in that chain?).

  On Precise, a “|| true” was added to avoid errors.

  I attach a patch to disable exit on failing iptables call.

  Regards.

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

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

[Touch-packages] [Bug 1515106] Re: sound was working completely stopped.sound was working then stopped.[LCI43NB, Realtek ALC888, Green Line Out, Rear] No sound at all

2015-11-11 Thread Raymond

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  sound was working completely stopped.sound was working then
  stopped.[LCI43NB, Realtek ALC888, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  sound was working then stopped. when i access the sound settings
  window in system settings the window appears transparent and bugging
  out? thank you!!! Love Ubuntu!!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic i686
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  electricdigits   1807 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 10 21:14:33 2015
  InstallationDate: Installed on 2015-10-17 (24 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  electricdigits   1807 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [LCI43NB, Realtek ALC888, Green Line Out, Rear] No sound at all
  UpgradeStatus: Upgraded to vivid on 2015-10-26 (16 days ago)
  dmi.bios.date: 07/28/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: NBG4310H.86A.0090.2009.0728.1547
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG43NB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE34877-404
  dmi.chassis.type: 3
  dmi.chassis.vendor: LeByte
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrNBG4310H.86A.0090.2009.0728.1547:bd07/28/2009:svnLeByteComputers:pnLCI43NB:pvr:rvnIntelCorporation:rnDG43NB:rvrAAE34877-404:cvnLeByte:ct3:cvr:
  dmi.product.name: LCI43NB
  dmi.sys.vendor: LeByte Computers

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

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

[Touch-packages] [Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)

** Description changed:

- We have released LXC 1.0.7 upstream:
+ We have released LXC 1.0.8 upstream:
  https://linuxcontainers.org/lxc/news
  
  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.
  
  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html
  
  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.
  
  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

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

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

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

Title:
  New upstream bugfix release 1.0.8 (LXC MRE)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  We have released LXC 1.0.8 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

** Tags added: regression-proposed trusty

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

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1514350] Re: /usr/bin/history-daemon:* Error in `/usr/bin/history-daemon': double free or corruption (out): ADDR *

2015-11-11 Thread Timo Jyrinki

** Also affects: qtpim-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  /usr/bin/history-daemon:*** Error in `/usr/bin/history-daemon': double
  free or corruption (out): ADDR ***

Status in Canonical System Image:
  In Progress
Status in history-service package in Ubuntu:
  In Progress
Status in qtpim-opensource-src package in Ubuntu:
  New

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

  Rank 4 on errors.u.c, started with 0.1+15.04.20151020.1-0ubuntu1

  See also bug 1513261 which started with the same version

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

2015-11-11 Thread Brad Marshall

FWIW and a totally expected result, I just downgraded the LXC packages
on these hosts and redeployed, and things came up ok.

$ dpkg-query -W lxc
lxc 1.0.7-0ubuntu0.10

I don't think this changes anything, but just putting it here for
completeness.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515179] Re: [nexus7][bluez5] Unable to pair with Arc Touch Bluetooth

2015-11-11 Thread Yung Shen

** Description changed:

  Unable to pair arc touch bluetooth mouse with nexus 7.
  
  Steps to reproduce:
  
- 1. install bluez5 stack on nexus7(fresh flashed)
+ 1. install bluez5 stack on nexus7(fresh flashed), instruction: 
https://wiki.ubuntu.com/Bluetooth/TouchBluez5Testing
  2. adb shell into nexus7, then type following commands:
  $ bluetoothctl (entering interactive mode)
  $ discoverable on
  $ pairable on
  $ scan on
  $ devices (to see the device mac that you want to pair)
  $ pair 
  $ trust 
  $ connect 

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

Title:
  [nexus7][bluez5] Unable to pair with Arc Touch Bluetooth

Status in ubuntu-nexus7:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Unable to pair arc touch bluetooth mouse with nexus 7.

  Steps to reproduce:

  1. install bluez5 stack on nexus7(fresh flashed), instruction: 
https://wiki.ubuntu.com/Bluetooth/TouchBluez5Testing
  2. adb shell into nexus7, then type following commands:
  $ bluetoothctl (entering interactive mode)
  $ discoverable on
  $ pairable on
  $ scan on
  $ devices (to see the device mac that you want to pair)
  $ pair 
  $ trust 
  $ connect 

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

Note that the only different between root.tar.gz and root.tar.xz is the
last compression step, the uncompressed tarball is the same.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

root.tar.xz images are available for all series and all architectures
and are indeed on cloud-images.ubuntu.com

I've not checked them all myself but after the CPC team told me they
added them to their generated images, I did confirm (through LXD which
uses them) that at least precise, trusty, vivid, wily and xenial are all
available and working on x86 and armhf.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1393752] Re: missing symbols in libssl1.0.1f-1ubuntu2.7

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

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

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

Title:
  missing symbols in libssl1.0.1f-1ubuntu2.7

Status in openssl package in Ubuntu:
  Expired

Bug description:
  _CONF_new_data is not exported.

  The function definition is still in the headers:

  # grep -r _CONF_new_data /usr/include/
  /usr/include/openssl/conf_api.h:int _CONF_new_data(CONF *conf);

  The library itself does not export the symbol:
  $ readelf -Ws /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 | grep CONF_new
    1540: 0012f63084 FUNCGLOBAL DEFAULT   12 
NCONF_new@@OPENSSL_1.0.0

  LSB Relase:
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

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

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

[Touch-packages] [Bug 1473727] Re: No DNS servers after netboot

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

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

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

Title:
  No DNS servers after netboot

Status in resolvconf package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.04 / resolvconf 1.69ubuntu1.1

  When netbooting a xen VM, I see the following output:

   address: 192.168.1.180broadcast: 192.168.1.255netmask:
  255.255.255.0

   gateway: 192.168.1.1  dns0 : 192.168.1.1  dns1   :
  0.0.0.0

  So I know DHCP is working.

  However, resolv.conf doesn't get updated - the interface is set to
  manual as DHCP was handled at the initrd level.

  Please let me know how I can help get this fixed.

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

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

[Touch-packages] [Bug 1515446] Re: NFS shares in FSTAB no longer mount at boot

2015-11-11 Thread Steve Langasek

Opening a task on systemd as well for this.

When called early in boot, mount.nfs may fail because of any number of
problems with the network.  In this case, it appears it's being called
by systemd before /etc/resolv.conf has been set up, resulting in a
temporary DNS failure.  There is no way for mount.nfs to work when
invoked at this point in the boot.

So either systemd needs to more finely control the timing of the mount
call so that it definitely happens only after the network is up
(including /etc/resolv.conf configuration), or it needs to handle
retrying the mount in the case of a temporary failure.  (The latter is
what mountall did in Ubuntu 14.10 and earlier.)

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in nfs-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After a fresh install of 15.10, nfs shares no longer mount on boot.
  I'm using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu10
Candidate: 1:1.2.8-9ubuntu10
Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
 Loaded: loaded (/etc/fstab)
 Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

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

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

[Touch-packages] [Bug 1515446] Re: NFS shares in FSTAB no longer mount at boot

2015-11-11 Thread Steve Langasek

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

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in nfs-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After a fresh install of 15.10, nfs shares no longer mount on boot.
  I'm using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu10
Candidate: 1:1.2.8-9ubuntu10
Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
 Loaded: loaded (/etc/fstab)
 Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

2015-11-11 Thread Ian Booth

Stephane, you are right. We can change Juju to use mangle the output of
the cloud-image-query to add "root.tar.xz". Is this guaranteed to always
work for all series / arch? Are there the correct root.tar.xz files on
cloud-image.ubuntu.com ?

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515067] Re: Redunt requests for artist art

2015-11-11 Thread Victor Thompson

** Changed in: music-app
   Status: New => Confirmed

** Changed in: music-app
 Assignee: (unassigned) => Victor Thompson (vthompson)

** Changed in: music-app
   Status: Confirmed => In Progress

** Branch linked: lp:~vthompson/music-app/fix-1515067

** Changed in: music-app
   Importance: Undecided => Low

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

Title:
  Redunt requests for artist art

Status in Ubuntu Music App:
  In Progress
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  I'm seeing redundant requests in the thumbnailer for every artist. For
  example:

  thumbnailer-service: [00:33:58.397] "artist: Mamady Keïta/Afö (512,512): 
5.732672 [q: 4.476239, d: 1.065771] sec (MISS)"
  thumbnailer-service: [00:33:58.439] "artist: Mamady Keïta/ (512,512): 
5.774881 [q: 3.434976, d: 2.267816] sec (MISS)"

  thumbnailer-service: [00:33:56.041] "artist: Passport/ (512,512): 3.741614 
[d: 3.681184] sec (MISS)"
  thumbnailer-service: [00:33:56.144] "artist: Passport/Passport to Paradise 
(512,512): 3.480054 [d: 3.446207] sec (MISS)"

  thumbnailer-service: [00:34:02.958] "artist: Pink Floyd/The Dark Side Of The 
Moon [2011 - Remaster] (512,512): 10.288417 [q: 6.923973, d: 3.262566] sec 
(MISS)"
  thumbnailer-service: [00:34:04.315] "artist: Pink Floyd/ (512,512): 11.646238 
[q: 10.182878, d: 1.348939] sec (MISS)"

  For every artist, it appears that a request is sent for the artist
  with an empty album title, plus a request for the artist with an album
  title. This is not great because it results in two remote server
  accesses for each artist. This hammers the CPU and the network on the
  phone, as well as the server on dash.ubuntu.com.

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

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

[Touch-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink

2015-11-11 Thread Christopher M. Penalver

Hannes Bochmann, as per
http://support.displaylink.com/knowledgebase/articles/641668-known-
issues-with-displaylink-ubuntu-support only two HD monitors are
officially supported.

Despite this, you may be able to seek support from DisplayLink anyways
following http://support.displaylink.com/knowledgebase/articles/757047
-how-can-i-report-ubuntu-issues-to-displaylink . Could you please report
this to them and advise to the results?

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

Title:
  Mouse pointer flickers at using DisplayLink

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Using the new official DisplayLink driver for Ubuntu from
  http://www.displaylink.com/downloads/ubuntu.php for my USB-
  DisplayLink-Adapter causes on the two main monitors (DisplayPort and
  internal monitor) a flickering mouse. The pointer doesn't flicker on
  third monitor (DisplayLink monitor).

  This also seems to be related to this bug:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1485682

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Thu Oct 29 08:29:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:503c]
  InstallationDate: Installed on 2015-09-25 (33 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: LENOVO 20DT0003GE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic 
root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JDET50WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: Intel powered classmate PC
  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:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DT0003GE
  dmi.product.version: ThinkPad L450
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct 29 07:45:59 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9782 
   vendor ENC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Touch-packages] [Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)

2015-11-11 Thread Cheryl Jennings

Bug #1515463 reveals that this change broke Juju.  Marking as
verification failed.

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

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

Title:
  New upstream bugfix release 1.0.8 (LXC MRE)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  We have released LXC 1.0.7 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

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

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

[Touch-packages] [Bug 1436973] Re: konsole crashes on closing due to kuniqueapplication

** Bug watch removed: KDE Bug Tracking System #344918
   https://bugs.kde.org/show_bug.cgi?id=344918

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

Title:
  konsole crashes on closing due to kuniqueapplication

Status in KDE Base:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src source package in Vivid:
  Confirmed
Status in qtbase-opensource-src source package in Wily:
  Confirmed

Bug description:
  https://bugs.kde.org/show_bug.cgi?id=344920

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1436973/+subscriptions

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

[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

** Changed in: bluez (Ubuntu)
Milestone: vivid-updates => None

** Changed in: pulseaudio (Ubuntu)
Milestone: vivid-updates => None

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Confirmed
Status in pulseaudio source package in Vivid:
  Confirmed

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

Well, the string returned by ubuntu-cloudimg-query already requires
mangling to be usable with the lxc-ubuntu-cloud template (as we do
inside the ubuntu-cloud template).

As there are no full cloud images compressed using .tar.xz, ubuntu-
cloudimg-query will continue to return .tar.gz and it's up to whatever
piece of software currently mangles its return value to the .root.tar.gz
equivalent to instead mangle it to .root.tar.xz (as I did in the ubuntu-
cloud template).

Anyway, as I said, I'll be changing the tar commands so they don't care
about the compression algorithm, that should make transitioning much
easier.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

2015-11-11 Thread Ian Booth

Stephane,

Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query 
for that.
So this utility will need to be changed. It is in the cloud-image-utils package.

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

Oh yeah, I can see how this is going to be a problem.

I'll look at changing the code path to use auto-detected compression
rather than specific one.

The reason for this change in the first place is that the .tar.gz images
will be deprecated in favor for .tar.xz, so I'd recommend JuJu also
switch to .tar.xz at some point soon (I don't believe the cloud team has
set a timeframe for phasing out tar.gz yet, but it's planned).

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1436973] Re: konsole crashes on closing due to kuniqueapplication

** Package changed: konsole (Ubuntu) => qtbase-opensource-src (Ubuntu)

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Medium => High

** Changed in: qtbase-opensource-src (Ubuntu Wily)
Milestone: ubuntu-15.10 => wily-updates

** Changed in: qtbase-opensource-src (Ubuntu Vivid)
   Importance: Medium => High

** Changed in: qtbase-opensource-src (Ubuntu Wily)
   Importance: Medium => High

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

Title:
  konsole crashes on closing due to kuniqueapplication

Status in KDE Base:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src source package in Vivid:
  Confirmed
Status in qtbase-opensource-src source package in Wily:
  Confirmed

Bug description:
  https://bugs.kde.org/show_bug.cgi?id=344920

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/1436973/+subscriptions

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

[Touch-packages] [Bug 1515463] [NEW] Broken juju LXC deployments

2015-11-11 Thread Brad Marshall

Public bug reported:

I've just tried using juju to deploy to a container with trusty-proposed
repo enabled, and I get an error message about 'failed to retrieve the
template to clone'.  The underlying error appears to be:

  tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
  xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
  Error is not recoverable: exiting now;

This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.

The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.

This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file.  You can see what juju is
providing from:

  $ ubuntu-cloudimg-query trusty released amd64 --format %{url}
  
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

>From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
  Installed: 1.0.8-0ubuntu0.1
  Candidate: 1.0.8-0ubuntu0.1
  Version table:
 *** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
100 /var/lib/dpkg/status

>From the host running juju:
$ apt-cache policy juju-core
juju-core:
  Installed: 1.22.8-0ubuntu1~14.04.1
  Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
  Version table:
 1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
 *** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status

All machine involved are running trusty:

$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04

Please let me know if you need any more information.

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


** Tags: canonical-bootstack

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  New

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1436973] [NEW] konsole crashes on closing due to kuniqueapplication

You have been subscribed to a public bug:

https://bugs.kde.org/show_bug.cgi?id=344920

** Affects: kde-baseapps
 Importance: High
 Status: Fix Released

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: High
 Status: Confirmed

** Affects: qtbase-opensource-src (Ubuntu Vivid)
 Importance: Medium
 Status: Confirmed

** Affects: qtbase-opensource-src (Ubuntu Wily)
 Importance: Medium
 Status: Confirmed


** Tags: kubuntu
-- 
konsole crashes on closing due to kuniqueapplication
https://bugs.launchpad.net/bugs/1436973
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu.

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

[Touch-packages] [Bug 1436952] Re: X crashes on some runs of Kubuntu live image returning in SDDM login

** Changed in: xorg (Ubuntu)
Milestone: ubuntu-15.04 => None

** Changed in: xorg (Ubuntu Vivid)
Milestone: ubuntu-15.04 => None

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

Title:
  X crashes on some runs of Kubuntu live image returning in SDDM login

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg source package in Vivid:
  Incomplete

Bug description:
  Running a Kubuntu vivid beta 2 live image on my laptop I get the
  ubituity-dm screen.  I press "Try Kubuntu" and it takes me to the SDDM
  login screen.  Autologin should work and trying the exact same USB
  drive on a different computer it does reliable autologin.  It's also
  reported to work fine on Virtualbox.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1436952/+subscriptions

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

[Touch-packages] [Bug 1446231] Re: console-setup prompts for keyboard layout during upgrade from Utopic to Vivid desktop

** No longer affects: ubiquity (Ubuntu)

** No longer affects: ubiquity (Ubuntu Vivid)

** Changed in: console-setup (Ubuntu)
Milestone: ubuntu-15.04 => None

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

Title:
  console-setup prompts for keyboard layout during upgrade from Utopic
  to Vivid desktop

Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Vivid:
  Fix Released

Bug description:
  There is a debconf prompt for keyboard-configuration during an upgrade
  from a stock Utopic in French to Vivid (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: keyboard-configuration 1.108ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 20 14:13:50 2015
  InstallationDate: Installed on 2013-09-03 (593 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1345682] Re: fsck on 24TB ext4 keeps crashing

2015-11-11 Thread Phillip Susi

I just tried a fresh install of 14.04.2 in a vm with a 20 tb virtual
disk and fsck seemed to work fine.  It might be specific to your disk
contents.  If you can reproduce this, please capture an image of the
filesystem metadata with e2image -r ( and bzip2 that ) and attach it and
I can try running on that.

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

Title:
  fsck on 24TB ext4 keeps crashing

Status in e2fsprogs package in Ubuntu:
  Incomplete

Bug description:
  date; fsck -vy /dev/mapper/raid61p1 ;date
  Thu Jul 17 11:54:21 PDT 2014
  fsck from util-linux 2.20.1
  I can't get my ext4 24TB to fsck clean. there came a whole bunch of file stat 
problems after a clean reboot.
  I tried 3 times so far, and each does something like segfault. I looked 
twice, and the errors were different,
  but was able to capture one output. The system has 6GB ram, and it used up 
all the memory. ended up adding 25GB
  of swap as fsck seems to use up a huge amount of memory. After a long while, 
usually after mem use is >90%,
  I come back to see the fsck has crashed and file system is still not clean.

  The reboot was clean and should not  have caused any corruption. the
  system is using ubuntu-14.04

  # uname -a
  Linux gigabyte133 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
  root@gigabyte133:~# 

  I had to use the 64 bit version since the 32 bit version I couldn't get more 
than 15TB file system built and read 
  that there were compatibility problems between 32bit version with the -O 
64bit and the 64 bit version so just
  built the whole thing in 64 bit ubuntu..

  
  e2fsck 1.42.9 (4-Feb-2014)

  
  /dev/mapper/raid61p1 contains a file system with errors, check forced.
  Pass 1: Checking inodes, blocks, and sizes
  Inode 203167820 has compression flag set on filesystem without compression 
support.  Clear? yes

  Signal (11) SIGSEGV si_code=SI_KERNEL fault addr=(nil)
  fsck.ext4[0x4266f1]
  /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0)[0x7fd38d087ff0]
  /lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_rb_next+0x23)[0x7fd38dc7bc43]
  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x10670)[0x7fd38dc5e670]
  fsck.ext4[0x4100f6]# lsb_release -va
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11c3d)[0x7fd38dc5fc3d]
  /lib/x86_64-linux-gnu/libext2fs.so.2(+0x11f78)[0x7fd38dc5ff78]
  
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_block_iterate3+0xa13)[0x7fd38dc60b13]
  fsck.ext4[0x4115c4]
  fsck.ext4[0x412699]
  fsck.ext4[0x412761]
  
/lib/x86_64-linux-gnu/libext2fs.so.2(ext2fs_get_next_inode_full+0x59)[0x7fd38dc6c9a9]
  fsck.ext4(e2fsck_pass1+0x8d8)[0x4130c8]
  fsck.ext4(e2fsck_run+0x52)[0x40deb2]
  fsck.ext4(main+0xd27)[0x40a0e7]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fd38d072ec5]
  fsck.ext4[0x40bde6]
  Thu Jul 17 15:55:01 PDT 2014

  # lsb_release -va
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04 LTS
  Release:14.04
  Codename:   trusty

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Jul 19 18:49:32 2014
  InstallationDate: Installed on 2014-07-11 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1363482] Re: ubuntu-keyring includes 1024D keys

2015-11-11 Thread Colin Watson

I've added double-signing support to cdimage, and re-signed everything
with both old and new keys.  For good measure I've also updated
https://help.ubuntu.com/community/VerifyIsoHowto.

** Changed in: ubuntu-cdimage
   Status: New => Fix Released

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

Title:
  ubuntu-keyring includes 1024D keys

Status in Ubuntu CD Images:
  Fix Released
Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-keyring as shipped in trusty contains old 1024D keys dating
  back to 2004 which are still being trusted for the main archive:

   % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg | grep 1024D
  pub  1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key 

  pub  1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key 


  Given that newer 4096R keys are present and have been in precise
  (through -updates) and trusty, it seems to be about time to drop the
  older keys. (In the hope that apt does not chose on signatures it
  cannot verify, otherwise the publisher would need to stop signing with
  the old key as well.)

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

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

[Touch-packages] [Bug 1511704] Re: Xorg crash (probably on window resize)

2015-11-11 Thread nimu

penalvch, thank you for your help.

I don't want to risk a BIOS update for now, so I cannot tell you if the
bug is somehow BIOS-related.

Instead, I have decided to try an update of my graphics drivers using this repo:
ppa:oibaf/graphics-drivers

This "fixes" the crash problem.

So, while it may still be true, that this bug is somehow BIOS-related,
the fact that I am not experiencing any crashes since I've updated the
graphics drivers suggests that there probably is something wrong with
the graphics drivers that Ubuntu 15.10 uses by default.

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

Title:
  Xorg crash (probably on window resize)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Whole UI crashes and returns to login screen. All open applications
  are closed (the whole session is gone). Crashes happen irregularly but
  seem to be provoked by window resizes or window animations

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  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 Oct 30 12:49:07 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Device [10cf:16c2]
  InstallationDate: Installed on 2015-05-22 (160 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: FUJITSU LIFEBOOK A532
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=cc91c7ea-2cb7-4ac7-ae59-560aa09e6167 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2012
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 2.05
  dmi.board.name: FJNBB2A
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion2.05:bd09/28/2012:svnFUJITSU:pnLIFEBOOKA532:pvr:rvnFUJITSU:rnFJNBB2A:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK A532
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Oct 30 12:30:17 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13890 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-11-11 Thread Tony Espy

Here's a script that calls dbus-monitor with the correct match rules in
order to catch AccessPointAdded and Removed signals, as well as
PropertiesChanged signals for the Device.Wireless 'AccessPoints'
property.

** Attachment added: "monitor-aps.sh"
   
https://bugs.launchpad.net/ubuntu-rtm/+source/location-service/+bug/1480877/+attachment/4517317/+files/monitor-aps.sh

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in location-service package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-11-11 Thread Tony Espy

@taiebot65

I don't think this is related to bug #1462664.   This is specifically
related to the number of processes watching individual network-manager
access point objects, and the fact that these processes leak match
rules, so they continue to add match rules to dbus for new access
points, but never cleanup the old rules for access points that
disappear.  Also, per an earlier comment, as a vivid fix related to the
ubuntu-software-center relaxed the per process dbus match limits to 5000
( from 512 ), when all of these processes max out, the total is
something like 40k rules that DBus has to match for every incoming
message on the bus.

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in location-service package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

2015-11-11 Thread Tony Espy

@Pat

We might want to hotfix this once we come to fully understand it( and I
think we're getting close ).

While working with tvoss a fixes to  location-services, we realized that
by default, the get-all-match.py script only outputs warnings.  While
reviewing a test run from tvoss, I didn't see any rules at all for
posclientd or slpgwd, as he'd fixed the warnings.  As I wanted to check
whether or not the leak was still there, I realized I needed to specify
"--all" with the script.

This revealed a whole other group of processes that also were monitoring
AccessPoint signals.  I hadn't noticed them when first running the
script, as I was just looking at the default warnings output, and these
other processes appear to have specified the rules cleanly.   It also
appears that these processes are also leaking match rules for the
AccessPoint signals as well.

In addition to posclientd, and slpgwd ( tvoss has removed the watches
for ubuntu-location-servicesd ) the following processes are involved:

 - msyncd ( part of bueto-syncfw )
 - unity8
 - unity8-dash
 - sync-monitor
 - maliit-server 

So, when fully maxed out, these too can reach 5k match rules each (
that's 25k for the five of them ).  I just verified that they're all
north of 1000 match rules on my krillin just now.   This explains why
after killing the location-service processes, we still were seeing a
brief hiccup every time a WiFi scan occurs.

I also noticed that mission-control-5 listed five AccessPoint match
rules only, so that while it's listening, it's not leaking...

All of the above processes except mission-control-5 use
QtNetworkSession, whereas mission-control-5 uses nm-glib directly.

I've also verified on krillin that AccessPointAdded and Removed signals
are being generated when scan occur, and they seem to make sense.  One
or more of each signals are received, then a PropertiesChanged signal is
fired for the AccessPoints property itself, with the changes indicated
by the signals now applied.  As it appears none of the AcessPoints are
ever being removed from these match rules, my guess is that this is a
bug in QNetworkSession vs. NM.  I've monitored NM and when scanning
occurs, APs are continually added/removed.  The list can grow or shrink
by 3-10 APs at a time.  Of course this doesn't absolutely verify that
the signals were sent or received.

I'll attach a script which uses dbus-monitor to watch just the signals
sent to the Device.Wireless interface, which should result in just
monitoring AccessPointAdded/Removed and the associated PropertiesChanged
for the AccessPoints property.

Finally, we urgently need to fix the remaining leaks, but we also
probably need to have someone determine whether there's any way to get
rid of these rules completely.  Does maliit-server really need to see
'LastSeen' property changes from individual access points???  Do any of
these processes?

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in location-service package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

2015-11-11 Thread Peter Bittner

Just wanted to confirm that this is still causing me pain daily on my bq
Aquaris E5 (OTA-7). I can not at all (or hardly) use any phone call
features (e.g. transfering to the loudspeaker to do hands-free talking
is an acrobatic act, because the screen insists in turning black
immediately again, e.g. I'm pressing the lock button on the right upper
side of the phone).

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

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

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

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

2015-11-11 Thread kevin gunn

ok, went back to 159, verified no issue after several reboots.
updated only qtmir/qtubuntu to the very latest and the issue appeared on the 
first reboot.

so these 2 changes are the suspects
https://code.launchpad.net/~unity-team/qtmir/revert-occlusion-detection/+merge/277049
https://code.launchpad.net/~unity-team/qtubuntu/revert-occlusion-detection/+merge/277048

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

** No longer affects: unity8 (Ubuntu)

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

** Changed in: qtubuntu
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => kevin gunn (kgunn72)

** Changed in: qtubuntu
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Nick Dedekind (nick-dedekind)

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

Title:
  After a boot the dash doesn't display until touched

Status in Canonical System Image:
  Confirmed
Status in qtubuntu:
  New
Status in qtmir package in Ubuntu:
  New

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

[Touch-packages] [Bug 1403955] Re: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0

2015-11-11 Thread PshemK

The bug is still present in 1.25.

The fact that it only manifests itself during the subsequent machine
reboots (and not during the initial build) makes it more difficult to
troubleshoot - services that worked before reboot do not work after.

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

Title:
  DHCP's "Option interface-mtu 9000" is being ignored on bridge
  interface br0

Status in juju-core:
  Triaged
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  In an env with jumbo frames enabled, and using MAAS as DHCP server,
  the client receives the following IPv4 lease:

  $ cat /var/lib/dhcp/dhclient.br0.leases
  lease {
    interface "br0";
    fixed-address 10.230.20.26;
    filename "pxelinux.0";
    option subnet-mask 255.255.248.0;
    option dhcp-lease-time 43200;
    option routers 10.230.16.1;
    option dhcp-message-type 5;
    option dhcp-server-identifier 10.230.20.1;
    option domain-name-servers 10.230.20.1;
    option interface-mtu 9000;
    option broadcast-address 10.230.23.255;
    option domain-name "ctsstack.qa.1ss";
    renew 3 2014/12/17 16:48:15;
    rebind 3 2014/12/17 21:52:09;
    expire 3 2014/12/17 23:22:09;
  }

  The interfaces show the following config after boot:

  $ ifconfig br0
  br0   Link encap:Ethernet  HWaddr a0:d3:c1:01:9d:58
    inet addr:10.230.20.26  Bcast:10.230.23.255  Mask:255.255.248.0
    inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:68713489 (68.7 MB)  TX bytes:213710979 (213.7 MB)

  $ ifconfig eth0
  eth0  Link encap:Ethernet  HWaddr a0:d3:c1:01:9d:58
    inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
    TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2320560616 (2.3 GB)  TX bytes:3562885157 (3.5 GB)
    Interrupt:32

  
  "option interface-mtu 9000;" from the lease file is being ignored by br0. 
Could it be related to eth0 MTU size? If that's the case, shouldn't both 
interfaces be updated?

  Other info:

  $ brctl show br0
  bridge name   bridge id   STP enabled interfaces
  br0   8000.a0d3c1019d58   no  eth0

  $ cat /etc/network/eth0.config
  iface eth0 inet manual

  auto br0
  iface br0 inet dhcp
    bridge_ports eth0

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions

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

[Touch-packages] [Bug 1389215] Re: Brightness controls are not working in Unity / Xorg because of Nvidia proprietary driver.

2015-11-11 Thread Hans Deragon

This LTS Enablement Stack scares me a lot; I do not want to screw my
system.  So if I understand you correctly, I should return to my
previous state with the following command, right?

sudo apt-get remove linux-generic-lts-vivid xserver-xorg-core-lts-vivid
xserver-xorg-lts-vivid xserver-xorg-video-all-lts-vivid xserver-xorg-
input-all-lts-vivid libwayland-egl1-mesa-lts-vivid libgl1-mesa-glx-lts-
vivid libgl1-mesa-glx-lts-vivid:i386 libglapi-mesa-lts-vivid:i386

If any of you work for Canonical, please suggest that a "Talk" page be
implemented on the Wiki like Wikipedia has.  I would like to communicate
with the people who wrote this page so I could ask them to officially
endorse this rollback procedure.

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

Title:
  Brightness controls are not working in Unity / Xorg because of Nvidia
  proprietary driver.

Status in Nvidia:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Brightness controls are not working in Unity / Xorg.  When pressing
  the keys  and  on my Lenovo W510, I see the
  indicator on the screen showing the level of brightness changing, so
  key mapping is not the problem.  However, the brightness is not
  changing.

  On the kernel level, I have the single following device:

  # cd /sys/class/backlight
  # ls -l
  total 0
  lrwxrwxrwx 1 root root 0 Nov  3 17:16 acpi_video0 -> 
../../devices/pci:00/:00:03.0/:01:00.0/backlight/acpi_video0

  When playing with the  and , the value of
  /sys/class/backlight/brightness changes accordingly.  The screen
  brightness does not change.

  Performing:

  # echo 10 >brightness

  ...does not have any effect (regardless of the value provided, 10
  being just an example).

  WORKAROUND

  There is an odd workaround.  Simply go to the console using
   and using the  and  keys,
  brightness then changes.  Return to Unity / Xorg with 
  and the selected brightness persists.

  NON WORKING WORKAROUND

  On the web, I read that adding:

  Option "RegistryDwords" "EnableBrightnessControl=1"'

  in xorg.conf might fix the problem.  I do not have an xorg and when I
  let the proprietary Nvidia driver generate one and add this option, X
  does not start anymore.

  Ubuntu 14.04.1 LTS with latest updates as of this writing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,place,put,snap,resize,move,regex,session,vpswitch,imgpng,gnomecompat,text,ring,grid,mousepoll,animation,unitymtgrabhandles,wall,expo,ezoom,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov  4 07:38:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-39-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-32-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-39-generic, x86_64: installed
   tp-smapi, 0.41, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo Device [17aa:2145]
  InstallationDate: Installed on 2014-11-01 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4318CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic 
root=UUID=994f9c2c-f967-472e-ace3-23cd620ec702 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  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:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.v

[Touch-packages] [Bug 1427275] Re: clean cloud images of python2

2015-11-11 Thread Barry Warsaw

Just tested with Xenial server, with no additional packages installed.
vim is the last thing keeping libpython2.7 on the server image.  Verify
with `apt-get purge python2.7 libpython2.7`

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

Title:
  clean cloud images of python2

Status in cloud-utils package in Ubuntu:
  Fix Released
Status in landscape-client package in Ubuntu:
  Fix Committed
Status in software-properties package in Ubuntu:
  Fix Released
Status in vim package in Ubuntu:
  Confirmed
Status in cloud-utils source package in Vivid:
  Fix Released
Status in vim package in Debian:
  New

Bug description:
  cloud-init is now running in python3 in the cloud images in vivid.
  We'd like to remove the remaining few python2 packages.
  P

  From a 20150228 image, that looks like:
  $ sudo apt-get remove python
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    cloud-guest-utils cloud-init landscape-client landscape-common python
    python-apt python-characteristic python-chardet python-configobj
    python-debian python-gdbm python-idna python-openssl python-pam
    python-pkg-resources python-pyasn1 python-pyasn1-modules python-pycurl
    python-serial python-service-identity python-six python-twisted-bin
    python-twisted-core python-twisted-web python-zope.interface
    update-notifier-common
  0 upgraded, 0 newly installed, 26 to remove and 17 not upgraded.
  After this operation, 18.1 MB disk space will be freed.
  Do you want to continue? [Y/n]

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: landscape-client 14.12-0ubuntu1
  ProcVersionSignature: User Name 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Mon Mar  2 15:56:05 2015
  Ec2AMI: ami-01cc
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: aki-0002
  Ec2Ramdisk: ari-0002
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: landscape-client
  UpgradeStatus: No upgrade log present (probably fresh install)

  Related bugs:
   * Bug 1497030: [FFE] Cloud Images include landscape-client (Python2.7)

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

2015-11-11 Thread Arnett Carroll

arnett@UbunutuLinuxLTS-Gateway-NE56R41u-NE56R:~$ sudo apt-get --purge 
autoremove[sudo] password for arnett: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-3.13.0-68-generic (3.13.0-68.111) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.13.0-68-generic
vmlinuz(/boot/vmlinuz-3.13.0-68-generic
) points to /boot/vmlinuz-3.13.0-68-generic
 (/boot/vmlinuz-3.13.0-68-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-3.13.0-68-generic.postinst line 491.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-68-generic 
/boot/vmlinuz-3.13.0-68-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-68-generic 
/boot/vmlinuz-3.13.0-68-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-68-generic 
/boot/vmlinuz-3.13.0-68-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-68-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-68-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-3.13.0-68-generic.postinst line 1025.
E: Sub-process /usr/bin/dpkg returned an error code (1)
arnett@UbunutuLinuxLTS-Gateway-NE56R41u-NE56R:~$ sudo apt-get --purge autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up linux-image-3.13.0-68-generic (3.13.0-68.111) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.13.0-68-generic
vmlinuz(/boot/vmlinuz-3.13.0-68-generic
) points to /boot/vmlinuz-3.13.0-68-generic
 (/boot/vmlinuz-3.13.0-68-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-3.13.0-68-generic.postinst line 491.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-68-generic 
/boot/vmlinuz-3.13.0-68-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-68-generic 
/boot/vmlinuz-3.13.0-68-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-68-generic 
/boot/vmlinuz-3.13.0-68-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-68-generic

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-68-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-3.13.0-68-generic.postinst line 1025.
dpkg: error processing package linux-image-3.13.0-68-generic (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of 
linux-image-extra-3.13.0-68-generic:
 linux-image-extra-3.13.0-68-generic depends on linux-image-3.13.0-68-generic; 
however:
  Package linux-image-3.13.0-68-generic is not configured yet.

dpkg: error processing package linux-image-extra-3.13.0-68-generic 
(--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-3.13.0-68-generic; however:
  Package linux-image-3.13.0-68-generic is not configured yet.
 linux-image-generic depends on linux-image-extra-3.13.0-68-generic; however:
  Package linux-image-extra-3.13.0-68-generic is not configured yet.

dpkg: error processing package linux-image-generic (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problemsNo apport report written because the error message 
indicates its a followup error from a previous failure.
No apport report written because the error message indicates its a followup 
error from a previous failure.

  No apport report written because MaxReports is 
reached already
 E: Sub-process /usr/bin/dpkg returned an 
error code (1)
arnett@UbunutuLinuxLTS-Gateway-NE56R41u-NE56R:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  flashplugin-installer libnautilus-extension1a nautilus nautilus-data
  wpasupplicant
5 upgraded, 0 newly installed, 0 to remove an

[Touch-packages] [Bug 1452004] Re: Pulseaudio network stream gets recurrung short interruptions

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

Title:
  Pulseaudio network stream gets recurrung short interruptions

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I use pulseaudio to stream music over wifi to a Rasberry Pi 2 at 192kb. 
Exactly every 5 minutes there is a short dropout in the stream. This is always 
followed by the following warning in plamashell:
  networkmanager-qt: void 
NetworkManager::AccessPointPrivate::propertiesChanged(const QVariantMap&) 
Unhandled property "LastSeen"
  which comes from the corresponding function in accesspoint.cpp. See (line 
211):
  
http://api.kde.org/frameworks-api/frameworks5-apidocs/networkmanager-qt/html/accesspoint_8cpp_source.html

  I am running on Vivid with kubuntu-ppa-ubuntu-backports-vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  5 20:56:09 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-20 (105 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.1.1.1 dev wlan0  proto static  metric 1024 
   10.1.1.0/24 dev wlan0  proto kernel  scope link  src 10.1.1.2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (11 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-01-22T14:45:53.513596
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
moni3ecf8bc2-98cd-4298-a963-d77d9d1aca22  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   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/1452004/+subscriptions

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

[Touch-packages] [Bug 1452004] Re: Pulseaudio network stream gets recurrung short interruptions

2015-11-11 Thread Scarlett Clark

Happening for me with the latest 5.4.3 in Wily.. off to hunt for an
upstream bug.

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

Title:
  Pulseaudio network stream gets recurrung short interruptions

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I use pulseaudio to stream music over wifi to a Rasberry Pi 2 at 192kb. 
Exactly every 5 minutes there is a short dropout in the stream. This is always 
followed by the following warning in plamashell:
  networkmanager-qt: void 
NetworkManager::AccessPointPrivate::propertiesChanged(const QVariantMap&) 
Unhandled property "LastSeen"
  which comes from the corresponding function in accesspoint.cpp. See (line 
211):
  
http://api.kde.org/frameworks-api/frameworks5-apidocs/networkmanager-qt/html/accesspoint_8cpp_source.html

  I am running on Vivid with kubuntu-ppa-ubuntu-backports-vivid.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  5 20:56:09 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-20 (105 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 10.1.1.1 dev wlan0  proto static  metric 1024 
   10.1.1.0/24 dev wlan0  proto kernel  scope link  src 10.1.1.2 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (11 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-01-22T14:45:53.513596
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
moni3ecf8bc2-98cd-4298-a963-d77d9d1aca22  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   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/1452004/+subscriptions

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

2015-11-11 Thread kevin gunn

scratch that - retested fresh 161 and i see the issue

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

Title:
  After a boot the dash doesn't display until touched

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

[Touch-packages] [Bug 1515012] Re: SIM not selected in header on incoming call

This bug was fixed in the package dialer-app -
0.1+16.04.2015.1-0ubuntu1

---
dialer-app (0.1+16.04.2015.1-0ubuntu1) xenial; urgency=medium

  * Make sure the account label is selected on the live call. (LP:
#1515012)

 -- Gustavo Pichorim Boiko   Wed, 11 Nov
2015 20:25:42 +

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

Title:
  SIM not selected in header on incoming call

Status in Canonical System Image:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Fix Released

Bug description:
  latest rc-proposed
  When you receive a call, the dialer shows the correct SIM label in the header 
but it is not selected. It should be selected (i.e. should have orange 
highlighting).

  See attached screenshot

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

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

[Touch-packages] [Bug 1515379] Re: rsyslog stopped too early during shutdown/reboot

2015-11-11 Thread Simon Déziel

** Summary changed:

- rsyslog not omitted by sendsigs when managed by upstart/systemd
+ rsyslog stopped too early during shutdown/reboot

** Description changed:

+ The upstart job managing rsyslog includes a "stop on runlevel [06]"
+ clause that makes it terminate very early during the shutdown/reboot
+ sequence.
+ 
+ This prevents proper logging of the shutdown/reboot sequence. Since this
+ logging can be crucial rsyslog should be kept running for as long as
+ possible. As such, I believe that the "stop on" clause should be dropped
+ from the upstart job definition.
+ 
+ 
+ Original description:
+ 
  When rsyslog is managed by the init script, it symlinks its PID to
  /run/sendsigs.omit.d so that we can capture logs very late during the
  shutdown sequence:
  
  sendsigs_omit() {
-   OMITDIR=/run/sendsigs.omit.d
-   mkdir -p $OMITDIR
-   ln -sf $PIDFILE $OMITDIR/rsyslog
+   OMITDIR=/run/sendsigs.omit.d
+   mkdir -p $OMITDIR
+   ln -sf $PIDFILE $OMITDIR/rsyslog
  }
  
  When rsyslog is managed by upstart this functionality is lost. I quickly
  looked in Xenial's package and it seems this functionality is also
  absent when run through systemd.
  
- 
- P.S.: I'm trying to investigate a reboot sequence taking ~forever but for 
which I have 0 log of the actual shutdown sequence:
+ P.S.: I'm trying to investigate a reboot sequence taking ~forever but
+ for which I have 0 log of the actual shutdown sequence:
  
  Nov 10 22:00:46 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1603" x-info="http://www.rsyslog.com";] exiting on signal 15.
  Nov 10 22:55:25 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1935" x-info="http://www.rsyslog.com";] start
  
  This 55 minutes gap caused of lot of stress as the machine is a big iron
  in a DC far away.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.6
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 14:14:54 2015
  InstallationDate: Installed on 2014-01-26 (653 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

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

Title:
  rsyslog stopped too early during shutdown/reboot

Status in rsyslog package in Ubuntu:
  New

Bug description:
  The upstart job managing rsyslog includes a "stop on runlevel [06]"
  clause that makes it terminate very early during the shutdown/reboot
  sequence.

  This prevents proper logging of the shutdown/reboot sequence. Since
  this logging can be crucial rsyslog should be kept running for as long
  as possible. As such, I believe that the "stop on" clause should be
  dropped from the upstart job definition.

  
  Original description:

  When rsyslog is managed by the init script, it symlinks its PID to
  /run/sendsigs.omit.d so that we can capture logs very late during the
  shutdown sequence:

  sendsigs_omit() {
    OMITDIR=/run/sendsigs.omit.d
    mkdir -p $OMITDIR
    ln -sf $PIDFILE $OMITDIR/rsyslog
  }

  When rsyslog is managed by upstart this functionality is lost. I
  quickly looked in Xenial's package and it seems this functionality is
  also absent when run through systemd.

  P.S.: I'm trying to investigate a reboot sequence taking ~forever but
  for which I have 0 log of the actual shutdown sequence:

  Nov 10 22:00:46 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1603" x-info="http://www.rsyslog.com";] exiting on signal 15.
  Nov 10 22:55:25 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1935" x-info="http://www.rsyslog.com";] start

  This 55 minutes gap caused of lot of stress as the machine is a big
  iron in a DC far away.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.6
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 14:14:54 2015
  InstallationDate: Installed on 2014-01-26 (653 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  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/1515379/+subscriptions

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

2015-11-11 Thread kevin gunn

OK, verified that Pat didn't see this on 161, i flashed on MX4 and i didn't see 
either.
all the qtmir/qtubuntu updates were already in 161 so i updated and witnessed 
the problem

here were the list of updates

The following packages will be upgraded:
  coreutils dialer-app indicator-sound language-pack-touch-ast 
language-pack-touch-bg language-pack-touch-bs
  language-pack-touch-ca language-pack-touch-cs language-pack-touch-da 
language-pack-touch-de
  language-pack-touch-el language-pack-touch-en language-pack-touch-es 
language-pack-touch-eu
  language-pack-touch-fi language-pack-touch-fr language-pack-touch-gl 
language-pack-touch-he
  language-pack-touch-hu language-pack-touch-id language-pack-touch-it 
language-pack-touch-ja
  language-pack-touch-ko language-pack-touch-lt language-pack-touch-lv 
language-pack-touch-ms
  language-pack-touch-nb language-pack-touch-nl language-pack-touch-oc 
language-pack-touch-pl
  language-pack-touch-pt language-pack-touch-ro language-pack-touch-ru 
language-pack-touch-sk
  language-pack-touch-sl language-pack-touch-sr language-pack-touch-sv 
language-pack-touch-tr
  language-pack-touch-ug language-pack-touch-uk language-pack-touch-zh-hans 
language-pack-touch-zh-hant
  libubuntu-location-service2 ubuntu-location-service-bin

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

Title:
  After a boot the dash doesn't display until touched

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

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

2015-11-11 Thread Dave Chiluk

Subscribing sponsors and sru team, as both are still necessary for
Trusty.

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

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

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

Bug description:
[Impact]

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

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

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

[Test Case]

* $ mount

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

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

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

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

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

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

[Regression Potential]

* Patch is upstreamed.

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

[Other Info]

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

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

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

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

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

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

for example.
$ mount

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

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

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

[Touch-packages] [Bug 1512454] Re: Refresh change colours

2015-11-11 Thread Dominik

the full computer model that I found is: Samsung np-r540-ja07pl

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

Title:
Refresh change colours

Status in xorg package in Ubuntu:
Incomplete

Bug description:
I had experienced few times that refreshing window causes some places to lose
right information about colour. I mean that colours change to different for
e.g. grey become yellowish, and strips are visible. Also in web browser some
letters disappear.
It is happening not often, maybe about 2/3 times per month. I am using Ubuntu
14.04, with following Hardware:
Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System
Is 64 bit version. 3,7GiB Ram.
I'm using two screens with different size. First one is built-in laptop
screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with
resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and
before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until
now I notice this bug only when on firefox so I thought it could be something
wrong with firefox, but today I noticed this bug on Terminal Window. I cannot
really provide information how to create this bug - twice it happened on
facebook when board automatically refreshed, and today it happened on Terminal
when I clicked on firefox. I tried to repeat the problem with terminal, using
the same commands but without positive results. Bug is fixing when window /
application getting refreshed - scrolling up / down or moving window on screen
fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen
with animation that everything becoming white and going to normal imag
e)
I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or
something - log finishing after screen setting up.
I attached picture with example in firefox window (screenshots was bit edited
- facebook's board, chat and chat list been deleted).
---
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.18
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
DistUpgraded: Fresh install
DistroCodename: trusty
DistroRelease: Ubuntu 14.04
DistroVariant: ubuntu
DkmsStatus: virtualbox, 4.3.10: added
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0046]
(rev 18) (prog-if 00 [VGA controller])
Subsystem: Samsung Electronics Co Ltd Device [144d:c06a]
InstallationDate: Installed on 2015-10-17 (23 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730
Package: xorg 1:7.7+1ubuntu8.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic
root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
Tags: trusty ubuntu compiz-0.9
Uname: Linux 3.19.0-32-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 03/24/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04JV.M012.20100324.hkk
dmi.board.asset.tag: Tag 12345
dmi.board.name: R530/R730
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: R530/R730
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A

[Touch-packages] [Bug 1491612] Re: doesn't scan for available wifi networks often enough + no way to manually force a scan

2015-11-11 Thread Brad Kowalczyk

This one has annoyed me for quite a while now (well before 15.x). Having
to disable/enable wifi to get network manager applet to see the wifi
ssid (or wait quit a while) is a bit of a pain and shouldn't be
necessary for a modern OS. Also, the fact that there is no way anywhere,
either in network-manager applet or in network manager itself (network
settings), to force a refresh really sucks.

My network manager applet disappeared for a while (until I worked out
how to fix that) so to get my lappy to see my wifi I had open Network
Settings, click "Connect to a hidden network", then select the ssid from
the drop down list of known networks. Not exactly convenient!

So a "scan now" button would be great, along with more frequent
automatic wifi scanning.

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

Title:
  doesn't scan for available wifi networks often enough + no way to
  manually force a scan

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  - turn on a wifi router nearby
  - click on the network applet icon

  Expected behavior:
  As soon as the new network becomes available, it should become visible in the 
list within few seconds (and if it is a network you have already configured and 
set to automatically connect to, it should connect)

  Observed behavior:
  You won't see the network show up in the list, or perhaps it will, after a 
few minutes. Way too much time.

  
  Additionally, there should be an item in the menu such as "scan for networks 
now" to force scanning for available networks. But there's no such thing even.

  So the only workaround is to physically disable and reenable wifi on
  hardware, if your computer has a button for that. That will trigger
  re-scanning for available networks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  2 23:48:42 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-11 (691 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.167
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (18 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-20T16:52:59.722501
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID  CON-PATH
   
   wlan0  wifi  connected 
/org/freedesktop/NetworkManager/Devices/2  Sixty-Seven  
2dfa6e3a-076f-48f9-a40c-d182c47e4178  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   43:29:1A:07:53:91  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   eth0   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  -- 
   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/hundredpapercuts/+bug/1491612/+subscriptions

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

[Touch-packages] [Bug 1515379] Re: rsyslog not omitted by sendsigs when managed by upstart/systemd

2015-11-11 Thread Simon Déziel

A simplification of this workaround is:

  echo "stop on never-dies" >> /etc/init/rsyslog.override

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

Title:
  rsyslog not omitted by sendsigs when managed by upstart/systemd

Status in rsyslog package in Ubuntu:
  New

Bug description:
  When rsyslog is managed by the init script, it symlinks its PID to
  /run/sendsigs.omit.d so that we can capture logs very late during the
  shutdown sequence:

  sendsigs_omit() {
OMITDIR=/run/sendsigs.omit.d
mkdir -p $OMITDIR
ln -sf $PIDFILE $OMITDIR/rsyslog
  }

  When rsyslog is managed by upstart this functionality is lost. I
  quickly looked in Xenial's package and it seems this functionality is
  also absent when run through systemd.

  
  P.S.: I'm trying to investigate a reboot sequence taking ~forever but for 
which I have 0 log of the actual shutdown sequence:

  Nov 10 22:00:46 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1603" x-info="http://www.rsyslog.com";] exiting on signal 15.
  Nov 10 22:55:25 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1935" x-info="http://www.rsyslog.com";] start

  This 55 minutes gap caused of lot of stress as the machine is a big
  iron in a DC far away.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.6
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 14:14:54 2015
  InstallationDate: Installed on 2014-01-26 (653 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  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/1515379/+subscriptions

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

[Touch-packages] [Bug 1513958] Re: arm64: failure with small objects passed on stack

2015-11-11 Thread dann frazier

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

Title:
  arm64: failure with small objects passed on stack

Status in libffi package in Ubuntu:
  Fix Released
Status in libffi source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  It isn't possible to build newer versions of python-cffi on trusty/arm64 
because it's test cases will fail due to this bug. The thing that's biting me 
is that cloud-archive:liberty is incomplete on arm64, making key packages 
uninstallable on arm64 (e.g. nova-compute).

  Additionally, libffi is used by several languages in Ubuntu (python,
  ruby, haskell, etc), so this may also be causing issues in the closed
  set of Ubuntu/trusty packages. I don't have evidence either way.

  [TestCase]
  Build python-cffi_1.1.2-1ubuntu2 from wily on trusty/arm64. With unfixed 
libffi, the build will fail during dh_auto_test in the
  "TestFFI.test_struct_by_value" test case.

  [Regression Risk]
  The fix is in the aarch64-specific code, so there's a negligible risk of 
regression on other platforms. This exact fix was included in vivid and wily 
and no regressions have been triaged to libffi in those releases.

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

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

[Touch-packages] [Bug 1350821] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press()

This bug was fixed in the package ido - 13.10.0+14.04.20151021-0ubuntu1

---
ido (13.10.0+14.04.20151021-0ubuntu1) trusty; urgency=medium

  * IdoCalendarMenuItem: add crash guard on
ido_calendar_menu_item_key_press (LP: #1350821)

 -- Marco Trevisan (Treviño)   Wed, 21 Oct 2015 15:52:32
+

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

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

Title:
  unity-panel-service crashed with SIGSEGV in
  ido_calendar_menu_item_key_press()

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Trusty:
  Fix Released

Bug description:
  
  [Impact]
  Unity panel service crashes when opening the Calendar menu

  [Test Case]
  There's not a way to reproduce this systemically. Just open frequently the 
calendar menu, but this crash can happen or not.

  [Regression Potential]
  None, the code change consists only on protecting against a null pointer 
(recorded in the stacktraces here), so it's just pretty safe.

  
  ProblemType: CrashDistroRelease: Ubuntu 14.10
  Package: unity-services 7.3.0+14.10.20140711-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 31 13:53:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed
   virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2013-12-22 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx
   PC (0x7ffbbaf3b766) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  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:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Jul 30 18:55:05 2014
  xserver.configfile: default
  xserver.errors:
   intel: Failed to load module "dri3" (module does not exist, 0)
   int

[Touch-packages] [Bug 1432871] Update Released

The verification of the Stable Release Update for coreutils has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

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

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

Bug description:
  [Impact]

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

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

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

  [Test Case]

   * $ mount
  
  192.168.1.2:/raid on /raid type nfs
  /dev/sdc5 on /data type ext4 (rw)
  
  /data/a on /a type none (rw,bind)
  /raid/temp on /b type none (rw,bind)

  $df
  Filesystem   1K-blocks   Used  Available Use% Mounted on
  
  /data/a  449830616  229975284  196982196  54% /a
  /raid/temp  7752072192 5581343744 1780023296  76% /b
  

  I'd expect to see the real mount prioritized over the bind mount.  Like so.
  $df
  Filesystem   1K-blocks   Used  Available Use% Mounted on
  
  /dev/sdc5449830616  229975284  196982196  54% /data
  192.168.1.2:/raid   7752072192 5581438976 1779929088  76% /raid
  

  [Regression Potential]

   * Patch is upstreamed.

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

  [Other Info]

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

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

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

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

  Origin: upstream, coreutils - 
http://git.savannah.gnu.org/gitweb/?p=coreutils.git
  commit: 
http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=1b1c40e1d6f8cf30b6c7c9d31bbddbc3d5cc72e6
  Original bug.
  
  Depending on mount path length df so

[Touch-packages] [Bug 1350821] Update Released

The verification of the Stable Release Update for ido has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  unity-panel-service crashed with SIGSEGV in
  ido_calendar_menu_item_key_press()

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Trusty:
  Fix Released

Bug description:
  
  [Impact]
  Unity panel service crashes when opening the Calendar menu

  [Test Case]
  There's not a way to reproduce this systemically. Just open frequently the 
calendar menu, but this crash can happen or not.

  [Regression Potential]
  None, the code change consists only on protecting against a null pointer 
(recorded in the stacktraces here), so it's just pretty safe.

  
  ProblemType: CrashDistroRelease: Ubuntu 14.10
  Package: unity-services 7.3.0+14.10.20140711-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 31 13:53:14 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed
   virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed
  ExecutablePath: /usr/lib/unity/unity-panel-service
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2013-12-22 (221 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/unity/unity-panel-service
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx
   PC (0x7ffbbaf3b766) ok
   source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  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:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Jul 30 18:55:05 2014
  xserver.configfile: default
  xserver.errors:
   in

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

This bug was fixed in the package coreutils - 8.23-3ubuntu1.1

---
coreutils (8.23-3ubuntu1.1) vivid; urgency=medium

  * Add support for correctly processing /proc/self/mountinfo.
  * Fix df to prioritize mounts of the root of a device over bind mounts.
(LP: #1432871)

 -- Dave Chiluk   Wed, 30 Sep 2015 21:06:59 +

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

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

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

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

Bug description:
  [Impact]

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

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

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

  [Test Case]

   * $ mount
  
  192.168.1.2:/raid on /raid type nfs
  /dev/sdc5 on /data type ext4 (rw)
  
  /data/a on /a type none (rw,bind)
  /raid/temp on /b type none (rw,bind)

  $df
  Filesystem   1K-blocks   Used  Available Use% Mounted on
  
  /data/a  449830616  229975284  196982196  54% /a
  /raid/temp  7752072192 5581343744 1780023296  76% /b
  

  I'd expect to see the real mount prioritized over the bind mount.  Like so.
  $df
  Filesystem   1K-blocks   Used  Available Use% Mounted on
  
  /dev/sdc5449830616  229975284  196982196  54% /data
  192.168.1.2:/raid   7752072192 5581438976 1779929088  76% /raid
  

  [Regression Potential]

   * Patch is upstreamed.

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

  [Other Info]

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

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

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

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

  Origin: upstream, coreutils - 
http://git.savannah.gnu.org/gitweb/?p=coreutils.git
  commit: 
http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=commit;h=1b1c40e1d6f8cf30b6c7c9d31bbddbc3d5cc72e6
  Original bug.
  
  Depending on mount path length df sometimes prioritizes showing bind mounts 
ov

[Touch-packages] [Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)

Hello Stéphane, or anyone else affected,

Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.1
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: lxc (Ubuntu Trusty)
   Status: 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1514623

Title:
  New upstream bugfix release 1.0.8 (LXC MRE)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  We have released LXC 1.0.7 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

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

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

[Touch-packages] [Bug 1429140] Re: lxc-net upstart script fails on nonexistent iptables rules

Hello Daniel, or anyone else affected,

Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.8-0ubuntu0.1
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: lxc (Ubuntu Trusty)
   Status: 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1429140

Title:
  lxc-net upstart script fails on nonexistent iptables rules

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Committed

Bug description:
  Hello,

  On Trusty, the stop of lxc-net fails if the iptables rules are not
  present.

  I added “exec >> /tmp/lxc-net.log 2>&1” at the beginning of pre-start
  and post-stop and get:

  iptables: Bad rule (does a matching rule exist in that chain?).

  On Precise, a “|| true” was added to avoid errors.

  I attach a patch to disable exit on failing iptables call.

  Regards.

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

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

[Touch-packages] [Bug 1515379] Re: rsyslog not omitted by sendsigs when managed by upstart/systemd

2015-11-11 Thread Simon Déziel

In the upstart case, simply removing the "stop on runlevel [06]" clause
is enough to capture the log output of the shutdown sequence.

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

Title:
  rsyslog not omitted by sendsigs when managed by upstart/systemd

Status in rsyslog package in Ubuntu:
  New

Bug description:
  When rsyslog is managed by the init script, it symlinks its PID to
  /run/sendsigs.omit.d so that we can capture logs very late during the
  shutdown sequence:

  sendsigs_omit() {
OMITDIR=/run/sendsigs.omit.d
mkdir -p $OMITDIR
ln -sf $PIDFILE $OMITDIR/rsyslog
  }

  When rsyslog is managed by upstart this functionality is lost. I
  quickly looked in Xenial's package and it seems this functionality is
  also absent when run through systemd.

  
  P.S.: I'm trying to investigate a reboot sequence taking ~forever but for 
which I have 0 log of the actual shutdown sequence:

  Nov 10 22:00:46 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1603" x-info="http://www.rsyslog.com";] exiting on signal 15.
  Nov 10 22:55:25 node9 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" 
x-pid="1935" x-info="http://www.rsyslog.com";] start

  This 55 minutes gap caused of lot of stress as the machine is a big
  iron in a DC far away.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.6
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 14:14:54 2015
  InstallationDate: Installed on 2014-01-26 (653 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  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/1515379/+subscriptions

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

apt-cache policy qtdeclarative5-qtmir-plugin
qtdeclarative5-qtmir-plugin:
  Installed: 0.4.6+15.04.20151110-0ubuntu1
  Candidate: 0.4.6+15.04.20151110-0ubuntu1

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

Title:
  After a boot the dash doesn't display until touched

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

-- 
Mailing list: https://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 1514102] Re: Intermittent graphics corruption

2015-11-11 Thread Ian Bruntlett

On 11 November 2015 at 19:36, Ian Bruntlett 
wrote:

> To test this PC I reinstalled lubuntu 15.10 64-bit and used Synaptic
> Package manager to install a few bits and pieces.
>
> The PC is behaving much better now and graphics are OK.
>
PC graphics are still misbehaving.

One day I will know enough about Linux to be able to debug graphics
drivers.

-- 
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.google.com/site/ianbruntlett/
-- Free Software page -
https://sites.google.com/site/ianbruntlett/home/free-software

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

Title:
  Intermittent graphics corruption

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Every so often the screen would be corrupted with horizontal lines of
  junk.

  WORKAROUND: Add to /etc/default/grub GRUB_CMDLINE_LINUX nomodeset:
  sudo update-grub
  reboot

  Now the system will only allow VGA 640x480 graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Nov  7 18:44:01 2015
  InstallationDate: Installed on 2015-11-07 (0 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

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

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

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

Title:
  After a boot the dash doesn't display until touched

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

[Touch-packages] [Bug 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend

2015-11-11 Thread Wolf Rogner

I can confirm that this bug is eliminated in 15.10.
Unfortunately another old bug reappeared (random disconnect).
I will look into this in more detail.

For me it is solved.

Thanks

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

Title:
  network-manager does not autoconnect to wifi network after resume from
  suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 15.04 network manager does not reconnect to the
  wifi network after resuming from a suspend to memory.

  Workaround:
  disable and re-enable wireless network -> connects immediately

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 25 23:53:54 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-05-17 (708 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac 
(20130424)
  IpRoute:
   default via 10.1.0.254 dev wlan0  proto static  metric 1024 
   10.0.0.0/8 dev wlan0  proto kernel  scope link  src 10.1.0.103 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlan0  wifi  connected 
/org/freedesktop/NetworkManager/Devices/1  rsb_hs  
d8793959-2da1-4dc6-85ad-2dcf9e36e64b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   EC:88:92:61:E9:5F  btdisconnected  
/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/1448555/+subscriptions

-- 
Mailing list: https://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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

2015-11-11 Thread Alan Burgess

Iain,

This 'bug has been around for a long time now and the information that 
is on or comes back from the forum is inadequate and in one instance 
rendered my computer unbootable.

In the end I moved back to Windows 7 for all my serious work and now use 
Ubuntu 14.04 for anything that I'm prepared to loose.  I hope one day to 
be able to move back to Ubuntu as my main computing platform when it is 
as stable as Win 7.

Good luck.


On 10/11/15 23:43, Iain wrote:
> As a very new member of the Ubuntu community can I make a couple of
> observations?
>
> First: I understand the statement "Insufficient space in /boot" however:
> when I used the instruction that is supposed to clear space [sudo apt-
> get clean] it either didn't or didn't clear enough. So I thought I'd
> take the direct approach.  I'm an Administrator, so I loaded the Files
> application and went looking, but when I found what I thought was the
> /boot folder the system would not allow me to delete some older files
> (looked like downloads from earlier updates). Maybe the error message
> can include a solution that tells me how to delete the old files and/or
> increase the space of the /boot folder? Or even where to find the /boot
> folder?
>
> My second comment is that maybe once the installation of an update has
> successfully completed then the downloaded installation files could be
> deleted?
>
> I've tried limiting the download to smaller sections of the current
> update but nothing seems to install.
>
> Quick update: I thought I'd take one more look at the search engine and
> I found another command to remove junk from the boot (sudo apt-get
> autoremove) and this tells me it removed 300MB but the install still
> says it needs 30MB more than the available limit...
>
> How do I clean up the /boot folder?
>

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor or manually free space on
  your partition containing the /boot file system.

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

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

[Touch-packages] [Bug 1363482] Re: ubuntu-keyring includes 1024D keys

** Branch linked: lp:ubuntu-cdimage

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

Title:
  ubuntu-keyring includes 1024D keys

Status in Ubuntu CD Images:
  New
Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-keyring as shipped in trusty contains old 1024D keys dating
  back to 2004 which are still being trusted for the main archive:

   % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg | grep 1024D
  pub  1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key 

  pub  1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key 


  Given that newer 4096R keys are present and have been in precise
  (through -updates) and trusty, it seems to be about time to drop the
  older keys. (In the hope that apt does not chose on signatures it
  cannot verify, otherwise the publisher would need to stop signing with
  the old key as well.)

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

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

[Touch-packages] [Bug 1496163] Re: i915 firmware is not copied to initrd

2015-11-11 Thread Brad Parker

Peter: Manually modifying the file per comment #9's fix worked for me on
14.04. But I am still having lots of problems with the GPUs on my
laptop. Also had to use xorg-edgers ppa to get hardware acceleration
back, otherwise X complained about unknown chipset. Also, the newest
kernel versions (like 4.3) are freezing up hard for me, and different
older versions only work on certain GPUs. What I mean is like, if I want
to use the discrete nvidia GPU, I have to boot 3.19, but if I want
integrated graphics, then I have to boot 4.2.4 with
i915.preliminary_hw_support=1. Also, running "lspci" on newer kernels
freezes the machine hard.

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

Title:
  i915 firmware is not copied to initrd

Status in Linux:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  In Progress
Status in initramfs-tools source package in Vivid:
  In Progress
Status in initramfs-tools source package in Wily:
  Fix Released

Bug description:
  On Skylake, the skl_dmc firmware is failing to load. From dmesg:

  [0.728803] i915 :00:02.0: Direct firmware load for 
i915/skl_dmc_ver1.bin failed with error -2
  [0.728817] [drm:i915_firmware_load_error_print [i915]] *ERROR* failed to 
load firmware i915/skl_dmc_ver1.bin (0)

  This means the GPU can't enter its lowest available power states, plus
  many display hotplugging scenarios (that only the skl_dmc firmware can
  handle) are broken.

  On a whim I tried some other firmware versions:

  1) pointed the skl_dmc_ver1.bin symlink to skl_dmc_ver1_18.bin
  (instead of skl_dmc_ver1_19.bin)

  2) downloaded the latest (skl_dmc_ver1_21.bin) and pointed the
  skl_dmc_ver1.bin symlink to it

  But neither corrected the situation.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-10-generic 4.2.0-10.11
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oem1251 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 15 16:21:24 2015
  HibernationDevice: RESUME=UUID=637df075-0afa-420f-a3ca-342be8bf297f
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:0833 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 004: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader 
Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-10-generic 
root=UUID=f967534a-9cc3-4d1a-a7f3-72d28959e3c6 ro i915.verbose_state_checks=1 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-10-generic N/A
   linux-backports-modules-4.2.0-10-generic  N/A
   linux-firmware1.147
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0403
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P D3
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0403:bd08/19/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1363482] Re: ubuntu-keyring includes 1024D keys

2015-11-11 Thread Colin Watson

** Changed in: ubuntu-cdimage
 Assignee: Adam Conrad (adconrad) => Colin Watson (cjwatson)

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

Title:
  ubuntu-keyring includes 1024D keys

Status in Ubuntu CD Images:
  New
Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-keyring as shipped in trusty contains old 1024D keys dating
  back to 2004 which are still being trusted for the main archive:

   % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg | grep 1024D
  pub  1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key 

  pub  1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key 


  Given that newer 4096R keys are present and have been in precise
  (through -updates) and trusty, it seems to be about time to drop the
  older keys. (In the hope that apt does not chose on signatures it
  cannot verify, otherwise the publisher would need to stop signing with
  the old key as well.)

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

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

** Description changed:

  Saw this on 162 and 163
  MX4
+ also on krillin and mako
  
  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately
  
- Also reproduces occasionally after reboot
+ Also reproduces frequently after reboot

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

Title:
  After a boot the dash doesn't display until touched

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

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

[Touch-packages] [Bug 1515356] Re: After a boot the dash doesn't display until touched

** Summary changed:

- Firs boot after an update the dash doesn't display until touched
+ After a boot the dash doesn't display until touched

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

Title:
  After a boot the dash doesn't display until touched

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

Bug description:
  Saw this on 162 and 163
  MX4
  also on krillin and mako

  Get the update and reboot to install, open the greeter, there is a blank 
screen with just the bottom edge hint
  touch the screen and it displays the scope contents immediately

  Also reproduces frequently after reboot

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

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

[Touch-packages] [Bug 1496845] Re: Number containing # are incorrectly sent unencoded to url-dispatcher