[Touch-packages] [Bug 1855140] Re: How to handle tmpfiles.d in non-systemd environments
Hi Christian
According to https://www.debian.org/vote/2019/vote_002#outcome the
decision was to use "Systemd but we support exploring alternatives".
>From the proposal:
"Packages should include service units or init scripts to start daemons
and services. Packages may use any systemd facility at the package
maintainer's discretion, provided that this is consistent with other
Policy requirements and the normal expectation that packages shouldn't
depend on experimental or unsupported (in Debian) features of other
packages. Packages may include support for alternate init systems
besides systemd and may include alternatives for any systemd-specific
interfaces they use. Maintainers use their normal procedures for
deciding which patches to include."
>From my understanding this means that supporting an alternative init
system is optional ("Packages may include support for alternate init
systems besides systemd"). So basically this is up to the package
maintainer whether or not the package should support an alternative init
system.
Given the (still rising) popularity of Docker/Kubernetes containers, it
would indeed by very nice that the affected packages (such as haproxy)
do adjust for a non-systemd environment.
--
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/1855140
Title:
How to handle tmpfiles.d in non-systemd environments
Status in haproxy package in Ubuntu:
Opinion
Status in systemd package in Ubuntu:
New
Bug description:
This is a general issue about systemd features like tmpfiles.d which
won't run in some environments like docker containers.
Packages more and more rely on that with haproxy being the example
that opened the bug, but clearly not the only one.
I wanted to add tasks for all affected, but a qucik check showed that
there are almost to many.
$ apt-file search tmpfiles.d | cut -d':' -f 1 | sort | uniq
129 at the moment and probably increasing.
List of affected as of Dec 2019:
acmetool anytun apt-cacher-ng bacula-common bind9 binkd bley bzflag-server
ceph-common certmonger cockpit-ws colord connman courier-authdaemon
courier-imap courier-ldap courier-mlm courier-mta courier-pop cryptsetup-bin
cyrus-common dbus dhcpcanon diaspora-common dnssec-trigger ejabberd fail2ban
firebird3.0-server freeipa-client freeipa-server glusterfs-server gvfs-common
haproxy hddemux heartbeat htcondor i2pd inn inspircd iodine knot knot-resolver
krb5-otp laptop-mode-tools lemonldap-ng-fastcgi-server libreswan lighttpd lirc
lvm2 mailman mailman3 mailman3-web man-db mandos memcached mon mpd munge
munin-common myproxy-server nagios-nrpe-server ngircd nrpe-ng nscd nsd
nullmailer nut-client nut-server opencryptoki opendkim opendmarc
opendnssec-enforcer opendnssec-signer opennebula opennebula-sunstone opensips
open-vm-tools-desktop openvpn passwd pesign php7.2-fpm pidentd ploop
postgresql-common prads prelude-correlator prelude-lml prelude-manager puppet
pushpin resource-agents rkt rpcbind rsyslog samba-common-bin screen
shairport-sync shibboleth-sp2-utils slurmctld slurmd slurmdbd sogo
spice-vdagent sqwebmail sslh sudo sudo-ldap systemd systemd-container tcpcryptd
tinyproxy tuned ulogd2 uptimed vrfydmn vsftpd w1retap-doc wdm
wesnoth-1.12-server x2goserver-common xpra yadifa zabbix-agent
zabbix-java-gateway zabbix-proxy-mysql zabbix-proxy-pgsql zabbix-proxy-sqlite3
zabbix-server-mysql zabbix-server-pgsql
Handling of these heavily Depends on the recent Debian GR [1].
I'd suggest we wait how that turns out and then need to consider how
(if?) to handle it in a central place, probably systemd or a
derivative tool as started to be discussed in [2]
If possible I'd avoid fixes in individual packages as it encourages
growth of various workarounds for a problem that needs a general
solution.
[1]: https://www.debian.org/vote/2019/vote_002
[2]: https://lists.debian.org/debian-devel/2019/12/msg00060.html
--- Original report below ---
When installing the haproxy package from the current Ubuntu 18.04
Bionic repos, the package does not install the directory /run/haproxy.
This directory is mentioned in the default config file
/etc/haproxy/haproxy.cfg:
stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd
listeners
Starting HAProxy manually will show the following error:
# /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg
[ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket
[/run/haproxy/admin.sock]
After manual creation of the directory, the start works:
# mkdir /run/haproxy
# /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg
# ps auxf
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash
root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf
root 1
[Touch-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
Please file an upstream bug at https://bugzilla.kernel.org/ Product: Drivers Component: Sound(ALSA) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.3 LTS Kernel 5.5.0 pulseaudio: Installed: 1:11.1-1ubuntu7.4 X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound. I have surround 5.1 speakers and the Front Left and Right are Muted. I have to unmute Headphones in alsamixer to hear sound from the front left and right speakers is the workaround. This step should not be required for speakers 5.1 to work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: richard2533 F pulseaudio /dev/snd/controlC1: richard2533 F pulseaudio /dev/snd/controlC0: richard2533 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-28 (2 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Please test this kernel: https://people.canonical.com/~khfeng/lp1860754/ -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1862865] 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 1862865
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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [7
[Touch-packages] [Bug 1805543] Re: Packaged version of iptables doesn't provide --random-fully flag.
Hi all,
I manually built iptables 1.6.2 using the instructions at
http://www.linuxfromscratch.org/blfs/view/8.2/postlfs/iptables.html and my
problem is if I use
#iptables -V
output is 1.6.2
and if I use
#apt-cache policy iptables
it is showing 1.6.0 only. i went through following process. can anybody
suggest/correct me wr is the mistake.
1 downloaded and extracted iptables-1.6.2.tar.bz2
2 ./configure --prefix=/usr \
--sbindir=/sbin\
--disable-nftables \
--enable-libipq\
--with-xtlibdir=/lib/xtables &&
make
3 make install &&
ln -sfv ../../sbin/xtables-multi /usr/bin/iptables-xml &&
for file in ip4tc ip6tc ipq iptc xtables
do
mv -v /usr/lib/lib${file}.so.* /lib &&
ln -sfv ../../lib/$(readlink /usr/lib/lib${file}.so) /usr/lib/lib${file}.so
done
4 downloaded and extracted blfs-bootscripts-20180105
5 make install-iptables
Please suggest how to get the updated info in apt-cache policy iptables
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1805543
Title:
Packaged version of iptables doesn't provide --random-fully flag.
Status in iptables package in Ubuntu:
Confirmed
Bug description:
Hello. This isn't strictly a bug, but more of an upgrade-request on
the iptables package. Normally i wouldn't be inclined to submit such
a bug report, but a user on the ubuntu-devel-discuss mailing list
encouraged me to submit this anyway [1]. For our production systems,
we're running into a kernel race condition bug, for which a workaround
has been made available. The fix boils down to iptables having a new
flag which it passes down to the kernel, to enable the workaround.
However, the version of iptables in Ubuntu (v1.6.1) doesn't support
that kernel feature yet. Specifically, it's introduced in this commit
on the iptables codebase:
https://git.netfilter.org/iptables/commit/?id=8b0da2130b8af3890ef20afb2305f11224bb39ec.
The feature we need from that commit is part of the v1.6.2 and newer
iptables releases, but it looks like the Bionic, Cosmic, and Disco
releases of Ubuntu all include v1.6.1 without that patch, so for now
we're going to have to build iptables from source on our production
machines. That shouldn't pose any huge issues, but of course, we'd
prefer to be able to use the package from package management, or
perhaps a backported package from a newer Ubuntu release.
So to summarise, this might be an invalid bug report, but consider it
a vote to upgrade the packaged version of iptables. If this bug
report is entirely inappropriate, then I apologise.
1. Link to thread on ubuntu-devel-discuss where I describe the problem
and Nish suggests I file this bug report:
https://lists.ubuntu.com/archives/ubuntu-devel-
discuss/2018-November/018181.html
Ubuntu version we're using:
Description: Ubuntu 18.04.1 LTS
Release: 18.04
$ apt-cache policy iptables
iptables:
Installed: 1.6.1-2ubuntu2
Candidate: 1.6.1-2ubuntu2
Version table:
*** 1.6.1-2ubuntu2 500
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64
Packages
100 /var/lib/dpkg/status
Thanks for your time,
Paul
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1805543/+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 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
** Package changed: linux-meta-5.4 (Ubuntu Focal) => linux (Ubuntu
Focal)
--
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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Incomplete
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Incomplete
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:15 dharkan kernel: [71070.591932] i91
[Touch-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
| 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
(prog-if 00 [VGA controller])
| Subsystem: Lenovo ThinkPad X1 Carbon 5th Gen
Linux 5.4.0-9.12
** Also affects: linux-meta-5.4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: Invalid
** Also affects: linux-meta-5.4 (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux-meta-5.4 package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in linux-meta-5.4 source package in Focal:
New
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
This bug is fixed with commit 82f23e3d to curtin on branch master. To view that commit see the following URL: https://git.launchpad.net/curtin/commit/?id=82f23e3d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: In Progress Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: In Progress Status in util-linux source package in Focal: New Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1863195] Re: py3compile should not emit python runtime warnings during dist-upgrade
Setting up printer-driver-hpcups (3.19.12+dfsg0-3ubuntu1) ... Setting up gir1.2-freedesktop:amd64 (1.62.0-4ubuntu3) ... Setting up ubuntu-drivers-common (1:0.7.7) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) Setting up linux-generic (5.4.0.14.17) ... Setting up python3-talloc:amd64 (2.3.0-3ubuntu1) ... Setting up hplip-data (3.19.12+dfsg0-3ubuntu1) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) /usr/share/hplip/base/utils.py:2063: SyntaxWarning: "is" with a literal. Did you mean "=="? if weburl is "" or weburl is None: /usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did you mean "=="? if log_level is 'debug': /usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you mean "!="? if 'getfacl' not in g and '' is not g and 'file' not in g: /usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a literal. Did you mean "=="? if home_dir is "": /usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": /usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. Did you mean "!="? if self.latest_available_version is not "": Setting up samba-libs:amd64 (2:4.11.1+dfsg-3ubuntu4) ... Setting up libswresample3:amd64 (7:4.2.2-1build1) ... and similar. We cannot, and will not fix them all. -- 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/1863195 Title: py3compile should not emit python runtime warnings during dist-upgrade Status in dh-python package in Ubuntu: New Bug description: py3compile should compile without emitting python runtime warnings on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are emitted during apt upgrade, due to buffering=1 being deprecated. We will not fix all the packages, and these warnings are not helpful to the users, as they cannot and shouldn't need to do anything about them, as they come from packages that are maintained by the distro. Imho py3compile should execute python interpreter with -W ignore Or maybe set PYTHONWARNINGS=ignore in the environment during the upgrade? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195/+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 1752200] Re: toolbar and the menubar disappear
** Summary changed: - desktop bug + toolbar and the menubar disappear ** Summary changed: - toolbar and the menubar disappear + toolbar and the menubar disappear ** Package changed: xorg (Ubuntu) => unity (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/1752200 Title: toolbar and the menubar disappear Status in unity package in Ubuntu: New Bug description: My notebook show a bug, the toolbar and the menubar has dissapear, after i refresh for the program have sugest ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 27 21:21:43 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:100c] InstallationDate: Installed on 2017-09-29 (151 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 04f2:b520 Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-574 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic 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: 11/27/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/27/2015:svnAcer:pnAspireE5-574:pvrV1.10:rvnAcer:rnZoro_SL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-574 dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Feb 27 21:19:48 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1752200/+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 1752723] Re: Screen keeps flickering
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (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/1752723 Title: Screen keeps flickering Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: Trying to see if there was any issues with my graphics drivers, as my laptops screen keeps flickering. It flickers less so on browsers etc, but I just booted up a game on steam and it was flickering constantly, almost enough to give me epilepsy ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Thu Mar 1 21:50:43 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed nvidia-304, 304.135, 4.4.0-116-generic, x86_64: installed GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:0941] InstallationDate: Installed on 2016-10-05 (512 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b550 Chicony Electronics Co., Ltd Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited W94_95_97JU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-109-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: 03/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: W94_95_97JU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd03/30/2016:svnPCSpecialistLimited:pnW94_95_97JU:pvrNotApplicable:rvnCLEVO:rnW94_95_97JU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: W94_95_97JU dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.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 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Feb 26 18:13:11 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1170 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1752723/+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 1863195] [NEW] py3compile should not emit python runtime warnings during dist-upgrade
Public bug reported: py3compile should compile without emitting python runtime warnings on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are emitted during apt upgrade, due to buffering=1 being deprecated. We will not fix all the packages, and these warnings are not helpful to the users, as they cannot and shouldn't need to do anything about them, as they come from packages that are maintained by the distro. Imho py3compile should execute python interpreter with -W ignore Or maybe set PYTHONWARNINGS=ignore in the environment during the upgrade? ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New ** Tags: champagne ** Summary changed: - py3compile should compile without emitting python runtime warnings + py3compile should not emit python runtime warnings during dist-upgrade -- 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/1863195 Title: py3compile should not emit python runtime warnings during dist-upgrade Status in dh-python package in Ubuntu: New Bug description: py3compile should compile without emitting python runtime warnings on dist-upgrade from bionic to focal a tonne of RuntimeWarnings are emitted during apt upgrade, due to buffering=1 being deprecated. We will not fix all the packages, and these warnings are not helpful to the users, as they cannot and shouldn't need to do anything about them, as they come from packages that are maintained by the distro. Imho py3compile should execute python interpreter with -W ignore Or maybe set PYTHONWARNINGS=ignore in the environment during the upgrade? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1863195/+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 1862459] Re: ubuntu 18 screen flicker/blink
Thanks for the bug report. I can see two possible problems here that might relate to screen flicker: * The i915 kernel driver crashed, in intel_modeset_init * Xorg is using probably the wrong driver 'intel'. It should be using the modesetting driver on a modern system like yours. Please try removing that wrong driver: sudo apt remove xserver-xorg-video-intel or just try logging into "Ubuntu on Wayland" instead. Maybe it's some combination of the above two issues. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- 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/1862459 Title: ubuntu 18 screen flicker/blink Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Ubuntu screen flicker /blinking on start laptop every time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Sat Feb 8 20:50:43 2020 DistUpgraded: 2019-06-27 23:49:46,134 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1574 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-27 (225 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Thu Jun 27 18:02:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862459/+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 1759796] Re: Ubuntu images fail to build due to broken dh-python package
3.20180325ubuntu2~cloud1 in the cloud archive and everywhere else. ** Changed in: dh-python (Ubuntu) Status: New => 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/1759796 Title: Ubuntu images fail to build due to broken dh-python package Status in kolla: Fix Released Status in dh-python package in Ubuntu: Fix Released Bug description: Some ubuntu images fails to build and block the gate. 2018-03-28 15:07:13.498244 | primary | CRITICAL:tests.test_build:>>> Expected image 'ovn-controller' to succeed! 2018-03-28 15:07:13.498650 | primary | CRITICAL:tests.test_build:>>> Expected image 'ovn-northd' to succeed! 2018-03-28 15:07:13.498957 | primary | CRITICAL:tests.test_build:>>> Expected image 'bifrost-base' to succeed! 2018-03-28 15:07:13.499241 | primary | CRITICAL:tests.test_build:>>> Expected image 'ovsdpdk' to succeed! 2018-03-28 15:07:13.499559 | primary | CRITICAL:tests.test_build:>>> Expected image 'ovn-sb-db-server' to succeed! 2018-03-28 15:07:13.499867 | primary | CRITICAL:tests.test_build:>>> Expected image 'ovn-nb-db-server' to succeed! http://logs.openstack.org/33/555733/1/check/kolla-build-ubuntu- source/72f9085/job-output.txt.gz#_2018-03-28_15_07_13_498244 Looking more closely, it appears they fail to install lsb-release that depends on python3. Going up the dependency chain, the issue seems to be in dh-python that added a dependency on python3-distuils. However python3-distuils doesn't exist and should probably be python3-distutils. ()[root@f8bc5d1d504e bifrost-5.0.1.dev43]# apt-cache show dh-python Package: dh-python Priority: optional Section: python Installed-Size: 429 Maintainer: Piotr Ożarowski Architecture: all Version: 3.20180325ubuntu1~cloud0 Replaces: python3 (<< 3.3.2-4~) Suggests: libdpkg-perl, dpkg-dev Depends: python3:any (>= 3.3.2-2~), python3-distuils Breaks: python3 (<< 3.3.2-4~) Supported: 60m Filename: pool/main/d/dh-python/dh-python_3.20180325ubuntu1~cloud0_all.deb Size: 89382 SHA256: 5d31a348f141d7ca366eeb21b58633bed96a0b27417ce8759e1cb785cb1db8bc SHA1: a817acac0042ab6e22dd686376717a20e449ae03 MD5sum: d89b5e505bbb93b57efe4bfb85fc353d Description: Debian helper tools for packaging Python libraries and applications Description-md5: b21cd6f99d6093fdc7e0ba30c8dd949f Multi-Arch: foreign Original-Maintainer: Piotr Ożarowski To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1759796/+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 1863049] Re: plz rectify this bugs
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! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1863049 Title: plz rectify this bugs Status in Ubuntu: Incomplete Bug description: q ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_64_73_generic_59 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:20:24 2020 DistUpgraded: 2018-09-13 18:17:06,036 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2016-03-08 (1437 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. X555LAB ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=a8582c35-8f2e-4581-8019-65e2d7d13535 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-13 (517 days ago) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Thu Sep 13 14:39:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1116 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1863049/+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 1863083] Re: systemerror detected
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Won't Fix -- 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/1863083 Title: systemerror detected Status in Ubuntu: Won't Fix Bug description: get message systemerror detected. press button sent nothing heppens on reboot same message don 't know what error is detected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 11:12:23 2020 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2016-09-26 (1234 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=c763e4d7-fb91-470e-88b9-75aeb931dd49 ro nomode=1 SourcePackage: xorg SystemImageInfo: Error: [Errno 2] Bestand of map bestaat niet: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM DH dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd06/01/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: Thu Feb 13 10:48:03 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Keyboard KEYBOARD, id 8 inputLogitech USB Keyboard KEYBOARD, id 9 inputDarfon USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 505 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1863083/+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 1863123] Re: Fail to connect bug still persists - Removal tool???
*** This bug is a duplicate of bug 1858280 *** https://bugs.launchpad.net/bugs/1858280 ** This bug has been marked a duplicate of bug 1858280 Firefox reports "cannot connect to internet" message -- 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/1863123 Title: Fail to connect bug still persists - Removal tool??? Status in xorg package in Ubuntu: New Bug description: Any help in removing this bug that randomly mimics connection failure. After x-Diagnose program and reporting this bug, it clears out but always reappears later again and again. Is there a removal tool or program that can clear it out for good? I appreciate any tips or help that I can get. Thank you for your time in reading this report. J.Chosta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:27:26 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1289 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (414 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863123/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Just checked again and it seems neither upstream Linux nor upstream PulseAudio have landed this yet. Perhaps they don't know about it or have lost track of the patches. To get the ball rolling, anyone affected please open new upstream bugs in both: Linux: https://bugzilla.kernel.org/ PulseAudio: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues and then tell us the new bug IDs. If the Ubuntu kernel team is listening then maybe they can help with this. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Paolo, To check if ucm files getting loaded, what I know is to check the pusleaudio's log. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1862267] Re: sqlite3 3.31.1-1 is broken on s390x
** Changed in: sqlite3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1862267 Title: sqlite3 3.31.1-1 is broken on s390x Status in sqlite3 package in Ubuntu: Fix Released Bug description: sqlite3 3.31.1-1 is broken on s390x for example building orthanc against 3.30.1-1ubuntu1 is successful without any errors, whilst upgrading sqlite3 to 3.31.1-1 and reruning the orthanc testsuite without rebuilding results in segfaults. please remove 3.31.1-1 sqlite3 from the archive until it is fixed on s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1862267/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Paolo, Just remove "Headset" from all LENOVO-*.conf, change that line to cset "name='Mic Boost Volume' 2" reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1863189] [NEW] package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo
Public bug reported: I can't update my packages by using sudo apt-get update, because it fails to download some repositories. (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB] Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB] Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages [210 kB] Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages [167 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata [73,0 kB] Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 Metadata File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons [9.954 B] Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 Icons Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons [15,1 kB] Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 Icons Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata [26,2 kB] Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 Metadata Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons [18,5 kB] Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 Icons Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons [22,9 kB] Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 Icons Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata [8.064 B] Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 DEP-11 Metadata File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 200.236.31.4 80] Hashes of expected file: - Filesize:8064 [weak] - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak] - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak] Release file created at: Thu, 13 Feb 2020 22:50:01 + Baixados 186 kB em 4s (44,0 kB/s) Lendo listas de pacotes... Pronto E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 2801:82:80ff:8000::5 80] Hashes of expected file: - Filesize:73000 [weak] - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak] - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak] Release file created at: Thu, 13 Feb 2020 22:49:41 + E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/universe/dep11/Components-amd64.yml.xz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/universe/dep11/icons-48x48.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/universe/dep11/icons-64x64.tar.gz E: Falhou ao buscar http://br.archive.ubuntu.com/ubuntu/dists/eoan-backports/universe/dep11/Components-amd64.yml.xz File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 200.236.31.4 80] Hashes of expected file: - Filesize:8064 [weak] - SHA256:ec8750e513d95f057f05b2c0269f
[Touch-packages] [Bug 1863148] Re: RFE: update libjson-c-dev to 0.13
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: json-c (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1863148 Title: RFE: update libjson-c-dev to 0.13 Status in json-c package in Ubuntu: Confirmed Bug description: All versions of libjson-c-dev prior to 0.13 lack the json_pointer API. As the result, libjson-c-dev is only useful since Eoan, which is very disappointing. Please update json-c to 0.13 on every supported distro prior to Eoan (Disco, Bionic, Xenial etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1863148/+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 1757600] Re: RM: Please remove from focal (Qt4 removal)
Removing packages from focal: autopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal amd64 autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal arm64 autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal armhf autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal ppc64el autopilot-qt4 1.4+15.10.20150825-0ubuntu1 in focal s390x autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal amd64 autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal arm64 autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal armhf autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal ppc64el autopilot-qt5 1.4+15.10.20150825-0ubuntu1 in focal s390x libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal amd64 libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal arm64 libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal armhf libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal ppc64el libautopilot-qt 1.4+15.10.20150825-0ubuntu1 in focal s390x libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal amd64 libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal arm64 libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal armhf libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal ppc64el libautopilot-qt-autopilot 1.4+15.10.20150825-0ubuntu1 in focal s390x qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal amd64 qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal arm64 qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal armhf qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal ppc64el qttestability-autopilot 1.4+15.10.20150825-0ubuntu1 in focal s390x Comment: Unmaintained, depends on obsolete Qt4, last upload 5 years ago; LP: #1757600 1 package successfully removed. ** Changed in: autopilot-qt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757600 Title: RM: Please remove from focal (Qt4 removal) Status in autopilot-qt package in Ubuntu: Fix Released Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-qt/+bug/1757600/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
Balint, based on your input... > thanks for the fixes in Eoan. Unfortunately we have a product based on > disco and cannot move forward at this time. Being a networking shop, > this issue has a serious effect on us and we would like to avoid moving > to something like ifupdown2 within our stable branch. So, Disco is EOL as it is not a LTS version, that is why it did not get a fix (as the fix is very close to the one done in Eoan). Since its unsupported by the community, it's up to you backport the Eoan fixes to Disco if you'd like... you can even create a PPA for your product and distribute along. > For our users the real impact of the bug is not that that the interface > that we are currently reconfiguring is suffering a downtime, but the > fact that _all_ interfaces have their aliases removed if networkd is > restarted. The proposed KeepConfiguration solution kind of beats the > purpose of reconfiguring the interfaces, as old addresses are kept and > need to be handled manually. Also it interferes with how DHCP works. I > believe this might be an issue for others as well. We are following systemd-networkd upstream decisions here. The option "dhcp" only exists for CERTAIN scenarios (when root disk depends on that connection, for iSCSI and/or NFS/ROOT for example). It is explicitly said in the documentation: """ Takes a boolean or one of "static", "dhcp-on-stop", "dhcp". When "static", systemd-networkd will not drop static addresses and routes on starting up process. When set to "dhcp-on-stop", systemd-networkd will not drop addresses and routes on stopping the daemon. When "dhcp", the addresses and routes provided by a DHCP server will never be dropped even if the DHCP lease expires. This is contrary to the DHCP specification, but may be the best choice if, e.g., the root filesystem relies on this connection. The setting "dhcp" implies "dhcp-on-stop", and "yes" implies "dhcp" and "static". Defaults to "no". """ and it is a question of choice: to have a window of opportunity for duplicate IPs - in cases where there is no dynamic IP mapping to that mac address - but possibly maintain the connection instead of causing uninterruptable I/Os trying to shutdown a machine, for example. I particularly don't like this option but it is not the default one and was meant for a specific purpose. > > >From our point of view the ideal solution would be a combination of the > keepalived patch that detects VIP removal and systemd version 244 that > already supports "networkctl reconfigure" and "networkctl reload". networkctl reconfigure/reload is a new functionality and won't be added to previous already released versions as this is against SRU guidelines. Systemd 244.2-1ubuntu1 is being included in 20.04, our NEXT LTS version. Like said before, you can try backporting systemd 244 to disco, or bionic, if you are willing to support it on your own as it was already EOL for community support. You should follow: https://packaging.ubuntu.com/html/backports.html if you would like to do that. For the keepalived patches, they could be backported to Eoan, maybe Bionic and Xenial depending on the amount of work. But then I would need a practical example of why the systemd-networkd fix is no good in most used scenarios. > Is there any chance that v244 is backported to bionic? It is already > included in focal and debian stable backports, but unfortunately I am > not familiar enough with systemd development to tell what the impact of > this would be. Problem with backports is that they are unsupported even on supported releases. I wouldn't be able to guarantee functionalities or fix it in a constant basis. You can do it on your own and have it in a PPA of your product, for example. As systemd nowadays include networkd, udev management, sysV runtime generators, tmpfiles creation, sockets creation, cgroups integration for the process slices, etc etc... it is very very risky to backport systemd to have "just" those 2 functionalities. > > As for keepalived, in bug #1819074 there was an ongoing investigation on > the patch, that implements the keepalived transition on removing the > VIP. We have traced back this functionality to this patch: > > https://github.com/acassen/keepalived/commit/0b1528c76d3fe8d1c5765841df86c59570a036da > > It was born before v1.3.6 was released, so we hope that it is self- > contained enough for a backport if v2.0 of keepalived is not included in > bionic-backports. Let me check keepalived fix more closely and see what can be done for the previous releases. As we are close to freeze date for our next LTS release, it is unlikely that I do it before 2 weeks from now (as our focus is in the development version entirely and I still need to fix netplan to support the networkd KeepConfiguration functionality). Lets keep talking.. I'll first patch netplan and go back with other releases to check what can be done for them. For now I would *strongly* recommend that in previous releases, whoever wants to u
[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
** Also affects: heartbeat (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: keepalived (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: keepalived (Ubuntu Xenial) Status: New => Confirmed ** Changed in: keepalived (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** No longer affects: heartbeat (Ubuntu Xenial) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- 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/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in Keepalived Charm: New Status in netplan: Confirmed Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: In Progress Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Status in keepalived source package in Disco: Won't Fix Status in systemd source package in Disco: Won't Fix Status in keepalived source package in Eoan: In Progress Status in systemd source package in Eoan: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses:
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
I have tried, unsuccessfully, to reproduce this issue internally. Details of my setup below. 1) I have a pair of Dell R210 servers racked (u072 and u073 below), each with a BCM57416 installed: root@u072:~# lspci | grep BCM57416 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) 01:00.1 Ethernet controller: Broadcom Inc. and subsidiaries BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet Controller (rev 01) 2) I've matched the firmware version to one that Nivedita reported in a bad system: root@u072:~# ethtool -i enp1s0f0np0 driver: bnxt_en version: 1.10.0 firmware-version: 214.0.253.1/pkg 21.40.25.31 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: no 3) Matched Ubuntu release and kernel version: root@u072:~# lsb_release -dr Description:Ubuntu 18.04.3 LTS Release:18.04 root@u072:~# uname -a Linux u072 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux 4) Configured the interface into an active-backup bond: root@u072:~# cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup) Primary Slave: None Currently Active Slave: enp1s0f1np1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: enp1s0f1np1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: 00:0a:f7:a7:10:61 Slave queue ID: 0 Slave Interface: enp1s0f0np0 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 1 Permanent HW addr: 00:0a:f7:a7:10:60 Slave queue ID: 0 5) Run the provided mtr and netperf test cases with the 1st port selected as active: root@u072:~# ip l set enp1s0f1np1 down root@u072:~# ip l set enp1s0f1np1 up root@u072:~# cat /proc/net/bonding/bond0 | grep Active Currently Active Slave: enp1s0f0np0 a) initiated on u072: root@u072:~# mtr --no-dns --report --report-cycles 60 192.168.1.2 Start: 2020-02-13T20:48:01+ HOST: u072Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.1.20.0%600.2 0.2 0.2 0.2 0.0 root@u072:~# netperf -t TCP_RR -H 192.168.1.2 -- -r 1,1 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.2 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 131072 11 10.0029040.91 16384 87380 root@u072:~# netperf -t TCP_RR -H 192.168.1.2 -- -r 64,64 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.2 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 131072 64 64 10.0028633.36 16384 87380 root@u072:~# netperf -t TCP_RR -H 192.168.1.2 -- -r 128,8192 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.2 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 131072 128 819210.0017469.30 16384 87380 b) initiated on u073: root@u073:~# mtr --no-dns --report --report-cycles 60 192.168.1.1 Start: 2020-02-13T20:53:37+ HOST: u073Loss% Snt Last Avg Best Wrst StDev 1.|-- 192.168.1.10.0%600.1 0.1 0.1 0.2 0.0 root@u073:~# netperf -t TCP_RR -H 192.168.1.1 -- -r 1,1 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.1 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 87380 11 10.0028514.93 16384 131072 root@u073:~# netperf -t TCP_RR -H 192.168.1.1 -- -r 64,64 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.1 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate bytes Bytes bytesbytes secs.per sec 16384 87380 64 64 10.0027405.88 16384 131072 root@u073:~# netperf -t TCP_RR -H 192.168.1.1 -- -r 128,8192 MIGRATED TCP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.1 () port 0 AF_INET : demo : first burst 0 Local /Remote Socket Size Request Resp. Elapsed Trans. Send Recv Size SizeTime Rate b
[Touch-packages] [Bug 1863165] Re: autoremove-kernels doesn't purge kernels
So, how can I convince APT to _automatically_ remove all kernel
leftovers? I could of course run a cron job with the workaround, but
maybe this can be done The Right Way? :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863165
Title:
autoremove-kernels doesn't purge kernels
Status in apt package in Ubuntu:
Invalid
Bug description:
Maybe this is a configuration issue, but:
# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# dpkg -l | grep ^rc | cut -c-70
rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
upgrades.service) doesn't seem to remove the kernel's configuration
files.
The kernel images and modules are removed, only the package list (and
maybe /usr/share/doc/linux*) is cluttered with the remnants of old
kernels.
Workaround:
dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg
-P
# lsb_release -r; dpkg -s apt | grep Ver; uname -r
Release:18.04
Version: 1.6.12
5.3.0-23-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863165/+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 1863001] Re: [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
The attachment "Patch against console-setup-1.194ubuntu2/debian /keyboard-configuration.config - fixes LT layout" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg- reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Confirmed Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1857542] Re: lxc-checkpoint needs the criu package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- 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/1857542 Title: lxc-checkpoint needs the criu package Status in lxc package in Ubuntu: Confirmed Bug description: lxc-checkpoint needs criu to be installed but the criu package is absent in eoan and focal (criu exists in disco and bionic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857542/+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 1863165] Re: autoremove-kernels doesn't purge kernels
This is not what the purge flag does. Starting in 20.04, you can use apt
purge ~c aka apt purge ?configuration-files to purge packages left in
configuration files.
The latter also works in 19.10. both also work with aptitude purge in
older releases.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863165
Title:
autoremove-kernels doesn't purge kernels
Status in apt package in Ubuntu:
Invalid
Bug description:
Maybe this is a configuration issue, but:
# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# dpkg -l | grep ^rc | cut -c-70
rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
upgrades.service) doesn't seem to remove the kernel's configuration
files.
The kernel images and modules are removed, only the package list (and
maybe /usr/share/doc/linux*) is cluttered with the remnants of old
kernels.
Workaround:
dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg
-P
# lsb_release -r; dpkg -s apt | grep Ver; uname -r
Release:18.04
Version: 1.6.12
5.3.0-23-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863165/+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 1863164] Re: ImportError: could not import gobject (error was: ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so: undefined symbol: PyExc_NotImple
Definitely not a bug in python-apt. Reassigning to python3.8, but
haven't seen this before, so must be something special on your system.
** Package changed: python-apt (Ubuntu) => python3.8 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863164
Title:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64
-linux-gnu.so: undefined symbol: PyExc_NotImplementedError'))
Status in python3.8 package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install Ubuntu 20.04 LTS
2. Start first terminal with `tail -f ~/.xsession-errors`
3. Start second terminal and run `caja -q` from here
Expected results:
* there are no error messages or warnings in 1st terminl
Actual results:
* there are several error messages and warnings:
(caja:14755): Gtk-WARNING **: 22:55:26.070: Failed to register client:
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register
client
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in
import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in
import apt_pkg
ImportError:
/usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_ValueError
Original exception was:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-apt 1.9.5
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 13 22:52:33 2020
InstallationDate: Installed on 2020-02-11 (1 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64
(20200211)
SourcePackage: python-apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1863164/+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 1863165] [NEW] autoremove-kernels doesn't purge kernels
Public bug reported:
Maybe this is a configuration issue, but:
# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# dpkg -l | grep ^rc | cut -c-70
rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels (triggered by unattended-
upgrades.service) doesn't seem to remove the kernel's configuration
files.
The kernel images and modules are removed, only the package list (and
maybe /usr/share/doc/linux*) is cluttered with the remnants of old
kernels.
Workaround:
dpkg -l | awk '/^rc.*linux-(image|modules)/ {print $2}' | xargs dpkg -P
# lsb_release -r; dpkg -s apt | grep Ver; uname -r
Release:18.04
Version: 1.6.12
5.3.0-23-generic
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Maybe this is a configuration issue, but:
-
# apt-get --purge autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
- # dpkg -l | grep ^rc | cut -c-80
- rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel image
generic
- rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel image
generic
- rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel extra
modules
- rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel extra
modules
+ # dpkg -l | grep ^rc | cut -c-70
+ rc linux-image-4.15.0-66-generic 4.15.0-66.75 amd64 Signed kernel imag
+ rc linux-image-4.15.0-67-generic 4.15.0-67.76 amd64 Signed kernel imag
+ rc linux-image-4.15.0-71-generic 4.15.0-71.80 amd64 Signed kernel imag
+ rc linux-image-4.15.0-72-generic 4.15.0-72.81 amd64 Signed kernel imag
+ rc linux-image-4.15.0-73-generic 4.15.0-73.82 amd64 Signed kernel imag
+ rc linux-image-4.15.0-74-generic 4.15.0-74.84 amd64 Signed kernel imag
+ rc linux-image-4.15.0-75-generic 4.15.0-75.85 amd64 Signed kernel imag
+ rc linux-image-4.15.0-76-generic 4.15.0-76.86 amd64 Signed kernel imag
+ rc linux-modules-4.15.0-66-generic 4.15.0-66.75 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-67-generic 4.15.0-67.76 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-71-generic 4.15.0-71.80 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-72-generic 4.15.0-72.81 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-73-generic 4.15.0-73.82 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-74-generic 4.15.0-74.84 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-75-generic 4.15.0-75.85 amd64 Linux kernel ext
+ rc linux-modules-4.15.0-76-generic 4.15.0-76.86 amd64 Linux kernel ext
-
- And the "rc" translates to "Remove/Conf-files". For some reason
/etc/apt/apt.conf.d/01autoremove-kernels (tr
[Touch-packages] [Bug 1863164] [NEW] ImportError: could not import gobject (error was: ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so: undefined symbol: PyExc_NotImp
Public bug reported:
Steps to reproduce:
1. Install Ubuntu 20.04 LTS
2. Start first terminal with `tail -f ~/.xsession-errors`
3. Start second terminal and run `caja -q` from here
Expected results:
* there are no error messages or warnings in 1st terminl
Actual results:
* there are several error messages and warnings:
(caja:14755): Gtk-WARNING **: 22:55:26.070: Failed to register client:
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register
client
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in
import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in
import apt_pkg
ImportError:
/usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_ValueError
Original exception was:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-apt 1.9.5
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 13 22:52:33 2020
InstallationDate: Installed on 2020-02-11 (1 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200211)
SourcePackage: python-apt
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1863164
Title:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64
-linux-gnu.so: undefined symbol: PyExc_NotImplementedError'))
Status in python-apt package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install Ubuntu 20.04 LTS
2. Start first terminal with `tail -f ~/.xsession-errors`
3. Start second terminal and run `caja -q` from here
Expected results:
* there are no error messages or warnings in 1st terminl
Actual results:
* there are several error messages and warnings:
(caja:14755): Gtk-WARNING **: 22:55:26.070: Failed to register client:
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register
client
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in
from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in
import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in
from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in
import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in
import apt_pkg
ImportError:
/usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_ValueError
Original exception was:
ImportError: could not import gobject (error was:
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
undefined symbol: PyExc_NotImplementedError'))
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-apt 1.9.5
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 13 22:52:33 2020
InstallationDate: Installed on 2020-02-11 (1 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64
(20200211)
SourcePack
[Touch-packages] [Bug 1863158] [NEW] UTF-8 Encoding errors with Security patch in 2.9.4+dfsg1-6.1ubuntu1.3
Public bug reported: I'm using libxml2 via perl-bindings in XML::LibXML. After upgrading to 2.9.4+dfsg1-6.1ubuntu1.3 my perl-scripts threw many UTF-8 encoding errors, e.g. "Malformed UTF-8 character: \xb0 (unexpected continuation byte 0xb0, with no preceding start byte." Re-installing libxml2.so.2.9.4 from 2.9.4+dfsg1-6.1ubuntu1.2 and linking libxml2.so.2 to this file without changing anything else lead to error- free execution of the perl-scripts: All Unicode characters are ok. At present, I'm not able to reduce the error situation in such a way that a simple perl script can be given which reproduces this error - I'm working on this. I'm also not able to provide an error description using libxml2 directly, without perl. So, please be patient with me and this stumbling bug-report. My system is: Description:Ubuntu 18.04.4 LTS Release:18.04 ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1863158 Title: UTF-8 Encoding errors with Security patch in 2.9.4+dfsg1-6.1ubuntu1.3 Status in libxml2 package in Ubuntu: New Bug description: I'm using libxml2 via perl-bindings in XML::LibXML. After upgrading to 2.9.4+dfsg1-6.1ubuntu1.3 my perl-scripts threw many UTF-8 encoding errors, e.g. "Malformed UTF-8 character: \xb0 (unexpected continuation byte 0xb0, with no preceding start byte." Re-installing libxml2.so.2.9.4 from 2.9.4+dfsg1-6.1ubuntu1.2 and linking libxml2.so.2 to this file without changing anything else lead to error-free execution of the perl-scripts: All Unicode characters are ok. At present, I'm not able to reduce the error situation in such a way that a simple perl script can be given which reproduces this error - I'm working on this. I'm also not able to provide an error description using libxml2 directly, without perl. So, please be patient with me and this stumbling bug-report. My system is: Description:Ubuntu 18.04.4 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1863158/+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 1863157] [NEW] Petition to bring back file name copy/paste functionality in GTK file chooser
Public bug reported: For a very long time, I've never/rarely needed to hand-type file paths/names - it is extremely slow, error-proning and requiring a lot more work (reading/clicking/moving cursors) to do this simple task. Instead, I use tabs in a terminal to navigate, pwd to print, and copy/paste to another file browser or window to use the full path. In many file browsers (like Thunar), I could also single click on the file, and directly paste it to the address bar and it directly gives the full file name. But this becomes increasingly difficult to do on the GTK file chooser rolled out sometimes ago. The file chooser window first removed the file path address bar, but at least there was a button I can click to show it to copy/paste. Then, even that button disappeared - after many frustrating hours, the only way to show the address bar is "Ctrl+L", after reading many similarly frustrated posts https://www.google.com/search?q=unable+to+type+path+dialog+ubuntu https://www.google.com/search?q=unable+to+type+path+dialog+site%3Aaskubuntu.com&oq=unable+to+type+path+dialog+site https://www.google.com/search?q=can+not+type+path+in+file+selector+linux+site:askubuntu.com >From the long lists of complains that one can find online (I could easily find more), I think this just prove that removing/hiding the address bar is very counter intuitive and should be reverted. I see where this came from - to mimic Mac OS, like most GNOME style/appearance was trying to achieve, and this setting maybe cleaner and easier to attract less experienced users, but for people use Linux for work day-in-and-day-out, this is highly annoying and counter productive. Here I would like to petition to revert the change and bring back the address bar in the file chooser dialog (which is shared among not just GNOME, but other GTK based desktops, such as xfce), or at least bring back the button option. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "current file chooser" https://bugs.launchpad.net/bugs/1863157/+attachment/5328055/+files/Screenshot_2020-02-13_14-01-19.png -- 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/1863157 Title: Petition to bring back file name copy/paste functionality in GTK file chooser Status in gtk+3.0 package in Ubuntu: New Bug description: For a very long time, I've never/rarely needed to hand-type file paths/names - it is extremely slow, error-proning and requiring a lot more work (reading/clicking/moving cursors) to do this simple task. Instead, I use tabs in a terminal to navigate, pwd to print, and copy/paste to another file browser or window to use the full path. In many file browsers (like Thunar), I could also single click on the file, and directly paste it to the address bar and it directly gives the full file name. But this becomes increasingly difficult to do on the GTK file chooser rolled out sometimes ago. The file chooser window first removed the file path address bar, but at least there was a button I can click to show it to copy/paste. Then, even that button disappeared - after many frustrating hours, the only way to show the address bar is "Ctrl+L", after reading many similarly frustrated posts https://www.google.com/search?q=unable+to+type+path+dialog+ubuntu https://www.google.com/search?q=unable+to+type+path+dialog+site%3Aaskubuntu.com&oq=unable+to+type+path+dialog+site https://www.google.com/search?q=can+not+type+path+in+file+selector+linux+site:askubuntu.com From the long lists of complains that one can find online (I could easily find more), I think this just prove that removing/hiding the address bar is very counter intuitive and should be reverted. I see where this came from - to mimic Mac OS, like most GNOME style/appearance was trying to achieve, and this setting maybe cleaner and easier to attract less experienced users, but for people use Linux for work day-in-and-day-out, this is highly annoying and counter productive. Here I would like to petition to revert the change and bring back the address bar in the file chooser dialog (which is shared among not just GNOME, but other GTK based desktops, such as xfce), or at least bring back the button option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1863157/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
A pity that I have to look for an extra usb microphone while I spent $200+ on a fancy bluetooth headset to have conference calls on my laptop. Reproduced with 3 bluetooth headsets. Quality is so poor on hsp/hfp that it's unusable. Didn't understand why I couldn't make it work decently until I found this bug. Does anyone have a workaround, managed to hack his way out of this bug? -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1863148] [NEW] RFE: update libjson-c-dev to 0.13
Public bug reported: All versions of libjson-c-dev prior to 0.13 lack the json_pointer API. As the result, libjson-c-dev is only useful since Eoan, which is very disappointing. Please update json-c to 0.13 on every supported distro prior to Eoan (Disco, Bionic, Xenial etc). ** Affects: json-c (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1863148 Title: RFE: update libjson-c-dev to 0.13 Status in json-c package in Ubuntu: New Bug description: All versions of libjson-c-dev prior to 0.13 lack the json_pointer API. As the result, libjson-c-dev is only useful since Eoan, which is very disappointing. Please update json-c to 0.13 on every supported distro prior to Eoan (Disco, Bionic, Xenial etc). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1863148/+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 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)
** Changed in: gtk Status: Fix Released => New -- 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/1846188 Title: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only) Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Fix Committed Status in nautilus package in Ubuntu: Invalid Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 In Nautilus, tooltips appear far to the left in the app menu. (Kazam and Peek were unable to record Nautilus) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1846188/+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 1863001] Re: [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg- reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: Confirmed Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: libodb-mysql (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: libgda5 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: jabberd2 (Ubuntu) Status: New => In Progress ** Changed in: kannel (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: hoel (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: New Status in kannel package in Ubuntu: New Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1862846] Re: Crash and failure installing focal
** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1862846 Title: Crash and failure installing focal Status in subiquity: New Status in curtin package in Ubuntu: In Progress Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: In Progress Status in util-linux source package in Focal: New Status in util-linux package in Debian: New Bug description: During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system. Attached are the logs left on the install USB key. To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1862846/+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 1840375] Re: groupdel doesn't support extrausers
** Description changed:
snapd needs the ability to call 'groupdel --extrausers foo' to clean up
after itself, but --extrausers is currently unsupported.
- [Impact]
+ [Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
+ 0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and configure it
2. run "groupadd --extrausers foo"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
- * low: this adds a new (optional) option which is off by default
+ * low: this adds a new (optional) option which is off by default
** Description changed:
snapd needs the ability to call 'groupdel --extrausers foo' to clean up
after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
- 1. install the libnss-extrausers and configure it
+ 1. install the libnss-extrausers and configure it (see
/usr/share/doc/libnss-extrausers/README for the modifications in sswitch.conf)
2. run "groupadd --extrausers foo"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Triaged
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Committed
Status in shadow source package in Disco:
Fix Committed
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and configure it (see
/usr/share/doc/libnss-extrausers/README for the modifications in sswitch.conf)
2. run "groupadd --extrausers foo"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1863026] Re: Remove my_bool typedef workaround
** Changed in: gnokii (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: In Progress Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in hoel package in Ubuntu: New Status in jabberd2 package in Ubuntu: New Status in kannel package in Ubuntu: New Status in libgda5 package in Ubuntu: New Status in libodb-mysql package in Ubuntu: New Status in lyricue package in Ubuntu: New Status in motion package in Ubuntu: New Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: New Status in mysqltcl package in Ubuntu: New Status in opendnssec package in Ubuntu: New Status in opensmtpd-extras package in Ubuntu: New Status in orthanc-mysql package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in pvpgn package in Ubuntu: New Status in qt4-x11 package in Ubuntu: New Status in redland package in Ubuntu: New Status in tango package in Ubuntu: New Status in tntdb package in Ubuntu: New Status in voms-mysql-plugin package in Ubuntu: New Status in vtk7 package in Ubuntu: New Status in w1retap package in Ubuntu: New Status in zoneminder package in Ubuntu: New Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1849859] Re: smb printing fails
Hi everyone. Any news about this bug? I'm trying just now...but it asks me for credentials with no way to insert username and password -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1863123] [NEW] Fail to connect bug still persists - Removal tool???
Public bug reported: Any help in removing this bug that randomly mimics connection failure. After x-Diagnose program and reporting this bug, it clears out but always reappears later again and again. Is there a removal tool or program that can clear it out for good? I appreciate any tips or help that I can get. Thank you for your time in reading this report. J.Chosta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:27:26 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1289 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (414 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** 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/1863123 Title: Fail to connect bug still persists - Removal tool??? Status in xorg package in Ubuntu: New Bug description: Any help in removing this bug that randomly mimics connection failure. After x-Diagnose program and reporting this bug, it clears out but always reappears later again and again. Is there a removal tool or program that can clear it out for good? I appreciate any tips or help that I can get. Thank you for your time in reading this report. J.Chosta ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:27:26 2020 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1289 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang thans for your reply. tree -L 1 . . ├── apq8064-tabla-snd-card ├── broadwell-rt286 ├── chtrt5645 ├── DAISY-I2S ├── DB410c ├── Dell-WD15-Dock ├── GoogleNyan ├── HDAudio-Lenovo-DualCodecs ├── LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX ├── LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC ├── LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05 ├── LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17 ├── LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO ├── Manta-I2S ├── Manta-SPDIF ├── msm8974-taiko-mtp-snd-card ├── PandaBoard ├── PandaBoardES ├── PAZ00 ├── SDP4430 ├── skylake-rt286 ├── sof-skl_hda_card ├── tegraalc5632 ├── tegra-rt5640 ├── Tuna └── VEYRON-I2S > grep -r "Headset Mic Boost Volume" LENOVO-* LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX/LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX.conf: cset "name='Headset Mic Boost Volume' 2" LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC/LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC.conf: cset "name='Headset Mic Boost Volume' 2" LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05/LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05.conf: cset "name='Headset Mic Boost Volume' 2" LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17/LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17.conf: cset "name='Headset Mic Boost Volume' 1" LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO/LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO.conf: cset "name='Headset Mic Boost Volume' 2" But nothing changed, i still need "load-module module-alsa-source device=hw:0,7" under "/etc/pulse/default.pa" to see a working mic. How can i see which ucm files getting loaded by Alsa ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
This patch replaces not intuitive secondary lt(us) layout with us(altgr- intl), which uses majority of Lithuanian users as secondary layout. ** Patch added: "Patch against console-setup-1.194ubuntu2/debian/keyboard-configuration.config - fixes LT layout" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+attachment/5328000/+files/keyboard-configuration.config-LT-layout.patch ** Description changed: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" - I will attach a patch to debian/keyboard-configuration.config file which + I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue ** Tags added: patch ** Summary changed: - Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity + [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: [PATCH] Incorrect LAYOUT is set when choosing Lithuanian in dpkg- reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: New Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I'm attaching a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1863001] Re: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity
** Tags added: bionic focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863001 Title: Incorrect LAYOUT is set when choosing Lithuanian in dpkg-reconfigure keyboard-configuration and Ubiquity Status in console-setup package in Ubuntu: New Bug description: If user chooses Lithuanian keyboard layout during installation (Ubiquity) or dpkg-reconfigure keyboard-configuration then incorrect layout is set in /etc/default/keyboard : XKBLAYOUT="lt,lt" XKBVARIANT=",us" This configuration is not intuitive, because people think, that sometimes Lithuanian keyboard works (when lt1 is selected in GNOME shell panel) and sometimes doesn't work (when lt2 is selected). So, majority of Lithuanian users are force to removed second lt(us) layout and add English (US) altgr-intl layout. So, correct /etc/default/keyboard should be: XKBMODEL="pc105" XKBLAYOUT="lt,us" XKBVARIANT=",altgr-intl" XKBOPTIONS="grp_led:scroll" BACKSPACE="guess" I will attach a patch to debian/keyboard-configuration.config file which fixes this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863001/+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 1862459] Re: ubuntu 18 screen flicker/blink
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1862459 Title: ubuntu 18 screen flicker/blink Status in xorg package in Ubuntu: New Bug description: Ubuntu screen flicker /blinking on start laptop every time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Sat Feb 8 20:50:43 2020 DistUpgraded: 2019-06-27 23:49:46,134 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1574 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-06-27 (225 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Thu Jun 27 18:02:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1862459/+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 1862770] Re: MySQL autopkgtest regressed in Focal release pocket
*** This bug is a duplicate of bug 1862364 *** https://bugs.launchpad.net/bugs/1862364 Ah, nm, this is a duplicate =o). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1862770 Title: MySQL autopkgtest regressed in Focal release pocket Status in mysql-8.0 package in Ubuntu: New Status in shadow package in Ubuntu: New Bug description: http://autopkgtest.ubuntu.com/packages/m/mysql-8.0/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/m/mysql-8.0/20200211_122839_60bab@/log.gz ... 63%] main.events_1 [ fail ] Test ended at 2020-02-11 12:06:00 CURRENT_TEST: main.events_1 mysqltest: At line 69: Query 'ALTER EVENT event_starts_test ON SCHEDULE AT '2020-02-02 20:00:02'' failed. ERROR 1589 (HY000): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future. The result from queries just before the failure was: drop event if exists event1; Warnings: Note 1305Event event1 does not exist create event event1 on schedule every 15 minute starts now() ends date_add(now(), interval 5 hour) DO begin end; alter event event1 rename to event2 enable; alter event event2 disable; alter event event2 enable; alter event event2 on completion not preserve; alter event event2 on schedule every 1 year on completion preserve rename to event3 comment "new comment" do begin select 1; end__ alter event event3 rename to event2; drop event event2; create event event2 on schedule every 2 second starts now() ends date_add(now(), interval 5 hour) comment "some" DO begin end; drop event event2; CREATE EVENT event_starts_test ON SCHEDULE EVERY 10 SECOND COMMENT "" DO SELECT 1; SELECT interval_field, interval_value, event_definition FROM information_schema.events WHERE event_name='event_starts_test'; INTERVAL_FIELDINTERVAL_VALUE EVENT_DEFINITION SECOND10 SELECT 1 SELECT execute_at IS NULL, starts IS NULL, ends IS NULL, event_comment FROM information_schema.events WHERE event_schema='events_test' AND event_name='event_starts_test'; execute_at IS NULLstarts IS NULL ends IS NULLEVENT_COMMENT 1 0 1 safe_process[25029]: Child process: 25030, exit: 1 - the logfile can be found in '/tmp/tmp.YL1y5O4jCj/var/log/main.events_1/events_1.log' ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770/+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 1862770] Re: MySQL autopkgtest regressed in Focal release pocket
*** This bug is a duplicate of bug 1862364 *** https://bugs.launchpad.net/bugs/1862364 I have just uploaded mysql-8.0_8.0.19-0ubuntu3 containing fixes for the 2020 year in mysql tests. I'll flag this as Fix Committed and Fix Released manually as only LP: #1862364 was referred in that changelog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1862770 Title: MySQL autopkgtest regressed in Focal release pocket Status in mysql-8.0 package in Ubuntu: New Status in shadow package in Ubuntu: New Bug description: http://autopkgtest.ubuntu.com/packages/m/mysql-8.0/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/m/mysql-8.0/20200211_122839_60bab@/log.gz ... 63%] main.events_1 [ fail ] Test ended at 2020-02-11 12:06:00 CURRENT_TEST: main.events_1 mysqltest: At line 69: Query 'ALTER EVENT event_starts_test ON SCHEDULE AT '2020-02-02 20:00:02'' failed. ERROR 1589 (HY000): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future. The result from queries just before the failure was: drop event if exists event1; Warnings: Note 1305Event event1 does not exist create event event1 on schedule every 15 minute starts now() ends date_add(now(), interval 5 hour) DO begin end; alter event event1 rename to event2 enable; alter event event2 disable; alter event event2 enable; alter event event2 on completion not preserve; alter event event2 on schedule every 1 year on completion preserve rename to event3 comment "new comment" do begin select 1; end__ alter event event3 rename to event2; drop event event2; create event event2 on schedule every 2 second starts now() ends date_add(now(), interval 5 hour) comment "some" DO begin end; drop event event2; CREATE EVENT event_starts_test ON SCHEDULE EVERY 10 SECOND COMMENT "" DO SELECT 1; SELECT interval_field, interval_value, event_definition FROM information_schema.events WHERE event_name='event_starts_test'; INTERVAL_FIELDINTERVAL_VALUE EVENT_DEFINITION SECOND10 SELECT 1 SELECT execute_at IS NULL, starts IS NULL, ends IS NULL, event_comment FROM information_schema.events WHERE event_schema='events_test' AND event_name='event_starts_test'; execute_at IS NULLstarts IS NULL ends IS NULLEVENT_COMMENT 1 0 1 safe_process[25029]: Child process: 25030, exit: 1 - the logfile can be found in '/tmp/tmp.YL1y5O4jCj/var/log/main.events_1/events_1.log' ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770/+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 1862770] Re: MySQL autopkgtest regressed in Focal release pocket
*** This bug is a duplicate of bug 1862364 *** https://bugs.launchpad.net/bugs/1862364 Related bugs: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862364 https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1859100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1862770 Title: MySQL autopkgtest regressed in Focal release pocket Status in mysql-8.0 package in Ubuntu: New Status in shadow package in Ubuntu: New Bug description: http://autopkgtest.ubuntu.com/packages/m/mysql-8.0/focal/amd64 https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/m/mysql-8.0/20200211_122839_60bab@/log.gz ... 63%] main.events_1 [ fail ] Test ended at 2020-02-11 12:06:00 CURRENT_TEST: main.events_1 mysqltest: At line 69: Query 'ALTER EVENT event_starts_test ON SCHEDULE AT '2020-02-02 20:00:02'' failed. ERROR 1589 (HY000): Event execution time is in the past and ON COMPLETION NOT PRESERVE is set. The event was not changed. Specify a time in the future. The result from queries just before the failure was: drop event if exists event1; Warnings: Note 1305Event event1 does not exist create event event1 on schedule every 15 minute starts now() ends date_add(now(), interval 5 hour) DO begin end; alter event event1 rename to event2 enable; alter event event2 disable; alter event event2 enable; alter event event2 on completion not preserve; alter event event2 on schedule every 1 year on completion preserve rename to event3 comment "new comment" do begin select 1; end__ alter event event3 rename to event2; drop event event2; create event event2 on schedule every 2 second starts now() ends date_add(now(), interval 5 hour) comment "some" DO begin end; drop event event2; CREATE EVENT event_starts_test ON SCHEDULE EVERY 10 SECOND COMMENT "" DO SELECT 1; SELECT interval_field, interval_value, event_definition FROM information_schema.events WHERE event_name='event_starts_test'; INTERVAL_FIELDINTERVAL_VALUE EVENT_DEFINITION SECOND10 SELECT 1 SELECT execute_at IS NULL, starts IS NULL, ends IS NULL, event_comment FROM information_schema.events WHERE event_schema='events_test' AND event_name='event_starts_test'; execute_at IS NULLstarts IS NULL ends IS NULLEVENT_COMMENT 1 0 1 safe_process[25029]: Child process: 25030, exit: 1 - the logfile can be found in '/tmp/tmp.YL1y5O4jCj/var/log/main.events_1/events_1.log' ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770/+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 1863049] Re: plz rectify this bugs
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1863049 Title: plz rectify this bugs Status in xorg package in Ubuntu: New Bug description: q ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_64_73_generic_59 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 10:20:24 2020 DistUpgraded: 2018-09-13 18:17:06,036 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2016-03-08 (1437 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: ASUSTeK COMPUTER INC. X555LAB ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=a8582c35-8f2e-4581-8019-65e2d7d13535 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-13 (517 days ago) dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Thu Sep 13 14:39:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1116 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863049/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@Paolo, That is easy to fix. change cset "name='Headset Mic Boost Volume' 1" to cset "name='Mic Boost Volume' 2" in the all LENOVO_*/LENOVO_*.conf sudo cp -rf /usr/share/alsa/ucm/LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO/ /usr/share/alsa/ucm/LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX/ sudo mv /usr/share/alsa/ucm/LENOVO-20QD00LKIX-ThinkPadX1Carbon7th- 20QD00LKIX/LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO.conf /usr/share/alsa/ucm /LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX/LENOVO-20QD00LKIX- ThinkPadX1Carbon7th-20QD00LKIX.conf reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1863083] Re: systemerror detected
** Package changed: ubuntu => xorg (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/1863083 Title: systemerror detected Status in xorg package in Ubuntu: New Bug description: get message systemerror detected. press button sent nothing heppens on reboot same message don 't know what error is detected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 11:12:23 2020 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2016-09-26 (1234 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=c763e4d7-fb91-470e-88b9-75aeb931dd49 ro nomode=1 SourcePackage: xorg SystemImageInfo: Error: [Errno 2] Bestand of map bestaat niet: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM DH dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd06/01/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: Thu Feb 13 10:48:03 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Keyboard KEYBOARD, id 8 inputLogitech USB Keyboard KEYBOARD, id 9 inputDarfon USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 505 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863083/+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 1863083] [NEW] systemerror detected
You have been subscribed to a public bug: get message systemerror detected. press button sent nothing heppens on reboot same message don 't know what error is detected ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 13 11:12:23 2020 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2016-09-26 (1234 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=c763e4d7-fb91-470e-88b9-75aeb931dd49 ro nomode=1 SourcePackage: xorg SystemImageInfo: Error: [Errno 2] Bestand of map bestaat niet: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-VM DH dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd06/01/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: Thu Feb 13 10:48:03 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Keyboard KEYBOARD, id 8 inputLogitech USB Keyboard KEYBOARD, id 9 inputDarfon USB Optical Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 505 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubuntu -- systemerror detected https://bugs.launchpad.net/bugs/1863083 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1786495] Re: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all
Seems that it still breaks: https://www.reddit.com/r/linuxhardware/comments/f37ypz/audio_stopped_working_after_upgrade_from_50037/ And nic30 solution either works for me, previously after upgrading kernel I had problems with sound but downgrade was bringing sound back. For now, it's not working on my company M4800, but I need audio because I talk with clients. I have Nvidia 440. Thanks! -- 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/1786495 Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am head no sound from my headphone jack. Laptop speaker work fine. Tried 2 different headphones and still no sound. pavucontrol can see my headphone and I see the sound bar move but no sound comes out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hhernandez 2083 F...m pulseaudio /dev/snd/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio CurrentDesktop: MATE Date: Fri Aug 10 07:59:09 2018 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/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0V5GVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/19/2015:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1786495/+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 1757600] Re: RM: Please port your package away from Qt 4
Please remove autopilot-qt from focal: src and binaries $ reverse-depends src:autopilot-qt No reverse dependencies found $ reverse-depends -b src:autopilot-qt No reverse dependencies found ** Summary changed: - RM: Please port your package away from Qt 4 + RM: Please remove from focal (Qt4 removal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu. https://bugs.launchpad.net/bugs/1757600 Title: RM: Please remove from focal (Qt4 removal) Status in autopilot-qt package in Ubuntu: Triaged Bug description: Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case. Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so. If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me [1] https://wiki.debian.org/Qt4Removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-qt/+bug/1757600/+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 1858092] Re: Network Manager not saving OpenVPN password
Can confirm that, after updating from the official repositories (Kubuntu 19.10), saving passwords "for this user only" works as intended again. Thanks! -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1863080] [NEW] Unable to use dead keys in Java apps
Public bug reported: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: dead-keys ibus java -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1863080 Title: Unable to use dead keys in Java apps Status in ibus package in Ubuntu: New Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1863080/+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 1863078] Re: package keyboard-configuration 1.178ubuntu2.9 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863078 Title: package keyboard-configuration 1.178ubuntu2.9 failed to install/upgrade: installed keyboard-configuration package post- installation script subprocess returned error exit status 127 Status in console-setup package in Ubuntu: New Bug description: i have no details. I'm just a user. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-1012.15-oem 4.15.18 Uname: Linux 4.15.0-1012-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Thu Feb 13 07:31:16 2020 DuplicateSignature: package:keyboard-configuration:1.178ubuntu2.9 Setting up keyboard-configuration (1.178ubuntu2.9) ... archdetect: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory dpkg: error processing package keyboard-configuration (--configure): installed keyboard-configuration package post-installation script subprocess returned error exit status 127 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-02-11 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.9 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863078/+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 1863078] [NEW] package keyboard-configuration 1.178ubuntu2.9 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned erro
Public bug reported: i have no details. I'm just a user. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-1012.15-oem 4.15.18 Uname: Linux 4.15.0-1012-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Thu Feb 13 07:31:16 2020 DuplicateSignature: package:keyboard-configuration:1.178ubuntu2.9 Setting up keyboard-configuration (1.178ubuntu2.9) ... archdetect: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory dpkg: error processing package keyboard-configuration (--configure): installed keyboard-configuration package post-installation script subprocess returned error exit status 127 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-02-11 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.9 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (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 console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1863078 Title: package keyboard-configuration 1.178ubuntu2.9 failed to install/upgrade: installed keyboard-configuration package post- installation script subprocess returned error exit status 127 Status in console-setup package in Ubuntu: New Bug description: i have no details. I'm just a user. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-1012.15-oem 4.15.18 Uname: Linux 4.15.0-1012-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Thu Feb 13 07:31:16 2020 DuplicateSignature: package:keyboard-configuration:1.178ubuntu2.9 Setting up keyboard-configuration (1.178ubuntu2.9) ... archdetect: error while loading shared libraries: libdebian-installer.so.4: cannot open shared object file: No such file or directory dpkg: error processing package keyboard-configuration (--configure): installed keyboard-configuration package post-installation script subprocess returned error exit status 127 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-02-11 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.9 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1863078/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Thanks for your reply @hui.wang So, i've tried to change "name='Mic Boost Volume' 2"" all the LENOVO files but nothing changed. Your assumption about the cardlongname was right, because it seems that is different from the versioned ones, mine is "LENOVO-20QD00LKIX- ThinkPadX1Carbon7th-20QD00LKIX". pactl list cards Card #0 Name: alsa_card.pci-_00_1f.3-platform-skl_hda_dsp_generic Driver: module-alsa-card.c Owner Module: 7 Properties: alsa.card = "0" alsa.card_name = "sof-skl_hda_card" alsa.long_card_name = "LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9dc8" device.string = "0" device.description = "sof-skl_hda_card" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: input:stereo-fallback: Stereo Input (sinks: 0, sources: 1, priority: 51, available: no) input:multichannel-input: Multichannel Input (sinks: 0, sources: 1, priority: 1, available: yes) output:stereo-fallback: Stereo Output (sinks: 1, sources: 0, priority: 5100, available: yes) output:stereo-fallback+input:stereo-fallback: Stereo Output + Stereo Input (sinks: 1, sources: 1, priority: 5151, available: yes) output:stereo-fallback+input:multichannel-input: Stereo Output + Multichannel Input (sinks: 1, sources: 1, priority: 5101, available: yes) output:multichannel-output: Multichannel Output (sinks: 1, sources: 0, priority: 100, available: yes) output:multichannel-output+input:stereo-fallback: Multichannel Output + Stereo Input (sinks: 1, sources: 1, priority: 151, available: yes) output:multichannel-output+input:multichannel-input: Multichannel Duplex (sinks: 1, sources: 1, priority: 101, available: yes) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: output:stereo-fallback+input:multichannel-input Ports: analog-input-mic: Microphone (priority: 8700, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-input-microphone" Part of profile(s): input:stereo-fallback, output:stereo-fallback+input:stereo-fallback, output:multichannel-output+input:stereo-fallback multichannel-input: Multichannel Input (priority: 0, latency offset: 0 usec) Part of profile(s): input:multichannel-input, output:stereo-fallback+input:multichannel-input, output:multichannel-output+input:multichannel-input analog-output-speaker: Speakers (priority: 1, latency offset: 0 usec) Properties: device.icon_name = "audio-speakers" Part of profile(s): output:stereo-fallback, output:stereo-fallback+input:stereo-fallback, output:stereo-fallback+input:multichannel-input analog-output-headphones: Headphones (priority: 9000, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-headphones" Part of profile(s): output:stereo-fallback, output:stereo-fallback+input:stereo-fallback, output:stereo-fallback+input:multichannel-input multichannel-output: Multichannel Output (priority: 0, latency offset: 0 usec) Part of profile(s): output:multichannel-output, output:multichannel-output+input:stereo-fallback, output:multichannel-output+input:multichannel-input -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect th
[Touch-packages] [Bug 1832802] Re: disco: curl error while loading shared libraries: libssl.so.1.0.0
*** This bug is a duplicate of bug 1832801 *** https://bugs.launchpad.net/bugs/1832801 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832802 Title: disco: curl error while loading shared libraries: libssl.so.1.0.0 Status in curl package in Ubuntu: Confirmed Bug description: Linux 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DISTRIB_RELEASE=19.04 DISTRIB_DESCRIPTION="Ubuntu 19.04" curl: Installed: 7.64.0-2ubuntu1.1 Candidate: 7.64.0-2ubuntu1.1 Version table: *** 7.64.0-2ubuntu1.1 1001 1001 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.64.0-2ubuntu1 1001 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco/main amd64 Packages When I run curl, I get the following error: curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory On other disco machines I'm not experiencing this issue. I apt purged openssl/libssl/curl and re-installed, but the error persists. I'm sure my system has some issue, but I'm unable to figure it out, and this felt like a bug as curl was working before upgrade to disco. I tried proposed packages to see if openssl 1.1.1b-1ubuntu2.2 instead of 1.1.1b-1ubuntu2 would make any difference, but the error persists. me@mbp:/usr/lib/x86_64-linux-gnu$ curl curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory me@mbp:/usr/lib/x86_64-linux-gnu$ which curl /usr/bin/curl me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep curl ii curl 7.64.0-2ubuntu1.1 amd64command line tool for transferring data with URL syntax ii libcurl3-gnutls:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (GnuTLS flavour) ii libcurl4:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (OpenSSL flavour) ii python3-pycurl 7.43.0.2-0.1 amd64Python bindings to libcurl (Python 3) me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep ssl ii android-libboringssl8.1.0+r23-2 amd64Google's internal fork of OpenSSL for the Android SDK rc docbook-dsssl 1.79-9.1 all modular DocBook DSSSL stylesheets, for print and HTML ii libflac++6v5:amd64 1.3.2-3 amd64Free Lossless Audio Codec - C++ runtime library ii libflac8:amd64 1.3.2-3 amd64Free Lossless Audio Codec - runtime C library ii libflac8:i386 1.3.2-3 i386 Free Lossless Audio Codec - runtime C library ii libio-socket-ssl-perl 2.060-3 all Perl module implementing object oriented interface to SSL sockets ii libnet-smtp-ssl-perl1.04-1 all Perl module providing SSL support to Net::SMTP ii libnet-ssleay-perl 1.85-2ubuntu3 amd64Perl module for Secure Sockets Layer (SSL) ii libssl-dev:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - development files ii libssl1.1:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - shared libraries ii libssl1.1:i386 1.1.1b-1ubuntu2.2 i386 Secure Sockets Layer toolkit - shared libraries ii libwavpack1:amd64 5.1.0-5ubuntu0.1amd64audio codec (lossy and lossless) - library ii libwavpack1:i386 5.1.0-5ubuntu0
[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes
Thank you, Dan. The PPA build indeed fixes the test case in #8, for Xenial at the very least. Sending SIGABRT to foo.service's process now causes services to restart, just as intended. Here are the logs from the very same Xenial machine, as in #8: $ sudo apt install systemd=229-4ubuntu21.28~next20200212b2 <...> $ sudo systemctl daemon-reexec $ sudo systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Thu 2020-02-13 11:04:06 MSK; 5min ago Main PID: 4753 (sleep) CGroup: /system.slice/foo.service └─4753 /bin/sleep infinity Feb 13 11:04:06 pono-mac systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Thu 2020-02-13 11:04:06 MSK; 5min ago Main PID: 4759 (sleep) CGroup: /system.slice/bar.service └─4759 /bin/sleep infinity Feb 13 11:04:06 pono-mac systemd[1]: Started bar.service. $ sudo kill -6 4753 $ sudo systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Thu 2020-02-13 11:12:05 MSK; 2s ago Main PID: 11122 (sleep) Tasks: 1 Memory: 200.0K CPU: 1ms CGroup: /system.slice/foo.service └─11122 /bin/sleep infinity Feb 13 11:12:05 pono-mac systemd[1]: Stopped foo.service. Feb 13 11:12:05 pono-mac systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Thu 2020-02-13 11:12:05 MSK; 2s ago Main PID: 11123 (sleep) Tasks: 1 Memory: 224.0K CPU: 1ms CGroup: /system.slice/bar.service └─11123 /bin/sleep infinity Feb 13 11:12:05 pono-mac systemd[1]: Started bar.service. I'll test it with Bionic in a few hours. -- 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/1839290 Title: systemd doesn't restart a service after crashes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: Fix Released Bug description: [impact] when a service configured to restart crashes, under certain configurations, that service is not correctly restarted. [test case] see comment 8 [regression potential] this changes the job mode of manager-triggered restarts to 'replace' any existing queued job(s), instead of failing if there are queued job(s). thus any regressions would occur when a service fails, that is configured to restart on failure. [scope] This is needed only for Xenial and Bionic. this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51 which is included already in Eoan. [other info] original description: --- Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1839290/+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
