[Touch-packages] [Bug 1490347] Re: [Regresision] 15:10 - Cannot pair with devices using PIN codes

[Dainius]

This happens on current version of Xenial as well.

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

Title:
  [Regresision] 15:10 - Cannot pair with devices using PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Raymond]

5.039| 0.000) D: [pulseaudio] alsa-util.c: Managed to open hw:5 ( 5.039|
0.000) I: [pulseaudio] alsa-util.c: Disabling tsched mode since BATCH
flag is set ( 5.039| 0.000) D: [pulseaudio] alsa-util.c: Maximum hw
buffer size is 11888 ms ( 5.041| 0.001) D: [pulseaudio] alsa-util.c: Set
buffer size first (to 4408 samples), period size second (to 1102
samples). ( 5.042| 0.000) D: [pulseaudio] alsa-mixer.c: Profile output
:analog-stereo+input:analog-mono supported. ( 5.042| 0.000) D:
[pulseaudio] alsa-mixer.c: Skipping profile output:analog-stereo+input
:analog-stereo - will not be able to open input:analog-stereo ( 5.042|
0.000) D: [pulseaudio] alsa-mixer.c: Skipping profile output:analog-
stereo+input:iec958-stereo - will not be able to open
input:iec958-stereo ( 5.059| 0.016) D: [pulseaudio] alsa-mixer.c:
Looking at profile output:analog-surround-21 ( 5.059| 0.000) D:
[pulseaudio] alsa-mixer.c: Checking for playback on Analog Surround 2.1
(analog-surround-21) ( 5.059| 0.000) D: [pulseaudio] alsa-util.c: Trying
surround21:5 with SND_PCM_NO_AUTO_FORMAT ... ( 5.060| 0.000) I:
[pulseaudio] (alsa-lib)pcm_hw.c: Invalid PCM state for chmap_get: OPEN


Different error on your different usb audio device, seem no channel map

-- 
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:  

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

[Raymond]

If your card 2 only support stereo, it is strange that surround21 can be
opened

155| 0.000) D: [pulseaudio] alsa-mixer.c: Checking for playback on
Analog Surround 2.1 (analog-surround-21) ( 5.155| 0.000) D: [pulseaudio]
alsa-util.c: Trying surround21:2 with SND_PCM_NO_AUTO_FORMAT ... (
5.156| 0.000) I: [pulseaudio] (alsa-lib)pcm_hw.c: Invalid PCM state for
chmap_get: OPEN ( 5.156| 0.000) D: [pulseaudio] alsa-util.c: Managed to
open surround21:2 ( 5.156| 0.000) I: [pulseaudio] alsa-util.c: Disabling
tsched mode since BATCH flag is set ( 5.156| 0.000) D: [pulseaudio]
alsa-util.c: Maximum hw buffer size is 1981 ms ( 5.158| 0.001) I:
[pulseaudio] (alsa-lib)pcm_hw.c: SNDRV_PCM_IOCTL_PREPARE failed (-32

-- 
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: 

[Touch-packages] [Bug 1373070] Re: full fix for disconnected path (paths)

[Rafael David Tinoco]

Okay, so, I had more time to dig a bit into this and, after some
analysis, I got:

Errors being reproduced:

[1668392.078137] audit: type=1400 audit(1459311786.129:1375455):
apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
disconnected path" error=-13 profile="/usr/sbin/dnsmasq" name="dev/log"
pid=15735 comm="dnsmasq" requested_mask="w" denied_mask="w" fsuid=0
ouid=0

And apparmor dnsmasq profile:

#/usr/sbin/dnsmasq flags=(attach_disconnected) {
#/usr/sbin/dnsmasq flags=(complain) {
/usr/sbin/dnsmasq {

Without any flags.

And the command causing the apparmor errors:

root 16877  0.0  0.2  66416  3648 ?S13:23   0:00 sudo
/usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ip netns exec
qdhcp-37d013b6-f6fa-4652-8073-5e7d2c418a9d env
NEUTRON_NETWORK_ID=37d013b6-f6fa-4652-8073-5e7d2c418a9d dnsmasq --no-
hosts --no-resolv --strict-order --bind-interfaces --interface=ns-
aa95fe20-ff --except-interface=lo --pid-
file=/var/lib/neutron/dhcp/37d013b6-f6fa-4652-8073-5e7d2c418a9d/pid
--dhcp-
hostsfile=/var/lib/neutron/dhcp/37d013b6-f6fa-4652-8073-5e7d2c418a9d/host
--addn-
hosts=/var/lib/neutron/dhcp/37d013b6-f6fa-4652-8073-5e7d2c418a9d/addn_hosts
--dhcp-
optsfile=/var/lib/neutron/dhcp/37d013b6-f6fa-4652-8073-5e7d2c418a9d/opts
--dhcp-
leasefile=/var/lib/neutron/dhcp/37d013b6-f6fa-4652-8073-5e7d2c418a9d/leases
--dhcp-range=set:tag0,192.168.21.0,static,86400s --dhcp-lease-max=256
--conf-file=/etc/neutron/dnsmasq.conf --domain=openstacklocal

It is a "sudo-like" approach from openstack (rootwrap) to execute
dnsmasq in a new network namespace with different privileges.

Ubuntu kernel 3.13.X has apparmor 3 alpha 6 code: 
https://pastebin.canonical.com/152812/
Ubuntu kernel 3.16 and 3.19 has apparmor 3 rc 1 code: 
https://pastebin.canonical.com/152813/

>From apparmor I could see that the error comes from "aa_path_name"
called by either:

- path_name *
- aa_remount
- aa_bind_mount
- aa_mount_change_type
- aa_move_mount
- aa_new_mount
- aa_unmount
- aa_pivotroot

So, since the job is being restarted by neutron (or at least it is
trying to re-start it, causing the apparmor to block the access), I
created a systemtap script to monitor path_name and check for dnsmasq
trying to open "log" (allegedly /dev/log) file.

probe kernel.function("path_name").call {
funcname = execname();
if (funcname == "dnsmasq") {
filename = reverse_path_walk($path->dentry);
if (filename == "log") {
printf("(%s) %s\n", execname(), filename);
print_backtrace();
}
}
}

And got the backtrace from the denials:

(dnsmasq) log

 0x8132deb0 : path_name+0x0/0x140 [kernel]
 0x8132e413 : aa_path_perm+0xa3/0x130 [kernel]
 0x81337e26 : aa_unix_peer_perm+0x536/0x990 [kernel]
 0x8132c653 : apparmor_unix_may_send+0x73/0x150 [kernel]
 0x812eb8a6 : security_unix_may_send+0x16/0x20 [kernel]
 0x817019db : unix_dgram_connect+0x23b/0x250 [kernel]
 0x8164a987 : SYSC_connect+0xe7/0x120 [kernel]
 0x8164b68e : sys_connect+0xe/0x10 [kernel]
 0x817700cd : system_call_fastpath+0x1a/0x1f [kernel]

 When trying to check if "log" could be converted to "fullpath" by using
systemtap function:

return task_dentry_path(task_current(),
@cast(path,"path","kernel:nfs:kernel")->dentry,
@cast(path,"path","kernel:nfs:kernel")->mnt)

I saw that I could resolve path for all other files but "/dev/log":

(dnsmasq) /usr/lib/x86_64-linux-gnu/libnfnetlink.so.0.2.0
(dnsmasq) /usr/lib/x86_64-linux-gnu/libmnl.so.0.1.0
(dnsmasq) /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache
(dnsmasq) /etc/neutron/dnsmasq.conf
(dnsmasq) /etc/neutron/dnsmasq.conf
(dnsmasq) /etc/localtime
(dnsmasq) /etc/localtime
(dnsmasq) /etc/localtime
(dnsmasq) 

Because

function task_dentry_path:string(task:long,dentry:long,vfsmnt:long)

Couldn't handle the udev (vfsmnt) path. With that, I thought apparmor
couldn't be handling udev path for different root vfsmnt (like a
different FS namespace).

Checking iproute2 ipnetns.c I saw that executing a command in a new
network namespace causes:

unshare(CLONE_NEWNS) AND
mount("", "/", "none", MS_SLAVE | MS_REC, NULL)

This second being possibly the "problem" - its intent is not to allow
mounts to propagate back to parent task - since it basically removes a
root vfsmnt from the execution taken in place, breaking apparmor (or
even dentry cache) path resolution logic. Here, the needed flag
"attach_disconnected" (present in apparmor path resolution logic) comes
in place, to allow "/" to be added in path names missing leading / due
to missing root vfsmnt from dentry cache.

To observe: 3.13 (apparmor 3 alpha 6) doesn't complain on disconnected
paths but 3.16 and beyond (rc1) does (needing the flag
"attach_disconnected").

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which 

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

[Raymond]

| 0.000) W: [pulseaudio] alsa-mixer.c: Volume element Speaker has 8
channels. That's too much! I can't handle that! ( 5.131| 0.000) D:
[pulseaudio] alsa-mixer.c: Probe of element 'Speaker' failed.

Pulseaudio not support volume control with more than two channels

Card hw:4 'Device'/'USB Sound Device at usb-:00:12.2-3.3.3, full
speed' Mixer name : 'USB Mixer' Components : 'USB0d8c:0102' Controls :
16 Simple ctrls : 6 Simple mixer control 'Speaker',0 Capabilities:
pvolume pswitch pswitch-joined Playback channels: Front Left - Front
Right - Rear Left - Rear Right - Front Center - Woofer - Side Left -
Side Right Limits: Playback 0 - 197 Mono: Front Left: Playback 197
[100%] [0.00dB] [on] Front Right: Playback 197 [100%] [0.00dB] [on] Rear
Left: Playback 197 [100%] [0.00dB] [on] Rear Right: Playback 197 [100%]
[0.00dB] [on] Front Center: Playback 197 [100%] [0.00dB] [on] Woofer:
Playback 197 [100%] [0.00dB] [on] Side Left: Playback 197 [100%]
[0.00dB] [on] Side Right: Playback 197 [100%] [0.00dB] [on]

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

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

[Raymond]

Check your system log,  seem kernel oops

- [26825.955291] WARNING: CPU: 0 PID: 16771 at 
/build/linux-_Kv5oI/linux-4.2.0/fs/block_dev.c:57 __blkdev_put+0xbd/0x280() 
[26825.955293] Modules linked in: nls_iso8859_1 uas usb_storage binfmt_misc 
ax88179_178a usbnet uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
v4l2_common snd_hda_codec_via snd_hda_codec_hdmi snd_hda_codec_generic 
snd_usb_audio snd_hda_intel snd_hda_codec videodev joydev media snd_usbmidi_lib 
snd_hda_core snd_hwdep snd_pcm input_leds snd_seq_midi snd_seq_midi_event 
kvm_amd snd_rawmidi kvm nvidia(POE) edac_core snd_seq snd_seq_device snd_timer 
edac_mce_amd snd drm serio_raw k10temp asus_atk0110 soundcore 8250_fintek 
shpchp i2c_piix4 wmi mac_hid parport_pc ppdev lp parport autofs4 hid_generic 
usbhid hid pata_acpi psmouse pata_atiixp ahci r8169 libahci mii 
[26825.955347] CPU: 0 PID: 16771 Comm: pool Tainted: P OE 4.2.0-34-lowlatency 
#39-Ubuntu

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

[Touch-packages] [Bug 1550582] Re: Cant delete messages

[Arnaud Ober]

The issue is when you have so many messages to delete in the same time.
I already saw this bug. The partial solution is to select some messages
and delete the, reselect some messages and delete them. Until the full
conversation is removed...

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

Title:
  Cant delete messages

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

Bug description:
  I swipe to the right to reveal the red delete icon. I tap, and the app
  freezes for around 30 seconds. Then the message is still there. E4.5,
  OTA9.1.

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

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

[Touch-packages] [Bug 1563658] [NEW] two typos in /etc/init.d/skeleton

[Jonathanius]

Public bug reported:

