date:20160401

** Bug watch added: Linux Kernel Bug Tracker #115531
   http://bugzilla.kernel.org/show_bug.cgi?id=115531

** Also affects: alsa-driver via
   http://bugzilla.kernel.org/show_bug.cgi?id=115531
   Importance: Unknown
   Status: Unknown

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

2016-04-01 Thread Tim

Upgrades are working for Ubuntu GNOME, but screensaver issues exist, see
Bug 1565177 w/ proposed fix

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

Title:
  Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

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

Bug description:
  STEPS:
  1. Install 14.04.4 on a uefi securebooted system
  2. update it
  3. Install openssh-server for debug access
  4. reboot
  5. Hit alt+f2
  6. Type update-manager -d and hit enter

  EXPECTED:
  I expected a smooth transition to 16.04

  ACTUAL:
  System is completely taken out mid way through the process killing the 
session and x also no tty when hitting ctrl+alt+f1-6

  ---

  TESTS RESULTS (from cyphermox):

  On amd64 (no EFI) under qemu/libvirt, qxl graphics:
  - upgrading just libglib2.0-0 from 16.04 on top of 14.04.4: PASS
  - upgrading ubuntu-desktop (running gnome-shell) 14.04.4 to 16.04: PASS
  - upgrading ubuntu-desktop (running xubuntu-session) 14.04.4 to 16.04: PASS
  - manually upgrading compiz and other packages to 16.04 versions; after 
adding xenial sources:
    - compiz and related packages (http://paste.ubuntu.com/15415280/) : PASS
    - xserver-xorg and related: PASS
    - unity and related: PASS
    - ubuntu-desktop: PASS
    - libgl1-mesa-dri: PASS
    - apt-get dist-upgrade: FAIL (screensaver may have kicked in)
  - standard upgrading 14.04.4 to 16.04; screensaver disabled: FAIL (looked 
fine, but upgrade eventually froze, might well be a different issue)
  - re-enabling screensaver after upgrade, before reboot: TODO (above failed)

  On ppc64el:
  - upgrading ubuntu-server 14.04.4 -> 16.04: PASS

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Mar  9 17:01:27 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Beta amd64 (20160224)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

https://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/src/daemon/daemon.conf.in

; default-fragments = 4 
; default-fragment-size-msec = 25

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=810aa36189f82f77403826defa76a4f9f1f01454

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1322353] Re: [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all (The speakers had worked before with 14.04 but suddenly they do not anymore)

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/hda/thinkpad_helper.c

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/hda/patch_realtek.c?qt=grep&q=alc269

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

Title:
  [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all (The
  speakers had worked before with 14.04 but suddenly they do not
  anymore)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I do not know which update has caused the problem. The speakers had
  worked already with 14.04 but since a few days there is no sound
  anymore.

  Headphones work correctly.

  I have a Thinkpad S531 Laptop which is certified to work with Ubuntu.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  2609 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 22 23:16:22 2014
  InstallationDate: Installed on 2014-04-25 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  2609 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKET24WW (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B00050GE
  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:bvrGKET24WW(1.04):bd05/02/2013:svnLENOVO:pn20B00050GE:pvrThinkPadS5-S531:rvnLENOVO:rn20B00050GE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B00050GE
  dmi.product.version: ThinkPad S5-S531
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1528416] Re: gedit deadlocks on opening Open or Save As dialog

2016-04-01 Thread Jeffrey

I've figured out that this bug is triggered by having bookmarked the
Trash, which I must have done by accident with an errant Ctrl-D a long
time ago. After removing that bookmark, the problem seems to go away.
(And, just to verify, if I bookmark the Trash again, it comes back.)

** Summary changed:

- gedit deadlocks on opening Open or Save As dialog
+ With Trash bookmarked, gedit deadlocks on opening Open or Save As dialog

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

Title:
  With Trash bookmarked, gedit deadlocks on opening Open or Save As
  dialog

Status in Ubuntu GNOME:
  New
Status in tracker package in Ubuntu:
  New

Bug description:
  On Ubuntu 15.10, gedit randomly (about half the time) hangs when
  either the Open or the Save As dialog is opened.

  The cause appears to be a deadlock:

  Thread 1 is in a GCancellable::cancelled signal handler, and indirectly calls 
g_dbus_connection_signal_subscribe which tries to acquire a GDBusConnection's 
mutex
  Thread 3 is in on_worker_message_received, which holds the GDBusConnection's 
mutex and indirectly calls g_cancellable_disconnect which waits for the 
GCancellable's signal handler to complete.

  Thread 1 (Thread 0x77f27a00 (LWP 10630)):
  #0  0x748c45a9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  #1  0x7514102c in g_mutex_lock_slowpath (mutex=mutex@entry=0x6e55a8) 
at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gthread-posix.c:1315
  #2  0x75141872 in g_mutex_lock (mutex=mutex@entry=0x6e55a8) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./glib/gthread-posix.c:1339
  #3  0x7591cdb9 in g_dbus_connection_signal_subscribe 
(connection=0x6e5590 [GDBusConnection], sender=0x0, 
interface_name=interface_name@entry=0x75969d10 
"org.freedesktop.DBus.Properties", member=member@entry=0x759681f0 
"PropertiesChanged", object_path=0xd7a210 "/org/gtk/vfs/Daemon", arg0=0xc09880 
"org.gtk.vfs.Daemon", flags=G_DBUS_SIGNAL_FLAGS_NONE, callback=0x75925da0 
, user_data=0x8be350, user_data_free_func=0x75925cf0 
) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gdbusconnection.c:3445
  #4  0x759263c2 in async_initable_init_first 
(initable=initable@entry=0x7fffd4010780)
  at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gdbusproxy.c:1740
  #5  0x75927238 in async_initable_init_async (initable=0x7fffd4010780, 
io_priority=0, cancellable=0x0, callback=, user_data=) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gdbusproxy.c:1862
  #6  0x7587fb51 in g_async_initable_new_valist_async 
(object_type=, first_property_name=0x7fffe8c83b40 "g-flags", 
var_args=0x7fffd360, io_priority=0, cancellable=0x0, 
callback=0x7fffe8eb0780 , user_data=0x2)
  at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gasyncinitable.c:426
  #7  0x7587fc08 in g_async_initable_new_async (object_type=, io_priority=io_priority@entry=0, cancellable=cancellable@entry=0x0, 
callback=callback@entry=0x7fffe8eb0780 , 
user_data=user_data@entry=0x2, 
first_property_name=first_property_name@entry=0x7fffe8c83b40 "g-flags") at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gasyncinitable.c:339
  #8  0x7fffe8c74df8 in gvfs_dbus_daemon_proxy_new (connection=0x6e5590 
[GDBusConnection], flags=flags@entry=G_DBUS_PROXY_FLAGS_NONE, 
name=name@entry=0x0, object_path=object_path@entry=0x7fffe8ebbb95 
"/org/gtk/vfs/Daemon", cancellable=cancellable@entry=0x0, 
callback=callback@entry=0x7fffe8eb0780 , user_data=0x2) at 
gvfsdbus.c:1201
  #9  0x7fffe8eb0528 in async_call_cancelled_cb (cancellable=, _data=) at gvfsdaemondbus.c:376
  #13 0x753ed12f in  (instance=instance@entry=0xd57450, signal_id=, 
detail=detail@entry=0) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gsignal.c:3439
  #10 0x753d2015 in g_closure_invoke (closure=0xd792f0, 
return_value=return_value@entry=0x0, n_param_values=1, 
param_values=param_values@entry=0x7fffd6b0, 
invocation_hint=invocation_hint@entry=0x7fffd630) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gclosure.c:801
  #11 0x753e4061 in signal_emit_unlocked_R 
(node=node@entry=0x6efa40, detail=detail@entry=0, 
instance=instance@entry=0xd57450, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd6b0)
  at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gsignal.c:3627
  #12 0x753ecdfc in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffd860) at 
/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gobject/gsignal.c:3383
  #14 0x758833b8 in g_cancellable_cancel (cancellable=0xd57450 
[GCancellable]) at /build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/gcancellable.c:508
  #15 0x76fe6ba4 in update_places (sidebar=0xd92460 [GtkPlacesSidebar]) 
at /build/gtk+3.0-pIzeMy/gtk+3.0-3.16.7/./gtk/gtkplacessidebar.c:941
  #16 0

[Touch-packages] [Bug 1405988] Re: X don't start after installation of programs

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

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

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

Title:
  X don't start after installation of programs

Status in xorg package in Ubuntu:
  Expired

Bug description:
  On a new board ASUS H81M-Plus, with the chipset H81 Intel, and an
  Intel I3.

  I install Xubuntu 14.04, reboot, update/upgrade.
  After, that, i launch a script to install a few programs.
  The X-server seems to be break, and at the next start, the server X fails to 
load.
  I'm able to change the console, connect to my account, and launch the X 
server (startx).
  All don't work correctly, but the server seems to be correctly launched.

  I must say that on another computer with Wubuntu 14.04, but without
  this chipset, it works fine.

  I join my script, hoping you're able to find what is wrong. A great
  part of the packages are taken in ubuntu (apt-get), a few are located
  locally and installed using gdebi.

  I must add that I have tried to truncate my script, with a reboot
  between each part, and the problems occurs at different part, without
  I'm able to determine which could be the packet which can generate
  such problem.

  It seems to come after new linux build, new xorg and new intel driver.

  To the question about the package which can bug, I answer 'I don't
  know', but it ought to be 'xserver-xorg-video-intel'.

  I'm really lost about the cause ...

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

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

[Touch-packages] [Bug 1539881] Re: /usr/bin/unity8 crashed in mir::scene::GLPixelBuffer::~GLPixelBuffer (src/server/scene/gl_pixel_buffer.cpp:74)

[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  /usr/bin/unity8 crashed in mir::scene::GLPixelBuffer::~GLPixelBuffer
  (src/server/scene/gl_pixel_buffer.cpp:74)

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

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

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

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

[Touch-packages] [Bug 1539881] Re: /usr/bin/unity8 crashed in mir::scene::GLPixelBuffer::~GLPixelBuffer (src/server/scene/gl_pixel_buffer.cpp:74)

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

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

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

Title:
  /usr/bin/unity8 crashed in mir::scene::GLPixelBuffer::~GLPixelBuffer
  (src/server/scene/gl_pixel_buffer.cpp:74)

Status in Mir:
  Expired
Status in mir package in Ubuntu:
  Expired
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

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

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

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

[Touch-packages] [Bug 1538221] Re: Monitors on DisplayPort do not wake from sleep

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

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

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

Title:
Monitors on DisplayPort do not wake from sleep

Status in xorg package in Ubuntu:
Expired

Bug description:
Potentially related:

http://askubuntu.com/questions/546818/displayport-monitor-not-detected-if-switched-off-and-on-again
https://bugs.freedesktop.org/show_bug.cgi?id=88063

http://superuser.com/questions/945362/displayport-link-failure-after-monitor-sleep

I have three monitors plugged into an ATI HD 7950, one through DVI,
the others through DisplayPort, via dual-link adapters. When KDE puts
the monitors to sleep, only the DVI monitor wakes up, not the
DisplayPort monitors.

xrandr shows all three monitors on.

xset dpms force on does not work. Using xrandr to change the
resolution and change it back does not work. Logging out and logging
back in does not work. Trying to switch to CLI with shift-alt-f1, I
see a console, but it shows the bootlog (on the DVI monitor), without
a login prompt.

Trying to log out and log back in, lightdm behaves as though the other
two monitors are on, but only displays on the DVI.

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

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

[Touch-packages] [Bug 1565194] [NEW] Files button disappears from unity launcher

2016-04-01 Thread Ivan Kurnosov

Public bug reported:

I'm experiencing this behaviour on 2 separated machines (in a virtualbox
vm and physically installed on another laptop):

Sometimes after I start the Files Gnome application - its corresponding
button disappears from the Unity Launcher couple seconds after it's
started. So if I minimize the application - I have no chance to close
the application rather than killing its process with kill.

The opposite is also true: sometimes a Files instance that I have
minimised (and which has already disappeared from the launcher)
sometimes - appears back.

I cannot determine under what circumstances it happens, but it's more
often happens than not.

In the attachment there is a gif file with the problem demostration.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-desktop 1.354
ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
Uname: Linux 4.4.0-11-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr  2 17:09:58 2016
InstallationDate: Installed on 2016-02-07 (54 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "desktop-2.gif"
   
https://bugs.launchpad.net/bugs/1565194/+attachment/4620174/+files/desktop-2.gif

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

Title:
  Files button disappears from unity launcher

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm experiencing this behaviour on 2 separated machines (in a
  virtualbox vm and physically installed on another laptop):

  Sometimes after I start the Files Gnome application - its
  corresponding button disappears from the Unity Launcher couple seconds
  after it's started. So if I minimize the application - I have no
  chance to close the application rather than killing its process with
  kill.

  The opposite is also true: sometimes a Files instance that I have
  minimised (and which has already disappeared from the launcher)
  sometimes - appears back.

  I cannot determine under what circumstances it happens, but it's more
  often happens than not.

  In the attachment there is a gif file with the problem demostration.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-desktop 1.354
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr  2 17:09:58 2016
  InstallationDate: Installed on 2016-02-07 (54 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1562698] Re: Browser is rotated 90 degrees on VirtualBox with portrait-sized VM console

2016-04-01 Thread rww

How to get that configuration: install the virtualbox guest addition
packages in the Ubuntu guest, specifically I have virtualbox-guest-x11
and virtualbox-guest-dkms installed. Then, just resize the VM console
window to taste.

Moving launcher to bottom: gsettings set com.canonical.Unity.Launcher 
launcher-position Bottom as discussed at 
https://plus.google.com/+MarcoTrevisan/posts/X46usgf7gSk
As mentioned above, this issue persists regardless of launcher position, I just 
mentioned it because the screenshot was potentially confusing :)

I'm unable to find another UITK app that actually runs inside
Virtualbox, regardless of the "3D acceleration" setting in Virtualbox VM
settings being enabled or not. gallery-app just gives me a white screen
and running it in Terminal gives errors about DRI. I tried notes-app and
mediaplayer-app and was unsuccessful at launching both. Any
recommendations for another to try?

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

Title:
  Browser is rotated 90 degrees on VirtualBox with portrait-sized VM
  console

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  Dragging the console window so that it is no longer taller than it is
  wide causes the browser to rotate to the correct orientation.

  Also, I moved my Dash to the bottom, hence it not being on the left in
  the attached screenshot. That's working as intended :)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160322-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 27 22:20:42 2016
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1554621] Re: Invalid use of palette apparent with new SDK

2016-04-01 Thread Michael Zanetti

** Changed in: tagger
   Status: New => Fix Released

** Changed in: tagger
 Assignee: (unassigned) => Michael Zanetti (mzanetti)

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

Title:
  Invalid use of palette apparent with new SDK

Status in address-book-app:
  Fix Committed
Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  Fix Committed
Status in Tagger:
  Fix Released
Status in Telegram app:
  Fix Committed
Status in Ubuntu Clock App:
  Fix Committed
Status in Ubuntu File Manager App:
  Fix Committed
Status in camera-app package in Ubuntu:
  Fix Released
Status in content-hub package in Ubuntu:
  Invalid
Status in messaging-app package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  The content hub uses the wrong palette values for text (which becomes
  apparent with new UITK), see screenshot.

  The new UITK is landing here: https://requests.ci-
  train.ubuntu.com/#/ticket/905

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: content-hub 0.1+15.04.20160129.1-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Mar  8 18:00:22 2016
  InstallationDate: Installed on 2016-03-08 (0 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160308-020304)
  SourcePackage: content-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

2016-04-01 Thread Lampros Liontos

It's probably something basic, but I'm not sure... how do I change
period sizes?

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1565183] [NEW] Processing triggers for ca-certificates shows 2 times "done."

2016-04-01 Thread Sworddragon

Public bug reported:

I'm using Ubuntu 16.04 dev with ca-certificates 20160104ubuntu1 and on
installing ca-certificates I got this output on processing the triggers
for it (which shows "done." 2 times which is a bit confusing):

