[Touch-packages] [Bug 1802689] Re: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot
Hi Adam: Could you try 4.19 kernel with i2c_i801 loaded? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/ to see if it is fixed? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1802689 Title: Upgrade to kmod (25-1ubuntu1.1) causes Lenovo x240 laptop to hang on boot Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in kmod source package in Xenial: Fix Committed Status in linux source package in Xenial: Incomplete Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Incomplete Status in kmod source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Incomplete Bug description: After upgrading my Lenovo x240 laptop to kmod (25-1ubuntu1.1), it hangs on boot. After blacklisting i2c_i801 everything works great again. I realize that this was a fix for bug 1786574, and that helps some other folks out. I'm not sure what the right fix is but there's got to be something that works for everyone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1802689/+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 1804437] Re: Saving new password for VPN (IPSec) fails silently
Thanks ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=797392 Importance: Unknown Status: Unknown -- 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/1804437 Title: Saving new password for VPN (IPSec) fails silently Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Triaged Bug description: Ubuntu: 18.04 Involved packages (non-exhaustive list): network-manager, vpnc Steps to reproduce: 1) Open "Network Connections" dialog 2) Add a non-existing entry for a working IPSec VPN connection, fill all required fields but enter a wrong password 3) Save the entry 4) Edit entry again, put in the correct password, make sure to fill all required fields 5) Save the entry 6) Open Edit view of the entry again to verify that the password has not been changed with last save action. Expected behavior: Either password should be stored when modified and saved -OR- user should be notified that password could not be saved for whatever reason. Work-around: Delete whole VPN entry and create a new one with the correct password entered from the beginning. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1804437/+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 1774419] Re: easy_install command is missing
That has been reported to Debian as well, https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=896652 ** Bug watch added: Debian Bug tracker #896652 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896652 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1774419 Title: easy_install command is missing Status in python-setuptools package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 Package: python-setuptools Version: 39.0.1-2 This package installs the easy_install module, but the command is missing: deploy@controller0:~$ which easy_install deploy@controller0:~$ echo $? 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1774419/+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 1561278] Re: internal sound card not detected HP X2
@Simon, see comment #34? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1804755] Re: SRU of LXC 3.0.3 (upstream bugfix release)
This bug was fixed in the package lxc - 3.0.3-0ubuntu1
---
lxc (3.0.3-0ubuntu1) disco; urgency=medium
* New upstream bugfix release (LP: #1804755):
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style in introduction
- CONTRIBUTING: Add 'be' to fix grammar
- CODING_STLYE: Simplify explanation for use of 'extern'
- CODING_STLYE: Remove sections implied by 'kernel style'
- CODING_STYLE: Fix non-uniform heading level
- CODING_STYLE: Update section header format
- cmd: Use parenthesis around complex macro
- cmd: Use 'void' instead of empty parameter list
- cmd: Do not use braces for single statement block
- cmd: Fix whitespace issues
- cmd: Use 'const' for static string constant.
- cmd: Remove unnecessary whitespace in string
- cmd: Put trailing */ on a separate line
- cmd: Remove typo'd semicolon
- cmd: Do not use comparison to NULL
- lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
- tools: lxc-attach: add default log priority & cleanups
- tools: lxc-cgroup: add default log priority & cleanups
- tools: lxc-checkpoint: add default log priority & cleanups
- tools: lxc-console: add default log priority & cleanups
- tools: lxc-create: add default log priority & cleanups
- tools: lxc-destroy: add default log priority & cleanups
- tools: lxc-device: add default log priority & cleanups
- tools: lxc-execute: add default log priority & cleanups
- tools: lxc-start: add default log priority & cleanups
- tools: lxc-stop: add default log priority & cleanups
- tools: lxc-freeze: add default log priority & cleanups
- tools: lxc-unfreeze: add default log priority & cleanups
- storage_utils: move duplicated function from tools
- tools: fix lxc-execute command parsing
- lseek - integer overflow
- cmd: lxc-user-nic: change log macro & cleanups
- cmd: lxc-usernsexec reorder includes
- cmd: move declarations to macro.h
- cmd: use utils.{c,h} helpers in lxc-usernsexec
- cmd: simplify lxc-usernsexec
- cmd: use safe number parsers in lxc-usernsexec
- macro: add missing headers
- macro: add macvlan properties
- tools: Indicate container startup failure
- storage: exit() => _exit(). when exec is failed
- tools: lxc-wait: add default log priority & cleanups
- conf: fix path/lxcpath mixups in tty setup
- cmd: use goto for cleanup in lxc-usernsexec
- cmd: Do not reassign variable before it is used
- cmd: Reduce scope of 'count' variable
- cmd: Fix format issues found by clang-format
- list: fix indent
- utils: split into {file,string}_utils.{c,h}
- pam_cgfs: build from the same sources as liblxc
- conf: fix devpts mounting when fully unprivileged
- macro: s/rexit()/_exit()/g
- attach: move struct declaration to top
- macro: move macros from attach.c
- Makefile: don't allow undefined symbols
- autotools: check if compiler is new enough
- log: handle strerror_r() versions
- autotools: add --{disable,enable}-thread-safety
- log: fail build on ENFORCE_THREAD_SAFETY error
- {file,string}_utils: remove NO_LOG
- initutils: remove useless comment
- string_utils: remove unnecessary include
- string_utils: remove unused headers
- string_utils: add remove_trailing_slashes()
- Makefile: remove last pam_cgfs special-casing
- conf: add missing headers
- Fix typo
- ifaddrs: add safe implementation of getifaddrs()
- Makefile: conditionalize ifaddrs.h inclusion
- execute: skip lxc-init logging when unprivileged
- execute: pass /proc/self/fd/
- tests: cleanup get_item.c
- build: fix musl
- configure: reorder header checks
- compiler: add compiler.h header
- commands: return -1 on lxc_cmd_get_init_pid() err
- tests: add basic.c
- tests: cleanup Makefile
- commands: ensure -1 is sent on EPIPE for init pid
- macro: add LXC_AUDS_ADDR_LEN
- macro: move LXC_CMD_DATA_MAX from commands.h
- macro: add PTR_TO_INT() and INT_TO_PTR()
- macro: add INTTYPE_TO_STRLEN()
- caps: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- cgfsng: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- confile: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- log: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lsm: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- macro: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lxccontainer: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- monitor: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- network: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- string_utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tools: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- conf: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tests:
[Touch-packages] [Bug 1804755] Re: SRU of LXC 3.0.3 (upstream bugfix release)
Uploaded to disco, will wait for autopkgtest to be happy before I start
pushing the SRUs.
** Changed in: lxc (Ubuntu Xenial)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Bionic)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Cosmic)
Assignee: (unassigned) => Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Disco)
Assignee: (unassigned) => Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1804755
Title:
SRU of LXC 3.0.3 (upstream bugfix release)
Status in lxc package in Ubuntu:
In Progress
Status in lxc source package in Xenial:
Triaged
Status in lxc source package in Bionic:
Triaged
Status in lxc source package in Cosmic:
Triaged
Status in lxc source package in Disco:
In Progress
Bug description:
LXC upstream released LXC 3.0.3 as a bugfix release with following
changelog:
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style in introduction
- CONTRIBUTING: Add 'be' to fix grammar
- CODING_STLYE: Simplify explanation for use of 'extern'
- CODING_STLYE: Remove sections implied by 'kernel style'
- CODING_STYLE: Fix non-uniform heading level
- CODING_STYLE: Update section header format
- cmd: Use parenthesis around complex macro
- cmd: Use 'void' instead of empty parameter list
- cmd: Do not use braces for single statement block
- cmd: Fix whitespace issues
- cmd: Use 'const' for static string constant.
- cmd: Remove unnecessary whitespace in string
- cmd: Put trailing */ on a separate line
- cmd: Remove typo'd semicolon
- cmd: Do not use comparison to NULL
- lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
- tools: lxc-attach: add default log priority & cleanups
- tools: lxc-cgroup: add default log priority & cleanups
- tools: lxc-checkpoint: add default log priority & cleanups
- tools: lxc-console: add default log priority & cleanups
- tools: lxc-create: add default log priority & cleanups
- tools: lxc-destroy: add default log priority & cleanups
- tools: lxc-device: add default log priority & cleanups
- tools: lxc-execute: add default log priority & cleanups
- tools: lxc-start: add default log priority & cleanups
- tools: lxc-stop: add default log priority & cleanups
- tools: lxc-freeze: add default log priority & cleanups
- tools: lxc-unfreeze: add default log priority & cleanups
- storage_utils: move duplicated function from tools
- tools: fix lxc-execute command parsing
- lseek - integer overflow
- cmd: lxc-user-nic: change log macro & cleanups
- cmd: lxc-usernsexec reorder includes
- cmd: move declarations to macro.h
- cmd: use utils.{c,h} helpers in lxc-usernsexec
- cmd: simplify lxc-usernsexec
- cmd: use safe number parsers in lxc-usernsexec
- macro: add missing headers
- macro: add macvlan properties
- tools: Indicate container startup failure
- storage: exit() => _exit(). when exec is failed, child process needs to
use _exit()
- tools: lxc-wait: add default log priority & cleanups
- conf: fix path/lxcpath mixups in tty setup
- cmd: use goto for cleanup in lxc-usernsexec
- cmd: Do not reassign variable before it is used
- cmd: Reduce scope of 'count' variable
- cmd: Fix format issues found by clang-format
- list: fix indent
- utils: split into {file,string}_utils.{c,h}
- pam_cgfs: build from the same sources as liblxc
- conf: fix devpts mounting when fully unprivileged
- macro: s/rexit()/_exit()/g
- attach: move struct declaration to top
- macro: move macros from attach.c
- Makefile: don't allow undefined symbols
- autotools: check if compiler is new enough
- log: handle strerror_r() versions
- autotools: add --{disable,enable}-thread-safety
- log: fail build on ENFORCE_THREAD_SAFETY error
- {file,string}_utils: remove NO_LOG
- initutils: remove useless comment
- string_utils: remove unnecessary include
- string_utils: remove unused headers
- string_utils: add remove_trailing_slashes()
- Makefile: remove last pam_cgfs special-casing
- conf: add missing headers
- Fix typo
- ifaddrs: add safe implementation of getifaddrs()
- Makefile: conditionalize ifaddrs.h inclusion
- execute: skip lxc-init logging when unprivileged
- execute: pass /proc/self/fd/
- tests: cleanup get_item.c
- build: fix musl
- configure: reorder header checks
- compiler: add compiler.h header
- commands: return -1 on lxc_cmd_get_init_pid() err
- tests: add basic.c
- tests: cleanup Makefile
- commands: ensure -1 is sent on EPIPE for init pid
- macro: add LXC_AUDS_ADDR_LEN
- macro: move
[Touch-packages] [Bug 1804755] [NEW] SRU of LXC 3.0.3 (upstream bugfix release)
Public bug reported:
LXC upstream released LXC 3.0.3 as a bugfix release with following
changelog:
- CONTRIBUTING: Update reference to kernel coding style
- CONTRIBUTING: Link to latest online kernel docs
- CONTRIBUTING: Direct readers to CODING_STYLE.md
- CODING_STYLE: Mention kernel style in introduction
- CONTRIBUTING: Add 'be' to fix grammar
- CODING_STLYE: Simplify explanation for use of 'extern'
- CODING_STLYE: Remove sections implied by 'kernel style'
- CODING_STYLE: Fix non-uniform heading level
- CODING_STYLE: Update section header format
- cmd: Use parenthesis around complex macro
- cmd: Use 'void' instead of empty parameter list
- cmd: Do not use braces for single statement block
- cmd: Fix whitespace issues
- cmd: Use 'const' for static string constant.
- cmd: Remove unnecessary whitespace in string
- cmd: Put trailing */ on a separate line
- cmd: Remove typo'd semicolon
- cmd: Do not use comparison to NULL
- lxc_init: s/SYSDEBUG()/SYSERROR()/g in remove_self
- tools: lxc-attach: add default log priority & cleanups
- tools: lxc-cgroup: add default log priority & cleanups
- tools: lxc-checkpoint: add default log priority & cleanups
- tools: lxc-console: add default log priority & cleanups
- tools: lxc-create: add default log priority & cleanups
- tools: lxc-destroy: add default log priority & cleanups
- tools: lxc-device: add default log priority & cleanups
- tools: lxc-execute: add default log priority & cleanups
- tools: lxc-start: add default log priority & cleanups
- tools: lxc-stop: add default log priority & cleanups
- tools: lxc-freeze: add default log priority & cleanups
- tools: lxc-unfreeze: add default log priority & cleanups
- storage_utils: move duplicated function from tools
- tools: fix lxc-execute command parsing
- lseek - integer overflow
- cmd: lxc-user-nic: change log macro & cleanups
- cmd: lxc-usernsexec reorder includes
- cmd: move declarations to macro.h
- cmd: use utils.{c,h} helpers in lxc-usernsexec
- cmd: simplify lxc-usernsexec
- cmd: use safe number parsers in lxc-usernsexec
- macro: add missing headers
- macro: add macvlan properties
- tools: Indicate container startup failure
- storage: exit() => _exit(). when exec is failed, child process needs to use
_exit()
- tools: lxc-wait: add default log priority & cleanups
- conf: fix path/lxcpath mixups in tty setup
- cmd: use goto for cleanup in lxc-usernsexec
- cmd: Do not reassign variable before it is used
- cmd: Reduce scope of 'count' variable
- cmd: Fix format issues found by clang-format
- list: fix indent
- utils: split into {file,string}_utils.{c,h}
- pam_cgfs: build from the same sources as liblxc
- conf: fix devpts mounting when fully unprivileged
- macro: s/rexit()/_exit()/g
- attach: move struct declaration to top
- macro: move macros from attach.c
- Makefile: don't allow undefined symbols
- autotools: check if compiler is new enough
- log: handle strerror_r() versions
- autotools: add --{disable,enable}-thread-safety
- log: fail build on ENFORCE_THREAD_SAFETY error
- {file,string}_utils: remove NO_LOG
- initutils: remove useless comment
- string_utils: remove unnecessary include
- string_utils: remove unused headers
- string_utils: add remove_trailing_slashes()
- Makefile: remove last pam_cgfs special-casing
- conf: add missing headers
- Fix typo
- ifaddrs: add safe implementation of getifaddrs()
- Makefile: conditionalize ifaddrs.h inclusion
- execute: skip lxc-init logging when unprivileged
- execute: pass /proc/self/fd/
- tests: cleanup get_item.c
- build: fix musl
- configure: reorder header checks
- compiler: add compiler.h header
- commands: return -1 on lxc_cmd_get_init_pid() err
- tests: add basic.c
- tests: cleanup Makefile
- commands: ensure -1 is sent on EPIPE for init pid
- macro: add LXC_AUDS_ADDR_LEN
- macro: move LXC_CMD_DATA_MAX from commands.h
- macro: add PTR_TO_INT() and INT_TO_PTR()
- macro: add INTTYPE_TO_STRLEN()
- caps: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- cgfsng: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- confile: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- log: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lsm: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- macro: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- lxccontainer: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- monitor: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- network: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- string_utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- utils: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tools: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- conf: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- tests: s/LXC_NUMSTRLEN64/INTTYPE_TO_STRLEN()/
- macro: final INTTYPE_TO_STRLEN() related cleanups
- macro: coding style fixes
- Makefile: correctly add ifaddrs to noinst_HEADERS
- start: remove duplicate macros
- caps: move macros to macro header
- string_utils: use UINT64_MAX macro
- tree-wide: use sizeof on static arrays
- Revert
[Touch-packages] [Bug 1788457] Re: SRU of LXC 3.0.2 (upstream bugfix release)
** Changed in: lxc (Ubuntu Xenial)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1788457
Title:
SRU of LXC 3.0.2 (upstream bugfix release)
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Xenial:
Fix Released
Status in lxc source package in Bionic:
Fix Released
Status in lxc source package in Cosmic:
Fix Released
Bug description:
LXC upstream released LXC 3.0.2 as a bugfix release with following changelog:
- CVE 2018-6556: verify netns fd in lxc-user-nic
- fixed a range of bugs found by Coverity
- lxc-usernsexec: cleanup and bugfixes
- log: add CMD_SYSINFO()
- log: add CMD_SYSERROR()
- state: s/sleep()/nanosleep()/
- lxclock: improve file locking
- lxccontainer: improve file locking
- lxccontainer: fix F_OFD_GETLK checks
- netlink: add __netlink_{send,recv,transaction}
- netns: allocate network namespace id
- MAINTAINERS: add Wolfgang Bumiller
- pam_cgfs: cleanups
- log: add default log priority
- tree-wide: pass unsigned long to prctl()
- macro: add new macro header
- conf: mount devpts without “max” on EINVAL
- tree-wide: handle EINTR in read() and write()
- tree-wide: replace pipe() with pipe2()
- confile: split mount options into flags and data
- conf: improve rootfs setup
- autotools: default to -Wvla -std=gnu11
- tree-wide: remove VLAs
- tree-wide: replace strtok_r() with lxc_iterate_parts()
- utils: add lxc_iterate_parts()
- apparmor: allow start-container to change to lxc-**
- apparmor: update current profiles
- apparmor: Allow /usr/lib* paths for mount and pivot_root
- conf: the atime flags are locked in userns
- conf: handle partially functional device nodes
- conf: create /dev directory
- autotools: build both a shared and static liblxc
- namespace: add api to convert namespaces to standard identifiers
- tree-wide: set MSG_NOSIGNAL
- tree-wide: use mknod() to create dummy files
- cgfsng: respect lxc.cgroup.use
- cgroups: remove is_crucial_cgroup_subsystem()
- tree-wide: remove unneeded log prefixes
- tests: cleanup all tests
- terminal: set FD_CLOEXEC on pty file descriptors
- conf: simplify lxc_setup_dev_console()
- tools: rework tools
- autodev: adapt to changes in Linux 4.18
- log: change DEBUG, INFO, TRACE, NOTICE macro using strerror to SYS*
macro
- log: add lxc_log_strerror_r macro
- network: unpriv lxc will run lxc.net.[i].script.up now
- conf: only use newuidmap and newgidmap when necessary
- autotools: support tls in cross-compile
Just like Ubuntu itself, upstream releases long term support releases,
as is 3.0 and then periodic point releases including all the
accumulated bugfixes.
Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.
This should qualify under the minor upstream bugfix release allowance
of the SRU policy, letting us SRU this without paperwork for every
single change included in this upstream release.
Once the SRU hits -updates, we will be backporting this to xenial-
backports as well, making sure we have the same version everywhere.
[Test case]
lxc has autopkgtests which will assert that the binaries built in -proposed
are functional.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1788457/+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 1804754] [NEW] systemd-timesyncd should fire after network?
Public bug reported: Hi, Should systemd-timesyncd start before network is brought online? | Starting Network Time Synchronization... | Starting Update UTMP about System Boot/Shutdown... | [ OK ] Started Dispatch Password Requests to Console Directory Watch. | [ OK ] Started Set console font and keymap. | [FAILED] Failed to start LSB: AppArmor initialization. | See 'systemctl status apparmor.service' for details. | [ OK ] Started Commit a transient machine-id on disk. | [ OK ] Started Network Time Synchronization. | [ OK ] Found device /dev/ttyS0. | [ OK ] Started Update UTMP about System Boot/Shutdown. | [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. | [ OK ] Reached target System Time Synchronized. | [ OK ] Created slice system-getty.slice. | [ 203.966839] cloud-init[1267]: Cloud-init v. 18.4-0ubuntu1~16.04.2 running 'init-local' at Fri, 23 Nov 2018 04:14:41 +. Up 72.55 seconds. | [ OK ] Started Initial cloud-init job (pre-networking). | [ OK ] Reached target Network (Pre). | Starting Raise network interfaces... | [ OK ] Started Raise network interfaces. | Starting Initial cloud-init job (metadata service crawler)... | [ OK ] Reached target Network. Or should it (systemd-timesyncd.service) have something like the following so it's started after we have networking? | After=network-online.target | Wants=network-online.target On a couple of systems, it seems to take a while booting up (MAAS commissioning) and I'm wondering if it's related to the above. The last logging line is: | [ OK ] Started Network Time Synchronization. | [ OK ] Reached target System Time Synchronized. With a long pause before the rest. I mean, it may or may not be this, but thought I'll file a bug anyways. ** 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/1804754 Title: systemd-timesyncd should fire after network? Status in systemd package in Ubuntu: New Bug description: Hi, Should systemd-timesyncd start before network is brought online? | Starting Network Time Synchronization... | Starting Update UTMP about System Boot/Shutdown... | [ OK ] Started Dispatch Password Requests to Console Directory Watch. | [ OK ] Started Set console font and keymap. | [FAILED] Failed to start LSB: AppArmor initialization. | See 'systemctl status apparmor.service' for details. | [ OK ] Started Commit a transient machine-id on disk. | [ OK ] Started Network Time Synchronization. | [ OK ] Found device /dev/ttyS0. | [ OK ] Started Update UTMP about System Boot/Shutdown. | [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. | [ OK ] Reached target System Time Synchronized. | [ OK ] Created slice system-getty.slice. | [ 203.966839] cloud-init[1267]: Cloud-init v. 18.4-0ubuntu1~16.04.2 running 'init-local' at Fri, 23 Nov 2018 04:14:41 +. Up 72.55 seconds. | [ OK ] Started Initial cloud-init job (pre-networking). | [ OK ] Reached target Network (Pre). | Starting Raise network interfaces... | [ OK ] Started Raise network interfaces. | Starting Initial cloud-init job (metadata service crawler)... | [ OK ] Reached target Network. Or should it (systemd-timesyncd.service) have something like the following so it's started after we have networking? | After=network-online.target | Wants=network-online.target On a couple of systems, it seems to take a while booting up (MAAS commissioning) and I'm wondering if it's related to the above. The last logging line is: | [ OK ] Started Network Time Synchronization. | [ OK ] Reached target System Time Synchronized. With a long pause before the rest. I mean, it may or may not be this, but thought I'll file a bug anyways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804754/+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 338291] Re: cannot set lpd printer with system-config-printer
[Expired for system-config-printer (Ubuntu) because there has been no activity for 60 days.] ** Changed in: system-config-printer (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/338291 Title: cannot set lpd printer with system-config-printer Status in gtk+2.0 package in Ubuntu: Incomplete Status in pygtk package in Ubuntu: Incomplete Status in system-config-printer package in Ubuntu: Expired Bug description: Binary package hint: system-config-printer Im using Ubuntu Jaunty. I have a printer shared with some computers over ethernet using a d-link printserver. To install it on my computer I run system-config-printer, then new -> printer, after this i expand the Network Printer tree and click on LPD/LPR Host or printer. In the right side in "host" box i write the ip of the printserver (192.168.1.240) and in the other box i write the name of the printer I set in the printserver (LASER). Now I should click foward button but... i cannot because the Foward button isn't enabled! Did I make a mistake? If I have to do in other way in my opinion it should be explained better. P.S. the version of system-config-printer is 1.1.3+git20090218-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/338291/+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 1804748] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1804748 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1804748 Title: s390x qemu vt220 terminal, tput cols and lines is wrong Status in linux package in Ubuntu: Incomplete Status in ncurses package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804748/+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 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/
** Changed in: fontconfig (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1590804 Title: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/ Status in Canonical System Image: In Progress Status in fontconfig package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I noticed that a significant amount of time (around 35ms) was spent solely on parsing the XML configuration files in /etc/fonts/conf.d/ There seems to be around 40 files on Ubuntu Phone in that directory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590804/+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 1804748] Re: s390x qemu vt220 terminal, tput cols and lines is wrong
tput reset -> breaks the terminal resizing the qemu window -> fixes things Thus e.g. SIGWINCH is probably handled correctly. However it seems like there is terminal definitions missing or something. ** Tags added: s390x -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1804748 Title: s390x qemu vt220 terminal, tput cols and lines is wrong Status in linux package in Ubuntu: New Status in ncurses package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804748/+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 1804748] [NEW] s390x qemu vt220 terminal, tput cols and lines is wrong
Public bug reported: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2018-11-23 03-31-40.png" https://bugs.launchpad.net/bugs/1804748/+attachment/5215498/+files/Screenshot%20from%202018-11-23%2003-31-40.png ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1804748 Title: s390x qemu vt220 terminal, tput cols and lines is wrong Status in linux package in Ubuntu: New Status in ncurses package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804748/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path
Note that this also appears to affect openntpd in the same fashion, see following for log excerpt of a fresh 18.04 install with the latest openntpd installation: Nov 23 13:27:34 gbjcdc01 kernel: [1542242.548426] audit: type=1400 audit(1542941854.500:97): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5693 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Invalid Status in ntp source package in Zesty: Invalid Status in ntp source package in Artful: Fix Released Status in ntp source package in Bionic: Fix Released Bug description: [Impact] * NTP has new isolation features which makes it trigger apparmor issues. * Those apparmor issues not only clutter the log and make other things less readable, they also prevent ntp from reporting its actual messages. * Fix is opening the apparmor profile to follow ntp through the disconnect by the isolation feature. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Install ntp and check demsg for denies * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Hi Pawel, You may be right, but I think the common thread in all the laptops exhibiting this problem is the ALC294. Does the power save trick mentioned in my comment work for you at all? Cheers, Craig -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1804739] [NEW] libz.a is not compiled with -fPIC
Public bug reported: Ubuntu version: xenial Package: zlib1g-dev Package version: 1:2.2.8.dfsg-2ubuntu4.1 libz.a in this package is not compiled with -fPIC. So it can't be linked into my shared library. ** Affects: zlib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1804739 Title: libz.a is not compiled with -fPIC Status in zlib package in Ubuntu: New Bug description: Ubuntu version: xenial Package: zlib1g-dev Package version: 1:2.2.8.dfsg-2ubuntu4.1 libz.a in this package is not compiled with -fPIC. So it can't be linked into my shared library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1804739/+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 1803743] Re: Sometimes the sound disappears
If you have crash files then please don't attach them to bugs. Instead send them by running: ubuntu-bug *.crash However, I suspect RHVoice is not a standard Ubuntu package so we are unable to handle it here at all. Next time the problem happens, please run this command immediately after the sound disappears: journalctl -b > justafter.txt and attach the file 'justafter.txt' here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803743 Title: Sometimes the sound disappears Status in pulseaudio package in Ubuntu: Incomplete Bug description: Здравствуйте! С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук. Определить по какой причине так и не получилось. Если звук пропадает то помогает только перезагрузка. Обращался на форум, но безрезультатно https://forum.ubuntu.ru/index.php?topic=278602.0 Пару раз переустанавливал Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. Первых два шага не помогают. Проблема остается и звук появляется только при перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю. В третьем шаге предлагается специальный скрипт, который собирает всю необходимую информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей системе в момент когда звук отсутствует http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 Помогите, пожалуйста. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: a 1288 F pulseaudio /dev/snd/controlC0: a 1288 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: H61MLV2 dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/02/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.family: None dmi.product.name: H61MLV2 dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803743/+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 1253693] Re: top status bar missing shutdown button, clock, sound icon and more on upgrade to 13.10
I am new to using Linux. My unit is running on Mint 19 with Gnome 3.28.2 desktop environment. I am experiencing this bug as well; after initial login, icons in top bar are complete but, after I lock the desktop then login again, icons for date, speaker, battery, wifi, and buttons to reboot/shutdown are all missing. I have to execute "alt+F2, r" command for all the icons reappear on the top bar. Any way to permanently fix this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1253693 Title: top status bar missing shutdown button, clock, sound icon and more on upgrade to 13.10 Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-session package in Ubuntu: Confirmed Bug description: This bug has been split from #1239710 as the branch for which changing launcher placement to "all displays" does not work. Every time I login, without fail, the top status bar is missing the gear icon for shutdown, the date, the sound icon and some others. The icons do show from the login window. So if I let the session time out so that the screen locks, I the gear icon appears in the top status bar and works. I have also added a new user to see if the issue has something to do with my account. The new user also has an empty top status bar. The issue happens for both dual monitor and single monitor configurations. When the second monitor is connected, setting launcher placement to "all displays" does not solve the problem. Neither does mirroring the displays. Everything worked just fine with 13.04. The problem appeared immediately following upgrade to 13.10. mark@mark-desktop:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1253693/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Guys please keep this ticket for Zenbook S UX391UA nad ALC294. UX533 is different issue. This not make sense. I've got 3 other Asus laptops, where sound worked perfectly on Linux. Rebooting through Windows 10 or setting card in power_save does not work on UX391UA. I bought external usb-c soundcard and now I am using it with headphones. I think that without support from Realtek (for example Kailang Yang https://www.systutorials.com/linux-kernels/84502/alsa-hda-realtek-new-codecs-support-for-alc234-alc274-alc294-linux-4-4-12/), Kernel Alsa team, Canonical team or Asus there will be no changes. I've tried to contact all of them but without any results. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1804719] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: This is what do I do on my terminal: $ sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils [sudo] password for septian: Reading package lists... Done Building dependency tree Reading state information... Done bridge-utils is already the newest version (1.5-15ubuntu1). ubuntu-vm-builder is already the newest version (0.12.4+bzr494-0ubuntu1). libvirt-bin is already the newest version (4.0.0-1ubuntu8.5). qemu-kvm is already the newest version (1:2.11+dfsg-1ubuntu7.7). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3.5) ... update-initramfs: Generating /boot/initrd.img-4.15.0-39-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 06:47:21 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-11-19 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1804719 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: This is what do I do on my terminal: $ sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils [sudo] password for septian: Reading package lists... Done Building dependency tree Reading state information... Done bridge-utils is already the newest version (1.5-15ubuntu1). ubuntu-vm-builder is already the newest version (0.12.4+bzr494-0ubuntu1). libvirt-bin is already the newest version (4.0.0-1ubuntu8.5). qemu-kvm is already the newest version (1:2.11+dfsg-1ubuntu7.7). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3.5) ... update-initramfs: Generating /boot/initrd.img-4.15.0-39-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 06:47:21 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-11-19 (3 days ago)
[Touch-packages] [Bug 1804719] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1804719 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: New Bug description: This is what do I do on my terminal: $ sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils [sudo] password for septian: Reading package lists... Done Building dependency tree Reading state information... Done bridge-utils is already the newest version (1.5-15ubuntu1). ubuntu-vm-builder is already the newest version (0.12.4+bzr494-0ubuntu1). libvirt-bin is already the newest version (4.0.0-1ubuntu8.5). qemu-kvm is already the newest version (1:2.11+dfsg-1ubuntu7.7). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) Docs: man:lvmetad(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.130ubuntu3.5) ... update-initramfs: Generating /boot/initrd.img-4.15.0-39-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 06:47:21 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-11-19 (3 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1804719/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1742852 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1784485, as I'm seeing the same symptoms, with the same temporary improvement enabling the power save as described above. Asus UX533 Kubuntu 18.10 (4.18.0-11-generic) fresh install (dual boot with Windows 10). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
** Also affects: fonts-ubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: New Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in fonts-ubuntu package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 1561278] Re: internal sound card not detected HP X2
Thanks for the tip, but I use the machine mainly at home and would find internal speakers much more convenient. On a different thread, there's talk of downloading UCM files to fix this (specifically UCM- master/bytcr5645 and chtrt5645), but no details of where from. Perhaps it's obvious to Ubuntu pros, but not to me. Any idea? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1574534] Re: Aspect ratio of Ubuntu Mono font at small sizes changed
** Package changed: ubuntu-font-family-sources (Ubuntu) => fonts-ubuntu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1574534 Title: Aspect ratio of Ubuntu Mono font at small sizes changed Status in fonts-ubuntu package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu MATE 15.10 to 16.04 I notice that the Ubuntu Mono font is considerably wider at 11pt than it was before. In fact, character widths at 11pt are the same as at 12pt, which can be easily verified in the following way: * Use a regular density (~100 dpi) display * Open MATE Terminal * Edit the current profile, selecting Ubuntu Mono 12 as the font, and apply changes. * Edit the profile again, changing the font size to 11. Apply changes and observe how the window resizes: it will shrink in height but maintain the same width. This is undesirable for a number of reasons: * Stability: drastically altering font may cause all kinds of display issues (and use cases for monospaced fonts are likely to be even more vulnerable to this) * Screen real estate: text at 11pt now takes up considerably more size (width is the same as it is at 12pt) * Aesthetics: 11pt test looks unnaturally stretched out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/1574534/+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 1561278] Re: internal sound card not detected HP X2
For what it's worth: An easy solution for audio is a bluetooth headset. Works great under 18.04. I'd also like to get the main speakers working, but I suspect the passengers next to me on the plane are happier with the headset-only arrangement. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers
@seb128 Ok, let's sync tomorrow. I thought we already took parts of these patches in =/ -- 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/1799364 Title: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * All Dell Latitude and Precision computer users can not use the wlan/bt hotkey. [Test Case] * Use any Dell Latitude and Precision computer to check the wlan/bt hotkey. * If you don't have the computer above, you can use the following command to check, and the expected output is "KEYBOARD_KEY_88=!wlan" instead of "KEYBOARD_KEY_88=!". `systemd-hwdb query evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: | grep KEYBOARD_KEY_88` [Regression Potential] * No regression [Other Info] * None Just install the official Ubuntu 18.10 on any Dell Latitude or Precision computer and press wlan/bt hotkey on the keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 15:37:41 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.0.24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1804663] Re: audio of web is off
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1804663 Title: audio of web is off Status in pulseaudio package in Ubuntu: Invalid Bug description: i don't hear anything from web ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 22 15:11:04 2018 DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] [174b:7162] InstallationDate: Installed on 2016-08-05 (838 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3840 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3840 dmi.product.version: P01-B1 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 31 16:50:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1804663/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers
the patch created issues (see the comments on bug #1740894 and https://github.com/systemd/systemd/issues/10704) and was reverted upstream in https://github.com/systemd/systemd/pull/10709 , please don't backport that change to older series but rather the revert/more recent upstream changes ** Bug watch added: github.com/systemd/systemd/issues #10704 https://github.com/systemd/systemd/issues/10704 -- 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/1799364 Title: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * All Dell Latitude and Precision computer users can not use the wlan/bt hotkey. [Test Case] * Use any Dell Latitude and Precision computer to check the wlan/bt hotkey. * If you don't have the computer above, you can use the following command to check, and the expected output is "KEYBOARD_KEY_88=!wlan" instead of "KEYBOARD_KEY_88=!". `systemd-hwdb query evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: | grep KEYBOARD_KEY_88` [Regression Potential] * No regression [Other Info] * None Just install the official Ubuntu 18.10 on any Dell Latitude or Precision computer and press wlan/bt hotkey on the keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 15:37:41 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.0.24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
identical for me. My problem reporting has not been disabled: $ cat /etc/default/apport # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=1 -- 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/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Interestingly, if I put the sound device into power save mode and wait a few seconds before playing a sound, I can actually hear it perffectly clearly, but after repeating the playing of the sound a few times, it distorts then disappears: sudo -i echo 10 >/sys/module/snd_hda_intel/parameters/power_save sleep 10 aplay /usr/share/sounds/alsa/Front_Center.wav -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1758994] Re: "There was an error playing video from the webcam"
Hi, I was wondering as to when the fix will be included in Ubuntu 18.04.1 LTS? The fix has been out since July but users of Ubuntu 18.04 LTS haven't received the updated packages with the fix yet. It is still 1.14.1 for gst-plugins-good1.0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1758994 Title: "There was an error playing video from the webcam" Status in cheese package in Ubuntu: Confirmed Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Bug description: Chesee version: 3.28 Ubuntu version: 18.04 (26.03.18 updated) when i open cheese, cheese shows "There was an error playing video from the webcam" Crashlog: UNPC:~$ cheese (cheese:2): Gtk-WARNING **: 21:07:11.856: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version (cheese:2): cheese-WARNING **: 21:07:12.958: Device '/dev/video0' failed during initialization: gstv4l2object.c(3695): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for YUYV @ 1280x720: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1758994/+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 1803849] Re: libgl1-mesa-dri:i386 can not be installed
I was able to install 'steam-latest.deb' from Valve on a chroot without issues, and then ran 'steam' which installed all the i386 bits, again without any issues. If you have problems with the upgrade, try asking for help on a forum or IRC. There's nothing to be fixed in the Ubuntu archive anyway, so closing again. ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1803849 Title: libgl1-mesa-dri:i386 can not be installed Status in mesa package in Ubuntu: Invalid Bug description: Steam client tries to install a set of i386 libraries. One of them is libgl1-mesa-dri:i386. But since upgrade to Ubuntu 18.10 this package got broken dependency and thus installation fails. >The following packages have unmet dependencies: > libgl1-mesa-dri:i386 : Depends: libllvm7:i386 (>= 1:7~svn298832-1~) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgl1-mesa-dri:i386 (not installed) Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 09:54:04 2018 DistUpgraded: 2018-10-19 13:34:56,068 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: exfat, 1.2.10, 4.18.0-11-generic, x86_64: installed exfat, 1.2.10, 4.18.0-12-generic, x86_64: installed exfat, 1.2.10, 4.19.1-041901-generic, x86_64: installed exfat, 1.2.10, 4.19.2-041902-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2018-03-27 (235 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.2-041902-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 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/mesa/+bug/1803849/+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 1724307] Re: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V
I have the same issue on Ubuntu 18.04.1 LTS (kernel 4.15.0-38-generic) connected with DisplayLink (driver 4.4.24). I'm connecting through Display port on a Dell Inspiron 15, and a docker D6000. The flicker occurs only on the laptop's monitor, and the external monitors seem fine. No flicker whatsoever. As similar reports, when the docker is disconnected the flicker stops. -- 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/1724307 Title: [Dell XPS 13 9360] Mouse cursor flickers with one external monitor connected via HDMI+Wavlink WL-UG39DK1V Status in xorg package in Ubuntu: Triaged Bug description: When I connect my laptop to my DisplayLink based device with USB (Wavlink universal USB 3.0 docking station https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers as per the following video: https://launchpadlibrarian.net/346625588/20171121_131417.mp4 Only if the mouse is on the laptop monitor, it can vanish for several minutes, but remains active. Animations/overlays or typing inside a Chrome window causes the mouse pointer to flicker more often. If there is no interaction or animation, the mouse pointer remains static and drawn. Monitor 1: 1920 x 1080 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor This issue doesn't happen if I don't connect my laptop to an external monitor via the Wavlink device. This issue is reproducible with DisplayLink driver 1.4, and 1.3.54. This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64. I've reported this to DisplayLink via: https://displaylink.org/forum/showthread.php?p=84713#post84713 WORKAROUND: Use GNOME Flashback (Metacity) session. WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary monitor change Rotation from Normal to any of the following: Clockwise Anti-clockwise 180 degrees ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 17 10:01:55 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:082a] InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.1 dmi.board.name: 05FPM2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Oct 17 09:39:15 2017 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5193 vendor SHP xserver.version: 2:1.19.3-1ubuntu1~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode
17.10 isn't affected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1804568 Title: click position is flipped to cursor position when in tent mode Status in coreutils package in Ubuntu: New Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1804568/+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 1804568] Re: click position is flipped to cursor position when in tent mode
further explanation: https://youtu.be/ZI_qteOiB0I (250MB, 2:20) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1804568 Title: click position is flipped to cursor position when in tent mode Status in coreutils package in Ubuntu: New Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1804568/+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 1734106] Re: virtualbox crash after update 4.13.0-18 version
** Attachment added: "crash after update on ubuntu 18.10"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1734106/+attachment/5215372/+files/IMG_20181122_124810_DRO.jpg
--
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/1734106
Title:
virtualbox crash after update 4.13.0-18 version
Status in apport package in Ubuntu:
New
Bug description:
An update to day : 4.13.0-18
virtualbox don't start prg
Échec de l'ouverture de session pour la machine virtuelle Android 7.1.
The virtual machine 'Android 7.1' has terminated unexpectedly during
startup with exit code 1 (0x1).
Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : MachineWrap
Interface : IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Good works on 4.13.0-17 version !
I had same problem with update from 4.13.0-16 to 4.13.0-17
It seems to be a problem with kernel
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
support driver is not installed. On linux, open returned ENOENT.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1734106/+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 1734106] Re: virtualbox crash after update 4.13.0-18 version
Ubuntu crashes after update on nov 22 <<< On 4 18.0 12
impossible to restart //
can open on recovery ;ode <<< 1st part and thenm crashs see picture on
--
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/1734106
Title:
virtualbox crash after update 4.13.0-18 version
Status in apport package in Ubuntu:
New
Bug description:
An update to day : 4.13.0-18
virtualbox don't start prg
Échec de l'ouverture de session pour la machine virtuelle Android 7.1.
The virtual machine 'Android 7.1' has terminated unexpectedly during
startup with exit code 1 (0x1).
Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : MachineWrap
Interface : IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Good works on 4.13.0-17 version !
I had same problem with update from 4.13.0-16 to 4.13.0-17
It seems to be a problem with kernel
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
support driver is not installed. On linux, open returned ENOENT.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1734106/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
I have a similar problem after update from 229-4ubuntu21.2 to 229-4ubuntu21.9 in arm version. lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 apt-cache policy systemd systemd: Installed: 229-4ubuntu21.2 Candidate: 229-4ubuntu21.9 Version table: 229-4ubuntu21.9 500 500 http://ports.ubuntu.com xenial-security/main armhf Packages 500 http://ports.ubuntu.com xenial-updates/main armhf Packages *** 229-4ubuntu21.2 100 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://ports.ubuntu.com xenial/main armhf Packages -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Confirmed Bug description: After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers
In disco-proposed systemd (239-7ubuntu11) disco; urgency=medium * hwdb: Fix wlan keycode for all Dell Latitude and Precision systems (LP: #1799364) Author: Shih-Yuan Lee (FourDollars) File: debian/patches/hwdb-Fix-wlan-keycode-for-all-Dell-Latitude-and-Precision.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8ac9a5640be39ede9cebcd8c4cc44e8811e0e49 * hwdb: Update PNP IDs of Goldstar (now: LG Electronics) (LP: #1804584) File: debian/patches/hwdb-Update-PNP-IDs-of-Goldstar-now-LG-Electronics-.-1005.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=10204fb5761c759be6ddf27dc43c851ef24c96cb * btrfs-util: unbreak tmpfiles' subvol creation File: debian/patches/btrfs-util-unbreak-tmpfiles-subvol-creation.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4ab5b8275a0487e301553fb6de6a905abb7ea833 -- Dimitri John Ledkov Thu, 22 Nov 2018 16:30:28 + -- 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/1799364 Title: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * All Dell Latitude and Precision computer users can not use the wlan/bt hotkey. [Test Case] * Use any Dell Latitude and Precision computer to check the wlan/bt hotkey. * If you don't have the computer above, you can use the following command to check, and the expected output is "KEYBOARD_KEY_88=!wlan" instead of "KEYBOARD_KEY_88=!". `systemd-hwdb query evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: | grep KEYBOARD_KEY_88` [Regression Potential] * No regression [Other Info] * None Just install the official Ubuntu 18.10 on any Dell Latitude or Precision computer and press wlan/bt hotkey on the keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 15:37:41 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.0.24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1804584] Re: LG screen reported as being a Goldstar one
In disco-proposed systemd (239-7ubuntu11) disco; urgency=medium * hwdb: Fix wlan keycode for all Dell Latitude and Precision systems (LP: #1799364) Author: Shih-Yuan Lee (FourDollars) File: debian/patches/hwdb-Fix-wlan-keycode-for-all-Dell-Latitude-and-Precision.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8ac9a5640be39ede9cebcd8c4cc44e8811e0e49 * hwdb: Update PNP IDs of Goldstar (now: LG Electronics) (LP: #1804584) File: debian/patches/hwdb-Update-PNP-IDs-of-Goldstar-now-LG-Electronics-.-1005.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=10204fb5761c759be6ddf27dc43c851ef24c96cb * btrfs-util: unbreak tmpfiles' subvol creation File: debian/patches/btrfs-util-unbreak-tmpfiles-subvol-creation.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4ab5b8275a0487e301553fb6de6a905abb7ea833 -- Dimitri John Ledkov Thu, 22 Nov 2018 16:30:28 + -- 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/1804584 Title: LG screen reported as being a Goldstar one Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Fix Committed Bug description: * Impact The GNOME configuration interface labels LG screens as being from Goldstar, that's because the hwdb has an outdate record for the brand and still its old name, that has been fixed upstream now with https://github.com/systemd/systemd/commit/c6d7a5e9 * Test case - connect to a LG screen - log into an Ubuntu/GNOME session - open gnome-control-center display section -> the screen should be described as from LG and not from Goldstar * Regression potential It's just a name change in the hwdb data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804584/+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 1778936] Re: please re-add Support-system-image-read-only-etc.patch
@mvo Security wants to trump this again... Can you please validate this? I'm not sure how to boot a core18 system. -- 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1804663] Re: audio of web is off
now i find out it is right excuse me Il giorno gio 22 nov 2018 alle ore 15:50 Sebastien Bacher ha scritto: > what do you call "web"? what web browser do you use? do you have sound > in other places? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1804663 > > Title: > audio of web is off > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > i don't hear anything from web > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 > Uname: Linux 4.15.0-39-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > Date: Thu Nov 22 15:11:04 2018 > DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, > re-reading > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if > 00 [VGA controller]) > Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT > 530] [174b:7162] > InstallationDate: Installed on 2016-08-05 (838 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: Packard Bell imedia S3840 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic > root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago) > dmi.bios.date: 07/08/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: P01-B1 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: imedia S3840 > dmi.board.vendor: Packard Bell > dmi.chassis.type: 3 > dmi.chassis.vendor: Packard Bell > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: > dmi.product.family: Packard Bell Desktop > dmi.product.name: imedia S3840 > dmi.product.version: P01-B1 > dmi.sys.vendor: Packard Bell > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.91-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > xserver.bootTime: Fri Aug 31 16:50:45 2018 > xserver.configfile: default > xserver.devices: >inputPower Button KEYBOARD, id 6 >inputPower Button KEYBOARD, id 7 >inputAT Translated Set 2 keyboard KEYBOARD, id 8 >inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 > xserver.errors: >Failed to load module "nvidia" (module does not exist, 0) >Failed to load module "nvidia" (module does not exist, 0) > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.4-0ubuntu0.8 > xserver.video_driver: nouveau > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1804663/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1804663 Title: audio of web is off Status in pulseaudio package in Ubuntu: Incomplete Bug description: i don't hear anything from web ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 22 15:11:04 2018 DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] [174b:7162] InstallationDate: Installed on 2016-08-05 (838 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia
[Touch-packages] [Bug 1798073] Re: [SRU] Provide 2018 archive signing key on stable releases
This upload lists autopkgtest regressions for all arches for pbuilder - could you take a look if those are unrelated or not? Looks fishy, since some of those were passing fine just recently for other packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1798073 Title: [SRU] Provide 2018 archive signing key on stable releases Status in ubuntu-keyring package in Ubuntu: Fix Released Status in ubuntu-keyring source package in Bionic: Fix Committed Bug description: [Impact] * For LTS releases to be able to bootstrap dual and single signed future releases, and validate all signatures, 2018 archive signing key should be SRUed back * Also build process has improved documentation and vague validation that all key snippets are signed correctly [Test Case] * $ apt-key list ... /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg -- pub rsa4096 2018-09-17 [SC] F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C uid [ unknown] Ubuntu Archive Automatic Signing Key (2018) ... apt-key list should contain the 2018 archive key. [Regression Potential] * Build-process, key algo, and key size, and file format are the same as previous key snippets thus supported by all of gpg1 gpg2 gpgv1 gpgv2. [Other Info] * 2018 key is to be used for dual-signing in DD series and up * Bileto PPA is built against security pocket only, suitable to be released into both -security and -updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1798073/+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 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.service: Transaction is destructive. See system logs and 'systemctl status systemd-networkd.service' for details. Failed to try-restart
[Touch-packages] [Bug 1804584] Re: LG screen reported as being a Goldstar one
** Changed in: systemd (Ubuntu Disco) Status: Triaged => Fix Committed -- 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/1804584 Title: LG screen reported as being a Goldstar one Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Fix Committed Bug description: * Impact The GNOME configuration interface labels LG screens as being from Goldstar, that's because the hwdb has an outdate record for the brand and still its old name, that has been fixed upstream now with https://github.com/systemd/systemd/commit/c6d7a5e9 * Test case - connect to a LG screen - log into an Ubuntu/GNOME session - open gnome-control-center display section -> the screen should be described as from LG and not from Goldstar * Regression potential It's just a name change in the hwdb data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804584/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers
** Changed in: systemd (Ubuntu Disco) Status: New => Fix Committed -- 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/1799364 Title: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Fix Committed Bug description: [Impact] * All Dell Latitude and Precision computer users can not use the wlan/bt hotkey. [Test Case] * Use any Dell Latitude and Precision computer to check the wlan/bt hotkey. * If you don't have the computer above, you can use the following command to check, and the expected output is "KEYBOARD_KEY_88=!wlan" instead of "KEYBOARD_KEY_88=!". `systemd-hwdb query evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: | grep KEYBOARD_KEY_88` [Regression Potential] * No regression [Other Info] * None Just install the official Ubuntu 18.10 on any Dell Latitude or Precision computer and press wlan/bt hotkey on the keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 15:37:41 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.0.24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1778767] Re: iPhone doesn't charge when plugged in after disconnect
Thanks Leo for the patch, looking at the upstream git log there were some other follow up fixes to the udev rules, I included those as well and uploaded as a SRU to bionic now ** Description changed: - Plugging in the iPhone via usb will charge the iPhone after reboot, but - after disconnect usbmuxd's systemctl service is inactive and does not - start. + * Impact + the usbmuxd service is not restarted after disconnecting/reconnecting a device, which means users need to reboot (or use the command line to activate the service) to have their iphone handled a second time in a session + + * Test case + - open an Ubuntu/GNOME session and connect an iphone + - disconnect the device + - connect it again + + -> it should be handled the second time like it was the first time + + * Regression potential + The changes are in the udev rule, just make sure that idevices are correctly detected when connected + + + + + + Plugging in the iPhone via usb will charge the iPhone after reboot, but after disconnect usbmuxd's systemctl service is inactive and does not start. Problem and workaround documented here: https://ubuntuforums.org/showthread.php?t=2376741=13779062#post13779062 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1778767 Title: iPhone doesn't charge when plugged in after disconnect Status in usbmuxd package in Ubuntu: Fix Released Status in usbmuxd source package in Bionic: Fix Committed Status in usbmuxd package in Debian: New Bug description: * Impact the usbmuxd service is not restarted after disconnecting/reconnecting a device, which means users need to reboot (or use the command line to activate the service) to have their iphone handled a second time in a session * Test case - open an Ubuntu/GNOME session and connect an iphone - disconnect the device - connect it again -> it should be handled the second time like it was the first time * Regression potential The changes are in the udev rule, just make sure that idevices are correctly detected when connected Plugging in the iPhone via usb will charge the iPhone after reboot, but after disconnect usbmuxd's systemctl service is inactive and does not start. Problem and workaround documented here: https://ubuntuforums.org/showthread.php?t=2376741=13779062#post13779062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+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 1778767] Re: iPhone doesn't charge when plugged in after disconnect
The issue was fixed in cosmic ** Changed in: usbmuxd (Ubuntu) Importance: Undecided => High ** Changed in: usbmuxd (Ubuntu) Status: Confirmed => Fix Released ** Also affects: usbmuxd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: usbmuxd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: usbmuxd (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1778767 Title: iPhone doesn't charge when plugged in after disconnect Status in usbmuxd package in Ubuntu: Fix Released Status in usbmuxd source package in Bionic: Fix Committed Status in usbmuxd package in Debian: New Bug description: * Impact the usbmuxd service is not restarted after disconnecting/reconnecting a device, which means users need to reboot (or use the command line to activate the service) to have their iphone handled a second time in a session * Test case - open an Ubuntu/GNOME session and connect an iphone - disconnect the device - connect it again -> it should be handled the second time like it was the first time * Regression potential The changes are in the udev rule, just make sure that idevices are correctly detected when connected Plugging in the iPhone via usb will charge the iPhone after reboot, but after disconnect usbmuxd's systemctl service is inactive and does not start. Problem and workaround documented here: https://ubuntuforums.org/showthread.php?t=2376741=13779062#post13779062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+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 1799287] Re: usbmud service will not load on boot
Thank you for your bug report. What iphone model do you have? The service should start when you connect your device, can you boot, log in add, connect the device and add your journalctl log then? ** Changed in: usbmuxd (Ubuntu) Importance: Undecided => Low ** Changed in: usbmuxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1799287 Title: usbmud service will not load on boot Status in usbmuxd package in Ubuntu: Incomplete Bug description: I use usbmux for my iphone so I can access my photos via shotwell and move files around. I have to start the service manually via systemd. When I try to enable I get the following. hhernandez@hhernandez-Precision-M4800:~$ sudo systemctl enable usbmuxd [sudo] password for hhernandez: The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: usbmuxd 1.1.0-2build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Mon Oct 22 13:04:24 2018 SourcePackage: usbmuxd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1799287/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Confirmed Bug description: After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache
** Changed in: alembic (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1794229 Title: python packages should not ship colliding /usr/lib/python3/dist- packages/.pytest_cache Status in alembic package in Ubuntu: Fix Committed Status in astroid package in Ubuntu: Invalid Status in dh-python package in Ubuntu: New Status in Debian: Fix Released Status in alembic package in Debian: Fix Released Bug description: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alembic/+bug/1794229/+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 1804663] Re: audio of web is off
what do you call "web"? what web browser do you use? do you have sound in other places? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1804663 Title: audio of web is off Status in pulseaudio package in Ubuntu: Incomplete Bug description: i don't hear anything from web ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 22 15:11:04 2018 DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] [174b:7162] InstallationDate: Installed on 2016-08-05 (838 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3840 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3840 dmi.product.version: P01-B1 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 31 16:50:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1804663/+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 1804663] Re: audio of web is off
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => pulseaudio (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/1804663 Title: audio of web is off Status in pulseaudio package in Ubuntu: Incomplete Bug description: i don't hear anything from web ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 22 15:11:04 2018 DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] [174b:7162] InstallationDate: Installed on 2016-08-05 (838 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3840 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3840 dmi.product.version: P01-B1 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 31 16:50:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1804663/+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 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
please test new xserver from https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging only for cosmic at this point ** Changed in: xorg-server (Ubuntu Disco) Status: Confirmed => Incomplete -- 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/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Status in mesa source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in mesa source package in Disco: Confirmed Status in xorg-server source package in Disco: Incomplete Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
[Touch-packages] [Bug 1804663] [NEW] audio of web is off
Public bug reported: i don't hear anything from web ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 22 15:11:04 2018 DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] [174b:7162] InstallationDate: Installed on 2016-08-05 (838 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3840 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name: imedia S3840 dmi.product.version: P01-B1 dmi.sys.vendor: Packard Bell version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 31 16:50:45 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1804663 Title: audio of web is off Status in xorg package in Ubuntu: New Bug description: i don't hear anything from web ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 22 15:11:04 2018 DistUpgraded: 2018-08-31 19:36:01,573 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 530] [174b:7162] InstallationDate: Installed on 2016-08-05 (838 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Packard Bell imedia S3840 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=562bbd01-6a42-4bcd-b109-080f909cc9ae ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-31 (82 days ago) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-B1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: imedia S3840 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd07/08/2011:svnPackardBell:pnimediaS3840:pvrP01-B1:rvnPackardBell:rnimediaS3840:rvr:cvnPackardBell:ct3:cvr: dmi.product.family: Packard Bell Desktop dmi.product.name:
[Touch-packages] [Bug 1804584] Re: LG screen reported as being a Goldstar one
** Also affects: systemd (Ubuntu Disco) Importance: Low Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) 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/1804584 Title: LG screen reported as being a Goldstar one Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: Triaged Bug description: * Impact The GNOME configuration interface labels LG screens as being from Goldstar, that's because the hwdb has an outdate record for the brand and still its old name, that has been fixed upstream now with https://github.com/systemd/systemd/commit/c6d7a5e9 * Test case - connect to a LG screen - log into an Ubuntu/GNOME session - open gnome-control-center display section -> the screen should be described as from LG and not from Goldstar * Regression potential It's just a name change in the hwdb data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804584/+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 1778767] Re: iPhone doesn't charge when plugged in after disconnect
This patch solves the issue by backporting the udev rule from usbmuxd-1.1.1~git20180428.b95a0a0-1 (cosmic) This is a debdiff for Bionic applicable to 1.1.0-2build1. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended. ** Patch added: "1-1.1.0-2build2.debdiff" https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+attachment/5215269/+files/1-1.1.0-2build2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1778767 Title: iPhone doesn't charge when plugged in after disconnect Status in usbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Debian: New Bug description: Plugging in the iPhone via usb will charge the iPhone after reboot, but after disconnect usbmuxd's systemctl service is inactive and does not start. Problem and workaround documented here: https://ubuntuforums.org/showthread.php?t=2376741=13779062#post13779062 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1778767/+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 1804648] Re: host utility doesn't support switch -U (force UDP)
** Package changed: iputils (Ubuntu) => bind9 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1804648 Title: host utility doesn't support switch -U (force UDP) Status in bind9 package in Ubuntu: New Bug description: Ubuntu 18.04.1 man page for host utility (man host) has information, that "-U" switch forces UDP mode. But there is no "-U" switch coded in host utility. Is it a bug in manpage or in host utility? # host -V host 9.11.3-1ubuntu1.3-Ubuntu # host -T www.ubuntu.com www.ubuntu.com has address 91.189.89.103 # host -U www.ubuntu.com Usage: host [-aCdilrTvVw] [-c class] [-N ndots] [-t type] [-W time] [-R number] [-m flag] hostname [server] -a is equivalent to -v -t ANY Information in manpage (man host): -T, -U TCP/UDP: By default, host uses UDP when making queries. The -T option makes it use a TCP connection when querying the name server. TCP will be automatically selected for queries that require it, such as zone transfer (AXFR) requests. Type ANY queries default to TCP but can be forced to UDP initially using -U. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1804648/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Same problem, no external monitor via HDMI detected: Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1920x1080 60.03*+ 60.0159.9759.9659.9348.03 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) DP-1-3 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540
[Touch-packages] [Bug 1804648] [NEW] host utility doesn't support switch -U (force UDP)
Public bug reported: Ubuntu 18.04.1 man page for host utility (man host) has information, that "-U" switch forces UDP mode. But there is no "-U" switch coded in host utility. Is it a bug in manpage or in host utility? # host -V host 9.11.3-1ubuntu1.3-Ubuntu # host -T www.ubuntu.com www.ubuntu.com has address 91.189.89.103 # host -U www.ubuntu.com Usage: host [-aCdilrTvVw] [-c class] [-N ndots] [-t type] [-W time] [-R number] [-m flag] hostname [server] -a is equivalent to -v -t ANY Information in manpage (man host): -T, -U TCP/UDP: By default, host uses UDP when making queries. The -T option makes it use a TCP connection when querying the name server. TCP will be automatically selected for queries that require it, such as zone transfer (AXFR) requests. Type ANY queries default to TCP but can be forced to UDP initially using -U. ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1804648 Title: host utility doesn't support switch -U (force UDP) Status in iputils package in Ubuntu: New Bug description: Ubuntu 18.04.1 man page for host utility (man host) has information, that "-U" switch forces UDP mode. But there is no "-U" switch coded in host utility. Is it a bug in manpage or in host utility? # host -V host 9.11.3-1ubuntu1.3-Ubuntu # host -T www.ubuntu.com www.ubuntu.com has address 91.189.89.103 # host -U www.ubuntu.com Usage: host [-aCdilrTvVw] [-c class] [-N ndots] [-t type] [-W time] [-R number] [-m flag] hostname [server] -a is equivalent to -v -t ANY Information in manpage (man host): -T, -U TCP/UDP: By default, host uses UDP when making queries. The -T option makes it use a TCP connection when querying the name server. TCP will be automatically selected for queries that require it, such as zone transfer (AXFR) requests. Type ANY queries default to TCP but can be forced to UDP initially using -U. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1804648/+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 1318975] Re: /usr/bin/host utility cannot change port for DNS querires
the host command is from the bind9 package not from iputils right? ** Package changed: iputils (Ubuntu) => bind9 (Ubuntu) ** Changed in: bind9 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1318975 Title: /usr/bin/host utility cannot change port for DNS querires Status in bind9 package in Ubuntu: Confirmed Bug description: This is not a bug report. It is request for missing feature... /usr/bin/host utility to check DNS is limited to send DNS queries to port 53. There is no option to change port for DNS queries. Other utilities, like dig, can change port. I can change DNS server but port is always 53. I found this missing feature while I was troubleshooting my DNS. My ISP is hijacking port 53 and I found I cannot use host utility to diagnose this problem... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1318975/+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 1804624] Re: Rhythmbox freezes after playing a Amiga mod file
thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1804624 Title: Rhythmbox freezes after playing a Amiga mod file Status in gstreamer1.0 package in Ubuntu: New Bug description: Easy to reproduce: 1. Get a Amiga .mod file (any will do). 2. Add it to rhythmbox play queue 3. Play it 4. After playing rhythmbox GUI freezes and needs to be killed. The bug may be as well in gstreamer plugin responsible for mods but this is how it appears for end users. Tested on up to date Ubuntu 18.04.1 LTS and rhythmbox 3.4.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 22 11:25:48 2018 InstallationDate: Installed on 2018-11-20 (1 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1804624/+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 1318975] Re: /usr/bin/host utility cannot change port for DNS querires
This issue was created in 2014. I just verified that "host" in Ubuntu 18.04.1 still uses hard-coded port 53; there was no progress during last 4 years. It looks like an easy change. Some hints for an easy test. OpenDNS runs DNS server listening at port 53, 443 and 5353. # host resolver1.opendns.com resolver1.opendns.com has address 208.67.222.222 resolver1.opendns.com has IPv6 address 2620:119:35::35 All these commmands work (test at port 53, 443 and 5353): # nslookup -po=53 www.ubuntu.com 208.67.222.222 # nslookup -po=443 www.ubuntu.com 208.67.222.222 # nslookup -po=5353 www.ubuntu.com 208.67.222.222 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1318975 Title: /usr/bin/host utility cannot change port for DNS querires Status in bind9 package in Ubuntu: Confirmed Bug description: This is not a bug report. It is request for missing feature... /usr/bin/host utility to check DNS is limited to send DNS queries to port 53. There is no option to change port for DNS queries. Other utilities, like dig, can change port. I can change DNS server but port is always 53. I found this missing feature while I was troubleshooting my DNS. My ISP is hijacking port 53 and I found I cannot use host utility to diagnose this problem... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1318975/+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 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
from my /var/log/boot.log [FAILED] Failed to start Process error reports when automatic reporting is enabled. See 'systemctl status apport-autoreport.service' for details. Shows up twice in the log. When I run: systemctl status apport-autoreport.service ● apport-autoreport.service - Process error reports when automatic reporting is enabled Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static; vendor preset: enabled) Active: inactive (dead) since Thu 2018-11-22 12:14:37 GMT; 29s ago Process: 12896 ExecStart=/usr/share/apport/whoopsie-upload-all (code=exited, status=0/SUCCESS) Main PID: 12896 (code=exited, status=0/SUCCESS) Nov 22 12:14:37 cerebus systemd[1]: Starting Process error reports when automatic reporting is enabled... Nov 22 12:14:37 cerebus whoopsie-upload-all[12896]: /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash already marked for u Nov 22 12:14:37 cerebus whoopsie-upload-all[12896]: All reports processed Nov 22 12:14:37 cerebus systemd[1]: Started Process error reports when automatic reporting is enabled. -- 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/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. Status in apport package in Ubuntu: Incomplete Bug description: Hello, Attached image. Regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1803706] Re: long application menus overflowing when screen too small
** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- 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/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: Won't Fix Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: Invalid Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+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 1803706] Re: long application menus overflowing when screen too small
** Changed in: df-libreoffice Status: New => Won't Fix -- 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/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: Won't Fix Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+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 1803706]
This behavior is from GTK+ (so NOTOURBUG), but good luck trying to convince GNOME it’s a bug; they’re notoriously stubborn. -- 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/1803706 Title: long application menus overflowing when screen too small Status in LibreOffice: Won't Fix Status in gtk+3.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Hi I am not a developer, only a user. In 18.10 Cosmic with new Yaru theme: any application with long menus are overflowing and covering the menubar making impossible to slide mouse to the next menu. It affects long sub-menus too. It mainly affects LibreOffice as it has got quite large menus but it is also present in CherryTree app and I guess in any other. When the menu is not wider than the available vertical area of the screen than they show up nicely aligned under the menu toolbar but when it is too large: it might even run edge to edge vertically. (As for Design: probably a slightly different colour at the end of these long menus would make them more visible where the arrows are.) Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803706/+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 1579451] Re: Network manager doesn't ask for password in new connections
I just find out, that this bug is related to another bug: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825 This problem with wifi password is just another one of many, all probably connected to the gnome-keyring. After calling ```gnome-keyring-daemon &``` after login, problem is not present any more. -- 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/1579451 Title: Network manager doesn't ask for password in new connections Status in network-manager package in Ubuntu: Confirmed Bug description: When trying to connect to a new WPA-PSK encrypted network, I click in the wireless icon and select the network I want to connect. Then the wireless icon suffers a glitch, I'm not prompted a password, and I'm informed that I'm offline. There's the first time in 2 or 3 months that I tried to connect to a new network. Despite this, in /etc/NetworkManager/system-connections/ there is the file matching the network I tried to connect, without a psk=... item on it. Then I edited it, put the password and could connect to the network like if I was already connected to it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 7 21:30:11 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-05 (92 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.2.1 dev wlan0 proto static 192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.6 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579451/+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 1804624] Re: Rhythmbox freezes after playing a Amiga mod file
Attached a example mod file for testing. Mods are generally public domain so no copyright infringement should happen. ** Attachment added: "Example mod file" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1804624/+attachment/5215272/+files/3ddemoii_159.mod -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1804624 Title: Rhythmbox freezes after playing a Amiga mod file Status in gstreamer1.0 package in Ubuntu: New Bug description: Easy to reproduce: 1. Get a Amiga .mod file (any will do). 2. Add it to rhythmbox play queue 3. Play it 4. After playing rhythmbox GUI freezes and needs to be killed. The bug may be as well in gstreamer plugin responsible for mods but this is how it appears for end users. Tested on up to date Ubuntu 18.04.1 LTS and rhythmbox 3.4.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 22 11:25:48 2018 InstallationDate: Installed on 2018-11-20 (1 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1804624/+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 1794229] Re: python packages should not ship colliding /usr/lib/python3/dist-packages/.pytest_cache
** Bug watch added: Debian Bug tracker #909529 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909529 ** Also affects: alembic (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909529 Importance: Unknown Status: Unknown ** Changed in: alembic (Ubuntu) Status: New => Fix Committed ** Changed in: alembic (Ubuntu) Assignee: (unassigned) => James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1794229 Title: python packages should not ship colliding /usr/lib/python3/dist- packages/.pytest_cache Status in alembic package in Ubuntu: Fix Committed Status in astroid package in Ubuntu: Invalid Status in dh-python package in Ubuntu: New Status in Debian: Fix Released Status in alembic package in Debian: Unknown Bug description: Python packages should not ship /usr/lib/python3/dist- packages/.pytest_cache Recently, two packages python3-alembic and python3-astroid both shipped these files which collided on package install dh-python has been improved upstream to stream all hidden "dot" directories in Debian #907871 This change should be imported and both alembic and astroid should be rebuilt (plus any other packages shipping this file) Preparing to unpack .../178-python3-astroid_2.0.4-1_all.deb ... Unpacking python3-astroid (2.0.4-1) over (1.6.5-1ubuntu4) ... dpkg: error processing archive /tmp/apt-dpkg-install-rbF4wE/178-python3-astroid_2.0.4-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/.pytest_cache/v/cache/nodeids', which is also in package python3-alembic 1.0.0-1ubuntu1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alembic/+bug/1794229/+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 1582470] Re: should put OOPS ID / URL in .uploaded file
This bug was fixed in the package whoopsie - 0.2.63 --- whoopsie (0.2.63) disco; urgency=medium * Write the reported OOPS ID to the .uploaded file. (LP: #1582470) -- Brian Murray Wed, 21 Nov 2018 12:42:23 -0800 ** Changed in: whoopsie (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1582470 Title: should put OOPS ID / URL in .uploaded file Status in Whoopsie: In Progress Status in whoopsie package in Ubuntu: Fix Released Bug description: To make it easier to investigate crash dumps, it would be helpful if whoopsie could put the OOPS ID and errors.ubuntu.com URL in the .uploaded file it creates after upload to indicate successful transfer. This makes it much easier, for example, for a script to pull everything in /var/crash/ and get information relevant for submitting a bug report. At the moment, I instead try to parse the ID out of whoopsie.log and generate the URL, but that tends to be a bit brittle. This is mostly to help with data collection during automated testing, but also to make manual investigations easier. To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1582470/+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 1804624] Re: Rhythmbox freezes after playing a Amiga mod file
Thank you for your bug repot, could you attach a file example here or give an url to download one? ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1804624 Title: Rhythmbox freezes after playing a Amiga mod file Status in gstreamer1.0 package in Ubuntu: New Bug description: Easy to reproduce: 1. Get a Amiga .mod file (any will do). 2. Add it to rhythmbox play queue 3. Play it 4. After playing rhythmbox GUI freezes and needs to be killed. The bug may be as well in gstreamer plugin responsible for mods but this is how it appears for end users. Tested on up to date Ubuntu 18.04.1 LTS and rhythmbox 3.4.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 22 11:25:48 2018 InstallationDate: Installed on 2018-11-20 (1 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1804624/+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 1803743] Re: Sometimes the sound disappears
I am do step 3 in link "Missing a crash report or having a .crash attachment" when sound disappears. I find one .crash file _usr_bin_RHVoice-client.1000.crash Мaybe that's what we need. But the service is installed much later than the appearance of the problem. Please, see my screenshots https://cloud.mail.ru/public/4xRS/Y6TbMXT7s Pictures 1 3 *.png. I am change variable "realtime-scheduling" and rebooted the system until the problem appeared. Then i am do steps 1-2 in link "Missing a crash report or having a .crash attachment". But there are no new crash reports. Only _usr_bin_RHVoice-client.1000.crash. Please, see my screenshots https://cloud.mail.ru/public/4xRS/Y6TbMXT7s Pictures 2 1 *.png. Sorry for bad english. This is a partially google translation. ** Attachment added: "_usr_bin_RHVoice-client.1000.crash" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803743/+attachment/5215268/+files/_usr_bin_RHVoice-client.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1803743 Title: Sometimes the sound disappears Status in pulseaudio package in Ubuntu: Incomplete Bug description: Здравствуйте! С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук. Определить по какой причине так и не получилось. Если звук пропадает то помогает только перезагрузка. Обращался на форум, но безрезультатно https://forum.ubuntu.ru/index.php?topic=278602.0 Пару раз переустанавливал Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. Первых два шага не помогают. Проблема остается и звук появляется только при перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю. В третьем шаге предлагается специальный скрипт, который собирает всю необходимую информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей системе в момент когда звук отсутствует http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 Помогите, пожалуйста. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: a 1288 F pulseaudio /dev/snd/controlC0: a 1288 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: H61MLV2 dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/02/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.family: None dmi.product.name: H61MLV2 dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803743/+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 1804624] [NEW] Rhythmbox freezes after playing a Amiga mod file
Public bug reported: Easy to reproduce: 1. Get a Amiga .mod file (any will do). 2. Add it to rhythmbox play queue 3. Play it 4. After playing rhythmbox GUI freezes and needs to be killed. The bug may be as well in gstreamer plugin responsible for mods but this is how it appears for end users. Tested on up to date Ubuntu 18.04.1 LTS and rhythmbox 3.4.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 22 11:25:48 2018 InstallationDate: Installed on 2018-11-20 (1 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1804624 Title: Rhythmbox freezes after playing a Amiga mod file Status in gstreamer1.0 package in Ubuntu: New Bug description: Easy to reproduce: 1. Get a Amiga .mod file (any will do). 2. Add it to rhythmbox play queue 3. Play it 4. After playing rhythmbox GUI freezes and needs to be killed. The bug may be as well in gstreamer plugin responsible for mods but this is how it appears for end users. Tested on up to date Ubuntu 18.04.1 LTS and rhythmbox 3.4.2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Nov 22 11:25:48 2018 InstallationDate: Installed on 2018-11-20 (1 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1804624/+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 1804611] [NEW] systemd-networkd is stuck in 'configuring' with DHCP and no default route
Public bug reported: In our network setup systemd-networkd fails to configure everything correctly. Our systems have two NIC which are configured via DHCP. One NIC is in a service network without a default route. With this setup we get systemd-networkd-wait-online.service failing after timeout and the service NIC stuck in 'configuring'. Besides that, everything is working as expected. Our config: # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Package # cat /etc/systemd/network/ens160.network [Match] Name=ens160 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac # cat /etc/systemd/network/ens192.network [Match] Name=ens192 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac UseRoutes=false UseDNS=false networkctl status -a ● 1: lo Link File: n/a Network File: n/a Type: loopback State: carrier (unmanaged) Address: 127.0.0.1 ::1 ● 2: ens160 Link File: n/a Network File: /etc/systemd/network/ens160.network Type: ether State: routable (configured) Path: pci-:03:00.0 Vendor: VMware Model: VMXNET3 Ethernet Controller HW Address: 00:50:56:a4:98:4c (VMware, Inc.) Address: 10.22.0.30 fe80::250:56ff:fea4:984c Gateway: 10.22.200.254 (Hewlett Packard Enterprise) DNS: 10.22.0.2 Search Domains: xxx ● 3: ens192 Link File: n/a Network File: /etc/systemd/network/ens192.network Type: ether State: routable (configuring) Path: pci-:0b:00.0 Vendor: VMware Model: VMXNET3 Ethernet Controller HW Address: 00:50:56:a4:c0:42 (VMware, Inc.) Address: 10.23.0.30 fe80::250:56ff:fea4:c042 Search Domains: This also happens in other configurations, which are more complex as soon as I add the service NIC which has no default route. systemd 239 from ubuntu 16.10 works fine. ** 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/1804611 Title: systemd-networkd is stuck in 'configuring' with DHCP and no default route Status in systemd package in Ubuntu: New Bug description: In our network setup systemd-networkd fails to configure everything correctly. Our systems have two NIC which are configured via DHCP. One NIC is in a service network without a default route. With this setup we get systemd-networkd-wait-online.service failing after timeout and the service NIC stuck in 'configuring'. Besides that, everything is working as expected. Our config: # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Package # cat /etc/systemd/network/ens160.network [Match] Name=ens160 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac # cat /etc/systemd/network/ens192.network [Match] Name=ens192 [Network] DHCP=ipv4 [DHCP] UseMTU=true RouteMetric=100 ClientIdentifier=mac UseRoutes=false UseDNS=false networkctl status -a ● 1: lo Link File: n/a Network File: n/a Type: loopback State: carrier (unmanaged) Address: 127.0.0.1 ::1 ● 2: ens160 Link File: n/a Network File: /etc/systemd/network/ens160.network Type: ether State: routable (configured) Path: pci-:03:00.0 Vendor: VMware Model: VMXNET3 Ethernet Controller HW Address: 00:50:56:a4:98:4c (VMware, Inc.) Address: 10.22.0.30 fe80::250:56ff:fea4:984c Gateway: 10.22.200.254 (Hewlett Packard Enterprise) DNS: 10.22.0.2 Search Domains: xxx ● 3: ens192
[Touch-packages] [Bug 1804603] [NEW] systemd-tmpfiles-setup.service fails on btrfs
Public bug reported: After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: New Bug description: After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1804422] Re: package python3 3.6.7-1~18.04 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
this seems to be a gdebi bug. bad package? maybe re-installation helps
Setting up python3 (3.6.7-1~18.04) ...
running python rtupdate hooks for python3.6...
dpkg-query: package 'gdebi-core' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
Traceback (most recent call last):
File "/usr/bin/py3clean", line 210, in
main()
File "/usr/bin/py3clean", line 196, in main
pfiles = set(dpf.from_package(options.package))
File "/usr/share/python3/debpython/files.py", line 53, in from_package
raise Exception("cannot get content of %s" % package_name)
Exception: cannot get content of gdebi-core
error running python rtupdate hook gdebi-core
dpkg: error processing package python3 (--configure):
installed python3 package post-installation script subprocess returned error
exit status 4
** Package changed: python3-defaults (Ubuntu) => gdebi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1804422
Title:
package python3 3.6.7-1~18.04 failed to install/upgrade: installed
python3 package post-installation script subprocess returned error
exit status 4
Status in gdebi package in Ubuntu:
Confirmed
Bug description:
installation or removal of the package failed
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3 3.6.7-1~18.04
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Wed Nov 21 11:51:47 2018
ErrorMessage: installed python3 package post-installation script subprocess
returned error exit status 4
InstallationDate: Installed on 2018-07-17 (126 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal,
3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu2.1
apt 1.6.6
SourcePackage: python3-defaults
Title: package python3 3.6.7-1~18.04 failed to install/upgrade: installed
python3 package post-installation script subprocess returned error exit status 4
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1804422/+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