In /etc/init.d/skeleton:
line 14: "start" should read "starts"
line 16: "behavoirs, implemend" should read "behaviors, implement"

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: initscripts 2.88dsf-59.2ubuntu2.1
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Mar 29 23:36:22 2016
InstallationDate: Installed on 2016-03-23 (6 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
SourcePackage: sysvinit
UpgradeStatus: Upgraded to wily on 2016-03-27 (2 days ago)
modified.conffile..etc.default.rcS: [modified]
mtime.conffile..etc.default.rcS: 2016-03-23T00:36:45.603711

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


** Tags: amd64 apport-bug wily

** Patch added: "patch fixing reported typos"
   https://bugs.launchpad.net/bugs/1563658/+attachment/4616630/+files/patch.txt

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

Title:
  two typos in /etc/init.d/skeleton

Status in sysvinit package in Ubuntu:
  New

Bug description:
  In /etc/init.d/skeleton:
  line 14: "start" should read "starts"
  line 16: "behavoirs, implemend" should read "behaviors, implement"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: initscripts 2.88dsf-59.2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar 29 23:36:22 2016
  InstallationDate: Installed on 2016-03-23 (6 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to wily on 2016-03-27 (2 days ago)
  modified.conffile..etc.default.rcS: [modified]
  mtime.conffile..etc.default.rcS: 2016-03-23T00:36:45.603711

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

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

[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot

[Cemil Azizoglu]

As the last step to isolate the issue, I've created a trivial GL-based
TPP and was NOT able to repro after trying many times. I assume at this
point that the Qt QuickSceneGraph Renderer the actual TPP uses is doing
something funny.

I am off the next couple of days and if anyone wants to try the TPP is
in silo 80 (https://requests.ci-train.ubuntu.com/#/ticket/1187). Please
use the packages with the '15.04.20160330-0ubuntu1' tag as 'citrain
device upgrade' picks up the older versions, probably because not all
'arch'es built successfully the last time.

At this time, I'll remove myself and Mir from the bug, as I am not
familiar with the QSG.

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

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Telegram app:
  Invalid
Status in trust-store:
  New
Status in mir package in Ubuntu:
  Invalid

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  --

  Same happens with the following steps:

  1. Flash device (arale) with

  $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
  proposed/meizu.en --recovery-image 
  --bootstrap

  2. Wait until flash process is done
  3. Go through first-start wizard
  4. Pass tutorial
  5. Directly launch camera-app, approve trust-prompt

  Repeat 1-5 multiple times and you will see a frozen device after step
  5. You can verify it happened due to a kernel panic mentioned in
  comment #7.

  You can reset the trust db entry for the camera app using :
  $rm -rf ~/.local/share/CameraService
  $restart cameraservice-trust-stored

  Run the following to get the command line for all threads so you can match 
the pid from the kmsg later (see below):
  ps H -eo 'pid tid cmd:250 comm'

  To verify it was really the kernel panic run

  $ sudo cat /proc/last_kmsg

  once the device has rebooted.

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

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

[Touch-packages] [Bug 1560797] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured

[peter swain]

Seems to be resolved by today's update to systemd-sysv 229-3ubuntu1

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

Title:
  package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade:
  libgcrypt20 was unconfigured

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Happened during upgrade to 16.04, don't know any more details.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 225-1ubuntu9.1
  Uname: Linux 4.4.5-040405-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 22 22:56:03 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  InstallationDate: Installed on 2013-04-24 (1064 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.7
  SourcePackage: systemd
  Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago)

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

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

[Touch-packages] [Bug 1551811] Re: Opening the camera for the first time leads to reboot

[Cemil Azizoglu]

** Changed in: mir (Ubuntu)
 Assignee: Cemil Azizoglu (cemil-azizoglu) => (unassigned)

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

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

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

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

Title:
  Opening the camera for the first time leads to reboot

Status in camera-app:
  New
Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in Telegram app:
  Invalid
Status in trust-store:
  New
Status in mir package in Ubuntu:
  Invalid

Bug description:
  Test case.
  - Flash the phone.
  - Open Telegram app.
  - Fill the account details.
  - Add a contact (if needed).
  - Select a contact to send a message.
  - Tap on the clip to attach a photo.
  - Select the camera.

  Expected result.
  - After accepting the permission dialog, camera app allows to take a picture.

  Actual result.
  - After accepting the permission dialog, phone reboots.

  I'm not sure whether this is a problem with Telegram or with the
  camera. However, I couldn't reproduce the problem using the messaging-
  app. And once the permission dialog is accepted, the reboot is gone.

  com.ubuntu.telegram_2.0.8.0_armhf.click
  current build number: 259
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  --

  Same happens with the following steps:

  1. Flash device (arale) with

  $ ubuntu-device-flash touch --device arale --channel ubuntu/rc-
  proposed/meizu.en --recovery-image 
  --bootstrap

  2. Wait until flash process is done
  3. Go through first-start wizard
  4. Pass tutorial
  5. Directly launch camera-app, approve trust-prompt

  Repeat 1-5 multiple times and you will see a frozen device after step
  5. You can verify it happened due to a kernel panic mentioned in
  comment #7.

  You can reset the trust db entry for the camera app using :
  $rm -rf ~/.local/share/CameraService
  $restart cameraservice-trust-stored

  Run the following to get the command line for all threads so you can match 
the pid from the kmsg later (see below):
  ps H -eo 'pid tid cmd:250 comm'

  To verify it was really the kernel panic run

  $ sudo cat /proc/last_kmsg

  once the device has rebooted.

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

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

[Touch-packages] [Bug 66308] Re: Network mounts don't get unmounted on ifdown

[Launchpad Bug Tracker]

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

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

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

Title:
  Network mounts don't get unmounted on ifdown

Status in sysvinit package in Ubuntu:
  Expired

Bug description:
  Binary package hint: initscripts

  This is for Ubuntu 6.06.1.

  When a network interface comes up, network mounts from fstab get
  mounted via /etc/network/if-up.d/mountnfs. But if the (single present)
  network interface gets shut down via ifdown, the network mounts don't
  get unmounted beforehand, resulting for example in timeouts when
  listing the directory where the network mount is (or should be)
  mounted.

  Now there's the problem if more than one network interface is present,
  so that network mounts can't simply be automatically unmounted on
  every ifdown via a script in /etc/network/if-down.d/.

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

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

[Touch-packages] [Bug 1538555] Re: Intel Graphics don´t work

[Launchpad Bug Tracker]

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

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

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

Title:
  Intel Graphics don´t work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The system unknow my lcd screen in my Pavlion dc6235us with VGA
  compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML
  Express Integrated Graphics Controller (rev 03).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 27 08:24:38 2016
  DistUpgraded: Fresh install
  DistroCodename: n/a
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:30bb]
 Subsystem: Hewlett-Packard Company Device [103c:30bb]
  InstallationDate: Installed on 2016-01-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release i386 
(20151021)
  MachineType: Hewlett-Packard HP Pavilion dv6000 (RP298UA#ABA)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic 
root=UUID=a7acbc25-5a5d-44cc-af92-8b6ce4b47cd0 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.16
  dmi.board.name: 30BB
  dmi.board.vendor: Quanta
  dmi.board.version: 66.37
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.16:bd02/02/2007:svnHewlett-Packard:pnHPPaviliondv6000(RP298UA#ABA):pvrRev1:rvnQuanta:rn30BB:rvr66.37:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6000 (RP298UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Jan 27 08:02:39 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1537163] Re: Xorg crash

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Expired

Bug description:
  freeze and Cranach x-server , work only teamwiever and  firefox

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-59.79~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-59-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Fri Jan 22 21:05:58 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e244]
  InstallationDate: Installed on 2015-05-19 (248 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-59-generic 
root=UUID=78b0b1ac-9887-40b9-851c-0aad32632288 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88X-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan 22 21:02:27 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1538823] Re: Menu bar menu options are small and do not reflect system font changes

[Launchpad Bug Tracker]

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

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

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

Title:
  Menu bar menu options are small and do not reflect system font changes

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Just upgraded to Ubuntu 15.10

  The individual menu bar menu options are very small.  I am not talking
  about the menu bar title or the menu names e.g. "File" "Edit" etc.,
  I'm talking about the individual options within each menu.  I expect
  the text of the menu items to be the same as other UI text, e.g. the
  Ubuntu Default font.

  Also, I would expect the size of the menu options text to change with
  the setting System Settings > Universal Access > Large Text but it
  does not.

  See attached image for two screen shots, one with Large Text disabled
  and one with it enabled.  The text "Contents", "Universal Access", and
  "Quit" is the text that I expect to be bigger, and that I expect to
  get larger when enabling the Large Text setting.

  Further, the size of the menu item text is not affected by any of the
  font settings exposed by the app "ubuntu-tweak" which lets you change
  the default font, etc.

  This problem exists whether the menu bar is pinned to the top of the
  screen, or to the title bar of the individual application windows.

  I think this is a bug in xorg, but I am not sure.

  lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4
Version table:
   *** 1:7.7+7ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call when proximity sensor triggered

[Launchpad Bug Tracker]

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

** Changed in: telephony-service (Ubuntu)
   Status: New => Confirmed

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

Title:
  Display doesn't turn on for incoming phone call when proximity sensor
  triggered

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

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

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

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call when proximity sensor triggered

[Launchpad Bug Tracker]

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

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Confirmed

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

Title:
  Display doesn't turn on for incoming phone call when proximity sensor
  triggered

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

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

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

[Touch-packages] [Bug 1524648] Re: Display doesn't turn on for incoming phone call when proximity sensor triggered

[Lorn Potter]

I can reproduce this.

Start with screen blanked.
Cover top of phone with something., so it covers the proximity sensor.
Call that phone from another one.
While it is ringing, lift the cover off the proximity sensor.

See that screen stays blanked and only way to unblank it is to push
button.

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

Title:
  Display doesn't turn on for incoming phone call when proximity sensor
  triggered

Status in Canonical System Image:
  Incomplete
Status in telephony-service package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  I just received two phone calls.  In each case the phone started
  ringing but the screen stayed black.  In the first case I let it ring
  for a while hoping that it would magically wake up, since some bugs do
  seem to work that way.  But nothing happened.  I was unwilling to
  press the power button since in iOS that immediately hangs up the
  call.  Eventually however I did press it, and the screen woke up.  But
  I was too late to answer the call.  When the person phoned back the
  screen was black again, so I pressed the power button and was then
  able to slide the slider to answer the call.

  I don't think this is the same as Bug #1493574, since that bug seems
  to happen after the phone has been answered.

  Syslog of about the right time attached.  Phone reports the times of
  the calls as 15:41 and 15:47.

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

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

[Touch-packages] [Bug 1175669] Re: fcitx often fails to work in dash with Unity

[JH Park]

Has it been fixed?
It's the same as usual on Ubuntu 16.04.

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

Title:
  fcitx often fails to work in dash with Unity

Status in Nux:
  Fix Released
Status in Unity:
  Invalid
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in nux source package in Saucy:
  Won't Fix

Bug description:
  The input method "fcitx' is supposed to work with Unity dash in raring,but it 
is not working well.
  This happens *only* when I set the launcher to hide as default.
  When I press Super to open the dash and begin to type characters into dash or 
HUD display (by pressing left alt),sometimes I can activate the input method.In 
more cases,there aren't any response when pressing "ctrl+space".Sometimes I 
can't type anything into dash.

  I've asked a developer of fcitx ("csslayer") but he said he knew
  nothing about it.He said it could be a bug of unity and suggested me
  to report the bug here.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu May  2 23:51:07 2013
  InstallationDate: Installed on 2012-05-01 (365 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-04-03 (28 days ago)

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

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

[Touch-packages] [Bug 1563287] Re: [regression] Right edge switcher stutters badly with only a few apps opened

[Daniel van Vugt]

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

** Also affects: qtmir
   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/1563287

Title:
  [regression] Right edge switcher stutters badly with only a few apps
  opened

Status in Canonical System Image:
  New
Status in QtMir:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  tested on krillin and arale on rc-proposed.
  also I tried the fix for bug 1556763 but that's not related to this as well.

  The right edge switcher on both krillin and arale stutter when I drag
  it from the right edge and then swipe through the list of opened
  windows.

  This was not the case a few months ago, so we clearly regressed here.

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

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

[Touch-packages] [Bug 1563591] Re: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.dpk

[Seth Arnold]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment to this bug report it
seems that there may be a problem with your hardware.  I'd recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

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

Title:
  package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot
  copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to
  '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or
  stream

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  sytem failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssl 1.0.1f-1ubuntu2.16
  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: Wed Mar 30 01:43:17 2016
  DuplicateSignature: package:openssl:1.0.1f-1ubuntu2.16:cannot copy extracted 
data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2013-08-01 (971 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: openssl
  Title: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot 
copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (593 days ago)

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

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

[Touch-packages] [Bug 1563287] Re: Right edge switcher stutters badly with only a few apps opened

[Daniel van Vugt]

Nice videos. Although I found I had to save them offline before they
play nicely and the difference is clear.

I've been wondering about spread performance actually. In particular how
we implement texture smoothing. If it's just GL_LINEAR filtering that
should be fast. But if someone has unwittingly turned on mipmapping then
it could get very slow.

** Tags added: performance regression regression-proposed

** Summary changed:

- Right edge switcher stutters badly with only a few apps opened
+ [regression] Right edge switcher stutters badly with only a few apps opened

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

Title:
  [regression] Right edge switcher stutters badly with only a few apps
  opened

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  tested on krillin and arale on rc-proposed.
  also I tried the fix for bug 1556763 but that's not related to this as well.

  The right edge switcher on both krillin and arale stutter when I drag
  it from the right edge and then swipe through the list of opened
  windows.

  This was not the case a few months ago, so we clearly regressed here.

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

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

[Touch-packages] [Bug 1553549] Re: unity-system-compositor crashed with SIGSEGV in get_adjusted_ptr(), when proprietary Nvidia drivers are installed

[Chris Halse Rogers]

Yeah, remove the nvidia binary drivers and this will likely work. We're
not going to have a release that works with the nvidia binary drivers in
the immediate future :)

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

Title:
  unity-system-compositor crashed with SIGSEGV in get_adjusted_ptr(),
  when proprietary Nvidia drivers are installed

Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  unity-system-co[5574]: segfault at 7f8056ee2490 ip 7f805c592c3b sp
  7fffd6b871a0 error 4 in libstdc++.so.6.0.21[7f805c506000+172000]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.4.2+16.04.20160219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Mar  5 19:03:39 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1455894356
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1102]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM204M [GeForce GTX 
970M] [1462:1102]
  InstallationDate: Installed on 2015-02-25 (374 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file 
/run/lightdm-mir-0 --from-dm-fd 11 --to-dm-fd 20 --vt 8
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f805c592c3b:mov(%rsi),%rax
   PC (0x7f805c592c3b) ok
   source "(%rsi)" (0x7f8056ee2490) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   __gxx_personality_v0 () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   _Unwind_RaiseException () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   _Unwind_Resume_or_Rethrow () from /lib/x86_64-linux-gnu/libgcc_s.so.1
   __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGSEGV in __gxx_personality_v0()
  UpgradeStatus: Upgraded to xenial on 2015-11-03 (122 days ago)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1
  version.lightdm: lightdm 1.17.5-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1545969] Re: webbrowser-app crashes with SIGABRT every time I start it

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1520537 ***
https://bugs.launchpad.net/bugs/1520537

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

** Changed in: oxide-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  webbrowser-app crashes with SIGABRT every time I start it

Status in oxide-qt package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  webbrowser-app crashes every time, a few seconds after I launch it.
  But that's an improvement since I found the workaround for bug
  1535058,

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160202-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.20-0ubuntu2
  Architecture: amd64
  Date: Tue Feb 16 15:58:27 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2015-12-03 (74 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
  Title: webbrowser-app crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Haw Loeung]

FYI, this also affects our mirrors in various clouds such as Amazon AWS
and Google Cloud Compute.

-- 
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 1563591] Re: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.dpk

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

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

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

Title:
  package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot
  copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to
  '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or
  stream

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  sytem failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssl 1.0.1f-1ubuntu2.16
  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: Wed Mar 30 01:43:17 2016
  DuplicateSignature: package:openssl:1.0.1f-1ubuntu2.16:cannot copy extracted 
data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2013-08-01 (971 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: openssl
  Title: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot 
copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (593 days ago)

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

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

[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Gumuiyul]

** Attachment added: "_usr_lib_upower_upowerd.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+attachment/4616513/+files/_usr_lib_upower_upowerd.0.crash

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Jim Hodapp]

I'm experiencing some similar difficulties with my 2016 VW GTI. I
haven't had a chance to gather any useful logs for it yet and need to
play around some more to see more precisely how it's failing and the
steps to reproduce.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

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

[Touch-packages] [Bug 1557248] Re: OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code

[Maciej Puzio]

I created patched openldap packages for xenial, available on the same
PPA as above. I tested amd64 packages on xenial beta 2.

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

Title:
  OpenLDAP: Backport a fix for use-after-free in GnuTLS-related code

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  May I ask that you backport an upstream patch that resolves the issue
  of use-after-free in libldap that interferes with syncrepl, causing
  failures and segfaults.

  OpenLDAP commit: 283f3ae1713df449cc170965b311b19157f7b7ea
  Link: 
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commitdiff;h=283f3ae1713df449cc170965b311b19157f7b7ea
  Modifications to file: libraries/libldap/tls_g.c

  This problem affects openldap 2.4.41 (in Ubuntu wily), 2.4.42 (in Ubuntu 
xenial), as well as in 2.4.44 (current upstream stable version). More details 
are availble on OpenLDAP project bug tracker at:
  http://www.openldap.org/its/index.cgi/Software%20Bugs?id=8385

  Thank you

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

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

[Touch-packages] [Bug 1547927] Re: LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and STARTTLS

[Maciej Puzio]

I created a PPA with patched openldap packages for wily and xenial. If
you would like to test them, there is more information in bug 1557248.

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

Title:
  LDAP_OPT_X_TLS_REQUIRE_CERT handling differences between ldaps:// and
  STARTTLS

Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  Tested with vivid and wily...
  also logged with openldap as 
http://www.openldap.org/its/index.cgi/Incoming?id=8374

  
  The handling of the LDAP_OPT_X_TLS_REQUIRE_CERT option appears to be different
  between servers accessed via ldaps:// and ldap:// (plus STARTTLS) URIs.

  When accessing server with a self-signed certificate, the results are:

  
  ldaps://

  neverOK
  hard Error: can't contact LDAP server
  demand   Error: can't contact LDAP server
  allowOK
  try  Error: can't contact LDAP server

  
  ldap:// plus explicit ldap_start_tls_s()

  neverOK
  hard OK
  demand   OK
  allowOK
  try  OK

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

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

[Touch-packages] [Bug 1562636] Re: battery percentage drops suddenly from 10% to 1%

[Thomas Meyssonnier]

Update:
It only seems to happen when phone stays plugged for some time (4h) after end 
of charge.
 Then it stays for a while at 100%, and drops suddenly from 10%.
Problem disappears if phone is unplugged within 2h after full charge.
So maybe a calibration problem, but possibly without solution due to changing 
battery parameters (voltage for energy, etc...).

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

Title:
  battery percentage drops suddenly from 10% to 1%

Status in upower package in Ubuntu:
  New

Bug description:
  The battery percentage drops from 10% to 1% and probably less in about a 
minute, even with phone locked and inactive.
  This has happened twice in a row already, and probably will systematically.
  Battery warning means I need to plug in instantly to avoid shutdown.
  There seems to be no way to calibrate battery measurements, or set a 
different warning level.
  I have no idea where to get log history for battery level, but I'll do it if 
someone gives me directions.
  Thanks,
  TM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: upower 0.99.2-2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  CurrentDesktop: Unity
  Date: Mon Mar 28 01:20:15 2016
  InstallationDate: Installed on 2016-02-17 (39 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160217-111536)
  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/1562636/+subscriptions

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

[Touch-packages] [Bug 1563594] [NEW] epson printer begins printing but the ubuntu says "stopped"

[Mike]

Public bug reported:

2. laptop@laptop-HP-Pavilion:~$ lsmod | grep usb
usblp  24576  0 
usb_storage69632  1 uas
usbhid 53248  0 
hid   110592  3 hid_generic,usbhid

3. laptop@laptop-HP-Pavilion:~$ tail -f /var/log/syslog
Mar 29 19:24:28 laptop-HP-Pavilion kernel: [ 1570.910012] usblp1: removed
Mar 29 19:24:28 laptop-HP-Pavilion kernel: [ 1570.927392] usblp 1-5:1.1: 
usblp1: USB Bidirectional printer dev 5 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1106
Mar 29 19:31:17 laptop-HP-Pavilion kernel: [ 1979.855077] usb 1-5: USB 
disconnect, device number 5
Mar 29 19:31:17 laptop-HP-Pavilion kernel: [ 1979.860379] usblp1: removed
Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: remove 
/devices/pci:00/:00:12.2/usb1/1-5
Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: URI of detected 
printer: usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1, 
normalized: epson et 2550 series serial 57424e4b3033373518 interface 1
Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: URI of print queue: 
ecblp:/var/run/ecblp0, normalized: ecblp var run ecblp0
Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: URI of print queue: 
usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1, normalized: 
epson et 2550 series serial 57424e4b3033373518 interface 1
Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: Queue 
ipp://localhost:631/printers/EPSON-ET-2550-Series has matching device URI
Mar 29 19:31:17 laptop-HP-Pavilion udev-configure-printer: Disabled printer 
ipp://localhost:631/printers/EPSON-ET-2550-Series as the corresponding device 
was unplugged or turned off

4. Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.052099] usb 1-5: new 
high-speed USB device number 6 using ehci-pci
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192441] usb 1-5: New USB 
device found, idVendor=04b8, idProduct=1106
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192463] usb 1-5: New USB 
device strings: Mfr=1, Product=2, SerialNumber=3
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192475] usb 1-5: Product: 
EPSON ET-2550 Series
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192486] usb 1-5: 
Manufacturer: EPSON
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.192495] usb 1-5: 
SerialNumber: 57424E4B3033373518
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.204576] usblp 1-5:1.1: 
usblp1: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1106
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.205595] usb-storage 1-5:1.2: 
USB Mass Storage device detected
Mar 29 19:32:34 laptop-HP-Pavilion kernel: [ 2056.205919] scsi host10: 
usb-storage 1-5:1.2
Mar 29 19:32:34 laptop-HP-Pavilion mtp-probe: checking bus 1, device 6: 
"/sys/devices/pci:00/:00:12.2/usb1/1-5"
Mar 29 19:32:34 laptop-HP-Pavilion mtp-probe: bus: 1, device: 6 was not an MTP 
device
Mar 29 19:32:34 laptop-HP-Pavilion udev-configure-printer: add 
/devices/pci:00/:00:12.2/usb1/1-5
Mar 29 19:32:34 laptop-HP-Pavilion udev-configure-printer: device devpath is 
/devices/pci:00/:00:12.2/usb1/1-5
Mar 29 19:32:34 laptop-HP-Pavilion udev-configure-printer: MFG:EPSON 
MDL:ET-2550 Series SERN:- serial:57424E4B3033373518
Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.207085] scsi 10:0:0:0: 
Direct-Access EPSONStorage  1.00 PQ: 0 ANSI: 2
Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.207708] sd 10:0:0:0: Attached 
scsi generic sg2 type 0
Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.221908] sd 10:0:0:0: [sdb] 
Attached SCSI removable disk
Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.274797] usblp1: removed
Mar 29 19:32:35 laptop-HP-Pavilion kernel: [ 2057.286627] usblp 1-5:1.1: 
usblp1: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1106
Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI contains USB 
serial number
Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI match: 
usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1
Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI of detected 
printer: usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1, 
normalized: epson et 2550 series serial 57424e4b3033373518 interface 1
Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI of print queue: 
ecblp:/var/run/ecblp0, normalized: ecblp var run ecblp0
Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: URI of print queue: 
usb://EPSON/ET-2550%20Series?serial=57424E4B3033373518=1, normalized: 
epson et 2550 series serial 57424e4b3033373518 interface 1
Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: Queue 
ipp://localhost:631/printers/EPSON-ET-2550-Series has matching device URI
Mar 29 19:32:35 laptop-HP-Pavilion udev-configure-printer: Re-enabled printer 
ipp://localhost:631/printers/EPSON-ET-2550-Series
^C

6. laptop@laptop-HP-Pavilion:~$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 

[Touch-packages] [Bug 1563591] Re: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.dpk

[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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1563591

Title:
  package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot
  copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to
  '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or
  stream

Status in openssl package in Ubuntu:
  New

Bug description:
  sytem failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssl 1.0.1f-1ubuntu2.16
  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: Wed Mar 30 01:43:17 2016
  DuplicateSignature: package:openssl:1.0.1f-1ubuntu2.16:cannot copy extracted 
data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2013-08-01 (971 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: openssl
  Title: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot 
copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (593 days ago)

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

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

[Touch-packages] [Bug 1563591] [NEW] package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.d

[Claudio Bevilacqua]

Public bug reported:

sytem failed

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: openssl 1.0.1f-1ubuntu2.16
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: Wed Mar 30 01:43:17 2016
DuplicateSignature: package:openssl:1.0.1f-1ubuntu2.16:cannot copy extracted 
data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
ErrorMessage: cannot copy extracted data for './usr/share/man/man1/ca.1ssl.gz' 
to '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
InstallationDate: Installed on 2013-08-01 (971 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.11
SourcePackage: openssl
Title: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot 
copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
UpgradeStatus: Upgraded to trusty on 2014-08-14 (593 days ago)

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


** Tags: apport-package i386 trusty

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

Title:
  package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot
  copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to
  '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or
  stream

Status in openssl package in Ubuntu:
  New

Bug description:
  sytem failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: openssl 1.0.1f-1ubuntu2.16
  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: Wed Mar 30 01:43:17 2016
  DuplicateSignature: package:openssl:1.0.1f-1ubuntu2.16:cannot copy extracted 
data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/share/man/man1/ca.1ssl.gz' to '/usr/share/man/man1/ca.1ssl.gz.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2013-08-01 (971 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: openssl
  Title: package openssl 1.0.1f-1ubuntu2.16 failed to install/upgrade: cannot 
copy extracted data for './usr/share/man/man1/ca.1ssl.gz' to 
'/usr/share/man/man1/ca.1ssl.gz.dpkg-new': unexpected end of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-08-14 (593 days ago)

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

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Selene Scriven]

I tried to determine when this started happening.

* krillin rc-proposed 270 (2016-03-01): works.
* arale rc-proposed 270 (2016-03-15.1): works.
* krillin rc-proposed 285 (2016-03-17.1): works.
* arale rc-proposed 280 (2016-03-22.0): the app 'install' button appears to do 
nothing at all, except for making the device vibrate a little.
* arale 286 (2016-03-25): works.
* krillin 293 (2016-03-25): works.
* krillin 294 (2016-03-25): works.
* krillin 295 (2016-03-25): works.
* arale 287 (2016-03-26): it stalled at 0% during install on the first try but 
there was no crash.
* krillin 296 (2016-03-26): crashed just after U1 login, but worked when I 
tried on this rev yesterday.
* arale 288 (2016-03-29): crashed just after U1 login.
* arale 289 (2016-03-29): worked (but earlier crashed by simply tapping an app 
to view details).

My conclusion is that the change was most likely sometime in the past few days, 
but the behavior isn't consistent.  I'm not sure why it sometimes works, 
sometimes crashes while loading app details, and sometimes crashes after U1 
login.  Some suspects include:
* https://requests.ci-train.ubuntu.com/#/ticket/1177
* https://code.launchpad.net/~dobey/unity-scope-click/unsign-reviews
* unity-scope-click changed from 0.1.1+15.04.20160321-0ubuntu1 to 
0.1.1+15.04.20160325-0ubuntu1
* pay-ui changed from 15.10+15.04.20160311-0ubuntu1 to 
15.10+15.04.20160324.1-0ubuntu1

http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/296.commitlog
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/meizu.en/arale/287.commitlog

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 1553309] Re: [FFe]: Include FIPS 140-2 into openssl package

[Joy Latten]

Overview
-
FIPS 140-2 is a U.S. Government computer security standard to accredit 
cryptographic modules.  The certification process  validates and certifies the 
crypto within the module or used by the module.

Canonical is pursuing FIPS 140-2 certification for several modules in
16.04, openssl, kernel crypto, strongswan and openssh server and client.
Each module will require some additions and/or modifications to meet the
FIPS 140-2 standard. From what I understand, we will certify on an
update to 16.04. However, I was informed it would be a good idea to
begin getting some of the changes into 16.04 now. Thus this openssl
freeze exception.

Some general  FIPS 140-2 requirements are
1. Selftests
Each fips-approved crypto algorithm tests against a known test vector to 
verify its correctness.
2. Integrity check
Verify that hmac-sha of the running library is the same as the hmac-sha of 
the shipped and nstalled binary.

The selftests and integrity check are done upon startup and initialization of 
the module and once passed, the module runs in fips mode, meaning only 
fips-approved crypto algorithms that have been certified are to be accessed. 
However, applications can link to the library and choose to use the 
non-approved algorithms. When they do so, they cannot claim to conform to fips. 
 
(I refer to openssl as the module here.)

Implementation specifics
---
For openssl to run in fips mode, several things must occur successfully.
1. openssl must read a 1 from /proc/sys/crypto/fips_enabled.
2. The selftests must pass
3. The integrity check must pass

openssl does not run in fips mode unless all 3 things are successfully 
accomplished.
A linking application can also call FIPS_mode_set(), to enable fips_mode. If 
openssl is not already in fips mode,   
FIPS_mode_set will run selftests and integrity check and they must both pass in 
order for fips mode to be enabled. 

Patchset background
---
Both Red Hat and Suse have already acquired FIPS 140-2 certification for some 
of the same modules we are wanting to certify.
The openssl community has also pursued and achieved fips 140-2 certification. 
https://www.openssl.org/docs/fips.html
However, the openssl community created an entirely separate openssl fips module 
to achieve this. Upon investigation and consultations,  Canonical has decided 
to pursue fips 140-2 certification of openssl in a manner more similar to 
redhat and suse which requires making changes to the regular openssl rather 
than including a separate openssl fips module.

Redhat and Suse appear to have used the same fips patchset for openssl,
with some minor differences between the two. The code in debdiff
attached to this bug is based upon Red Hat and Suse's fips patches found
in the opensuse and fedora openssl source,  with some minor changes to
accommodate updates to the fips standards and some code improvements.
The openssl community's openssl fips module had a few updated self-
tests, so I included these where appropriate.

The fips patchsets will not be included into the upstream openssl nor
the upstream debian. They are to be maintained by Canonical and used to
achieve FIPS 140-2 certification for Ubuntu.

Brief overview of the patchset

The openssl changes and additions in this bug are the following.
1. Include the selftests. The selftests are run upon startup and initialization 
of openssl. These run successfully.

2. Partially completed integrity check. This patch includes the code to
perform the integrity check. But it does not include the hmac-sha of
libcrypto and libssl to verify against.  Thus the integrity check will
fail and openssl won't run in fips-mode. Linking applications can access
the same crypto they always have and run as they always have.

3. Defines OPENSSL_FIPS , which introduces additional code that had previously 
been undefined. Some of the code within this define was no longer needed or 
needed updating to comply with recent fips specs. Those changes were done where 
appropriate.  Also most of the crypto code changes within this define requires 
openssl to be running in fips mode to be executed.  i.e. if (FIPS_mode) then do 
something  OR if (FIPS_selftest_failed) return error;   
When not in fips mode, 0 is returned by these routines, and nothing happens.
 
4. This patchset does not enable openssl to run in fips mode. Runtime behaviour 
should not change, other than the selftest and integrity check are run upon 
initialization and startup. 
 - The Ubuntu kernel does not yet create the /proc/sys/crypto/fips_enabled 
file and put a 1 in it. 
This check will fail and openssl will run in "non-fips" mode, in other 
words run as it normally does.
 - The integrity check will never pass since we do not ship the hmac-sha of 
the installed binary to verify against.
   So, any linking applications that call FIPS_mode_set(), 

[Touch-packages] [Bug 1563583] [NEW] package libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1 failed to install/upgrade: package libqt5webkit5:amd64 is not ready for configuration cannot configure (current s

[Massimo Luraschi]

Public bug reported:

I was trying to install unity tweak tool, after performing updates right
after a fresh install. There seemed to be a problem with dpkg and
lightdm, so I restarted the PC. After restarting, I get this error.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1
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
AptOrdering:
 libqt5webkit5: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Mar 30 00:12:56 2016
DpkgTerminalLog:
 dpkg: error processing package libqt5webkit5:amd64 (--configure):
  package libqt5webkit5:amd64 is not ready for configuration
  cannot configure (current status 'half-installed')
DuplicateSignature: package:libqt5webkit5:amd64:5.4.2+dfsg-1ubuntu2.1:package 
libqt5webkit5:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
ErrorMessage: package libqt5webkit5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-03-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: qtwebkit-opensource-src
Title: package libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1 failed to 
install/upgrade: package libqt5webkit5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtwebkit-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package wily

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

Title:
  package libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1 failed to
  install/upgrade: package libqt5webkit5:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

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

Bug description:
  I was trying to install unity tweak tool, after performing updates
  right after a fresh install. There seemed to be a problem with dpkg
  and lightdm, so I restarted the PC. After restarting, I get this
  error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1
  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
  AptOrdering:
   libqt5webkit5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Mar 30 00:12:56 2016
  DpkgTerminalLog:
   dpkg: error processing package libqt5webkit5:amd64 (--configure):
package libqt5webkit5:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  DuplicateSignature: package:libqt5webkit5:amd64:5.4.2+dfsg-1ubuntu2.1:package 
libqt5webkit5:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  ErrorMessage: package libqt5webkit5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-03-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: qtwebkit-opensource-src
  Title: package libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1 failed to 
install/upgrade: package libqt5webkit5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1563583] Re: package libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1 failed to install/upgrade: package libqt5webkit5:amd64 is not ready for configuration cannot configure (current sta

[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 qtwebkit-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1563583

Title:
  package libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1 failed to
  install/upgrade: package libqt5webkit5:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

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

Bug description:
  I was trying to install unity tweak tool, after performing updates
  right after a fresh install. There seemed to be a problem with dpkg
  and lightdm, so I restarted the PC. After restarting, I get this
  error.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1
  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
  AptOrdering:
   libqt5webkit5: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Mar 30 00:12:56 2016
  DpkgTerminalLog:
   dpkg: error processing package libqt5webkit5:amd64 (--configure):
package libqt5webkit5:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  DuplicateSignature: package:libqt5webkit5:amd64:5.4.2+dfsg-1ubuntu2.1:package 
libqt5webkit5:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  ErrorMessage: package libqt5webkit5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-03-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: qtwebkit-opensource-src
  Title: package libqt5webkit5:amd64 5.4.2+dfsg-1ubuntu2.1 failed to 
install/upgrade: package libqt5webkit5:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Alberto Aguirre]

** Changed in: mir
   Importance: Undecided => High

** Changed in: mir/0.21
   Importance: Undecided => High

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

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Mir 0.21 series:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

  The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
  The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.

  We could fix this by:
  - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
  - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
  - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

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

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

[Touch-packages] [Bug 1537308] Re: System sends Control, Alt and Shift events without input.

[Joe Helfrifch]

*** This bug is a duplicate of bug 1532746 ***
https://bugs.launchpad.net/bugs/1532746

** This bug has been marked a duplicate of bug 1532746
   SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

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

Title:
  System sends Control, Alt and Shift events without input.

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I noticed strange behavior from my Ubuntu system.  While left idle,
  the screensaver would shut off with no interaction with the machine.
  While using the machine, webpages would zoom in or out when trying to
  scroll, and command windows would open while typing.

  Using xev, I found that these events corresponded with ALt_L,
  Control_L and Shift_R events, even though those buttons were not being
  pressed.  I'm attaching a xev log, searching for _L will show the
  events.  ((Shift_R events are, for some reason, much rarer and do not
  occur in the particular log I'm adding.)  In many (but not all)
  incidents, the KeyRelease event occurs without a preceding KeyPress
  event.  This problem starts a variable period of time after booting
  the machine; generally within 4 hours.  Once it starts, it persists
  until a reboot.

  Disabling the trackpad with xinput will stop the problem for several
  hours, but eventually something re-enables the trackpad and the
  problem reappears.

  Running memtest on the box generates an error when one specific core
  runs one specific test, but I cannot rule out that being related to
  memtest's problems with UEFI systems.  (See
  passmark.com/forum/showthread.php?5638 for info on my memtest results
  and the UEFI issues.) I returned the machine to HP for service.  They
  replaced the keyboard, trackpad and memory.  This did not resolve the
  problem.

  I've recreated the problem in UbuntuMate, Ubuntu, and Debian, on both
  3.x and 4.x kernels.  I cannot reliably reproduce the issue on the
  Windows partition on the same box; I think I might have seen it once
  or twice while working on the machine, but can't rule out accidental
  keypresses by me at those times.  Leaving a keylogger running for over
  24 hours on the Windows partition did not show any unexpected keyboard
  events.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 22 21:36:14 2016
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.19.0-32-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-33-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-42-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:80af]
  InstallationDate: Installed on 2015-10-30 (84 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:938): WARNING **: [PIDs] Failed to execute command: 
upstart
   
   ** (lightdm-gtk-greeter:938): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1191): WARNING **: [PIDs] Failed to execute command: 
upstart
   
   ** (lightdm-gtk-greeter:1191): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic.efi.signed 
root=UUID=613f6223-b665-4289-9dfa-7b003124dfdf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80AF
  dmi.board.vendor: HP
  dmi.board.version: 81.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd08/06/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80AF:rvr81.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  

[Touch-packages] [Bug 1399289] Re: Subtitle support in Header

[Launchpad Bug Tracker]

** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/subtitle

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

Title:
  Subtitle support in Header

Status in Ubuntu Document Viewer App:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  In the PdfView we are using a multi-line header, that provides
  informations about the name of the file and the current page (as sub-
  text).

  For UX consistence, we should extend the custom header to the Image
  Viewer and the Text Viewer. However it's not clear which information
  should be provided as sub-text.

  See attached screenshot.

  UX:
  This is going to be available in the SDK. The Header title slot might have 
two lines of text

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

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

[Touch-packages] [Bug 1537308] Re: System sends Control, Alt and Shift events without input.

[Joe Helfrifch]

Possible duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532746

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

Title:
  System sends Control, Alt and Shift events without input.

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  I noticed strange behavior from my Ubuntu system.  While left idle,
  the screensaver would shut off with no interaction with the machine.
  While using the machine, webpages would zoom in or out when trying to
  scroll, and command windows would open while typing.

  Using xev, I found that these events corresponded with ALt_L,
  Control_L and Shift_R events, even though those buttons were not being
  pressed.  I'm attaching a xev log, searching for _L will show the
  events.  ((Shift_R events are, for some reason, much rarer and do not
  occur in the particular log I'm adding.)  In many (but not all)
  incidents, the KeyRelease event occurs without a preceding KeyPress
  event.  This problem starts a variable period of time after booting
  the machine; generally within 4 hours.  Once it starts, it persists
  until a reboot.

  Disabling the trackpad with xinput will stop the problem for several
  hours, but eventually something re-enables the trackpad and the
  problem reappears.

  Running memtest on the box generates an error when one specific core
  runs one specific test, but I cannot rule out that being related to
  memtest's problems with UEFI systems.  (See
  passmark.com/forum/showthread.php?5638 for info on my memtest results
  and the UEFI issues.) I returned the machine to HP for service.  They
  replaced the keyboard, trackpad and memory.  This did not resolve the
  problem.

  I've recreated the problem in UbuntuMate, Ubuntu, and Debian, on both
  3.x and 4.x kernels.  I cannot reliably reproduce the issue on the
  Windows partition on the same box; I think I might have seen it once
  or twice while working on the machine, but can't rule out accidental
  keypresses by me at those times.  Leaving a keylogger running for over
  24 hours on the Windows partition did not show any unexpected keyboard
  events.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 22 21:36:14 2016
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.19.0-32-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-33-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-42-generic, x86_64: installed
   fglrx-core, 15.200, 3.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:80af]
  InstallationDate: Installed on 2015-10-30 (84 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:938): WARNING **: [PIDs] Failed to execute command: 
upstart
   
   ** (lightdm-gtk-greeter:938): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1191): WARNING **: [PIDs] Failed to execute command: 
upstart
   
   ** (lightdm-gtk-greeter:1191): WARNING **: Failed to load user image: Failed 
to open file '/home/jbhelfrich/.face': No such file or directory
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic.efi.signed 
root=UUID=613f6223-b665-4289-9dfa-7b003124dfdf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80AF
  dmi.board.vendor: HP
  dmi.board.version: 81.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd08/06/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80AF:rvr81.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2

[Touch-packages] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

[Serge Hallyn]

** Changed in: libvirt (Ubuntu)
   Importance: Medium => High

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

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

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

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

[Touch-packages] [Bug 1551150] Re: devel-proposed - android lxc container fails to start

[Serge Hallyn]

Assuming this is running upstart (as it looks like), try adding the
debug and verbose flags as shown in the upstart cookbook?

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

Title:
  devel-proposed - android lxc container fails to start

Status in Canonical System Image:
  Confirmed
Status in lxc package in Ubuntu:
  New

Bug description:
  Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446

  ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and
  equivalent images on other devices do not boot and hang on the boot
  logo.

  From the list of changes, it could be lxc:
  446: lxc 2.0.0~rc2-0ubuntu2
  447: lxc 2.0.0~rc3-0ubuntu1

  Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either.

  lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium

    * New upstream release (2.0.0~rc3)
  - Make the cgfs backend and cgns work without cgmanager
  - Manpage updates
  - Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
    * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral

  lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium

    * Use versioned dependencies against the various binary packages.
    * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
    * Move the lxcfs recommends from lxc-templates to liblxc1.
    * Drop cgmanager, use the cgfs backend instead.
    * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.

  Device tarballs between 446 and 447 are the same.

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

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

[Touch-packages] [Bug 1435765] Re: focused gtk tab looks same as unfocused

[Amr Ibrahim]

** This bug is no longer a duplicate of bug 1399734
   Current tab is not highlighted

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

Title:
  focused gtk tab looks same as unfocused

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Open two or more tabs in gnome-terminal. Click on one of the tab
  labels to give it the Gtk+ focus.

  Notice that typing letters don't send it to the terminal whereas
  left/right arrows move to the prev/next tab. This is to confirm that
  it's indeed the tab label, and not the actual terminal area that has
  the focus.

  This is a quite bad scenario, as you might have absolutely no clue
  what's going on and why you can't type to the terminal.

  In Utopic, the focused tab label had a different (orange-ish) look, so
  it gave you a visual clue about what was happening. This is gone from
  Vivid, making it much harder to see what the problem is. I guess
  there'll be several bugreports along the lines of "suddenly I can't
  type into the terminal anymore" with no reasonable explanation.

  Could you please restore Utopic's behavior, so that a visual feedback
  is given if a tab label has the Gtk+ focus?

  I'm using the default Unity desktop with its default Ambiance theme,
  everything's the default as shipped by Ubuntu, except for gnome-
  terminal which I'm a developer of, so I use git master (and used to
  use that on Utopic too). So I'm absolutely sure that it was not gnome-
  terminal that changed. Probably either Gtk+ itself or the Ambiance
  theme is the culprit. And probably more apps are affected, not just
  the terminal.

  (Just for reference: gnome-terminal ticket to disallow focusing the
  tab bar: https://bugzilla.gnome.org/show_bug.cgi?id=746665)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: light-themes 14.04+15.04.20150319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 24 10:39:32 2015
  InstallationDate: Installed on 2012-05-30 (1027 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (6 days ago)

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

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

[Touch-packages] [Bug 1399734] Re: Current tab is not highlighted

[Amr Ibrahim]

** No longer affects: gnome-terminal (Ubuntu)

** No longer affects: gnome-terminal

** Patch removed: "notebook-dont-let-keyboard-focus-enter-from-tab-label.patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1399734/+attachment/4598177/+files/notebook-dont-let-keyboard-focus-enter-from-tab-label.patch

** Tags removed: patch

** Bug watch removed: GNOME Bug Tracker #746665
   https://bugzilla.gnome.org/show_bug.cgi?id=746665

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

Title:
  Current tab is not highlighted

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  With the Ambiance or Radiance theme, in windows using a GtkNotebook
  the current tab is not highlighted to distinguish it from hidden tabs.
  In some apps you can just about see a faint line under the inactive
  tabs, but some apps, such as roxterm, don't use the border option, so
  it's impossible to tell which tab is selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: light-themes 14.04+14.10.20141015-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  5 17:27:41 2014
  InstallationDate: Installed on 2014-06-13 (174 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (42 days ago)

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

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Alberto Aguirre]

** Also affects: mir
   Importance: Undecided
   Status: New

** Changed in: mir
 Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)

** Changed in: mir
   Status: New => In Progress

** Also affects: mir/0.21
   Importance: Undecided
   Status: New

** Changed in: mir/0.21
   Status: New => Fix Committed

** Changed in: mir/0.21
Milestone: None => 0.21.0

** Changed in: mir
Milestone: None => 0.22.0

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

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in Mir:
  In Progress
Status in Mir 0.21 series:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

  The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
  The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.

  We could fix this by:
  - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
  - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
  - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

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

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

[Touch-packages] [Bug 1399734] Re: Current tab is not highlighted

[Amr Ibrahim]

The patch comes from the attached upstream bug.

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

Title:
  Current tab is not highlighted

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  With the Ambiance or Radiance theme, in windows using a GtkNotebook
  the current tab is not highlighted to distinguish it from hidden tabs.
  In some apps you can just about see a faint line under the inactive
  tabs, but some apps, such as roxterm, don't use the border option, so
  it's impossible to tell which tab is selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: light-themes 14.04+14.10.20141015-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  5 17:27:41 2014
  InstallationDate: Installed on 2014-06-13 (174 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1399734/+subscriptions

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

[Touch-packages] [Bug 1399734] Re: Current tab is not highlighted

[Amr Ibrahim]

It's fixed in gnome-terminal 3.18.3 in xenial.

** Changed in: gnome-terminal (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Current tab is not highlighted

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  With the Ambiance or Radiance theme, in windows using a GtkNotebook
  the current tab is not highlighted to distinguish it from hidden tabs.
  In some apps you can just about see a faint line under the inactive
  tabs, but some apps, such as roxterm, don't use the border option, so
  it's impossible to tell which tab is selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: light-themes 14.04+14.10.20141015-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec  5 17:27:41 2014
  InstallationDate: Installed on 2014-06-13 (174 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1399734/+subscriptions

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

[Touch-packages] [Bug 1563572] [NEW] Greeter password entry cut/paste widget in portrait mode

[Allan LeSage]

Public bug reported:

This feels pretty minor in the scheme of things but on avila.

TEST CASE
1.  Unlock device, device greeter appears
2.  Tap on Password entry
3.  Long-press on cursor in Password entry
EXPECTED
Selection pop-up appears in landscape mode
ACTUAL
Selection pop-up appears in portrait mode

Happy to furnish a screenshot.  Meanwhile I don't know what I'm
expecting to do with the cut/paste selection tool here, maybe it doesn't
apply here?

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

** Summary changed:

- Greeter password entry selection in portrait mode
+ Greeter password entry cut/paste widget in portrait mode

** Package changed: unity8 (Ubuntu) => canonical-devices-system-image

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

Title:
  Greeter password entry cut/paste widget in portrait mode

Status in Canonical System Image:
  New

Bug description:
  This feels pretty minor in the scheme of things but on avila.

  TEST CASE
  1.  Unlock device, device greeter appears
  2.  Tap on Password entry
  3.  Long-press on cursor in Password entry
  EXPECTED
  Selection pop-up appears in landscape mode
  ACTUAL
  Selection pop-up appears in portrait mode

  Happy to furnish a screenshot.  Meanwhile I don't know what I'm
  expecting to do with the cut/paste selection tool here, maybe it
  doesn't apply here?

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

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

[Touch-packages] [Bug 1563115] Re: System moves xorg.conf

[Tracker1]

workaround:
sudo chattr +i /etc/X11/xorg.conf

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

Title:
  System moves xorg.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  Every time i boot into Xubuntu 16.04 (daily) my xorg.conf got moved to 
xorg.conf.%DATE% by somebody.
  Tested on both 15.10 upgraded copy and 16.04 clean install

  
  $ ls /etc/X11
  app-defaults  default-display-manager  rgb.txt  xkb Xreset
Xresources  Xsession.dxsm
  cursors   fontsxinitxorg.conf.03292016  Xreset.d  
XsessionXsession.options

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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: XFCE
  Date: Tue Mar 29 02:40:51 2016
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1563563] Re: package libmpdec2:i386 2.4.2-1 failed to install/upgrade: package libmpdec2:i386 is already installed and configured

[Apport retracing service]

*** This bug is a duplicate of bug 1563561 ***
https://bugs.launchpad.net/bugs/1563561

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1563561
   package python3.5 3.5.1-9ubuntu1 failed to install/upgrade: package 
python3.5 is already installed and configured

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

Title:
  package libmpdec2:i386 2.4.2-1 failed to install/upgrade: package
  libmpdec2:i386 is already installed and configured

Status in mpdecimal package in Ubuntu:
  New

Bug description:
  restart after update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmpdec2:i386 2.4.2-1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: i386
  Date: Tue Mar 29 23:03:48 2016
  Dependencies:
   gcc-6-base 6-20160319-0ubuntu1
   libc6 2.23-0ubuntu2
   libgcc1 1:6-20160319-0ubuntu1
  DuplicateSignature:
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libmpdec2:i386 (--configure):
package libmpdec2:i386 is already installed and configured
  ErrorMessage: package libmpdec2:i386 is already installed and configured
  InstallationDate: Installed on 2015-11-08 (141 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: mpdecimal
  Title: package libmpdec2:i386 2.4.2-1 failed to install/upgrade: package 
libmpdec2:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1561924] Re: can't scroll to bottom of wifi list in wizard

[Selene Scriven]

(er, rc-proposed 297, not plain rc)

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

Title:
  can't scroll to bottom of wifi list in wizard

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  On today's phone image (arale rc-proposed 286), I can't connect to my
  access point in the OOBE wizard because the WAP name starts with a 'w'
  and I can't get the wifi list to scroll all the way to the bottom.

  Any time I get it near the bottom, the list re-shuffles itself and
  scrolls back up.

  Taochen reports seeing the same on a krillin.

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

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

[Touch-packages] [Bug 1563563] [NEW] package libmpdec2:i386 2.4.2-1 failed to install/upgrade: package libmpdec2:i386 is already installed and configured

[Yann]

Public bug reported:

restart after update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libmpdec2:i386 2.4.2-1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic i686
ApportVersion: 2.20-0ubuntu3
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: i386
Date: Tue Mar 29 23:03:48 2016
Dependencies:
 gcc-6-base 6-20160319-0ubuntu1
 libc6 2.23-0ubuntu2
 libgcc1 1:6-20160319-0ubuntu1
DuplicateSignature:
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package libmpdec2:i386 (--configure):
  package libmpdec2:i386 is already installed and configured
ErrorMessage: package libmpdec2:i386 is already installed and configured
InstallationDate: Installed on 2015-11-08 (141 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.9
SourcePackage: mpdecimal
Title: package libmpdec2:i386 2.4.2-1 failed to install/upgrade: package 
libmpdec2:i386 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed apport-package i386 need-duplicate-check xenial

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

Title:
  package libmpdec2:i386 2.4.2-1 failed to install/upgrade: package
  libmpdec2:i386 is already installed and configured

Status in mpdecimal package in Ubuntu:
  New

Bug description:
  restart after update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libmpdec2:i386 2.4.2-1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic i686
  ApportVersion: 2.20-0ubuntu3
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: i386
  Date: Tue Mar 29 23:03:48 2016
  Dependencies:
   gcc-6-base 6-20160319-0ubuntu1
   libc6 2.23-0ubuntu2
   libgcc1 1:6-20160319-0ubuntu1
  DuplicateSignature:
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libmpdec2:i386 (--configure):
package libmpdec2:i386 is already installed and configured
  ErrorMessage: package libmpdec2:i386 is already installed and configured
  InstallationDate: Installed on 2015-11-08 (141 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: mpdecimal
  Title: package libmpdec2:i386 2.4.2-1 failed to install/upgrade: package 
libmpdec2:i386 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Selene Scriven]

FWIW, I'm getting a similar crash on arale rc-proposed 289...  except
the crash happens merely by tapping on an app to view the details.  No
U1 login attempt is required.  I'm not sure if it's the same bug or not,
but it's a crash in the same component.

https://errors.ubuntu.com/oops/8621d07e-f5f4-11e5-9852-fa163e30221b

I think I saw this earlier and thought it was the usual network / server
timeout issue, but a closer look shows it's not.

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 784549] Re: [nc] Mono: Style: Cyrillic Ghe Г has incorrect bottom serif and looks strange

[drkwv]

Wow there's almost 5 years to this bug and it's still persists, now in
Xenial. Does anybody know how to fix it manually?

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

Title:
  [nc] Mono: Style: Cyrillic Ghe Г has incorrect bottom serif and looks
  strange

Status in Ubuntu Font Family:
  Fix Committed
Status in ubuntu-font-family-sources package in Ubuntu:
  Triaged

Bug description:
  The serif on the uppercase Г in Cyrillic in the monospace font seems
  very weird to a native Cyrillic reader such as me (for Serbian
  language).

  Ideally the design should be changed to the same as in the Ubuntu
  proportional fonts, just a plain two-stroke character, suitably
  proportioned to fill out the monospace cell when used in runs of
  monospace Cyrillic.

  Proposed solution:
    1. Monospace Г to have bottom serif removed
    2. Redrawn as two strokes, correctly proportioned for monospace Cyrillic 
usage

  See also: bug 867577 (about greek Gamma).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/784549/+subscriptions

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Selene Scriven]

I'm accustomed to the store sometimes taking a few tries to install an
app, but this issue is new and leads to the crash as described.

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Launchpad Bug Tracker]

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

** Changed in: ubuntuone-credentials (Ubuntu)
   Status: New => Confirmed

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 1563007] Re: App is not installed after credentials are introduced

[Launchpad Bug Tracker]

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

** Changed in: unity-scope-click (Ubuntu)
   Status: New => Confirmed

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

Title:
  App is not installed after credentials are introduced

Status in Canonical System Image:
  Confirmed
Status in ubuntuone-credentials package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Confirmed

Bug description:
  Test case.
  - Remove your Ubuntu One account
  - Go to App Store and select an app to install (e.g. Terminal)
  - Introduce your credentials

  Expected result.
  - App is intalled.

  Actual result.
  - App is not installed

  current build number: 66
  device name: frieza

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

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

[Touch-packages] [Bug 1561924] Re: can't scroll to bottom of wifi list in wizard

[Selene Scriven]

I see this on the latest krillin rc 297.  Since it breaks one of the
main wizard steps, is this a release blocker?

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

Title:
  can't scroll to bottom of wifi list in wizard

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  On today's phone image (arale rc-proposed 286), I can't connect to my
  access point in the OOBE wizard because the WAP name starts with a 'w'
  and I can't get the wifi list to scroll all the way to the bottom.

  Any time I get it near the bottom, the list re-shuffles itself and
  scrolls back up.

  Taochen reports seeing the same on a krillin.

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

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

[Touch-packages] [Bug 1562783] Re: GPS stops without reason

[Joan CiberSheep]

