[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

2018-06-25 Thread Chen-Han Hsiao (Stanley)
** Changed in: oem-priority
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-07-01 Thread Chen-Han Hsiao (Stanley)
** Changed in: oem-priority
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)

2018-10-02 Thread Chen-Han Hsiao (Stanley)
I found that this issue could also be triggered by chrome-remote-desktop

After uninstall chrome-remote-desktop, this issue is gone.
(In fact, disable remote connections also helps. Not necessary uninstall 
chrome-remote-desktop.)


DistroRelease: Ubuntu 18.04.1
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
Uname: Linux 4.15.0-34-generic x86_64

chrome-remote-desktop  69.0.3497.7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740106

Title:
  Gnome terminal not starting, timeout reached (bionic)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)

2018-10-02 Thread Chen-Han Hsiao (Stanley)
While remote connection is enabled for chrome-remote-desktop

There are environment variables for GUI login session. Such as:

CHROME_REMOTE_DESKTOP_SESSION=1
CHROME_USER_DATA_DIR=/home/vagrant/.config/chrome-remote-desktop/chrome-profile

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740106

Title:
  Gnome terminal not starting, timeout reached (bionic)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

2018-05-11 Thread Chen-Han Hsiao (Stanley)
** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770580] [NEW] 2-in-1 laptop won't auto-rotate after installation

2018-05-11 Thread Chen-Han Hsiao (Stanley)
Public bug reported:

Device: Dell Inspiron 5379 2-in-1 laptop
Image: ubuntu-18.04-desktop-amd64.iso

2-in-1 laptop won't auto-rotate after finishing installation.
iio-sensor-proxy.service is stopped during oem installation. But not restarted 
after install.

This issue will gone after reboot once.

** Affects: oem-priority
 Importance: Undecided
 Status: New

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

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770580

Title:
  2-in-1 laptop won't auto-rotate after installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1770580/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770580] Re: 2-in-1 laptop won't auto-rotate after installation

2018-05-11 Thread Chen-Han Hsiao (Stanley)
** Attachment added: "sosreport-u-Inspiron-5379-20180511040643.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1770580/+attachment/5137649/+files/sosreport-u-Inspiron-5379-20180511040643.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770580

Title:
  2-in-1 laptop won't auto-rotate after installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1770580/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] [NEW] ubiquity need mount point /sys/firmware/efi/efivars

2018-05-21 Thread Chen-Han Hsiao (Stanley)
Public bug reported:

Without mount point /sys/firmware/efi/efivars for target system,
ubiquity sometimes failed to install bootloader on target system.

May 21 08:21:55 ubuntu ubiquity[29387]: Setting up grub-efi-amd64 
(2.02-2ubuntu8) ...
May 21 08:21:56 ubuntu ubiquity[29387]:
May 21 08:21:56 ubuntu ubiquity[29387]: Creating config file /etc/default/grub 
with new version
May 21 08:21:56 ubuntu ubiquity[29387]: Installing for x86_64-efi platform.
May 21 08:21:57 ubuntu ubiquity[29387]: Skipping unreadable variable 
"Boot": Input/output error
May 21 08:21:57 ubuntu ubiquity[29387]: Could not prepare Boot variable: 
Input/output error
May 21 08:21:57 ubuntu ubiquity[29387]: grub-install: error: efibootmgr failed 
to register the boot entry: Input/output error.
May 21 08:21:57 ubuntu ubiquity[29387]: Failed: grub-install --target=x86_64-efi
May 21 08:21:57 ubuntu ubiquity[29387]: WARNING: Bootloader is not properly 
installed, system may not be bootable
May 21 08:21:57 ubuntu ubiquity[29387]: Setting up grub-efi-amd64-signed 
(1.93+2.02-2ubuntu8) ...
May 21 08:21:57 ubuntu ubiquity[29387]: Installing for x86_64-efi platform.
May 21 08:21:58 ubuntu ubiquity[29387]: Skipping unreadable variable 
"Boot": Input/output error
May 21 08:21:58 ubuntu ubiquity[29387]: Could not prepare Boot variable: 
Input/output error
May 21 08:21:58 ubuntu ubiquity[29387]: grub-install: error: efibootmgr failed 
to register the boot entry: Input/output error.
May 21 08:21:58 ubuntu ubiquity[29387]: dpkg: error processing package 
grub-efi-amd64-signed (--configure):
May 21 08:21:58 ubuntu ubiquity[29387]:  installed grub-efi-amd64-signed 
package post-installation script subprocess returned error exit status 1
May 21 08:21:58 ubuntu ubiquity[29387]: Errors were encountered while 
processing:
May 21 08:21:58 ubuntu ubiquity[29387]:  grub-efi-amd64-signed