Processing triggers for ca-certificates (20160104ubuntu1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

done.
done.

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Processing triggers for ca-certificates shows 2 times "done."

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04 dev with ca-certificates 20160104ubuntu1 and on
  installing ca-certificates I got this output on processing the
  triggers for it (which shows "done." 2 times which is a bit
  confusing):

  Processing triggers for ca-certificates (20160104ubuntu1) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

Blender request 15ms but your usb use period time 24.998 ms


0) I: [pulseaudio] sink-input.c: application.process.binary = "blender" ( 
6.034| 0.000) I: [pulseaudio] sink-input.c: application.language = "C" ( 6.034| 
0.000) I: [pulseaudio] sink-input.c: window.x11.display = ":0.0" ( 6.034| 
0.000) I: [pulseaudio] sink-input.c: application.process.machine_id = 
"135d836b29434d8cbea95fc6909f7fcc" ( 6.034| 0.000) I: [pulseaudio] 
sink-input.c: application.process.session_id = "c2" ( 6.034| 0.000) I: 
[pulseaudio] sink-input.c: application.icon_name = "blender" ( 6.034| 0.000) I: 
[pulseaudio] sink-input.c: module-stream-restore.id = 
"sink-input-by-application-name:Blender" ( 6.035| 0.000) I: [pulseaudio] 
protocol-native.c: Requested tlength=60.00 ms, minreq=14.99 ms ( 6.035| 0.000) 
D: [pulseaudio] protocol-native.c: Adjust latency mode enabled, configuring 
sink latency to half of overall latency. ( 6.035| 0.000) D: [pulseaudio] 
protocol-native.c: Requested latency=15.01 ms, Received latency=99.95 ms ( 
6.035| 0.000) D: [pulseaudio] memblockq.c: memblockq
  requested: maxlength=4194304, tlength=45840, base=8, prebuf=40560, 
minreq=5288 maxrewind=0 ( 6.035| 0.000) D: [pulseaudio] memblockq.c: memblockq 
sanitized: maxlength=4194304, tlength=45840, base=8, prebuf=40560, minreq=5288 
maxrewind=0 ( 6.035| 0.000) I: [pulseaudio] protocol-native.c: Final latency 
229.88 ms = 99.95 ms + 2*14.99 ms + 99.95

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thin

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

Try specify period time to multiple of 10ms since you are using 44100Hz

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

Your usb audio are using about 25ms period time with 4 periods

) I: [pulseaudio] source.c: device.vendor.id = "0d8c" ( 5.364| 0.000) I:
[pulseaudio] source.c: device.vendor.name = "C-Media Electronics, Inc."
( 5.364| 0.000) I: [pulseaudio] source.c: device.product.id = "0102" (
5.364| 0.000) I: [pulseaudio] source.c: device.product.name = "CM106
Like Sound Device" ( 5.364| 0.000) I: [pulseaudio] source.c:
device.serial = "0d8c_USB_Sound_Device" ( 5.364| 0.000) I: [pulseaudio]
source.c: device.string = "2" ( 5.364| 0.000) I: [pulseaudio] source.c:
module-udev-detect.discovered = "1" ( 5.364| 0.000) I: [pulseaudio]
source.c: device.icon_name = "audio-card-usb" ( 5.364| 0.000) I:
[pulseaudio] alsa-sink.c: Using 4.0 fragments of size 4408 bytes
(24.99ms), buffer size is 17632 bytes (99.95ms) ( 5.364| 0.000) D:
[pulseaudio] alsa-sink.c: hwbuf_unused=0 ( 5.364| 0.000) D: [pulseaudio]
alsa-sink.c: setting avail_min=1 ( 5.364| 0.000) D: [pulseaudio] alsa-
mixer.c: Activating path analog-output ( 5.364| 0.000) D: [pulseaudio]
alsa-mixer.c: Path analog-output (Analog Output), direction=1,
priority=99, probed=yes, supported=yes, has_mute=no, has_volume=no,
has_dB=no, min_volume=0, max_volume=0, min_dB=inf, max_dB=-inf ( 5.364|
0.000) I: [pulseaudio] alsa-sink.c: Driver does not support hardware
volume control, falling back to software volume control. ( 5.364| 0.000)
I: [pulseaudio] alsa-sink.c: Driver does not support hardware mute
control, falling back to software mute control. ( 5.364| 0.000) D:
[pulseaudio] alsa-util.c: snd_pcm_dump(): ( 5.364| 0.000) D:
[pulseaudio] alsa-util.c: Hardware PCM card 2 'USB Sound Device' device
0 subdevice 0 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c: Its setup is:
( 5.364| 0.000) D: [pulseaudio] alsa-util.c: stream : PLAYBACK ( 5.364|
0.000) D: [pulseaudio] alsa-util.c: access : MMAP_INTERLEAVED ( 5.364|
0.000) D: [pulseaudio] alsa-util.c: format : S16_LE ( 5.364| 0.000) D:
[pulseaudio] alsa-util.c: subformat : STD ( 5.364| 0.000) D:
[pulseaudio] alsa-util.c: channels : 2 ( 5.364| 0.000) D: [pulseaudio]
alsa-util.c: rate : 44100 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c:
exact rate : 44100 (44100/1) ( 5.364| 0.000) D: [pulseaudio] alsa-
util.c: msbits : 16 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c:
buffer_size : 4408 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c:
period_size : 1102 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c:
period_time : 24988 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c:
tstamp_mode : ENABLE ( 5.364| 0.000) D: [pulseaudio] alsa-util.c:
tstamp_type : MONOTONIC ( 5.364| 0.000) D: [pulseaudio] alsa-util.c:
period_step : 1 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c: avail_min :
1102 ( 5.364| 0.000) D: [pulseaudio] alsa-util.c: period_event : 1 (
5.364| 0.000) D: [pulseaudio] alsa-util.c: start_threshold : -1 ( 5.364|
0.000) D: [pulseaudio] alsa-util.c: stop_threshold : 4962966789362286592
( 5.364| 0.000) D: [pulseaudio] alsa-util.c: silence_threshold: 0 (
5.364| 0.000) D: [pulseaudio] alsa-util.c: silence_size : 0 ( 5.364|
0.000) D: [pulseaudio] alsa-util.c: boundary : 4962966789362286592 (
5.364| 0.000) D: [pulseaudio] alsa-util.c: appl_ptr : 0 ( 5.364| 0.000)
D: [pulseaudio] alsa-util.c: hw_ptr : 0 ( 5.365| 0.000) D: [alsa-s

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analo

[Touch-packages] [Bug 1225644] Re: old e2fsprogs version can corrupt fs during offline resize

2016-04-01 Thread racitup

I would strongly urge e2fsprogs v1.43 be brought in sooner rather than
later.

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

Title:
  old e2fsprogs version can corrupt fs during offline resize

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  The version of e2fsprogs (1.42.5 and below) included in Precise,
  Quantal, and Raring contains the bug described here:

  http://forums.whirlpool.net.au/archive/2060328

  and fixed in 1.42.8. 1.42.8 is included in Saucy. I think the newer
  version should be included as an update, as the bug causes data loss.
  Further, documentation should reflect that it isn't necessarily better
  to unmount before resizing under ext4 - at the moment, it is always
  impressed on everyone to NEVER touch a filesystem online.

  I believe Ubuntu's installer sets the flag (resize_inode) in question
  by default, so the combination of:

  1) ext4 with resize_inode set
  2) gparted and documentation insist that you only ever modify the filesystem 
offline
  3) the old version of e2fsprogs

  creates the risk that the holes in the swiss cheese line up and lead
  to a disaster.

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

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

[Touch-packages] [Bug 1563139] Re: filefrag bug requires update from 1.42.9 -> 1.42.12

2016-04-01 Thread racitup

Further to this and my testing results at the link below, I would
strongly urge e2fsprogs be updated to v1.43-WIP once full validation of
the package is completed.

I have found another issue with filefrag on FAT filesystems.

https://github.com/racitup/testfilefrag/wiki

** Summary changed:

- filefrag bug requires update from 1.42.9 -> 1.42.12
+ filefrag bug requires update from 1.42.9 -> 1.43-WIP

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

Title:
  filefrag bug requires update from 1.42.9 -> 1.43-WIP

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Ubuntu Trusty is affected by a known issue in filefrag whereby incorrect 
block numbers are reported by the -e or -v options.
  I have specifically found the issue using filefrag on FAT partitions on 
Ubuntu Trusty.

  The bug is fixed by this commit which first appears in e2fsprogs v1.42.12:
  
http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/?id=01824c9bbcd2c1037085213f6cd7d591f78db9c5

  Debian jessie (stable) ships v1.42.12.
  Ubuntu vivid ships v1.42.12 also.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: e2fsprogs 1.42.9-3ubuntu1.3
  Uname: Linux 4.1.20-040120-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar 29 01:44:54 2016
  InstallationDate: Installed on 2015-04-16 (347 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

-32 is EPIPE

http://git.alsa-project.org/?p=alsa-lib.git;a=blob;f=src/pcm/pcm.c

http://git.alsa-project.org/?p=alsa-lib.git;a=blob;f=src/pcm/pcm_hw.c

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1562279] Re: Can't set en_NZ locale

2016-04-01 Thread Gunnar Hjalmarsson

On 2016-04-02 02:25, Jane Atkinson wrote:
> The locale settings were simply the result of following the standard
> install process and confirming that my location was Auckland when
> requested.

Right, understood. The installer tried to set reasonable locales based
on the selections you made.

> It sounds like something isn't working properly during the install.

It works as expected. But there is an inconsistency under the hood:
While the UIs you encounter after the installation only show language
options which represent translations, the installer does not care about
that. So in your case the installer set en_NZ.UTF-8 everywhere. But
since there are no en_NZ translations, that locale is ignored with
respect to the display language.

In case of Xubuntu, with lightdm-gtk-greeter, you instantly are enforced
to select one of the available translations, and the locale is altered
accordingly.

So please focus on the actual behavior of your desktop. Are you
encountering a real problem? I don't think you are.

What I think you should do is asking yourself which of the available
translations are closest to the English you speak in NZ, and select that
language. Based on your geographical location I would suspect it's
en_AU, but really don't know.

> Do I need to report a new bug?

No need to. If you can convince me that there is a problem which needs
to be fixed, I'll be happy to open this bug report again. But I don't
think you can. ;)

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

Title:
Can't set en_NZ locale

Status in language-pack-en-base package in Ubuntu:
Invalid

Bug description:
After updating language-pack-en and language-pack-en-base in Xubuntu
16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-
greeter.

Current locale, after fiddling with language support, is:

LANG=en_US.UTF-8
LANGUAGE=en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_NZ.UTF-8
LC_TIME=en_NZ.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_NZ.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_NZ.UTF-8
LC_NAME=en_NZ.UTF-8
LC_ADDRESS=en_NZ.UTF-8
LC_TELEPHONE=en_NZ.UTF-8
LC_MEASUREMENT=en_NZ.UTF-8
LC_IDENTIFICATION=en_NZ.UTF-8
LC_ALL=

Previously, everything was "en_NZ.UTF-8"

I imagine that the same issue is going to apply to a number of
English-language locales other than Australia, Canada, UK and US.
These four, plus a generic "en" (which appears to default to en_US)
are all that are displayed in the lightdm-greeter language menu.

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa
/alsa-mixer.c?id=c87917cf0da9add5c282a1c15831fd481f9fcc22

Pulseaudio drop support of those volume controls with more than two
channels

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1562208] Re: OpenAL Software Silent/Freezes

2016-04-01 Thread Lampros Liontos

More information about the issue can be found here:
https://github.com/kcat/openal-soft/issues/34

I don't know what can affect the prebuf value, but hopefully, something
can be figured out.  And the log above was using 1.16; I tried 1.17.2
after submitting this report.

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

Title:
  OpenAL Software Silent/Freezes

Status in openal-soft package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Following an update I made this week to the system, I have attempted
  to play a number of games, including "X Rebirth" from gog.com,
  "Minecraft," downloaded from Mojang.  In those games making use of the
  OpenAL library, no sound is coming through PulseAudio; there is a
  stream listed in Pulse, but there is no sound, and the meter does not
  indicate that PulseAudio is even receiving any audio.  I am also
  noticing the problem in Blender, but in this case, the issue seems to
  cause the VSE to stick to the frame it's at when set to "A/V Sync"

  To make matters worse, once the stream shows in "pavucontrol," the
  program won't end.  If the audio is integral to the software, such as
  the case of Blender, the software itself will freeze when I attempt to
  close it; I will have to kill the program to make it shut down
  completely.  Other programs that use a sound server with OpenAL seem
  to close, but the stream is still showing in pavucontrol, and the
  process is still shown as running in "ps x".  Killing the frozen app
  makes it go away; and so far, the normal kill command will work;
  there's no need to "-9" it.

  Even openal-info freezes, after displaying the following:

  ---

  Available playback devices:
  CM106 Like Sound Device Analog Stereo
  Available capture devices:
  M-Audio Fast Track MKII Analog Stereo
  Monitor of CM106 Like Sound Device Analog Stereo
  Default playback device: CM106 Like Sound Device Analog Stereo
  Default capture device: CM106 Like Sound Device Analog Stereo
  ALC version: 1.1

  ** Info for device "CM106 Like Sound Device Analog Stereo" **
  ALC version: 1.1
  ALC extensions:
  ALC_ENUMERATE_ALL_EXT, ALC_ENUMERATION_EXT, ALC_EXT_CAPTURE,
  ALC_EXT_DEDICATED, ALC_EXT_disconnect, ALC_EXT_EFX,
  ALC_EXT_thread_local_context, ALC_SOFTX_device_clock, ALC_SOFTX_HRTF,
  ALC_SOFT_loopback, ALC_SOFTX_midi_interface, ALC_SOFT_pause_device
  OpenAL vendor string: OpenAL Community
  OpenAL renderer string: OpenAL Soft
  OpenAL version string: 1.1 ALSOFT 1.16.0
  OpenAL extensions:
  AL_EXT_ALAW, AL_EXT_DOUBLE, AL_EXT_EXPONENT_DISTANCE, AL_EXT_FLOAT32,
  AL_EXT_IMA4, AL_EXT_LINEAR_DISTANCE, AL_EXT_MCFORMATS, AL_EXT_MULAW,
  AL_EXT_MULAW_MCFORMATS, AL_EXT_OFFSET, AL_EXT_source_distance_model,
  AL_LOKI_quadriphonic, AL_SOFT_block_alignment, AL_SOFT_buffer_samples,
  AL_SOFT_buffer_sub_data, AL_SOFT_deferred_updates, 
AL_SOFT_direct_channels,
  AL_SOFT_loop_points, AL_SOFT_MSADPCM, AL_SOFT_source_latency,
  AL_SOFT_source_length
  EFX version: 1.0
  Max auxiliary sends: 4
  Supported filters:
  Low-pass, High-pass, Band-pass
  Supported effects:
  EAX Reverb, Reverb, Chorus, Distortion, Echo, Flanger, Ring Modulator,
  Compressor, Equalizer, Dedicated Dialog, Dedicated LFE

  ---

  This problem persisted, even following a clean installation with no
  PPAs installed.  I'm assuming the problem is in OpenAL, because
  programs not making use of that library (YouTube, VLC, etc.) don't
  seem to have the problem.  The update that seemed to be the breaking
  point was an update to kernel 4.2.0-34 (I no longer have the original
  system, thinking a full restore would fix things), so there might be
  something in the new kernel that's interfering with OpenAL.

  ---

  The required information:

  Description:  Ubuntu 15.10
  Release:  15.10

  libopenal1:
Installed: 1:1.16.0-3
Candidate: 1:1.16.0-3
Version table:
   *** 1:1.16.0-3 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

  ---

  Please let me know if there's any additional information that I will
  need to provide.

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

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

[Touch-packages] [Bug 1562279] Re: Can't set en_NZ locale

2016-04-01 Thread Jane Atkinson

The locale settings were simply the result of following the standard
install process and confirming that my location was Auckland when
requested.

It sounds like something isn't working properly during the install. Do I
need to report a new bug?

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

Title:
  Can't set en_NZ locale

Status in language-pack-en-base package in Ubuntu:
  Invalid

