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

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

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

$ 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

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

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

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

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

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

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

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

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.

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

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.

[Bug 135355] Re: Bug 1353355

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

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

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

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

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

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

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

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

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

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

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

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

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

[Bug 1711756] Re: Chromium crashes when changing profiles

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.

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

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

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

** 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.ne

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

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

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

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

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

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

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

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"

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

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,

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

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

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

$ 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

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

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

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

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

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

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

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

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.

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

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 notificat

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

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,

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

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:

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

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

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

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

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

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.

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

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

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

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

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

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,

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

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:

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

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

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

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

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

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

[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

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: