[Touch-packages] [Bug 1458336] Re: Allow users to decide which apps can display anything in the circle

[Rüdiger Kupper]

Addition to #5: Fluffychat seems to have solved how to do that: once in
a while it slips in reminders as a circle message and this message
always appears first after boot.

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

Title:
  Allow users to decide which apps can display anything in the circle

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

Bug description:
  Currently a user has no control over which apps can display stuff in
  the circle. Potentially an app could show there something what a user
  do not want. It would be nice to have for example setting (like for
  notifications) which apps are allowed to use the circle.

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


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

[Touch-packages] [Bug 1458336] Re: Allow users to decide which apps can display anything in the circle

[Rüdiger Kupper]

See also 
https://github.com/ubports/ubuntu-touch/issues/1391#issuecomment-600214923.
It suggestes using the "circle message" app in order to display emergency data 
on the lock screen. However, it is not very useful if the message is not shown 
directly after boot.

** Bug watch added: github.com/ubports/ubuntu-touch/issues #1391
   https://github.com/ubports/ubuntu-touch/issues/1391

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

Title:
  Allow users to decide which apps can display anything in the circle

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

Bug description:
  Currently a user has no control over which apps can display stuff in
  the circle. Potentially an app could show there something what a user
  do not want. It would be nice to have for example setting (like for
  notifications) which apps are allowed to use the circle.

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

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

[Touch-packages] [Bug 1458336] Re: Allow users to decide which apps can display anything in the circle

[Rüdiger Kupper]

I'd like to add that it would be useful if one could customize the order
of messages displayed. Especially which message is displayed right after
bootup.

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

Title:
  Allow users to decide which apps can display anything in the circle

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

Bug description:
  Currently a user has no control over which apps can display stuff in
  the circle. Potentially an app could show there something what a user
  do not want. It would be nice to have for example setting (like for
  notifications) which apps are allowed to use the circle.

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

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

[Touch-packages] [Bug 1458336] Re: Allow users to decide which apps can display anything in the circle

[Rüdiger Kupper]

Still a very good idea.

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

Title:
  Allow users to decide which apps can display anything in the circle

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

Bug description:
  Currently a user has no control over which apps can display stuff in
  the circle. Potentially an app could show there something what a user
  do not want. It would be nice to have for example setting (like for
  notifications) which apps are allowed to use the circle.

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

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

[Touch-packages] [Bug 1856738] Re: access always denied when using @{HOME} tunable in peer_addr for abstract socket

[Rüdiger Kupper]

Is this issue related to Bug #1890905?

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

Title:
  access always denied when using @{HOME} tunable in peer_addr for
  abstract socket

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  With this profile:

  #include 

  profile test {
#include 

# Parses but always denied
unix (connect, receive, send)
  type=stream
  peer=(addr="@@{HOME}/.cache/ibus/dbus-*"),

# parses and allows access
  #  unix (connect, receive, send)
  #type=stream
  #peer=(addr="@/home/*/.cache/ibus/dbus-*"),
  }

  In one terminal I start a server:
  $ ./abstract-server stream /home/jamie/.cache/ibus/dbus-foo

  Then in another terminal do:

  $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- 
./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi
  connect() failed

  With the following denial (and no output from the server terminal):
  apparmor="DENIED" operation="connect" profile="test" pid=3665 