Bug description:
  After updating language-pack-en and language-pack-en-base in Xubuntu
  16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-
  greeter.

  Current locale, after fiddling with language support, is:

  LANG=en_US.UTF-8
  LANGUAGE=en
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_NZ.UTF-8
  LC_TIME=en_NZ.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_NZ.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_NZ.UTF-8
  LC_NAME=en_NZ.UTF-8
  LC_ADDRESS=en_NZ.UTF-8
  LC_TELEPHONE=en_NZ.UTF-8
  LC_MEASUREMENT=en_NZ.UTF-8
  LC_IDENTIFICATION=en_NZ.UTF-8
  LC_ALL=

  Previously, everything was "en_NZ.UTF-8"

  I imagine that the same issue is going to apply to a number of
  English-language locales other than Australia, Canada, UK and US.
  These four, plus a generic "en" (which appears to default to en_US)
  are all that are displayed in the lightdm-greeter language menu.

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

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

[Touch-packages] [Bug 1565080] Re: ubuntuBSD support

2016-04-01 Thread Ubuntu Foundations Team Bug Bot

The attachment "mesa.diff" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

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

Title:
  ubuntuBSD support

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi

  Please could you apply attached patch to make mesa buildable on
  ubuntuBSD? It just needs to adjust a few dependencies.

  Thanks!

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

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

[Touch-packages] [Bug 1562279] Re: Can't set en_NZ locale

2016-04-01 Thread Gunnar Hjalmarsson

Considering that there is no longer any en_NZ 'translation', it's
pointless to use the en_NZ.UTF-8 locale for language. It results in the
original untranslated (en_US) strings being showed. That's why Language
Support and lightdm-gtk-greeter work as I said. The installer may set
LANG to en_NZ.UTF-8 etc., but it doesn't change the behavior compared to
en_US.UTF-8.

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

Title:
  Can't set en_NZ locale

Status in language-pack-en-base package in Ubuntu:
  Invalid

Bug description:
  After updating language-pack-en and language-pack-en-base in Xubuntu
  16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-
  greeter.

  Current locale, after fiddling with language support, is:

  LANG=en_US.UTF-8
  LANGUAGE=en
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_NZ.UTF-8
  LC_TIME=en_NZ.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_NZ.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_NZ.UTF-8
  LC_NAME=en_NZ.UTF-8
  LC_ADDRESS=en_NZ.UTF-8
  LC_TELEPHONE=en_NZ.UTF-8
  LC_MEASUREMENT=en_NZ.UTF-8
  LC_IDENTIFICATION=en_NZ.UTF-8
  LC_ALL=

  Previously, everything was "en_NZ.UTF-8"

  I imagine that the same issue is going to apply to a number of
  English-language locales other than Australia, Canada, UK and US.
  These four, plus a generic "en" (which appears to default to en_US)
  are all that are displayed in the lightdm-greeter language menu.

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

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

[Touch-packages] [Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

2016-04-01 Thread flocculant

ftr - got an upgraded from 14.04 system here now (vanilla virtual - but
even so ...)

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

Title:
  Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

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

Bug description:
  STEPS:
  1. Install 14.04.4 on a uefi securebooted system
  2. update it
  3. Install openssh-server for debug access
  4. reboot
  5. Hit alt+f2
  6. Type update-manager -d and hit enter

  EXPECTED:
  I expected a smooth transition to 16.04

  ACTUAL:
  System is completely taken out mid way through the process killing the 
session and x also no tty when hitting ctrl+alt+f1-6

  ---

  TESTS RESULTS (from cyphermox):

  On amd64 (no EFI) under qemu/libvirt, qxl graphics:
  - upgrading just libglib2.0-0 from 16.04 on top of 14.04.4: PASS
  - upgrading ubuntu-desktop (running gnome-shell) 14.04.4 to 16.04: PASS
  - upgrading ubuntu-desktop (running xubuntu-session) 14.04.4 to 16.04: PASS
  - manually upgrading compiz and other packages to 16.04 versions; after 
adding xenial sources:
    - compiz and related packages (http://paste.ubuntu.com/15415280/) : PASS
    - xserver-xorg and related: PASS
    - unity and related: PASS
    - ubuntu-desktop: PASS
    - libgl1-mesa-dri: PASS
    - apt-get dist-upgrade: FAIL (screensaver may have kicked in)
  - standard upgrading 14.04.4 to 16.04; screensaver disabled: FAIL (looked 
fine, but upgrade eventually froze, might well be a different issue)
  - re-enabling screensaver after upgrade, before reboot: TODO (above failed)

  On ppc64el:
  - upgrading ubuntu-server 14.04.4 -> 16.04: PASS

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Mar  9 17:01:27 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Beta amd64 (20160224)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1554848] Re: Please randomise automatic updates over a longer period

2016-04-01 Thread Brian Murray

** Tags removed: rls-x-incoming

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

Title:
  Please randomise automatic updates over a longer period

Status in apt package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Confirmed

Bug description:
  Load on the main Ubuntu archive servers is rather peakish, and tends
  to create a traffic peak on our Internet links at fairly regular times
  each day, preventing customers from accessing the archive.  This
  impacts the cloud archive mirrors using the ubuntu-repository-cache
  charm also, because they are hitting a squid cache which is backed by
  the main archive.  This effect will be even more pronounced under the
  recently-announced automatic update policy for xenial.

  One solution which would alleviate this to some extent would be to
  spread the load over a longer period by increasing the random sleep
  time in the daily update script from 30 minutes to, say, 1-2 hours.

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

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

[Touch-packages] [Bug 1562279] Re: Can't set en_NZ locale

2016-04-01 Thread Jane Atkinson

I just installed the latest daily ISO for Ubuntu.

Immediately after installation, the command "locale" shows the
following:

LANG=en_NZ.UTF-8
LANGUAGE=en_NZ:en
LC_CTYPE="en_NZ.UTF-8"
LC_NUMERIC="en_NZ.UTF-8"
LC_TIME="en_NZ.UTF-8"
LC_COLLATE="en_NZ.UTF-8"
LC_MONETARY="en_NZ.UTF-8"
LC_MESSAGES="en_NZ.UTF-8"
LC_PAPER="en_NZ.UTF-8"
LC_NAME="en_NZ.UTF-8"
LC_ADDRESS="en_NZ.UTF-8"
LC_TELEPHONE="en_NZ.UTF-8"
LC_MEASUREMENT="en_NZ.UTF-8"
LC_IDENTIFICATION="en_NZ.UTF-8"
LC_ALL=

Which is more or less what I'm wanting.

This leads me to think that the problem may be with the way I installed
this instance of Xubuntu in the first place (from ubuntu-core, if that's
relevant).

Time for a reinstall, I think.

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

Title:
  Can't set en_NZ locale

Status in language-pack-en-base package in Ubuntu:
  Invalid

Bug description:
  After updating language-pack-en and language-pack-en-base in Xubuntu
  16.04, I can no longer set en_NZ.UTF-8 as my locale in lightdm-
  greeter.

  Current locale, after fiddling with language support, is:

  LANG=en_US.UTF-8
  LANGUAGE=en
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_NZ.UTF-8
  LC_TIME=en_NZ.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=en_NZ.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=en_NZ.UTF-8
  LC_NAME=en_NZ.UTF-8
  LC_ADDRESS=en_NZ.UTF-8
  LC_TELEPHONE=en_NZ.UTF-8
  LC_MEASUREMENT=en_NZ.UTF-8
  LC_IDENTIFICATION=en_NZ.UTF-8
  LC_ALL=

  Previously, everything was "en_NZ.UTF-8"

  I imagine that the same issue is going to apply to a number of
  English-language locales other than Australia, Canada, UK and US.
  These four, plus a generic "en" (which appears to default to en_US)
  are all that are displayed in the lightdm-greeter language menu.

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

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

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-01 Thread Len Ovens

@Dmitry, doing:
$ export XDG_CURRENT_DESKTOP=Unity
$ qjackctl

Does make the icon behave as expected. Good. However, the rest of the problems 
still exist:
 - The qjackctl menu does not work, instead an empty drop-down appears. (for 
the reasons you already mentioned)
 - Setting "Start minimized to system tray" makes desktop unusable. Mouse 
moves, but no input is possible. One has to use c/a/f1 to a vterm in order to 
kill qjackctl to make the desktop usable again.

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1565130] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

2016-04-01 Thread Bernhard Nikola

Public bug reported:

update started in 16.04 / beta

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Fri Apr  1 23:57:23 2016
ErrorMessage: Trigger bilden eine Schleife, aufgegeben
InstallationDate: Installed on 2016-02-22 (39 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160221)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.9
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package ca-certificates 20160104ubuntu1 failed to install/upgrade:
  Trigger bilden eine Schleife, aufgegeben

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  update started in 16.04 / beta

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Fri Apr  1 23:57:23 2016
  ErrorMessage: Trigger bilden eine Schleife, aufgegeben
  InstallationDate: Installed on 2016-02-22 (39 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160221)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 876279] Re: Upowerd excessive CPU usage

2016-04-01 Thread Mihai Secasiu

I just installed Ubuntu 16.04 and I have this problem

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

Title:
  Upowerd excessive CPU usage

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  Fresh installation of Oneiric on Activo A-1100 (Atom N450-based)
  netbook. Top reports CPU usage fluctuating between 60% and 100%,
  averaging around 80%. Machine still marginally usable, due to having a
  second core.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: upower 0.9.13-1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Mon Oct 17 18:59:31 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1565123] Re: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: missing dependency File/Find.pm

2016-04-01 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: missing
  dependency File/Find.pm

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Did do-release-upgrade -d from ubuntu 14.04.

  From screenlog.0:

  Preparing to unpack .../lvm2_2.02.133-1ubuntu8_i386.deb ...
  Can't locate File/Find.pm in @INC (you may need to install the File::Find 
module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.22.1 
/usr/local/share/per
  l/5.22.1 /usr/lib/i386-linux-gnu/perl5/5.22 /usr/share/perl5 
/usr/lib/i386-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl 
/usr/lib/i386-linux-gnu/perl-
  base .) at /usr/bin/deb-systemd-helper line 88.
  BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line 88.
  dpkg: error processing archive 
/var/cache/apt/archives/lvm2_2.02.133-1ubuntu8_i386.deb (--unpack):
   subprocess new pre-installation script returned error exit status 2
  dpkg: considering deconfiguration of lvm2, which would be broken by 
installation of initramfs-tools ...
  dpkg: yes, will deconfigure lvm2 (broken by initramfs-tools)
  Preparing to unpack .../initramfs-tools_0.122ubuntu6_all.deb ...
  De-configuring lvm2 (2.02.98-6ubuntu2) ...
  Unpacking initramfs-tools (0.122ubuntu6) over (0.103ubuntu4.3) ...
  dpkg: warning: unable to delete old directory '/var/lib/initramfs-tools': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/initramfs-tools/conf.d': 
Directory not empty
  ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/lvm2.0.crash'

  Ran "aptitude install perl-modules-5.22" afterwards for the dependency
  and it also allowed me to continue to bother with the other unrelated
  errors :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Fri Apr  1 23:40:14 2016
  DuplicateSignature: package:lvm2:2.02.98-6ubuntu2:subprocess new 
pre-installation script returned error exit status 2
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.1ubuntu2.11
  SourcePackage: lvm2
  Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess 
new pre-installation script returned error exit status 2
  UpgradeStatus: Upgraded to xenial on 2016-04-01 (0 days ago)

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

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

[Touch-packages] [Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

This bug was fixed in the package dbus - 1.10.6-1ubuntu3

---
dbus (1.10.6-1ubuntu3) xenial; urgency=medium

  * debian/dbus.preinst: divert the dbus-daemon-launch-helper if upgrading
from < 1.9.4-2~. This will make sure we keep the setuid bit during upgrade.
(LP: #1555237)
  * debian/dbus.postinst: remove diversion.

 -- Mathieu Trudel-Lapierre   Thu, 31 Mar 2016
15:07:46 -0400

** Changed in: dbus (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 dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1555237

Title:
  Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

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

Bug description:
  STEPS:
  1. Install 14.04.4 on a uefi securebooted system
  2. update it
  3. Install openssh-server for debug access
  4. reboot
  5. Hit alt+f2
  6. Type update-manager -d and hit enter

  EXPECTED:
  I expected a smooth transition to 16.04

  ACTUAL:
  System is completely taken out mid way through the process killing the 
session and x also no tty when hitting ctrl+alt+f1-6

  ---

  TESTS RESULTS (from cyphermox):

  On amd64 (no EFI) under qemu/libvirt, qxl graphics:
  - upgrading just libglib2.0-0 from 16.04 on top of 14.04.4: PASS
  - upgrading ubuntu-desktop (running gnome-shell) 14.04.4 to 16.04: PASS
  - upgrading ubuntu-desktop (running xubuntu-session) 14.04.4 to 16.04: PASS
  - manually upgrading compiz and other packages to 16.04 versions; after 
adding xenial sources:
    - compiz and related packages (http://paste.ubuntu.com/15415280/) : PASS
    - xserver-xorg and related: PASS
    - unity and related: PASS
    - ubuntu-desktop: PASS
    - libgl1-mesa-dri: PASS
    - apt-get dist-upgrade: FAIL (screensaver may have kicked in)
  - standard upgrading 14.04.4 to 16.04; screensaver disabled: FAIL (looked 
fine, but upgrade eventually froze, might well be a different issue)
  - re-enabling screensaver after upgrade, before reboot: TODO (above failed)

  On ppc64el:
  - upgrading ubuntu-server 14.04.4 -> 16.04: PASS

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Mar  9 17:01:27 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Beta amd64 (20160224)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1565123] [NEW] package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: missing dependency File/Find.pm

2016-04-01 Thread Åke Svedin

Public bug reported:

Did do-release-upgrade -d from ubuntu 14.04.

>From screenlog.0:

Preparing to unpack .../lvm2_2.02.133-1ubuntu8_i386.deb ...
Can't locate File/Find.pm in @INC (you may need to install the File::Find 
module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.22.1 
/usr/local/share/per
l/5.22.1 /usr/lib/i386-linux-gnu/perl5/5.22 /usr/share/perl5 
/usr/lib/i386-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl 
/usr/lib/i386-linux-gnu/perl-
base .) at /usr/bin/deb-systemd-helper line 88.
BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line 88.
dpkg: error processing archive 
/var/cache/apt/archives/lvm2_2.02.133-1ubuntu8_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 2
dpkg: considering deconfiguration of lvm2, which would be broken by 
installation of initramfs-tools ...
dpkg: yes, will deconfigure lvm2 (broken by initramfs-tools)
Preparing to unpack .../initramfs-tools_0.122ubuntu6_all.deb ...
De-configuring lvm2 (2.02.98-6ubuntu2) ...
Unpacking initramfs-tools (0.122ubuntu6) over (0.103ubuntu4.3) ...
dpkg: warning: unable to delete old directory '/var/lib/initramfs-tools': 
Directory not empty
dpkg: warning: unable to delete old directory '/etc/initramfs-tools/conf.d': 
Directory not empty
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/lvm2.0.crash'

Ran "aptitude install perl-modules-5.22" afterwards for the dependency
and it also allowed me to continue to bother with the other unrelated
errors :)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.98-6ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
Uname: Linux 3.13.0-83-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
Date: Fri Apr  1 23:40:14 2016
DuplicateSignature: package:lvm2:2.02.98-6ubuntu2:subprocess new 
pre-installation script returned error exit status 2
ErrorMessage: subprocess new pre-installation script returned error exit status 
2
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.0.1ubuntu2.11
SourcePackage: lvm2
Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess new 
pre-installation script returned error exit status 2
UpgradeStatus: Upgraded to xenial on 2016-04-01 (0 days ago)

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


** Tags: apport-package i386 third-party-packages xenial

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

Title:
  package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: missing
  dependency File/Find.pm

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Did do-release-upgrade -d from ubuntu 14.04.

  From screenlog.0:

  Preparing to unpack .../lvm2_2.02.133-1ubuntu8_i386.deb ...
  Can't locate File/Find.pm in @INC (you may need to install the File::Find 
module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.22.1 
/usr/local/share/per
  l/5.22.1 /usr/lib/i386-linux-gnu/perl5/5.22 /usr/share/perl5 
/usr/lib/i386-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl 
/usr/lib/i386-linux-gnu/perl-
  base .) at /usr/bin/deb-systemd-helper line 88.
  BEGIN failed--compilation aborted at /usr/bin/deb-systemd-helper line 88.
  dpkg: error processing archive 