Hello again.
Today I did some tests as promised.
I updated to 0.57.

I couldn't manage to reproduce the situation were GPS is not updated but
I got 5 white screens in a route of 1,5 hours, witch didn't happen
before (with 0.54, 0.55)

Phone rebooted.
Search for a location (I'm in movement). Ask for route and uNav doesn't find 
route but points my exact location with no problem
http://paste.ubuntu.com/15549519/

Closed uNav and search again... no problem until: white screen
While GPS is bouncing
http://paste.ubuntu.com/15549611/
+ & - buttons vibrate on tap.
when tap on route icon, all icons stopped vibrating (screen is still white).

Closed and opened uNav
White screen while readjusting the route
All buttons vibrate on tap.
http://paste.ubuntu.com/15549702/

Closed and opened uNav
Crashed searching for gps signal. App just closed.

Closed and opened uNav.
White screen while screen rotates
All buttons vibrate on tap.
http://paste.ubuntu.com/15549733/

Closed and opened uNav. Blocked screen rotation
Blank in the middle of a sentence while searching for new route
All buttons vibrate on tap.
http://paste.ubuntu.com/15549808/

Closed uNav
http://paste.ubuntu.com/15549812/

I can't see a pattern. Is my device short of memory? It's 1GB Aquaris E5
HD, I had no other app opened but logviewer.

I hope this is of some help ;)

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

Title:
  GPS stops without reason

Status in uNav:
  Invalid
Status in location-service package in Ubuntu:
  New

Bug description:
  Hello Marcos,

  yesterday I was using uNav and:

  1) Looked for an address, found a route. Started driving and after some 
indications, uNav just freezed in a location. No more response.
  2) Closed it, opened again (^__^) . Searched for the same location  and 
quickly continued the route indications (without searching the route again: 
good) but after sometime screen went blank (except for  zoom buttons on screen).

  3) Remembered that I didn't reboot the phone in a while. Reboot.
  Search for location,route, start driving. After some time blank screen
  again.

  4) Started logging, searached location, route... driving: blank screen (a 
couple more)
  http://paste.ubuntu.com/15527213/
  http://paste.ubuntu.com/15527312/

  5) Reboot phone, etc: blank screen
  http://paste.ubuntu.com/15529159/

  6) Put phone into flight mode (don't ask) went out again, search for 
location, route... driving: freeze in location
  http://paste.ubuntu.com/15529638/

  7) Closed uNav opened again: search for location: error: GPS Denied. Error 
reading GPS status. Please review device settings.
  (obviouly I did not turned off the GPS... :))

  ¿Es grave doctor?

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

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

[Touch-packages] [Bug 1560710] Re: ISST-SAN:KVM:R3-0: LVM udev rules deadlock with large number of PVs

[Martin Pitt]

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

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

Title:
  ISST-SAN:KVM:R3-0: LVM udev rules deadlock with large number of PVs

Status in lvm2 package in Ubuntu:
  Triaged
Status in watershed package in Ubuntu:
  In Progress

Bug description:
  Oringinal problem statement:

  Today I reinstalled lucky03.Installation went fine.After Installation
  it got rebooted and after reboot ,Unable to get the login prompt

  == Comment: #3 - Kevin W. Rudd - 2016-03-14 18:49:02 ==
  It looks like this might be related to bug 124628 .  I was able to get to a 
login prompt by adding the following to the boot options:

  udev.children-max=500

  Lekshmi,

  Can you provide additional information on how you did the install for
  this lpar?  It would be nice to replicate the exact install sequence
  from the beginning in order to try to capture some additional debug
  information.

  == Comment: #18 - Mauricio Faria De Oliveira - 2016-03-22 16:59:40 ==
  It's possible to reproduce this on a qemu-kvm guest w/ emulated hard disks 
(i.e., image/file-backed disks).

  Configuration:
  - 1 disk w/ 16.04 (no LVM required)
  - 50 disks (w/ LVM volumes)

  # ps l
  ...
  S 0  7014   145  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7015   144  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7016   140  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7017   139  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7018   142  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7019  7014  3520  1280 0:0   20:53 00:00:00 sh -c /sbin/lvm vgscan; /
  S 0  7020   137  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7021   143  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7023   136  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7024   141  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7025   138  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7026  7019 10560  9344 0:0   20:53 00:00:00 /sbin/lvm vgchange -a y
  ...

  # cat /proc/7014/stack
  [] 0xc34e3b20
  [] __switch_to+0x1f8/0x350
  [] do_wait+0x22c/0x2d0
  [] SyS_wait4+0xa8/0x140
  [] system_call+0x38/0xb4

  # cat /proc/7019/stack
  [] 0xc31cfb20
  [] __switch_to+0x1f8/0x350
  [] do_wait+0x22c/0x2d0
  [] SyS_wait4+0xa8/0x140
  [] system_call+0x38/0xb4

  # cat /proc/7026/stack
  [] 0xc31aba80
  [] __switch_to+0x1f8/0x350
  [] SyS_semtimedop+0x810/0x9f0
  [] SyS_ipc+0x154/0x3c0
  [] system_call+0x38/0xb4

  # dmsetup udevcookies
  Cookie   Semid  Value  Last semop time   Last change time
  0xd4d888a0  1  Tue Mar 22 20:53:55 2016  Tue Mar 22 
20:53:55 2016

  == Comment: #19 - Mauricio Faria De Oliveira - 2016-03-22 17:00:13 ==
  Command to create the LVM volumes on initramfs:

  # for sd in /sys/block/sd*; do sd="$(basename $sd)"; [ "$sd" = 'sda' ]
  && continue; lvm pvcreate /dev/$sd; lvm vgcreate vg-$sd /dev/$sd; lvm
  lvcreate --size 1000m --name lv-$sd vg-$sd; done

  # lvm vgdisplay | grep -c 'VG Name'
  50

  == Comment: #20 - Mauricio Faria De Oliveira - 2016-03-22 17:57:50 ==
  Hm, got a better picture of this:

  The problem doesn't seem to be a synchronization issue.
  I've learned a bit more about the udev events/cookies for sdX and lvm volumes.

  1) The sdX add events happen, for multiple devices.  
  Each device consumes 1 udev worker.

  2) The sdX add events run 'watershed .. vgchange -a y...'.
   If this detects an LVM volume in sdX, it will try  to activate it, and 
then block/wait for the respective LVM/udev cookie to complete (i.e., wait for 
the LVM dm-X device add event to finish)

  3) The dm-X device add event is fired from the kernel.

  4) There are no available udev workers to process it.
  The event processing remains queued.
  Thus, the cookie will not be released.

  5) No udev workers from sdX devices will finish, since all are waiting
  for cookies to be complete, which demand available udev workers.

  == Comment: #21 - Mauricio Faria De Oliveira - 2016-03-22 18:02:11 ==
  Got a confirmation of the previous hypothesis.

  Added the --noudevsync argument to the vgchange command in the initramfs's 
/lib/udev/rules.d/85-lvm2.rules.
  This causes vgchange not to wait for an udev cookie.

  Things didn't block, actually finished quite fast.

  == Comment: #23 - Mauricio Faria De Oliveira - 2016-03-22 18:14:41 ==
  Hi Canonical,

  May you please help in finding a solution to this problem?
  If I recall correctly, @pitti works w/ udev and early boot in general.

  The problem summary (from previous comments) is:

  1) There are more SCSI disks w/ LVM volumes 

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

[Karl Foley]

Forgot to mention that I also updated the vmlinuz and initrd.img links
by hand in /boot to point to the 3.18.0-25 versions.

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

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

Status in ubuntu-mate:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Error occured during UBUNTU Mate upgrade to 15.10 on Raspberry PI2 and
  once trying perform manual update getting:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.120ubuntu6) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.120ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-3.18.0-25-rpi2
  Unsupported platform.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 
1
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.120ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: armhf
  Date: Sun Oct 25 08:19:08 2015
  DuplicateSignature: package:initramfs-tools:0.120ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Scarlett Clark]

As noted above, you must install from the PPA to get the fix.
We are still blocked by one package to be able to push these into release.
Scarlett

-- 
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 1560710] Re: ISST-SAN:KVM:R3-0: LVM udev rules deadlock with large number of PVs

[Martin Pitt]

** Summary changed:

- ISST-SAN:KVM:R3-0:Unable to get the login prompt after reinstallation of 
Ubuntu16.04
+ ISST-SAN:KVM:R3-0: LVM udev rules deadlock with large number of PVs

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

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

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

Title:
  ISST-SAN:KVM:R3-0: LVM udev rules deadlock with large number of PVs

Status in lvm2 package in Ubuntu:
  Triaged
Status in watershed package in Ubuntu:
  Triaged

Bug description:
  Oringinal problem statement:

  Today I reinstalled lucky03.Installation went fine.After Installation
  it got rebooted and after reboot ,Unable to get the login prompt

  == Comment: #3 - Kevin W. Rudd - 2016-03-14 18:49:02 ==
  It looks like this might be related to bug 124628 .  I was able to get to a 
login prompt by adding the following to the boot options:

  udev.children-max=500

  Lekshmi,

  Can you provide additional information on how you did the install for
  this lpar?  It would be nice to replicate the exact install sequence
  from the beginning in order to try to capture some additional debug
  information.

  == Comment: #18 - Mauricio Faria De Oliveira - 2016-03-22 16:59:40 ==
  It's possible to reproduce this on a qemu-kvm guest w/ emulated hard disks 
(i.e., image/file-backed disks).

  Configuration:
  - 1 disk w/ 16.04 (no LVM required)
  - 50 disks (w/ LVM volumes)

  # ps l
  ...
  S 0  7014   145  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7015   144  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7016   140  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7017   139  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7018   142  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7019  7014  3520  1280 0:0   20:53 00:00:00 sh -c /sbin/lvm vgscan; /
  S 0  7020   137  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7021   143  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7023   136  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7024   141  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7025   138  3008  1216 0:0   20:53 00:00:00 /lib/udev/watershed sh -c
  S 0  7026  7019 10560  9344 0:0   20:53 00:00:00 /sbin/lvm vgchange -a y
  ...

  # cat /proc/7014/stack
  [] 0xc34e3b20
  [] __switch_to+0x1f8/0x350
  [] do_wait+0x22c/0x2d0
  [] SyS_wait4+0xa8/0x140
  [] system_call+0x38/0xb4

  # cat /proc/7019/stack
  [] 0xc31cfb20
  [] __switch_to+0x1f8/0x350
  [] do_wait+0x22c/0x2d0
  [] SyS_wait4+0xa8/0x140
  [] system_call+0x38/0xb4

  # cat /proc/7026/stack
  [] 0xc31aba80
  [] __switch_to+0x1f8/0x350
  [] SyS_semtimedop+0x810/0x9f0
  [] SyS_ipc+0x154/0x3c0
  [] system_call+0x38/0xb4

  # dmsetup udevcookies
  Cookie   Semid  Value  Last semop time   Last change time
  0xd4d888a0  1  Tue Mar 22 20:53:55 2016  Tue Mar 22 
20:53:55 2016

  == Comment: #19 - Mauricio Faria De Oliveira - 2016-03-22 17:00:13 ==
  Command to create the LVM volumes on initramfs:

  # for sd in /sys/block/sd*; do sd="$(basename $sd)"; [ "$sd" = 'sda' ]
  && continue; lvm pvcreate /dev/$sd; lvm vgcreate vg-$sd /dev/$sd; lvm
  lvcreate --size 1000m --name lv-$sd vg-$sd; done

  # lvm vgdisplay | grep -c 'VG Name'
  50

  == Comment: #20 - Mauricio Faria De Oliveira - 2016-03-22 17:57:50 ==
  Hm, got a better picture of this:

  The problem doesn't seem to be a synchronization issue.
  I've learned a bit more about the udev events/cookies for sdX and lvm volumes.

  1) The sdX add events happen, for multiple devices.  
  Each device consumes 1 udev worker.

  2) The sdX add events run 'watershed .. vgchange -a y...'.
   If this detects an LVM volume in sdX, it will try  to activate it, and 
then block/wait for the respective LVM/udev cookie to complete (i.e., wait for 
the LVM dm-X device add event to finish)

  3) The dm-X device add event is fired from the kernel.

  4) There are no available udev workers to process it.
  The event processing remains queued.
  Thus, the cookie will not be released.

  5) No udev workers from sdX devices will finish, since all are waiting
  for cookies to be complete, which demand available udev workers.

  == Comment: #21 - Mauricio Faria De Oliveira - 2016-03-22 18:02:11 ==
  Got a confirmation of the previous hypothesis.

  Added the --noudevsync argument to the vgchange command in the initramfs's 
/lib/udev/rules.d/85-lvm2.rules.
  This causes vgchange not to wait for an udev cookie.

  Things didn't block, actually finished quite fast.

  == Comment: #23 - Mauricio Faria De Oliveira - 2016-03-22 18:14:41 ==
  Hi Canonical,

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Andreas Pokorny]

** Branch linked: lp:~andreas-pokorny/mir/fix-1549701

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

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

  The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
  The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.

  We could fix this by:
  - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
  - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
  - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

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

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

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

[mnoveli]

my ubuntu 16.04 betaa toten black screen video .mp4

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

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

Status in gstreamer1.0 package in Ubuntu:
  New

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

  Terminal says :

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

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

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

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

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

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

[mnoveli]

I have some problem  Totem can't play H264 on fresh 16.04 beta install
solution ?

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

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

Status in gstreamer1.0 package in Ubuntu:
  New

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

  Terminal says :

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

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

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

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

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

[Touch-packages] [Bug 1556412] Re: webappUrlPatterns does not work on multiple "radiofrance" sites

[Nicolas Delvaux]

@Alexandre: If you come by here again, I'm still interested by the way I
could inject JS in webapp-container. It would really help if you could
point me to a documentation or to an existing app source code :-)

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

Title:
  webappUrlPatterns does not work on multiple "radiofrance" sites

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Hi,

  I do not manage to confine my webapp on its site, the "--webappUrlPatterns" 
just seems to be ignored.
  I tested on Ubuntu 15.10 and on Mako (up-to-date rc-proposed).

  Test case 1 (working):
  Run "webapp-container --webappUrlPatterns=http://foo.org/* 
http://www.google.com/;
  → As expected, any link clicked on this page is opened in the Web browser (as 
no URL match the pattern)

  Test case 2 (failure):
  Run "webapp-container --webappUrlPatterns=http://foo.org/* 
http://www.fipradio.fr/player;
  → All URLs are opened in the webapp. I can go to twitter, facebook... 
anywhere.

  I have the same issue on other Radio France sites, like:
  * http://www.franceculture.fr/
  * http://www.mouv.fr/
  * http://www.francebleu.fr/

  Strangely enough, everything seems to work on:
  * http://www.francemusique.fr/
  * http://www.franceinter.fr/

  If it can help, I noticed strange things on http://www.franceinfo.fr/:
  At the bottom of the page, the Twitter, Facebook and Dailymotion links are 
opened in the webapp whereas the "radiofrance.fr" link is opened in the web 
browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: webapp-container 0.23+15.10.20150929-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 12 12:36:31 2016
  InstallationDate: Installed on 2015-10-19 (144 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151017)
  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/1556412/+subscriptions

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

[Touch-packages] [Bug 1516403] Re: Upper angles of window not curved

[varlesh]

It's problem tgk themes - Ambiance and Radiance. Because with Adwaita, Arc GTK 
and other not reproduced.
Please fix Ambiance and Radiance GTK Themes

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

Title:
  Upper angles of window not curved

Status in Unity:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  In Progress
Status in unity source package in Xenial:
  Fix Released

Bug description:
  Hallo
  The upper angles aren't curved as all the other windows, see attached 
screenshot.
  Best regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 15 17:21:04 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-11 (35 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151010)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1516403] Re: Upper angles of window not curved

[varlesh]

Bug not fixed!
Unity 7.4.0+16.04.20160322-0ubuntu1
Font Viewer attcached


** Attachment added: "preview"
   
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1516403/+attachment/4616322/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202016-03-29%2022-58-07.png

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

Title:
  Upper angles of window not curved

Status in Unity:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  In Progress
Status in unity source package in Xenial:
  Fix Released

Bug description:
  Hallo
  The upper angles aren't curved as all the other windows, see attached 
screenshot.
  Best regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 15 17:21:04 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-11 (35 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151010)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1382209] Re: [Enhancement] Add an API to adjust preferred surface orientation at runtime

[Michal Predotka]

I'm looking forward to this feature. I have an which displays moving
text. It would be great if a user could decide if she wants the text
displayed in portrait or landscape regardless of phone orientation and
if that orientation is locked or not.

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

Title:
  [Enhancement] Add an API to adjust preferred surface orientation at
  runtime

Status in Mir:
  Fix Released
Status in QtMir:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, applications are written to take advantage of the entire surface 
of screen. So they need a way to tell MIR, the orientation they want for 
drawing themselves. This can be portrait for some, landscape for others, or 
even combinations.
  Without this feature, portrait application get distorted when running in a 
landscape oriented device.

  So, it would be nice to have an API, in MIR client, to precisely lock
  the orientation of the MirSurface used for drawing.

  My use case is a full-screen game, that require always Portrait
  Orientation. Another is a full-screen game that requires always
  Landscape.

  Better (future):
  - allow this even for non full-screen applications
  - allow combination like Portait+PortraitUpsideDown, or 
LandscapeLeft+LandscapeRight
  - allow to change the orientation when the application run (so not only when 
creating/requesting the surface).

  Remarks :
  - touch event may need to be translated into the correct coordinates system!

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

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

[Touch-packages] [Bug 1563525] [NEW] Show low graphics on screen in ubuntu 14.04lts

[swopnil]

Public bug reported:

when i install ubuntu 14.04lts and do not install graphics driver then
show low graphics. HP probook 450 G1 is my pc. why show low graphics ?

please solve this problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Mar 30 01:43:57 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:1942]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] 
[1002:6600] (rev ff) (prog-if ff)
InstallationDate: Installed on 2016-03-29 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Hewlett-Packard HP ProBook 450 G1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=9c908313-118c-4aa9-8dbf-16c46f1c731d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L74 Ver. 01.08
dmi.board.name: 1942
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 89.10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL74Ver.01.08:bd02/13/2014:svnHewlett-Packard:pnHPProBook450G1:pvrA3008CD10003:rvnHewlett-Packard:rn1942:rvrKBCVersion89.10:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 450 G1
dmi.product.version: A3008CD10003
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Mar 30 01:37:40 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5564 
 vendor CMN
xserver.version: 2:1.17.1-0ubuntu3~trusty1

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


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

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

Title:
  Show low graphics on screen in ubuntu 14.04lts

Status in xorg package in Ubuntu:
  New

Bug description:
  when i install ubuntu 14.04lts and do not install graphics driver then
  show low graphics. HP probook 450 G1 is my pc. why show low graphics ?

  please solve this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Mar 30 01:43:57 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1942]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] 
[1002:6600] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-03-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP ProBook 450 G1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=9c908313-118c-4aa9-8dbf-16c46f1c731d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2014
  dmi.bios.vendor: 

[Touch-packages] [Bug 1561795] Re: Fullscreen Crash Intel GPU since Ubuntu 15.10

[Michael Kasprzak]

Sure thing. Downloading it now.

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

Title:
  Fullscreen Crash Intel GPU since Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ever since I upgraded to Ubuntu 15.10, I haven't been able to exit
  fullscreen without video crashing. There are rare cases when I've been
  able to safely exit, but more times than not, it doesn't. This is
  typically when I'm using Chrome to watch YouTube or Twitch video
  streams. The only way out is switch over and do a "killall -u myname".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:57:24 2016
  DistUpgraded: 2015-10-25 04:02:46,508 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2203]
  InstallationDate: Installed on 2015-01-03 (446 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=a630eb7a-a0ab-49aa-bdb6-8221ae278346 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-25 (151 days ago)
  dmi.bios.date: 09/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA0WW(2.60):bd09/12/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Mar 24 19:14:03 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1549701] Re: Sometimes devices don't suspend - display turns back on immediately

[Launchpad Bug Tracker]

** Branch linked: lp:~andreas-pokorny/mir/fix-1549701-0.21.0

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

Title:
  Sometimes devices don't suspend - display turns back on immediately

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  current build number: 267
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  it happens also on arale.

  sometimes the screen lock timeout is not honoured and the devices
  don't suspend when the lock timeout expires (display doesn' t turn
  off)

  $ sudo powerd-cli list
  [sudo] password for phablet:
  System State Requests:
    Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1

  Steps to reproduce on arale:

  1. Turn on the screen
  2. Touch the circular touch button at the lower part of the device
  3. Press/release the power button to turn off screen
  4. Release the circular touch button

  Expected results: The screen turns off and further on/off cycles work properly
  Actual results: The screen stays on and attempts to turn it off fail

  The touchscreen is handling the circular button and emits a key down event. 
When turning the screen of the touch screen device is turned off too. Mir is 
not aware of the touchscreen being off. So meanwhile the repeat handling kicks 
in and emits key events. This makes USC turn the screen back on again.
  The touchscreen driver does not notice that the circular button is still 
held. So still no release event is sent.

  We could fix this by:
  - fixing the touchscreen driver to release any touch contacts or buttons 
pressed, when the device is turned off (something the bluetooth stack seems to 
do on some devices)
  - sidestep the problem by making usc only react to press events as a wake 
trigger and make repeat and release events only reset the inactivity timer
  - give mir the knowledge that the disabled output also disables the 
touchscreen (a connection we need to be aware of to get the mapping of touch 
screen coordinates onto scene coordinates right), hence remove the device and 
thus turn of any repeat key handling attached to that device.

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

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

[Touch-packages] [Bug 1563354] Re: systemd-tmpfiles-setup.service fails after switching SELinux to enforcing

[Martin Pitt]

We don't support SELinux in Ubuntu (only AppArmor), and I'm afraid this
doesn't tell me anything. Can you please report this upstream directly
(https://github.com/systemd/systemd/issues), as most people there
actually use SELinux? Thanks!

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

Title:
  systemd-tmpfiles-setup.service fails after switching SELinux to
  enforcing

Status in systemd package in Ubuntu:
  New

Bug description:
  After switching SELinux to enforcing, the systemd-tmpfiles-
  setup.service failed:

  Mar 29 16:12:42  systemd-tmpfiles[546]: [/usr/lib/tmpfiles.d/var.conf:14] 
Duplicate line for path "/var/log", ignoring.
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/log: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/lib: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /home: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /srv: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/lib/systemd: Permission denied
  Mar 29 16:12:42  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/lib/systemd/coredump: Permission denied
  Mar 29 16:12:43  systemd-tmpfiles[546]: Unable to fix SELinux security 
context of /var/cache: Permission denied
  Mar 29 16:12:43  systemd[1]: systemd-tmpfiles-setup.service: Main process 
exited, code=exited, status=1/FAILURE
  Mar 29 16:12:43  systemd[1]: Failed to start Create Volatile Files and 
Directories.
  Mar 29 16:12:43  systemd[1]: systemd-tmpfiles-setup.service: Unit entered 
failed state.
  Mar 29 16:12:43  systemd[1]: systemd-tmpfiles-setup.service: Failed with 
result 'exit-code'.

  No further AVC or audit.log is logged. When manually setting
  'setenforce 0' and starting this service, it obviously works fine.

  My environment:

  # lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  (Build  / packages from last night)

  # apt-cache policy systemd
  systemd:
Installed: 229-3ubuntu1
Candidate: 229-3ubuntu1

  If you need more infos, please drop a short note.

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

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

[Touch-packages] [Bug 1563514] Re: [util-linux] lscpu: Fix model and model name on Power Systems

[Gary Gaydos]

** Package changed: ubuntu => util-linux (Ubuntu)

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

Title:
  [util-linux] lscpu: Fix model and model name on Power Systems

Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #5 - VASANT HEGDE  - 2016-03-29 01:17:15 
==
  Updated description : Please mirror this description and comment 1 (ignore 
original description).
  


  -Problem Description---
  lscpu: Fix model and model name on Power Systems
   
  Contact Information = hegdevas...@linux.vnet.ibm.com 
   
  ---uname output---
  Linux lep8d 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:06:23 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

   
  Machine Type = All Power System 
   
  ---Steps to Reproduce---
  - run lscpu on Ubuntu system and check for Model name and Model information.
it displays system model instead of processor model.

   
  Userspace tool common name: util-linux

  Userspace rpm: util-linux

  

 
  -Vasant


  
  == Comment: #1 - VASANT HEGDE  - 2016-03-28 11:38:39 
==
  Please pull below patches from upstream:

  commit 3ac03fe4d20558b55635a048d7f2fb0f5e85ee2a
  Author: Vasant Hegde 
  Date:   Mon Mar 14 20:18:07 2016 +0530

  lscpu: Fix model and model name on Power Systems
  
  On Power System, lspcu presently displays system model number instead of
  processor model name. 'model' tag in cpuinfo contains system model name,
  not processor model. Instead it uses 'cpu' tag for processor model name.
  Also it uses 'revision' tag for processor model.
  
  Fix lspcu so that it displays processor model number. Also display 
processor
  model name.

  
  commit 641350fe822e7f1ac10873dad9a364bdeaba8083
  Author: Karel Zak 
  Date:   Tue Mar 15 14:23:59 2016 +0100

  lscpu: keep lscpu usable on snapshots
  
  This patch reverts 3ac03fe4d20558b55635a048d7f2fb0f5e85ee2a for
  snapshots (--sysroot).


  commit 86c4817e0ea02656ddb62fe27757a9fd4f13b2d3
  Author: Ruediger Meier 
  Date:   Wed Mar 16 13:18:17 2016 +0100

  Revert "lscpu: keep lscpu usable on snapshots"


  commit c95e3889725389e9d7e24d29c2a71b015959575f
  Author: Ruediger Meier 
  Date:   Wed Mar 16 13:18:18 2016 +0100

  lscpu: use cpu and revision tag if available
  
  Avoid ifdef which does not work with --sysroot. Our existing test
  dumps produce even better output now for ppc and sparc.
  
  The logic moved to the printing section.

  
  -Vasant

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

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

[Touch-packages] [Bug 1563514] [NEW] [util-linux] lscpu: Fix model and model name on Power Systems

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #5 - VASANT HEGDE  - 2016-03-29 01:17:15 ==
Updated description : Please mirror this description and comment 1 (ignore 
original description).


-Problem Description---
lscpu: Fix model and model name on Power Systems
 
Contact Information = hegdevas...@linux.vnet.ibm.com 
 
---uname output---
Linux lep8d 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:06:23 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

 
Machine Type = All Power System 
 
---Steps to Reproduce---
- run lscpu on Ubuntu system and check for Model name and Model information.
  it displays system model instead of processor model.

 
Userspace tool common name: util-linux

Userspace rpm: util-linux


 
-Vasant



== Comment: #1 - VASANT HEGDE  - 2016-03-28 11:38:39 ==
Please pull below patches from upstream:

commit 3ac03fe4d20558b55635a048d7f2fb0f5e85ee2a
Author: Vasant Hegde 
Date:   Mon Mar 14 20:18:07 2016 +0530

lscpu: Fix model and model name on Power Systems

On Power System, lspcu presently displays system model number instead of
processor model name. 'model' tag in cpuinfo contains system model name,
not processor model. Instead it uses 'cpu' tag for processor model name.
Also it uses 'revision' tag for processor model.

Fix lspcu so that it displays processor model number. Also display processor
model name.


commit 641350fe822e7f1ac10873dad9a364bdeaba8083
Author: Karel Zak 
Date:   Tue Mar 15 14:23:59 2016 +0100

lscpu: keep lscpu usable on snapshots

This patch reverts 3ac03fe4d20558b55635a048d7f2fb0f5e85ee2a for
snapshots (--sysroot).


commit 86c4817e0ea02656ddb62fe27757a9fd4f13b2d3
Author: Ruediger Meier 
Date:   Wed Mar 16 13:18:17 2016 +0100

Revert "lscpu: keep lscpu usable on snapshots"


commit c95e3889725389e9d7e24d29c2a71b015959575f
Author: Ruediger Meier 
Date:   Wed Mar 16 13:18:18 2016 +0100

lscpu: use cpu and revision tag if available

Avoid ifdef which does not work with --sysroot. Our existing test
dumps produce even better output now for ppc and sparc.

The logic moved to the printing section.


-Vasant

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-139768 severity-high 
targetmilestone-inin---
-- 
[util-linux] lscpu: Fix model and model name on Power Systems
https://bugs.launchpad.net/bugs/1563514
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to util-linux 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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Joseph Salisbury]

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

-- 
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 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/ubuntu/+source/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 1563503] [NEW] splashscreen flickering

[Jppande]

Public bug reported:

the ubuntu splash screen flickers while startup. stops flickering when a
button is hit on the keyboard.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-67.87~14.04.1-generic 3.16.7-ckt24
Uname: Linux 3.16.0-67-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Mar 30 00:11:09 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0597]
InstallationDate: Installed on 2015-04-20 (344 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Dell Inc. Inspiron 3521
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-67-generic 
root=UUID=e6eee077-e095-4086-9d02-f5c1b831797b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0FXP6Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/19/2013:svnDellInc.:pnInspiron3521:pvrA10:rvnDellInc.:rn0FXP6Y:rvrA00:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Inspiron 3521
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Mar 29 23:03:24 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 939 
 vendor LGD
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


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

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

Title:
  splashscreen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  the ubuntu splash screen flickers while startup. stops flickering when
  a button is hit on the keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-67.87~14.04.1-generic 3.16.7-ckt24
  Uname: Linux 3.16.0-67-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar 30 00:11:09 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0597]
  InstallationDate: Installed on 2015-04-20 (344 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-67-generic 
root=UUID=e6eee077-e095-4086-9d02-f5c1b831797b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0FXP6Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/19/2013:svnDellInc.:pnInspiron3521:pvrA10:rvnDellInc.:rn0FXP6Y:rvrA00:cvnDellInc.:ct8:cvrA10:
  

[Touch-packages] [Bug 1562055] Re: unity8 black screen

[Martin Vysny]

Sorry, back to "can't run unity8": after the computer boots up, no
matter how much I press CTRL+ALT+F1-F12, nothing happens, the screen
stays completely blank.

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

Title:
  unity8 black screen

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I have installed the unity8-desktop-session-mir on a fully upgraded
  16.04. When I select the Unity8 session, type in the password and
  press Enter, the screen goes black and nothing happens. I tried to
  wait a minute, but nothing changed (there no mouse cursor either), so
  I have rebooted the computer. I have an older Intel onboard graphics,
  I'm not sure whether it is even supported by Mir or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160323.2-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: Fri Mar 25 16:43:49 2016
  InstallationDate: Installed on 2015-11-19 (127 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to xenial on 2016-03-23 (1 days ago)
  upstart.unity8-filewatcher.log:
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
  upstart.unity8.log:
   ()
   QXcbConnection: Could not connect to display

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

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

[Touch-packages] [Bug 1562055] Re: unity8 black screen

[Martin Vysny]

Oh, finally resolved this: while starring at the blank screen, waiting
for unity8 to start, I pressed CTRL+ALT+F8 and voila - the screen
suddenly shown the unity8 :-) Thank you.

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

Title:
  unity8 black screen

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  I have installed the unity8-desktop-session-mir on a fully upgraded
  16.04. When I select the Unity8 session, type in the password and
  press Enter, the screen goes black and nothing happens. I tried to
  wait a minute, but nothing changed (there no mouse cursor either), so
  I have rebooted the computer. I have an older Intel onboard graphics,
  I'm not sure whether it is even supported by Mir or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160323.2-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: Fri Mar 25 16:43:49 2016
  InstallationDate: Installed on 2015-11-19 (127 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to xenial on 2016-03-23 (1 days ago)
  upstart.unity8-filewatcher.log:
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
   Failed to open connection to "session" message bus: Failed to connect to 
socket /tmp/dbus-Ir9W603yS3: Connection refused
  upstart.unity8.log:
   ()
   QXcbConnection: Could not connect to display

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

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

[Touch-packages] [Bug 1508438] Re: Do not notify for events marked as not attending

[Charles Kerr]

The thing to do here is to get some sample input from an imported
calendar with "not attending" set so that (a) this ical can be used as
the basis for a regression test and (b) we can see how to test for this
state in engine-eds.cc.

Once we have that test in place the rest of implementation is trivial,
just don't call add_alarms_to_subtask() for components that have "not
attending" set.

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

Title:
  Do not notify for events marked as not attending

Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-up from bug #1371871. While it was marked as Fix
  Released, it doesn't seem to have had any effect. I'm reporting it as
  two separate bugs to reopen it now.

  I've got a few events in my calendar for meetings where I'm marked as
  not going, which I still want to see in my calendar unless I
  explicitly delete them.

  An example is a recurring event which I've got on my work calendar. During my 
holiday:
  - I'll mark myself as not attending
  - I will not delete the event
  - I don't expect to be notified

  As I'm not marked as attending, I wouldn't expect to get a reminder
  notification, even less if I'm in a different timezone and it's 3:00
  a.m. :)

  See bug 1508440 for the "display events not being attended clearly"
  part.

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

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

[Touch-packages] [Bug 1533681] Re: imported google calendar events sound when they shouldn't

[Charles Kerr]

Renato, thanks for working on some of the indicator-datetime backlog. =)