** Affects: oem-priority
 Importance: Undecided
 Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

2018-05-21 Thread Chen-Han Hsiao (Stanley)
My patch to fix this issue:

** Patch added: "0001-add-mount-point-LP-1759196.patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1772374/+attachment/5142254/+files/0001-add-mount-point-LP-1759196.patch

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

2018-05-21 Thread Chen-Han Hsiao (Stanley)
installation failed:

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1772374/+attachment/5142253/+files/journal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

2018-05-21 Thread Chen-Han Hsiao (Stanley)
My patch to fix this issue:

** Patch removed: "0001-add-mount-point-LP-1759196.patch"
   
https://bugs.launchpad.net/oem-priority/+bug/1772374/+attachment/5142254/+files/0001-add-mount-point-LP-1759196.patch

** Patch added: "0001-add-mount-point-LP-1772374.patch"
   
https://bugs.launchpad.net/oem-priority/+bug/1772374/+attachment/5142256/+files/0001-add-mount-point-LP-1772374.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

2018-05-21 Thread Chen-Han Hsiao (Stanley)
http://manpages.ubuntu.com/manpages/bionic/man8/efibootmgr.8.html

Note: efibootmgr requires that the kernel support access to EFI non-
volatile variables through /sys/firmware/efi/vars or
/sys/firmware/efi/efivars/.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

2018-03-15 Thread Chen-Han Hsiao (Stanley)
For Intel GLK user: There is a upstream bug opened and fixed:
https://bugs.freedesktop.org/show_bug.cgi?id=100302

And this patch works for me on Intel Gemini Lake platform:
https://github.com/torvalds/linux/commit/ed69cd40685c949ec9c65701758bbf9e6840240f

This patch is merged starting from v4.15-rc1

** Bug watch added: freedesktop.org Bugzilla #100302
   https://bugs.freedesktop.org/show_bug.cgi?id=100302

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550779

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-05-01 Thread Chen-Han Hsiao (Stanley)
I'll keep identifying root cause for this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766890

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2018-05-01 Thread Chen-Han Hsiao (Stanley)
I could reproduce this issue with oem image (somerville 20170614-0).
With exactly the same error "dpkg: cycle found while processing
triggers:"

But can't reproduce this issue with oem image (columbia 20161201-0).

Attachment is the log for oem image (columbia 20161201-0).

** Attachment added: "sosreport-u-VirtualBox-20180502021308.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5131826/+files/sosreport-u-VirtualBox-20180502021308.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766890

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

2018-05-09 Thread Chen-Han Hsiao (Stanley)
seeded snap in Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180508)%

$ ll /var/lib/snapd/seed/snaps/
total 273560
drwxr-xr-x 2 root root  4096 May  8 04:23 ./
drwxr-xr-x 4 root root  4096 May  8 04:23 ../
-rw-r--r-- 2 root root  90828800 May  8 04:22 core_4571.snap
-rw-r--r-- 2 root root 146841600 May  8 04:22 gnome-3-26-1604_62.snap
-rw-r--r-- 2 root root   2428928 May  8 04:22 gnome-calculator_167.snap
-rw-r--r-- 2 root root  13594624 May  8 04:23 gnome-characters_86.snap
-rw-r--r-- 2 root root  22609920 May  8 04:23 gnome-logs_31.snap
-rw-r--r-- 2 root root   3813376 May  8 04:23 gnome-system-monitor_39.snap

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

2018-05-09 Thread Chen-Han Hsiao (Stanley)
After finishing the installation and reboot, this issue could be observed 
before connecting to internet. snapd restarts again and again and consuming 
high percentage of cpu.
(Daily Build image: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180508)%)

May  9 06:40:11 u-XPS-13-9360 systemd[1]: Starting Snappy daemon...
May  9 06:40:11 u-XPS-13-9360 systemd[1]: Started Snappy daemon.
May  9 06:40:17 u-XPS-13-9360 systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
May  9 06:40:17 u-XPS-13-9360 systemd[1]: Stopped Snappy daemon.
May  9 06:40:17 u-XPS-13-9360 systemd[1]: Starting Snappy daemon...
May  9 06:40:18 u-XPS-13-9360 systemd[1]: Started Snappy daemon.
May  9 06:40:22 u-XPS-13-9360 systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
May  9 06:40:22 u-XPS-13-9360 systemd[1]: Stopped Snappy daemon.
May  9 06:40:22 u-XPS-13-9360 systemd[1]: Starting Snappy daemon...
May  9 06:40:22 u-XPS-13-9360 systemd[1]: Started Snappy daemon.
May  9 06:40:29 u-XPS-13-9360 systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
May  9 06:40:29 u-XPS-13-9360 systemd[1]: Stopped Snappy daemon.
May  9 06:40:29 u-XPS-13-9360 systemd[1]: Starting Snappy daemon...
May  9 06:40:30 u-XPS-13-9360 systemd[1]: Started Snappy daemon.


$ snap version 
snap2.32.6
snapd   2.32.6
series  16
ubuntu  18.04
kernel  4.15.0-20-generic

$ snap changes 
ID   Status  Spawn Ready Summary
1Error   2018-05-09T10:40:16Z  2018-05-09T10:40:23Z  Initialize system state
2Done2018-05-09T10:40:16Z  2018-05-09T10:45:20Z  Initialize device
3Error   2018-05-09T10:40:27Z  2018-05-09T10:40:35Z  Initialize system state
4Error   2018-05-09T10:40:38Z  2018-05-09T10:40:45Z  Initialize system state
5Error   2018-05-09T10:40:48Z  2018-05-09T10:40:56Z  Initialize system state
6Error   2018-05-09T10:40:59Z  2018-05-09T10:41:07Z  Initialize system state
7Error   2018-05-09T10:41:10Z  2018-05-09T10:41:18Z  Initialize system state
8Error   2018-05-09T10:41:21Z  2018-05-09T10:41:30Z  Initialize system state
9Error   2018-05-09T10:41:33Z  2018-05-09T10:41:42Z  Initialize system state
10   Error   2018-05-09T10:41:45Z  2018-05-09T10:41:54Z  Initialize system state
11   Error   2018-05-09T10:41:57Z  2018-05-09T10:42:07Z  Initialize system state
12   Error   2018-05-09T10:42:10Z  2018-05-09T10:42:19Z  Initialize system state
13   Error   2018-05-09T10:42:22Z  2018-05-09T10:42:32Z  Initialize system state
14   Error   2018-05-09T10:42:35Z  2018-05-09T10:42:45Z  Initialize system state
15   Error   2018-05-09T10:42:48Z  2018-05-09T10:42:58Z  Initialize system state
16   Error   2018-05-09T10:43:02Z  2018-05-09T10:43:13Z  Initialize system state
17   Error   2018-05-09T10:43:16Z  2018-05-09T10:43:27Z  Initialize system state
18   Error   2018-05-09T10:43:30Z  2018-05-09T10:43:42Z  Initialize system state
19   Error   2018-05-09T10:43:46Z  2018-05-09T10:43:58Z  Initialize system state
20   Error   2018-05-09T10:44:01Z  2018-05-09T10:44:13Z  Initialize system state
21   Error   2018-05-09T10:44:16Z  2018-05-09T10:44:28Z  Initialize system state
22   Error   2018-05-09T10:44:31Z  2018-05-09T10:44:50Z  Initialize system state
23   Error   2018-05-09T10:44:53Z  2018-05-09T10:46:37Z  Initialize system state

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

2018-05-09 Thread Chen-Han Hsiao (Stanley)
output of "snap tasks --last=seed"

This issue could be reproduced on every platform.

** Attachment added: "snap-tasks-seed.txt"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767896/+attachment/5136966/+files/snap-tasks-seed.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

2018-05-09 Thread Chen-Han Hsiao (Stanley)
Note that this issue doesn't happen with official released image
ubuntu-18.04-desktop-amd64.iso.

But does happen with daily build image http://cdimage.ubuntu.com/bionic
/daily-live/pending/bionic-desktop-amd64.iso (For example, 20180508)

I think this issue is introduced between 2018-04-24 and 2018-04-30

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

2018-05-10 Thread Chen-Han Hsiao (Stanley)
** Changed in: oem-priority
 Assignee: (unassigned) => Chen-Han Hsiao (Stanley) (swem)

** Changed in: oem-priority
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

2018-05-10 Thread Chen-Han Hsiao (Stanley)
Code for fetching seeded snap while image building:

https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
build/functions?id=af65a5affaecdf538c2d7e90775e9e5c4de8af09#n387

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

2018-05-10 Thread Chen-Han Hsiao (Stanley)
gtk-common-themes is not published in channel "stable/ubuntu-18.04",
thus the image building will fail.

Hi, chipaca
Could you help to publish gtk-common-themes in channel "stable/ubuntu-18.04".


Ref:

$ SNAPPY_STORE_NO_CDN=1 snap download --channel=stable/ubuntu-18.04 
gtk-common-themes
Fetching snap "gtk-common-themes"
error: cannot find snap "gtk-common-themes": snap not found

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

2018-05-10 Thread Chen-Han Hsiao (Stanley)
Also proposed code changes to ubuntu seeds:

https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.cosmic/+merge/345355
https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.bionic/+merge/345356

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529715] Re: ASUSTek Computer, Inc. AC51 Wireless Adapter [Mediatek MT7610/Ralink RT2870] doesn't work on ubuntu 14.04 LTS &15.10 with kernel 3.19&4.2 & 4.4

2018-12-28 Thread Chen-Han Hsiao (Stanley)
Starting from Linux Kernel 4.19, the Asus USB-AC51 is supported.

See
https://github.com/torvalds/linux/blob/v4.19/drivers/net/wireless/mediatek/mt76/mt76x0/usb.c#L30

You might wanna give it a try.

(Try install all the following debian packages:
 linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
 linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb


 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/ )

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529715

Title:
  ASUSTek Computer, Inc. AC51 Wireless Adapter [Mediatek MT7610/Ralink
  RT2870]  doesn't work on ubuntu 14.04 LTS &15.10 with kernel 3.19&4.2
  & 4.4

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

2018-05-22 Thread Chen-Han Hsiao (Stanley)
This issue fixed in daily build bionic-desktop-amd64.iso (20180522)

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

2018-05-22 Thread Chen-Han Hsiao (Stanley)
Proposed for merging:

https://code.launchpad.net/~swem/ubiquity/+git/ubiquity/+merge/346665
https://code.launchpad.net/~swem/ubiquity/+git/ubiquity/+merge/34


** Changed in: oem-priority
 Assignee: (unassigned) => Chen-Han Hsiao (Stanley) (swem)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] [NEW] snapd didn't initialize all the seeded snaps

2018-05-23 Thread Chen-Han Hsiao (Stanley)
Public bug reported:

snapd didn't initialize all the seeded snaps

bionic-desktop-amd64.iso (20180522)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: snapd 2.32.9+18.04
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 22 22:59:18 2018
InstallationDate: Installed on 2018-05-23 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: oem-priority
 Importance: Undecided
 Assignee: Chen-Han Hsiao (Stanley) (swem)
 Status: New

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


** Tags: amd64 apport-bug bionic package-from-proposed third-party-packages

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Chen-Han Hsiao (Stanley) (swem)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-05-23 Thread Chen-Han Hsiao (Stanley)
$ ll /var/lib/snapd/seed/snaps/
total 305668
drwxr-xr-x 2 root root  4096 May 22 04:17 ./
drwxr-xr-x 4 root root  4096 May 22 04:17 ../
-rw-r--r-- 2 root root  90812416 May 22 04:15 core_4650.snap
-rw-r--r-- 2 root root 146276352 May 22 04:15 gnome-3-26-1604_64.snap
-rw-r--r-- 2 root root   2428928 May 22 04:15 gnome-calculator_167.snap
-rw-r--r-- 1 root root  13594624 May 22 04:16 gnome-characters_86.snap
-rw-r--r-- 1 root root  22609920 May 22 04:16 gnome-logs_31.snap
-rw-r--r-- 1 root root   3813376 May 22 04:16 gnome-system-monitor_39.snap
-rw-r--r-- 1 root root  33460224 May 22 04:17 gtk-common-themes_3.snap

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-05-23 Thread Chen-Han Hsiao (Stanley)
output of

snap tasks --last=seed

** Attachment added: "snap-tasks-last-seed.txt"
   
https://bugs.launchpad.net/oem-priority/+bug/1772844/+attachment/5143197/+files/snap-tasks-last-seed.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-05-23 Thread Chen-Han Hsiao (Stanley)
output of:

snap list

** Attachment added: "snap-list.txt"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1772844/+attachment/5143198/+files/snap-list.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-05-23 Thread Chen-Han Hsiao (Stanley)
The snapd stuck here:

$ snap watch --last=seed
Automatically connect eligible plugs and slots of snap "gnome-calculator"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-05-23 Thread Chen-Han Hsiao (Stanley)
** Attachment added: "seed.yaml"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1772844/+attachment/5143203/+files/seed.yaml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

2018-05-23 Thread Chen-Han Hsiao (Stanley)
I've confirmed #10 works. File merge proposal:

https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.cosmic/+merge/346726
https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.bionic/+merge/346727

** Package changed: snapd (Ubuntu) => ubuntu-meta (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-02-24 Thread Chen-Han Hsiao (Stanley)
This issue could be reproduced with following command. More easily to be
reproduced with narrow terminal (such as 40 characters width)

wget http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04
-desktop-amd64.iso

This issue has been fixed by the following commit
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=7099f4899880eaefc2c40a3dc7693ab4174a819b

>From 7099f4899880eaefc2c40a3dc7693ab4174a819b Mon Sep 17 00:00:00 2001
From: Darshit Shah 
Date: Mon, 22 Feb 2016 15:08:15 +0100
Subject: [PATCH] Sanitize value sent to memset to prevent SEGFAULT

---
 src/progress.c | 5 +
 1 file changed, 5 insertions(+)

diff --git a/src/progress.c b/src/progress.c
index 93f6246..8a5df21 100644
--- a/src/progress.c
+++ b/src/progress.c
@@ -1164,6 +1164,8 @@ create_image (struct bar_progress *bp, double 
dl_total_time, bool done)
 }
 
   padding = bp->width - count_cols (bp->buffer);
+  assert (padding > 0 && "Padding length became non-positive!");
+  padding = padding > 0 ? padding : 0;
   memset (p, ' ', padding);
   p += padding;
   *p = '\0';
@@ -1174,6 +1176,9 @@ create_image (struct bar_progress *bp, double 
dl_total_time, bool done)
* from the release code since we do not want Wget to crash and burn when the
* assertion fails. Instead Wget should continue downloading and display a
* horrible and irritating progress bar that spams the screen with newlines.
+   *
+   * By default, all assertions are disabled in a Wget build and are enabled
+   * only with the --enable-assert configure option.
*/
   assert (count_cols (bp->buffer) == bp->width);
 }
-- 
2.7.4


** Patch added: "wget_1.17.1-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+attachment/4825717/+files/wget_1.17.1-1ubuntu1.2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573307

Title:
  wget crashed with SIGSEGV in __memset_avx2()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-02-24 Thread Chen-Han Hsiao (Stanley)
Hi,

I made a testing PPA at ppa:swem/lp1573307
Please help to check if it can fix this issue for you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573307

Title:
  wget crashed with SIGSEGV in __memset_avx2()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-02-28 Thread Chen-Han Hsiao (Stanley)
Hi, Murray

Thanks you help, I will update the bug description.

Also, after checking the latest wget source code, I think upstream
commit
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=7cb9efa668f80ab5ca4d25133c3133e10473d1ef
is also needed.

>From 7cb9efa668f80ab5ca4d25133c3133e10473d1ef Mon Sep 17 00:00:00 2001
From: Darshit Shah 
Date: Sat, 5 Mar 2016 11:58:53 +0100
Subject: [PATCH] Fix assertion in Progress bar

* src/progress.c (create_image): Fix off-by-one error in assert()
statement for progress bar width.
Reported-By: Gisle Vanem 
---
 src/progress.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/progress.c b/src/progress.c
index 8a5df21..481e21e 100644
--- a/src/progress.c
+++ b/src/progress.c
@@ -1164,7 +1164,7 @@ create_image (struct bar_progress *bp, double 
dl_total_time, bool done)
 }
 
   padding = bp->width - count_cols (bp->buffer);
-  assert (padding > 0 && "Padding length became non-positive!");
+  assert (padding >= 0 && "Padding length became non-positive!");
   padding = padding > 0 ? padding : 0;
   memset (p, ' ', padding);
   p += padding;
-- 
2.7.4


Update debdiff

** Patch added: "wget_1.17.1-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+attachment/4828036/+files/wget_1.17.1-1ubuntu1.2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573307

Title:
  wget crashed with SIGSEGV in __memset_avx2()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-02-28 Thread Chen-Han Hsiao (Stanley)
** Description changed:

+ [Impact] 
+  * wget will crash while displaying progress bar under narrow terminal
+  * Upstream already has fixed this issue in commit 7099f489 and 7cb9efa6
+ Steps to reproduce:
+   1. execute "wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest";
 under a narrow terminal (such as width less than 40 characters)
+ Problems:
+   1. The wget crash with segmentation fault
+ Expected behavior:
+   1. wget will not crash
+ 
+ [Test Case]
+   After upgrading to the new version, the repeating the above steps should 
give expected behavior.
+ 
+ [Regression Potential]
+   Potential of causing regression is relatively small for a two line change 
for assertion check
+ 
+ [Other Info]
+ 
+ 
+ 
  EDIT(other user): The crash actually happens when the terminal window is
  too small.
  
  When I try to download a big file with wget on Ubuntu 16.04 it crashes
  after a couple seconds.
  
  To reproduce the bug try the following:
  
  wget http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  
  I've asked another guy on IRC on channel #ubuntu-it to try and reproduce this 
bug
  and he said it was crashing also on his machine.
  
  evan@HPPC:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  evan@HPPC:~$ apt-cache policy wget
  wget:
-   Installato: 1.17.1-1ubuntu1
-   Candidato:  1.17.1-1ubuntu1
-   Tabella versione:
-  *** 1.17.1-1ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installato: 1.17.1-1ubuntu1
+   Candidato:  1.17.1-1ubuntu1
+   Tabella versione:
+  *** 1.17.1-1ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:34:10 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: wget 
http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  SegvAnalysis:
-  Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
-  PC (0x7f4eac3b7328) ok
-  source "%al" ok
-  destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
+  Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
+  PC (0x7f4eac3b7328) ok
+  source "%al" ok
+  destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
-  __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
-  ?? ()
-  ?? ()
-  ?? ()
-  ?? ()
+  __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
+  ?? ()
+  ?? ()
+  ?? ()
+  ?? ()
  Title: wget crashed with SIGSEGV in __memset_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573307

Title:
  wget crashed with SIGSEGV in __memset_avx2()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723915] Re: [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

2017-11-13 Thread Chen-Han Hsiao (Stanley)
Check on Wyse 3040

with Ubuntu Desktop 17.10

This issue is gone after upgrade linux-generic from 4.13.0.16.17 to
4.13.0.17.18

Install: linux-signed-image-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic), 
linux-image-extra-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic), 
linux-headers-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic), 
linux-headers-4.13.0-17:amd64 (4.13.0-17.20, automatic), 
linux-image-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic)
Upgrade: linux-headers-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-image-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-signed-image-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-signed-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), linux-generic:amd64 
(4.13.0.16.17, 4.13.0.17.18)
End-Date: 2017-11-13  02:24:30

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723915

Title:
  [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1723915/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723913] Re: [Artful] Support headset mode for DELL WYSE

2017-11-13 Thread Chen-Han Hsiao (Stanley)
Headset mode is supported after upgrade linux-generic 4.13.0.16.17 to
4.13.0.17.18.

Install: linux-image-extra-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic), 
linux-headers-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic), 
linux-headers-4.13.0-17:amd64 (4.13.0-17.20, automatic), 
linux-image-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic)
Upgrade: linux-headers-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-image-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), linux-generic:amd64 
(4.13.0.16.17, 4.13.0.17.18)
End-Date: 2017-11-13  02:49:00


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723913

Title:
  [Artful] Support headset mode for DELL WYSE

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1723913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1711756] Re: Chromium crashes when changing profiles

2017-08-28 Thread Chen-Han Hsiao (Stanley)
I've also encountered this issue.

$ dpkg --list | grep chromium 
ii  chromium-browser   60.0.3112.78-0ubuntu0.16.04.1293 
amd64Chromium web browser, open-source version of Chrome
ii  chromium-browser-l10n  60.0.3112.78-0ubuntu0.16.04.1293 
all  chromium-browser language packages
ii  chromium-codecs-ffmpeg-extra   60.0.3112.78-0ubuntu0.16.04.1293 
amd64Extra ffmpeg codecs for the Chromium Browser
ii  unity-scope-chromiumbookmarks  0.1+13.10.20130723-0ubuntu1  
all  Chromium bookmarks scope for Unity

DistroRelease: Ubuntu 16.04
Uname: Linux 4.10.0-33-generic x86_64
"Use system title bar and borders" is turned off.



Received signal 11 SEGV_MAPERR 
#0 0x7ff82038e3f7 base::debug::StackTrace::StackTrace()
#1 0x7ff82038df6f 
#2 0x7ff820b31390 
  r8: 55ba72b2cc90  r9:  r10: 0008588a r11: 
7ff806d96350
 r12: 55ba71b80b60 r13: 55ba71d975c0 r14: 55ba72c92a80 r15: 
7fffa20bacc0
  di: 55ba722d6868  si: 55ba72c92a80  bp: 7fffa20bb110  bx: 
7fffa20baca0
  dx: 0003  ax: 55ba722d7be0  cx: 0002  sp: 
7fffa20bac98
  ip:  efl: 00010202 cgf: 002b0033 erf: 
0014
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[1:1:0100/00.715193:ERROR:broker_posix.cc(41)] Invalid node channel message
[1:1:0100/00.715989:ERROR:broker_posix.cc(41)] Invalid node channel message

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711756

Title:
  Chromium crashes when changing profiles

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1573959] Re: On-screen text disappears after suspend

2017-04-11 Thread Chen-Han Hsiao (Stanley)
It's been 50 days since I upgraded from 16.04 kernel 4.4 to LTS
Enablement Stack kernel 4.8 and I haven't had this issue again.

https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Ubuntu_16.04_LTS_-
_Xenial_Xerus


$ lspci -nn | egrep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06)

$ uname -a
Linux USER-PC 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573959

Title:
  On-screen text disappears after suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1573959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

2017-03-28 Thread Chen-Han Hsiao (Stanley)
After enabled xenial-proposed and upgrade wget to 1.17.1-1ubuntu1.2,
this issue is fixed.

Reproduce Step:
1. download 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
 via wget within narrow terminal (< 40 characters)


 wget 1.17.1-1ubuntu1.1 
$ wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
--2017-03-28 07:06:55--  
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
Resolving old-releases.ubuntu.com (old-releases.ubuntu.com)... 91.189.88.17
Connecting to old-releases.ubuntu.com 
(old-releases.ubuntu.com)|91.189.88.17|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 64142 (63K) [application/x-ms-manifest]
Saving to: 'ubuntu-16.04-desktop-amd64.manifest.2'

Segmentation fault (core dumped)



 wget 1.17.1-1ubuntu1.2 
$ wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
--2017-03-28 07:07:17--  
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
Resolving old-releases.ubuntu.com (old-releases.ubuntu.com)... 91.189.88.17
Connecting to old-releases.ubuntu.com 
(old-releases.ubuntu.com)|91.189.88.17|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 64142 (63K) [application/x-ms-manifest]
Saving to: 'ubuntu-16.04-desktop-amd64.manifest.3'

ubuntu-16.04-desktop-amd64.manifest.3
100%[==>]
62.64K  --.-KB/sin 0.007s

2017-03-28 07:07:17 (8.19 MB/s) - 'ubuntu-16.04-desktop-amd64.manifest.3' saved 
[64142/64142]


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573307

Title:
  wget crashed with SIGSEGV in __memset_avx2()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1471983] Re: USB HDD makes lshw seg-fault when run as root

2015-09-03 Thread Chen-Han Hsiao (Stanley)
I also encounter this issue in Ubuntu OEM project.

This bug is fixed in
https://github.com/lyonel/lshw/commit/d048d300b5daeb44887a7fc06ddeb120119cac8a

The issue in upstream: [lshw segfaults, with some 16GB USB-3 sticks from
Patriot] http://www.ezix.org/project/ticket/653

I've made a patch to fix it.

** Bug watch added: Ezix Trac #653
   http://ezix.org/project/ticket/653

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471983

Title:
  USB HDD makes lshw seg-fault when run as root

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1494135] [NEW] Microphone mute hotkey for Dell Precision series

2015-09-09 Thread Chen-Han Hsiao (Stanley)
Public bug reported:

Microphone mute hotkey on Dell Precision series is needed to be support.
I encounter this issue on Ubuntu OEM project.

This feature is similar to microphone mute hotkey on Dell Latitude
series.

I've submit a patch to systemd upstream and have been merged.
https://github.com/systemd/systemd/commit/0018e4e47947b1a65855e8404480131e9d0c93ca
Now we can backport to Ubuntu system.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494135

Title:
  Microphone mute hotkey for Dell Precision series

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1494135] Re: Microphone mute hotkey for Dell Precision series

2015-09-10 Thread Chen-Han Hsiao (Stanley)
For trusty, this commit could fix this issue.
http://bazaar.launchpad.net/~swem/ubuntu/trusty/systemd/lp1494135/revision/3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494135

Title:
  Microphone mute hotkey for Dell Precision series

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1494135] Re: Microphone mute hotkey for Dell Precision series

2015-09-14 Thread Chen-Han Hsiao (Stanley)
I've verify the package

libudev1 204-5ubuntu20.14
udev 204-5ubuntu20.14

which fix this issue.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1494135