/var/cache/apt/archives/lvm2_2.02.133-1ubuntu8_i386.deb (--unpack):
   subprocess new pre-installation script returned error exit status 2
  dpkg: considering deconfiguration of lvm2, which would be broken by 
installation of initramfs-tools ...
  dpkg: yes, will deconfigure lvm2 (broken by initramfs-tools)
  Preparing to unpack .../initramfs-tools_0.122ubuntu6_all.deb ...
  De-configuring lvm2 (2.02.98-6ubuntu2) ...
  Unpacking initramfs-tools (0.122ubuntu6) over (0.103ubuntu4.3) ...
  dpkg: warning: unable to delete old directory '/var/lib/initramfs-tools': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/initramfs-tools/conf.d': 
Directory not empty
  ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/lvm2.0.crash'

  Ran "aptitude install perl-modules-5.22" afterwards for the dependency
  and it also allowed me to continue to bother with the other unrelated
  errors :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lvm2 2.02.98-6ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Fri Apr  1 23:40:14 2016
  DuplicateSignature: package:lvm2:2.02.98-6ubuntu2:subprocess new 
pre-installation script returned error exit status 2
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.1ubuntu2.11
  SourcePackage: lvm2
  Title: package lvm2 2.02.98-6ubuntu2 failed to install/upgrade: subprocess 
new

[Touch-packages] [Bug 320700] Re: gvim rendering is slow

2016-04-01 Thread Eric Jiang

I am running VIM 7.4 on Ubuntu 14.04.4 and noticed that this problem
only appeared *after* I switched to an AMD Radeon 7770 graphics card.
Previously, with my Nvidia graphics card this problem did not exist.

I am running the fglrx-updates proprietary driver provided by the built-
in "Additional drivers" tool (2:15.201-0ubuntu0.14.04.1).

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

Title:
  gvim rendering is slow

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: vim

  Rendering in gvim is very slow compared to previous Ubuntu releases.
  It's usable, but takes patience. I'm using vim/gvim 7.1.314-3ubuntu3.1
  on Ubuntu 8.10.

  Others have reported this same issue on a thread from the vim mailing list. 
Many solutions have been tried w/o success:
  http://groups.google.com/group/vim_use/browse_thread/thread/dd1d8d9a799adf4a

  From the thread, someone provided this benchmark script:
  -- -- --
  " Benchmark vim's redrawing speed
  let i = 0
  while i < 2000
1
redraw
$
redraw
let i = i + 1
  endwhile
  qa!
  -- -- --

  I've run it with /etc/init.d/README as an input file (just to pick
  something consistent across Ubuntu machines):

  $ time vim -u NONE -U NONE  -S test-redraw-speed.vim /etc/init.d/README 
  real  0m5.407s
  user  0m0.568s
  sys   0m0.048s

  $ time gvim -u NONE -U NONE -f -S test-redraw-speed.vim /etc/init.d/README 
  real  3m27.614s
  user  0m11.685s
  sys   0m0.312s

  As you can see gvim is almost 40x slower then vim (running in gnome-
  terminal). You'd expect gvim to be slower then vim, but not by this
  much. Note, from the thread, not all users experience this huge
  difference. Some only report 2-3x slowdown, which I'd be very happy
  with at this point :)

  I'm using the radeon X11 driver (open source) on a ThinkPad T42p, and
  do _not_ experience slow rendering in other apps (for example, gedit).

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

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

[Touch-packages] [Bug 1565059] Re: command when printing on Epson L355, the printer prints nothing freezes and ubuntu 16.04 in unity so as gnome

2016-04-01 Thread Till Kamppeter

Please follow the instructions on
https://wiki.ubuntu.com/DebuggingPrintingProblems, especially of the
section "CUPS error_log". Thanks.

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

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

Title:
  command when printing on Epson L355, the printer prints nothing
  freezes and ubuntu 16.04 in unity so as gnome

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  command when printing on Epson L355, the printer prints nothing
  freezes and ubuntu 16.04 in unity so as gnome

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

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

[Touch-packages] [Bug 1565059] Re: command when printing on Epson L355, the printer prints nothing freezes and ubuntu 16.04 in unity so as gnome

2016-04-01 Thread Brian Murray

** Package changed: ubuntu => cups (Ubuntu)

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

Title:
  command when printing on Epson L355, the printer prints nothing
  freezes and ubuntu 16.04 in unity so as gnome

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  command when printing on Epson L355, the printer prints nothing
  freezes and ubuntu 16.04 in unity so as gnome

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

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

[Touch-packages] [Bug 1565059] [NEW] command when printing on Epson L355, the printer prints nothing freezes and ubuntu 16.04 in unity so as gnome

You have been subscribed to a public bug:

command when printing on Epson L355, the printer prints nothing freezes
and ubuntu 16.04 in unity so as gnome

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


** Tags: bot-comment
-- 
command when printing on Epson L355, the printer prints nothing freezes and 
ubuntu 16.04 in unity so as gnome
https://bugs.launchpad.net/bugs/1565059
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups 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 1480274] Re: Music plays for about 0.5 seconds through speakers when headphones removed

2016-04-01 Thread L D

I've just checked and this is still happening. I'm using an E5. The
music does pause but only after playing for approximately 0.5 seconds
out of the speakers.

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

Title:
  Music plays for about 0.5 seconds through speakers when headphones
  removed

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Music App:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu RTM:
  New

Bug description:
  If you remove the headphones while music is playing, the sound comes
  out of the loudspeakers for about 0.5 seconds before stopping.

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

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

[Touch-packages] [Bug 1565103] Re: bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app

2016-04-01 Thread Gustavo Pichorim Boiko

** Description changed:

  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.
  
  Steps to reproduce:
  
  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.
  
- Another case is when launching messaging-app or dialer-app. we have a
- first time dialog that appears behind the wizard. Not sure if that's
- expected, but seems to cause a bad user experience to me.
+ Another case is when launching messaging-app or dialer-app in a dual sim
+ environment. We have a first time dialog that appears behind the wizard.
+ Not sure if that's expected, but seems to cause a bad user experience to
+ me.

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

Title:
  bottom edge first time wizard is being incorrectly displayed on
  dialer-app and messaging-app

Status in unity8 package in Ubuntu:
  New

Bug description:
  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.

  Steps to reproduce:

  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

  Another case is when launching messaging-app or dialer-app in a dual
  sim environment. We have a first time dialog that appears behind the
  wizard. Not sure if that's expected, but seems to cause a bad user
  experience to me.

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

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

[Touch-packages] [Bug 1565102] [NEW] The AlwaysShared option for lightdm does not work.

2016-04-01 Thread mikenash

Public bug reported:

Setup lightdm on Ubuntu 16.04 s390x beta2.  Successfully updated
software.  Changed lightdm.conf to use the AlwaysShared option so that I
could share a VNC session.  This did not work.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.0-0ubuntu2 [modified: lib/systemd/system/lightdm.service]
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic s390x
ApportVersion: 2.20.1-0ubuntu1
Architecture: s390x
Date: Fri Apr  1 17:19:06 2016
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.pam.d.lightdm: 2016-03-31T11:20:02.696961
mtime.conffile..etc.pam.d.lightdm.greeter: 2016-03-31T11:47:26.478007

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


** Tags: apport-bug s390x xenial

** Summary changed:

- The AlwaysShared otion for lightdm does not work.
+ The AlwaysShared option for lightdm does not work.

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

Title:
  The AlwaysShared option for lightdm does not work.

Status in lightdm package in Ubuntu:
  New

Bug description:
  Setup lightdm on Ubuntu 16.04 s390x beta2.  Successfully updated
  software.  Changed lightdm.conf to use the AlwaysShared option so that
  I could share a VNC session.  This did not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.0-0ubuntu2 [modified: 
lib/systemd/system/lightdm.service]
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic s390x
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: s390x
  Date: Fri Apr  1 17:19:06 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2016-03-31T11:20:02.696961
  mtime.conffile..etc.pam.d.lightdm.greeter: 2016-03-31T11:47:26.478007

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

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

[Touch-packages] [Bug 1565103] [NEW] bottom edge first time wizard is being incorrectly displayed on dialer-app and messaging-app

2016-04-01 Thread Tiago Salem Herrmann

Public bug reported:

A new bottom edge wizard is being displayed in the recent images, but
there are cases where it is being displayed when it shouldn't.

Steps to reproduce:

1) Flash the phone with --wipe.
2) Before opening dialer-app, lock the phone and receive a call.
3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

Another case is when launching messaging-app or dialer-app. we have a
first time dialog that appears behind the wizard. Not sure if that's
expected, but seems to cause a bad user experience to me.

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: 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/1565103

Title:
  bottom edge first time wizard is being incorrectly displayed on
  dialer-app and messaging-app

Status in unity8 package in Ubuntu:
  New

Bug description:
  A new bottom edge wizard is being displayed in the recent images, but
  there are cases where it is being displayed when it shouldn't.

  Steps to reproduce:

  1) Flash the phone with --wipe.
  2) Before opening dialer-app, lock the phone and receive a call.
  3) Once you accept the call, dialer-app is launched and instead of the live 
call view, the wizard is displayed on top of it, but there is no bottom edge on 
that screen, and I believe in this case we should not display any wizards, 
specially because the phone is locked, but even if the phone was unlocked, we 
should not display the wizard if the view does not have bottom edge enabled.

  Another case is when launching messaging-app or dialer-app. we have a
  first time dialog that appears behind the wizard. Not sure if that's
  expected, but seems to cause a bad user experience to me.

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

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

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

2016-04-01 Thread John Johansen

@Jamie, I had assumed we would be using --skip-kernel-load. I was just
bringing up that policy versioning is not just about having different
versions of policy for different kernels but also about dealing with
failure cases.

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged
Status in click-apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and when it does, it is typically for policy)
  2. Investigate ways to utilize the custom tarball and rootfs precompiled
     cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and
     click-apparmor are updated: DONE
  3. Improve cache handling for app store apps (eg, having the app store
     server precompile them so that the device can download them when it
     needs to rather than having to regenerate them itself): WONTFIX
     (doesn't scale)
  4. For systems with apt upgrades, compile the policy either during
     install or on kernel upgrade rather than on boot. For systems with
     read-only fs-style upgrades, compile the policy prior to reboot
     rather than on boot.
  5. Support cache files per kernel .features file (or kernel version).
     This will allow people to boot into a previous kernel without having
     to recompile policy
  6. Improve parser compile time
  7. Investigate how to utilize profile composition and profile stacking to
     decrease compile and load times (eg, one idea is that the policy template
     is compiled once and each policy group once such that the parser need
     only stitch the already compiled bits together)
  8. For Ubuntu Touch/Personal system-image based systems, investigate ways 
 to utilize the update tarball and compile policy before rebooting to
 improve the user experience

  Work is planned for the medium term for '1-3' with '4

[Touch-packages] [Bug 1565101] [NEW] linker failures possibly due to wrong ABI config

2016-04-01 Thread Karthik Sarma

Public bug reported:

Hello,

I'm not really an expert in this sort of thing, but I was having trouble
building things that depend on glog-dev in 15.10 (such as FB folly).
Some google searching found me this thread:
https://groups.google.com/d/msg/caffe-users/a6TDx89IByY/lTWaK0dPBQAJ
from folks having trouble building caffe. The linked poster suggests
that this is because the package in the repo has been built with
-D_GLIBCXX_USE_CXX11_ABI=0 rather than 1. I was able to fix my problem
by recompiling from the source distribution, which might lend some
credence.

Anyway, just wanted to make sure you folks were aware of this.

** Affects: google-glog (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  linker failures possibly due to wrong ABI config

Status in google-glog package in Ubuntu:
  New

Bug description:
  Hello,

  I'm not really an expert in this sort of thing, but I was having
  trouble building things that depend on glog-dev in 15.10 (such as FB
  folly). Some google searching found me this thread:
  https://groups.google.com/d/msg/caffe-users/a6TDx89IByY/lTWaK0dPBQAJ
  from folks having trouble building caffe. The linked poster suggests
  that this is because the package in the repo has been built with
  -D_GLIBCXX_USE_CXX11_ABI=0 rather than 1. I was able to fix my problem
  by recompiling from the source distribution, which might lend some
  credence.

  Anyway, just wanted to make sure you folks were aware of this.

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

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

[Touch-packages] [Bug 1565083] Re: 16.04 beta2, cannot override udev network interface name in VM

2016-04-01 Thread Marc Na

OK, so I have spent quite some time typing this bug report but ultimately found 
the solution.
I leave a comment in case other people face the same issue.

After a lot of head scratching:

You have to run "sudo update-initramfs -u" to regenerate the image!

What a pity it's not in the docs! (upstream issue?)

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

Title:
  16.04 beta2, cannot override udev network interface name in VM

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  I just cannot seem to override a network interface name on a Ubuntu Server 
16.04 beta 2 fresh install.
  Reproduce steps were tried on both VirtualBox 4 and VMware Player 7.

  (Sadly, despite updating apt, I could not find apport in the
  repositories, so please bear with me)

  --N.B.: following is not an apport output--
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-3ubuntu1
  Package: udev 229-3ubuntu1
  Uname: Linux ubuntu 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  Architecture: amd64
  InstallationMedia: ubuntu-16.04-beta2-server-amd64.iso, checksummed (20160323)
  ProcEnviron:
   LANG=en_US.UTF-8
  UpgradeStatus: fresh install
  --

  Steps to Reproduce:
  1. Setup VM with a network card (VirtualBox: Intel Pro/1000 MT Server; VMware 
Player: E1000 or (hand-edited vmx) vmxnet3
  2. Install
  3. Upgrade
  4. Login
  5. Run "networkctl" and note interface name
  6. Run "/sbin/udevadm test /sys/class/net/ens160" replacing ens160 with the 
interface name
  ID_PATH=pci-:03:00.0
  ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  7. Create an override rule : "sudo vi /etc/systemd/50-eth0.link"  -- see 
systemd.link(5) -- with these contents:
  [Match]
  Path=pci-:03:00.0*

  [Link]
  Name=eth0
  MACAddressPolicy=persistent

  8. Run again "/sbin/udevadm test /sys/class/net/ens160"
  ID_NET_LINK_FILE=/etc/systemd/network/50-eth0.link
  9. Run "sudo reboot"
  10. Login and run "networkctl"

  Expected result:
  interface name is now eth0

  Actual Result:
  No change in interface name.

  Other thoughts:
  - journalctl does not provide extra info, just that the interface has been 
renamed to the persistent name as usual.

  - /etc/udev/rules.d/ is empty.

  - network-manager package is not installed

  - Have also tried adding a blank "NamePolicy=" line just under [Link]

  - Have tried with Name=ethfoo to avoid potential conflicts; no dice

  - Of course, you can disable the new names by adding net.ifnames=0
  kernel boot option to grub; it works (but then you don't assign an
  name to a matching device).

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

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

[Touch-packages] [Bug 1565083] [NEW] 16.04 beta2, cannot override udev network interface name in VM

2016-04-01 Thread Marc Na

Public bug reported:

Hello,

I just cannot seem to override a network interface name on a Ubuntu Server 
16.04 beta 2 fresh install.
Reproduce steps were tried on both VirtualBox 4 and VMware Player 7.

(Sadly, despite updating apt, I could not find apport in the
repositories, so please bear with me)

--N.B.: following is not an apport output--
DistroRelease: Ubuntu 16.04
Package: systemd 229-3ubuntu1
Package: udev 229-3ubuntu1
Uname: Linux ubuntu 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
Architecture: amd64
InstallationMedia: ubuntu-16.04-beta2-server-amd64.iso, checksummed (20160323)
ProcEnviron:
 LANG=en_US.UTF-8
UpgradeStatus: fresh install
--

Steps to Reproduce:
1. Setup VM with a network card (VirtualBox: Intel Pro/1000 MT Server; VMware 
Player: E1000 or (hand-edited vmx) vmxnet3
2. Install
3. Upgrade
4. Login
5. Run "networkctl" and note interface name
6. Run "/sbin/udevadm test /sys/class/net/ens160" replacing ens160 with the 
interface name
ID_PATH=pci-:03:00.0
ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
7. Create an override rule : "sudo vi /etc/systemd/50-eth0.link"  -- see 
systemd.link(5) -- with these contents:
[Match]
Path=pci-:03:00.0*

[Link]
Name=eth0
MACAddressPolicy=persistent

8. Run again "/sbin/udevadm test /sys/class/net/ens160"
ID_NET_LINK_FILE=/etc/systemd/network/50-eth0.link
9. Run "sudo reboot"
10. Login and run "networkctl"

Expected result:
interface name is now eth0

Actual Result:
No change in interface name.

Other thoughts:
- journalctl does not provide extra info, just that the interface has been 
renamed to the persistent name as usual.

- /etc/udev/rules.d/ is empty.

- network-manager package is not installed

- Have also tried adding a blank "NamePolicy=" line just under [Link]

- Have tried with Name=ethfoo to avoid potential conflicts; no dice

- Of course, you can disable the new names by adding net.ifnames=0
kernel boot option to grub; it works (but then you don't assign an name
to a matching device).

** 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/1565083

Title:
  16.04 beta2, cannot override udev network interface name in VM

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello,

  I just cannot seem to override a network interface name on a Ubuntu Server 
16.04 beta 2 fresh install.
  Reproduce steps were tried on both VirtualBox 4 and VMware Player 7.

  (Sadly, despite updating apt, I could not find apport in the
  repositories, so please bear with me)

  --N.B.: following is not an apport output--
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-3ubuntu1
  Package: udev 229-3ubuntu1
  Uname: Linux ubuntu 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08:31 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  Architecture: amd64
  InstallationMedia: ubuntu-16.04-beta2-server-amd64.iso, checksummed (20160323)
  ProcEnviron:
   LANG=en_US.UTF-8
  UpgradeStatus: fresh install
  --

  Steps to Reproduce:
  1. Setup VM with a network card (VirtualBox: Intel Pro/1000 MT Server; VMware 
Player: E1000 or (hand-edited vmx) vmxnet3
  2. Install
  3. Upgrade
  4. Login
  5. Run "networkctl" and note interface name
  6. Run "/sbin/udevadm test /sys/class/net/ens160" replacing ens160 with the 
interface name
  ID_PATH=pci-:03:00.0
  ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  7. Create an override rule : "sudo vi /etc/systemd/50-eth0.link"  -- see 
systemd.link(5) -- with these contents:
  [Match]
  Path=pci-:03:00.0*

  [Link]
  Name=eth0
  MACAddressPolicy=persistent

  8. Run again "/sbin/udevadm test /sys/class/net/ens160"
  ID_NET_LINK_FILE=/etc/systemd/network/50-eth0.link
  9. Run "sudo reboot"
  10. Login and run "networkctl"

  Expected result:
  interface name is now eth0

  Actual Result:
  No change in interface name.

  Other thoughts:
  - journalctl does not provide extra info, just that the interface has been 
renamed to the persistent name as usual.

  - /etc/udev/rules.d/ is empty.

  - network-manager package is not installed

  - Have also tried adding a blank "NamePolicy=" line just under [Link]

  - Have tried with Name=ethfoo to avoid potential conflicts; no dice

  - Of course, you can disable the new names by adding net.ifnames=0
  kernel boot option to grub; it works (but then you don't assign an
  name to a matching device).

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

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

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

@Pat, this is assigned to me but the changes needed are probably for
phonedations and possibly unity8. The click-apparmor patch for --with-
progress would be fast and wouldn't need our help (but we could do that
if needed). The security team would be happy to answer any questions and
advise on the implementation of course. I'm going to remove the
assignment from me for now.

** Changed in: canonical-devices-system-image
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

** Also affects: click-apparmor (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: click-apparmor (Ubuntu)
   Status: New => Triaged

** Changed in: click-apparmor (Ubuntu)
   Importance: Undecided => Low

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged
Status in click-apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and when it does, it is typically for policy)
  2. Investigate ways to utilize the custom tarball and rootfs precompiled
     cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and
     click-apparmor are updated: DONE
  3. Improve cache handling for app store apps (eg, having the app store
     server precompile them so that the device can download them when it
     needs to rather than having to regenerate them itself): WONTFIX
     (doesn't scale)
  4. For systems with apt upgrades, compile the policy either during
     install or on kernel upgrade rather than on boot. For systems with
     read-only fs-style upgrades, compile the policy prior to reboot
     rather than on boot.
  5. Support cache files per kernel .features file (or kernel version).
     This will allow people to boot into a previous kernel without having
     to recompile policy
  6. Improve parser compile time
  7. Investigate how to utilize profile com

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

Adding click-apparmor task with same priority as the for canonical
system image.

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged
Status in click-apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and when it does, it is typically for policy)
  2. Investigate ways to utilize the custom tarball and rootfs precompiled
     cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and
     click-apparmor are updated: DONE
  3. Improve cache handling for app store apps (eg, having the app store
     server precompile them so that the device can download them when it
     needs to rather than having to regenerate them itself): WONTFIX
     (doesn't scale)
  4. For systems with apt upgrades, compile the policy either during
     install or on kernel upgrade rather than on boot. For systems with
     read-only fs-style upgrades, compile the policy prior to reboot
     rather than on boot.
  5. Support cache files per kernel .features file (or kernel version).
     This will allow people to boot into a previous kernel without having
     to recompile policy
  6. Improve parser compile time
  7. Investigate how to utilize profile composition and profile stacking to
     decrease compile and load times (eg, one idea is that the policy template
     is compiled once and each policy group once such that the parser need
     only stitch the already compiled bits together)
  8. For Ubuntu Touch/Personal system-image based systems, investigate ways 
 to utilize the update tarball and compile policy before rebooting to
 improve the user experience

  Work is planned for the medium term for '1-3' with '4' and '5' coming
  as needed. '6' will of course help, but it is already very optimized
  and compile average ~2 seconds on armhf per profile (n

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

@John, I was thinking of using --skip-kernel-load so the policy is still
in the running kernel. I agree that versioned policy is safer though.

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged
Status in click-apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and when it does, it is typically for policy)
  2. Investigate ways to utilize the custom tarball and rootfs precompiled
     cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and
     click-apparmor are updated: DONE
  3. Improve cache handling for app store apps (eg, having the app store
     server precompile them so that the device can download them when it
     needs to rather than having to regenerate them itself): WONTFIX
     (doesn't scale)
  4. For systems with apt upgrades, compile the policy either during
     install or on kernel upgrade rather than on boot. For systems with
     read-only fs-style upgrades, compile the policy prior to reboot
     rather than on boot.
  5. Support cache files per kernel .features file (or kernel version).
     This will allow people to boot into a previous kernel without having
     to recompile policy
  6. Improve parser compile time
  7. Investigate how to utilize profile composition and profile stacking to
     decrease compile and load times (eg, one idea is that the policy template
     is compiled once and each policy group once such that the parser need
     only stitch the already compiled bits together)
  8. For Ubuntu Touch/Personal system-image based systems, investigate ways 
 to utilize the update tarball and compile policy before rebooting to
 improve the user experience

  Work is planned for the medium term for '1-3' with '4' and '5' coming
  as needed. '6' will of course help, but it is already very optimized

[Touch-packages] [Bug 1565080] [NEW] ubuntuBSD support

2016-04-01 Thread Jon Boden

Public bug reported:

Hi

Please could you apply attached patch to make mesa buildable on
ubuntuBSD? It just needs to adjust a few dependencies.

Thanks!

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


** Tags: patch ubuntubsd

** Patch added: "mesa.diff"
   https://bugs.launchpad.net/bugs/1565080/+attachment/4619847/+files/mesa.diff

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

Title:
  ubuntuBSD support

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi

  Please could you apply attached patch to make mesa buildable on
  ubuntuBSD? It just needs to adjust a few dependencies.

  Thanks!

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

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

[Touch-packages] [Bug 1564351] Re: "Swipe from the left edge to open the launcher" - do not work on the desktop

2016-04-01 Thread Michael Terry

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Opinion

** Changed in: unity8 (Ubuntu)
   Status: Opinion => In Progress

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

Title:
  "Swipe from the left edge to open the launcher" - do not work on the
  desktop

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1322353] Re: [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all (The speakers had worked before with 14.04 but suddenly they do not anymore)

2016-04-01 Thread Thomas G Henry

I'm hitting the same thing.
https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/289640

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

Title:
  [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all (The
  speakers had worked before with 14.04 but suddenly they do not
  anymore)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I do not know which update has caused the problem. The speakers had
  worked already with 14.04 but since a few days there is no sound
  anymore.

  Headphones work correctly.

  I have a Thinkpad S531 Laptop which is certified to work with Ubuntu.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  2609 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 22 23:16:22 2014
  InstallationDate: Installed on 2014-04-25 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  2609 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKET24WW (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B00050GE
  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:bvrGKET24WW(1.04):bd05/02/2013:svnLENOVO:pn20B00050GE:pvrThinkPadS5-S531:rvnLENOVO:rn20B00050GE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B00050GE
  dmi.product.version: ThinkPad S5-S531
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1322353] Re: [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all (The speakers had worked before with 14.04 but suddenly they do not anymore)

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

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

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

Title:
  [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all (The
  speakers had worked before with 14.04 but suddenly they do not
  anymore)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I do not know which update has caused the problem. The speakers had
  worked already with 14.04 but since a few days there is no sound
  anymore.

  Headphones work correctly.

  I have a Thinkpad S531 Laptop which is certified to work with Ubuntu.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  2609 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 22 23:16:22 2014
  InstallationDate: Installed on 2014-04-25 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Internes Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  2609 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [20B00050GE, Realtek ALC269VC, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKET24WW (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B00050GE
  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:bvrGKET24WW(1.04):bd05/02/2013:svnLENOVO:pn20B00050GE:pvrThinkPadS5-S531:rvnLENOVO:rn20B00050GE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B00050GE
  dmi.product.version: ThinkPad S5-S531
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1565077] [NEW] Rhythmbox missing a GStreamer plug-in

2016-04-01 Thread Curtis Schroeder

Public bug reported:

Rhythmbox was not able to play some of my FLAC files until I installed
the gstreamer1.0-pulseaudio plug-in.

Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

rhythmbox:
  Installed: 3.3-1ubuntu6
  Candidate: 3.3-1ubuntu6
  Version table:
 *** 3.3-1ubuntu6 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

Playback stopped and the track was marked with a warning symbol. Opening
the track properties dialog showed a GStreamer missing plug-in error
message.

Recommended the gstreamer1.0-pulseaudio plug-in be added to the 16.04
desktop distro to improve the out-of-box experience for less experienced
users.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.0-1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Apr  1 21:05:20 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-31 (1 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug gstreamer rhythmbox xenial

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

Title:
  Rhythmbox missing a GStreamer plug-in

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Rhythmbox was not able to play some of my FLAC files until I installed
  the gstreamer1.0-pulseaudio plug-in.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  rhythmbox:
Installed: 3.3-1ubuntu6
Candidate: 3.3-1ubuntu6
Version table:
   *** 3.3-1ubuntu6 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Playback stopped and the track was marked with a warning symbol.
  Opening the track properties dialog showed a GStreamer missing plug-in
  error message.

  Recommended the gstreamer1.0-pulseaudio plug-in be added to the 16.04
  desktop distro to improve the out-of-box experience for less
  experienced users.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr  1 21:05:20 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-31 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

2016-04-01 Thread John Johansen

Versioned policy is needed on touch if the compile is going to be done
before reboot. You do not want to blow away currently enforcing policy
and install the new version and then run into a situation where you
fail, or don't reboot.  So at the very least for the failure case we
need to support versioned policy.

Another reason however is that policy compiles currently still take a
long time and the user should still be able to use their phone while the
compile is happening.

The good news is that the features set for a given phone kernel has not
been updated, and so we won't hit this yet and can do a first pass
without it.

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and when it does, it is typically for policy)
  2. Investigate ways to utilize the custom tarball and rootfs precompiled
     cache files on upgrades when apparmor, apparmor-easyprof-ubuntu and
     click-apparmor are updated: DONE
  3. Improve cache handling for app store apps (eg, having the app store
     server precompile them so that the device can download them when it
     needs to rather than having to regenerate them itself): WONTFIX
     (doesn't scale)
  4. For systems with apt upgrades, compile the policy either during
     install or on kernel upgrade rather than on boot. For systems with
     read-only fs-style upgrades, compile the policy prior to reboot
     rather than on boot.
  5. Support cache files per kernel .features file (or kernel version).
     This will allow people to boot into a previous kernel without having
     to recompile policy
  6. Improve parser compile time
  7. Investigate how to utilize profile composition and profile stacking to
     decrease compile and load times (eg, one idea is that the policy template
     is compiled once

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

A few things I neglected to mention that John reminded me of are

1. if the kernel changes its apparmor feature set or the apparmor parser
itself changes how it generates policy, we'll still be running the old
kernel and parser. This will happen on an upgrade from 15.04 to 16.04
for example. If the device tarball exported the apparmor feature set (it
can be mocked as a text file-- we do that for custom tarballs already
for example) then we can point the parser at that. Furthermore the
parser could be extracted from the tarball as part of the recompile
step.

Since most upgrades very-much-intentionally do not change the parser or
the feature set, I think the first iteration could avoid dealing with
the apparmor features file and the parser. The second iteration could
incorporate it.

2. Due to how profile caching is currently implemented, the recompiling
caches is a one way operation. In other words, if prior to reboot we
recompile all the policy that invalidates the old caches. If on reboot
the boot detects that a recompile is needed (eg, we got something wrong
before reboot-- eg, the kernel in the device tarball was updated but
someone forgot to update the mocked features file), then the recompile
will still happen on reboot. If the processes surrounding updates are
sufficient and QA is involved, this should be an avoidable situation.

3. The security team has worked on versioned policy caches in previous
cycles but the work is incomplete and deprioritized. Depending on how
things are ultimately implemented, its possible versioned policy caches
could help with the implementation. I think performing point '8' on
Touch and carefully handling the features file and parser changes, this
is probably not needed (there isn't a concept of rolling back on Touch
for example).

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gai

[Touch-packages] [Bug 1565063] [NEW] Update the chromium version in the user agent

Public bug reported:

We have never updated the version, which is 35, and now we are based on 49
While this may not have any impact it does reflect the core support we have, 
and its possible some sites may check it.

Ideally we would query oxide for this dynamically.

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

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

Title:
  Update the chromium version in the user agent

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  We have never updated the version, which is 35, and now we are based on 49
  While this may not have any impact it does reflect the core support we have, 
and its possible some sites may check it.

  Ideally we would query oxide for this dynamically.

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

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

[Touch-packages] [Bug 1538703] Re: Playlist next/prev controls only available when player is in foreground

2016-04-01 Thread Jim Hodapp

** Changed in: media-hub (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: qtubuntu-media (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 unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1538703

Title:
  Playlist next/prev controls only available when player is in
  foreground

Status in Canonical System Image:
  In Progress
Status in indicator-sound package in Ubuntu:
  Invalid
Status in media-hub package in Ubuntu:
  Fix Committed
Status in qtubuntu-media package in Ubuntu:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Invalid

Bug description:
  Switch to the dash (i.e. app scope) while music app is playing
  The indicator switches to mediaplayer with controls disabled

  Note also that the media player is shown with controls disabled on a
  fresh boot when no media has ever been played, the indicator should
  only show controls after playback.

  Something in the scopes is incorrectly telling media hub there is a
  new ctive player.

  Install the music app from the store
  Start a playlist in music app
  Switch apps
  Next and Prev are disabled in the indicator

  This was fixed after a reboot.

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

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

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-01 Thread Dmitry Shachnev

The mentioned fix is https://codereview.qt-project.org/154459. If it
gets accepted upstream, I'll try to make sure it gets included in Xenial
(or at least Xenial-updates).

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1564625] Re: aa-complain exits 0 when path not found

2016-04-01 Thread Christian Boltz

** Tags added: aa-tools

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

Title:
  aa-complain exits 0 when path not found

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I'm using juju to deploy apparmor profiles and I've found that when
  the apparmor path isn't found the command still exists 0.  If this
  exited with a non zero status I could detect I had a problem in my
  code and take action :)

  root@ip-172-31-29-100:/etc/apparmor.d/local# aa-complain foo
  Can't find foo in the system path list. If the name of the application
  is correct, please run 'which foo' as a user with correct PATH
  environment set up in order to find the fully-qualified path and
  use the full path as parameter.
  root@ip-172-31-29-100:/etc/apparmor.d/local# echo $?
  0

  Some context on the environment:
  root@ip-172-31-29-100:/etc/apparmor.d/local# cat /etc/issue
  Ubuntu 14.04.4 LTS \n \l

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

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

[Touch-packages] [Bug 1565055] [NEW] google hangouts thinks we are unsupported

Public bug reported:

We should be able to work properly with webrtc. Instead I got presented
the unsupported page listing chrome, firefox and safari

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: Bill Filler (bfiller)
 Status: Confirmed

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

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

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 11

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

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

Title:
  google hangouts thinks we are unsupported

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  We should be able to work properly with webrtc. Instead I got
  presented the unsupported page listing chrome, firefox and safari

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

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

[Touch-packages] [Bug 1350598] Re: AppArmor policy compile improvements

@Pat, I think we actually want '8' for the phone. I mentioned what needs
to happen in the description. I'll mention it again here:

'8' can be implemented now to improve the user experience:
"
> Sorry for not being clear. The idea is that when the phone says that
> there is an update, the user has to tap 'Install and Reboot'. The idea > is 
> that before reboot (and therefore still in the unity8 session), we
> look inside what is downloaded, see if there are any policy changes. If
> there are, we extract them and then compile policy with a progress
> meter. The question I posed to you is how hard is it to look inside (or
> provide a manifest of changed packages) and extract what is needed to
> compile policy?

Ok. The update is available as a set of tarballs, available in a fixed
directory. It should be straightforward to check whether any of those
tarballs contains files matching a particular path. If you want to know
whether particular packages have changed, that would be a matter of
extracting the dpkg database and comparing. (We don't otherwise track the
packagewise delta between the images.)

A partial extraction of the tarball based on particular filenames is a
simple matter of tar arguments."

Basically, when the user presses 'Install and reboot". Essentially wherever the 
upgrade code lives it should do something along the lines of:
* download everything
* before installing, peak inside the rootfs to see if things changed, unpack 
the bits that changed, regenerate and recompile click policy with progress meter

I don't know where the upgrade code lives and/or if something needs to
be done with unity8 for the progress meter. aa-clickhook would need to
gain --with-progress.

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

Title:
  AppArmor policy compile improvements

Status in AppArmor:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  apparmor_parser can take a long time to compile policy especially when there 
is a lot of policy, so we want to utilize compiled cache profile as much as 
possible. Cache files will have to be regenerated in the following cases:
   * the kernel .features file is updated (eg, new features are added to
     apparmor in the new kernel)
   * apparmor itself is updated
   * on devices with click packages, apparmor-easyprof-ubuntu and/or
     click-apparmor is updated

  As of 2014-10-02, what can be expected is:

  - Systems with system-image updates (eg, Ubuntu Touch):
    - First boot will use the precompiled cache files in the rootfs or custom
  tarball and be fast
    - Reboots will use the cache files on the device and be fast
    - First boots after upgrades will use the cache files on the device if the
  above conditions are not met and be fast
    - Production devices will not meet any of those conditions except under
  exceptional and rare circumstances (eg, major OS upgrades like 14.10 to
  15.04) and be fast
    - First boots after upgrades that meet one of the conditions will need to
  regenerate the cache. This can happen on development releases where the
  kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates
  - Systems with apt updates (eg, current Ubuntu Desktop and Server):
    - First boot will compile cache files
    - Reboots will use the cache files on the machine and be fast
    - First boots after upgrades will use the cache files on the machine if the
  above conditions are not met and be fast
    - Stable releases of Ubuntu will not meet any of those conditions except
  under exceptional and rare circumstances (eg, major OS upgrades like
  14.10 to 15.04) and be fast
    - First boots after upgrades that meet one of the above conditions will
  need to regenerate the cache. This can happen on development releases
  where the kernel features file, apparmor, apparmor-easyprof-ubuntu or
  click-apparmor are still under development and getting updates

  In addition to the above, updates to only apparmor-easyprof-ubuntu
  will regenerate the cache files for only the policy that is affected
  (eg, if there is a change to the location policy group in policy
  version 1.2, only apps using this policy version and this policy group
  will need to be recompiled).

  Planned improvements (in order of most likely to be done first):
  1. Finetuning the checks to invalidate the cache (eg, .md5sums could only
     be for /etc/apparmor.d/abstractions, ...): WONTFIX (will want an
     md5sum on apparmor_parser since it could change the cache and the md5sum
     will always change. Furthermore, apparmor-easyprof-ubuntu is all policy
     so there is no gain there. click-apparmor could possibly benefit, but
     it doesn't change often and whe

[Touch-packages] [Bug 1546328] Re: Systray option does not work.

2016-04-01 Thread Dmitry Shachnev

Dear Ross,

>> Without appmenu-qt5, the menu works from the systray, but the icon is not 
>> animated. It just shows a red cross all the time, which is misleading for 
>> the user.
>
> Thanks for letting me know that, I will try to look at this issue a bit later.

Can you please check if starting qjackctl with XDG_CURRENT_DESKTOP=Unity
fixes the icon issue you mentioned?

If it does, then I have an idea on how to workaround this bug in Qt (the
idea is to check not XDG_CURRENT_DESKTOP, but rather whether the
StatusNotifierWatcher cmdline ends with indicator-application-service).

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

Title:
  Systray option does not work.

Status in Ubuntu Studio:
  New
Status in qjackctl package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  Setting Qjackctl to "Enable system tray icon" does not display
  Qjackctl's icon and the menu provided by qjackctl from systray is
  blank. Further setting Qjackctl to "Start minimized to system tray"
  makes the application unusable.

  A reboot after Qjackctl to "Enable system tray icon" and  "Start
  minimized to system tray" are set, starting Qjackctl not only doesn't
  show Qjackctl's icon, but the mouse stops working correctly:

  The mouse moves ok, but does not have any hover effect or clicks so
  the menu no longer works and the only way to kill qjackctl is with
  control-alt-F1 (which does still work).

  Qjackctl is the main application used for controlling Jackd or
  jackdbus for those using any of the pro audio software.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qjackctl 0.4.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-lowlatency 4.4.1
  Uname: Linux 4.4.0-4-lowlatency x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 16 14:30:46 2016
  InstallationDate: Installed on 2015-11-19 (89 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151118)
  SourcePackage: qjackctl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1563398] Re: Set the front camera as the default for video media requests

We should also provide a way to select the camera in settings, or better
by dynamically adding an option to the menu

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

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

** Changed in: canonical-devices-system-image
Milestone: None => 11

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => David Barth (dbarth)

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

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

Title:
  Set the front camera as the default for video media requests

Status in Canonical System Image:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  At the moment, the selected camera (in form factors having multiple
  ones) defaults to the back camera which does not work very well for
  cases like hangouts, the container and the browser should default to
  the front camera.

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

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

[Touch-packages] [Bug 1563398] Re: Set the front camera as the default for video media requests

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

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

Title:
  Set the front camera as the default for video media requests

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  At the moment, the selected camera (in form factors having multiple
  ones) defaults to the back camera which does not work very well for
  cases like hangouts, the container and the browser should default to
  the front camera.

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

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

[Touch-packages] [Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

2016-04-01 Thread Mathieu Trudel-Lapierre

Mathew, please, pretty please stop removing tasks, even if they're
marked Invalid.

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

Title:
  Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

Status in dbus package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Install 14.04.4 on a uefi securebooted system
  2. update it
  3. Install openssh-server for debug access
  4. reboot
  5. Hit alt+f2
  6. Type update-manager -d and hit enter

  EXPECTED:
  I expected a smooth transition to 16.04

  ACTUAL:
  System is completely taken out mid way through the process killing the 
session and x also no tty when hitting ctrl+alt+f1-6

  ---

  TESTS RESULTS (from cyphermox):

  On amd64 (no EFI) under qemu/libvirt, qxl graphics:
  - upgrading just libglib2.0-0 from 16.04 on top of 14.04.4: PASS
  - upgrading ubuntu-desktop (running gnome-shell) 14.04.4 to 16.04: PASS
  - upgrading ubuntu-desktop (running xubuntu-session) 14.04.4 to 16.04: PASS
  - manually upgrading compiz and other packages to 16.04 versions; after 
adding xenial sources:
    - compiz and related packages (http://paste.ubuntu.com/15415280/) : PASS
    - xserver-xorg and related: PASS
    - unity and related: PASS
    - ubuntu-desktop: PASS
    - libgl1-mesa-dri: PASS
    - apt-get dist-upgrade: FAIL (screensaver may have kicked in)
  - standard upgrading 14.04.4 to 16.04; screensaver disabled: FAIL (looked 
fine, but upgrade eventually froze, might well be a different issue)
  - re-enabling screensaver after upgrade, before reboot: TODO (above failed)

  On ppc64el:
  - upgrading ubuntu-server 14.04.4 -> 16.04: PASS

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Mar  9 17:01:27 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Beta amd64 (20160224)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1501041] Re: No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up

2016-04-01 Thread Doug McMahon

** Tags added: trusty-lts-wily

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

Title:
  No visible display in non gnome sessions when using nvidia drivers via
  nvidia-prime until screen goes to sleep, then waked up

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged
Status in unity-greeter package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  ** this appears to be that the display is blanked/asleep at greeter & login.
  Forcing or waiting for screen to blank/sleep then waking up restores display
  See comments 8 & 10 for further info, demonstrations **

  Please note that this bug is being filed on a recent 15.10 Ubuntu
  image install but from a gnome session

  In a nutshell -
  Once nividia drivers are installed & used from nvidia-prime there is no 
longer a visible display in unity-greeter nor in an ubuntu session once logged 
in. (a blind log in successfully loads an ubuntu session.
  Everything in the ubuntu session works fine, there are no errors & all the 
related logs look ok, there is just no visible display.

  I can open apps, run commands, copy/create logs, play music, play
  videos, just no display so has to be done blindly from keyboard.

  On the other hand if I install gnome-shell & log in (blindly) to a
  gnome session from greeter then all is well & I get a visible
  display.

  The same behaviour is seen on an Xubuntu image install, once nvidia is
  installed & switched to, no visible display. Again there installing &
  logging into a gnome session works fine with visible display

  nvidia driver version doesn't matter, exact same is seen with current
  15.10 versions & the one I'm currently using (355) from drivers ppa.

  ** this appears to be that the display is blanked/asleep at greeter & login.
  Forcing or waiting for screen to blank/sleep then waking up restores display
  See comment 8 for further info **

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-core 2:1.17.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Sep 29 16:15:21 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-11-generic, x86_64: installed
   nvidia-355, 355.11, 4.2.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-09-28 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150928)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed 
root=UUID=3712249e-a4c8-4b29-9ffb-f9f9e7d5259a ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20150908-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu7
  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-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver

[Touch-packages] [Bug 1564343] Re: Notifications should not dim the screen

2016-04-01 Thread Lukáš Tinkl

** Branch unlinked: lp:~lukas-kde/unity8/dontDimScreen

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

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

Title:
  Notifications should not dim the screen

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Currently, incoming notifications (at least snap decisions - but check
  all of them) dim the screen. In light of convergence, this does not
  make sense for bigger screens and should be removed.

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

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

[Touch-packages] [Bug 989819] Re: Make duplicate signature more specific for DBusException and OSError

2016-04-01 Thread Brian Murray

Hello Sebastien, or anyone else affected,

Accepted apport into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.14.1-0ubuntu3.20 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: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/989819

Title:
  Make duplicate signature more specific for DBusException and OSError

Status in Daisy:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Trusty:
  Fix Committed
Status in apport source package in Xenial:
  Fix Released

Bug description:
  Looking through some db bug examples and saw some incorrect bug
  associations, one example

  "Traceback (most recent call last):
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1090, in on_combobox_locale_chooser_changed
  self.writeUserFormats()
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
  self.writeUserFormatsSetting(userFormats=code)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
  iface.SetFormatsLocale(macr['SYSLOCALE'])
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  DBusException: org.freedesktop.Accounts.Error.PermissionDenied: Not 
authorized"

  has been associated to
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/930785

  "Traceback (most recent call last):
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1081, in on_combobox_locale_chooser_changed
  self.writeUserFormats()
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
  self.writeUserFormatsSetting(userFormats=code)
    File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
  iface.SetFormatsLocale(macr['SYSLOCALE'])
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
  return self._proxy_method(*args, **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
  **keywords)
    File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
  message, timeout)
  DBusException: org.freedesktop.Accounts.Error.Failed: 'bg_BG.UTF-8' is not a 
valid locale name"

  The "functions signature" is the same, the exceptions are different
  though, it should probably consider that as part of the signature

  SRU TEST CASE:
  --
   * Modify /usr/bin/pybuild to append these two lines right after "def 
main(cfg):"

  raise OSError(99, 'some OS error')

   * Now running "pybuild" will provoke an OSError, and you should get a
  /var/crash/_usr_share_dh-python_pybuild.1000.crash

   * With current apport, the crash signature looks like this, i. e. it
  does not include the errno (99):

$ python3 -c 'import apport; r = apport.Report(); 
r.load(open("/var/crash/_usr_share_dh-python_pybuild.1000.crash"

[Touch-packages] [Bug 1508225] [Bug 158255] Re: tipc tool isn't built in iproute2

2016-04-01 Thread Jon Maloy

Hi,
I added a comment to this bug report, noting that this still hasn't been fixed 
in 16.04.
So far, no response...

BR
///Jon Maloy

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

Title:
  tipc tool isn't built in iproute2

Status in iproute2 package in Ubuntu:
  Triaged
Status in iproute2 package in Debian:
  New

Bug description:
  A new tool "tipc" was added to iproute2 v 4.1.1, needed for managing
  the TIPC kernel module.

  Despite being present in the source code, it has not been built in the 
current iproute2 package that comes with 15.10, something forcing all users to 
check out the code and build it manually.
  The reason for the buld failure is that it has a dependency to libmnl-dev, 
although this is not listed in the dependency list. Stephen Hemminger has 
confirmed that that using libmnl in iproute2 is ok, but unfortunately the 
dependency has been made optional, meaning that the build will just silently 
bypass TIPC is libmnl-dev is not found.

  If you just add libmnl-dev to the dependency list and make sure it is
  available when iproute2 is built the problem should be solved. On our
  side we will try to have the optionality removed from iproute2.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: iproute2 4.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 20 17:56:42 2015
  InstallationDate: Installed on 2015-10-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151019)
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1536077] Re: nmcli hangs when running from tty and connecting to wifi

2016-04-01 Thread LinuXperia

I am having the same Problem with nmcli also with same Version.
i could Isolate the Problem however a little more.

If i run the same nmcli command i allways used like
nmcli con up uuid xyz
with sudo aka root rights everything works like it should but not without sudo 
rights like it worked before 

Looks like a Permission Problem.

In my SysLog i have lot of such lines here that pop up every 5 Seconds
suggesting root rights are needed  ..

Apr  1 19:18:20  gnome-session[1791]: (Es konnten nicht alle Prozesse 
identifiziert werden; Informationen über
Apr  1 19:18:20  gnome-session[1791]: nicht-eigene Processe werden nicht 
angezeigt; Root kann sie anzeigen.)
Apr  1 19:18:35  gnome-session[1791]: (Es konnten nicht alle Prozesse 
identifiziert werden; Informationen über
Apr  1 19:18:35  gnome-session[1791]: nicht-eigene Processe werden nicht 
angezeigt; Root kann sie anzeigen.)
Apr  1 19:18:50  gnome-session[1791]: (Es konnten nicht alle Prozesse 
identifiziert werden; Informationen über
Apr  1 19:18:50  gnome-session[1791]: nicht-eigene Processe werden nicht 
angezeigt; Root kann sie anzeigen.)
Apr  1 19:19:05  gnome-session[1791]: (Es konnten nicht alle Prozesse 
identifiziert werden; Informationen über
Apr  1 19:19:05  gnome-session[1791]: nicht-eigene Processe werden nicht 
angezeigt; Root kann sie anzeigen.)
Apr  1 19:19:20  gnome-session[1791]: (Es konnten nicht alle Prozesse 
identifiziert werden; Informationen über
Apr  1 19:19:20  gnome-session[1791]: nicht-eigene Processe werden nicht 
angezeigt; Root kann sie anzeigen.)
Apr  1 19:19:35  gnome-session[1791]: (Es konnten nicht alle Prozesse 
identifiziert werden; Informationen über
Apr  1 19:19:35  gnome-session[1791]: nicht-eigene Processe werden nicht 
angezeigt; Root kann sie anzeigen.)
Apr  1 19:19:50  gnome-session[1791]: (Es konnten nicht alle Prozesse 
identifiziert werden; Informationen über
Apr  1 19:19:50  gnome-session[1791]: nicht-eigene Processe werden nicht 
angezeigt; Root kann sie anzeigen.)

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

Title:
  nmcli hangs when running from tty  and connecting to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  nmcli version 1.0.4
  Ubuntu Xenial Xerus (development branch)
  16.04 - Updated 

  Try this command from virtual consoles.

  nmcli device wifi  password 

  Expected: Some kind of error message notifying about wrong password
  It never responds until keyboard interrupt.

  
  When i run the same command from terminal, it spawns a window asking for the 
correct password.

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

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

[Touch-packages] [Bug 1536077] Re: nmcli hangs when running from tty and connecting to wifi

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

Title:
  nmcli hangs when running from tty  and connecting to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  nmcli version 1.0.4
  Ubuntu Xenial Xerus (development branch)
  16.04 - Updated 

  Try this command from virtual consoles.

  nmcli device wifi  password 

  Expected: Some kind of error message notifying about wrong password
  It never responds until keyboard interrupt.

  
  When i run the same command from terminal, it spawns a window asking for the 
correct password.

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

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

[Touch-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

2016-04-01 Thread TJ

It seems there's a deficiency in isc-dhcp client that leads to this.
Fedora have been carrying a patch since 2013 that solves it by the
simple expedient of scanning the .lease file first for unexpired leases
before allocate an address.

See:

http://pkgs.fedoraproject.org/cgit/rpms/dhcp.git/commit/dhcp-honor-
expired.patch?h=f24&id=e83fb19c51765442d77fa60596bfdb2b3b9fbe2e

There's no sign that the Fedora devs creating this patch made any
attempt to upstream it. I'm going to follow-up with the ISC DHCP devs to
find out what their view is.

In the meantime I'm working with the Network Manager devs to develop an
acceptable band-aid solution to solve the immediate problem.

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

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

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

[Touch-packages] [Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

** No longer affects: ubuntu-release-upgrader (Ubuntu)

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

Title:
  Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

Status in dbus package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  STEPS:
  1. Install 14.04.4 on a uefi securebooted system
  2. update it
  3. Install openssh-server for debug access
  4. reboot
  5. Hit alt+f2
  6. Type update-manager -d and hit enter

  EXPECTED:
  I expected a smooth transition to 16.04

  ACTUAL:
  System is completely taken out mid way through the process killing the 
session and x also no tty when hitting ctrl+alt+f1-6

  ---

  TESTS RESULTS (from cyphermox):

  On amd64 (no EFI) under qemu/libvirt, qxl graphics:
  - upgrading just libglib2.0-0 from 16.04 on top of 14.04.4: PASS
  - upgrading ubuntu-desktop (running gnome-shell) 14.04.4 to 16.04: PASS
  - upgrading ubuntu-desktop (running xubuntu-session) 14.04.4 to 16.04: PASS
  - manually upgrading compiz and other packages to 16.04 versions; after 
adding xenial sources:
    - compiz and related packages (http://paste.ubuntu.com/15415280/) : PASS
    - xserver-xorg and related: PASS
    - unity and related: PASS
    - ubuntu-desktop: PASS
    - libgl1-mesa-dri: PASS
    - apt-get dist-upgrade: FAIL (screensaver may have kicked in)
  - standard upgrading 14.04.4 to 16.04; screensaver disabled: FAIL (looked 
fine, but upgrade eventually froze, might well be a different issue)
  - re-enabling screensaver after upgrade, before reboot: TODO (above failed)

  On ppc64el:
  - upgrading ubuntu-server 14.04.4 -> 16.04: PASS

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:0.220.8
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Mar  9 17:01:27 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Beta amd64 (20160224)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

2016-04-01 Thread TJ

** Changed in: isc-dhcp (Ubuntu)
   Status: Invalid => In Progress

** Changed in: isc-dhcp (Ubuntu)
   Importance: Low => High

** Changed in: isc-dhcp (Ubuntu)
 Assignee: (unassigned) => TJ (tj)

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

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

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

[Touch-packages] [Bug 1561778] Re: Kubuntu 14.04 -> 16.04 freezes kvm

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

** This bug has been marked a duplicate of bug 1555237
   Upgrade from 14.04.4→ 16.04 dies midway taking out the session.

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

Title:
  Kubuntu 14.04 -> 16.04 freezes kvm

Status in gcr package in Ubuntu:
  New

Bug description:
  I did 2 attempts to upgrade Kubuntu 14.04 to 16.04 during the Beta2 tests in 
KVM and both runs froze the VM once the upgrader reached
  Configuring libgck-1-0 (amd64)

  I'll see if I can find any more information about this

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

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

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

** Changed in: ktp-accounts-kcm (Ubuntu Wily)
Milestone: ubuntu-15.10 => None

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

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

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

Bug description:
  Installing from Kubuntu 15.04 backports:

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

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

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

[Touch-packages] [Bug 1561778] Re: Kubuntu 14.04 -> 16.04 freezes kvm

** Tags added: dist-upgrade

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

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

Title:
  Kubuntu 14.04 -> 16.04 freezes kvm

Status in gcr package in Ubuntu:
  New

Bug description:
  I did 2 attempts to upgrade Kubuntu 14.04 to 16.04 during the Beta2 tests in 
KVM and both runs froze the VM once the upgrader reached
  Configuring libgck-1-0 (amd64)

  I'll see if I can find any more information about this

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

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

[Touch-packages] [Bug 1564876] Re: [hostname, Realtek ALC668, Mic, Internal] No autoswitch

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

** Summary changed:

- [hostname, Realtek ALC668, Mic, Internal] No autoswitch
+ [Asus N551JM, Realtek ALC668, Mic, Internal] No autoswitch

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

Title:
  [Asus N551JM, Realtek ALC668, Mic, Internal] No autoswitch

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  No auto switch with internal microphone and external microphone on
  headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   mogost 1869 F...m pulseaudio
   /dev/snd/controlC1:  mogost 1869 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr  1 18:08:52 2016
  InstallationDate: Installed on 2016-03-29 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [hostname, Realtek ALC668, Mic, Internal] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-04-01T00:51:58.276057

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

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

[Touch-packages] [Bug 1564351] Re: "Swipe from the left edge to open the launcher" - do not work on the desktop

** Branch linked: lp:~mterry/unity8/usage-mode-fixes

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

Title:
  "Swipe from the left edge to open the launcher" - do not work on the
  desktop

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1456195] Re: Zero-minimum possessive groups does not match empty string

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

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

Title:
  Zero-minimum possessive groups does not match empty string

Status in pcre3 package in Ubuntu:
  New

Bug description:
  The 14.04/15.04 pcre version doesn't match some inputs with possessive
  qualfiers:

  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  $

  Earlier versions (10.04, 12.04):
  $ echo '"a"'|pcregrep '("([^b"]*+(b.)?)*+")*+'
  "a"
  $

  this is fixed with the following upstream commit (that applies cleanly
  to the 15.04 pcre):

  http://vcs.pcre.org/pcre?view=revision&revision=1478

  https://lists.exim.org/lurker/message/20140527.131833.2fd7547c.html

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

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

[Touch-packages] [Bug 1511735] Re: libnl: fail to bind() netlink sockets

The previous upload is still in -proposed. There also needs to be a new
upload from lp_1511735_libnl3_v3.diff

** Changed in: libnl3 (Ubuntu Trusty)
   Status: Fix Released => Triaged

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

Title:
  libnl: fail to bind() netlink sockets

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:
  Triaged
Status in libnl3 package in Debian:
  Fix Released

Bug description:
  [Triage Notes]

  The proposed fix for this bug in libnl3 caused a regression in trusty-
  proposed, tracked in bug 1539634. The regression is caused by a latent
  bug in Network Manager. We expect to fix this by landing a fix for the
  bug in Network Manager in trusty-updates at the same time as this fix.

  [Impact]

   * Applications in Trusty using libnl-3-200 which frequently open and
     close netlink sockets can easily fail when attempting to bind the
     local socket.  The problem happens when libnl choose a port id
     already used by another application and subsequently libnl fails
     instead of trying another port id.

     The original bug was discovered when attempting to start a virtual
     machine under libvirt, which is a user of this library.

   * Backporting fixes from upstream release fixes a real bug in the
     current version of the library in Trusty.  The alternative is for all
     applications to manually manage their local port allocation, or as
     upstream has accepted allowing libnl to attempt to try for other
     local ports.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

  [Test Case]

   * On a Trusty 14.04 system
     1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \
     libnl-genl-3-dev libnl-route-3-200 \
     make gcc build-essential libnl1
     2. download and unpack attachment: lp_1511735_test.tar
     3. Run testcases:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 6975 (pid: 6974)
  local port has been set by the libnl to 6975 (pid: 6975)
  ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975)
  libnl FAILED
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=6978
  TEST (a)...
  Traceback (most recent call last):
    File "libnl3-test-rh1249158.py", line 226, in 
  locals()["TEST_" + arg]()
    File "libnl3-test-rh1249158.py", line 140, in TEST_a
  sk = nl_get_socket()
    File "libnl3-test-rh1249158.py", line 115, in nl_get_socket
  raise IOError(-err, _nl_geterror())
  OSError: [Errno 6] b'Unspecific failure'

     4. After applying the updated packages:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 11295 (pid: 11294)
  local port has been set by the libnl to 2894081055 (pid: 11295)
  libnl OK
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=11296
  TEST (a)...
  ...done
  TEST (b)...
  ...done
  TEST (c)...
  ...done
  TEST (d)...
  ...done

  [Regression Potential]

   * There are quite a few high profile packages that depend on this package,
     notably libvirt and network-manager.  The complete list is here:

     # on Trusty
  % apt-rdepends -r libnl-3-200 | head -n 33
  libnl-3-200
    Reverse Depends: batctl (>= 2013.4.0-2)
    Reverse Depends: bmon (>= 1:3.1-1)
    Reverse Depends: crda (>= 1.1.2-1ubuntu2)
    Reverse Depends: hostapd (>= 1:2.1-0ubuntu1)
    Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1)
    Reverse Depends: iw (>= 3.4-1)
    Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1)
    Reverse Depends: kismet (>= 2013.03.R1b-3)
    Reverse Depends: knemo (>= 0.7.6-2)
    Reverse Depends: libfsobasics3 (>= 0.12.0-4)
    Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1)
    Reverse Depends: libnl-3-200-dbg (= 3.2.21-1)
    Reverse Depends: libnl-3-dev (= 3.2.21-1)
    Reverse Depends: libnl-cli-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-genl-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-nf-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-route-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-utils (>= 3.2.21-1)
    Reverse Depends: libnss-gw-name (>= 0.3-2)
    Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13)
    Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13)
    Reverse Depends: lowpan-test-tools (>= 0.3-1)
    Reverse Depends: lowpan-tools (>= 0.3-1)
    Rever

[Touch-packages] [Bug 1562743] Re: Items are invisible in the drop-down lists of 'Service Terms/Privacy Policy' under Nokia HERE terms and conditions during wizard

Note that when pressing an item in the list and keeping the finger
pressed, the background of the list item becomes dark, and the text is
displayed in a light color.

Something’s up with the theming applied to that list view, but I don’t
know what.

** Changed in: oxide-qt (Ubuntu)
   Status: New => Invalid

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Items are invisible in the drop-down lists of 'Service Terms/Privacy
  Policy' under Nokia HERE terms and conditions during wizard

Status in Canonical System Image:
  Confirmed
Status in oxide-qt package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  $ adb shell  system-image-cli -i
  current build number: 296
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-28 09:51:15
  version version: 296
  version ubuntu: 20160326
  version device: 20160323-1467d3c
  version custom: 20160324--36-54-vivid

  Steps to reproduce:
  1. New flashed the device with image r296
  2. During wizard, open the Nokia HERE link of 'terms and conditions' in 
Location Services phase
  3. Then open the link of 'Service Terms' or 'Privacy Policy'
  4. Check the item list of 'Service Terms' and 'Country and language' or 
'Privacy Policy' and 'Country and language'

  Actual results:
  All items are invisible unless tap on them

  Additional information:
  After the wizard, the items show correctly if check them from System Settings 
--> Security & Privacy -->Location --> Nokia HERE terms and conditions

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

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

[Touch-packages] [Bug 1562743] Re: Items are invisible in the drop-down lists of 'Service Terms/Privacy Policy' under Nokia HERE terms and conditions during wizard

I flashed my test device with --wipe, and I can observe the issue
described here. The OOBE wizard uses an unmodified Ubuntu WebView
(https://bazaar.launchpad.net/~unity-
team/unity8/trunk/view/head:/qml/Wizard/Pages/here-terms.qml#L115),
which uses a ListView inside a Popover for the item selection
(https://bazaar.launchpad.net/~phablet-team/webbrowser-
app/trunk/view/head:/src/Ubuntu/Web/ItemSelector02.qml). Delegates
inside that listview have no special theming applied, they use a stock
ListItemLayout.

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

Title:
  Items are invisible in the drop-down lists of 'Service Terms/Privacy
  Policy' under Nokia HERE terms and conditions during wizard

Status in Canonical System Image:
  Confirmed
Status in oxide-qt package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  $ adb shell  system-image-cli -i
  current build number: 296
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-03-28 09:51:15
  version version: 296
  version ubuntu: 20160326
  version device: 20160323-1467d3c
  version custom: 20160324--36-54-vivid

  Steps to reproduce:
  1. New flashed the device with image r296
  2. During wizard, open the Nokia HERE link of 'terms and conditions' in 
Location Services phase
  3. Then open the link of 'Service Terms' or 'Privacy Policy'
  4. Check the item list of 'Service Terms' and 'Country and language' or 
'Privacy Policy' and 'Country and language'

  Actual results:
  All items are invisible unless tap on them

  Additional information:
  After the wizard, the items show correctly if check them from System Settings 
--> Security & Privacy -->Location --> Nokia HERE terms and conditions

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

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

[Touch-packages] [Bug 1564351] Re: "Swipe from the left edge to open the launcher" - do not work on the desktop

2016-04-01 Thread Michael Terry

Hrm.  So to reproduce, install unity8 on the desktop and then:

1) sudo gdbus call --system --dest org.freedesktop.Accounts --object-path 
/org/freedesktop/Accounts/User1000 --method org.freedesktop.DBus.Properties.Set 
com.canonical.unity.AccountsService demo-edges ''
2) gsettings set com.canonical.Unity8 usage-mode Staged

(Replace 1000 in step #1 with your UID.)

The problem is that the tutorial is thus fooled about what mode we're
running in (it thinks tablet/phone).

The left-edge tutorial bits assume a touch screen.  And they don't run
in desktop mode (when there is at least one pointer).  So everything
*should* work, except that usage-mode was overridden.

I think since we no longer treat the gsettings value as a user-setting
(unity8 will override it at will), we should re-evaluate it on startup.
That should avoid this particular scenario.

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

Title:
  "Swipe from the left edge to open the launcher" - do not work on the
  desktop

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Can not unlock my desktop, swipe is not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160330-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 31 19:29:50 2016
  InstallationDate: Installed on 2016-03-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1564965] [NEW] s390x tests should be re-enabled

2016-04-01 Thread Dimitri John Ledkov

Public bug reported:

glib2.0 (2.48.0-1ubuntu3) xenial; urgency=medium

  * Revert the last change, don't run the tests on s390x for a first
build.

 -- Matthias Klose   Thu, 31 Mar 2016 20:56:40 +0200

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
 Status: New


** Tags: s390x

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

Title:
  s390x tests should be re-enabled

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  glib2.0 (2.48.0-1ubuntu3) xenial; urgency=medium

* Revert the last change, don't run the tests on s390x for a first
  build.

   -- Matthias Klose   Thu, 31 Mar 2016 20:56:40 +0200

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

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

[Touch-packages] [Bug 1511735] Re: libnl: fail to bind() netlink sockets

2016-04-01 Thread Pavlic

** Changed in: libnl3 (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 libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1511735

Title:
  libnl: fail to bind() netlink sockets

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:
  Fix Released
Status in libnl3 package in Debian:
  Fix Released

Bug description:
  [Triage Notes]

  The proposed fix for this bug in libnl3 caused a regression in trusty-
  proposed, tracked in bug 1539634. The regression is caused by a latent
  bug in Network Manager. We expect to fix this by landing a fix for the
  bug in Network Manager in trusty-updates at the same time as this fix.

  [Impact]

   * Applications in Trusty using libnl-3-200 which frequently open and
     close netlink sockets can easily fail when attempting to bind the
     local socket.  The problem happens when libnl choose a port id
     already used by another application and subsequently libnl fails
     instead of trying another port id.

     The original bug was discovered when attempting to start a virtual
     machine under libvirt, which is a user of this library.

   * Backporting fixes from upstream release fixes a real bug in the
     current version of the library in Trusty.  The alternative is for all
     applications to manually manage their local port allocation, or as
     upstream has accepted allowing libnl to attempt to try for other
     local ports.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

  [Test Case]

   * On a Trusty 14.04 system
     1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \
     libnl-genl-3-dev libnl-route-3-200 \
     make gcc build-essential libnl1
     2. download and unpack attachment: lp_1511735_test.tar
     3. Run testcases:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 6975 (pid: 6974)
  local port has been set by the libnl to 6975 (pid: 6975)
  ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975)
  libnl FAILED
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=6978
  TEST (a)...
  Traceback (most recent call last):
    File "libnl3-test-rh1249158.py", line 226, in 
  locals()["TEST_" + arg]()
    File "libnl3-test-rh1249158.py", line 140, in TEST_a
  sk = nl_get_socket()
    File "libnl3-test-rh1249158.py", line 115, in nl_get_socket
  raise IOError(-err, _nl_geterror())
  OSError: [Errno 6] b'Unspecific failure'

     4. After applying the updated packages:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 11295 (pid: 11294)
  local port has been set by the libnl to 2894081055 (pid: 11295)
  libnl OK
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=11296
  TEST (a)...
  ...done
  TEST (b)...
  ...done
  TEST (c)...
  ...done
  TEST (d)...
  ...done

  [Regression Potential]

   * There are quite a few high profile packages that depend on this package,
     notably libvirt and network-manager.  The complete list is here:

     # on Trusty
  % apt-rdepends -r libnl-3-200 | head -n 33
  libnl-3-200
    Reverse Depends: batctl (>= 2013.4.0-2)
    Reverse Depends: bmon (>= 1:3.1-1)
    Reverse Depends: crda (>= 1.1.2-1ubuntu2)
    Reverse Depends: hostapd (>= 1:2.1-0ubuntu1)
    Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1)
    Reverse Depends: iw (>= 3.4-1)
    Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1)
    Reverse Depends: kismet (>= 2013.03.R1b-3)
    Reverse Depends: knemo (>= 0.7.6-2)
    Reverse Depends: libfsobasics3 (>= 0.12.0-4)
    Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1)
    Reverse Depends: libnl-3-200-dbg (= 3.2.21-1)
    Reverse Depends: libnl-3-dev (= 3.2.21-1)
    Reverse Depends: libnl-cli-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-genl-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-nf-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-route-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-utils (>= 3.2.21-1)
    Reverse Depends: libnss-gw-name (>= 0.3-2)
    Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13)
    Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13)
    Reverse Depends: lowpan-test-tools (>= 0.3-1)
    Reverse Depends: lowpan-tools (>= 0.3-1)
    Reverse Depends: neard (>= 0.11-1)
    Reverse Depends: neard-tools (>= 0.11-1)
    Reverse Depen

[Touch-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta

2016-04-01 Thread Bryan Quigley

@Mathieu
Tried the PPA.  The Canonical VPN doesn't work for me.  It says it connects, 
but then I can't access anything on the net or VPN.  Reverting it, and its 
working again.  A few times the nm-applet has also crashed when I do this.  -  
Should I open a new bug for these issues?

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

Title:
  [FFE] NetworkManager 1.2-beta

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed
Status in network-manager-iodine package in Ubuntu:
  Confirmed
Status in network-manager-openconnect package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-vpnc package in Ubuntu:
  Confirmed

Bug description:
  We really should update NetworkManager to 1.2 (or some other updated
  stable release) for the LTS, this will allow us to better deal with
  any bugs that might come up post-release.

  This new release will also much improve interop with LXC, which has
  recently been an issue.

  Other FFEs will be opened for NM VPN plugins and for NetworkManager-
  applet.

  
  
  
  NetworkManager-1.2
  Overview of changes since NetworkManager-1.0
  

  This is a new stable release of NetworkManager.  Notable changes
  include:

  * Added an option to enable use of random MAC addresses for Wi-Fi access
  point scanning (defaults to disabled).  Controlled with
  'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key 
in
  ifcfg files).
  * Wi-Fi scanning now utilizes wpa_supplicant's AP list.
  * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
  files.
  * Added support for creation of more types of software devices: tun & tap,
  macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
  * The software devices (bond, bridge, vlan, team, ...) can now be stacked
  arbitrarily.  The nmcli interface for creating master-slave relationships
  has been significantly improved by the use of 'master' argument to
  all link types.
  * RFC7217 stable privacy addressing is now used by default to protect from
  address-based host tracking. The IPv6 addressing mode is configured with
  IPV6_ADDR_GEN_MODE key in ifcfg files.
  * Improved route management code to avoid clashes between conflicting
  routes in multiple connections.
  * Refactored platform code resulting in more robust interface to platform,
  less overhead and reduced memory footprint.
  * Improved interoperability with other network management tools.  The
  externally created software devices are not managed until they're
  activated.
  * The Device instances now exist for all software connections and the platform
  devices are now only created when the device is activated.  This makes it
  possible for connections with device of same name not to clash unless
  they're activated concurrently.  The links are now not unnecessarily 
present
  unless the connection is active, avoiding pollution of the link namespace.
  * NetworkManager now correctly manages connectivity in namespace-based
  containers such as LXC and Docker.
  * Support for configuring ethernet Wake-On-Lan has been added.
  * Added LLDP listener functionality and related CLI client commands. Enabled 
via
  LLDP option in ifcfg files.
  * CLI secret agent has been extended with support for VPN secrets.
  * The command line client now utilizes colors for its output.
  * The command line client now sorts the devices and properties for better
  clarity.
  * Numerous improvements to Bash command completion for nmcli.
  * NetworkManager relies on less external libraries.  The use of dbus-glib
  has been replaced with gio's native D-Bus support and libnl-route is no
  longer used.
  * Dependency on avahi-autoipd has been dropped.  Native IPv4 link-local
  addressing configuration based on systemd network library is now used
  instead.
  * Hostname is now managed via systemd-hostnamed on systemd-based systems.
  * Management of resolv.conf management can be changed at runtime, private
  resolv.conf is always written in /run.
  * NetworkManager can now write DNS options to resolv.conf.
  * Updated version of systemd network library used for internal DHCP and
  IPv4 link-local support.
  * Support for event logging via audit subsystem has been added.
  * Support for native logging via systemd-journald has been added taking
  advantage of its structured logging.
  * Live reconfiguration of IP configuration after changing the settings without
  reactivation of the device with "nmcli device reapply" comman

[Touch-packages] [Bug 1564951] Re: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

2016-04-01 Thread Simon Déziel

strace'ing it showed this:

  clock_adjtime(CLOCK_REALTIME, 0x7ffcc1567020) = -1 EINVAL (Invalid argument)
  writev(2, [{"Failed to call clock_adjtime(): "..., 48}, {"\n", 1}], 2) = 49



** Attachment added: "Full strace"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564951/+attachment/4619508/+files/strace

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

Title:
  systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading systemd from 229-3ubuntu1 to 229-3ubuntu2, I noticed
  this on one of my VM:

systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

  systemd-timesyncd says it was able to sync the clock but also report
  failures:

  # systemctl status systemd-timesyncd
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: active (running) since Fri 2016-04-01 10:55:09 EDT; 3s ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 2523 (systemd-timesyn)
 Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 512)
 CGroup: /system.slice/systemd-timesyncd.service
 └─2523 /lib/systemd/systemd-timesyncd

  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Starting Network Time 
Synchronization...
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Started Network Time 
Synchronization.
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Failed to 
call clock_adjtime(): Invalid argument
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Synchronized 
to time server 172.24.21.1:123 (ntp.ubuntu.com).

  The clock_adjtime error repeats every ~30 seconds after that.

  Oddly, I cannot reproduce this on my physical machine, only on this
  VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Fri Apr  1 10:50:35 2016
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=ce88e7e4-836f-42d6-8e39-4bc8abd23541 ro 
console=hvc0 kaslr
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.0:cvnBochs:ct1:cvr:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-2.0
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1564951] [NEW] systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