For this one, after the EDS engine collects all the alarms for an event,
it should cull out the ones that have neither an audio_url nor display
text, ie:

=== modified file 'src/engine-eds.cpp'
--- src/engine-eds.cpp  2016-02-03 16:33:39 +
+++ src/engine-eds.cpp  2016-03-29 17:53:12 +
@@ -960,7 +960,8 @@
 appointment.end = i.first.second;
 appointment.alarms.reserve(i.second.size());
 for (auto& j : i.second)
-appointment.alarms.push_back(j.second);
+if (!j.second.text.empty() || !j.second.audio_url.empty())
+appointment.alarms.push_back(j.second);
 subtask->task->appointments.push_back(appointment);
 }
 }

A few important notes:

1. I believe the clock app used to (and possibly still does?) write
empty valarms, so when testing this or any other fix you should confirm
that it doesn't break the clock. For backwards compatibility with
existing clock-app alarms, we may need indicator-datetime to inject an
Alarm if none is present for any event containing the "x-canonical-
alarm" tag.

2. Most of indicator-datetime's EDS tests were created with output from
clock-app, so new ical tests are needed to cover these other valarm
action types.

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

Title:
  imported google calendar events sound when they shouldn't

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Calendar App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I use the calendar-app with my work google calendar. For that calendar
  I have alarms setup to automatically send an email 24 hours, 4 hours
  and 30 minutes before any event and I choose email as the reminder (as
  opposed to popup) so that I wouldn't be bombarded with reminders all
  day. Unfortunately the calendar app does not make a distinction
  between email and popup and every event with an email reminder gets
  imported as an event that gets an event notification on the phone with
  an alarm sound. I have a lot of events in my calendar and so my phone
  is constantly making noise at all times of the day. This is
  particularly annoying at night time since I might get a reminder as
  early as 3am or 4am, which wakes me up. Of course, I could use silent
  mode at night, but, like last night, I forgot and was awoken at 6am.
  Plus, I don't necessarily want the phone in silent mode-- I'd like to
  be able to hear if a phone call comes in since that is likely an
  emergency call I need to take.

  There are a lot of different bugs related to calendar event
  notifications and if some of them were fixed, it would ameliorate this
  bug. For example, I've been hoping for a setting to disable sounds for
  just the calendar (whether via the app or system settings) but
  otherwise get calendar notifications. Being able to change the alarm
  sound to 'None' would work too. TBH at this point I don't care which
  bug is fixed, I need to get this phone to stop sounding off
  constantly.

  WORKAROUND:
  1. download https://commons.wikimedia.org/wiki/File:Silence.ogg to 
/home/phablet
  2. use gsettings to adjust the sound:
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/usr/share/sounds/ubuntu/ringtones/Marimbach.ogg'
  $ DISPLAY=:0.0 gsettings set com.canonical.indicator.datetime 
calendar-default-sound /home/phablet/Silence.ogg 
  $ DISPLAY=:0.0 gsettings get com.canonical.indicator.datetime 
calendar-default-sound
  '/home/phablet/Silence.ogg'

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

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

[Touch-packages] [Bug 1563481] Re: ubuntu-server should recommend lxd

[lightraven24]

*** This bug is a duplicate of bug 1563026 ***
https://bugs.launchpad.net/bugs/1563026

** This bug has been marked a duplicate of bug 1563026
   LXC/LXD installed by default on Ubuntu server

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

Title:
  ubuntu-server should recommend lxd

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-server should recommend the lxd package, not depend on it.

  While it is an interesting new technology, I would rather have one
  virtualization/container technology running on my server farms at the
  time without having to remove the ubuntu-server package on them.

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

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

[Touch-packages] [Bug 1563481] [NEW] ubuntu-server should recommend lxd

[lightraven24]

*** This bug is a duplicate of bug 1563026 ***
https://bugs.launchpad.net/bugs/1563026

Public bug reported:

ubuntu-server should recommend the lxd package, not depend on it.

While it is an interesting new technology, I would rather have one
virtualization/container technology running on my server farms at the
time without having to remove the ubuntu-server package on them.

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

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

Title:
  ubuntu-server should recommend lxd

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-server should recommend the lxd package, not depend on it.

  While it is an interesting new technology, I would rather have one
  virtualization/container technology running on my server farms at the
  time without having to remove the ubuntu-server package on them.

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

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

[Touch-packages] [Bug 1563287] Re: Right edge switcher stutters badly with only a few apps opened

[Omer Akram]

** Attachment added: "bad.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1563287/+attachment/4616181/+files/bad.mp4

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

Title:
  Right edge switcher stutters badly with only a few apps opened

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  tested on krillin and arale on rc-proposed.
  also I tried the fix for bug 1556763 but that's not related to this as well.

  The right edge switcher on both krillin and arale stutter when I drag
  it from the right edge and then swipe through the list of opened
  windows.

  This was not the case a few months ago, so we clearly regressed here.

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

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

[Touch-packages] [Bug 1563287] Re: Right edge switcher stutters badly with only a few apps opened

[Omer Akram]

Kevin: I just tested and its all good on last OTA (image 30), so the
delta is between then and now (rc-proposed). I have also attached the
video (second is being uploaded)

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

Title:
  Right edge switcher stutters badly with only a few apps opened

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  tested on krillin and arale on rc-proposed.
  also I tried the fix for bug 1556763 but that's not related to this as well.

  The right edge switcher on both krillin and arale stutter when I drag
  it from the right edge and then swipe through the list of opened
  windows.

  This was not the case a few months ago, so we clearly regressed here.

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

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

[Touch-packages] [Bug 1563287] Re: Right edge switcher stutters badly with only a few apps opened

[Omer Akram]

** Attachment added: "good.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1563287/+attachment/4616179/+files/good.mp4

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

Title:
  Right edge switcher stutters badly with only a few apps opened

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  tested on krillin and arale on rc-proposed.
  also I tried the fix for bug 1556763 but that's not related to this as well.

  The right edge switcher on both krillin and arale stutter when I drag
  it from the right edge and then swipe through the list of opened
  windows.

  This was not the case a few months ago, so we clearly regressed here.

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

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

[Touch-packages] [Bug 1563470] Re: systemd crashed with SIGABRT

[Apport retracing service]

*** This bug is a duplicate of bug 1547851 ***
https://bugs.launchpad.net/bugs/1547851

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1563470/+attachment/4616160/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd crashed with SIGABRT

Status in systemd package in Ubuntu:
  New

Bug description:
  The last started action was running unetbootin.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar 29 18:22:13 2016
  EcryptfsInUse: Yes
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2016-02-02 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120
   Bus 001 Device 002: ID 1532:001c Razer USA, Ltd RZ01-0036 Optical Gaming 
Mouse [Abyssus]
   Bus 001 Device 006: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /lib/systemd/systemd --user
  ProcEnviron:
   LANG=en_IE.UTF-8
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=619d6ee9-475a-42ed-9ea3-e46bf1b18748 ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 1: Failed to get properties: Failed to activate 
service 'org.freedesktop.systemd1': timed out
  Title: systemd crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Z170M Pro4S
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd08/13/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170MPro4S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1438910] Re: unable to set event as yearly or monthly

[Pat McGowan]

This is working in the latest app (you can add such events), but I
entered  bug #1563473 that the app hangs

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

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

Title:
  unable to set event as yearly or monthly

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu Calendar App:
  Fix Committed
Status in Ubuntu UX:
  Invalid
Status in qtorganizer5-eds package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  1. Open calendar
  2. Add a new event
  3. Mark it as "allday event"
  4. Set repeat to yearly or monthly
  5. Press the back arrow <

  Expected:
  it should go back to the calendar view

  Actual:
  Nothing happens

  I am using my Aquaris 4.5 with Ubuntu 14.10 r20, calendar 0.4.600.

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Gianmaria Scorza]

This is a tree of module on the latest kernel on my pc

/lib/modules/4.6.0-040600rc1-generic/kernel/sound/soc/intel $ tree
.
├── atom
│   ├── snd-soc-sst-mfld-platform.ko
│   └── sst
│   ├── snd-intel-sst-acpi.ko
│   ├── snd-intel-sst-core.ko
│   └── snd-intel-sst-pci.ko
├── boards
│   ├── snd-soc-skl_rt286.ko
│   ├── snd-soc-sst-bytcr-rt5640.ko
│   ├── snd-soc-sst-cht-bsw-max98090_ti.ko
│   ├── snd-soc-sst-cht-bsw-rt5645.ko
│   └── snd-soc-sst-cht-bsw-rt5672.ko
├── common
│   ├── snd-soc-sst-acpi.ko
│   ├── snd-soc-sst-dsp.ko
│   ├── snd-soc-sst-ipc.ko
│   └── snd-soc-sst-match.ko
└── skylake
├── snd-soc-skl-ipc.ko
└── snd-soc-skl.ko

5 directories, 15 files

-- 
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 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/ubuntu/+source/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 1440111] Re: [calendar] Reminder notifications are not integrated into system notifications

[Pat McGowan]

partial fix as described, carry forward

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

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

Title:
  [calendar] Reminder notifications are not integrated into system
  notifications

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  The calendar app does not use the standard notification system. You
  can't find it in the "Notifications" area of System Settings, and it
  uses its own notification sound regardless of what is set in "Sound".

  Also, reminders are not muted when the phone is in silent mode (I
  guess it's related).

  I'm on bq Aquaris, r20 and with the latest calendar-app.

  --- --- --- ---
  UX Comment:

  Calendar Notifications need to be overhauled:
  -- Calendar Notifications are displayed for too brief a period and should 
conform to the same timing as other notifications.

  -- Calendar Notifications are not currently appearing in the
  notification tray within indicators and should be.

  -- Calendar Notification title is misleading ('Alarm') and should make
  clear that the notification relates to a calendar event ('Event') and
  not a alarm-clock event.

  -- Calendar Notification's should NOT override silent mode (unlike
  clock-alarms) although the notification should still be displayed,
  appear in the notification within indicators and cause the device to
  vibrate (if enabled) - This is accepted/common behaviour for
  notifications of this type on mobile.

  Notifications Spec:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit

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

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

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

[Hangman]

In fact I can't play any other videos...

"Impossible de trouver le greffon requis

Vidéos nécessite d'installer un greffon pour lire les fichiers
multimédias du type suivant : DivX MPEG-4 Version 5 decoder"

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

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

Status in gstreamer1.0 package in Ubuntu:
  New

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

  Terminal says :

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

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

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

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

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

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[Colin Watson]

Edd, if you read up through this bug log you'll see a reference to bug
155, which has status on getting this sorted out for PPAs.  Please,
everyone, stop telling us about PPAs that are weakly signed; we know
about it, we're working on it, and further comments are not going to
make it happen any faster.

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

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The title pretty much says it all.

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

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

[Touch-packages] [Bug 1434517] Re: 480p and 1080p video appear to use the same bitrate

[Pat McGowan]

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

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

Title:
  480p and 1080p video appear to use the same bitrate

Status in Canonical System Image:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress
Status in libhybris package in Ubuntu:
  Confirmed

Bug description:
  I just recorded two 10 second videos of the the same object using my
  Nexus 4, one using the 1080p setting and the other 480p.  Both videos
  came out at roughly 8MB, each with approximately a 6.3 Mb/s video bit
  rate and 96 kb/s audio bit rate.

  This seems a bit weird to me: the only reason I can think of to offer
  multiple resolutions is to let the user pick the quality / storage
  space trade off they want.  If the lower resolution videos take up
  just as much space as the high resolution ones, then this doesn't make
  sense.

  I am running build 143 on a Nexus 4, which looks to have camera-app
  3.0.0.516 installed:

  current build number: 143
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-20 07:05:06
  version version: 143
  version ubuntu: 20150320
  version device: 20150210
  version custom: 20150320

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

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

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

[Alberto Aguirre]

@Peter, that would explain the behavior then.

"So, is this maybe a hardware defect? In a series of devices of the same
model?"

That's a possibility; A look at the proximity device driver and/or
sensor stack wouldn't hurt though...

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

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

Status in Canonical System Image:
  Incomplete
Status in powerd package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => backlog

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

Title:
  No keyboards shortcuts in QT apps

Status in appmenu-qt5:
  In Progress
Status in Canonical System Image:
  In Progress
Status in sni-qt:
  New
Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  In some apps built using QT4 & 5, menu shortcuts are greyed out and
  inoperant. Only alt and FKeys-based shortcuts work. Others, notably
  ctrl+c for copying, do not.

  This is quite serious ; mail me for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Gianmaria Scorza]

dmesg say :
[   12.270548] intel_sst_acpi 808622A8:00: No matching machine driver found 

there is 0x808622a8, but there isn't a driver for it

** Attachment added: "logdmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563110/+attachment/4616138/+files/logdmesg.txt

-- 
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 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/ubuntu/+source/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 1534807] Re: Cannot run "sudo chroot ." in Terminal

[Pat McGowan]

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

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

Title:
  Cannot run "sudo chroot ." in Terminal

Status in Canonical System Image:
  Fix Committed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  The Terminal app is being denied to exec the shell inside a chroot
  when attempting to run sudo chroot .:

  Jan 15 15:09:22 ubuntu-phablet kernel: [66337.301777] type=1400
  audit(1452888562.238:76): apparmor="DENIED" operation="exec"
  profile="com.ubuntu.terminal_terminal_0.7.140" name="/home/phablet
  /vivid-chroot/bin/bash" pid=30547 comm="chroot" requested_mask="x"
  denied_mask="x" fsuid=0 ouid=0

  It would be nice to fix this so that sudo chroot . will work, so that
  people can use a chroot to install additional console apps and tools,
  rather than using writable images, following the instructions on
  AskUbuntu at http://bit.ly/1RLv3g9

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

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