[Touch-packages] [Bug 1995757] [NEW] Overview of the application icon size error

2022-11-05 Thread Zhang
Public bug reported:

But after I turned on the Dock's auto-hide, the size of the app icons in
the overview became significantly smaller.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov  5 18:08:41 2022
DistUpgraded: Fresh install
DistroCodename: kinetic
DistroVariant: ubuntu
DkmsStatus:
 asg_xdroid/2.0, 5.19.0-23-generic, x86_64: installed
 ashmem_xdroid/2.0, 5.19.0-23-generic, x86_64: installed
 binder_xdroid/2.0, 5.19.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Alder Lake-P Integrated Graphics Controller 
[1043:1213]
InstallationDate: Installed on 2022-11-05 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:5463 IMC Networks USB2.0 HD UVC WebCam
 Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless 
rechargeable vertical mouse [More]
 Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. Adol_ADOLBOOK I1403ZA_ADOL14ZA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=d0016f25-a431-42d3-9bdc-c8652f0ed6c9 ro quiet splash 
systemd.unified_cgroup_hierarchy=0 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2022
dmi.bios.release: 5.25
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: I1403ZA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: I1403ZA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrI1403ZA.302:bd09/06/2022:br5.25:svnASUSTeKCOMPUTERINC.:pnAdol_ADOLBOOKI1403ZA_ADOL14ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnI1403ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Adolbook
dmi.product.name: Adol_ADOLBOOK I1403ZA_ADOL14ZA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug kinetic ubuntu wayland-session

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

Title:
  Overview of the application icon size error

Status in xorg package in Ubuntu:
  New

Bug description:
  But after I turned on the Dock's auto-hide, the size of the app icons
  in the overview became significantly smaller.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  5 18:08:41 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus:
   asg_xdroid/2.0, 5.19.0-23-generic, x86_64: installed
   ashmem_xdroid/2.0, 5.19.0-23-generic, x86_64: installed
   binder_xdroid/2.0, 5.19.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Alder Lake-P Integrated Graphics 
Controller [1043:1213]
  InstallationDate: Installed on 2022-11-05 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:5463 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz 

[Touch-packages] [Bug 1973424] [NEW] ibus-extension-gtk3 does not start automatically

2022-05-14 Thread Zhang
Public bug reported:

ibus-extension-gtk3 does not start automatically, which causes the
candidate box of the Ibus input method to not follow the cursor of any
gtk application.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ibus 1.5.26-4
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat May 14 22:18:41 2022
InstallationDate: Installed on 2022-04-23 (21 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

** Summary changed:

- ibus-extension-gtk3
+ ibus-extension-gtk3 does not start automatically

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

Title:
  ibus-extension-gtk3 does not start automatically

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-extension-gtk3 does not start automatically, which causes the
  candidate box of the Ibus input method to not follow the cursor of any
  gtk application.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-4
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 14 22:18:41 2022
  InstallationDate: Installed on 2022-04-23 (21 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1969868] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-04-21 Thread Zhang Zheng Fu
Public bug reported:

I don't have anymore details.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Apr 21 14:05:23 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2022-03-01 (51 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I don't have anymore details.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Apr 21 14:05:23 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-03-01 (51 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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


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


[Touch-packages] [Bug 1967145] Re: Keyboard keys are misfiring

2022-03-30 Thread Zhang
I have found that this is only an issue in Wayland sessions. In the Gdm3
interface, and in other ttys there is no such problem

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

Title:
  Keyboard keys are misfiring

Status in console-setup package in Ubuntu:
  New

Bug description:
  My keyboard is a standard 104 layout, but when I press ~, it will type into ¬.
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: keyboard-configuration 1.205ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 22:42:39 2022
  InstallationDate: Installed on 2022-02-09 (48 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Keyboard:
   BACKSPACE="guess"
   XKBLAYOUT="cn"
   XKBMODEL="pc104"
   XKBVARIANT="altgr-pinyin"
   XKBOPTIONS=""
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1967145] [NEW] Keyboard keys are misfiring

2022-03-30 Thread Zhang
Public bug reported:

My keyboard is a standard 104 layout, but when I press ~, it will type into ¬.
Wayland

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: keyboard-configuration 1.205ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 22:42:39 2022
InstallationDate: Installed on 2022-02-09 (48 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Keyboard:
 BACKSPACE="guess"
 XKBLAYOUT="cn"
 XKBMODEL="pc104"
 XKBVARIANT="altgr-pinyin"
 XKBOPTIONS=""
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Keyboard keys are misfiring

Status in console-setup package in Ubuntu:
  New

Bug description:
  My keyboard is a standard 104 layout, but when I press ~, it will type into ¬.
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: keyboard-configuration 1.205ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 22:42:39 2022
  InstallationDate: Installed on 2022-02-09 (48 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Keyboard:
   BACKSPACE="guess"
   XKBLAYOUT="cn"
   XKBMODEL="pc104"
   XKBVARIANT="altgr-pinyin"
   XKBOPTIONS=""
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"

2022-03-29 Thread Zhang
.-/+oooo+/-.   xiaozhangup@xiaozhangup 
`:+ss+:`   --- 
  -+ssyy+- OS: Ubuntu Jammy Jellyfish (developm 
.ossdMMMNyo.   Kernel: 5.15.0-23-generic 
   /ssshdmmNNmmyNhss/  Uptime: 1 hour, 32 mins 
  +shmydMMMNy+ Packages: 2135 (dpkg), 15 (snap) 
 /hNMMMyhhhmNMMMNh/Shell: bash 5.1.16 
.dMMMNhsshNMMMd.   Resolution: 1600x900 
+hhhyNMMNyyNMMMysss+   DE: GNOME 
ossyNMMMNyMMhsshmmmhssso   WM: Mutter 
ossyNMMMNyMMhsshmmmhssso   WM Theme: Adwaita 
+hhhyNMMNyyNMMMysss+   Theme: Yaru-prussiangreen-dark [GTK2 
.dMMMNhsshNMMMd.   Icons: Yaru-prussiangreen [GTK2/3] 
 /hNMMMyhhhdNMMMNh/Terminal: gnome-terminal 
  +sdmydy+ CPU: Intel i3-3220 (4) @ 3.300GHz 
   /ssshdmmyNhss/  GPU: Intel HD Graphics 
.ossdMMMNyo.   Memory: 2799MiB / 7627MiB 
  -+syyy+-
`:+ss+:`   
.-/+oooo+/-.   


My computer information, maybe it helps?

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

Title:
  gnome-extensions-app crashes with "Segmentation fault (core dumped)"

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  when I use the command "gnome-extensions-app" in command line ,it will
  crash and report "Segmentation fault (core dumped)"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-prefs 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 22:32:21 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-02-09 (42 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
Both Xorg and Wayland can be solved this way, and this is what I just tested 
out.
They both seem to have this problem, but both can be solved this way.

Thank you for your positive response and help!

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
Everything is just as you said it would be.And it correctly on Microsoft
Edge.

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
Not just Edge, but all applications

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-27 Thread Zhang
This is indeed a problem caused by the environment, but I found that my 
/etc/environment file was blank.
I did various tests and could finally determine that this would fix the problem 
directly.

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-26 Thread Zhang
https://zh.opensuse.org/SDB:%E5%9C%A8_Wayland_%E4%B8%AD%E5%90%AF%E7%94%A8%E8%BE%93%E5%85%A5%E6%B3%95

This will fix the bug

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966552] Re: IBus input method candidate box cannot follow the cursor

2022-03-26 Thread Zhang
Indeed, all of the included applications were fine, so I pointed out
other software, such as Microsoft Edge. i now go upstream to submit the
problem

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

Title:
  IBus input method candidate box cannot follow the cursor

Status in ibus package in Ubuntu:
  New
Status in ibus-libpinyin package in Ubuntu:
  New

Bug description:
  I have tested it in some software, such as Microsoft Edge, Onlyoffice,
  and it does not follow the cursor position correctly, but always at
  the bottom left of the application window. However, in some
  applications such as Gedit, it works fine.

  Pictures are here:https://i.bmp.ovh/imgs/2022/03/34ebb5158ceeedfc.png

  OS: Ubuntu Jammy Jellyfish
  Kernel: 5.15.0-23-generic
  on Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus-libpinyin 1.12.1-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 23:59:28 2022
  InstallationDate: Installed on 2022-02-09 (45 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966548] Re: Ubuntu 22.04 input can't work

2022-03-26 Thread Zhang
it become normal on wayland

** Changed in: ibus (Ubuntu)
   Status: New => Fix Released

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

Title:
  Ubuntu 22.04 input can't work

Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  I can;t entre Chinese in any applications.
  No matter how I pree my keyboard, only the original letter will be entered.
  This is what happended after I updated the package yesterday, that is, 
everything is normal before yesterday.I have not modified any settings.
  Interestingly, in the popup menu after I press Alt+F2, I can type Chinese 
normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 20:20:08 2022
  InstallationDate: Installed on 2022-02-09 (44 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1966548] [NEW] Ubuntu 22.04 input can't work

2022-03-26 Thread Zhang
Public bug reported:

I can;t entre Chinese in any applications.
No matter how I pree my keyboard, only the original letter will be entered.
This is what happended after I updated the package yesterday, that is, 
everything is normal before yesterday.I have not modified any settings.
Interestingly, in the popup menu after I press Alt+F2, I can type Chinese 
normal.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ibus 1.5.26-2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 26 20:20:08 2022
InstallationDate: Installed on 2022-02-09 (44 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Ubuntu 22.04 input can't work

Status in ibus package in Ubuntu:
  New

Bug description:
  I can;t entre Chinese in any applications.
  No matter how I pree my keyboard, only the original letter will be entered.
  This is what happended after I updated the package yesterday, that is, 
everything is normal before yesterday.I have not modified any settings.
  Interestingly, in the popup menu after I press Alt+F2, I can type Chinese 
normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 26 20:20:08 2022
  InstallationDate: Installed on 2022-02-09 (44 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell

2021-12-27 Thread Chaoqi Zhang
Still not fixed on 2022-12-27. Ubuntu 20.04 LTS 64-bits. NetworkManager
version 1.22.10.

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

Title:
  Problem to connect to WPA2/PEAP WIFI  - gnome-shell

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This problem is also happened on my desktop.

  After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC
  could not connect and authenticate on WiFi with  WPA2/PEAP/MSCHAPv2/no
  CA certificate/true username and password.

  
  I tried to solve the  problem following URL link; however, it could not help 
me also. 
  
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
 

  
  My PC  is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, 
OS: Ubuntu 18.04.1 (64-bit).

  root@joe-UBTPC:/root # lspci

  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
  00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 5 (rev b5)
  00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 6 (rev b5)
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC 
Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family SATA AHCI Controller (rev 05)
  00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus 
Controller (rev 05)
  03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter
  06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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


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


[Touch-packages] [Bug 1925827] Re: [v247] backport routing policy rule fix

2021-07-12 Thread Zhang Youfu
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem.

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

Title:
  [v247] backport routing policy rule fix

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [impact]

  routing policy rules not correctly configured

  [test case]

  more detail in upstream bug linked from original description.

  configure interface with:

  [Match]
  Name = ens3

  [Network]
  Address = 10.0.0.1/32

  [RoutingPolicyRule]
  Family = both
  IncomingInterface = ens3
  Table = 42
  Priority = 42

  
  then networkctl reload. then update the network file with:

  [Route]
  Table = 42
  Destination = 10.0.0.0/24
  Gateway = 0.0.0.0

  and run networkctl reload again, checking systemd-networkd for error.

  [regression potential]

  failure to properly configure networking in general, or policy routes.

  [scope]

  this is needed only for h.

  this is fixed already in i, and this is not reproducable in g.

  see original descrption for link to specific upstream issue and pr.

  [original description]

  The original issue can be found at 
https://github.com/systemd/systemd/issues/18107.
  I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which got merged and released in v247.4.
  However due to the freezing state of Debian bullseye, upstream systemd 
package is frozen at v247.3.
  Please apply this patchset for Ubuntu if possible.
  Thanks.

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

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


[Touch-packages] [Bug 1925827] Re: [v247] backport routing policy rule fix

2021-07-12 Thread Zhang Youfu
Tested systemd 247.3-3ubuntu3.2 on hirsute, without problem.

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

Title:
  [v247] backport routing policy rule fix

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Committed

Bug description:
  [impact]

  routing policy rules not correctly configured

  [test case]

  more detail in upstream bug linked from original description.

  configure interface with:

  [Match]
  Name = ens3

  [Network]
  Address = 10.0.0.1/32

  [RoutingPolicyRule]
  Family = both
  IncomingInterface = ens3
  Table = 42
  Priority = 42

  
  then networkctl reload. then update the network file with:

  [Route]
  Table = 42
  Destination = 10.0.0.0/24
  Gateway = 0.0.0.0

  and run networkctl reload again, checking systemd-networkd for error.

  [regression potential]

  failure to properly configure networking in general, or policy routes.

  [scope]

  this is needed only for h.

  this is fixed already in i, and this is not reproducable in g.

  see original descrption for link to specific upstream issue and pr.

  [original description]

  The original issue can be found at 
https://github.com/systemd/systemd/issues/18107.
  I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which got merged and released in v247.4.
  However due to the freezing state of Debian bullseye, upstream systemd 
package is frozen at v247.3.
  Please apply this patchset for Ubuntu if possible.
  Thanks.

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

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


[Touch-packages] [Bug 1897365] Re: RoutingPolicyRule not applied on reconfigure

2021-06-29 Thread Zhang Youfu
Per my testing, restart systemd-networkd is also affected.

Debian maintainer refused to apply my backport due to patch size.
https://github.com/systemd/systemd-stable/pull/96

That’s fair.

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

Title:
  RoutingPolicyRule not applied on reconfigure

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd source package in Groovy:
  Won't Fix

Bug description:
  I noticed some error message from systemd-networkd in log journal.

  systemd-networkd[4343]: Failed to parse RPDB rule family, ignoring:
  AF_INETpriority=28fwmark=28/0

  This appears to be a known issue at 
https://github.com/systemd/systemd/issues/16784
  Fix is available at https://github.com/systemd/systemd/pull/16986

  Please backport the fix, thx.

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

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


[Touch-packages] [Bug 1925827] Re: [v247] backport routing policy rule fix

2021-05-22 Thread Zhang Youfu
> I'm able to reproduce this on hirsute, but not groovy, so this seems to 
> affect only hirsute; please correct me if that's wrong.
That’s correct.

> only 'networkctl reload' doesn't work, normal systemd-networkd startup works
`systemctl restart systemd-networkd` doesn’t work either.

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

Title:
  [v247] backport routing policy rule fix

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Hirsute:
  Triaged

Bug description:
  The original issue can be found at 
https://github.com/systemd/systemd/issues/18107.
  I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which got merged and released in v247.4.
  However due to the freezing state of Debian bullseye, upstream systemd 
package is frozen at v247.3.
  Please apply this patchset for Ubuntu if possible.
  Thanks.

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

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


[Touch-packages] [Bug 1925827] [NEW] [v247] backport routing policy rule fix

2021-04-23 Thread Zhang Youfu
Public bug reported:

The original issue can be found at 
https://github.com/systemd/systemd/issues/18107.
I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which got merged and released in v247.4.
However due to the freezing state of Debian bullseye, upstream systemd package 
is frozen at v247.3.
Please apply this patchset for Ubuntu if possible.
Thanks.

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


** Tags: systemd-networkd

** Patch added: "96.patch"
   https://bugs.launchpad.net/bugs/1925827/+attachment/5491460/+files/96.patch

** Description changed:

  The original issue can be found at 
https://github.com/systemd/systemd/issues/18107.
- I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which get merged and released in v247.4.
+ I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which got merged and released in v247.4.
  However due to the freezing state of Debian bullseye, upstream systemd 
package is frozen at v247.3.
  Please apply this patchset for Ubuntu if possible.
  Thanks.

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

Title:
  [v247] backport routing policy rule fix

Status in systemd package in Ubuntu:
  New

Bug description:
  The original issue can be found at 
https://github.com/systemd/systemd/issues/18107.
  I filed a backport PR (https://github.com/systemd/systemd-stable/pull/96) 
against v247-stable branch, which got merged and released in v247.4.
  However due to the freezing state of Debian bullseye, upstream systemd 
package is frozen at v247.3.
  Please apply this patchset for Ubuntu if possible.
  Thanks.

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

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


[Touch-packages] [Bug 1768755] Re: Missing links to libGL.so and libglapi.so

2020-12-03 Thread Hongda Zhang
libglvnd-dev only provide libGL.so, but not libapi.so!

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

Title:
  Missing links to libGL.so and libglapi.so

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  In Ubuntu 18.04, the package libgl1-mesa-dev:amd64 does not contain
  the symbolic links libGL.so and libglapi.so.

  Thus, it is not possible to use the -lGL option to compile a
  program...

  System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit
  Package: libgl1-mesa-dev:amd64 18.0.0~rc5-1ubuntu1

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

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


[Touch-packages] [Bug 1897365] Re: RoutingPolicyRule not applied on reconfigure

2020-10-11 Thread Zhang Youfu
And https://github.com/systemd/systemd/pull/16881
Not available in systemd-stable v246 yet.

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

Title:
  RoutingPolicyRule not applied on reconfigure

Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed some error message from systemd-networkd in log journal.

  systemd-networkd[4343]: Failed to parse RPDB rule family, ignoring:
  AF_INETpriority=28fwmark=28/0

  This appears to be a known issue at 
https://github.com/systemd/systemd/issues/16784
  Fix is available at https://github.com/systemd/systemd/pull/16986

  Please backport the fix, thx.

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

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


[Touch-packages] [Bug 1897365] [NEW] RoutingPolicyRule not applied on reconfigure

2020-09-26 Thread Zhang Youfu
Public bug reported:

I noticed some error message from systemd-networkd in log journal.

systemd-networkd[4343]: Failed to parse RPDB rule family, ignoring:
AF_INETpriority=28fwmark=28/0

This appears to be a known issue at 
https://github.com/systemd/systemd/issues/16784
Fix is available at https://github.com/systemd/systemd/pull/16986

Please backport the fix, thx.

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

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

Title:
  RoutingPolicyRule not applied on reconfigure

Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed some error message from systemd-networkd in log journal.

  systemd-networkd[4343]: Failed to parse RPDB rule family, ignoring:
  AF_INETpriority=28fwmark=28/0

  This appears to be a known issue at 
https://github.com/systemd/systemd/issues/16784
  Fix is available at https://github.com/systemd/systemd/pull/16986

  Please backport the fix, thx.

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

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


[Touch-packages] [Bug 1859739] [NEW] package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 - 仍未被配置

2020-01-14 Thread zhang
Public bug reported:

when I open the system,it would tell me this question

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ubuntu-minimal 1.361.4
ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Wed Jan 15 10:12:17 2020
ErrorMessage: 依赖关系问题 - 仍未被配置
InstallationDate: Installed on 2019-12-17 (28 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: ubuntu-meta
Title: package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 - 仍未被配置
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 -
  仍未被配置

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  when I open the system,it would tell me this question

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-minimal 1.361.4
  ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Wed Jan 15 10:12:17 2020
  ErrorMessage: 依赖关系问题 - 仍未被配置
  InstallationDate: Installed on 2019-12-17 (28 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: ubuntu-meta
  Title: package ubuntu-minimal 1.361.4 failed to install/upgrade: 依赖关系问题 - 
仍未被配置
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1859740] [NEW] package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 10

2020-01-14 Thread zhang
Public bug reported:

when I open the system,it would tell me this question

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.16.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Wed Jan 15 10:12:17 2020
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 10
InstallationDate: Installed on 2019-12-17 (28 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: rsyslog
Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 10
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.d.rsyslog: 2016-02-03T18:55:28

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


** Tags: amd64 apport-package xenial

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

Title:
  package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 10

Status in rsyslog package in Ubuntu:
  New

Bug description:
  when I open the system,it would tell me this question

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: rsyslog 8.16.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-74.83~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Wed Jan 15 10:12:17 2020
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 10
  InstallationDate: Installed on 2019-12-17 (28 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: rsyslog
  Title: package rsyslog 8.16.0-1ubuntu3.1 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 10
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.d.rsyslog: 2016-02-03T18:55:28

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

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


[Touch-packages] [Bug 1856953] [NEW] Misconfigured Debian control file makes dist-upgrading with package libdbusmenu-qt5 crash

2019-12-18 Thread Tianyun Zhang
Public bug reported:

Dear maintainers,

Lacking of `Breaks` and `Replaces` parts in the Debian control file of
libdbusmenu-qt5-2 package (version 0.9.3+16.04.20160218-2) would make
dist-upgrading from Xenial (with libdbusmenu-qt5 installed) to Eoan or
Focal crash.

Expected behavior of dist-upgrading:
- should deconfigure `libdbusmenu-qt5` first
- only then can `libdbusmenu-qt5-2` be installed

What happened instead:
- dpkg unpacks `libdbusmenu-qt5-2` over files of `libdbusmenu-qt5`, thus 
causing a crash

Steps to reproduce:
1. install a fresh Ubuntu 16.04.6 and upgrade packages
2. change the release in apt source list from `xenial` to `eoan` or `focal` and 
include universe section
3. perform `apt dist-upgrade`

** Affects: libdbusmenu-qt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Misconfigured Debian control file makes dist-upgrading with package
  libdbusmenu-qt5 crash

Status in libdbusmenu-qt package in Ubuntu:
  New

Bug description:
  Dear maintainers,

  Lacking of `Breaks` and `Replaces` parts in the Debian control file of
  libdbusmenu-qt5-2 package (version 0.9.3+16.04.20160218-2) would make
  dist-upgrading from Xenial (with libdbusmenu-qt5 installed) to Eoan or
  Focal crash.

  Expected behavior of dist-upgrading:
  - should deconfigure `libdbusmenu-qt5` first
  - only then can `libdbusmenu-qt5-2` be installed

  What happened instead:
  - dpkg unpacks `libdbusmenu-qt5-2` over files of `libdbusmenu-qt5`, thus 
causing a crash

  Steps to reproduce:
  1. install a fresh Ubuntu 16.04.6 and upgrade packages
  2. change the release in apt source list from `xenial` to `eoan` or `focal` 
and include universe section
  3. perform `apt dist-upgrade`

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

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


[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-30 Thread Zhang Youfu
filed an upstream issue

** Bug watch added: github.com/systemd/systemd/issues #13882
   https://github.com/systemd/systemd/issues/13882

** Changed in: systemd
   Status: Fix Released => Unknown

** Changed in: systemd
 Remote watch: github.com/systemd/systemd/issues #12886 => 
github.com/systemd/systemd/issues #13882

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

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  when a networkd interface is configured with LinkLocalAddressing=no,
  networkd still assigns a link-local address to it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.

  [regression potential]

  this moves the point when ipv6ll is configured; regressions would most
  likely involve failure to correctly configure an ipv6ll address when
  desired.

  [other info]

  this bug was attempted to be fixed by 
'debian/patches/networkd-honour-LinkLocalAddressing.patch' from upstream issue 
9890, using a commit that does not correctly fix the issue and was never 
accepted upstream:
  https://github.com/systemd/systemd/issues/9890#issuecomment-455168751

  this SRU completely reverts that patch, and adds the correct fix which
  was merged upstream:
  
https://github.com/systemd/systemd/commit/0e2fdb83bb5e22047e0c7cc058b415d0e93f02cf

  that commit is already included in Eoan so this sru is needed only for
  Disco.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

2019-10-12 Thread Zhang Youfu
For my installation, I found that dnsmasq is running with -7
/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new arguments.

/etc/dnsmasq.d/libvirt-daemon specified bind-interfaces, causing dnsmasq
trying to bind to each interface on startup, which was unfortunately not
available yet.

Comment out the CONFIG_DIR= directive in /etc/default/dnsmasq works for
me.

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

Title:
  [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

Status in One Hundred Papercuts:
  Confirmed
Status in dnsmasq package in Ubuntu:
  Confirmed
Status in dnsmasq package in Debian:
  New

Bug description:
  [Impact]
  dnsmasq will fail to respond on network devices that weren't up when its
  service started, thus not binding as expected.

  [Test Case]
  TBD

  [Regression Potential]
  The fix is just configuring the order of service startup, so is unlikely to 
create any regressions.  Things to watch would be service related misbehaviors 
and general availability of the dnsmasq functionality.

  [Fix]
  Straightforward packaging fix to the service to make it delay startup
  until after the network is online.

  https://bugs.debian.org/cgi-
  bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-
  online.debdiff;msg=22

  [Discussion]

  [Original Report]
  My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is 
managed manually in /etc/network/interfaces.

  During boot, dnsmasq is started before br-vz0 is created and this
  causes dnsmasq to exit:

  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0
  Jan  5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up
  Jan  5 08:56:17 simon-laptop NetworkManager[937]:   NetworkManager 
(version 1.0.4) is starting...
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]: 
interface-parser: parsing file /etc/network/interfaces
  ...
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   found bridge ports 
none for br-vz0
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   adding bridge port 
none to eni_ifaces
  Jan  5 08:56:18 simon-laptop NetworkManager[937]:   management mode: 
unmanaged

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq 2.75-1
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan  5 09:53:30 2016
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-05 Thread Zhang Youfu
This issue also affects 18.04 LTS with systemd 237-3ubuntu10.29
A VLAN interface with LinkLocalAddressing=no configured is not honored

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

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Disco:
  New

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-04 Thread Zhang Youfu
After upgraded to Ubuntu 19.10 with systemd 242-6ubuntu1, the issue I
encountered disappeared.

```
# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc fq_codel state UP group default 
qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.50.249/24 brd 192.168.50.255 scope global eno1
   valid_lft forever preferred_lft forever
3: wlp58s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 40:a3:cc:22:45:25 brd ff:ff:ff:ff:ff:ff
4: pppoe@eno1:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
```

Now pppoe interface does not get IPv6 link-local address.

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

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

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-10-04 Thread Zhang Youfu
I'm running Ubuntu 19.04 with systemd 240-6ubuntu5.7

systemd-networkd configuration:
```
# eno1.network
[Match]
Name=eno1

[Link]
Multicast=no

[Network]
LinkLocalAddressing=no
Address=192.168.50.249/24
Gateway=192.168.50.1
DNS=192.168.50.1
VLAN=pppoe

# pppoe.netdev
[NetDev]
Name=pppoe
Kind=vlan

[VLAN]
Id=1006

# pppoe.network
[Match]
Name=pppoe

[Link]
Multicast=no
ARP=no

[Network]
LinkLocalAddressing=no
```

result:
```
# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc fq_codel state UP group default 
qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
inet 192.168.50.249/24 brd 192.168.50.255 scope global eno1
   valid_lft forever preferred_lft forever
3: wlp58s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 40:a3:cc:22:45:25 brd ff:ff:ff:ff:ff:ff
4: pppoe@eno1:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
link/ether 94:c6:91:18:8c:3c brd ff:ff:ff:ff:ff:ff
inet6 fe80::96c6:91ff:fe18:8c3c/64 scope link
   valid_lft forever preferred_lft forever
5: docker0:  mtu 1500 qdisc noqueue state 
DOWN group default
link/ether 02:42:3c:35:9c:76 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
   valid_lft forever preferred_lft forever
```

The pppoe interface still got an IPv6 link-local address.

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

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

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Zhang Youfu
Emm, I think the issue I referenced above is an incorrect one.

https://github.com/systemd/systemd/issues/9890
&
https://github.com/systemd/systemd/pull/11423

I think `debian/patches/networkd-honour-LinkLocalAddressing.patch` might
be an incorrect backport of this upstream bug.

** Bug watch added: github.com/systemd/systemd/issues #9890
   https://github.com/systemd/systemd/issues/9890

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd package in Ubuntu:
  New

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1845909] [NEW] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Zhang Youfu
Public bug reported:

upstream issue: https://github.com/systemd/systemd/issues/12886
upstream patch: https://github.com/systemd/systemd/pull/13565

The upstream fix will be available in systemd 244.
Backport please. Thanks.

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

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd package in Ubuntu:
  New

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

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


[Touch-packages] [Bug 1824739] [NEW] Xorg freeze

2019-04-14 Thread ZHANG TIANYANG
Public bug reported:

The computer is not able to resume after suspend.
The screen brightness is not able to be adjusted

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
Uname: Linux 5.0.0-05-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 06:18:34 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: I don't know
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0]
InstallationDate: Installed on 2018-06-27 (291 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b718 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 13d3:5654 IMC Networks 
 Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL553VD
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-05-generic 
root=UUID=efd91b16-1bc9-46b5-805f-5994b58f82f6 ro nouveau.modeset=0 
nouveau.blacklist=1 quiet splash nomodeset acpi_backlight=vendor 
nouveau.modeset=0 nouveau.blacklist=1 vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL553VD.306
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL553VD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL553VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic freeze possible-manual-nvidia-install 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/1824739

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  The computer is not able to resume after suspend.
  The screen brightness is not able to be adjusted

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  Uname: Linux 5.0.0-05-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 06:18:34 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:15e0]
  InstallationDate: Installed on 2018-06-27 (291 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b718 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 13d3:5654 IMC Networks 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-05-generic 
root=UUID=efd91b16-1bc9-46b5-805f-5994b58f82f6 ro 

[Touch-packages] [Bug 1692353] Re: systemd-fsckd : useless CR displayed on console

2019-03-20 Thread Zhang Youfu
This bug still exists in 19.04 Disco. Please fix it.

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

Title:
  systemd-fsckd : useless CR displayed on console

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hello,

  My system is "Ubuntu 16.04.2 LTS" (grep DISTRIB_DESCRIPTION /etc/lsb-
  release).

  The systemd package is installed:
$ dpkg -l | grep systemd
> systemd 229-4ubuntu17 

  I noticed that approximately 15 seconds after the boot, a useless
  Carriage Return ('\r') is displayed on the console (/dev/console).
  This character interacts with the display of the user currently logued in
  on the console. This screws the current line, when users is pressing keys.

  After monitoring system activity, I found the culprit:
/lib/systemd/system/systemd-fsckd.service

  To test, run:
service systemd-fsckd stop# In case, it is still running.
service systemd-fsckd start
  Go to the console, wait for approximately 15 seconds, and you see the cursor
  jumping from its current position to the beginning of the line. This is the 
BUG.
  Note: the console is not the X11 terminal (xterm, lxterminal, etc.) ; the
  console is the text tty reached with Control-Alt-F1.

  The systemd-fsckd.service starts the following daemon:
/lib/systemd/systemd-fsckd
  This is the daemon which displays two useless '\r' characters.

  I went to:
http://packages.ubuntu.com/xenial/systemd

  I downloaded:

http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu10.debian.tar.xz

  The file debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch
  contains:
  +static int manager_write_console(Manager *m, const char *message) {
  [...]
  +if (message) {
  +fprintf(console, "\r%s\r%n", message, );
  +if (m->clear  < (size_t)l)
  +m->clear = (size_t)l;
  +} else {
  +fputc('\r', console);
  +for (j = 0; j < m->clear; j++)
  +fputc(' ', console);
  +fputc('\r', console);
  +}

  So, when no message was previously displayed, "m->clear" is still set
  to 0.

  Then, when the program ends it calls:
  +/* clear last line */
  +manager_write_console(m, NULL);

  However, in the "else" above, two '\r' characters are displayed, surrounding
  no space characters.

  So, when no message was previously displayed, there is nothing to clear, so
  no '\r' character to display.

  A trivial patch is attached. It is untested.

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

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


[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

2018-07-04 Thread Hua Zhang
I simply add a non-empty value into crash file then I can bypass this
issue.

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged

Bug description:
  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:
   
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

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


[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

2018-07-04 Thread Hua Zhang
I run into the same problem in trusty, any workaround to bypass it ?

$ sudo apport-unpack 
_usr_lib_erlang_erts-5.10.4_bin_beam.smp.108.27June2018.crash ./core
Traceback (most recent call last): 
File "/usr/bin/apport-unpack", line 74, in  
pr.extract_keys(f, bin_keys, dir) 
File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in 
extract_keys 
[item for item, element in b64_block.items() if element is False]) 
ValueError: ['UserGroups'] has no binary content

Then this code dump can not be used because ./core/CoreDump is truncated: 
expected core file size >= 20734648320, found: 5708352522.
Cannot access memory at address 0x7fe8f266e1a8
Cannot access memory at address 0x7fe8f266e1a0
(gdb) bt
Python Exception  Cannot access memory at address 
0x7fe8eb9bd738: 
#0  0x7fe8f1345c37 in ?? ()
Cannot access memory at address 0x7fe8eb9bd738

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged

Bug description:
  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:
   
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

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


[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

2018-03-28 Thread Frederick Zhang
A, yup! That's the missing piece of the puzzle! I once had it ticked
because of the bug of plasma-nm and totally forgot that I later turned
it off. Thank you, Rahn!

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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

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


[Touch-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

2018-03-28 Thread Frederick Zhang
Sorry to jump in out of the blue, but may I know whether there are any
updates to this issue?

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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

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


[Touch-packages] [Bug 1753954] Re: Intel Whiskey Lake (WHL) graphics support

2018-03-07 Thread alex zhang
Whiskey Lake (WHL)
Package/pin compatible Quad core WHL (U42) or Dual core CNL (U22) design in 
common board with stuffing option Two versions of CPU Si will be compatible 
with this platform:
•   WHL U4+2 derived based on Coffelake-U with CNL-LP PCH
Use CFL-S/H code already in upstream(4.13-4.15)
PCI ID Changes: Graphics Related(v4.16)
•   Cannonlake Prime –U 2+2 w/ CNL-H PCH and CNL-LP PCH
Use CNL-Y features (4.13-4.16)

Please don't forget CNL-H based components. Above is what I got from
Intel.

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

Title:
  Intel Whiskey Lake (WHL) graphics support

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libdrm source package in Xenial:
  New
Status in linux-oem source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in libdrm source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  New
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  [Impact]
  WHL is basically CFL-U with new PCI-ID's that are needed in the kernel, 
libdrm, mesa and xserver.

  [Test Case]

  Test the installation on a WHL machine, the graphical session should
  have full acceleration after these updates.

  [Regression Potential]

  None, just adds PCI-ID's to existing drivers.

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

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


[Touch-packages] [Bug 1705884] Re: Black screen

2017-09-09 Thread W Zhang
I have this problem with Nvidia GeForce 1080 Ti. Driver version 381.22.
Ubuntu 16.04, kernel version 4.10.0-33-generic.

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

Title:
  Black screen

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  black screen when lock. Black screen not able to recover login info to
  re-enter gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jul 23 11:29:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 420] 
[174b:1162]
  InstallationDate: Installed on 2017-06-04 (49 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Packard Bell imedia S3810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic 
root=UUID=61dd95f6-c8ec-48c9-82fd-87eee44dd781 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: imedia S3810
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd08/19/2010:svnPackardBell:pnimediaS3810:pvr:rvnPackardBell:rnimediaS3810:rvr:cvnPackardBell:ct3:cvr:
  dmi.product.name: imedia S3810
  dmi.sys.vendor: Packard Bell
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1613193] Re: apt-get does't work with http_proxy

2017-07-25 Thread zhang sheng
Finally I find the problem is User-Agent string in apt-get.

see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355782

** Bug watch added: Debian Bug tracker #355782
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355782

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

Title:
  apt-get does't work with http_proxy

Status in apt package in Ubuntu:
  New

Bug description:
  I use lubuntu 16.04.
  $ uname -a
  Linux ubuntu 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l |grep apt
  ii  apt  1.2.10ubuntu1
amd64commandline package manager

  When I set "http_proxy" environment var and run "apt-get update", I get many 
"connection failed"
  Err:16 http://archive.ubuntu.com/ubuntu xenial/main Sources
Connection failed
  Err:17 http://archive.ubuntu.com/ubuntu xenial/restricted Sources
Connection failed
  Err:18 http://archive.ubuntu.com/ubuntu xenial/universe Sources
Connection failed
  Err:19 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources
Connection failed
  Err:20 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Connection failed
  Err:21 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages
Connection failed

  But I can use curl and wget to fetch website homepage.
  And in centos7, yum can work with 'http_proxy', I can update my centos7.

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

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


[Touch-packages] [Bug 1637333] Re: gnome-terminal crashes when tab is dragged onto another tab's terminal area

2017-05-07 Thread Huan Zhang
I am suffering from this bug for years, and it is still not fixed in
Ubuntu 17.04. It is very annoying because sometimes I accidentally drag
the tab and all programs in terminal get killed!

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

Title:
  gnome-terminal crashes when tab is dragged onto another tab's terminal
  area

Status in GNOME Terminal:
  Confirmed
Status in GTK+:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  This bug occurs when I drag an existing terminal tab out of the tab
  bar and drop it onto the text area of the open terminal. Usually
  occurs by accident, to be honest (when I don't mean to drag the tab at
  all, for instance) but it's 100% reproducible intentionally.

  I found several old bug reports on similar issues, but they were
  either not detailed enough to figure out if they were exactly the same
  or were closed as duplicates of a bug that no longer exists
  (https://bugs.launchpad.net/ubuntu/+source/gnome-
  terminal/+bug/1442826).

  Apport generated a report (title: gnome-terminal-server crashed with
  SIGABRT in g_assertion_message()) for me and then helpfully explained
  that the bug had already been filed. It redirected me to a bug that
  doesn't exist (https://bugs.launchpad.net/bugs/1595907) though, so I'm
  refiling it here.

  1. Ubuntu release:
  spyro@julep:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2. Package version:
  spyro@julep:~$ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.20.2-1ubuntu3~ubuntu16.04.1
Candidate: 3.20.2-1ubuntu3~ubuntu16.04.1
Version table:
   *** 3.20.2-1ubuntu3~ubuntu16.04.1 500
  500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu 
xenial/main amd64 Packages
  100 /var/lib/dpkg/status
   3.18.3-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  spyro@julep:~$ 

  3. Expected behavior: Tab should split into a new window (as it does
  if you drop it onto someplace that's not a gnome-terminal window). At
  the worst, it should go back to where it was on the tab bar instead of
  crashing.

  4. Actual behavior: The whole gnome-terminal window crashes, losing
  any activity or work on other tabs. Other open gnome-terminal windows
  also crash and close.

  From /var/log/syslog:
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  Lib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER 
(cont
  ainer)' failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  Lib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
(gnome-terminal-server:30721): G
  tk-CRITICAL **: gtk_container_get_focus_child: assertion 'GTK_IS_CONTAINER 
(cont
  ainer)' failed
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: **
  Oct 27 14:54:03 julep org.gnome.Terminal[2217]: 
Gtk:ERROR:/build/gtk+3.0-j0Vp0u/
  gtk+3.0-3.20.8/./gtk/gtkwidget.c:5830:gtk_widget_get_frame_clock: assertion 
fail
  ed: (window != NULL)
  Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service 
name
  ='org.gnome.Contacts.SearchProvider'
  Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service 
name
  ='org.gnome.Documents'
  Oct 27 14:54:06 julep /usr/lib/gdm3/gdm-x-session[2197]: Activating service 
name
  ='org.gnome.Nautilus'

  I've also saved the apport-generated crash report if that would be
  helpful to upload.

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

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


[Touch-packages] [Bug 1645548] [NEW] click cannot correctly install clicks that have special version format

2016-11-28 Thread Zhang Enwei
Public bug reported:

I am using click 0.4.43+16.04.20160203-0ubuntu2 in arm64 environment
while building arm 64bit custom tarball(https://jenkins.canonical.com
/ues-phone/job/arm64-custom-tarball-test/)

I found this click cannot install below click correctly.
com.ubuntu.scopes.youtube_1.5.1-154_arm64.click

The apparmor profile it generated is
click_com.ubuntu.scopes.youtube_youtube_1.5.1-
while the expected should be 
click_com.ubuntu.scopes.youtube_youtube_1.5.1-154

The apparmor json file is generated as
com.ubuntu.scopes.youtube_youtube_1.5.1-.json
while the expected should be
com.ubuntu.scopes.youtube_youtube_1.5.1-154.json

We don't have this issue on armhf(vivid).
Thanks.

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

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

Title:
  click cannot correctly install clicks that have special version format

Status in click package in Ubuntu:
  New

Bug description:
  I am using click 0.4.43+16.04.20160203-0ubuntu2 in arm64 environment
  while building arm 64bit custom tarball(https://jenkins.canonical.com
  /ues-phone/job/arm64-custom-tarball-test/)

  I found this click cannot install below click correctly.
  com.ubuntu.scopes.youtube_1.5.1-154_arm64.click

  The apparmor profile it generated is
  click_com.ubuntu.scopes.youtube_youtube_1.5.1-
  while the expected should be 
  click_com.ubuntu.scopes.youtube_youtube_1.5.1-154

  The apparmor json file is generated as
  com.ubuntu.scopes.youtube_youtube_1.5.1-.json
  while the expected should be
  com.ubuntu.scopes.youtube_youtube_1.5.1-154.json

  We don't have this issue on armhf(vivid).
  Thanks.

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

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


[Touch-packages] [Bug 1639696] Re: The top and the bottom bar displays background colour when media player is opening.

2016-11-07 Thread freya zhang
** Attachment added: "screenshot20161107_155320412.png"
   
https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1639696/+attachment/4773924/+files/screenshot20161107_155320412.png

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

Title:
  The top and the bottom bar displays background colour when  media
  player is opening.

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 465
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-11-07 10:20:23
  version version: 465
  version ubuntu: 20161105
  version device: 20160606-ab415b2
  version custom: 20160831-991-38-18

  Steps:
  1.Open the camera application.
  2.Press the Video button.
  3.Press the Record button.
  4.Record the video for 10 seconds.
  5.Press the Stop button.
  6.Swipe right to view the photo roll.
  7.Press the Play button on the video
  8.Check the performance.

  
  Actual result:
  The top and the bottom bar displays background colour when 
  the video opens in the media player.

  Expected result:
  The screen should display media player interface completely,
  instead of top and botton bar displays background colour.

  Notes:The issue is also reproduced on Frieza device.

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

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


[Touch-packages] [Bug 1639696] [NEW] The top and the bottom bar displays background colour when media player is opening.

2016-11-06 Thread freya zhang
Public bug reported:

Information:
current build number: 465
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-11-07 10:20:23
version version: 465
version ubuntu: 20161105
version device: 20160606-ab415b2
version custom: 20160831-991-38-18

Steps:
1.Open the camera application.
2.Press the Video button.
3.Press the Record button.
4.Record the video for 10 seconds.
5.Press the Stop button.
6.Swipe right to view the photo roll.
7.Press the Play button on the video
8.Check the performance.


Actual result:
The top and the bottom bar displays background colour when 
the video opens in the media player.

Expected result:
The screen should display media player interface completely,
instead of top and botton bar displays background colour.

Notes:The issue is also reproduced on Frieza device.

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

** Attachment added: "video20161107_123228693.mp4"
   
https://bugs.launchpad.net/bugs/1639696/+attachment/4773895/+files/video20161107_123228693.mp4

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

Title:
  The top and the bottom bar displays background colour when  media
  player is opening.

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 465
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-11-07 10:20:23
  version version: 465
  version ubuntu: 20161105
  version device: 20160606-ab415b2
  version custom: 20160831-991-38-18

  Steps:
  1.Open the camera application.
  2.Press the Video button.
  3.Press the Record button.
  4.Record the video for 10 seconds.
  5.Press the Stop button.
  6.Swipe right to view the photo roll.
  7.Press the Play button on the video
  8.Check the performance.

  
  Actual result:
  The top and the bottom bar displays background colour when 
  the video opens in the media player.

  Expected result:
  The screen should display media player interface completely,
  instead of top and botton bar displays background colour.

  Notes:The issue is also reproduced on Frieza device.

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

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


[Touch-packages] [Bug 1628042] Re: Doesn't vibrate on incoming calls if "Other vibrations" not active

2016-09-28 Thread Zhang Enwei
Landing for usensord:https://bileto.ubuntu.com/#/ticket/2014

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

Title:
  Doesn't vibrate on incoming calls if "Other vibrations" not active

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Set "Vibrate on ring" and "Vibrate in silent mode" active under "Ringtone" 
in System settings > Sound.
  2. Make sure "Other vibrations" is NOT active in System settings > Sound.
  3. Get an incoming call.

  Expected:
  Phone vibrates.

  What happens:
  Phone doesn't vibrate. If the "Other vibrations" is set active, then the 
vibration works.

  Device: E5, stable, OTA-13.

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

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


[Touch-packages] [Bug 1628042] Re: Doesn't vibrate on incoming calls if "Other vibrations" not active

2016-09-27 Thread Zhang Enwei
** Changed in: usensord (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Doesn't vibrate on incoming calls if "Other vibrations" not active

Status in Canonical System Image:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Steps:
  1. Set "Vibrate on ring" and "Vibrate in silent mode" active under "Ringtone" 
in System settings > Sound.
  2. Make sure "Other vibrations" is NOT active in System settings > Sound.
  3. Get an incoming call.

  Expected:
  Phone vibrates.

  What happens:
  Phone doesn't vibrate. If the "Other vibrations" is set active, then the 
vibration works.

  Device: E5, stable, OTA-13.

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

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


[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

2016-09-09 Thread Zhang Enwei
Landing:https://requests.ci-train.ubuntu.com/#/ticket/1930
I verified vivid debian package on below images by creating 6 simultaneous 
alarms that will ring one minute later.
current build number: 827
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed
last update: 2016-09-09 23:42:32
version version: 827
version ubuntu: 20160907
version device: 20160606-ab415b2
version custom: 20160831-991-38-18

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  TEST CASE:
  1. Create to alarms that'll trigger at the same time
  2. Wait until they go off
  3. Dismiss the alarms
  4. Verify that there is still haptic feedback and OSK is still responsive

  ACTUAL RESULT
  Step 4 fails.

  
  UPDATE: see comment #5, it turns out it's the haptics plugin doing SYNC dbus 
calls and blocking the UI thread when the dbus service does not reply or the 
replies come with a big delay

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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


[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

2016-09-09 Thread Zhang Enwei
Thanks Andrea. I am using a similar way with that of yours, only four
commands executed simultaneously.

#!/bin/bash
dbus-send --session --print-reply --type=method_call 
--dest='com.canonical.usensord' /com/canonical/usensord/haptic 
com.canonical.usensord.haptic.Vibrate uint32:100 &
dbus-send --session --print-reply --type=method_call 
--dest='com.canonical.usensord' /com/canonical/usensord/haptic 
com.canonical.usensord.haptic.Vibrate uint32:100 &
dbus-send --session --print-reply --type=method_call 
--dest='com.canonical.usensord' /com/canonical/usensord/haptic 
com.canonical.usensord.haptic.Vibrate uint32:100 &
dbus-send --session --print-reply --type=method_call 
--dest='com.canonical.usensord' /com/canonical/usensord/haptic 
com.canonical.usensord.haptic.Vibrate uint32:100 &


I think this could simulate the operation in clock/alarm
I found the rule is that two or more senders(thread or process) calls the dbus 
function at the same time.
It freezes at below code,
http://bazaar.launchpad.net/~phablet-team/usensord/trunk/view/head:/haptic/haptic.go#L146

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  TEST CASE:
  1. Create to alarms that'll trigger at the same time
  2. Wait until they go off
  3. Dismiss the alarms
  4. Verify that there is still haptic feedback and OSK is still responsive

  ACTUAL RESULT
  Step 4 fails.

  
  UPDATE: see comment #5, it turns out it's the haptics plugin doing SYNC dbus 
calls and blocking the UI thread when the dbus service does not reply or the 
replies come with a big delay

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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


[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

2016-09-09 Thread Zhang Enwei
Thanks Pat telling me how to reproduce it.
I have reproduced it. I am trying to figuring out the reason and at the same 
time I wrote to James for help.

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  TEST CASE:
  1. Create to alarms that'll trigger at the same time
  2. Wait until they go off
  3. Dismiss the alarms
  4. Verify that there is still haptic feedback and OSK is still responsive

  ACTUAL RESULT
  Step 4 fails.

  
  UPDATE: see comment #5, it turns out it's the haptics plugin doing SYNC dbus 
calls and blocking the UI thread when the dbus service does not reply or the 
replies come with a big delay

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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


[Touch-packages] [Bug 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)

2016-09-09 Thread Zhang Enwei
** Changed in: usensord (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
  doesn't occur any more (although gestures continue to work)

Status in Canonical System Image:
  In Progress
Status in platform-api package in Ubuntu:
  In Progress
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  Krillin, rc-proposed/bq_aquaris.en r422

  TEST CASE:
  1. Create to alarms that'll trigger at the same time
  2. Wait until they go off
  3. Dismiss the alarms
  4. Verify that there is still haptic feedback and OSK is still responsive

  ACTUAL RESULT
  Step 4 fails.

  
  UPDATE: see comment #5, it turns out it's the haptics plugin doing SYNC dbus 
calls and blocking the UI thread when the dbus service does not reply or the 
replies come with a big delay

  Description:
  All at once taps have become incredibly delayed, by 1 or 2 secs.
  Gestures still work ok, no delay there.
  Swiping the greeter -> no delay. Tapping numbers to input code on the greeter 
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to 
only be a problem of unity8 clients, but also unity8 itself.
  I have no idea why horizontal/vertical swipes would be unaffected, though.

  The virtual keyboard is also completely unusable because of the huge
  delay that each tap has.

  Also noticed that the vibration is gone, taps don't trigger vibration
  anymore.

  Webview also seemed to be unaffected by the delays (although I'm not
  entirely sure, the bug is now gone)

  I also restarted unity8 and unity8-dash with Mir input logging enabled. That 
showed that the touch events were being delivered as expected, no delay.
  restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
  restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log

  Restarting lightdm (that forces the restart of unity-system-
  compositor) fixed the issue.

  Additional info: I had Mir touchspots visualization enabled, which are
  known to cause more stuttering, but I think they're unlikely to be the
  cause of this bug, I had them enabled for 2 weeks and haven't noticed
  any problem like this before.

  This is the log from a tap on an icon in the shell:
  [2016-09-06 10:52:51.876400]  input-receiver: Received 
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0, 
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963, 
minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.953821]  input-receiver: Received 
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0, 
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137, 
major=19.963, minor=0, size=19.963}, modifiers=1)
  [2016-09-06 10:52:51.954343]  input-receiver: Received 
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0, 
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963, 
minor=0, size=19.963}, modifiers=1)

  SEE VIDEO ATTACHMENT BELOW

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

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


[Touch-packages] [Bug 1613193] Re: apt-get does't work with http_proxy

2016-08-19 Thread zhang sheng
I use tcpdump to capture http request among "yum" "wget" "apt-get".
# yum repolist
Hypertext Transfer Protocol
GET http://mirrorlist.centos.org/?release=7=x86_64=os=stock 
HTTP/1.1\r\n
User-Agent: urlgrabber/3.10 yum/3.4.3\r\n
Host: mirrorlist.centos.org\r\n
Accept: */*\r\n
Proxy-Connection: Keep-Alive\r\n
\r\n
[Full request URI: 
http://mirrorlist.centos.org/?release=7=x86_64=os=stock]
[HTTP request 1/1]
[Response in frame: 8]

# wget 
http://archive.ubuntu.com/ubuntu/dists/xenial/restricted/i18n/Translation-zh
Hypertext Transfer Protocol
GET 
http://archive.ubuntu.com/ubuntu/dists/xenial/restricted/i18n/Translation-zh 
HTTP/1.1\r\n
User-Agent: Wget/1.17.1 (linux-gnu)\r\n
Accept: */*\r\n
Accept-Encoding: identity\r\n
Host: archive.ubuntu.com\r\n
Connection: Keep-Alive\r\n
Proxy-Connection: Keep-Alive\r\n
\r\n
[Full request URI: 
http://archive.ubuntu.com/ubuntu/dists/xenial/restricted/i18n/Translation-zh]
[HTTP request 1/1]
[Response in frame: 1180]

# apt-get update
Hypertext Transfer Protocol
GET 
http://archive.ubuntu.com/ubuntu/dists/xenial/restricted/i18n/Translation-zh 
HTTP/1.1\r\n
Host: archive.ubuntu.com\r\n
Cache-Control: max-age=0\r\n
Accept: text/*\r\n
User-Agent: Debian APT-HTTP/1.3 (1.2.10)\r\n
\r\n
[Full request URI: 
http://archive.ubuntu.com/ubuntu/dists/xenial/restricted/i18n/Translation-zh]
[HTTP request 1/1]

Only "apt-get" doesn't have "Proxy-Connection: Keep-Alive", how can i
add "Proxy-Connection: Keep-Alive" to apt-get? I need to verify this.

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

Title:
  apt-get does't work with http_proxy

Status in apt package in Ubuntu:
  New

Bug description:
  I use lubuntu 16.04.
  $ uname -a
  Linux ubuntu 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l |grep apt
  ii  apt  1.2.10ubuntu1
amd64commandline package manager

  When I set "http_proxy" environment var and run "apt-get update", I get many 
"connection failed"
  Err:16 http://archive.ubuntu.com/ubuntu xenial/main Sources
Connection failed
  Err:17 http://archive.ubuntu.com/ubuntu xenial/restricted Sources
Connection failed
  Err:18 http://archive.ubuntu.com/ubuntu xenial/universe Sources
Connection failed
  Err:19 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources
Connection failed
  Err:20 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Connection failed
  Err:21 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages
Connection failed

  But I can use curl and wget to fetch website homepage.
  And in centos7, yum can work with 'http_proxy', I can update my centos7.

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

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


[Touch-packages] [Bug 1613193] Re: apt-get does't work with http_proxy

2016-08-15 Thread zhang sheng
$ export http_proxy=http://192.168.1.1:8080
$ apt-get -o Debug::Acquire::http=1 -o Debug::pkgAcquire::Worker=1 update 
>apt-update.log 2>&1

I paste all output at "http://paste.ubuntu.com/23060145/;

I find something strange. I can't find port 8080 at debug output.
Does apt can't specify proxy port?

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

Title:
  apt-get does't work with http_proxy

Status in apt package in Ubuntu:
  New

Bug description:
  I use lubuntu 16.04.
  $ uname -a
  Linux ubuntu 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l |grep apt
  ii  apt  1.2.10ubuntu1
amd64commandline package manager

  When I set "http_proxy" environment var and run "apt-get update", I get many 
"connection failed"
  Err:16 http://archive.ubuntu.com/ubuntu xenial/main Sources
Connection failed
  Err:17 http://archive.ubuntu.com/ubuntu xenial/restricted Sources
Connection failed
  Err:18 http://archive.ubuntu.com/ubuntu xenial/universe Sources
Connection failed
  Err:19 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources
Connection failed
  Err:20 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Connection failed
  Err:21 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages
Connection failed

  But I can use curl and wget to fetch website homepage.
  And in centos7, yum can work with 'http_proxy', I can update my centos7.

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

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


[Touch-packages] [Bug 1613193] Re: apt-get does't work with http_proxy

2016-08-15 Thread zhang sheng
** Tags added: xenial

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

Title:
  apt-get does't work with http_proxy

Status in apt package in Ubuntu:
  New

Bug description:
  I use lubuntu 16.04.
  $ uname -a
  Linux ubuntu 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l |grep apt
  ii  apt  1.2.10ubuntu1
amd64commandline package manager

  When I set "http_proxy" environment var and run "apt-get update", I get many 
"connection failed"
  Err:16 http://archive.ubuntu.com/ubuntu xenial/main Sources
Connection failed
  Err:17 http://archive.ubuntu.com/ubuntu xenial/restricted Sources
Connection failed
  Err:18 http://archive.ubuntu.com/ubuntu xenial/universe Sources
Connection failed
  Err:19 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources
Connection failed
  Err:20 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Connection failed
  Err:21 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages
Connection failed

  But I can use curl and wget to fetch website homepage.
  And in centos7, yum can work with 'http_proxy', I can update my centos7.

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

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


[Touch-packages] [Bug 1613193] [NEW] apt-get does't work with http_proxy

2016-08-15 Thread zhang sheng
Public bug reported:

I use lubuntu 16.04.
$ uname -a
Linux ubuntu 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l |grep apt
ii  apt  1.2.10ubuntu1  
  amd64commandline package manager

When I set "http_proxy" environment var and run "apt-get update", I get many 
"connection failed"
Err:16 http://archive.ubuntu.com/ubuntu xenial/main Sources
  Connection failed
Err:17 http://archive.ubuntu.com/ubuntu xenial/restricted Sources
  Connection failed
Err:18 http://archive.ubuntu.com/ubuntu xenial/universe Sources
  Connection failed
Err:19 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources
  Connection failed
Err:20 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  Connection failed
Err:21 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages
  Connection failed

But I can use curl and wget to fetch website homepage.
And in centos7, yum can work with 'http_proxy', I can update my centos7.

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

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

Title:
  apt-get does't work with http_proxy

Status in apt package in Ubuntu:
  New

Bug description:
  I use lubuntu 16.04.
  $ uname -a
  Linux ubuntu 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l |grep apt
  ii  apt  1.2.10ubuntu1
amd64commandline package manager

  When I set "http_proxy" environment var and run "apt-get update", I get many 
"connection failed"
  Err:16 http://archive.ubuntu.com/ubuntu xenial/main Sources
Connection failed
  Err:17 http://archive.ubuntu.com/ubuntu xenial/restricted Sources
Connection failed
  Err:18 http://archive.ubuntu.com/ubuntu xenial/universe Sources
Connection failed
  Err:19 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources
Connection failed
  Err:20 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
Connection failed
  Err:21 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages
Connection failed

  But I can use curl and wget to fetch website homepage.
  And in centos7, yum can work with 'http_proxy', I can update my centos7.

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

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


[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-29 Thread Zhang Enwei
Hi Pat,
The ci-train ticket is created and package built 
successfully(https://requests.ci-train.ubuntu.com/#/silo/017).
@Zsombor, you could use silo17 for testing if you like. Thanks.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-28 Thread Zhang Enwei
Hi Pat,
I have got the permission to work on Bileto. Will learn how to make a landing.
Thanks.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  http://paste.ubuntu.com/10620834/

To manage 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-27 Thread Zhang Enwei
Hi Pat,
I think yes because I don't know how to request a landing. Thanks.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  http://paste.ubuntu.com/10620834/

To manage notifications about 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-25 Thread Zhang Enwei
Hi Zsombor,
Here is the latest usensord binary. Could you please help verify?
I verified unconfined apps, I cannot verify confined apps since this needs code 
change from Toolkit.
Thanks a lot.

** Attachment added: "usensord.zip"
   
https://bugs.launchpad.net/ubuntu/+source/usensord/+bug/1433590/+attachment/4707427/+files/usensord.zip

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-25 Thread Zhang Enwei
Hi Tyler and Seth,
Could you please help review current solution again? This bug is tagged ota13 
so I don't have much time left. Thanks a lot.
Hi Zsombor,
Have you verified the binary I sent to you? Thank you.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-18 Thread Zhang Enwei
Hi Seth,
Since Tyler is on vacation, could you please help review?
https://code.launchpad.net/~zhangew401/usensord/fix-lp-1433590/+merge/299959
Thanks.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-15 Thread Zhang Enwei
Thanks Seth.
Do you have any suggestion what we can use in this case?

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  http://paste.ubuntu.com/10620834/

To manage notifications about this 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-14 Thread Zhang Enwei
Proposition from James Henstridge (jamesh)
"If you want to identify the executable, calling os.Readlink() on 
/proc/$PID/exe would be more appropriate:

$ ps x | grep maliit
 5823 ? Ssl 2:38 maliit-server
25788 pts/16 S+ 0:00 grep --color=auto maliit
$ ls -l /proc/5823/exe
lrwxrwxrwx 1 phablet phablet 0 Jul 7 11:47 /proc/5823/exe -> 
/usr/bin/maliit-server

I'd combine that with the a check that the security label is
"unconfined" as Tyler suggested (which you can do using the code
fragment I gave via mail). That should be enough to ensure you aren't
being faked out by an untrusted application, and are talking to the
expected system service."

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-13 Thread Zhang Enwei
Thanks Seth and Tyler.
IMHO the start time of one process may always be different value. So... this 
solution is not correct.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-13 Thread Zhang Enwei
I have compiled the usensord binary based on current solution.
I did some tests and it works well.
Since settings part is not ready, I am using below command to change the 
property whose default value is 0(means not vibrate).
dbus-send --session --print-reply --type=method_call 
--dest='com.canonical.usensord' /com/canonical/usensord/haptic 
org.freedesktop.DBus.Properties.Set string:"com.canonical.usensord.haptic" 
string:"OtherVibrate" uint32:1

Code is here: https://code.launchpad.net/~zhangew401/usensord/fix-lp-1433590
and the logic is
do vibration for OSK always.
do vibration for others only when the property is 1(means enabled in settings)

The property is saved in file, /home/phablet/.config/usensord/prop so
that it will be restored after factory reset.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-13 Thread Zhang Enwei
** Changed in: usensord (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
  an error to console ... so transient)

  http://paste.ubuntu.com/10620834/

To manage notifications about this 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-13 Thread Zhang Enwei
I am now investigating if org.freedesktop.DBus.GetConnectionUnixProcessID is 
supported in go-dbus.
If it is supported, we can use pid to get the name of the process or path of 
the binary.

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  Confirmed

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also a
  /dev/tty one but i think this is just because soemthing tries to write
 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-13 Thread Zhang Enwei
Thanks Zsombor explaining a lot about this bug to me.
According to comment #13, I am now blocked because in usensord, based on 
currently info we could get from dbus message, we don't have a method to judge 
if the peer(caller) is OSK or the app.
The call flow is app--->toolkit>Qt Haptics-->uSensord
If the app or OSK don't send info for usensord to make the differentiation, I 
cannot achieve the goal.


** Changed in: usensord (Ubuntu)
 Assignee: Penk Chen (penk) => Zhang Enwei (zhangew401)

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if 

[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work

2016-07-06 Thread Zhang Enwei
Hi Pat,
I have exposed the property OtherVibrate from Object Path: 
com.canonical.usensord.haptic.
For remaining logic part about when to do vibration, I am contacting Zsombor. 
May be ready soon.
https://code.launchpad.net/~zhangew401/usensord/fix-lp-1433590

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

Title:
  apparmor dbus denial for org.freedesktop.Accounts and make Other
  vibrations work

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in usensord package in Ubuntu:
  In Progress

Bug description:
  This affects vivid and (somewhat recently?) 14.09.

  At some point, apps started to request access to
  org.freedesktop.Accounts for something, but I'm not sure what. It has
  been conjectured in this bug that it is due to vibration settings.
  Filing against ubuntu-system-settings for now, but please feel free to
  move to the correct package.

  This happens with webapps:
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"
  Apr  7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=2632 
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26" 
peer_pid=1596 peer_profile="unconfined"

  and QML apps:
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"
  Apr  7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/Accounts" 
interface="org.freedesktop.Accounts" member="FindUserById" mask="send" 
name="org.freedesktop.Accounts" pid=3377 
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596 
peer_profile="unconfined"

  The following rules allow the requested access:
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.DBus.{Introspectable,Properties}"
 member=Introspect
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts"
 interface="org.freedesktop.Accounts"
 member=FindUserById
 peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
 bus=system
 path="/org/freedesktop/Accounts/User[0-9]*"
 interface="org.freedesktop.DBus.Properties"
 member=Get
 peer=(name=org.freedesktop.Accounts,label=unconfined),

  However, the above is too lenient and constitutes a privacy leak for
  apps. FindUserById could be used by a malicious app to enumerate
  usernames on multiuser systems and because we can't mediate method
  data with apparmor, the Get() method can be used to obtain any
  information provided by this interface.

  The following can be used to see what can be leaked to a malicious app:
  gdbus introspect --system -d org.freedesktop.Accounts -o 
/org/freedesktop/Accounts/User`id -u phablet`

  This can be solved in a couple of ways:
  1. add whatever information the app is trying to access to a new helper 
service that only exposes things that the app needs. This could be a single 
standalone service, perhaps something from ubuntu-system-settings, that could 
expose any number of things-- the current locale, if the locale changed, if the 
grid units changed, the vibration settings, etc. Since this service wouldn't 
have any sensitive information, you could use standard dbus 
properties/Get()/etc 
  2. add a new dbus API to an existing service such that apparmor rules can 
then be used to allow by method (eg, GetVibration() or something)

  I won't dictate the implementation except to mention that '1' seems
  like something generally useful and I believe that it was something
  the ubuntu-system-settings devs were already looking at for detecting
  locale changes without rebooting.


  Original description
  starting an app in vivid (image 135 on arale currently)

  produces a bunch of dbus denials in syslog ... (there is also 

[Touch-packages] [Bug 1597634] Re: The "Share to" interface displays abnormal when the video is maximized in Video scope.

2016-06-30 Thread freya zhang
** Description changed:

  Information:
  current build number: 371
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-29 05:04:34
  version version: 371
  version ubuntu: 20160629
  version device: 20160606-ab415b2
  version custom: 2
  
  Precondition:
  Copy some video to the device.
  
  Steps:
  1.Go to the Videos scope and tap on 'My Videos'.
- 2.Select a video from the scope. Click on the video screen and then tap 
"maximize" button displayed on lower right corner.
- 3.After maximizing the video screen,press the share button on lower left 
corner.
- 4.Check the interface.
- 
+ 2.Select a video from the scope to detail page
+ 3.Click on the thumbnail of the video to play it inside of the page
+ 4.Tap on "maximize" button to play it full screen
+ 5.Tap on "share" button on bottom left corner.
+ 6.Check the result
  
  Actual result:
- The "Share to " interface displays under the video screen.
+ Content hub opens in a second layer under video playing layer.
+ 
  Expected result:
- The "Share to " interface should display over the video screen.
+ Content hub opens in the top layer.
  
  Notes:
  The issue is not reproduced when the video is minimized.

** Summary changed:

- The "Share to" interface displays abnormal when the video is maximized in 
Video scope.
+ Content hub opens in a second layer if share video when it plays full screen

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

Title:
  Content hub opens in a second layer if share video when it plays full
  screen

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 371
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-29 05:04:34
  version version: 371
  version ubuntu: 20160629
  version device: 20160606-ab415b2
  version custom: 2

  Precondition:
  Copy some video to the device.

  Steps:
  1.Go to the Videos scope and tap on 'My Videos'.
  2.Select a video from the scope to detail page
  3.Click on the thumbnail of the video to play it inside of the page
  4.Tap on "maximize" button to play it full screen
  5.Tap on "share" button on bottom left corner.
  6.Check the result

  Actual result:
  Content hub opens in a second layer under video playing layer.

  Expected result:
  Content hub opens in the top layer.

  Notes:
  The issue is not reproduced when the video is minimized.

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

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


[Touch-packages] [Bug 1597634] [NEW] The "Share to" interface displays abnormal when the video is maximized in Video scope.

2016-06-30 Thread freya zhang
Public bug reported:

Information:
current build number: 371
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-06-29 05:04:34
version version: 371
version ubuntu: 20160629
version device: 20160606-ab415b2
version custom: 2

Precondition:
Copy some video to the device.

Steps:
1.Go to the Videos scope and tap on 'My Videos'.
2.Select a video from the scope. Click on the video screen and then tap 
"maximize" button displayed on lower right corner.
3.After maximizing the video screen,press the share button on lower left corner.
4.Check the interface.


Actual result:
The "Share to " interface displays under the video screen.
Expected result:
The "Share to " interface should display over the video screen.

Notes:
The issue is not reproduced when the video is minimized.

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

** Attachment added: "screenshot20160630_145230400.png"
   
https://bugs.launchpad.net/bugs/1597634/+attachment/4692635/+files/screenshot20160630_145230400.png

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

Title:
  The "Share to" interface displays abnormal when the video is maximized
  in Video scope.

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 371
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-29 05:04:34
  version version: 371
  version ubuntu: 20160629
  version device: 20160606-ab415b2
  version custom: 2

  Precondition:
  Copy some video to the device.

  Steps:
  1.Go to the Videos scope and tap on 'My Videos'.
  2.Select a video from the scope. Click on the video screen and then tap 
"maximize" button displayed on lower right corner.
  3.After maximizing the video screen,press the share button on lower left 
corner.
  4.Check the interface.

  
  Actual result:
  The "Share to " interface displays under the video screen.
  Expected result:
  The "Share to " interface should display over the video screen.

  Notes:
  The issue is not reproduced when the video is minimized.

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

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


[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start

2016-06-24 Thread zhang sheng
** Summary changed:

- 15:10: bluetoothd reports "Not enough handles to register service" at start
+ 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" 
at start

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough handles to register
  service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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


[Touch-packages] [Bug 1490349] Re: 15:10: bluetoothd reports "Not enough handles to register service" at start

2016-06-20 Thread zhang sheng
I use ubuntu16.04, my computer can't connect to my bluetooth speaker
after reboot.

uname -a
Linux zs-PC 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

journalctl --unit=bluetooth
-- Logs begin at 一 2016-06-20 18:41:21 CST, end at 一 2016-06-20 18:43:45 CST. --
6月 20 18:41:36 zs-PC systemd[1]: Starting Bluetooth service...
6月 20 18:41:36 zs-PC bluetoothd[818]: Bluetooth daemon 5.37
6月 20 18:41:36 zs-PC systemd[1]: Started Bluetooth service.
6月 20 18:41:36 zs-PC bluetoothd[818]: Starting SDP server
6月 20 18:41:36 zs-PC bluetoothd[818]: Bluetooth management interface 1.10 
initialized
6月 20 18:41:36 zs-PC bluetoothd[818]: Failed to obtain handles for "Service 
Changed" characteristic
6月 20 18:41:36 zs-PC bluetoothd[818]: Not enough free handles to register 
service
6月 20 18:41:36 zs-PC bluetoothd[818]: Error adding Link Loss service
6月 20 18:41:36 zs-PC bluetoothd[818]: Not enough free handles to register 
service
6月 20 18:41:36 zs-PC bluetoothd[818]: Not enough free handles to register 
service
6月 20 18:41:36 zs-PC bluetoothd[818]: Not enough free handles to register 
service
6月 20 18:41:36 zs-PC bluetoothd[818]: Current Time Service could not be 
registered
6月 20 18:41:36 zs-PC bluetoothd[818]: gatt-time-server: Input/output error (5)
6月 20 18:41:36 zs-PC bluetoothd[818]: Not enough free handles to register 
service
6月 20 18:41:36 zs-PC bluetoothd[818]: Not enough free handles to register 
service
6月 20 18:41:36 zs-PC bluetoothd[818]: Sap driver initialization failed.
6月 20 18:41:36 zs-PC bluetoothd[818]: sap-server: Operation not permitted (1)
6月 20 18:41:48 zs-PC bluetoothd[818]: Endpoint registered: sender=:1.43 
path=/MediaEndpoint/A2DPSource
6月 20 18:41:48 zs-PC bluetoothd[818]: Endpoint registered: sender=:1.43 
path=/MediaEndpoint/A2DPSink
6月 20 18:41:53 zs-PC bluetoothd[818]: Endpoint registered: sender=:1.67 
path=/MediaEndpoint/A2DPSource
6月 20 18:41:53 zs-PC bluetoothd[818]: Endpoint registered: sender=:1.67 
path=/MediaEndpoint/A2DPSink
6月 20 18:41:53 zs-PC bluetoothd[818]: RFCOMM server failed for Headset Voice 
gateway: rfcomm_bind: Address already in use (98)
6月 20 18:42:10 zs-PC bluetoothd[818]: Endpoint unregistered: sender=:1.43 
path=/MediaEndpoint/A2DPSource
6月 20 18:42:10 zs-PC bluetoothd[818]: Endpoint unregistered: sender=:1.43 
path=/MediaEndpoint/A2DPSink


>From now, I can only use my bluetooth speaker by:
1. delete it from the bluetooth device list
2. research the bluetooth device
3. select and connect it
then everything is ok.

I don't konw why I can't connect my bluetooth speaker wituout delete it.

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

Title:
  15:10: bluetoothd reports "Not enough handles to register service" at
  start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

To manage notifications about this bug go to:

[Touch-packages] [Bug 1590188] Re: Widgets is are in wrong order after posting one comment in Preview Page

2016-06-16 Thread Zhang Enwei
Thanks Pawel.
I verified silo001 on Instagram and Flickr.

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

Title:
  Widgets is are in wrong order after posting one comment in Preview
  Page

Status in Canonical System Image:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  I am testing on some golang scopes such as
  doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban)
  flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr)
  After I post one comment and the Preview page refreshes, the order of Preview 
Widgets is reversed. For example, before I post comment, Art is on the up most 
position, while after I post comment, Art is the last widget in the page.

  I can see from the log, the order of widgets is adjusted(art at first
  is 0, and at last is 15). But i don't know why.

  AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which
  could fix this issue.

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

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


[Touch-packages] [Bug 1590188] Re: Widgets is are in wrong order after posting one comment in Preview Page

2016-06-16 Thread Zhang Enwei
So Pawel, Marcus, do you need me to test https://launchpad.net/~unity-
api-team/+archive/ubuntu/dev-build-1/+build/10027020/+files/unity-
plugin-scopes_0.5.7+16.10.20160525-0~327~ubuntu15.04.1_armhf.deb?

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

Title:
  Widgets is are in wrong order after posting one comment in Preview
  Page

Status in Canonical System Image:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress

Bug description:
  I am testing on some golang scopes such as
  doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban)
  flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr)
  After I post one comment and the Preview page refreshes, the order of Preview 
Widgets is reversed. For example, before I post comment, Art is on the up most 
position, while after I post comment, Art is the last widget in the page.

  I can see from the log, the order of widgets is adjusted(art at first
  is 0, and at last is 15). But i don't know why.

  AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which
  could fix this issue.

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

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


[Touch-packages] [Bug 1590188] [NEW] Widgets is are in wrong order after posting one comment in Preview Page

2016-06-07 Thread Zhang Enwei
Public bug reported:

I am testing on some golang scopes such as
doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban)
flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr)
After I post one comment and the Preview page refreshes, the order of Preview 
Widgets is reversed. For example, before I post comment, Art is on the up most 
position, while after I post comment, Art is the last widget in the page.

I can see from the log, the order of widgets is adjusted(art at first is
0, and at last is 15). But i don't know why.

AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which
could fix this issue.

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

** Attachment added: "unity8-dash.log"
   
https://bugs.launchpad.net/bugs/1590188/+attachment/4679275/+files/unity8-dash.log

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

Title:
  Widgets is are in wrong order after posting one comment in Preview
  Page

Status in unity8 package in Ubuntu:
  New

Bug description:
  I am testing on some golang scopes such as
  doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban)
  flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr)
  After I post one comment and the Preview page refreshes, the order of Preview 
Widgets is reversed. For example, before I post comment, Art is on the up most 
position, while after I post comment, Art is the last widget in the page.

  I can see from the log, the order of widgets is adjusted(art at first
  is 0, and at last is 15). But i don't know why.

  AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which
  could fix this issue.

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

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


[Touch-packages] [Bug 1582060] Re: The keyboard is not shown when entering HERE account.

2016-05-15 Thread freya zhang
** Changed in: unity (Ubuntu)
   Status: New => Invalid

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

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

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

Title:
  The keyboard is not shown when entering HERE account.

Status in unity8 package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 335
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-16 10:14:49
  version version: 335
  version ubuntu: 20160514
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9

  Precondition:
  1) WiFi connected 
  2) HERE account ready 

  Steps:
  1.Launch HERE and HERE launches and map displayed.
  2. Go to Here Maps Settings -> Sign in.Sign in page displayed.
  3.Tap the input box.And check the performance.

  Actual result:
  The keyboard is not shown.
  Expected result:
  The keyboard should be shown.

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

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


[Touch-packages] [Bug 1580857] [NEW] Cannot add more fields to a contact.

2016-05-11 Thread freya zhang
Public bug reported:

Information:
current build number: 331
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-05-12 12:57:13
version version: 331
version ubuntu: 20160512
version device: 20160329-a9bacdb
version custom: 20160505-975-38-9

Precondition:
Contacts are saved in address book.

Steps:
1.Launch Contacts app and  click on a contact
3.Click the "Edit Contact" button.
4.Click on "Add field" and select "Phone","Email" or "Address" option.Check the 
performance.

Actual Result: Nothing happens.
Expected result: Add email, phone, address field should appear.

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

** Description changed:

  Information:
  current build number: 331
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-12 12:57:13
  version version: 331
  version ubuntu: 20160512
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9
  
  Precondition:
  Contacts are saved in address book.
  
  Steps:
  1.Launch Contacts app and  click on a contact
- 3.Click the "Edit Contact" link
+ 3.Click the "Edit Contact" button.
  4.Click on "Add field" and select "Phone","Email" or "Address" option.Check 
the performance.
  
  Actual Result: Nothing happens.
  Expected result: Add email, phone, address field should appear.

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

Title:
  Cannot add more fields to a contact.

Status in address-book-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 331
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-05-12 12:57:13
  version version: 331
  version ubuntu: 20160512
  version device: 20160329-a9bacdb
  version custom: 20160505-975-38-9

  Precondition:
  Contacts are saved in address book.

  Steps:
  1.Launch Contacts app and  click on a contact
  3.Click the "Edit Contact" button.
  4.Click on "Add field" and select "Phone","Email" or "Address" option.Check 
the performance.

  Actual Result: Nothing happens.
  Expected result: Add email, phone, address field should appear.

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

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


[Touch-packages] [Bug 1549153] Re: The cursor on the bottom is hidden after you continue typing words in Message app.

2016-02-24 Thread freya zhang
** Attachment added: "IMG_20160224_173312.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1549153/+attachment/4579833/+files/IMG_20160224_173312.jpg

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

Title:
  The cursor on the bottom is hidden after you continue typing words in
  Message app.

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 266
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-24 04:40:50
  version version: 266
  version ubuntu: 20160224
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  Steps:
  1.Rotate device is to landscape mode.
  2.Launch message app and create a new message.
  3.Continue typing words in "Write a message" place and check the UI.

  Actual result:
  The cursor on the bottom is hidden after you continue entering words.

  Expected result:
  It should auto-scroll to show the current line where the cursor is.

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

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


[Touch-packages] [Bug 1549153] Re: The cursor on the bottom is hidden after you continue typing words in Message app.

2016-02-24 Thread freya zhang
** Summary changed:

- The vertical bar in edit box is hidden while typing words ,it should 
auto-scroll to show the current line where the cursor is in Message app.
+ The cursor on the bottom is hidden after you continue typing words in Message 
app.

** Description changed:

  Information:
  current build number: 266
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-24 04:40:50
  version version: 266
  version ubuntu: 20160224
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid
  
  Steps:
- 1.Launch message app and create a new message.
- 2.Enter a long text in "Write a message" place and check the UI.
+ 1.Rotate device is to landscape mode.
+ 2.Launch message app and create a new message.
+ 3.Continue typing words in "Write a message" place and check the UI.
  
  Actual result:
- The vertical line at the right border is hidde while typing words.
+ The cursor on the bottom is hidden after you continue entering words.
  
  Expected result:
- The vertical bar should auto-scroll to show the current line where the cursor 
is ,instead of hidden.
+ It should auto-scroll to show the current line where the cursor is.

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

Title:
  The cursor on the bottom is hidden after you continue typing words in
  Message app.

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 266
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-24 04:40:50
  version version: 266
  version ubuntu: 20160224
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  Steps:
  1.Rotate device is to landscape mode.
  2.Launch message app and create a new message.
  3.Continue typing words in "Write a message" place and check the UI.

  Actual result:
  The cursor on the bottom is hidden after you continue entering words.

  Expected result:
  It should auto-scroll to show the current line where the cursor is.

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

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


[Touch-packages] [Bug 1549153] [NEW] The vertical bar in edit box is hidden while typing words , it should auto-scroll to show the current line where the cursor is in Message app.

2016-02-23 Thread freya zhang
Public bug reported:

Information:
current build number: 266
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-02-24 04:40:50
version version: 266
version ubuntu: 20160224
version device: 20160108-efc96d8
version custom: 20160111-926-36--vivid

Steps:
1.Launch message app and create a new message.
2.Enter a long text in "Write a message" place and check the UI.

Actual result:
The vertical line at the right border is hidde while typing words.

Expected result:
The vertical bar should auto-scroll to show the current line where the cursor 
is ,instead of hidden.

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

** Attachment added: "IMG_20160224_153532.jpg"
   
https://bugs.launchpad.net/bugs/1549153/+attachment/4579737/+files/IMG_20160224_153532.jpg

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

Title:
  The vertical bar in edit box is hidden while typing words ,it should
  auto-scroll to show the current line where the cursor is in Message
  app.

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 266
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-24 04:40:50
  version version: 266
  version ubuntu: 20160224
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  Steps:
  1.Launch message app and create a new message.
  2.Enter a long text in "Write a message" place and check the UI.

  Actual result:
  The vertical line at the right border is hidde while typing words.

  Expected result:
  The vertical bar should auto-scroll to show the current line where the cursor 
is ,instead of hidden.

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

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


[Touch-packages] [Bug 1549129] [NEW] The "Enable MMS group chat" becomes unmark state when you enter the setting interface again in Message app.

2016-02-23 Thread freya zhang
Public bug reported:

Information:
current build number: 266
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-02-24 04:40:50
version version: 266
version ubuntu: 20160224
version device: 20160108-efc96d8
version custom: 20160111-926-36--vivid

Steps:
1.Launch message app and tap setting icon on top right.
2.Tap the toggle behind "Enable MMS group chat" and the state is on .
3.Tap back key on top left.
4.Tap the setting icon again and check the UI.

Actual result:
The toggle is "off" state.
Expected result:
The toggle should be "on" state.

** Affects: messaging-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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1549129

Title:
  The "Enable MMS group chat" becomes unmark state when you enter the
  setting interface again in Message app.

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 266
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-02-24 04:40:50
  version version: 266
  version ubuntu: 20160224
  version device: 20160108-efc96d8
  version custom: 20160111-926-36--vivid

  Steps:
  1.Launch message app and tap setting icon on top right.
  2.Tap the toggle behind "Enable MMS group chat" and the state is on .
  3.Tap back key on top left.
  4.Tap the setting icon again and check the UI.

  Actual result:
  The toggle is "off" state.
  Expected result:
  The toggle should be "on" state.

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

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


[Touch-packages] [Bug 1549056] [NEW] content sharing cannot work in scopes

2016-02-23 Thread Zhang Enwei
Public bug reported:

I tried to share one picture according to instructions in 
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.1/previewwidgets/ in my 
scope,
Code is as below:
PreviewWidget w_art("artId", "image");
w_art.add_attribute_mapping("source", "art");
w_art.add_attribute_value("zoomable", us::Variant(true));
VariantMap share_data;
share_data["uri"] = result()["art"];
qDebug() << "arturi:" << 
QString::fromStdString(result()["art"].get_string());
share_data["content-type"] = Variant("pictures");
w_art.add_attribute_value("share-data", us::Variant(share_data));
widgets.emplace_back(w_art);
I check the uri is correct.
When I tried to share the image, the Content Hub gives me some options and when 
I choose facebook, twitter or message, the image cannot be sent to them.
system info:
current build number: 431
device name: mako
channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed
last update: 2016-02-03 14:41:40
version version: 431
version ubuntu: 20160203
version device: 20160112
version custom: 20160201-5-vivid

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

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

Title:
  content sharing cannot work in scopes

Status in unity8 package in Ubuntu:
  New

Bug description:
  I tried to share one picture according to instructions in 
https://developer.ubuntu.com/api/scopes/cpp/sdk-15.04.1/previewwidgets/ in my 
scope,
  Code is as below:
  PreviewWidget w_art("artId", "image");
  w_art.add_attribute_mapping("source", "art");
  w_art.add_attribute_value("zoomable", us::Variant(true));
  VariantMap share_data;
  share_data["uri"] = result()["art"];
  qDebug() << "arturi:" << 
QString::fromStdString(result()["art"].get_string());
  share_data["content-type"] = Variant("pictures");
  w_art.add_attribute_value("share-data", us::Variant(share_data));
  widgets.emplace_back(w_art);
  I check the uri is correct.
  When I tried to share the image, the Content Hub gives me some options and 
when I choose facebook, twitter or message, the image cannot be sent to them.
  system info:
  current build number: 431
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en-proposed
  last update: 2016-02-03 14:41:40
  version version: 431
  version ubuntu: 20160203
  version device: 20160112
  version custom: 20160201-5-vivid

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

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


[Touch-packages] [Bug 1547754] Re: pppoe MTU problems

2016-02-22 Thread Wenzhuo Zhang
** Description changed:

  1. If the MTU of eth0 is 1500, network-manager fails to establish a
  pppoe connection, and the MTU of eth0 (not ppp0) is then automatically
  lowered to 1492. Now network-manager can successfully establish a pppoe
  connection. If I manually set the MTU of eth0 back to 1500, network-
  manager would fail again. See attached log.
  
  2. The Access Concentrator of my ISP offers MTU values of both 1492 and
- 1442. pppd-4.3.5 in Ubuntu 14.04 adopts 1492 as the MTU of the ppp
- device, while pppd-4.3.7 in Xenial adopts 1442. Setting the lower MTU on
+ 1442. pppd-2.4.5 in Ubuntu 14.04 adopts 1492 as the MTU of the ppp
+ device, while pppd-2.4.7 in Xenial adopts 1442. Setting the lower MTU on
  the WAN link (ppp0) can easily cause PMTU-D problems, especially for
  remote VPN clients.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat Feb 20 09:56:32 2016
  IpRoute:
-  default via 172.16.10.1 dev eth0  proto static  metric 100 
-  169.254.0.0/16 dev eth0  scope link  metric 1000 
-  172.16.10.0/24 dev eth0  proto kernel  scope link  src 172.16.10.32  metric 
100
+  default via 172.16.10.1 dev eth0  proto static  metric 100
+  169.254.0.0/16 dev eth0  scope link  metric 1000
+  172.16.10.0/24 dev eth0  proto kernel  scope link  src 172.16.10.32  metric 
100
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=false
-  WWANEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=false
+  WWANEnabled=true
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: yes
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: yes
+   Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-02-19 (0 days ago)
  WpaSupplicantLog:
-  
+ 
  nmcli-dev:
-  DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
-  eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Auto eth0   dff18f4d-6732-4eab-bd06-5209635b9bab  
/org/freedesktop/NetworkManager/ActiveConnection/11 
-  irda0   unknown   disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
  
-  eth1wifi  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
-  lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
+  DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
+  eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Auto eth0   dff18f4d-6732-4eab-bd06-5209635b9bab  
/org/freedesktop/NetworkManager/ActiveConnection/11
+  irda0   unknown   disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
+  eth1wifi  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  ----
+  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'.

** Attachment removed: "IfupdownConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547754/+attachment/4576094/+files/IfupdownConfig.txt

** Attachment removed: "IpAddr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547754/+attachment/4576095/+files/IpAddr.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547754/+attachment/4576096/+files/IwConfig.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547754/+attachment/4576097/+files/JournalErrors.txt

** Attachment removed: "NetDevice.eth0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547754/+attachment/4576098/+files/NetDevice.eth0.txt

** Attachment removed: "NetDevice.eth1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547754/+attachment/4576099/+files/NetDevice.eth1.txt

** Attachment removed: "NetDevice.irda0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547754/+attachment/4576100/+files/NetDevice.irda0.txt

** Attachment removed: "NetDevice.lo.txt"
   

[Touch-packages] [Bug 1547754] [NEW] pppoe MTU problems

2016-02-22 Thread Wenzhuo Zhang
Public bug reported:

1. If the MTU of eth0 is 1500, network-manager fails to establish a
pppoe connection, and the MTU of eth0 (not ppp0) is then automatically
lowered to 1492. Now network-manager can successfully establish a pppoe
connection. If I manually set the MTU of eth0 back to 1500, network-
manager would fail again. See attached log.

2. The Access Concentrator of my ISP offers MTU values of both 1492 and
1442. pppd-2.4.5 in Ubuntu 14.04 adopts 1492 as the MTU of the ppp
device, while pppd-2.4.7 in Xenial adopts 1442. Setting the lower MTU on
the WAN link (ppp0) can easily cause PMTU-D problems, especially for
remote VPN clients.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.0.4-0ubuntu9
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
CurrentDesktop: LXDE
Date: Sat Feb 20 09:56:32 2016
IpRoute:
 default via 172.16.10.1 dev eth0  proto static  metric 100
 169.254.0.0/16 dev eth0  scope link  metric 1000
 172.16.10.0/24 dev eth0  proto kernel  scope link  src 172.16.10.32  metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-02-19 (0 days ago)
WpaSupplicantLog:

nmcli-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
 eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Auto eth0   dff18f4d-6732-4eab-bd06-5209635b9bab  
/org/freedesktop/NetworkManager/ActiveConnection/11
 irda0   unknown   disconnected  /org/freedesktop/NetworkManager/Devices/2  --  
----
 eth1wifi  unavailable   /org/freedesktop/NetworkManager/Devices/3  --  
----
 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: apport-bug i386 xenial

** Attachment added: "$ sed -n '/^Feb 20 08:45/,/^Feb 20 08:51/p' 
/var/log/syslog | egrep '(pppd|NetworkManager)' | sed 's/...//g; 
s/00:11:25:.../00:11:25:aa:bb:cc/g; s/ac:85:3d:../ac:85:3d:ee:dd:ff/g' > 
network-manager-pppoe.log"
   
https://bugs.launchpad.net/bugs/1547754/+attachment/4576091/+files/network-manager-pppoe.log

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

Title:
  pppoe MTU problems

Status in network-manager package in Ubuntu:
  New

Bug description:
  1. If the MTU of eth0 is 1500, network-manager fails to establish a
  pppoe connection, and the MTU of eth0 (not ppp0) is then automatically
  lowered to 1492. Now network-manager can successfully establish a
  pppoe connection. If I manually set the MTU of eth0 back to 1500,
  network-manager would fail again. See attached log.

  2. The Access Concentrator of my ISP offers MTU values of both 1492
  and 1442. pppd-2.4.5 in Ubuntu 14.04 adopts 1492 as the MTU of the ppp
  device, while pppd-2.4.7 in Xenial adopts 1442. Setting the lower MTU
  on the WAN link (ppp0) can easily cause PMTU-D problems, especially
  for remote VPN clients.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sat Feb 20 09:56:32 2016
  IpRoute:
   default via 172.16.10.1 dev eth0  proto static  metric 100
   169.254.0.0/16 dev eth0  scope link  metric 1000
   172.16.10.0/24 dev eth0  proto kernel  scope link  src 172.16.10.32  metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-02-19 (0 days ago)
  WpaSupplicantLog:

  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Auto eth0   dff18f4d-6732-4eab-bd06-5209635b9bab  
/org/freedesktop/NetworkManager/ActiveConnection/11
   irda0   unknown   disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   eth1wifi  unavailable   /org/freedesktop/NetworkManager/Devices/3  
--  --

[Touch-packages] [Bug 1531331] [NEW] package linux-image-4.3.0-5-generic:amd64 4.3.0-5.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2016-01-05 Thread Jing Zhang
Public bug reported:

Occurred when updating for developing version.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-5-generic:amd64 4.3.0-5.16
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1532 F pulseaudio
Date: Wed Jan  6 11:39:10 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=834f3fa5-dc9a-4af7-a98c-e313151b96cf
InstallationDate: Installed on 2011-12-01 (1496 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: Intel Corporation Pine Trail - M CRB
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=11f904af-6544-471e-9153-2bc238d34d76 ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: initramfs-tools
Title: package linux-image-4.3.0-5-generic:amd64 4.3.0-5.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to xenial on 2016-01-05 (0 days ago)
dmi.bios.date: 06/24/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.asset.tag: PTL Nanjing
dmi.board.name: Pine Trail - M CRB
dmi.board.vendor: Intel Corporation
dmi.board.version: Revision A
dmi.chassis.asset.tag: None
dmi.chassis.type: 1
dmi.chassis.vendor: No
dmi.chassis.version: nclosure
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd06/24/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNo:ct1:cvrnclosure:
dmi.product.name: Pine Trail - M CRB
dmi.product.version: Revision A
dmi.sys.vendor: Intel Corporation

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package linux-image-4.3.0-5-generic:amd64 4.3.0-5.16 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Occurred when updating for developing version.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-5-generic:amd64 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1532 F pulseaudio
  Date: Wed Jan  6 11:39:10 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=834f3fa5-dc9a-4af7-a98c-e313151b96cf
  InstallationDate: Installed on 2011-12-01 (1496 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: Intel Corporation Pine Trail - M CRB
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=11f904af-6544-471e-9153-2bc238d34d76 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-32ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-4.3.0-5-generic:amd64 4.3.0-5.16 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-01-05 (0 days ago)
  dmi.bios.date: 06/24/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: PTL Nanjing
  dmi.board.name: Pine Trail - M CRB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: Revision A
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 1
  dmi.chassis.vendor: No
  

[Touch-packages] [Bug 1527144] [NEW] The "delete" function is invalid in history interface of Browser app.

2015-12-17 Thread freya zhang
Public bug reported:

Information:
current build number: 196
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en
last update: 2015-12-17 07:32:51
version version: 196
version ubuntu: 20151217
version device: 20151210-87377d3
version custom: 2015-918-8-52


Steps:1.Launch Browser app and view some webpage.
2.Tap the setting icon on top right and enter "History" interface.
3.Select one or several URL link and tap "Delete" button on top 
right.
4.Check the performance.

Actual result:The selected URL link should be deleted instead of still existing.
Expected result:The selected URL link still stay in the interface and there is 
no change.

Notes:Only by resetting the phone can delete the history URL.

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

Title:
  The "delete" function is invalid in history interface of Browser app.

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Information:
  current build number: 196
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-12-17 07:32:51
  version version: 196
  version ubuntu: 20151217
  version device: 20151210-87377d3
  version custom: 2015-918-8-52

  
  Steps:1.Launch Browser app and view some webpage.
  2.Tap the setting icon on top right and enter "History" interface.
  3.Select one or several URL link and tap "Delete" button on top 
right.
  4.Check the performance.

  Actual result:The selected URL link should be deleted instead of still 
existing.
  Expected result:The selected URL link still stay in the interface and there 
is no change.

  Notes:Only by resetting the phone can delete the history URL.

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

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


[Touch-packages] [Bug 1527464] [NEW] [trusty]Apt-get error in Azure repo due to “Hash Sum mismatch”

2015-12-17 Thread Scott Zhang
Public bug reported:

Description:
In Datastax deployment, the customer needs to install zulu. They follow the 
following steps:

1.  Log in as root or use sudo.
2.  Import Azul's public key.
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 
0x219BD9C9
3.  Add the Azul package to the APT repository.
•   For Ubuntu
$ sudo apt-add-repository 'deb http://repos.azulsystems.com/ubuntu stable main'

4.  Update the information about available packages.
$ sudo apt-get update
5.  Proceed to the installation section corresponding to your operating 
system and Zulu installer package.

error got:
Hit http://security.ubuntu.com trusty-security/main Translation-en
Hit http://security.ubuntu.com trusty-security/universe Translation-en
Fetched 6,205 B in 2s (2,295 B/s)
W: Failed to fetch 
http://repos.azulsystems.com/ubuntu/dists/stable/main/binary-amd64/Packages 
Hash Sum mismatch

This error has been seeing intermittently for at least weeks.

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

** Package changed: rsyslog (Ubuntu) => apt (Ubuntu)

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

Title:
  [trusty]Apt-get error in Azure repo due to “Hash Sum mismatch”

Status in apt package in Ubuntu:
  New

Bug description:
  Description:
  In Datastax deployment, the customer needs to install zulu. They follow the 
following steps:

  1.Log in as root or use sudo.
  2.Import Azul's public key.
  $ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 
0x219BD9C9
  3.Add the Azul package to the APT repository.
  • For Ubuntu
  $ sudo apt-add-repository 'deb http://repos.azulsystems.com/ubuntu stable 
main'

  4.Update the information about available packages.
  $ sudo apt-get update
  5.Proceed to the installation section corresponding to your operating 
system and Zulu installer package.

  error got:
  Hit http://security.ubuntu.com trusty-security/main Translation-en
  Hit http://security.ubuntu.com trusty-security/universe Translation-en
  Fetched 6,205 B in 2s (2,295 B/s)
  W: Failed to fetch 
http://repos.azulsystems.com/ubuntu/dists/stable/main/binary-amd64/Packages 
Hash Sum mismatch

  This error has been seeing intermittently for at least weeks.

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

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


[Touch-packages] [Bug 1520161] Re: The sound of music is not heard by a BT headset, it still comes from internal speaker after pairing with a BT headset.

2015-11-29 Thread freya zhang
Dear Simon Fels,
Following https://wiki.ubuntu.com/DebuggingBluetooth, I attach a syslog with 
debug output enabled.If you have any questions, please contact me freely.

Thanks.

Freya Zhang

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1520161/+attachment/4527401/+files/syslog

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

Title:
  The sound of music is not heard by a BT headset,it still comes from
  internal speaker after pairing with a BT headset.

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:LG Headset HBM-230

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect with the BT headset.
  2.Launch music app or music scope and play any music.
  3.Check the performance.

  Actual result:The music sound still comes form the internal speaker.
  Expected result:The music should come from BT headset,instead of internal 
speaker.

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

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


[Touch-packages] [Bug 1520161] Re: The sound of music is not heard by a BT headset, it still comes from internal speaker after pairing with a BT headset.

2015-11-29 Thread freya zhang
Dear Simon Fels,
Following https://wiki.ubuntu.com/DebuggingBluetooth, I attach a syslog with 
debug output enabled.If you have any questions, please contact me freely.

Thanks.

Freya Zhang

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1520161/+attachment/4527402/+files/syslog

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

Title:
  The sound of music is not heard by a BT headset,it still comes from
  internal speaker after pairing with a BT headset.

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:LG Headset HBM-230

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect with the BT headset.
  2.Launch music app or music scope and play any music.
  3.Check the performance.

  Actual result:The music sound still comes form the internal speaker.
  Expected result:The music should come from BT headset,instead of internal 
speaker.

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

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


[Touch-packages] [Bug 1520405] Re: The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
** Attachment added: "dbus.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1520405/+attachment/4526151/+files/dbus.log

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


[Touch-packages] [Bug 1520405] Re: The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1520405/+attachment/4526152/+files/syslog

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


[Touch-packages] [Bug 1520405] Re: The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1520405/+attachment/4526153/+files/syslog

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


[Touch-packages] [Bug 1520405] Re: The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
[Philips BT25]#info
Device FC:58:FA:11:D0:67 Philips BT25
Name: Nexus 4
Alias: Nexus 4
Class: 0x5c
Powered: yes
Discoverable: no
Pairable: yes
UUIDs:
  Headset AG(1112--1000-8000-00805f9b34fb)
  Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
  A/V Remote Control(110e--1000-8000-00805f9b34fb)
  SIM Access(112d--1000-8000-00805f9b34fb)
  Generic Access Profile(1800--1000-8000-00805f9b34fb)
  PnP Information   (1200--1000-8000-00805f9b34fb)
  A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  Audio Source  (110a--1000-8000-00805f9b34fb)
  Audio Sink(110b--1000-8000-00805f9b34fb)
  Handsfree Audio Gateway   (111f--1000-8000-00805f9b34fb)
  Message Notification Se.. (1133--1000-8000-00805f9b34fb)
  Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0523
Discovering: no

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


[Touch-packages] [Bug 1520405] Re: The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
** Attachment added: "application-legacy-ubuntu-system-settings-.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1520405/+attachment/4526150/+files/application-legacy-ubuntu-system-settings-.log

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


[Touch-packages] [Bug 1520405] [NEW] The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
Public bug reported:

Test Env:
current build number: 301
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2015-11-26 09:01:56
version version: 301
version ubuntu: 20151126
version device: 20150911
version custom: 20151126


BT speaker:Philips BT25


Precondition:
Some music saved in internal storage.

Steps:
1.Connect DUT with BT speaker and play any music.
2.Make a call to DUT.
3.After ending the call,the music plays again.Check the performance.

Actual result:The sound from BT speaker is  intermittent.
Expected result:The sound from BT speaker should be coherent.

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


[Touch-packages] [Bug 1520161] Re: The sound of music is not heard by a BT headset, it still comes from internal speaker after pairing with a BT headset.

2015-11-26 Thread freya zhang
[LG HBM-230]#info
Device 00:18:6B:20:AD:55 LG HBM-230
Name: LG HBM-230
Alias: LG HBM-230
Class: 0x200404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
ConnectedProfiles:
None
LegacyPairing: no
UUIDs:
  Headset   (1108--1000-8000-00805f9b34fb)
  Handsfree (111e--1000-8000-00805f9b34fb)

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

Title:
  The sound of music is not heard by a BT headset,it still comes from
  internal speaker after pairing with a BT headset.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:LG Headset HBM-230

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect with the BT headset.
  2.Launch music app or music scope and play any music.
  3.Check the performance.

  Actual result:The music sound still comes form the internal speaker.
  Expected result:The music should come from BT headset,instead of internal 
speaker.

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

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


[Touch-packages] [Bug 1520405] Re: The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
[Philips BT25]# info
Device FC:58:FA:11:D0:67
Name: Philips BT25
Alias: Philips BT25
Class: 0x260404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
ConnectedProfiles:
 A/V Remote Control(110e--1000-8000-00805f9b34fb)
  Audio Sink(110b--1000-8000-00805f9b34fb)
  Headset   (1108--1000-8000-00805f9b34fb)
LegacyPairing: no
UUIDs:
  Serial Port   (1101--1000-8000-00805f9b34fb)
  Headset   (1108--1000-8000-00805f9b34fb)
  Audio Sink(110b--1000-8000-00805f9b34fb)
  A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  A/V Remote Control(110e--1000-8000-00805f9b34fb)
  Handsfree (111e--1000-8000-00805f9b34fb)

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  New

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


Re: [Touch-packages] [Bug 1520405] Re: The sound from BT speaker is intermittent after ending the call.

2015-11-26 Thread freya zhang
After ending the call,the music is played again.The music is coming
throught the HFP headset.But the sound is intermittent.

Thanks.
Freya Zhang 

On 五, 2015-11-27 at 06:27 +, Simon Fels wrote:
> Can you describe a bit more in detail what happens after you've ended
> the call? Is music played again or not? Is the music coming throught he
> phone speaker or the HFP headset? ...
> 
> ** Tags added: bluetooth-ota9 bluez5
>

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

Title:
  The sound from BT speaker is intermittent after ending the call.

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Test Env:
  current build number: 301
  device name: mako
  channel: ubuntu-touch/rc-proposed/ubuntu
  last update: 2015-11-26 09:01:56
  version version: 301
  version ubuntu: 20151126
  version device: 20150911
  version custom: 20151126

  
  BT speaker:Philips BT25

  
  Precondition:
  Some music saved in internal storage.

  Steps:
  1.Connect DUT with BT speaker and play any music.
  2.Make a call to DUT.
  3.After ending the call,the music plays again.Check the performance.

  Actual result:The sound from BT speaker is  intermittent.
  Expected result:The sound from BT speaker should be coherent.

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

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


  1   2   >