comm="abstract-client" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive connect" denied_mask="send connect" addr=none 
peer_addr="@/home/jamie/.cache/ibus/dbus-fo" peer="unconfined"

  Commenting out the @{HOME} rule and uncommenting the /home/* rule, it
  works:

  $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- 
./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi
  MESSAGE FROM SERVER: received message number 1

  (with the server displaying 'MESSAGE FROM CLIENT: hi')

  Attached is the server and client code.

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

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

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Rüdiger Kupper]

For your reference: Bug #1890905

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly are included above under 'Extended test case'.

  = SRU apparmor =
  [Impac

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Rüdiger Kupper]

Agreed. I'll be referencing this issue there. And I'll have a look into
the journal, thanks.

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly are included ab

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Rüdiger Kupper]

We are talking about recent Ubuntu focal, thst is: Ubuntu 20.04.1. This
is deemed safe for LTS upgrade! It is not! It will make petfectly
working installs of 18.04 LTS unusable without any warning.

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-confi

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Rüdiger Kupper]

This will affect many installs, notably in professional multi user
environments. It is absurd assuming that $XDG_CACHE_HOME is unset (any
installation with a few hundred users will have homes on a network share
and consequently caches moved elsewhere).

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus i

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Rüdiger Kupper]

Test case: chromium snap with $XDG_CACHE_HOME set.

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the initial im-config
  upload which resulted in bug #1588197. Test cases ensuring this is
  working properly are included above under 'Extended test case'.

  = SRU a

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Rüdiger Kupper]

Our $XDG_CACHE_HOME points to /var/cache/usercache//
I tried adding /var/cache/usercache/ to @{HOMEDIRS} in apparmor, but it did not 
work. How do I tell my snaps that user caches are in /var/cache/usercache/ ??

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change intentionally requires a change to apparmor to add a unix
  rule for communicating with the new ibus address. This is in xenial-
  proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
  changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
  ensure that the apparmor abstraction is updated and policy recompiled
  before ibus is restarted. This was omitted from the in

[Touch-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Rüdiger Kupper]

This is *not* fixed. I still see this issue in a recent install of Ubuntu 
20.04, where $XDG_CACHE_HOME is set.
We have home dirs mounted via network, so user caches were moved to local 
storage to sanitize network load. The right and perfectly valid way of doing so 
is setting $XDG_CACHE_HOME.
Snapd honors this variable, from what I get from related bug reports. 
However, it appears that snaps are still not allowed access to the direcrory 
configured in this environment variable.

This is a production environment for 800+ users who rely on chromium and
Ubuntu. I *really, honestly* need this fixed ASOP.

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 snapd
  interface, which is in already done.

  This change

[Touch-packages] [Bug 1178272] Re: Lubuntu: banshee, rhythmbox, etc cannot play audio without pulseaudio or gstreamer1.0-alsa

[Rüdiger Kupper]

Hello Chris Guiver,
I am not currently using Lubuntu on any device, so I cannot easily test if the 
problem still exists. User deutrino could have more information.

@deutrino: Has the bug reached attention upstream? Is it still present
in recent Lubuntu installs?

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

Title:
  Lubuntu: banshee, rhythmbox, etc cannot play audio without pulseaudio
  or gstreamer1.0-alsa

Status in banshee package in Ubuntu:
  Invalid
Status in gstreamer0.10 package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  New
Status in lubuntu-meta package in Ubuntu:
  Incomplete
Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Lubuntu Raring (13.04).
  The Lubuntu standard installation comes without jack, and without pulse, just 
plain alsa. Gstreamer applications (rhythmbox, banshee) used to work fine after 
installing "ubuntu-restricted-extras", which pulls in the usual gstreamer 
plugins.
  On my system, gstreamer applications stopped working. They report:
  > Cannot connect to server socket err = No such file or directory
  > Cannot connect to server request channel
  > jack server is not running or cannot be started
  Since there is no jack on this system, never was, and is not intended to be 
there, I cannot understand this message. The applications do not produce sound.

  This looks like gstreamer tries to start up jackd, regardless whether
  it is installed or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Thu May  9 15:38:20 2013
  InstallationDate: Installed on 2013-02-12 (85 days ago)
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: gstreamer0.10
  UpgradeStatus: Upgraded to raring on 2013-04-25 (13 days ago)

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

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

[Touch-packages] [Bug 1502644] Re: nm-applet frequentyl fails with broadband activated

[Rüdiger Kupper]

This bugh is no longer present in recent Ubuntu. Thanks for caring,
Paul.

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

Title:
  nm-applet frequentyl fails with broadband activated

Status in One Hundred Papercuts:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Lenovo Thinkpad X230-t, Ubuntu 15.10.

  When the breadband device of my thinkpad is activated, nm-applet fails
  to start most of the time. This leaves the user without any NM
  indicator in the top panel.

  I.e., users of computers with a broadband device cannot even connect
  to WiFi, unless they know how to do so via terminal.

  I.e.: Network manager fails to provide it's purpose on computers with
  breadband devices. This heavily impairs usage of Ubuntu on these
  computers.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.3
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  4 17:21:18 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-12 (905 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 10.185.224.202 dev wwan0  proto static  metric 600 
   10.185.224.192/28 dev wwan0  proto kernel  scope link  metric 600 
   169.254.0.0/16 dev wwan0  scope link  metric 1000
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (163 days ago)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   ttyACM1  gsm   connected/org/freedesktop/NetworkManager/Devices/3  
O2 Go   365d64e7-fcf1-42c8-879d-d2f249ffd2f4  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   wlan0wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Rüdiger Kupper]

Possibly a duplicate of #520546.

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 1740134] Re: File received with "bluetooth file transfer" cannot be saved

[Rüdiger Kupper]

Hi! Yes, that's on Ubuntu Touch.

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

Title:
  File received with "bluetooth file transfer" cannot be saved

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Receiving files with "bluetooth file transfer" works fine -- but just that. 
The files received appear in the lower part of the app window, but you cannot 
save them anywhere! Swiping to the right only shows the trash can symbol, so 
literally the only thing I can do with the received files is delete them! You 
can't even save them to the "Downloads" folder. What good is a file transfer 
tool, if the received file cannot be used any further?
  I am quite puzzled -- or am I missing something essential?

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

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

[Touch-packages] [Bug 1740134] Re: File received with "bluetooth file transfer" cannot be saved

[Rüdiger Kupper]

Thanks, Paul, for directing this to the right package.

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

Title:
  File received with "bluetooth file transfer" cannot be saved

Status in bluez package in Ubuntu:
  New

Bug description:
  Receiving files with "bluetooth file transfer" works fine -- but just that. 
The files received appear in the lower part of the app window, but you cannot 
save them anywhere! Swiping to the right only shows the trash can symbol, so 
literally the only thing I can do with the received files is delete them! You 
can't even save them to the "Downloads" folder. What good is a file transfer 
tool, if the received file cannot be used any further?
  I am quite puzzled -- or am I missing something essential?

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

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

[Touch-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep

[Rüdiger Kupper]

This bug is marked as "fix released", but I still see this problem in
bionic as of today. is this a regression?

** Tags added: bionic

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Rüdiger Kupper]

Same problem here, and workaround in #10 NOT working.
I confirm the OP's analysis: ALT+PrintScreen does not generate a keyboard 
event. Other Keystrokes (ALT alone, PrintScreen alone) do.

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Rüdiger Kupper]

Addition: This is in Unity. On the GNOME desktop everything seems to
work as expected.

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

[Rüdiger Kupper]

Oh, I there's a typo in comment #10:
Workaround (2) should be

sudo sysctl -w kernel.sysrq=0

not =1.

This makes ALT+PrintScreen work for me for this session. So the problem
really is that PrintScreen also works as SysReq on Laptops. But
strangely, this was never a problem before? What has changed in 17.10?

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1364452] Re: People's own phone number isn't where they expect to find it

[Rüdiger Kupper]

My own phone number doesn't show up anywhere. Not in the about section
and not in contacts. And it never did, not on my Meizu MX4 and not on my
Nexus 5. SIM is from German provider O2 (=Telefonica).

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

Title:
  People's own phone number isn't where they expect to find it

Status in Canonical System Image:
  Confirmed
Status in address-book-app package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Twenty people were given an Ubuntu phone and asked to find their own
  phone number. (10 were iPhone users, 8 Android, 1 Windows Phone, and 1
  feature phone user.)

  The first place they looked:
  - 9 in the Contacts app
  - 5 in System Settings "Phone" screen
  - 3 in System Settings "About" screen
  - 2 in the Dialer app contacts screen
  - 1 in System Settings "Cellular" screen.

  So, our current placement of the phone number in the "About" screen
  (bug 1221908) is suboptimal.

  Instead it should be in the Contacts app, and possibly in the "Phone" screen.
  Where the phone is dual SIM, both phone numbers should be shown.

  Only once that is done, it should be removed from the "About" screen.

  : "Address Book should always contain one
  special contact representing you as the user of the phone ... To
  indicate its purpose and resilience, the “Me” contact should be
  denoted by the word “Me” as a caption at the trailing end (with a
  translation hint stating that it should be extremely short); and the
  contact’s visual design should be subtly different from other
  contacts. Apart from those two differences, the contact should be
  displayed and ordered the same as any other contacts in the list..."

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

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

[Touch-packages] [Bug 774071] Re: Indicator-datetime-service renders 100% CPU usage

[Rüdiger Kupper]

No. I see it in 17.10 as of today (2018-01-09). I cannot log intro Unity
because of this bug. Right after login, indicator-datetime-service" eats
all of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again, eats all of my CPU, breaks, starts again, eats all of my CPU,
breaks, starts again, eats all of my CPU, breaks, starts again, eats all
of my CPU, breaks, starts again, eats all of my CPU, breaks, starts
again...

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

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

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

[Touch-packages] [Bug 1452291] Re: Browser cannot use system proxy settings

[Rüdiger Kupper]

Problem still exists in the UBPorts image.

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

Title:
  Browser cannot use system proxy settings

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu RTM:
  Confirmed

Bug description:
  While I can create successfully system proxy settings using

  gsettings set org.gnome.system.proxy use-same-proxy false
  gsettings set org.gnome.system.proxy mode "'manual'"
  gsettings set org.gnome.system.proxy ignore-hosts "['localhost',
  '127.0.0.0/8', '192.168.0.0/16', '::1']"
  gsettings set org.gnome.system.proxy.ftp host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.ftp port 800
  gsettings set org.gnome.system.proxy.socks host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.socks port 800
  gsettings set org.gnome.system.proxy.http host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.http port 800
  gsettings set org.gnome.system.proxy.http use-authentication false
  gsettings set org.gnome.system.proxy.http enabled true
  gsettings set org.gnome.system.proxy.https host "'192.168.112.1'"
  gsettings set org.gnome.system.proxy.https port 800

  those settings are currently not being used by the browser app.
  Accordingly I would like to request the addition of a feature to use the 
system proxy settings in the browser app.

  I have tested this on an by Aquaris E4.5 with Ubuntu 14.10 (r21).

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

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

[Touch-packages] [Bug 1310104] Re: No way to trigger fingerprint authentication on lock screen

[Rüdiger Kupper]

As a note: This bug appeared in Trusty and is still present in Zesty. It
is very likely it affects all users using fingerprint readers.

** Tags added: utopic xenial zesty

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

Title:
  No way to trigger fingerprint authentication on lock screen

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  With fprintd/libpam_fprintd installed, the user can in all places 
authenticate via the fingerprint reader. (Command line, login screen, light 
locker screen). However, light locker does not interact well with fingerprint 
authentication:
  Immediately after locking the session, the user can unlock via fingerprint. 
But once the fingerprint authentication times out, light locker waits for a 
password to be typed, and the user cannot re-initiate fingerprint 
authentication. The usual way of pressing ESC does not have effect. There even 
is a state, where light locker does not accept fingerprint nor password 
authentication -- the user is left without any possibility to unlock the 
screen. This is not acceptable.
  Please correct light locker's behavior with respect to libpam-fprintd 
authentication.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-locker (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 23:21:11 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-20 (484 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: light-locker
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago)

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Rüdiger Kupper]

Filed another bug report for web browser not loading self-signed sites,
as this problem persists with OTA-15: Bug #1662559

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

Title:
  webbrowser only partially loads some https sites

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Rüdiger Kupper]

** Description changed:

- The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
+ The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

Title:
  webbrowser only partially loads some https sites

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

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Rüdiger Kupper]

** Summary changed:

- webbrowser only partially loads some https sites after accepting self-signed 
certificate once
+ webbrowser only partially loads some https sites

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

Title:
  webbrowser only partially loads some https sites

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

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites after accepting self-signed certificate once

[Rüdiger Kupper]

Olivier and Chris, thanks for tracking this down so quickly! I
understand it will be some weeks before the release of OTA-15. Is there
something I can do to make things work for me in the meantime?

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

Title:
  webbrowser only partially loads some https sites after accepting self-
  signed certificate once

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites after accepting self-signed certificate once

[Rüdiger Kupper]

** Summary changed:

- webbrowser only partially loads some https sites
+ webbrowser only partially loads some https sites after accepting self-signed 
certificate once

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

Title:
  webbrowser only partially loads some https sites after accepting self-
  signed certificate once

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Rüdiger Kupper]

Modified bug description.

** Description changed:

- The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open self-signed 
https-secured sites correctly. The browser presents the option to go back to a 
safe site or continue anyway. If I choose continue anyway, it starts to load 
the site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
+ The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents the option to go back to a safe 
site or continue anyway. If I choose continue anyway, it starts to load the 
site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
  It appears that transmission times out while loading the page.
- One common usecase of self-signed certificates is webinterfaces of DSL or 
cable routers, such as the popular fritz box.
  Test case:
- 1) Try loading the web interface of my router: https://rkupper.no-ip.org/
-You should see the login page of a fritz box router.
- 2) Try loading the web interface of my nextcloud 
instance:https://rkupper.no-ip.org:444/
-You should see the login page of nextcloud
- Observe that the appearance of the pages varies every time, depending on how 
much of the site was loaded. Observe that pressing the login button does 
nothing – probably because the scripts have not been loaded.
- I have tried other self-signed sites, and am confident that it is not a 
problem of my server.
+ 1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
+ 2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

** Description changed:

- The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents the option to go back to a safe 
site or continue anyway. If I choose continue anyway, it starts to load the 
site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
+ The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

Title:
  webbrowser only partially loads some https sites

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

[Rüdiger Kupper]

Forget about self-signed sites: It also happens on https://www.amazon.com and 
https://www.amazon.de:
First, webbrowser-app displays a warning that the site's certificate is invalid 
(without any reason). If I then choose "continue anyway", the amazon site is 
only incompletely displayed.

The amazon web-app (preinstalled on Ubuntu phone) is dysfunctional for
the same reason.

** Summary changed:

- webbrowser only partially loads https sites with self-signed certificate
+ webbrowser only partially loads some https sites

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

Title:
  webbrowser only partially loads some https sites

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents the option to go back to a safe 
site or continue anyway. If I choose continue anyway, it starts to load the 
site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1656551] [NEW] webbrowser only partially loads https sites with self-signed certificate

[Rüdiger Kupper]

Public bug reported:

The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open self-signed 
https-secured sites correctly. The browser presents the option to go back to a 
safe site or continue anyway. If I choose continue anyway, it starts to load 
the site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
It appears that transmission times out while loading the page.
One common usecase of self-signed certificates is webinterfaces of DSL or cable 
routers, such as the popular fritz box.
Test case:
1) Try loading the web interface of my router: https://rkupper.no-ip.org/
   You should see the login page of a fritz box router.
2) Try loading the web interface of my nextcloud 
instance:https://rkupper.no-ip.org:444/
   You should see the login page of nextcloud
Observe that the appearance of the pages varies every time, depending on how 
much of the site was loaded. Observe that pressing the login button does 
nothing – probably because the scripts have not been loaded.
I have tried other self-signed sites, and am confident that it is not a problem 
of my server.

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

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

Title:
  webbrowser only partially loads https sites with self-signed
  certificate

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open self-signed 
https-secured sites correctly. The browser presents the option to go back to a 
safe site or continue anyway. If I choose continue anyway, it starts to load 
the site, but never completes. After some time it stops loading and displays a 
rather incomplete version of the site. It is clearly composed of only some of 
the pages' elements and incomplete.The amount of the page that is displayed 
varies from time to time.
  It appears that transmission times out while loading the page.
  One common usecase of self-signed certificates is webinterfaces of DSL or 
cable routers, such as the popular fritz box.
  Test case:
  1) Try loading the web interface of my router: https://rkupper.no-ip.org/
 You should see the login page of a fritz box router.
  2) Try loading the web interface of my nextcloud 
instance:https://rkupper.no-ip.org:444/
 You should see the login page of nextcloud
  Observe that the appearance of the pages varies every time, depending on how 
much of the site was loaded. Observe that pressing the login button does 
nothing – probably because the scripts have not been loaded.
  I have tried other self-signed sites, and am confident that it is not a 
problem of my server.

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

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

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

[Rüdiger Kupper]

I do confirm Jonathan's findings from comment #9. Disabling eveolution-
data-server's access to google calendar stops the excessive memory
usage.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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

[Touch-packages] [Bug 1537774] Re: Viewfinder frozen and all buttons disabled after taking HDR picture

[Rüdiger Kupper]

Same problem here, and also MX4.

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

Title:
  Viewfinder frozen and all buttons disabled after taking HDR picture

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

Bug description:
  Reported by royden in https://bugs.launchpad.net/ubuntu/+source
  /camera-app/+bug/1475895/comments/6

  "Testing the fix released for Bug #1519766 (and likely #1478693) I can
  reliably freeze the camera-app (v. 3.0.0.616) on rc-proposed Arale
  r227 by taking HDR images.

  Freeze happens around the 3rd or 4th shot of the same subject as
  reported in Bug #1519766.

  HDR shots of shaded lamp in semi-dark room (taking up 3/4 of view)
  trigger freeze on 4/5th shot.

  HDR shots of lamp on small table at distance in semi-dark room do not
  reliably trigger freeze.

  Normal shots do not trigger freeze, with or without zoom AFAIKS.

  Freeze comprises either the viewfinder holding the image of the
  attempted capture and app being no longer responsive and needing to be
  closed. Re-opening produces "Cannot access camera" error message
  screen, with access permission or some other error as cause. Reboot
  needed to regain camera function.

  Other freeze seen was a return of the viewfinder to a dark screen, and
  the same error message screen appearing."

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

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

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

[Rüdiger Kupper]

Upon killing gnome-session and logging in again, the problem is gone,
but it reappears after reboot.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

[Rüdiger Kupper]

I see this bug on a Thinkpad T61 and a Thinkpad X230t.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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

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

[Touch-packages] [Bug 1565469] Re: GPS Denied without reason

[Rüdiger Kupper]

>From my experience I believe that the issue is triggered by several apps 
>sharing GPS access.
For instance, GPS frequently breaks down with uNav, when other apps access GPS 
data concurrently. Like: Browser (geolocation, e.g. Google maps), nearby scope, 
cachemere, etc.
I tend to have open a lot of apps in background, many of them acessIng GPS. If 
I use uNav togetjer with those, it usually works for a few minuites, then 
freezes an loses GPS.
I can resolve this issue by closing all other apps using GPS. After that, uNav 
works perfect.

I.e.: uNav requires exclusive access to GPS in order to work. It breaks
as soon as another process requires read access to GPS.

There us no logical reason, why not several processes at once should
read GPS data (it is read-obky after all). Still, this reproducibly
breaks.

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

Title:
  GPS Denied without reason

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

Bug description:
  You're using the GPS, and without reason, it stops. It doesn't return more 
positions.
  If you cancel the route and set a new one, a popup will tell you that the GPS 
is denied.
  I experienced this in OSM (From Alan) too.
  You know uNav is not freeze because you can drag the map.

  rc-proposed in Nexus 4 and BQ E4.5.

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

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

[Rüdiger Kupper]

Confirming that typing accented characters does not work. This is with
OTA-12, keyboard layout "German (Macintosh)".

-- 
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 1565236] Re: AltGr not working on external keyboards

[Rüdiger Kupper]

Confirmed for my BT keyboard with German layout (manufacturer: CSL).

In *some* applications, the AltGr-Symbols can be accessed via the 
"leftAlt-AltGr-key"-combination Timo describes in comment #12 (must be pressed 
in that order). But this varies from app to app.
In most situations, there is no way of typing the "@" character, which is 
particularly annoying.

None of the AltGr-characters work in the terminal app (though it
sometimes shows undefined characters in response). I confirm the
behaviour user 3524 describes in #11 ("(arg: [0-9])" prompt.)

This is on a MEIZU MX4 with OTA 10.1.

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

Title:
  AltGr not working on external keyboards

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

Bug description:
  Using my keyboard with Spanish layout:

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

  Extra info:

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

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

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

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

[Rüdiger Kupper]

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

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

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

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

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

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

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

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

[Rüdiger Kupper]

Confirmed. It does also happen after sleep/resume, not only hibernate.

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

Title:
  bluetooth indicator doesn't work properly after hibernate

Status in indicator-bluetooth package in Ubuntu:
  Confirmed

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

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

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

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

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

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

[Rüdiger Kupper]

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

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

Title:
  Use default keymap on creation of surface

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

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

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

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

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

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

[Touch-packages] [Bug 1567250] Re: ssh signin problem since OTA-10

[Rüdiger Kupper]

Thanks, Colin! I listed openssh, because it is listed as affected in bug 
#201786, having status "Confirmed". It may be wrong there, too, or the 
maintainers had a reason to confirm it. If it helps, have a look at bug #201786.
Regards, Rüdiger

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

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Incomplete
Status in gnome-keyring package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  Confirmed
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

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

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

[Touch-packages] [Bug 1567250] Re: ssh signin problem since OTA-10

[Rüdiger Kupper]

Confirming this problem exists since OTA-10 on Meizu MX4.
Confirming the workaround in comment #1 works.
Related report: bug #201786

** Also affects: gnome-keyring (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Incomplete
Status in gnome-keyring package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  Confirmed
Status in openssh package in Ubuntu:
  New

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

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

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

[Touch-packages] [Bug 1556583] [NEW] Return key not working with bluetooth keyboard

[Rüdiger Kupper]

Public bug reported:

When typing into a text field in the browser app using a bluetooth
keyboard, the return key does not work. Other keys work as expected.Test
it in launchpad (I'm experiencing it right now, there should have been a
line break after the previous sentence) or on any other web page.This is
Ubuntu Phone OTA-9.1 on Meizu MX4.

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

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

Title:
  Return key not working with bluetooth keyboard

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When typing into a text field in the browser app using a bluetooth
  keyboard, the return key does not work. Other keys work as
  expected.Test it in launchpad (I'm experiencing it right now, there
  should have been a line break after the previous sentence) or on any
  other web page.This is Ubuntu Phone OTA-9.1 on Meizu MX4.

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

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

[Touch-packages] [Bug 1546282] Re: No way of selecting layout of bluetooth keyboard

[Rüdiger Kupper]

Until this lands in the GUI—how would I change the layout of the bluetooth 
keyboard from the terminal?
Thanks!

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: bluez (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/1546282

Title:
  No way of selecting layout of bluetooth keyboard

Status in Ubuntu UX:
  New
Status in bluez package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  What happens:
  Having connected a bluetooth keyboard to Ubuntu phone, it is locked to 
American layout. There is no option of changing the layout.

  What should happen:
  The user should be able to select the layout of her bluetooth keyboard. The 
layout should default to the option the device reports (e.g. German for a 
qwertz-keyboard).

  Today I connected a bluetooth keyboard to my Ubuntu phone (Meizu MX4,
  OTA 9). Pairing worked flawlessly, the keyboard was usable right away.
  But there is no way to select the correct layout. Ubuntu phone applies
  American (qwerty) layout, but this is wrong. My bluetooth keyboard has
  German layout (qwertz). While I can easily switch layouts for the
  screen keyboard, I cannot do so for the bluetooth keyboard. It is
  fixed to American. This renders my keyboard next to useless.

  The user should be able to configure keyboard layout for bluetooth
  devices just like for the screen keyboard.

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

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

[Touch-packages] [Bug 1495553] Re: [System settings] VPN configuration not possible

[Rüdiger Kupper]

Please implement this. It's a highly desired feature.
Thank you, the team is doing an awesome job! Ubuntu mobile is getting better 
and better by the day.

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

Title:
  [System settings] VPN configuration not possible

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Reproduce:
  Try configuring VPN

  What happens:
  You can't.

  What should happen:
  You should be able to.

  Current specification: https://wiki.ubuntu.com/Networking#VPNs

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

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

[Touch-packages] [Bug 1322121] Re: pictures taken with flash are almost completely black

[Rüdiger Kupper]

Please check if this is the same bug as bug #1368063.

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

Title:
  pictures taken with flash are almost completely black

Status in camera-app:
  Invalid
Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  Triaged
Status in qtubuntu-camera package in Ubuntu:
  Triaged

Bug description:
  On the mako / Nexus 4, the camera has an LED to use for camera flash.
  Our camera app supports the flash, and fires it while taking a picture
  with flash enabled.  However, the resulting image ends up severely
  underexposed, to the point where almost the entire image is black.

  Steps to reproduce:
  1. Run the camera app.
  2. Take a picture with flash off.
  3. Turn the flash setting on and take a picture of the same scene again.
  4. Go to the gallery app to view the results.

  Expected results:  The picture with flash should appear brighter (or,
  at least, appear how most with-flash pictures look).

  Actual results:  The picture with flash is almost completely black,
  with only a few dim details in the brightest parts of the image.

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

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

[Touch-packages] [Bug 1368063] Re: [Nexus 4] The photo captured by Camera app show darkness.

[Rüdiger Kupper]

Please check if this is the same bug as bug #1322121.

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

Title:
  [Nexus 4] The photo captured by Camera app show darkness.

Status in camera-app:
  Confirmed
Status in OEM Priority Project:
  New
Status in camera-app package in Ubuntu:
  Confirmed

Bug description:
  Install Ubuntu 14.04 and boot into OS.
  Opened Camera app from dash home.Clicked the roundness button to capture 
photos.
  View the photos in /home/pictures.Found the photos show darkness.

  Steps to Reproduce:
  1.Boot into OS.
  2.Open Camera app from dash home.
  3. Activate the camera flash
  4.Click the roundness button to capture photos.
  5.View the photos in /home/pictures.
  6.Found the photos show darkness.

  Pictures are OK only if you do not activate the flash camera.

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

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

[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]

[Rüdiger Kupper]

Today the battery indicator of my MX4 is particularly informative. See the 
attached screenshot:
- It reads "100%" and at the same time "last time fully charged 38 hours ago" 
(Wow!! My Ubuntu phone can run for 38 hours without losing a single percent of 
power! -- Or can it?).
- The line of the diagram is missing completely.


** Attachment added: "Battery indicator missing line"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1473428/+attachment/4530090/+files/screenshot20151205_131115832.png

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

Title:
  battery indicator does not update after charge [meizu ubuntu phone]

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Battery charge indicator does not update after phone is charged.

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

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

[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]

[Rüdiger Kupper]

I confirm the problem is unchanged. Ubuntu phone's battery indicator is 
unreliable, confusing and best ignored. I do not understand how such an 
important element of the GUI can stay broken for such a long time. Itbis THE 
thing every user will check every day many times. It is also THE best way to 
let down users: Their phone may refuseto charge, even  switch off at 
unpredictable times.
This is more than slightly disconcerting.
I repeat Jay's question: Is there someone looking into this?

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

Title:
  battery indicator does not update after charge [meizu ubuntu phone]

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Battery charge indicator does not update after phone is charged.

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

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

[Touch-packages] [Bug 1422534] Re: No user name and password prompt for http basic authentication protected pages

[Rüdiger Kupper]

Works! Thank you!

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

Title:
  No user name and password prompt for http basic authentication
  protected pages

Status in Canonical System Image:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in webbrowser-app package in Ubuntu RTM:
  Fix Released

Bug description:
  When accessing a http basic authentication protected page the browser
  does not prompt for a user name and password it simply displays the
  HTTP Error 401 Unauthorized message.  The browser should prompt the
  user for credentials, set the Authorization header, etc...

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

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

[Touch-packages] [Bug 1502644] [NEW] nm-applet frequentyl fails with broadband activated

[Rüdiger Kupper]

Public bug reported:

Lenovo Thinkpad X230-t, Ubuntu 15.10.

When the breadband device of my thinkpad is activated, nm-applet fails
to start most of the time. This leaves the user without any NM indicator
in the top panel.

I.e., users of computers with a broadband device cannot even connect to
WiFi, unless they know how to do so via terminal.

I.e.: Network manager fails to provide it's purpose on computers with
breadband devices. This heavily impairs usage of Ubuntu on these
computers.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.3
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct  4 17:21:18 2015
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (905 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 10.185.224.202 dev wwan0  proto static  metric 600 
 10.185.224.192/28 dev wwan0  proto kernel  scope link  metric 600 
 169.254.0.0/16 dev wwan0  scope link  metric 1000
JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2015-04-24 (163 days ago)
WifiSyslog:
 
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 ttyACM1  gsm   connected/org/freedesktop/NetworkManager/Devices/3  O2 
Go   365d64e7-fcf1-42c8-879d-d2f249ffd2f4  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --  
----
 
 wlan0wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --  
----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: hundredpapercuts
 Importance: Undecided
 Status: New

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

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

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

Title:
  nm-applet frequentyl fails with broadband activated

Status in One Hundred Papercuts:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Lenovo Thinkpad X230-t, Ubuntu 15.10.

  When the breadband device of my thinkpad is activated, nm-applet fails
  to start most of the time. This leaves the user without any NM
  indicator in the top panel.

  I.e., users of computers with a broadband device cannot even connect
  to WiFi, unless they know how to do so via terminal.

  I.e.: Network manager fails to provide it's purpose on computers with
  breadband devices. This heavily impairs usage of Ubuntu on these
  computers.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.3
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  4 17:21:18 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-12 (905 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 10.185.224.202 dev wwan0  proto static  metric 600 
   10.185.224.192/28 dev wwan0  proto kernel  scope link  metric 600 
   169.254.0.0/16 dev wwan0  scope link  metric 1000
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (163 days ago)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID   

[Touch-packages] [Bug 1502643] Re: OpenVPN unrecoverably unavailable after sleep

[Rüdiger Kupper]

Steps to reproduce:
- Connect to OpenVPN via Network manager.
- Put your computer to sleep and wake it up again.
- Observe that OpenVPN connection is not automatically reestablished.
- Observe that manually reestablishing OpenVPN fails.
- Observe that restarting ModemManager or NetworkManager service does not help.
- Observe that rebooting is the only way of recoverng from this state.

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

Title:
  OpenVPN unrecoverably unavailable after sleep

Status in network-manager package in Ubuntu:
  New

Bug description:
  Just what the title says.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.3
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  4 17:15:03 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-12 (905 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.179.1 dev wlan0  proto static  metric 400 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.179.0/24 dev wlan0  proto kernel  scope link  metric 400
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (163 days ago)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
Turmbraeu Gastzugang_5GEXT  3e637552-b358-4ff8-8b36-8e8c9dc1e239  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyACM1  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   eth0 ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1502643] [NEW] OpenVPN unrecoverably unavailable after sleep

[Rüdiger Kupper]

Public bug reported:

Just what the title says.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.3
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct  4 17:15:03 2015
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (905 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 192.168.179.1 dev wlan0  proto static  metric 400 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.179.0/24 dev wlan0  proto kernel  scope link  metric 400
JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2015-04-24 (163 days ago)
WifiSyslog:
 
nmcli-dev:
 DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
Turmbraeu Gastzugang_5GEXT  3e637552-b358-4ff8-8b36-8e8c9dc1e239  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 ttyACM1  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
  
 eth0 ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
 lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

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

Title:
  OpenVPN unrecoverably unavailable after sleep

Status in network-manager package in Ubuntu:
  New

Bug description:
  Just what the title says.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.3
  ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  4 17:15:03 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-12 (905 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.179.1 dev wlan0  proto static  metric 400 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.179.0/24 dev wlan0  proto kernel  scope link  metric 400
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (163 days ago)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
Turmbraeu Gastzugang_5GEXT  3e637552-b358-4ff8-8b36-8e8c9dc1e239  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyACM1  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
 
   eth0 ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.n

[Touch-packages] [Bug 1502446] [NEW] Cannot login on trac pages

[Rüdiger Kupper]

Public bug reported:

Using Ubuntu phone's browser, I cannot log into pages powered by the popular 
bug tracker 'trac'. For an example, try logging into trac's own site on 
http://trac.edgewall.org. (Klick the gray "login" link on the top right.)
Don't bother you have no account -- you won't evrn get the chance to log in: 
The browser displays an error page right away.

(For a second exmple, try the same on our web site http://paedml.kg-
fds.de/trac.)

I found a bug report that looks pretty much like it, but it is marked
fixed since 2013. Could please someone check, if my problem is a
regression of bug #1212980? Thank you!

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

** Description changed:

  Using Ubuntu phone's browser, I cannot log into pages powered by the popular 
bug tracker 'trac'. For an example, try logging into trac's own site on 
http://trac.edgewall.org. (Klick the gray "login" link on the top right.)
  Don't bother you have no account -- you won't evrn get the chance to log in: 
The browser displays an error page right away.
  
  (For a second exmple, try the same on our web site http://paedml.kg-
- fd.de/trac.)
+ fds.de/trac.)
  
  I found a bug report that looks pretty much like it, but it is marked
  fixed since 2013. Could please someone check, if my problem is a
  regression of bug #1212980? Thank you!

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

Title:
  Cannot login on trac pages

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Using Ubuntu phone's browser, I cannot log into pages powered by the popular 
bug tracker 'trac'. For an example, try logging into trac's own site on 
http://trac.edgewall.org. (Klick the gray "login" link on the top right.)
  Don't bother you have no account -- you won't evrn get the chance to log in: 
The browser displays an error page right away.

  (For a second exmple, try the same on our web site http://paedml.kg-
  fds.de/trac.)

  I found a bug report that looks pretty much like it, but it is marked
  fixed since 2013. Could please someone check, if my problem is a
  regression of bug #1212980? Thank you!

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

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

[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]

[Rüdiger Kupper]

Another favourite. Note how the number reads 100%, while the graph is clearly 
at 0% and has been for several minutes. And the text reads 'Last fully charged: 
39 minutes ago.'
Now, that's what we call complete disinformation :-).

** Attachment added: "Power is relative."
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1473428/+attachment/4478654/+files/screenshot20150822_202011483.png

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

Title:
  battery indicator does not update after charge [meizu ubuntu phone]

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Battery charge indicator does not update after phone is charged.

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

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

[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]

[Rüdiger Kupper]

I have noticed that the behaviour of the battery indicator got much more 
predictable over a period of continued use of my MX4. However, I believe this 
is more likely caused by my battery capacity degrading (which is normal for Li 
ion). It looks as if the battery indicator has an explicit problem with very 
new batteries?
This is just a guess, we need a developer to have a look into this problem.

Is there a one-hndred-papercuts project for Ubuntu phpne yet? If so,
this issue certainly qualifies.

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

Title:
  battery indicator does not update after charge [meizu ubuntu phone]

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Battery charge indicator does not update after phone is charged.

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

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

[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]

[Rüdiger Kupper]

I attach a screenshot of how weird the battery indicator can look. This
was ob an MX4 few weeks old.

** Attachment added: "Would you trust this indicator?"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1473428/+attachment/4478653/+files/P1010697.JPG

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

Title:
  battery indicator does not update after charge [meizu ubuntu phone]

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Battery charge indicator does not update after phone is charged.

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

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

[Touch-packages] [Bug 1176351] Re: Running on battery ethernet does not reconnect after connection was dropped once

[Rüdiger Kupper]

This bug ist not present in vivid.

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

Title:
  Running on battery ethernet does not reconnect after connection was
  dropped once

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Raring, on a Thinkpad T61, with e1000e network driver.
  After resume form suspend, eth0 is down, but network manager shows "network 
connected". Reconnecting via the indicator menu does not work.
  When I type "sudo service networking restart" in a terminal, my whole session 
breaks: unity/compiz disappears, leaving the desktop unusable. Trying to use 
nmcli from a command line reports that dbus session cannot be found.
  I need to reboot to recover from this state.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.8.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sat May  4 16:26:24 2013
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-12-20 (134 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.129  metric 
1
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to raring on 2013-04-25 (8 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   disabled
disabled   enabled disabled

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

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

[Touch-packages] [Bug 1396986] Re: System Settings > Sound > Ringer volume - only changes ringer volume when no other sounds playing

[Rüdiger Kupper]

I, too, believe that Ubuntu phone's sound GUI is ill-designed. It does not give 
the user control over what channel's volume she changes. Instead, the OS tries 
to be overly clever, such as always controlling the app in foreground (which 
may or may not be desired), adding some bias when speakers are on in the phone 
app (resulting in sound being played though volume is zero and the crossed out 
speaker symbol isshown), games starting with sound on even when silent mode is 
on, etc, etc.
See also
Bug #1483890
Bug #1384274

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

Title:
  System Settings > Sound > Ringer volume - only changes ringer volume
  when no other sounds playing

Status in The Avila project:
  Invalid
Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Version: ubuntu-touch/ubuntu-rtm/14.09-proposed r169 krillin

  System Settings > Sound > Ringer volume  is always active and always
  labelled ringer, however it only changes the ringer volume if no other
  sound is currently playing on the system.

  : "The “Silent Mode” switch
  should be followed by a slider for adjusting the volume of the active
  output role through the primary sound output. It should be labelled
  according to the primary sound output: “Speaker:”, “Headset:”,
  “Earpiece:”, etc."

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

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

[Touch-packages] [Bug 1240548] Re: [osk] the 3 states of shift key are not correct

[Rüdiger Kupper]

Still present and very confusing. Leads to frequent errors whiletyping.
Please fix.

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

Title:
  [osk] the 3 states of shift key are not correct

Status in ubuntu-keyboard:
  Invalid
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  Current situation
  The visual states are not aligned and reflecting the different letter cases.

  
  Desired solution
  Ensure the 3 states on shift key is correct:
  lowercase: shift-key unfilled
  uppercase: shift-key filled in grey
  cap-lock: shift-key filled in orange

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

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

[Touch-packages] [Bug 1495553] Re: [System settings] VPN configuration not possible

[Rüdiger Kupper]

Highly, highly, highly wanted!

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

Title:
  [System settings] VPN configuration not possible

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Triaged
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  Try configuring VPN

  What happens:
  You can't.

  What should happen:
  You should be able to.

  Current specification: https://wiki.ubuntu.com/Networking#VPNs

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

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

[Touch-packages] [Bug 1187556] Re: File->Open and File->Delete show empty dialog

[Rüdiger Kupper]

My recent comments (comment:2--comment:4) refer to Ubuntu 15.04 (vivid).
The problem could formerly be worked around by selecting the menu entry twice. 
This does not work any longer. This seems to be related Unity's 
"menu-in-the-titlebar" feature. The problem can now be worked around by 
disabling this feature for gladish, see comment:4.

However, gladish's Open and Delete menus are still broken in the current Ubuntu 
version.
i attach two screenshots, with and without the workaround in comment:4.

I cannot tell if the problem is located in package "Unity"/"unity
(Ubuntu)" or package "ladish". Please check again. Thank you.

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

Title:
  File->Open and File->Delete show empty dialog

Status in Unity:
  Fix Released
Status in ladish package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Update: In willy, choosing "Open" twice does not solve the problem any more!
  Original description:

  to reproduce:
  - start gladish
  - press File -> Open (no recent configurations listed)
  - press File -> Open again (now the recent studios are listed and can be 
chosen)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gladish 1+dfsg0-3
  ProcVersionSignature: Ubuntu 3.8.0-24.16-lowlatency 3.8.13
  Uname: Linux 3.8.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Jun  4 22:24:56 2013
  ExecutablePath: /usr/bin/gladish
  InstallationDate: Installed on 2013-02-25 (99 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ladish
  UpgradeStatus: Upgraded to raring on 2013-04-30 (34 days ago)

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

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

[Touch-packages] [Bug 1187556] Re: File->Open and File->Delete show empty dialog

[Rüdiger Kupper]

Screenshot of same gladish with UBUNTU_MENUPROXY=0. Menu displays
properly.

** Attachment added: "Screenshot of same gladish with UBUNTU_MENUPROXY=0. Menu 
displays properly."
   
https://bugs.launchpad.net/ubuntu/+source/ladish/+bug/1187556/+attachment/4466916/+files/with-workaround.jpg

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

Title:
  File->Open and File->Delete show empty dialog

Status in Unity:
  Fix Released
Status in ladish package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Update: In willy, choosing "Open" twice does not solve the problem any more!
  Original description:

  to reproduce:
  - start gladish
  - press File -> Open (no recent configurations listed)
  - press File -> Open again (now the recent studios are listed and can be 
chosen)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gladish 1+dfsg0-3
  ProcVersionSignature: Ubuntu 3.8.0-24.16-lowlatency 3.8.13
  Uname: Linux 3.8.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Jun  4 22:24:56 2013
  ExecutablePath: /usr/bin/gladish
  InstallationDate: Installed on 2013-02-25 (99 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ladish
  UpgradeStatus: Upgraded to raring on 2013-04-30 (34 days ago)

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

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

[Touch-packages] [Bug 1187556] Re: File->Open and File->Delete show empty dialog

[Rüdiger Kupper]

Screenshot of gladish in current Ubuntu vivid. Note one-pixel line that
appears instead of proper menu entries.

** Attachment added: "Screenshot of gladish in current Ubuntu vivid. Note 
one-pixel line that appears instead of proper menu entries."
   
https://bugs.launchpad.net/ubuntu/+source/ladish/+bug/1187556/+attachment/4466915/+files/standard-unity-menu.jpg

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

Title:
  File->Open and File->Delete show empty dialog

Status in Unity:
  Fix Released
Status in ladish package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Update: In willy, choosing "Open" twice does not solve the problem any more!
  Original description:

  to reproduce:
  - start gladish
  - press File -> Open (no recent configurations listed)
  - press File -> Open again (now the recent studios are listed and can be 
chosen)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gladish 1+dfsg0-3
  ProcVersionSignature: Ubuntu 3.8.0-24.16-lowlatency 3.8.13
  Uname: Linux 3.8.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Jun  4 22:24:56 2013
  ExecutablePath: /usr/bin/gladish
  InstallationDate: Installed on 2013-02-25 (99 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ladish
  UpgradeStatus: Upgraded to raring on 2013-04-30 (34 days ago)

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

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

[Touch-packages] [Bug 1187556] Re: File->Open and File->Delete show empty dialog

[Rüdiger Kupper]

** Tags added: vivd

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

Title:
  File->Open and File->Delete show empty dialog

Status in Unity:
  Fix Released
Status in ladish package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Update: In willy, choosing "Open" twice does not solve the problem any more!
  Original description:

  to reproduce:
  - start gladish
  - press File -> Open (no recent configurations listed)
  - press File -> Open again (now the recent studios are listed and can be 
chosen)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gladish 1+dfsg0-3
  ProcVersionSignature: Ubuntu 3.8.0-24.16-lowlatency 3.8.13
  Uname: Linux 3.8.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Jun  4 22:24:56 2013
  ExecutablePath: /usr/bin/gladish
  InstallationDate: Installed on 2013-02-25 (99 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ladish
  UpgradeStatus: Upgraded to raring on 2013-04-30 (34 days ago)

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

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

[Touch-packages] [Bug 1364452] Re: People's own phone number isn't where they expect to find it

[Rüdiger Kupper]

Not working in 15.04 (r3) on MEIZU MX4:
My number is neither displayed in the about screen, nor in the address book. 
(Unless I put it there manually...)

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

Title:
  People's own phone number isn't where they expect to find it

Status in Ubuntu UX:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Triaged

Bug description:
  Twenty people were given an Ubuntu phone and asked to find their own
  phone number. (10 were iPhone users, 8 Android, 1 Windows Phone, and 1
  feature phone user.)

  The first place they looked:
  - 9 in the Contacts app
  - 5 in System Settings "Phone" screen
  - 3 in System Settings "About" screen
  - 2 in the Dialer app contacts screen
  - 1 in System Settings "Cellular" screen.

  So, our current placement of the phone number in the "About" screen
  (bug 1221908) is suboptimal.

  Instead it should be in the Contacts app, and possibly in the "Phone" screen.
  Where the phone is dual SIM, both phone numbers should be shown.

  Only once that is done, it should be removed from the "About" screen.

  : "Address Book should always contain one
  special contact representing you as the user of the phone ... To
  indicate its purpose and resilience, the “Me” contact should be
  denoted by the word “Me” as a caption at the trailing end (with a
  translation hint stating that it should be extremely short); and the
  contact’s visual design should be subtly different from other
  contacts. Apart from those two differences, the contact should be
  displayed and ordered the same as any other contacts in the list..."

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

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

[Touch-packages] [Bug 1483908] [NEW] Cannot copy URLs longer than display

[Rüdiger Kupper]

Public bug reported:

Go to a URL that is long, i.e.:
http://max-skizzen-blog.blogspot.de/2009/10/hessen-eine-geschichte-von-robert.html?m=1
In the browser window, try to copy the URL string from the location bar. You 
will not succeed: There is no way to select and copy the full string. Blue 
markers will erratically appear, but cannot be moved to the beginning and end 
of the string, because the string does not scroll left or right while blue 
markers are present.
This is akward and a very poor UX. Actually, it drives me mad.

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

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

Title:
  Cannot copy URLs longer than display

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Go to a URL that is long, i.e.:
  
http://max-skizzen-blog.blogspot.de/2009/10/hessen-eine-geschichte-von-robert.html?m=1
  In the browser window, try to copy the URL string from the location bar. You 
will not succeed: There is no way to select and copy the full string. Blue 
markers will erratically appear, but cannot be moved to the beginning and end 
of the string, because the string does not scroll left or right while blue 
markers are present.
  This is akward and a very poor UX. Actually, it drives me mad.

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

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

[Touch-packages] [Bug 1328183] Re: User-Agent string results in poor UX on web

[Rüdiger Kupper]

Confirming the problem exists, and is imminent. Acknowledging it is hard
to solve. However, it must be worked upon. UX depends on it.

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

Title:
  User-Agent string results in poor UX on web

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  The User-Agent string for the browser is similar enough to the Android
  browser User-Agent, that it creates a poor experience when browsing
  the web on an Ubuntu phone. An inordinately large number of web sites
  persistently advertise to "install our app" instead of providing the
  best web experience; an app which cannot be installed.

  This is exacerbated by the pervasiveness of webapps on Ubuntu phone,
  which simply embed the mobile web site with webapp-container, and
  still result in seeing such advertisements, despite the fact that the
  "app" on Ubuntu is already installed, and the Android apps being
  advertised are simply not installable.

  Having all the big web sites telling users of Ubuntu that they should
  be using Android instead, is not very good for the user experience at
  all.

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

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

[Touch-packages] [Bug 1483870] [NEW] Album disappears after editing

[Rüdiger Kupper]

Public bug reported:

After crrating a new album, it shows up in the list of albums. I tap and hold, 
then choose 'edit.. I am presented an editable view of the album cover. I edit 
title, subtitle and cover appearance.
Then I click the arrow on the upper left (only thing to do, since there is no 
'okay' option). This returns me to the list of albums.
Surprise: My new album has disappeared! It is gone and will not come back.
I start over. The same thing happens...

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

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

Title:
  Album disappears after editing

Status in gallery-app package in Ubuntu:
  New

Bug description:
  After crrating a new album, it shows up in the list of albums. I tap and 
hold, then choose 'edit.. I am presented an editable view of the album cover. I 
edit title, subtitle and cover appearance.
  Then I click the arrow on the upper left (only thing to do, since there is no 
'okay' option). This returns me to the list of albums.
  Surprise: My new album has disappeared! It is gone and will not come back.
  I start over. The same thing happens...

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

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

[Touch-packages] [Bug 1483870] Re: Album disappears after editing

[Rüdiger Kupper]

This is on Ubuntu Phone on MEIZU MX4, gallery-app 2.9.1.1232 (today's
update).

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

Title:
  Album disappears after editing

Status in gallery-app package in Ubuntu:
  New

Bug description:
  After crrating a new album, it shows up in the list of albums. I tap and 
hold, then choose 'edit.. I am presented an editable view of the album cover. I 
edit title, subtitle and cover appearance.
  Then I click the arrow on the upper left (only thing to do, since there is no 
'okay' option). This returns me to the list of albums.
  Surprise: My new album has disappeared! It is gone and will not come back.
  I start over. The same thing happens...

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

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

[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]

[Rüdiger Kupper]

That was before the OAT (r2).

However, I am on r3 now, and I see the same problem: I have my phone
plugged in right now, green symbol, but the battery indicator is stuck
at 43%. However, the graph updates: It shows a horizontal line at 43%.

I'd love to include the output of system-image-cli, but copy-and-paste
does not work in the Ubuntu phone's browser. I'll file a bug report for
that next ;-).

It reports 'current build number 3'.

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

Title:
  battery indicator does not update after charge [meizu ubuntu phone]

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Battery charge indicator does not update after phone is charged.

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

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

[Touch-packages] [Bug 1473428] Re: battery indicator does not update after charge [meizu ubuntu phone]

[Rüdiger Kupper]

I confirm and specify:
When charging the MX4 online (powered on or standby), the battery indicator 
does not recognize the phone is being charged. Instead, recording of power 
state seems to be completely disabled while the phone is plugged in.

Example:
- indicator is at 3%. I receive warnings about low battery.
- I plug in the phone.
- battery symbol in top panel changes to green with little flash symbol.
- I leave the phone charging for some time.
- after unlock, battery indicator still reports 3%. Both in the top panel page 
and in system con fig. Graph in system config has not updated at all (as if no 
time had passed!)
- I unplug the phone and keep using it.
- I notice that the power indicator goes down. Soon, it shows 2%, then 1%. I 
keep getting low battery warnings.
- I don't believe it and reboot the phone.
- After reboot, battery indicator in top panel shows 50%.
- Graph in system config shows vertical jump from 1(?)% to 50%, as if charging 
had appeared in zero time.

Adequate report of charge state is essential on a phone. Please fix
soon!

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

Title:
  battery indicator does not update after charge [meizu ubuntu phone]

Status in indicator-power package in Ubuntu:
  Confirmed

Bug description:
  Battery charge indicator does not update after phone is charged.

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

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

[Touch-packages] [Bug 1467079] [NEW] Seats do not start

[Rüdiger Kupper]

Public bug reported:

In trusty, I was able to get a second login screen by defining two seats
in the lightdm config. This does not work any more in vivid.

I have the following file:
  /usr/share/lightdm/lightdm.conf.d/60-seats.conf

with contents:
  [Seat:0]
  user-session=ubuntu
  
  [Seat:1]
  user-session=ubuntu

In trusty, this starts two login screens on vt7 and vt8.
In vivid, I just get the default seat on vt7. The config entries seem to be 
ignored.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lightdm 1.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 20 13:11:47 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-04-12 (798 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
SourcePackage: lightdm
UpgradeStatus: Upgraded to vivid on 2015-04-24 (57 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  Seats do not start

Status in lightdm package in Ubuntu:
  New

Bug description:
  In trusty, I was able to get a second login screen by defining two
  seats in the lightdm config. This does not work any more in vivid.

  I have the following file:
/usr/share/lightdm/lightdm.conf.d/60-seats.conf

  with contents:
[Seat:0]
user-session=ubuntu

[Seat:1]
user-session=ubuntu

  In trusty, this starts two login screens on vt7 and vt8.
  In vivid, I just get the default seat on vt7. The config entries seem to be 
ignored.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 20 13:11:47 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-12 (798 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (57 days ago)

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

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

[Touch-packages] [Bug 1434424] [NEW] [34382AG, Realtek ALC269VC, Speaker, Internal] Pulseaudio fails to detect card

[Rüdiger Kupper]

Public bug reported:

Only sound device listed is "Dummy Output".
The problem appeared with the last software update.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: pulseaudio 1:4.0-0ubuntu22
ProcVersionSignature: Ubuntu 3.16.0-31.43-lowlatency 3.16.7-ckt5
Uname: Linux 3.16.0-31-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
1:
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Fri Mar 20 08:51:10 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-04-12 (706 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Title: [34382AG, Realtek ALC269VC, Speaker, Internal] Pulseaudio fails to 
detect card
UpgradeStatus: Upgraded to utopic on 2014-10-24 (146 days ago)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET92WW (2.52 )
dmi.board.asset.tag: Not Available
dmi.board.name: 34382AG
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET92WW(2.52):bd02/25/2013:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 34382AG
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug utopic

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

Title:
  [34382AG, Realtek ALC269VC, Speaker, Internal] Pulseaudio fails to
  detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Only sound device listed is "Dummy Output".
  The problem appeared with the last software update.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu22
  ProcVersionSignature: Ubuntu 3.16.0-31.43-lowlatency 3.16.7-ckt5
  Uname: Linux 3.16.0-31-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', 
'/dev/snd/controlC29', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 
1:
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri Mar 20 08:51:10 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-12 (706 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [34382AG, Realtek ALC269VC, Speaker, Internal] Pulseaudio fails to 
detect card
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (146 days ago)
  dmi.bios.date: 02/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34382AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET92WW(2.52):bd02/25/2013:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 34382AG
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1410253] [NEW] nm-applet crashes upon activating mobile broadband device

[Rüdiger Kupper]

Public bug reported:

Selecting "activate mobile broadband" from the nm-applet-indicator reproducibly 
crashes nm-applet. (Indicator symbol disappears.)
The mobile device is nonetheless activated.
nm-applet can be restartet from the commandline.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu28
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 13 14:08:24 2015
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (640 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 10.40.33.42 dev wwan0  proto static 
 10.40.33.40/29 dev wwan0  proto kernel  scope link  src 10.40.33.44  metric 13
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to utopic on 2014-10-24 (81 days ago)
WifiSyslog:
 
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 ttyACM1gsm   connected 
/org/freedesktop/NetworkManager/Devices/2  
 wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

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

Title:
  nm-applet crashes upon activating mobile broadband device

Status in network-manager package in Ubuntu:
  New

Bug description:
  Selecting "activate mobile broadband" from the nm-applet-indicator 
reproducibly crashes nm-applet. (Indicator symbol disappears.)
  The mobile device is nonetheless activated.
  nm-applet can be restartet from the commandline.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu28
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 13 14:08:24 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-04-12 (640 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 10.40.33.42 dev wwan0  proto static 
   10.40.33.40/29 dev wwan0  proto kernel  scope link  src 10.40.33.44  metric 
13
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (81 days ago)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   ttyACM1gsm   connected 
/org/freedesktop/NetworkManager/Devices/2  
   wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Touch-packages] [Bug 1161136] Re: Dash: searching for files and folders does not work

[Rüdiger Kupper]

Not reproducible in 14.10. Closing.

** Changed in: unity (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  Dash: searching for files and folders does not work

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Whatever I type in the dash's search bar, it always  returns the same
  results for files&folders.

  I.e.:
  1. in the files&folders lens, typing any search phrase has no effect 
whatsoever on the results.
  2. in the home lens, typing a search phrase changes results for applications, 
music, etc. but *does not change* results for files&folders.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,vpswitch,resize,mousepoll,place,move,grid,compiztoolbox,obs,gnomecompat,imgpng,shift,regex,wall,session,unitymtgrabhandles,animation,expo,ezoom,workarounds,fade,scale,unityshell,addhelper]
  Date: Wed Mar 27 23:46:36 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-20 (97 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 704123] Re: Network Manager asks for the PIN even if it is memorized

[Rüdiger Kupper]

I confirm that the PIN prompt does appear over again. It even pops up at
the login screen, as Daniel described in comment #40.

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

Title:
  Network Manager asks for the PIN even if it is memorized

Status in One Hundred Papercuts:
  Triaged
Status in NetworkManager:
  New
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “network-manager” package in Debian:
  New

Bug description:
  
  HOW TO REPRODUCE
  

  1. Plug the USB modem into a port.

  2. When you are asked to enter the modem's PIN, do along with the
  "automatically unlock this device" option.

  3. Unplug the modem, and plug it again.

  **
  EXPECTED BEHAVIOUR
  **

  - The modem to be automatically unlocked.

  **
  REAL BEHAVIOUR
  **

  - You are asked to enter the PIN again.

  
  WORK-AROUNDS
  

  - Changing the SIM's PIN to empty.

  - Renaming the "/usr/share/nm-applet/gsm-unlock.ui" file.

  
  
  RELEVANT DETAILS
  

  - The same behaviour when configuring the PIN from the "Network
  Connections" menu.

  - Even if the PIN is stored in "/etc/NetworkManager/system-
  connections/", Network Manager cannot retrieve it.

  - The bug makes the device to become locked as soon as network
  connectivity is lost for a while.

  - This bug forces administrators to tell the PIN to other users, while
  they will rather want to keep it in secret and just allow themselves
  to be able to configure the connectivity in specific devices.

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

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

[Touch-packages] [Bug 1345597] [NEW] On a Thinkpad X230 tablet, the "rotate" bezel button does not rotate touch device

[Rüdiger Kupper]

Public bug reported:

In Trusty, pressing the "rotate" button on the bezel of a Thinkpad X230 tablet
- rotates the orientation of the display in steps of 90°
- rotates the orientation of the input device for the stylus accordingly (which 
is good, it did not work in saucy)
- BUT it does NOT rotate the orientation of the touch screen device (which 
makes using the touch screen impossible)

Please do rotate the orientation of the touch screen input device
synchronously with screen orientation. This will be such a useful
feature, once it works!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jul 20 16:14:17 2014
DistUpgraded: 2014-04-18 10:31:00,413 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2203]
InstallationDate: Installed on 2013-04-12 (463 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: LENOVO 34382AG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/vg-lv--root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-04-18 (93 days ago)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GCET92WW (2.52 )
dmi.board.asset.tag: Not Available
dmi.board.name: 34382AG
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGCET92WW(2.52):bd02/25/2013:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 34382AG
dmi.product.version: ThinkPad X230 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sun Jul 20 15:56:47 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  On a Thinkpad X230 tablet, the "rotate" bezel button does not rotate
  touch device

Status in “xorg” package in Ubuntu:
  New

Bug description:
  In Trusty, pressing the "rotate" button on the bezel of a Thinkpad X230 tablet
  - rotates the orientation of the display in steps of 90°
  - rotates the orientation of the input device for the stylus accordingly 
(which is good, it did not work in saucy)
  - BUT it does NOT rotate the orientation of the touch screen device (which 
makes using the touch screen impossible)

  Please do rotate the orientation of the touch screen input device
  synchronously with screen orientation. This will be such a useful
  feature, once it works!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul 20 16:14:17 2014
  Dis