2016-04-01 Thread Simon Déziel

Public bug reported:

After upgrading systemd from 229-3ubuntu1 to 229-3ubuntu2, I noticed
this on one of my VM:

  systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

systemd-timesyncd says it was able to sync the clock but also report
failures:

# systemctl status systemd-timesyncd
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
   └─disable-with-time-daemon.conf
   Active: active (running) since Fri 2016-04-01 10:55:09 EDT; 3s ago
 Docs: man:systemd-timesyncd.service(8)
 Main PID: 2523 (systemd-timesyn)
   Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 512)
   CGroup: /system.slice/systemd-timesyncd.service
   └─2523 /lib/systemd/systemd-timesyncd

Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Starting Network Time 
Synchronization...
Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Started Network Time 
Synchronization.
Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Failed to call 
clock_adjtime(): Invalid argument
Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Synchronized to 
time server 172.24.21.1:123 (ntp.ubuntu.com).

The clock_adjtime error repeats every ~30 seconds after that.

Oddly, I cannot reproduce this on my physical machine, only on this VM.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
Uname: Linux 4.4.0-17-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Fri Apr  1 10:50:35 2016
Lspci: Error: [Errno 2] No such file or directory: 'lspci'
Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: root=UUID=ce88e7e4-836f-42d6-8e39-4bc8abd23541 ro 
console=hvc0 kaslr
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: 
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.0:cvnBochs:ct1:cvr:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-2.0
dmi.sys.vendor: QEMU

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


** Tags: amd64 apport-bug xenial

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

Title:
  systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading systemd from 229-3ubuntu1 to 229-3ubuntu2, I noticed
  this on one of my VM:

systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

  systemd-timesyncd says it was able to sync the clock but also report
  failures:

  # systemctl status systemd-timesyncd
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: active (running) since Fri 2016-04-01 10:55:09 EDT; 3s ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 2523 (systemd-timesyn)
 Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 512)
 CGroup: /system.slice/systemd-timesyncd.service
 └─2523 /lib/systemd/systemd-timesyncd

  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Starting Network Time 
Synchronization...
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Started Network Time 
Synchronization.
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Failed to 
call clock_adjtime(): Invalid argument
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Synchronized 
to time server 172.24.21.1:123 (ntp.ubuntu.com).

  The clock_adjtime error repeats every ~30 seconds after that.

  Oddly, I cannot reproduce this on my physical machine, only on this
  VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Fri Apr  1 10:50:35 2016
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=ce88e7e4-836f-4

[Touch-packages] [Bug 1564585] Re: make an virtual package for updating to latest video drivers available

2016-04-01 Thread Jaime Pérez

** Package changed: mesa (Ubuntu) => apt (Ubuntu)

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

Title:
  make an virtual package for updating to latest video drivers available

Status in apt package in Ubuntu:
  New

Bug description:
  I would like to be able to install, for example, wily video
  drivers/kernel/mesa easily. For example, I install a package called
  "mesa-lts-wily" or better "wily-video-drivers" and it selects all
  needed packages to make the transition, instead having to select them
  individually.  Another one such as "vivid-enablement-package" that
  installs vivid kernel, vivid mesa, vivid xorg, etc.

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

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

[Touch-packages] [Bug 989819] Re: Make duplicate signature more specific for DBusException and OSError

2016-04-01 Thread Martin Pitt

Trusty backport of http://bazaar.launchpad.net/~apport-
hackers/apport/trunk/revision/3066 uploaded to the SRU review queue.

** Description changed:

  Looking through some db bug examples and saw some incorrect bug
  associations, one example
  
  "Traceback (most recent call last):
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
- res = f(*args, **kwargs)
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
- res = f(*args, **kwargs)
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1090, in on_combobox_locale_chooser_changed
- self.writeUserFormats()
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
- self.writeUserFormatsSetting(userFormats=code)
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
- iface.SetFormatsLocale(macr['SYSLOCALE'])
-   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
- return self._proxy_method(*args, **keywords)
-   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
- **keywords)
-   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
- message, timeout)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
+ res = f(*args, **kwargs)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
+ res = f(*args, **kwargs)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1090, in on_combobox_locale_chooser_changed
+ self.writeUserFormats()
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
+ self.writeUserFormatsSetting(userFormats=code)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
+ iface.SetFormatsLocale(macr['SYSLOCALE'])
+   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
+ return self._proxy_method(*args, **keywords)
+   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
+ **keywords)
+   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
+ message, timeout)
  DBusException: org.freedesktop.Accounts.Error.PermissionDenied: Not 
authorized"
  
  has been associated to
  https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/930785
  
  "Traceback (most recent call last):
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
- res = f(*args, **kwargs)
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
- res = f(*args, **kwargs)
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1081, in on_combobox_locale_chooser_changed
- self.writeUserFormats()
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
- self.writeUserFormatsSetting(userFormats=code)
-   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
- iface.SetFormatsLocale(macr['SYSLOCALE'])
-   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
- return self._proxy_method(*args, **keywords)
-   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
- **keywords)
-   File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in 
call_blocking
- message, timeout)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 62, in wrapper
+ res = f(*args, **kwargs)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 74, in wrapper
+ res = f(*args, **kwargs)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 1081, in on_combobox_locale_chooser_changed
+ self.writeUserFormats()
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 775, in writeUserFormats
+ self.writeUserFormatsSetting(userFormats=code)
+   File 
"/usr/lib/python2.7/dist-packages/LanguageSelector/LanguageSelector.py", line 
71, in writeUserFormatsSetting
+ iface.SetFormatsLocale(macr['SYSLOCALE'])
+   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in 
__call__
+ return self._proxy_method(*args, **keywords)
+   File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in 
__call__
+ **keywords)
+   File "/us

[Touch-packages] [Bug 1535666] Re: Downloading files fails on non-English systems

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

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

Title:
  Downloading files fails on non-English systems

Status in Canonical System Image:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  On my desktop setup (French locale), the XDG download folder is named
  "Téléchargements". The apparmor policy for webbrowser-app specifically
  requests read/write access to $HOME/Downloads/, which works only on
  systems where the downloads folder is named "Downloads".

  When downloading a file in the browser, I’m seeing the following error
  in the console:

  Failed moving file from "/home/osomon/.local/share/ubuntu-download-
  manager/webbrowser-app/Downloads/example.pdf" to
  "/home/osomon/Téléchargements/example.pdf"

  I wonder if apparmor exposes a way to specify XDG folders in policies.

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

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

[Touch-packages] [Bug 1500742] Re: Downloading a file requires its mime-type to be known in advance