[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

[Daniel van Vugt]

** Changed in: qtmir (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

Status in qtmir package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4

  wheel mouse scrolling is too fast, tried with firefox and geany.

  run firefox on mir scroll up/down some random long page using the
  mouse wheel

  TEST CASE:

1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
2. Roll your mouse wheel over it and watch the log

  Expected: vscroll values of +1/-1
  Observed: vscroll values of +7/-7

  WORKAROUND:

  System Settings > Mouse & Touchpad >
  Slide the second (unlabelled) slider all the way left, and then one notch 
right.

  Turns out that unlabelled slider is the wheel scroll speed. Setting it
  one notch from the left correctly reduces the wheel speed from 7.0 to
  1.0 as Mir clients expect.

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

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

[Touch-packages] [Bug 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

[Daniel van Vugt]

** Description changed:

  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4
  
  wheel mouse scrolling is too fast, tried with firefox and geany.
  
  run firefox on mir scroll up/down some random long page using the mouse
  wheel
+ 
+ TEST CASE:
+ 
+   1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
+   2. Roll your mouse wheel over it and watch the log
+ 
+ Expected: vscroll values of +1/-1
+ Observed: vscroll values of +7/-7
+ 
+ WORKAROUND:
+ 
+ System Settings > Mouse & Touchpad >
+ Slide the second (unlabelled) slider all the way left, and then one notch 
right.
+ 
+ Turns out that unlabelled slider is the wheel scroll speed. Setting it
+ one notch from the left correctly reduces the wheel speed from 7.0 to
+ 1.0 as Mir clients expect.

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

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

Status in qtmir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 16.10 + proposed
  Xmir 2:1.18.4-1ubuntu4

  wheel mouse scrolling is too fast, tried with firefox and geany.

  run firefox on mir scroll up/down some random long page using the
  mouse wheel

  TEST CASE:

1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log mir_demo_client_egltriangle -- 
--desktop_file_hint=unity8
2. Roll your mouse wheel over it and watch the log

  Expected: vscroll values of +1/-1
  Observed: vscroll values of +7/-7

  WORKAROUND:

  System Settings > Mouse & Touchpad >
  Slide the second (unlabelled) slider all the way left, and then one notch 
right.

  Turns out that unlabelled slider is the wheel scroll speed. Setting it
  one notch from the left correctly reduces the wheel speed from 7.0 to
  1.0 as Mir clients expect.

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

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

[Touch-packages] [Bug 1604704] Re: [regression] GTK apps hang for a long time on start-up under Xmir (and less under native Mir) failing to find dbus

[Daniel van Vugt]

Confirmed in all cases it's just that the X11/Xmir apps can't detect the
session bus address of the login (which is on a different TTY BTW).
Forcing DBUS_SESSION_BUS_ADDRESS solves the problem.

Here are some stack traces of the hangs:

gedit:
(gdb) bt
#0  0x7705e853 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7477acd1 in g_spawn_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7477b313 in g_spawn_command_line_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x77862b70 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x778645f2 in g_dbus_address_get_for_bus_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7786f7ee in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7787522b in g_bus_get_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x7784b969 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8  0x778488f3 in g_application_register ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x7784918f in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#10 0x778494f2 in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#11 0x00400cfa in main ()

nautilus:
(gdb) bt
#0  0x734c9833 in __select_nocancel ()
at ../sysdeps/unix/syscall-template.S:84
#1  0x7418ecd1 in g_spawn_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7418f313 in g_spawn_command_line_sync ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x74729b70 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7472b5f2 in g_dbus_address_get_for_bus_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x747367ee in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7473c22b in g_bus_get_sync ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x74712969 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8  0x7470f8f3 in g_application_register ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x0042c78e in ?? ()
#10 0x7fffedd29e40 in ffi_call_unix64 ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#11 0x7fffedd298ab in ffi_call ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#12 0x7441fcf5 in g_cclosure_marshal_generic_va ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x7441f1d4 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x744394b8 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x7443a08f in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x74710168 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#17 0x747104f2 in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#18 0x0042ba31 in ?? ()
#19 0x733ed7e0 in __libc_start_main (main=0x42b970, argc=1, 
argv=0x7fffe5b8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe5a8)
at ../csu/libc-start.c:291
#20 0x0042ba99 in ?? ()

/usr/games/sol:
(gdb) bt
#0  0x7537556d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x70fdacf8 in _dbus_read ()
   from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2  0x70fde349 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3  0x70fd2c95 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4  0x70fd2b3a in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5  0x70fbd32f in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#6  0x70fb8e08 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x7fffedc925f6 in atspi_get_a11y_bus ()
   from /usr/lib/x86_64-linux-gnu/libatspi.so.0
#8  0x739e9052 in atk_bridge_adaptor_init ()
   from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0
#9  0x77117134 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#10 0x75f3dfa5 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x75f4ffc1 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x75f58d5c in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x75f5908f in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x75f424d4 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x75f44961 in g_object_notify ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x76de5778 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#17 0x75f3e1d4 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x75f589a6 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x75f59555 in g_signal_emit_by_name ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x76e0b6c5 in ?? () from 

[Touch-packages] [Bug 1604872] Re: Apps can't connect to the user's session bus, even though it exists

[Daniel van Vugt]

Even with the fix GTK apps under Xmir are hung trying to connect to the
wrong dbus address. Moved that to bug 1604704.

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

Title:
  Apps can't connect to the user's session bus, even though it exists

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Systemd user sessions makes telepathy unhappy because access to
  /run/user//bus is denied

  [Test Case]

  $ sudo apt install dbus-user-session empathy

  Restart the session (or reboot) and then start empathy:

  $ empathy

  In 16.04, you may need to set correctly DBUS_SESSION_BUS_ADDRESS
  before launching empathy:

  $ DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" empathy

  Without this bug fix, empathy fails with "Error contacting the account
  manager", and dmesg shows several denial messages like so:

  [ 63.960358] audit: type=1400 audit(1469458539.595:27):
  apparmor="DENIED" operation="connect" profile="/usr/lib/telepathy
  /mission-control-5" name="/run/user/1000/bus" pid=4563 comm="mission-
  control" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000

  [Regression Potential]

  None. The fix simply adds permissions to the dbus-session-strict
  abstraction. This change will not introduce any new AppArmor denials
  since policy is being loosened instead of being restricted.

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

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

[Touch-packages] [Bug 1603904] Re: X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start

[Daniel van Vugt]

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

I'm making this a duplicate of bug 1604704 now which is clearer.

The fix for bug 1604872 has not solved it.

** This bug is no longer a duplicate of bug 1604872
   Apps can't connect to the user's session bus, even though it exists

** This bug has been marked a duplicate of bug 1604704
   [regression] GTK apps hang for a long time on start-up under Xmir (and less 
under native Mir) failing to find dbus

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

Title:
  X apps that use dbus (GTK, Firefox) either don't start or take a very
  long time to start

Status in Libertine:
  New
Status in dbus package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  ubuntu 16.10 + proposed / unity8 - desktop x86

  libertine apps don't work anymore
  attached are firefox and nautilus logs

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

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

[Touch-packages] [Bug 1604704] Re: [regression] GTK apps hang for a long time on start-up under Xmir (and less under native Mir) failing to find dbus

[Daniel van Vugt]

The yakkety fix for bug 1604872 has not solved this. So no longer a
duplicate.

** This bug is no longer a duplicate of bug 1604872
   Apps can't connect to the user's session bus, even though it exists
** This bug has been marked a duplicate of bug 1603904
   X apps that use dbus (GTK, Firefox) either don't start or take a very long 
time to start

** This bug is no longer a duplicate of bug 1603904
   X apps that use dbus (GTK, Firefox) either don't start or take a very long 
time to start

** Changed in: dbus (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [regression] GTK apps hang for a long time on start-up under Xmir (and
  less under native Mir) failing to find dbus

Status in dbus package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  $ /usr/games/sol

  (sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
  Failed to connect to socket /tmp/dbus-7diijTV1R5: Connection refused
  GConf Error: No D-BUS daemon running

  
  (sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
  Failed to connect to socket /tmp/dbus-Zlu4hiB92O: Connection refused
  GConf Error: No D-BUS daemon running

  
  $ nautilus

  (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
  Unable to connect to session bus: Could not connect: Connection
  refused

  (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
  Unable to connect to session bus: Could not connect: Connection
  refused

  (nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
  Unable to connect to session bus: Could not connect: Connection
  refused

  (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Could not connect: Connection refused

  (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Could not connect: Connection refused

  (nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Could not connect: Connection refused

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

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

[Touch-packages] [Bug 1555568] Re: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant cracking sound, even when idel (no media playback). Muting and unmuting the sound seems to help

[mtvoid]

I have tried that earlier. In my case, I can set Internal Mic, Headset
Mic, or Headphone Mic as the Capture source. The hiss does not go away
when it is set to Internal or Headset Mic. When I set it to Headphone
Mic, it stops, but so does all sound output, so it does not work for me.

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

Title:
  [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant
  cracking sound, even when idel (no media playback). Muting and
  unmuting the sound seems to help for around half a minute...

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound constantly cracking, even when not playing any media. Muting and 
unmuting solves the problem for less than a minute. 
  Running kernel 4.4.4, but the problem was still present on the factory Ubuntu 
15.10 installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.4-040404-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseny 1639 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 10 13:22:09 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P96YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/13/2015:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn0P96YG:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Inspiron 11 - 3147
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1607470] Re: LightDM (in locked state) shows desktop if I try to change keyboard layout

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

** Summary changed:

- LightDM (in locked state) shows desktop if I try to change keyboard layout
+ Screenlock shows desktop if I try to change keyboard layout

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

Title:
  Screenlock shows desktop if I try to change keyboard layout

Status in unity package in Ubuntu:
  New

Bug description:
  This bug is related to bug#1606555. But this is also a security and
  privacy threat.

  release of Ubuntu: Ubuntu 16.04

  What's happening:

  I lock my machine(Super + L key)
  LightDM greeter is showing.
  If I push hotkey to change keyboard layout, LightDM flashes and then it shows 
my desktop for a second. 
  It's a privacy risk.

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

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

[Touch-packages] [Bug 1605117] Re: LightDM tray items disappear after logout

[Robert Ancell]

I've made a release with just this change (1.18.2-0ubuntu2).

** Changed in: lightdm
   Status: Confirmed => Fix Committed

** Changed in: lightdm
Milestone: None => 1.18.3

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

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

** Description changed:

- LightDM tray items disappear after logout
+ [Impact]
+ Unity Greeter indications don't show second time greeter started.
  
- Steps to reproduce:
- 1) install latest LightDM updates (reboot)
- 2) login
- 3) logout
+ [Test Case]
+ 1. Log in with greeter
+ 2. Log out
  
- Downgrading to LightDM 1.18.1-0ubuntu1 fix problem
+ Expected result:
+ Unity greeter is shown with all UI elements as in step 1.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: lightdm 1.18.2-0ubuntu1
- ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
- Uname: Linux 4.4.0-31-generic i686
- ApportVersion: 2.20.1-0ubuntu2.1
- Architecture: i386
- CurrentDesktop: Unity
- Date: Thu Jul 21 10:57:44 2016
- InstallationDate: Installed on 2016-05-23 (58 days ago)
- InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
- SourcePackage: lightdm
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Observed result:
+ Unity greeter is shown but only one indicator shows (accessibility)
+ 
+ [Regression potential]
+ Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

** Description changed:

  [Impact]
- Unity Greeter indications don't show second time greeter started.
+ Unity Greeter indicatiors don't show second time greeter started.
  
  [Test Case]
  1. Log in with greeter
  2. Log out
  
  Expected result:
  Unity greeter is shown with all UI elements as in step 1.
  
  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)
  
  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

** Description changed:

  [Impact]
- Unity Greeter indicatiors don't show second time greeter started.
+ Unity Greeter indicators don't show second time greeter started.
  
  [Test Case]
  1. Log in with greeter
  2. Log out
  
  Expected result:
  Unity greeter is shown with all UI elements as in step 1.
  
  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)
  
  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

** Summary changed:

- LightDM tray items disappear after logout
+ Unity greeter indicators don't show on second launch

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

Title:
  Unity greeter indicators don't show on second launch

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Unity Greeter indicators don't show second time greeter started.

  [Test Case]
  1. Log in with greeter
  2. Log out

  Expected result:
  Unity greeter is shown with all UI elements as in step 1.

  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)

  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

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

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

[Touch-packages] [Bug 1582979] Re: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[cltien]

I just used 15% of my root directory, where the /boot resides. This
shouldn't be a failure caused by disk space.

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

Title:
  package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Just happened after software update, I did not restart, instead, I
  powered off and powered on the next day.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue May 17 23:32:21 2016
  DuplicateSignature: 
package:linux-image-3.16.0-71-generic:3.16.0-71.92~14.04.1:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2015-12-06 (163 days ago)
  InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1607431] Re: Blurry icons and bad quality text on external monitor

[Daniel van Vugt]

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

Thanks for your bug report.

You will first need to fix your TV settings as that will make everything blurry 
on your screen
 -> bug 1607445

Second, we have known issues with the quality of font rendering so I'll
make this a duplicate of that bug.

** This bug has been marked a duplicate of bug 1536751
   Font/text rendering is irregular and not pixel-aligned on low DPI screens

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

Title:
  Blurry icons and bad quality text on external monitor

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hey,

  I use M10 FHD tablet with OTA-12 and when I connect it to the external
  HD monitor (23") the icons in the left panel are a bit blurry and the
  title of the window and the icons on the top panel are really low
  quality (you can even see bitmap dots). I presume that this is still a
  work to do and probably that is not a priority at the moment. But
  still.

  Thanks

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

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

[Touch-packages] [Bug 1607427] Re: super key not showing scopes home

[Daniel van Vugt]

Weird. I did a Super key fix in Mir recently however AFAIK that
regression both occurred and was fixed between releases and never made
it onto any devices.

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

Title:
  super key not showing scopes home

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hey,

  if I press super key, the scopes home does not appear. In OTA-11 it
  worked as it should, but in OTA-12 it doesn't work.

  I use M10 FHD tablet with OTA-12 and external keyboard Logitech k810.

  Thanks

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

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

[Touch-packages] [Bug 1584601] Re: Mir fails to build in: COMPOSITOR_TRACE_CALL

[Daniel van Vugt]

Fix committed to lp:mir/0.23 at revision 3528, scheduled for release in
Mir 0.23.5

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

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

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

Title:
  Mir fails to build in: COMPOSITOR_TRACE_CALL

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Committed
Status in mir package in Ubuntu:
  New

Bug description:
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/compositor_report.cpp:30:1:
 error: use of GNU statement expression extension 
[-Werror,-Wgnu-statement-expression]
  13:08:37 COMPOSITOR_TRACE_CALL(started)
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/compositor_report.cpp:28:37:
 note: expanded from macro 'COMPOSITOR_TRACE_CALL'
  13:08:37 #define COMPOSITOR_TRACE_CALL(name) 
MIR_LTTNG_VOID_TRACE_CALL(CompositorReport, mir_server_compositor, name)
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/lttng_utils.h:28:9:
 note: expanded from macro 'MIR_LTTNG_VOID_TRACE_CALL'
  13:08:37 mir_tracepoint(comp, name, 0);   \
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/include/common/mir/report/lttng/mir_tracepoint.h:22:32:
 note: expanded from macro 'mir_tracepoint'
  13:08:37 #define mir_tracepoint(c, ...) tracepoint(c, __VA_ARGS__)
  13:08:37^
  13:08:37 note: (skipping 1 expansions in backtrace; use 
-fmacro-backtrace-limit=0 to see all)
  13:08:37 /usr/include/lttng/tracepoint.h:50:15: note: expanded from macro 
'tracepoint_enabled'
  13:08:37 
caa_unlikely(CMM_LOAD_SHARED(__tracepoint_##provider##___##name.state))
  13:08:37  ^
  13:08:37 /usr/include/urcu/system.h:35:3: note: expanded from macro 
'CMM_LOAD_SHARED'
  13:08:37 ({  \
  13:08:37  ^

  
  --- or ---

  
  13:13:56 /usr/bin/cmake -E cmake_progress_report 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/obj-arm-linux-gnueabihf/CMakeFiles 
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp: In 
member function 'virtual void mir::report::lttng::CompositorReport::started()':
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp:30:87: 
error: ISO C++ forbids braced-groups within expressions [-Werror=pedantic]
  13:13:56  COMPOSITOR_TRACE_CALL(started)
  13:13:56  
  ^
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp: In 
member function 'virtual void mir::report::lttng::CompositorReport::stopped()':
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp:31:87: 
error: ISO C++ forbids braced-groups within expressions [-Werror=pedantic]
  13:13:56  COMPOSITOR_TRACE_CALL(stopped)
  13:13:56

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

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

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

[Daniel van Vugt]

I see no evidence or history of work on this topic in the Mir code.
Please clarify if there were any code changes for it in Mir 0.24.0

** Changed in: mir
   Status: Fix Committed => Incomplete

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

Title:
  AltGr not working on external keyboards

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

Bug description:
  Using my keyboard with Spanish layout:

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

  Extra info:

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

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

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

[Touch-packages] [Bug 1590515] Re: AltGr composed keys don't work in the browser content

[Daniel van Vugt]

In bug 1565236 I'm not yet convinced that if a Mir fix is required or
exists that we have released it yet. That fix was targeted for Mir
0.24.0 which is not released yet. But also there's no concrete evidence
of a Mir fix existing either.

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

Title:
  AltGr composed keys don't work in the browser content

Status in qtubuntu package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  As the title says. Those keys work fine in the address bar, but not in
  any text fields inside the website. With a german layout I can't type
  things like ~ \ { } [ ] etc.

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

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

[Touch-packages] [Bug 1607445] Re: Zoom is not correct when using HD monitor

[Daniel van Vugt]

TVs are usually set up to chop off the edges of the image they get by
default(!). I've found this is almost always true with mine.

You need to go into your TV/monitor settings and tell it to display
images at full size, and not crop the edges.

** Changed in: mir (Ubuntu)
   Status: New => 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/1607445

Title:
  Zoom is not correct when using HD monitor

Status in mir package in Ubuntu:
  Invalid

Bug description:
  Hey,

  I use M10 FHD tablet with OTA-12 and when I connect it to the external HD 
monitor, the zoom is not correct. I cannot see the any of the border (top 
panel, launcher,...). But this only happens with some of the monitors.
  One of the monitors that doesn't work correct is Samsung SyncMaster 2333HD. 
Maybe because it's also a tv tuner?

  Thanks

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

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

[Daniel van Vugt]

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

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

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

** Changed in: mir (Ubuntu)
   Importance: Undecided => Critical

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

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

  Extra info:

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

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

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

[Touch-packages] [Bug 1607450] Re: Scroling in the scope goes untill the end of the page

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1556795, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1556795
   Mouse wheel scrolling keeps going inertially (past the location I want to 
scroll to)

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

Title:
  Scroling in the scope goes untill the end of the page

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hey,

  I use M10 FHD tablet with OTA-12 and sometimes I use it with mouse. When I 
scroll it down in my home scope it automatically goes untill the end of the 
scope. So if I need an app that is in the middle of the list, I have to click, 
hold and move mouse.
  It could be like that if I scroll it a little bit, it goes down just a bit.

  Thanks

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

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

[Touch-packages] [Bug 1607185] Re: It's difficult to close the launcher without tapping on something you didn't want to

[Daniel van Vugt]

No you can't. I mentioned in the bug description; on krillin the
launcher is too small to be able to do that with a finger.

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

Title:
  It's difficult to close the launcher without tapping on something you
  didn't want to

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

Bug description:
  It's difficult to close the launcher without tapping on something you
  didn't want to.

  Test case:
1. Open an app.
2. Open the launcher swiping from the left.
3. Close the launcher without triggering any touches in the app.

  Expected: Tapping outside the launcher will close it without touches reaching 
the app.
  Observed: Tapping outside the launcher closes it but unwanted touches reach 
the app.

  You can close the launcher by swiping it back off the side, but it's
  too small to do that very easily without also accidentally touching
  the top-most app.

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

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

Re: [Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

[Fritz Hudnut]

On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel 
wrote:

> In the meantime you could try to get one of the other drivers
>> "modesetting", "fbdev", "fbdevhw" to work with 24 bit depth. You can use
>> my xorg.conf as starting point and edit it manually. Just put it in
>> /etc/X11.
>>
>
> So, I tried the -configure and that failed.  Then I wrote the xorg.conf
> out as per your suggestion using "modesetting" . . . didn't seem to work;
> changed it to "fbdevhw" didn't seem to work.  Trying to "rm r128" and said
> "File not found."
>

My xorg.conf file, see anything wrong with it??  Still booting to black
screen--here I'm in "live" DVD and I copied the xorg.conf file:

Section   "Device"
  Identifier  "Card0"
  Driver  "fbdevhw"
EndSection

Section   "Monitor"
  Identifier  "Monitor0"
EndSection

Section   "Screen"

  Identifier "Screen0"
  Device "Card0"
  Monitor"Monitor0"
  DefaultDepth 24
  SubSection  "Display"
 Viewport   0 0
 Depth  24
 Modes "1024 x 768"
  EndSubSection
EndSection

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

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Adam Conrad]

Marking v-done, based on IRC feedback.

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

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577735] Re: Add missing SKL/BXT PCI-ID's

[Launchpad Bug Tracker]

This bug was fixed in the package libdrm - 2.4.67-1ubuntu0.14.04.1

---
libdrm (2.4.67-1ubuntu0.14.04.1) trusty; urgency=medium

  * Backport xenial package to trusty.
  * Adjust revert-65041c4a1.diff to only keep drmAllocCopy, though it
has never been in the header file and not part of API.

libdrm (2.4.67-1ubuntu0.16.04.1) xenial; urgency=medium

  * Add missing SKL/BXT pci-id's (LP: #1577735)

libdrm (2.4.67-1) unstable; urgency=medium

  * New upstream release.
  * patches: Refreshed.
  * libdrm-amdgpu1.symbols: Updated.

libdrm (2.4.66-2) unstable; urgency=medium

  * Update libdrm-exynos1.symbols and shlibs.

libdrm (2.4.66-1) unstable; urgency=medium

  * New upstream release.
  * Update symbols file and bump shlibs for libdrm2.
  * Update libdrm-intel1.symbols and shlibs.
  * Update libdrm-nouveau2.symbols and shlibs.
  * Drop obsolete Replaces from pre-wheezy.
  * Add myself to Uploaders.

libdrm (2.4.65-3) unstable; urgency=medium

  * rules: Bump freedreno shlib back to 2.4.65.

libdrm (2.4.65-2) unstable; urgency=medium

  [ Andreas Boll ]
  * Update libdrm-freedreno1.symbols and shlibs.
  * Drop Debian revision from new symbols in libdrm2.symbols.

  [ Fathi Boudra ]
  * Enable freedreno build on arm64 architecture.

libdrm (2.4.65-1) unstable; urgency=medium

  [ Andreas Boll ]
  * New upstream release.
  * Update debian/upstream/signing-key.asc.
  * Update symbols file and bump shlibs for libdrm2.
  * Enable libdrm-amdgpu1 on kfreebsd-*.
  * Fix Vcs-* fields.
  * Add upstream url.

 -- Timo Aaltonen   Tue, 03 May 2016 14:16:48 +0300

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

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

Title:
  Add missing SKL/BXT PCI-ID's

Status in libdrm package in Ubuntu:
  Fix Released
Status in libdrm source package in Trusty:
  Fix Released
Status in libdrm source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Some Skylake/Broxton GPU PCI-ID's are missing from libdrm, these need
  to be added.

  [Test case]

  own such hw, run a desktop session and check that it's using native
  drivers

  [Regression potential]

  none

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Launchpad Bug Tracker]

This bug was fixed in the package libxrandr - 2:1.5.0-1~trusty1

---
libxrandr (2:1.5.0-1~trusty1) trusty; urgency=medium

  * Backport for lts-xenial stack. (LP: #1577734)

 -- Timo Aaltonen   Tue, 03 May 2016 16:25:01 +0300

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

** Changed in: llvm-toolchain-3.8 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577734] Update Released

[Adam Conrad]

The verification of the Stable Release Update for x11proto-randr has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1568485] Re: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.5

---
isc-dhcp (4.2.4-7ubuntu12.5) trusty; urgency=medium

  * debian/apparmor-profile.dhclient: Add the attach_disconnected flag to 
prevent
disconnected path denials (LP: #1568485).

 -- Jorge Niedbalski   Fri, 15 Apr 2016
14:44:06 +0200

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Released
Status in isc-dhcp source package in Wily:
  Invalid

Bug description:
  Get this logged on a fully upgraded 64 desktop (proposed archive
  enabled)

  kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log"
  pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0
  ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr 10 12:23:56 2016
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Launchpad Bug Tracker]

This bug was fixed in the package x11proto-randr - 1.5.0-1~trusty1

---
x11proto-randr (1.5.0-1~trusty1) trusty; urgency=medium

  * Backport for lts-xenial stack. (LP: #1577734)

 -- Timo Aaltonen   Tue, 03 May 2016 16:41:48 +0300

** Changed in: x11proto-randr (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Launchpad Bug Tracker]

This bug was fixed in the package llvm-toolchain-3.8 -
1:3.8-2ubuntu3~trusty4

---
llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty4) trusty; urgency=medium

  * rules, libllvmX.Y.{links,install}.in: Rename libllvm3.8 to
libllvm3.8v4.

llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty3) trusty; urgency=medium

  * control: Rename libllvm3.8 to libllvm3.8v4 so upgrades to xenial
work.

llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty2) trusty; urgency=medium

  * Drop the libjsoncpp-dev Build-Depend, as it's in universe in trusty.

llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty1) trusty; urgency=medium

  * Backport to trusty. (LP: #1577734)
  * clang-X.Y.install.in: Drop cmake files, cmake in trusty is too old.

 -- Adam Conrad   Wed, 29 Jun 2016 21:20:51 -0600

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Released
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Released
Status in x11proto-core source package in Trusty:
  Invalid
Status in x11proto-randr source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1588126] Re: [regression] [OTA-11] Adding new wifi networks (with long passwords) never connect at all since OTA-11

[Tony Espy]

The fix is currently in silo 005, and was just marked 'Lander Approved'.

The version containing the fix will be 1.2.2-0ubuntu1~xenial3, and
should hopefully land in the next few days.


** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [regression] [OTA-11] Adding new wifi networks (with long passwords)
  never connect at all since OTA-11

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

  Also, forcefully flashing a device with OTA-10 fixes the problem. The
  regression began in OTA-11.

  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

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

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

[Touch-packages] [Bug 1559731] Re: Battery indicator turns red at 30% on desktop

[Anita Kuno]

It appears the solution to my problem was to use the dconf-editor and
set org.settings-daemon.plugins.power.critical-battery-action to
nothing. My laptop currently displays 19% battery life and continues to
work. Thanks, Anita.

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

Title:
  Battery indicator turns red at 30% on desktop

Status in Canonical System Image:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  Fix Committed

Bug description:
  The indicator turns red as soon as battery goes 30%

  Please refer to the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 20:43:32 2016
  InstallationDate: Installed on 2016-03-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1607552] Re: Blue dots for highlighting a text/cursor control can not be placed over the cursor

[Launchpad Bug Tracker]

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

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

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

Title:
  Blue dots for highlighting a text/cursor control can not be placed
  over the cursor

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

Bug description:
  Just because we cover everything with the finger and are unable to
  place the cursor where we want to. Correct is a BIG raindrop(Android)
  >under< the cursor so that we can put the finger on a blue control
  point and precisely put the cursor where we want to. On Ubuntu Touch:
  Mission impossible!

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

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

[Touch-packages] [Bug 1588994] Re: Location not working since OTA-11 on BQ 4.5

[Tony Pursell]

I think you may be right, Henry.  I went out on a walk along a country
lane this afternoon and decided to try out uNav.  I don't think that app
expects the device to have a location to hand to it when it starts. Your
press an icon in the header to determine you current location, and it
worked. As I walked up the lane my position changed automatically.  I
then found that Google and Here maps showed up my location automatically
on start up without complaining.  Nearby scope also began to work.

So is all well?  Probably, but location is a bit flaky.  I did a restart
and initially Google maps complained that location wasn't working, but
in a minute or two it came up with my location without any further
action on my part.  Nearby scope needed a refresh for it to find me.
So, grudgingly, I'm going to say that location is working (although not
as seamlessly as on my Android phone).

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

Title:
  Location not working since OTA-11 on BQ 4.5

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Since installing OTA-11 Google maps reports 'Google maps could not
  determine your precise location' and Here maps says 'Can't find your
  location'.

  Location detection is ON.

  'Using GPS, anonymised Wi-Fi and mobile network info' is selected in
  Location settings.

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

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

[Touch-packages] [Bug 1607552] Re: Blue dots for highlighting a text/cursor control can not be placed over the cursor

[GTriderXC]

The photos above are a bit big. You have to scroll them.

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

Title:
  Blue dots for highlighting a text/cursor control can not be placed
  over the cursor

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

Bug description:
  Just because we cover everything with the finger and are unable to
  place the cursor where we want to. Correct is a BIG raindrop(Android)
  >under< the cursor so that we can put the finger on a blue control
  point and precisely put the cursor where we want to. On Ubuntu Touch:
  Mission impossible!

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

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

[Touch-packages] [Bug 1607552] Re: Blue dots for highlighting a text/cursor control can not be placed over the cursor

[GTriderXC]

** Attachment added: "image20160729_001833810.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1607552/+attachment/4708988/+files/image20160729_001833810.jpg

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

Title:
  Blue dots for highlighting a text/cursor control can not be placed
  over the cursor

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

Bug description:
  Just because we cover everything with the finger and are unable to
  place the cursor where we want to. Correct is a BIG raindrop(Android)
  >under< the cursor so that we can put the finger on a blue control
  point and precisely put the cursor where we want to. On Ubuntu Touch:
  Mission impossible!

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

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

[Touch-packages] [Bug 1607552] Re: Blue dots for highlighting a text/cursor control can not be placed over the cursor

[GTriderXC]

** Attachment added: "image20160729_001827714.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1607552/+attachment/4708987/+files/image20160729_001827714.jpg

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

Title:
  Blue dots for highlighting a text/cursor control can not be placed
  over the cursor

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

Bug description:
  Just because we cover everything with the finger and are unable to
  place the cursor where we want to. Correct is a BIG raindrop(Android)
  >under< the cursor so that we can put the finger on a blue control
  point and precisely put the cursor where we want to. On Ubuntu Touch:
  Mission impossible!

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

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

[Touch-packages] [Bug 1607552] [NEW] Blue dots for highlighting a text/cursor control can not be placed over the cursor

[GTriderXC]

Public bug reported:

Just because we cover everything with the finger and are unable to place
the cursor where we want to. Correct is a BIG raindrop(Android) >under<
the cursor so that we can put the finger on a blue control point and
precisely put the cursor where we want to. On Ubuntu Touch: Mission
impossible!

** Affects: ubuntu-ui-toolkit (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-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1607552

Title:
  Blue dots for highlighting a text/cursor control can not be placed
  over the cursor

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

Bug description:
  Just because we cover everything with the finger and are unable to
  place the cursor where we want to. Correct is a BIG raindrop(Android)
  >under< the cursor so that we can put the finger on a blue control
  point and precisely put the cursor where we want to. On Ubuntu Touch:
  Mission impossible!

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

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

[Touch-packages] [Bug 1555568] Re: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant cracking sound, even when idel (no media playback). Muting and unmuting the sound seems to help

[Paulo Zúñiga]

Hi!, I have the same computer model, and activate the "headset mic" in
alsamixer fix the problem (sorry for my English).

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

Title:
  [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Has constant
  cracking sound, even when idel (no media playback). Muting and
  unmuting the sound seems to help for around half a minute...

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound constantly cracking, even when not playing any media. Muting and 
unmuting solves the problem for less than a minute. 
  Running kernel 4.4.4, but the problem was still present on the factory Ubuntu 
15.10 installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.4-040404-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseny 1639 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 10 13:22:09 2016
  InstallationDate: Installed on 2016-03-04 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Inspiron 11 - 3147, Realtek ALC3234, Speaker, Internal] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P96YG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd11/13/2015:svnDellInc.:pnInspiron11-3147:pvr:rvnDellInc.:rn0P96YG:rvrA00:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Inspiron 11 - 3147
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1607217] Re: QSysInfo doesn't work properly with AppArmor confinement

[Launchpad Bug Tracker]

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

** Changed in: qtsystems-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  QSysInfo doesn't work properly with AppArmor confinement

Status in qtsystems-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Trying to detect platform (OS) name and version on Ubuntu Touch 15.04
  based phones and tablets using QML. On the Ubuntu Desktop QSysInfo
  provides the following _correct_ values:

  QSysInfo::productType(): "ubuntu"
  QSysInfo::productVersion(): "16.04"
  QSysInfo::prettyProductName(): "Ubuntu 16.04 LTS"

  However, in a confined environment (e.g. bq Aquaris E5 HD Ubuntu
  Edition / 15.04 OTA-11) the following _incorrect_ values are provided
  by QSysInfo:

  QSysInfo::productType(): "unknown"
  QSysInfo::productVersion(): "unknown"
  QSysInfo::prettyProductName(): "Linux 3.4.67"

  I suppose it's because QSysInfo tries to (or would need to) access
  such files on the filesystem that are blocked by AppArmor, like /etc
  /os-release or such.

  Ideally, QSysInfo::productVersion() should return not only "15.04" on
  an Ubuntu Touch device, but also the OTA release number. So it should
  be more like: "15.04 OTA-11". That's because "15.04" alone doesn't
  tell much about the actual Ubuntu Touch OS release installed on a
  mobile device.

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

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

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

[Jyoti]

I am a Ubuntu supporter and was one of the first to buy the Ubuntu BQ
M10 tablet. We, the Portuguese speaking supporters were surprised that
was not possible to write in PORTUGUESE with the EXTERNAL KEYBOARD. We
were assured that this issue would be resolved soon. But… it's been
months and several OTAs and we still can not write Â, Ã, Á, À, Õ,
etc…This problem makes it impossible at all to use the tablet that we
bought in desktop mode.

Me, and all the people in Portugal who bought the Ubuntu tablet are very
tired of all this situation, we are on the edge. Many of us are thinking
about returning the tablet due to this fatal problem that has never been
solved, despite promises. Canonical is not interested in the Portuguese
users, this is the conclusion for many of us...

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

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

  Extra info:

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

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

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

[Jyoti]

I am a Ubuntu supporter and was one of the first to buy the Ubuntu BQ
M10 tablet. We, the Portuguese speaking supporters were surprised that
was not possible to write in PORTUGUESE with the EXTERNAL KEYBOARD. We
were assured that this issue would be resolved soon. But… it's been
months and several OTAs and we still can not write Â, Ã, Á, À, Õ,
etc…This problem makes it impossible at all to use the tablet that we
bought in desktop mode.

Me, and all the people in Portugal who bought the Ubuntu tablet are very
tired of all this situation, we are on the edge. Many of us are thinking
about returning the tablet due to this fatal problem that has never been
solved, despite promises. Canonical is not interested in the Portuguese
users, this is the conclusion for many of us...

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

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

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

  Extra info:

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

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[GTriderXC]

** Attachment added: "screenshot20160728_155621480.png"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708954/+files/screenshot20160728_155621480.png

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

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

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[GTriderXC]

** Attachment added: "screenshot20160728_155227118.png"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708957/+files/screenshot20160728_155227118.png

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

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

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[GTriderXC]

** Attachment added: "screenshot20160728_155617313.png"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708956/+files/screenshot20160728_155617313.png

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

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

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[GTriderXC]

Today I tried with OTA12. Actually nothing changed BUT!!! I see the
problem somewhere else! I tried to pair my phone with a few car audio
systems. What You will see in the photos that i'm gonna attach below
seems not to be a problem with the bluetooth itself but with the system.
My bq4.5 displays all devices i tried to pair! Thats why i was today
unable to connect: I used to connect my phone to "BT Scania" and "Scania
BT". They are both visible on the list and I can't get rid of them! That
seems to be a problem, cause i deleted the phone from the radio but
can't forget the radios in the phone. That's why pairing is impossible.
As You see in the screenshots, i'm unable to forget the device actually
both of them whether one of them is near or not. This way i'm unable to
pair, connect etc.

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

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

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth

[GTriderXC]

** Attachment added: "screenshot20160728_155456921.png"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708955/+files/screenshot20160728_155456921.png

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

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

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1475223] Re: Crash during Clock application start on Desktop

[Marcus Endberg]

Today I've updated my BQ 4.5 phone to Ubuntu 15.04 (OTA-12), can not
open clock APP any more. Just after the splash screen appears it closes
immediately.

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

Title:
  Crash during Clock application start on Desktop

Status in Ubuntu Clock App:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Statistically once per 8 Clock runs, the application is crashing with
  following BackTrace:

  #0  0x754539fc in g_type_check_instance 
(type_instance=type_instance@entry=0xf1a0b0) at 
/build/buildd/glib2.0-2.44.1/./gobject/gtype.c:4136
  #1  0x754496fe in g_signal_emit_valist (instance=0xf1a0b0, 
signal_id=289, detail=0, var_args=var_args@entry=0x7fffd250)
  at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3090
  #2  0x7544a8ff in g_signal_emit (instance=, 
signal_id=, detail=) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
  #3  0x7fffbe19e271 in  () at /usr/lib/x86_64-linux-gnu/libgeoclue.so.0
  #4  0x7fffdfb0ef3c in marshal_dbus_message_to_g_marshaller 
(closure=0x1520db0, return_value=0x0, n_param_values=, 
param_values=, invocation_hint=0x7fffd530, marshal_data=0x0) 
at dbus-gproxy.c:1736
  #8  0x7544a8ff in  (instance=instance@entry=0xf0f780, 
signal_id=, detail=) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3361
  #5  0x754302d5 in g_closure_invoke (closure=0x1520db0, 
return_value=0x0, n_param_values=3, param_values=0x7fffd590, 
invocation_hint=0x7fffd530)
  at /build/buildd/glib2.0-2.44.1/./gobject/gclosure.c:768
  #6  0x7544203c in signal_emit_unlocked_R 
(node=node@entry=0x151e740, detail=detail@entry=1533, 
instance=instance@entry=0xf0f780, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd590) at 
/build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3549
  #7  0x7544a698 in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffd740)
  at /build/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3305
  #9  0x7fffdfb0f882 in dbus_g_proxy_manager_filter (message=0x5307c0, 
proxy=0xf0f780 [DBusGProxy]) at dbus-gproxy.c:1789
  #10 0x7fffdfb0f882 in dbus_g_proxy_manager_filter (connection=, message=0x5307c0, user_data=0xf1f540) at dbus-gproxy.c:1356
  #11 0x7fffec3e21d1 in dbus_connection_dispatch () at 
/lib/x86_64-linux-gnu/libdbus-1.so.3
  #12 0x7fffdfb095d5 in message_queue_dispatch (source=, 
callback=, user_data=) at dbus-gmain.c:90
  #13 0x7515ac3d in g_main_context_dispatch (context=0x7fffe40016f0) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3122
  #14 0x7515ac3d in g_main_context_dispatch 
(context=context@entry=0x7fffe40016f0) at 
/build/buildd/glib2.0-2.44.1/./glib/gmain.c:3737
  #15 0x7515af20 in g_main_context_iterate 
(context=context@entry=0x7fffe40016f0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=)
  at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3808
  ---Type  to continue, or q  to quit---
  #16 0x7515afcc in g_main_context_iteration (context=0x7fffe40016f0, 
may_block=1) at /build/buildd/glib2.0-2.44.1/./glib/gmain.c:3869
  #17 0x767bcc57 in 
QEventDispatcherGlib::processEvents(QFlags) () 
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #18 0x767613e2 in 
QEventLoop::exec(QFlags) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #19 0x7676902c in QCoreApplication::exec() () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #20 0x00404098 in  ()
  #21 0x75ac1a40 in __libc_start_main (main=
  0x4037d0, argc=4, argv=0x7fffdf38, init=, 
fini=, rtld_fini=, stack_end=0x7fffdf28) at 
libc-start.c:289
  #22 0x004058b9 in  ()

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

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

[Touch-packages] [Bug 1604872] Re: Apps can't connect to the user's session bus, even though it exists

[Tyler Hicks]

** Description changed:

  [Impact]
  
- Using yakkety with systemd user session makes telepathy unhappy because
- access to /run/user//bus is denied
+ Systemd user sessions makes telepathy unhappy because access to
+ /run/user//bus is denied
  
  [Test Case]
  
  In yakkety:
  
-   sudo apt install dbus-user-session empathy
+   sudo apt install dbus-user-session empathy
  
  Restart the session (or reboot), start empathy. It fails with "Error
  contacting the account manager", and dmesg shows several
+ 
+ In 16.04, you may need to set correctly DBUS_SESSION_BUS_ADDRESS before
+ launching empathy:
+ 
+ $ DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" empathy
  
  [ 63.960358] audit: type=1400 audit(1469458539.595:27):
  apparmor="DENIED" operation="connect" profile="/usr/lib/telepathy
  /mission-control-5" name="/run/user/1000/bus" pid=4563 comm="mission-
  control" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
  
  [Regression Potential]
  
  None. The fix simply adds permissions to the dbus-session-strict
  abstraction. This change will not introduce any new AppArmor denials
  since policy is being loosened instead of being restricted.

** Description changed:

  [Impact]
  
  Systemd user sessions makes telepathy unhappy because access to
  /run/user//bus is denied
  
  [Test Case]
  
- In yakkety:
+ $ sudo apt install dbus-user-session empathy
  
-   sudo apt install dbus-user-session empathy
+ Restart the session (or reboot) and then start empathy:
  
- Restart the session (or reboot), start empathy. It fails with "Error
- contacting the account manager", and dmesg shows several
+ $ empathy
  
  In 16.04, you may need to set correctly DBUS_SESSION_BUS_ADDRESS before
  launching empathy:
  
  $ DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" empathy
+ 
+ Without this bug fix, empathy fails with "Error contacting the account
+ manager", and dmesg shows several denial messages like so:
  
  [ 63.960358] audit: type=1400 audit(1469458539.595:27):
  apparmor="DENIED" operation="connect" profile="/usr/lib/telepathy
  /mission-control-5" name="/run/user/1000/bus" pid=4563 comm="mission-
  control" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
  
  [Regression Potential]
  
  None. The fix simply adds permissions to the dbus-session-strict
  abstraction. This change will not introduce any new AppArmor denials
  since policy is being loosened instead of being restricted.

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

Title:
  Apps can't connect to the user's session bus, even though it exists

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Systemd user sessions makes telepathy unhappy because access to
  /run/user//bus is denied

  [Test Case]

  $ sudo apt install dbus-user-session empathy

  Restart the session (or reboot) and then start empathy:

  $ empathy

  In 16.04, you may need to set correctly DBUS_SESSION_BUS_ADDRESS
  before launching empathy:

  $ DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus" empathy

  Without this bug fix, empathy fails with "Error contacting the account
  manager", and dmesg shows several denial messages like so:

  [ 63.960358] audit: type=1400 audit(1469458539.595:27):
  apparmor="DENIED" operation="connect" profile="/usr/lib/telepathy
  /mission-control-5" name="/run/user/1000/bus" pid=4563 comm="mission-
  control" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000

  [Regression Potential]

  None. The fix simply adds permissions to the dbus-session-strict
  abstraction. This change will not introduce any new AppArmor denials
  since policy is being loosened instead of being restricted.

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

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

[Touch-packages] [Bug 1602737] SOS report for systemd PCI Roce Interface renaming

[bugproxy]

Default Comment by Bridge

** Attachment added: "SOS report for systemd PCI Roce Interface renaming"
   
https://bugs.launchpad.net/bugs/1602737/+attachment/4708952/+files/sosreport-HGrauer-20160713144947.tar.xz

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file: /lib/udev/rules.d/60-evdev.rules
  Reading rules file: /lib/udev/rules.d/60-gnupg.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules
  Reading rules file: 

[Touch-packages] [Bug 1589775] Re: ifupdown of ucarp interface fails

[Sangeetha Srikanth]

Hello, Any update on this defect?

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

Title:
  ifupdown of ucarp interface fails

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  apt-cache policy ifupdown
  ifupdown:
    Installed: 0.7.47.2ubuntu4.4
    Candidate: 0.7.47.2ubuntu4.4

  ifupdown of ucarp interface fails if the interface name >=16 chars.

  Example configuration,

  bond0.1234:ucarp

  /usr/share/ucarp/vip-up bond0.1234 10.10.20.2

  RTNETLINK answers: Numerical result out of range
  Failed to bring up bond0.1234:ucarp.

  To work around this issue,
  1) Rename the bond0.1234:ucarp interface manually in /etc/network/interfaces 
file to bond0.1234:u
  2) Edit /usr/share/ucarp/vip-up and /usr/share/ucarp/vip-down script
  to use the modified interface name.

  /sbin/ifup $1:u

  This issue affects all ucarp interfaces on vlans > 999.

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

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

[Touch-packages] [Bug 1607237] Re: Accented dead characters (áéíóú) not working on external keyboards

[Daniel Rodríguez Güell]

The problem persist in OTA-12 and bqm10. In xapps it works perfect but
in native apps. In addiction, the 'arroba' character and the "altgr
characters" works in all native apps except default navigator.

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

Title:
  Accented dead characters (áéíóú) not working on external keyboards

Status in Canonical System Image:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Using my keyboard with Spanish layout:

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

  Extra info:

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

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

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

[Touch-packages] [Bug 1607533] [NEW] [scopes] Unable to turn location services back on

[Michael Orovan]

Public bug reported:

I have disabled location services in each scope(top checkbox). Later
option to re-enable is not present(all remaining boxes are checked).
Afterwards I have allowed location detection to scopes (initially this
was not required. see https://bugs.launchpad.net/ubuntu/+source/unity-
scopes-shell/+bug/1458235 ), but error "Please enable location services.
Refresh by pulling... " remains and location dependent scopes are not
working.

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

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

Title:
  [scopes] Unable to turn location services back on

Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  I have disabled location services in each scope(top checkbox). Later
  option to re-enable is not present(all remaining boxes are checked).
  Afterwards I have allowed location detection to scopes (initially this
  was not required. see https://bugs.launchpad.net/ubuntu/+source/unity-
  scopes-shell/+bug/1458235 ), but error "Please enable location
  services. Refresh by pulling... " remains and location dependent
  scopes are not working.

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

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

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

[radiantptz]

Confirmed fixed on @robert123m post #5 above on ubuntu 16.04.1 LTS.
Can't thank you enough. Here is my env for reference:

$ dpkg -l | grep 'pulse\|bluetooth' 
ii  blueman 2.0.4-1ubuntu2
ii  gir1.2-gnomebluetooth-1.0:amd64 3.18.2-1ubuntu2
ii  gnome-bluetooth 3.18.2-1ubuntu2
ii  gstreamer1.0-pulseaudio:amd64   1.8.2-1ubuntu0.1
ii  libbluetooth3:amd64 5.37-0ubuntu5
ii  libcanberra-pulse:amd64 0.30-2.1ubuntu1
ii  libgnome-bluetooth13:amd64  3.18.2-1ubuntu2
ii  libpulse-mainloop-glib0:amd64   1:8.0-0ubuntu3
ii  libpulse0:amd64 1:8.0-0ubuntu3
ii  libpulse0:i386  1:8.0-0ubuntu3
ii  libpulsedsp:amd64   1:8.0-0ubuntu3
ii  pulseaudio  1:8.0-0ubuntu3
ii  pulseaudio-module-bluetooth 1:8.0-0ubuntu3
ii  pulseaudio-module-x11   1:8.0-0ubuntu3
ii  pulseaudio-utils1:8.0-0ubuntu3

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

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

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

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

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

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

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

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

[Touch-packages] [Bug 1604872] Re: Apps can't connect to the user's session bus, even though it exists

[Tyler Hicks]

** Description changed:

+ [Impact]
+ 
  Using yakkety with systemd user session makes telepathy unhappy because
  access to /run/user//bus is denied
+ 
+ [Test Case]
+ 
+ In yakkety:
+ 
+   sudo apt install dbus-user-session empathy
+ 
+ Restart the session (or reboot), start empathy. It fails with "Error
+ contacting the account manager", and dmesg shows several
+ 
+ [ 63.960358] audit: type=1400 audit(1469458539.595:27):
+ apparmor="DENIED" operation="connect" profile="/usr/lib/telepathy
+ /mission-control-5" name="/run/user/1000/bus" pid=4563 comm="mission-
+ control" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
+ 
+ [Regression Potential]
+ 
+ None. The fix simply adds permissions to the dbus-session-strict
+ abstraction. This change will not introduce any new AppArmor denials
+ since policy is being loosened instead of being restricted.

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

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

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  Apps can't connect to the user's session bus, even though it exists

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Using yakkety with systemd user session makes telepathy unhappy
  because access to /run/user//bus is denied

  [Test Case]

  In yakkety:

sudo apt install dbus-user-session empathy

  Restart the session (or reboot), start empathy. It fails with "Error
  contacting the account manager", and dmesg shows several

  [ 63.960358] audit: type=1400 audit(1469458539.595:27):
  apparmor="DENIED" operation="connect" profile="/usr/lib/telepathy
  /mission-control-5" name="/run/user/1000/bus" pid=4563 comm="mission-
  control" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000

  [Regression Potential]

  None. The fix simply adds permissions to the dbus-session-strict
  abstraction. This change will not introduce any new AppArmor denials
  since policy is being loosened instead of being restricted.

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

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

[Touch-packages] [Bug 1584069] Re: change_profile rules need a modifier to allow non-secureexec transitions

[Tyler Hicks]

** Description changed:

+ [Impact]
+ 
+ Applications which use libapparmor's aa_change_onexec() to set up an
+ AppArmor profile transition across an upcoming exec() cannot pre-
+ initialize the environment. This is caused by AppArmor unconditionally
+ setting the AT_SECURE flag on the process, causing libc to scrub the
+ environment upon exec().
+ 
+ Upstream AppArmor and Yakkety now support policy language that allows
+ the policy author to specify that the environment should not be scrubbed
+ but the changes need to be SRU'ed to Ubuntu 16.04.
+ 
+ [Test Case]
+ 
+ The upstream changes include exhaustive tests for the new policy
+ language keywords. Some of them are run at build time (the
+ apparmor_parser tests) and all of them are run by QRT's test-apparmor.py
+ (the apparmor_parser tests, the Python utility tests, and the kernel
+ regression tests).
+ 
+ If a manual test is desired, see the original report below for steps.
+ 
+ [Regression Potential]
+ 
+ Regression potential is considerable since the fixes add new keywords to
+ the policy language. No kernel changes are required, which mitigates
+ some of the risk. Additionally, as mentioned above, the upstream changes
+ include many new tests to ensure that regressions are not introduced.
+ 
+ [Original Report]
+ 
  As it stands today, all exec transitions triggered by a change_profile
  rule cause the AT_SECURE flag in the auxiliary vector to be set due to
  the kernel function apparmor_bprm_secureexec() returning 1 while setting
  up the execution environment. This causes libc to always scrub the
  environment variables during such an exec transition.
  
  There should be a way to indicate, in the policy language, that
  AT_SECURE should not be triggered. This would be equivalent to the file
  rule type having the Px permission to trigger AT_SECURE and the px
  permission to not trigger it. The file rule type even has an 'unsafe'
  modifier keyword that could be reused as the change_profile modifier
  keyword.
  
  Steps to show that AT_SECURE is being set:
  
  # Build a test program to dump the AT_SECURE flag
  $ cat < print_at_secure.c
  #include 
  #include 
  
  int main(void)
  {
-   printf("AT_SECURE = %lu\n", getauxval(AT_SECURE));
-   return 0;
+  printf("AT_SECURE = %lu\n", getauxval(AT_SECURE));
+  return 0;
  }
  EOF
  $ gcc -o print_at_secure print_at_secure.c
  
  # Load the test profile that allows all file accesses and any change_profile 
operations
  $ echo "profile test { file, change_profile, }" | sudo apparmor_parser -qr
  
  # Run bash under the test profile
  $ aa-exec -p test -- bash
  
  # Show the AT_SECURE is not set on exec
  $ ./print_at_secure
  AT_SECURE = 0
  
  # Set up an exec transition (change_profile from the test profile back to the 
test profile)
  $ echo "exec test" > /proc/self/attr/exec
  
  # See that AT_SECURE is now set on exec
  $ ./print_at_secure
  AT_SECURE = 1

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

Title:
  change_profile rules need a modifier to allow non-secureexec
  transitions

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Applications which use libapparmor's aa_change_onexec() to set up an
  AppArmor profile transition across an upcoming exec() cannot pre-
  initialize the environment. This is caused by AppArmor unconditionally
  setting the AT_SECURE flag on the process, causing libc to scrub the
  environment upon exec().

  Upstream AppArmor and Yakkety now support policy language that allows
  the policy author to specify that the environment should not be
  scrubbed but the changes need to be SRU'ed to Ubuntu 16.04.

  [Test Case]

  The upstream changes include exhaustive tests for the new policy
  language keywords. Some of them are run at build time (the
  apparmor_parser tests) and all of them are run by QRT's test-
  apparmor.py (the apparmor_parser tests, the Python utility tests, and
  the kernel regression tests).

  If a manual test is desired, see the original report below for steps.

  [Regression Potential]

  Regression potential is considerable since the fixes add new keywords
  to the policy language. No kernel changes are required, which
  mitigates some of the risk. Additionally, as mentioned above, the
  upstream changes include many new tests to ensure that regressions are
  not introduced.

  [Original Report]

  As it stands today, all exec transitions triggered by a change_profile
  rule cause the AT_SECURE flag in the auxiliary vector to be set due to
  the kernel function apparmor_bprm_secureexec() returning 1 while
  setting up the execution environment. This causes libc to always scrub
  the environment variables during such an exec transition.

  There should be a way to indicate, 

[Touch-packages] [Bug 1528230] Re: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected

[Tyler Hicks]

** Description changed:

+ [Impact]
+ 
+ The AppArmor regression tests are ran as part of the kernel SRU
+ verification process. One of the tests, onexec.sh, contains a racy
+ section that introduces intermittent failures. Such failures introduce
+ doubt in the kernel SRU process and generate additional work to verify
+ that the failures can be ignored.
+ 
+ [Test Case]
+ 
+ Since the fix is to the onexec.sh test itself, the best test case is to
+ simply run the test. The QRT test-apparmor.py script runs this test,
+ among many others, and should be used for verification.
+ 
+ [Regression Potential]
+ 
+ None. The fix is to the test and does not affect code that is user-
+ facing.
+ 
+ [Original Report]
+ 
  New ADT test failure in Vivid:
  
    running onexec
    ONEXEC - check current 'unconfined' != expected 
'/tmp/testlibIUFsmN/source/vivid/apparmor-2.9.1/tests/regression/apparmor/onexec'
    Fatal Error (onexec): Unable to run test sub-executable
  
  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20151218_175610@/log.gz

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

Title:
  [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py --
  ONEXEC - check current 'unconfined' != expected

Status in AppArmor:
  Fix Committed
Status in QA Regression Testing:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in apparmor source package in Xenial:
  In Progress
Status in linux source package in Xenial:
  Invalid

Bug description:
  [Impact]

  The AppArmor regression tests are ran as part of the kernel SRU
  verification process. One of the tests, onexec.sh, contains a racy
  section that introduces intermittent failures. Such failures introduce
  doubt in the kernel SRU process and generate additional work to verify
  that the failures can be ignored.

  [Test Case]

  Since the fix is to the onexec.sh test itself, the best test case is
  to simply run the test. The QRT test-apparmor.py script runs this
  test, among many others, and should be used for verification.

  [Regression Potential]

  None. The fix is to the test and does not affect code that is user-
  facing.

  [Original Report]

  New ADT test failure in Vivid:

    running onexec
    ONEXEC - check current 'unconfined' != expected 
'/tmp/testlibIUFsmN/source/vivid/apparmor-2.9.1/tests/regression/apparmor/onexec'
    Fatal Error (onexec): Unable to run test sub-executable

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20151218_175610@/log.gz

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

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

Re: [Touch-packages] [Bug 1602737] [NEW] PCI RoCE Interface could not be renamed from default name with link file

[Ryan Harper]

>From what I understand, systemd does not rename devices a second time:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579130

So, it's possible that existing udev rules have already applied to the
device in question and your .link file is "too late".

This maybe a dupe of that; but provide fodder to bump priority to figure
out a solution.


On Thu, Jul 28, 2016 at 3:23 PM, Launchpad Bug Tracker <
1602...@bugs.launchpad.net> wrote:

> Frank Heimes (frank-heimes) has assigned this bug to you for systemd in
> Ubuntu:
>
> == Comment: #0 - Helmut Grauer  - 2016-07-13
> 09:05:27 ==
> Try to rename PCI Roce Interface with .link file
>
> root@s35lp02:/etc/systemd/network# cat 10-net.link
> [Match]
> Path=pci-:00:00.0*
> MACAddress=82:01:14:07:85:70
>
> [Link]
> Name=hug0
> root@s35lp02:/etc/systemd/network#
>
> do  a reboot and journalctl show old interface name for RoCE PCI
> Interface
>
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX
> rings
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX
> rings
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 -
> size:1522 prefix:0 stride:1536
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:
> Initializing port
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX
> rings
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX
> rings
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 -
> size:1522 prefix:0 stride:1536
> Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:
> Initializing port
> Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed
> from eth0
> Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed
> from eth1
> Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed
> from eth3
> Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed
> from eth2
> Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file
> system using the ext4 subsystem
> Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with
> ordered data mode. Opts: (null)
>
> udevadm test show the following output
>
> oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
> calling: test
> version 229
> This program is for debugging only, it does not run any program
> specified by a RUN key. It may show incorrect results, because
> some values may be different, or not available at a simulation run.
>
> === trie on-disk ===
> tool version:  229
> file size: 6841701 bytes
> header size 80 bytes
> strings1755245 bytes
> nodes  5086376 bytes
> Load module index
> timestamp of '/etc/systemd/network' changed
> Skipping overridden file: /usr/lib/systemd/network/99-default.link.
> Skipping overridden file: /usr/lib/systemd/network/10-net.link.
> Skipping overridden file: /lib/systemd/network/99-default.link.
> Skipping overridden file: /lib/systemd/network/10-net.link.
> Parsed configuration file /etc/systemd/network/99-default.link
> Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
> Parsed configuration file /etc/systemd/network/11-net.link
> Parsed configuration file /etc/systemd/network/10-net.link
> Created link configuration context.
> timestamp of '/etc/udev/rules.d' changed
> Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
> Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
> Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
> Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
> Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
> Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
> Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
> Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
> Reading rules file: /lib/udev/rules.d/50-firmware.rules
> Reading rules file: /lib/udev/rules.d/50-udev-default.rules
> Reading rules file: /lib/udev/rules.d/55-dm.rules
> Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
> Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
> Reading rules file: /lib/udev/rules.d/56-lvm.rules
> Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
> Reading rules file: /lib/udev/rules.d/59-dasd.rules
> Reading rules file: /lib/udev/rules.d/60-block.rules
> Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
> Reading rules file: /lib/udev/rules.d/60-crda.rules
> Reading rules file: /lib/udev/rules.d/60-drm.rules
> Reading rules file: /lib/udev/rules.d/60-evdev.rules
> Reading rules file: /lib/udev/rules.d/60-gnupg.rules
> Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules
> Reading rules file: 

[Touch-packages] [Bug 1578619] Re: [regression] Extra flickable margin added when using PullToRefresh

[Alberto Mardegan]

I just tried the test application I attached to the bug, and I can still
reproduce this.

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

Title:
  [regression] Extra flickable margin added when using PullToRefresh

Status in Canonical System Image:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The attached test works fine under OTA-10, but fails in rc-proposed.
  This is most likely caused by https://code.launchpad.net/~tpeeters
  /ubuntu-ui-toolkit/invisible-header-topmargin/+merge/290659 which also
  causes bug 1572525 and I asked to be reverted.

  To reproduce, run the attached test case with qmlscene:

  1) Wait for the window to be populated (network connectivity is needed)
  2) Swipe down, to trigger the pull to refresh action
  3) View automatically jumps to the second page
  4) navigate back to the first page
  5) watch the flickable topMargin: the pulltorefresh item is now visible

  If time you repeat steps 2-4, the topMargin increases.

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

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

[Touch-packages] [Bug 1582374] Re: Log contains unknown mode senw

[Tyler Hicks]

** Description changed:

+ [Impact]
+ 
+ AppArmor policy developers cannot use aa-logprof without it exiting with
+ a traceback on certain denial messages.
+ 
+ [Test Case]
+ 
+ $ echo 'type=AVC msg=audit(1463403689.381:267599): apparmor="ALLOWED" \
+ operation="file_perm" profile="foo" pid=13215 comm="apache2" \
+ laddr=:::192.168.1.100 lport=80 faddr=:::192.168.1.100 fport=45658 \
+ family="inet6" sock_type="stream" protocol=6 requested_mask="send" \
+ denied_mask="send"' > /tmp/log
+ $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
+ $ aa-logprof -f /tmp/log -d /tmp/profiles
+ 
+ Expected output of the last command is:
+ 
+ Reading log entries from /tmp/log.
+ Updating AppArmor profiles in /tmp/profiles.
+ 
+ [Regression Potential]
+ 
+ There is little potential for regression. This "hotfix" could result in
+ some slight confusion because the problematic denial messages will
+ simply be ignored but it allows aa-logprof to do its intended job
+ without unexpectedly exiting.
+ 
+ [Original Report]
+ 
  Ref #1243932.  Same title but appears to be different cause.
  
  Ubuntu 16.04.  Error thrown on 'sudo aa-logprof'
  
  Python 3.5.1+: /usr/bin/python3
  Mon May 16 20:13:30 2016
  
  A problem occurred in a Python script.  Here is the sequence of
  function calls leading up to the error, in the order they occurred.
  
-  /usr/sbin/aa-logprof in ()
-42 
-43 if profiledir:
-44 apparmor.profile_dir = apparmor.get_full_path(profiledir)
-45 if not os.path.isdir(apparmor.profile_dir):
-46 raise apparmor.AppArmorException("%s is not a 
directory."%profiledir)
-47 
-48 apparmor.loadincludes()
-49 
-50 apparmor.do_logprof_pass(logmark)
-51 
+  /usr/sbin/aa-logprof in ()
+    42
+    43 if profiledir:
+    44 apparmor.profile_dir = apparmor.get_full_path(profiledir)
+    45 if not os.path.isdir(apparmor.profile_dir):
+    46 raise apparmor.AppArmorException("%s is not a 
directory."%profiledir)
+    47
+    48 apparmor.loadincludes()
+    49
+    50 apparmor.do_logprof_pass(logmark)
+    51
  apparmor = 
  apparmor.do_logprof_pass = 
  logmark = ''
  
-  /usr/lib/python3/dist-packages/apparmor/aa.py in do_logprof_pass(logmark='', 
passno=0, pid={13215: [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.xx.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']], 13697: [['path', 
13697, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', 
{'::a', '::w', 'a', 'w'}, '/proc/13697/attr/current', '']]})
-  2184 ##repo_cfg = read_config('repository.conf')
-  2185 ##if not repo_cfg['repository'].get('enabled', False) or 
repo_cfg['repository]['enabled'] not in ['yes', 'no']:
-  2186 ##UI_ask_to_enable_repo()
-  2187 
-  2188 log_reader = apparmor.logparser.ReadLog(pid, logfile, 
existing_profiles, profile_dir, log)
-  2189 log = log_reader.read_log(logmark)
-  2190 #read_log(logmark)
-  2191 
-  2192 for root in log:
-  2193 handle_children('', '', root)
+  /usr/lib/python3/dist-packages/apparmor/aa.py in do_logprof_pass(logmark='', 
passno=0, pid={13215: [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.xx.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']], 13697: [['path', 
13697, 'null-complain-profile', 'null-complain-profile', 'HINT', 'PERMITTING', 
{'::a', '::w', 'a', 'w'}, '/proc/13697/attr/current', '']]})
+  2184 ##repo_cfg = read_config('repository.conf')
+  2185 ##if not repo_cfg['repository'].get('enabled', False) or 
repo_cfg['repository]['enabled'] not in ['yes', 'no']:
+  2186 ##UI_ask_to_enable_repo()
+  2187
+  2188 log_reader = apparmor.logparser.ReadLog(pid, logfile, 
existing_profiles, profile_dir, log)
+  2189 log = log_reader.read_log(logmark)
+  2190 #read_log(logmark)
+  2191
+  2192 for root in log:
+  2193 handle_children('', '', root)
  global log = [[['path', 13697, 'null-complain-profile', 
'null-complain-profile', 'HINT', 'PERMITTING', {'::a', '::w', 'a', 'w'}, 
'/proc/13697/attr/current', '']], [['unknown_hat', 13215, '/usr/sbin/apache2', 
'null-www.po4management.co.uk', 'PERMITTING', 'null-www.xx.co.uk'], 
['path', 13215, 'null-complain-profile', 'null-complain-profile', 'HINT', 
'PERMITTING', {'::r', 'r'}, '/proc/13215/attr/current', '']]]
  log_reader = 
  log_reader.read_log = >
  logmark = ''
  
-  /usr/lib/python3/dist-packages/apparmor/logparser.py in 
read_log(self=, logmark='')
-   402 self.add_event_to_tree(event)
-   403 except AppArmorException as e:
-   404 ex_msg = ('%(msg)s\n\nThis error was caused by the 

[Touch-packages] [Bug 1584069] Re: change_profile rules need a modifier to allow non-secureexec transitions

[Tyler Hicks]

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

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => High

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

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  change_profile rules need a modifier to allow non-secureexec
  transitions

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  In Progress

Bug description:
  [Impact]

  Applications which use libapparmor's aa_change_onexec() to set up an
  AppArmor profile transition across an upcoming exec() cannot pre-
  initialize the environment. This is caused by AppArmor unconditionally
  setting the AT_SECURE flag on the process, causing libc to scrub the
  environment upon exec().

  Upstream AppArmor and Yakkety now support policy language that allows
  the policy author to specify that the environment should not be
  scrubbed but the changes need to be SRU'ed to Ubuntu 16.04.

  [Test Case]

  The upstream changes include exhaustive tests for the new policy
  language keywords. Some of them are run at build time (the
  apparmor_parser tests) and all of them are run by QRT's test-
  apparmor.py (the apparmor_parser tests, the Python utility tests, and
  the kernel regression tests).

  If a manual test is desired, see the original report below for steps.

  [Regression Potential]

  Regression potential is considerable since the fixes add new keywords
  to the policy language. No kernel changes are required, which
  mitigates some of the risk. Additionally, as mentioned above, the
  upstream changes include many new tests to ensure that regressions are
  not introduced.

  [Original Report]

  As it stands today, all exec transitions triggered by a change_profile
  rule cause the AT_SECURE flag in the auxiliary vector to be set due to
  the kernel function apparmor_bprm_secureexec() returning 1 while
  setting up the execution environment. This causes libc to always scrub
  the environment variables during such an exec transition.

  There should be a way to indicate, in the policy language, that
  AT_SECURE should not be triggered. This would be equivalent to the
  file rule type having the Px permission to trigger AT_SECURE and the
  px permission to not trigger it. The file rule type even has an
  'unsafe' modifier keyword that could be reused as the change_profile
  modifier keyword.

  Steps to show that AT_SECURE is being set:

  # Build a test program to dump the AT_SECURE flag
  $ cat < print_at_secure.c
  #include 
  #include 

  int main(void)
  {
   printf("AT_SECURE = %lu\n", getauxval(AT_SECURE));
   return 0;
  }
  EOF
  $ gcc -o print_at_secure print_at_secure.c

  # Load the test profile that allows all file accesses and any change_profile 
operations
  $ echo "profile test { file, change_profile, }" | sudo apparmor_parser -qr

  # Run bash under the test profile
  $ aa-exec -p test -- bash

  # Show the AT_SECURE is not set on exec
  $ ./print_at_secure
  AT_SECURE = 0

  # Set up an exec transition (change_profile from the test profile back to the 
test profile)
  $ echo "exec test" > /proc/self/attr/exec

  # See that AT_SECURE is now set on exec
  $ ./print_at_secure
  AT_SECURE = 1

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

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

[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Tyler Hicks]

** Description changed:

+ [Impact]
+ 
+ AppArmor policy developers cannot use aa-logprof without it exiting with
+ a traceback on certain denial messages.
+ 
+ [Test Case]
+ 
+ $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
+ type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
+ operation="file_perm" profile="foo" pid=12529 comm="java" \
+ laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 fport=52308 \
+ family="inet6" sock_type="stream" ^Cotocol=6 requested_mask="receive"  \
+ denied_mask="receive"' > /tmp/log
+ $ mkdir -p /tmp/profiles && printf "profile foo {\n}" > /tmp/profiles/foo
+ $ aa-logprof -f /tmp/log -d /tmp/profiles
+ 
+ Expected output of the last command is:
+ 
+ Reading log entries from /tmp/log.
+ Updating AppArmor profiles in /tmp/profiles.
+ 
+ [Regression Potential]
+ 
+ There is little potential for regression. This "hotfix" could result in
+ some slight confusion because the problematic denial messages will
+ simply be ignored but it allows aa-logprof to do its intended job
+ without unexpectedly exiting.
+ 
+ [Original Report]
+ 
  Ubuntu 16.04.
  
  Profiling apache tomcat.
-  
- 1) aa-genprof on the catalina.sh script that is used to start and stop 
tomcat. 
- 2) Start and stop tomcat. 
+ 
+ 1) aa-genprof on the catalina.sh script that is used to start and stop tomcat.
+ 2) Start and stop tomcat.
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message
  
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
- self.add_event_to_tree(event)
-   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
- e = self.parse_event_for_tree(e)
-   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
- raise AppArmorException(_('Log contains unknown mode %s') % rmask)
+   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
+ self.add_event_to_tree(event)
+   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
+ e = self.parse_event_for_tree(e)
+   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
+ raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'
  
  During handling of the above exception, another exception occurred:
  
  Traceback (most recent call last):
-   File "/usr/sbin/aa-logprof", line 50, in 
- apparmor.do_logprof_pass(logmark)
-   File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
- log = log_reader.read_log(logmark)
-   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
- raise AppArmorBug(ex_msg)  # py3-only: from None
+   File "/usr/sbin/aa-logprof", line 50, in 
+ apparmor.do_logprof_pass(logmark)
+   File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
+ log = log_reader.read_log(logmark)
+   File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
+ raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive
  
  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"
- 
  
  An unexpected error occoured!
  
  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  In Progress

Bug description:
  [Impact]

  AppArmor policy developers cannot use aa-logprof without it exiting
  with a traceback on certain denial messages.

  [Test Case]

  $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
  type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
  operation="file_perm" profile="foo" pid=12529 comm="java" \
  laddr=:::127.0.0.1 lport=8080 

[Touch-packages] [Bug 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file

[Frank Heimes]

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Changed in: ubuntu-z-systems
 Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Canonical Server Team (canonical-server)

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file: /lib/udev/rules.d/60-evdev.rules
  Reading rules file: 

[Touch-packages] [Bug 1577051] Re: aa-logprof fails with unknown mode "reweive"

[Tyler Hicks]

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

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

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

** Changed in: apparmor (Ubuntu Xenial)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  aa-logprof fails with unknown mode "reweive"

Status in AppArmor:
  Confirmed
Status in Linux Mint:
  New
Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  In Progress

Bug description:
  Ubuntu 16.04.

  Profiling apache tomcat.
   
  1) aa-genprof on the catalina.sh script that is used to start and stop 
tomcat. 
  2) Start and stop tomcat. 
  3) Scan and save the profile.
  4) aa-complain on the tomcat profile
  5) Start tomcat again and this time also send a http request to tomcat.
  6) Run aa-logprof which fails with this message

  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  Apr 30 21:53:05 nova kernel: [24668.960760] audit: type=1400 
audit(1462045985.636:2154): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/local/apache-tomcat-8.0.33/bin/catalina.sh///usr/local/jdk1.8.0_92/bin/java"
 pid=12529 comm="java" laddr=:::127.0.0.1 lport=8080 faddr=:::127.0.0.1 
fport=52308 family="inet6" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  
  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-wj6gamog.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

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

[Touch-packages] [Bug 1605513] Re: Touchpad scrolling in dash and system settings is disproportionately faster than mouse wheel scrolling

[Launchpad Bug Tracker]

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

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  Touchpad scrolling in dash and system settings is disproportionately
  faster than mouse wheel scrolling

Status in Canonical System Image:
  New
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Touchpad scrolling in dash and system settings is disproportionately
  faster than mouse wheel scrolling

  I can only say this with confidence today because I implemented
  accurate smooth scrolling in Xmir yesterday, so I know how it should
  behave.

  It's possible QtMir is overreacting to the large number of events that
  touchpads generate compared to a mouse wheel, without taking into
  account the scroll magnitude of each one is smaller.

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

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

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

[LlamasJM]

Alt-Gr works for me in XApps, but not in normal apps as Uwriter or
Telegram. Bq M10 FHD. OTA 12.

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

Title:
  AltGr not working on external keyboards

Status in Canonical System Image:
  Fix Released
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Using my keyboard with Spanish layout:

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

  Extra info:

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

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

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

[Touch-packages] [Bug 1584575] Re: /lib/systemd/system/lightdm.service file has no [Install] clause

[Daniel Richard G.]

Maybe make display-manager.service into an actual service file (rather
than a symlink), and have that start whatever /etc/X11/default-display-
manager points to?

What I want is to be able to disable and then re-enable the display
manager starting on boot using similar administrative commands, like a
"systemctl disable/enable" pair. Even better if the argument to the
commands is the same in both cases.

(Possibly even better yet if default-display-manager could be set to
some "null" option, so you can disable/re-enable the display manager
without ever touching systemd...)

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

Title:
  /lib/systemd/system/lightdm.service file has no [Install] clause

Status in lightdm package in Ubuntu:
  New

Bug description:
  This concerns lightdm 1.18.1-0ubuntu1 in Xenial.

  The /lib/systemd/system/lightdm.service file lacks an [Install]
  clause. Meaning, that if you do

  # systemctl disable display-manager

  to prevent LightDM from starting, running

  # systemctl enable lightdm

  does not restore the /etc/systemd/system/display-manager.service
  symlink, and thus does not re-enable LightDM to run at the next boot
  as intended.

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

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

[Touch-packages] [Bug 1598904] Re: X server crashes sporadically with a segfault

[Christopher M. Penalver]

Stefan Freyr, if you install the xenial xorg enablement stack following
https://wiki.ubuntu.com/Kernel/LTSEnablementStack is this issue still
reproducible?

** Tags removed: bios-outdated-1.24
** Tags added: latest-bios-1.25

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

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

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

Title:
  X server crashes sporadically with a segfault

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My desktop session crashes sporadically. Often this happens when I
  leave the computer and the screensaver starts (Euphoria GL
  screensaver). This bug is not reproducible on demand.

  Attached is my Xorg log file which seems to indicate that this problem
  is related to the i915 driver code.

  ---
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  DistUpgraded: 2016-06-15 15:16:54,383 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:5036]
  InstallationDate: Installed on 2016-05-26 (59 days ago)
  InstallationMedia: Kubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: LENOVO 20BWS18900
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7
  Tags:  trusty ubuntu
  Uname: Linux 4.6.3-040603-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2016-06-15 (39 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET46WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS18900
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20BWS18900:pvrThinkPadT450s:rvnLENOVO:rn20BWS18900:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BWS18900
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  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: Mon Jul 25 09:49:33 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1133
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

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

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

[Touch-packages] [Bug 1584601] Re: Mir fails to build in: COMPOSITOR_TRACE_CALL

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-landing-071

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

Title:
  Mir fails to build in: COMPOSITOR_TRACE_CALL

Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/compositor_report.cpp:30:1:
 error: use of GNU statement expression extension 
[-Werror,-Wgnu-statement-expression]
  13:08:37 COMPOSITOR_TRACE_CALL(started)
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/compositor_report.cpp:28:37:
 note: expanded from macro 'COMPOSITOR_TRACE_CALL'
  13:08:37 #define COMPOSITOR_TRACE_CALL(name) 
MIR_LTTNG_VOID_TRACE_CALL(CompositorReport, mir_server_compositor, name)
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/server/report/lttng/lttng_utils.h:28:9:
 note: expanded from macro 'MIR_LTTNG_VOID_TRACE_CALL'
  13:08:37 mir_tracepoint(comp, name, 0);   \
  13:08:37 ^
  13:08:37 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/src/include/common/mir/report/lttng/mir_tracepoint.h:22:32:
 note: expanded from macro 'mir_tracepoint'
  13:08:37 #define mir_tracepoint(c, ...) tracepoint(c, __VA_ARGS__)
  13:08:37^
  13:08:37 note: (skipping 1 expansions in backtrace; use 
-fmacro-backtrace-limit=0 to see all)
  13:08:37 /usr/include/lttng/tracepoint.h:50:15: note: expanded from macro 
'tracepoint_enabled'
  13:08:37 
caa_unlikely(CMM_LOAD_SHARED(__tracepoint_##provider##___##name.state))
  13:08:37  ^
  13:08:37 /usr/include/urcu/system.h:35:3: note: expanded from macro 
'CMM_LOAD_SHARED'
  13:08:37 ({  \
  13:08:37  ^

  
  --- or ---

  
  13:13:56 /usr/bin/cmake -E cmake_progress_report 
/��BUILDDIR��/mir-0.23.0+vivid1139bzr3514/obj-arm-linux-gnueabihf/CMakeFiles 
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp: In 
member function 'virtual void mir::report::lttng::CompositorReport::started()':
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp:30:87: 
error: ISO C++ forbids braced-groups within expressions [-Werror=pedantic]
  13:13:56  COMPOSITOR_TRACE_CALL(started)
  13:13:56  
  ^
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp: In 
member function 'virtual void mir::report::lttng::CompositorReport::stopped()':
  13:13:56 ../../../../../src/server/report/lttng/compositor_report.cpp:31:87: 
error: ISO C++ forbids braced-groups within expressions [-Werror=pedantic]
  13:13:56  COMPOSITOR_TRACE_CALL(stopped)
  13:13:56

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

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

[Touch-packages] [Bug 1587808] Re: Ubuntu-emulator no network on latest image

[Launchpad Bug Tracker]

** Branch linked: lp:~awe/lxc-android-config/fix-emulator-networking-
xenial

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

Title:
  Ubuntu-emulator no network on latest image

Status in Canonical System Image:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid
Status in phablet-tools package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. run sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test
  2. run ubuntu-emulator-run rc-test

  EXPECTED:
  Expected I expect there to be a mock sim installed and a network connection

  ACTUAL:
  You get the message from the wizard saying there is no sim installed and from 
the running setup you can not connect to the network.

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

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

[Touch-packages] [Bug 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

[Christopher M. Penalver]

Oliver, in 14.04, which version of the nvidia driver were you using
specifically?

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

Title:
  HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm working with an acer VN7-592G, with an Intel Core i7 Quad-Core-
  Prozessor and the NVIDIA GeForce GTX 960M. Since the upgrade to Ubuntu
  16.04 I have problems with the HDMI connection.

  If plugged in, the HDMI is recognised (xrandr), but the second monitor
  shows "no signal". After restarting the lightdm service (sudo service
  lightdm restart), the second monitor is working in most cases.
  Sometimes ubuntu freezes after lightdm restart and a hard reset has to
  be performed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 28 08:13:41 2016
  DistUpgraded: 2016-06-05 13:36:30,607 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1039]
     Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 960M] [1025:1039]
  InstallationDate: Installed on 2015-11-24 (246 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Acer Aspire VN7-592G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=347e424a-f916-4ca8-a254-caa35281e9c3 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-06-05 (52 days ago)
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-592G
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd09/25/2015:svnAcer:pnAspireVN7-592G:pvrV1.03:rvnAcer:rnAspireVN7-592G:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.name: Aspire VN7-592G
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 09:13:51 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: evdev: Dell Dell USB Wired Entry Keyboard: Unable to open 
evdev device "/dev/input/event7".
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2

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

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

[Touch-packages] [Bug 1594776] Re: add-apt-repository explodes on missing ppa

[Brian Murray]

Hello Mark, or anyone else affected,

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

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

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

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

** Changed in: software-properties (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  add-apt-repository explodes on missing ppa

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed

Bug description:
  Just saw this on freshly updated Xenial. I think it's trying to be
  helpful and tell me what PPAs a particular LP team has published, but
  in the end it explodes:

  $ sudo add-apt-repository ppa:juju/next
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 102, 
in _get_https_content_py3
  lp_page = urllib.request.urlopen(request, cafile=LAUNCHPAD_PPA_CERT)
File "/usr/lib/python3.5/urllib/request.py", line 162, in urlopen
  return opener.open(url, data, timeout)
File "/usr/lib/python3.5/urllib/request.py", line 471, in open
  response = meth(req, response)
File "/usr/lib/python3.5/urllib/request.py", line 581, in http_response
  'http', request, response, code, msg, hdrs)
File "/usr/lib/python3.5/urllib/request.py", line 509, in error
  return self._call_chain(*args)
File "/usr/lib/python3.5/urllib/request.py", line 443, in _call_chain
  result = func(*args)
File "/usr/lib/python3.5/urllib/request.py", line 589, in http_error_default
  raise HTTPError(req.full_url, code, msg, hdrs, fp)
  urllib.error.HTTPError: HTTP Error 404: Not Found

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 327, 
in get_ppa_info
  ret = get_ppa_info_from_lp(user, ppa)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 92, 
in get_ppa_info_from_lp
  return get_info_from_lp(lp_url)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 88, 
in get_info_from_lp
  return _get_https_content_py3(lp_url)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 108, 
in _get_https_content_py3
  raise PPAException("Error reading %s: %s" % (lp_url, reason), e)
  softwareproperties.ppa.PPAException: 'Error reading 
https://launchpad.net/api/1.0/~juju/+archive/ubuntu/next: Not Found'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 393, 
in shortcut_handler
  return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 356, 
in __init__
  info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 339, 
in get_ppa_info
  _get_suggested_ppa_message(user, ppa))
  softwareproperties.shortcuts.ShortcutException: Cannot add PPA: 
'ppa:~juju/ubuntu/next'.
  The team named '~juju' has no PPA named 'ubuntu/next'
  Please choose from the following available PPAs:
   * '1.22':  1.22 Updates
   * '1.22-proposed':  1.22 Proposed
   * '1.23':  1.23 Updates
   * 'daily':  Juju Daily
   * 'devel':  juju devel packages
   * 'enablement':  Juju Enablement
   * 'experimental':  juju experimental packages
   * 'golang':  juju-golang
   * 'proposed':  juju proposed packages
   * 'stable':  juju stable packages
  Error: 'ppa:juju/next' invalid

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

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

[Touch-packages] [Bug 1607490] [NEW] OTA 12 some aplications fail after upgrade

[Henry Sprog]

Public bug reported:

Following upgrades to OTA 12 the location failed to work on the BQ 4.5
and the Finger print option was missing from the setting menu on the Pro
5. A further reboot of both fixed the problems. I therefore assume that
the upgrade process is not initialising some programs correctly?

** Affects: ubuntu-touch-session (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-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/1607490

Title:
  OTA 12 some aplications fail after upgrade

Status in ubuntu-touch-session package in Ubuntu:
  New

Bug description:
  Following upgrades to OTA 12 the location failed to work on the BQ 4.5
  and the Finger print option was missing from the setting menu on the
  Pro 5. A further reboot of both fixed the problems. I therefore assume
  that the upgrade process is not initialising some programs correctly?

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

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

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

[delijati]

I got it again working by "disabling roaming" in the data connection.
http://askubuntu.com/questions/603101/gps-unvailable-on-
aquaris-e45?noredirect=1=1

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

Title:
  GPS not working on my BQ Ubuntu Touch

Status in Canonical System Image:
  Incomplete
Status in location-service package in Ubuntu:
  Confirmed

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

  I attached some screenshot from what I did.

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

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

[Touch-packages] [Bug 1588994] Re: Location not working since OTA-11 on BQ 4.5

[Henry Sprog]

Ok after Marks comment I tried again but without any luck. However I
also have a Pro 5 and the finger print function did not work (was not in
the menu). I rebooted and it appeared so In did the same with the E4.5
and the new location icon started to change colour and within a few
minutes it was all working correctly. It therefore looks like the
upgrade process does not initialise all of the programs correctly but a
reboot seems to cure this. I will file a bug.

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

Title:
  Location not working since OTA-11 on BQ 4.5

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Since installing OTA-11 Google maps reports 'Google maps could not
  determine your precise location' and Here maps says 'Can't find your
  location'.

  Location detection is ON.

  'Using GPS, anonymised Wi-Fi and mobile network info' is selected in
  Location settings.

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

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

[Touch-packages] [Bug 1480415] Re: cannot report a bug cause "apt, apt-utils are outdated" - proposed source active

[LAZA]

This is a nice trick @dino99 - and one of the points i left Ubuntu!

The report was made with Xubuntu 15.10 alpha...

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

Title:
  cannot report a bug cause "apt, apt-utils are outdated" - proposed
  source active

Status in apport package in Ubuntu:
  Invalid

Bug description:
  I have an
  Xubuntu 15.10 alpha
  VM with had an crash from aa-status

  which could not reported cause "apt, apt-utils are outdated"
  - but they are not
  - no more updates available
  - all sources were active

  Screenshot of the warning is attached.

  Xubuntu 15.10 alpha 32 Bit
  - upgraded from 15.04
  --- 
  ApportVersion: 2.18-0ubuntu5
  Architecture: i386
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-06-26 (35 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150626)
  Package: apt 1.0.9.10ubuntu5
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Tags:  wily package-from-proposed
  Uname: Linux 4.1.0-3-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1539158] Re: Unable to pair with in-car hands-free system after OTA-9 update

[Ferry Toth]

My Meizu MX4 is paired with my car (Renault with Carminat TomTom), but
the connection breaks within 2 sec. after connecting.

The sad thing is that it did work a bit before OTA 9.

Will this be fixed by the new silo?

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

Title:
  Unable to pair with in-car hands-free system after OTA-9 update

Status in Canonical System Image:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  After OTA-9 I started having trouble with my bluetooth connection to the car 
hands-free system (no sound, and incoming calls no longer displayed the 
number), so I have reset both the car and the phone connections (eg. forgot the 
devices).
  Now I can't even pair the phone with the car's system. 
  The car finds the phone, and then asks me to enter the code "" to pair 
the device, but after a few moments, it just says the connection failed and 
asks me to try again. Which fails again.

  It was working fine just before the update.

  Any logs I should post to help debug?

  PS - The car is a 2015 Honda Civic Tourer, if that matters.

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

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

[Touch-packages] [Bug 1607438] Re: Special characters are not working (alrgr + numebrs)

[Lukáš Tinkl]

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

** This bug has been marked a duplicate of bug 1590515
   AltGr composed keys don't work in the browser content

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

Title:
  Special characters are not working (alrgr + numebrs)

Status in mir package in Ubuntu:
  New

Bug description:
  Hey

  I use M10 FHD tablet with OTA-12 and bluetooth keyboard Logitech k810 and 
special characters that comes from combining altgr and numbers are not working. 
I use Slovenian layout
  So I cannot get characters such as: ˝'˙` (combining altgr and 0,9,8,7).

  Thanks

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

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

[Touch-packages] [Bug 1384394] Re: /etc/network/interfaces: "dns-nameservers" entries for bridge "br*" interfaces are ignored i.e. they are not listed in "/etc/resolv.conf" when invoking "ifup" comman

[naisanza]

This problem is present in Ubuntu 16.04 Xenial Desktop build, as well

Quick workaround:

$ rm /run/resolvconf/interface/NetworkManager

Deleting /run/resolvconf/interface/NetworkManager and re-running
ifdown/ifup will result in the /etc/network/interfaces dns-nameservers
to be populated into /etc/resolv.conf (aka
../run/resolvconf/resolv.conf)

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

Title:
  /etc/network/interfaces: "dns-nameservers" entries for bridge "br*"
  interfaces are ignored i.e. they are not listed in "/etc/resolv.conf"
  when invoking "ifup" command

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  apt-cache policy resolvconf
  resolvconf:
Installed: 1.69ubuntu1.1
Candidate: 1.69ubuntu1.1
Version table:
   *** 1.69ubuntu1.1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.69ubuntu1 0
  500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  DESCRIPTION:
  network-manager: My "eth0" and "wlan0" cards are managed by the 
network-manager and this works fine.

  /etc/network/interfaces: My 2 bridges "br0" and "br1" are managed in 
"/etc/network/interfaces" as follows:
  ...
  iface br0 inet static
   address 192.168.10.1
   netmask 255.255.255.0
   dns-nameservers 192.168.10.2
   bridge_ports none
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0

  iface br1 inet static
   address 192.168.0.1
   netmask 255.255.255.0
   dns-nameservers 192.168.0.2
   bridge_ports none
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0
  ...

  When I now bring up the bridge interfaces using:
  sudo ifup br0 br1
  Then they show up fine in "ifconfig".
  BUT "dns-nameservers 192.168.10.2" and "dns-nameservers 192.168.0.2" DO NOT 
show up in "/etc/resolv.conf"

  WORKAROUND: Until this has been fixed the following workaround works fine for 
me:
  sudo vi /etc/resolvconf/interface-order
  #Add the following entry (this entry can be put on any line BUT it has to 
come before the last entry "*"):
  ...
  br*
  ...
  *

  PS: Based on the workaround in "/etc/resolvconf/interface-order" I
  think the issue is in package "resolvconf" otherwise I would have
  reported the error against the "ifupdown scripts".

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

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

[Touch-packages] [Bug 1532899] Re: Group chat sometimes misses messages with Unknown Number Message not found

[Jason]

Hey Pat,

I'm happy to try this out on my own phone as an additional data point if
you think getting someone else to try out the fix might be helpful.
Though I'll have to dig around a bit to figure out how to build and swap
in a modified nuntium, as I'll admit I'm not familiar with that
component.

Let me know if you'd like me to try reproducing the fix.  It'd be nice
to get a fix prior to end of August, so I'm def willing to give it a
shot.

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

Title:
  Group chat sometimes misses messages with Unknown Number Message not
  found

Status in Canonical System Image:
  In Progress
Status in messaging-app package in Ubuntu:
  Invalid
Status in nuntium package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Confirmed

Bug description:
  This happened the last two times I received group chat messages.
  Several messages were not listed in the chat but rather under an
  Unknown Number contact with content Message no found.

  I see 4 such entries for the time covered in the log files.

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

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

[Touch-packages] [Bug 1492892] Re: Implement standalone bluetooth agent handler

[Launchpad Bug Tracker]

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

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

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

Title:
  Implement standalone bluetooth agent handler

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in indicator-bluetooth package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Currently the settings app registers an agent instance against BlueZ
  which can only be triggered when the application is currently active.
  To provide a better user experience we need a different place to
  implement the agent to have it running in the background all the time.
  indicator-bluetooth sounds like a suitable component for this but we
  need to sort out how we present the different user interface screens
  (trusted helper, notifications, units8, ).

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

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

[Touch-packages] [Bug 1492892] Re: Implement standalone bluetooth agent handler

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  Implement standalone bluetooth agent handler

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in indicator-bluetooth package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Currently the settings app registers an agent instance against BlueZ
  which can only be triggered when the application is currently active.
  To provide a better user experience we need a different place to
  implement the agent to have it running in the background all the time.
  indicator-bluetooth sounds like a suitable component for this but we
  need to sort out how we present the different user interface screens
  (trusted helper, notifications, units8, ).

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

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

[Touch-packages] [Bug 1530947] Re: Ubuntu One account was deleted

[Rodney Dawes]

For this bug, I don't think we can really fix the general "account gets
deleted" complaint in any reasonable time frame or manner. And even if
we could, the same issues which are causing the account to be deleted,
would still cause a request to log in again, but the complaint would
just be "u1 account doesn't work."

Due to the way online-accounts works, the way we use the U1 account in
the system, and to provide a remotely decent experience, the only
current viable option, is to delete the account and require logging in
again. This may be unfortunate, but it is what it is.

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

Title:
  Ubuntu One account was deleted

Status in ubuntuone-credentials package in Ubuntu:
  Confirmed

Bug description:
  I came into the office, checked for updates, hit the bug where it
  spins forever (meaning the 3G network was there but not accessible),
  turned on wifi, checked again and it showed me two app updates with
  the message to sign in to ubuntu one

  MX4 on rc-proposed r209

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

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

[Touch-packages] [Bug 1587808] Re: Ubuntu-emulator no network on latest image

[Launchpad Bug Tracker]

** Branch linked: lp:~awe/lxc-android-config/fix-emulator-networking

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

Title:
  Ubuntu-emulator no network on latest image

Status in Canonical System Image:
  In Progress
Status in lxc-android-config package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid
Status in phablet-tools package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. run sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test
  2. run ubuntu-emulator-run rc-test

  EXPECTED:
  Expected I expect there to be a mock sim installed and a network connection

  ACTUAL:
  You get the message from the wizard saying there is no sim installed and from 
the running setup you can not connect to the network.

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

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

[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth

[Dadio]

Did the update to OTA12 on a Meizu MX4 and trying to connect to an Audi
bluetooth system:

Small step forwards...

Works:
- Car bluetooth is detected
- The car bluetooth is shown (not just unknown...)
- If I press 'connect', I'm asked for the pincode
- If I enter the correct pincode, ubuntu says it's connected

Doesn't work:
- Altough ubuntu says it's connected, the car doesn't agree: no phone
  connected...
- If I place a call (using the phone), the bluethoot indicator icon turns
  white, but the sound go's through the phone speaker. Nothing happens on
  the car display
- If the phone is restarted, it can't connect again with the car system
- If I remove all the bluetooth devices on the car system, I can
  reconnect using the pin. But strangely, the signal strength is 'none'?
  Only removing the connection on both devices, gives me back 'strong'
  as signal strength...

I also have a Peugeot. For that car everything works excellent (even after 
removing the connections and connecting again):
- Calling trough bluetooth
- Syncing contacts
- Listening to music trough bluetooth

If new debug info/logs are useful, please let me know...

** Summary changed:

- Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
+ Ubuntu Phone does not connect to car-bluetooth

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

Title:
  Ubuntu Phone does not connect to car-bluetooth

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

Bug description:
  With my FORD Focus Car, pairing does not work. The bluetooth system in
  the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition"
  and then prompts me to connect with a 4-digit pin code, but the Ubuntu
  phone doesn't react at all and after a while the car system says that
  it failed to connect.

  image: 20150310-3201c0a
  KRILIN01A-S15A_BQ_L100EN_2020_150312
  OS Build 20

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

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

[Touch-packages] [Bug 1607470] [NEW] LightDM (in locked state) shows desktop if I try to change keyboard layout

[Alex]

Public bug reported:

This bug is related to bug#1606555. But this is also a security and
privacy threat.

release of Ubuntu: Ubuntu 16.04

What's happening:

I lock my machine(Super + L key)
LightDM greeter is showing.
If I push hotkey to change keyboard layout, LightDM flashes and then it shows 
my desktop for a second. 
It's a privacy risk.

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

** Information type changed from Private Security to Public

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

Title:
  LightDM (in locked state) shows desktop if I try to change keyboard
  layout

Status in lightdm package in Ubuntu:
  New

Bug description:
  This bug is related to bug#1606555. But this is also a security and
  privacy threat.

  release of Ubuntu: Ubuntu 16.04

  What's happening:

  I lock my machine(Super + L key)
  LightDM greeter is showing.
  If I push hotkey to change keyboard layout, LightDM flashes and then it shows 
my desktop for a second. 
  It's a privacy risk.

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

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

[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

** Description changed:

  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387
  
  Flash phone with --bootstrap, and walk through the welcome wizard. Once
  you have a phone to use, visit the BT settings, and pair a mono 'HSP'
  headset. In my case an old Jabra OTE-1.
  
  Once the device is paired, make an incoming call to the handset. Use the
- button to answer the call.
+ headset button to answer the call.
  
  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.
  
  I heard no audio.
  
  Expected: Audio was heard on the headset during the call.
  
  Note that this does not occur on rc-proposed/meizu.en #381, so it seems
  to be a recent regression.

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the headset button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Touch-packages] [Bug 1588994] Re: Location not working since OTA-11 on BQ 4.5

[Markcortbass]

It's working perfectly for me now with OTA 12 with my bq E4.5 phone and
bq M10 tablet. All services like uNav, Here Maps and Google Maps are
working with GPS.

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

Title:
  Location not working since OTA-11 on BQ 4.5

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Since installing OTA-11 Google maps reports 'Google maps could not
  determine your precise location' and Here maps says 'Can't find your
  location'.

  Location detection is ON.

  'Using GPS, anonymised Wi-Fi and mobile network info' is selected in
  Location settings.

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

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

[Touch-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Levente Ábrók]

"Tenten36 (tenten) wrote on 2016-07-27:

The problem still exists with kernel 4.6 and 4.7 from the mainline
build.

$ DRI_PRIME=1 glxgears

gives black screen"

That seems like a regression or the newest kernels weren't patched.
Currently using 4.4.14 and it still works.

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

I plan to capture logs, following the instructions here:

https://wiki.ubuntu.com/DebuggingBluetooth

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Touch-packages] [Bug 1607466] Re: Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

I discovered this apparent regression while testing the silo 60+37 combo
@koza is using to land bluez 5.41, but note that the bug appears (and
then disappears) on vanilla 387 vs 381.


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

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Touch-packages] [Bug 1607466] [NEW] Mono BT headset has no in-call audio on recent rc-proposed

[John McAleely]

Public bug reported:

MX4/arale
ubuntu-touch/rc-proposed/meizu.en #387

Flash phone with --bootstrap, and walk through the welcome wizard. Once
you have a phone to use, visit the BT settings, and pair a mono 'HSP'
headset. In my case an old Jabra OTE-1.

Once the device is paired, make an incoming call to the handset. Use the
button to answer the call.

The handset transitions to showing you an in-call UI, and appears to
claim the audio is routed to the headset.

I heard no audio.

Expected: Audio was heard on the headset during the call.

Note that this does not occur on rc-proposed/meizu.en #381, so it seems
to be a recent regression.

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

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

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

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

** Also affects: phone-app (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Mono BT headset has no in-call audio on recent rc-proposed

Status in Canonical System Image:
  New
Status in bluez package in Ubuntu:
  New
Status in phone-app package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  MX4/arale
  ubuntu-touch/rc-proposed/meizu.en #387

  Flash phone with --bootstrap, and walk through the welcome wizard.
  Once you have a phone to use, visit the BT settings, and pair a mono
  'HSP' headset. In my case an old Jabra OTE-1.

  Once the device is paired, make an incoming call to the handset. Use
  the button to answer the call.

  The handset transitions to showing you an in-call UI, and appears to
  claim the audio is routed to the headset.

  I heard no audio.

  Expected: Audio was heard on the headset during the call.

  Note that this does not occur on rc-proposed/meizu.en #381, so it
  seems to be a recent regression.

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

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

[Touch-packages] [Bug 1604433] Re: Listening audio does not work on the desktop

[Fabio]

Ok, thanks, here you are :)

** Attachment added: "application-click-com.ubuntu.music_music_2.4.1003.log"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604433/+attachment/4708875/+files/application-click-com.ubuntu.music_music_2.4.1003.log

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

Title:
  Listening audio does not work on the desktop

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Incomplete

Bug description:
  Playing any audio (eg. youtube video) does not produce any sound on
  the desktop

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

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

[Touch-packages] [Bug 1607464] [NEW] Postscript error during printing

[Jonathan Scheff]

Public bug reported:

Ubuntu 16.0.4
HP network printer
Prints document, except for last page, with this output:

ERROR:
undefined
OFFENDING COMMAND:
...Undefined
STACK:
{the rest of the error has varied; sometimes numbers like -699.95, -300.0, 
-mark-, and others}

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 E [28/Jul/2016:11:51:52 -0500] [cups-deviced] PID 19542 (gutenprint52+usb) 
stopped with status 1!
 E [28/Jul/2016:11:56:25 -0500] [cups-deviced] PID 19768 (gutenprint52+usb) 
stopped with status 1!
CurrentDesktop: Unity
Date: Thu Jul 28 12:11:59 2016
InstallationDate: Installed on 2016-07-25 (2 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lpstat: device for Hewlett-Packard-HP-LaserJet-P2055dn: 
hp:/net/HP_LaserJet_P2055dn?ip=129.59.192.55
MachineType: Dell Inc. OptiPlex 9020
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd: Permission 
denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=314827a7-bd99-490e-b24f-2d38a73a9889 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0N4YC8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd01/08/2015:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 9020
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Postscript error during printing

Status in cups package in Ubuntu:
  New

Bug description:
  Ubuntu 16.0.4
  HP network printer
  Prints document, except for last page, with this output:

  ERROR:
  undefined
  OFFENDING COMMAND:
  ...Undefined
  STACK:
  {the rest of the error has varied; sometimes numbers like -699.95, -300.0, 
-mark-, and others}

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   E [28/Jul/2016:11:51:52 -0500] [cups-deviced] PID 19542 (gutenprint52+usb) 
stopped with status 1!
   E [28/Jul/2016:11:56:25 -0500] [cups-deviced] PID 19768 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: Unity
  Date: Thu Jul 28 12:11:59 2016
  InstallationDate: Installed on 2016-07-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lpstat: device for Hewlett-Packard-HP-LaserJet-P2055dn: 
hp:/net/HP_LaserJet_P2055dn?ip=129.59.192.55
  MachineType: Dell Inc. OptiPlex 9020
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P2055dn.ppd: Permission 
denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=314827a7-bd99-490e-b24f-2d38a73a9889 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0N4YC8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd01/08/2015:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0N4YC8:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1602737] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From ru...@us.ibm.com 2016-07-28 12:47 EDT---
Pinging for status update.

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

Title:
  PCI RoCE Interface could not be renamed from default name with link
  file

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Helmut Grauer  - 2016-07-13 
09:05:27 ==
  Try to rename PCI Roce Interface with .link file

  root@s35lp02:/etc/systemd/network# cat 10-net.link
  [Match]
  Path=pci-:00:00.0*
  MACAddress=82:01:14:07:85:70

  [Link]
  Name=hug0
  root@s35lp02:/etc/systemd/network#

  do  a reboot and journalctl show old interface name for RoCE PCI
  Interface

  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX 
rings
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2:   frag:0 - 
size:1522 prefix:0 stride:1536
  Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing 
port
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from 
eth0
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from 
eth1
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed 
from eth3
  Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from 
eth2
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system 
using the ext4 subsystem
  Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with 
ordered data mode. Opts: (null)

  udevadm test show the following output

  oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0
  calling: test
  version 229
  This program is for debugging only, it does not run any program
  specified by a RUN key. It may show incorrect results, because
  some values may be different, or not available at a simulation run.

  === trie on-disk ===
  tool version:  229
  file size: 6841701 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086376 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Skipping overridden file: /usr/lib/systemd/network/99-default.link.
  Skipping overridden file: /usr/lib/systemd/network/10-net.link.
  Skipping overridden file: /lib/systemd/network/99-default.link.
  Skipping overridden file: /lib/systemd/network/10-net.link.
  Parsed configuration file /etc/systemd/network/99-default.link
  Parsed configuration file /lib/systemd/network/90-mac-for-usb.link
  Parsed configuration file /etc/systemd/network/11-net.link
  Parsed configuration file /etc/systemd/network/10-net.link
  Created link configuration context.
  timestamp of '/etc/udev/rules.d' changed
  Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules
  Reading rules file: /lib/udev/rules.d/40-z90crypt.rules
  Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules
  Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules
  Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules
  Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules
  Reading rules file: /lib/udev/rules.d/50-firmware.rules
  Reading rules file: /lib/udev/rules.d/50-udev-default.rules
  Reading rules file: /lib/udev/rules.d/55-dm.rules
  Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules
  Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules
  Reading rules file: /lib/udev/rules.d/56-lvm.rules
  Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules
  Reading rules file: /lib/udev/rules.d/59-dasd.rules
  Reading rules file: /lib/udev/rules.d/60-block.rules
  Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
  Reading rules file: /lib/udev/rules.d/60-crda.rules
  Reading rules file: /lib/udev/rules.d/60-drm.rules
  Reading rules file: /lib/udev/rules.d/60-evdev.rules
  Reading rules file: /lib/udev/rules.d/60-gnupg.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-input.rules
  Reading rules file: /lib/udev/rules.d/60-persistent-storage-dm.rules
  

[Touch-packages] [Bug 1416659] Re: Ubuntu can't detect bluetooth device of Lenovo s400u

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu can't detect bluetooth device of Lenovo s400u

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  As reported in this question:
  https://answers.launchpad.net/ubuntu/+question/250942, Ubuntu 14.04.1
  LTS with kernel 3.18.4-031804-generic can't detect bluetooth device
  of Lenovo s400u.

  
  root@galindro-nb:~# lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  
  root@galindro-nb:~# dmesg | grep Blue
  [   17.753263] Bluetooth: Core ver 2.19
  [   17.753288] Bluetooth: HCI device and connection manager initialized
  [   17.753296] Bluetooth: HCI socket layer initialized
  [   17.753300] Bluetooth: L2CAP socket layer initialized
  [   17.753308] Bluetooth: SCO socket layer initialized
  [   17.761037] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   17.761042] Bluetooth: BNEP filters: protocol multicast
  [   17.761051] Bluetooth: BNEP socket layer initialized
  [   17.788967] Bluetooth: RFCOMM TTY layer initialized
  [   17.788980] Bluetooth: RFCOMM socket layer initialized
  [   17.788986] Bluetooth: RFCOMM ver 1.11

  
  root@galindro-nb:~# hcitool scan
  Device is not available: No such device

  
  root@galindro-nb:/tmp# hcitool dev
  Devices:

  
  *** IMPORTANT thing about lsusb.log attached file ***

 The device displayed in this line: Bus 001 Device 003: ID 045e:0745
  Microsoft Corp. Nano Transceiver v1.0 for Bluetooth , isn't the
  ultrabook built-in bluetooth. It is a Microsoft wireless mouse that
  has a micro usb bluetooth adaptor. This hardware is working very well.

  The problem is with Lenovo S400U built-in bluetooth that isn't
  reconized by Ubuntu 14.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13
  Uname: Linux 3.18.4-031804-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Sat Jan 31 10:05:28 2015
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationDate: Installed on 2014-06-29 (215 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterestingModules: rfcomm bnep bluetooth
  MachineType: LENOVO VIUS3
  ProcEnviron:
   PATH=(custom, no user)
   TERM=linux
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.4-031804-generic 
root=UUID=56329ea0-54a8-4c9e-baf2-e8b2980b224d ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DCN92WW(V8.06)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194WIN8 STD SGL
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S400U
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DCN92WW(V8.06):bd02/21/2013:svnLENOVO:pnVIUS3:pvrLenovoIdeaPadS400U:rvnLENOVO:rnINVALID:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadS400U:
  dmi.product.name: VIUS3
  dmi.product.version: Lenovo IdeaPad S400U
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  syslog:
   <30>1 2015-01-31T10:02:56.875155-02:00 galindro-nb bluetoothd 3934 - -  
Bluetooth daemon 4.101
   <27>1 2015-01-31T10:02:56.876598-02:00 galindro-nb bluetoothd 3934 - -  
Unable to get on D-Bus
   <30>1 2015-01-31T10:04:58.601387-02:00 galindro-nb bluetoothd 3990 - -  
Bluetooth daemon 4.101
   <27>1 2015-01-31T10:04:58.602835-02:00 galindro-nb bluetoothd 3990 - -  
Unable to get on D-Bus

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

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

[Touch-packages] [Bug 1362180] Re: can't connect my mouse

[Launchpad Bug Tracker]

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

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

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

Title:
  can't connect my mouse

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  the mouse is Navigator 905BT (Genius), the laptop is Acer Aspire
  E1-731. i'm using Kubuntu 14.04 (64-bit). the os just won't see the
  mouse. the mouse works fine though in windows. i tried the latest
  fedora, no luck.

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

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

[Touch-packages] [Bug 1559731] Re: Battery indicator turns red at 30% on desktop

[Anita Kuno]

I don't know if this is the same bug or not but my laptop decided it was
critically low and shut itself off while the battery indicated it still
had about 3+ hours of life left. I couldn't power it back on until I
plugged in ac and at that point it was over 80% of battery life. I don't
think this is caused by a 30% icon. If you want me to open up a new bug,
I can do so but the title at least looks the same.

Thank you,
Anita.

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

Title:
  Battery indicator turns red at 30% on desktop

Status in Canonical System Image:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  Fix Committed

Bug description:
  The indicator turns red as soon as battery goes 30%

  Please refer to the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: indicator-power 12.10.6+16.04.20160105-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 20 20:43:32 2016
  InstallationDate: Installed on 2016-03-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160313)
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1602655] Re: The openssl s390x assembly pack is not used

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Confirmed => Fix Committed

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

Title:
  The openssl s390x assembly pack is not used

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl source package in Xenial:
  New

Bug description:
  The openssl s390x assembly code is not available, causing a fallback to 
openssl internal C-code.
  The performance degradation is up to a factor 4 for asymmetric (RSA, ...)  
and a factor >10 for symmetric cipher like SHA & AES.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1602655/+subscriptions

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

[Touch-packages] [Bug 1607450] [NEW] Scroling in the scope goes untill the end of the page

[Kristijan]

Public bug reported:

Hey,

I use M10 FHD tablet with OTA-12 and sometimes I use it with mouse. When I 
scroll it down in my home scope it automatically goes untill the end of the 
scope. So if I need an app that is in the middle of the list, I have to click, 
hold and move mouse.
It could be like that if I scroll it a little bit, it goes down just a bit.

Thanks

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

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

Title:
  Scroling in the scope goes untill the end of the page

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hey,

  I use M10 FHD tablet with OTA-12 and sometimes I use it with mouse. When I 
scroll it down in my home scope it automatically goes untill the end of the 
scope. So if I need an app that is in the middle of the list, I have to click, 
hold and move mouse.
  It could be like that if I scroll it a little bit, it goes down just a bit.

  Thanks

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

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

[Touch-packages] [Bug 1602655] Re: The openssl s390x assembly pack is not used

[Dimitri John Ledkov]

** Changed in: openssl (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  The openssl s390x assembly pack is not used

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl source package in Xenial:
  New

Bug description:
  The openssl s390x assembly code is not available, causing a fallback to 
openssl internal C-code.
  The performance degradation is up to a factor 4 for asymmetric (RSA, ...)  
and a factor >10 for symmetric cipher like SHA & AES.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1602655/+subscriptions

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

[Touch-packages] [Bug 1607445] [NEW] Zoom is not correct when using HD monitor

[Kristijan]

Public bug reported:

Hey,

I use M10 FHD tablet with OTA-12 and when I connect it to the external HD 
monitor, the zoom is not correct. I cannot see the any of the border (top 
panel, launcher,...). But this only happens with some of the monitors.
One of the monitors that doesn't work correct is Samsung SyncMaster 2333HD. 
Maybe because it's also a tv tuner?

Thanks

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

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

Title:
  Zoom is not correct when using HD monitor

Status in mir package in Ubuntu:
  New

Bug description:
  Hey,

  I use M10 FHD tablet with OTA-12 and when I connect it to the external HD 
monitor, the zoom is not correct. I cannot see the any of the border (top 
panel, launcher,...). But this only happens with some of the monitors.
  One of the monitors that doesn't work correct is Samsung SyncMaster 2333HD. 
Maybe because it's also a tv tuner?

  Thanks

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

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

[Touch-packages] [Bug 1607438] [NEW] Special characters are not working (alrgr + numebrs)

[Kristijan]

Public bug reported:

Hey

I use M10 FHD tablet with OTA-12 and bluetooth keyboard Logitech k810 and 
special characters that comes from combining altgr and numbers are not working. 
I use Slovenian layout
So I cannot get characters such as: ˝'˙` (combining altgr and 0,9,8,7).

Thanks

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

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

Title:
  Special characters are not working (alrgr + numebrs)

Status in mir package in Ubuntu:
  New

Bug description:
  Hey

  I use M10 FHD tablet with OTA-12 and bluetooth keyboard Logitech k810 and 
special characters that comes from combining altgr and numbers are not working. 
I use Slovenian layout
  So I cannot get characters such as: ˝'˙` (combining altgr and 0,9,8,7).

  Thanks

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

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