Title:
  Microphone mute hotkey for Dell Precision series

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1512262] [NEW] language-pack-gnome-ja-base 1:14.04+20150804 not published in trusty-updates, cause language-pack-gnome-ja installation error

2015-11-02 Thread Chen-Han Hsiao (Stanley)
Public bug reported:

With trusty and trusty-updates repository, installation of language-
pack-gnome-ja failed due to unmet dependencies.

The following packages have unmet dependencies:
 language-pack-gnome-ja : Depends: language-pack-gnome-ja-base (>= 
1:14.04+20150804) but it is not going to be installed
 language-pack-ja : Depends: language-pack-ja-base (>= 1:14.04+20150804) but it 
is not going to be installed

Release of Ubuntu: 14.04 trusty
Expect to happened: Can install language-pack-ja with apt-get successfully.
Actual happened: Installation failed due to unmet dependencies.

** Affects: language-pack-gnome-ja-base (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512262

Title:
  language-pack-gnome-ja-base 1:14.04+20150804 not published in trusty-
  updates, cause language-pack-gnome-ja installation error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1512262] Re: language-pack-gnome-ja-base 1:14.04+20150804 not published in trusty-updates, cause language-pack-gnome-ja installation error

2015-11-02 Thread Chen-Han Hsiao (Stanley)
$ apt-cache policy language-pack-gnome-ja
language-pack-gnome-ja:
  Installed: (none)
  Candidate: 1:14.04+20150804
  Version table:
 1:14.04+20150804 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
 1:14.04+20140410 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
$ apt-cache policy language-pack-gnome-ja-base
language-pack-gnome-ja-base:
  Installed: (none)
  Candidate: 1:14.04+20140410
  Version table:
 1:14.04+20140410 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512262

Title:
  language-pack-gnome-ja-base 1:14.04+20150804 not published in trusty-
  updates, cause language-pack-gnome-ja installation error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1512262] Re: language-pack-gnome-ja-base 1:14.04+20150804 not published in trusty-updates, cause language-pack-gnome-ja installation error

2015-11-02 Thread Chen-Han Hsiao (Stanley)
language-pack-gnome-ja-base 1:14.04+20150804 already in trusty-proposed
repository. But not yet published in trusty-updates.

See
https://launchpad.net/ubuntu/+source/language-pack-gnome-ja-base

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512262

Title:
  language-pack-gnome-ja-base 1:14.04+20150804 not published in trusty-
  updates, cause language-pack-gnome-ja installation error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 135355] Re: Bug 1353355

2016-02-21 Thread Chen-Han Hsiao (Stanley)
Hi, kailang

By the way,

The bug id should be 1535533

external microphone can't be detected

Best.
Stanley.

On Mon, Feb 22, 2016 at 3:20 PM, Kailang  wrote:

> OK, Thanks.
>
> I will check with our SD.
>
> > -Original Message-
> > From: David Henningsson [mailto:david.hennings...@canonical.com]
> > Sent: Friday, February 19, 2016 6:39 PM
> > To: Stanley Hsiao; TienFu Chen; Kent Lin; Kailang
> > Cc: 135...@bugs.launchpad.net
> > Subject: Bug 1353355
> >
> > Hi Kailang,
> >
> > Stanley Hsiao and I have again confirmed the bug of sound
> > coming from speaker even though the "Speaker Playback Switch"
> > is muted, and the amp-out on 0x14 is 0x80 (muted). In
> > addition "Speaker Playback Volume"
> > was also set to the minimum value (see the amp-out on node
> > 0x02) so that should *also* have prevented the speaker from
> > having output.
> >
> > Note that this bug is only present after applying your patch
> > to enable UAJ on the codec.
> >
> > The attached alsa-info is taken while sound was playing back
> > through the speaker even when it was supposed to be muted. I
> > hope it can be of assistance to you. Thanks!
> >
> > --
> > David Henningsson, Canonical Ltd.
> > https://launchpad.net/~diwic
> >
> > --Please consider the environment before printing this e-mail.
> >



-- 
Chen-Han (Stanley) Hsiao 蕭辰翰
Software Engineer / Mainstream OEM / Professional Engineering Services
stanley.hs...@canonical.com
https://launchpad.net/~swem

Canonical Ltd.
Room D, 46F, No. 7, Xin Yi Rd., Sec.5, Taipei 101, 11049 Taiwan
11049 台北市信義區信義路 5 段 7 號 46 樓 D 室
Phone: 886-2-8729-6856

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/135355

Title:
  error on installation of isdnutils

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs