[Touch-packages] [Bug 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions
Are you sure that your configuration was still set to manual and not "never"? (there is a timeout bug in whoopsie-preferences which reset the condition to "never" if g-c-c is kept opened). I just tried with the -proposed version, generated a crash which can be reported (note as well that some crashes can't be reported under some condition, hence the "Continue"), and got Don't Send/Send. Marking as verified as I guess your issue is due to the above issue in -preferences (and I tested a lot of combinations) ^ ** Tags removed: verification-failed verification-failed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+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 1692353] Re: systemd-fsckd : useless CR displayed on console
Interesting, I was sure we upstreamed completely systemd-fsckd. Anyway, +1 for me, let me assign to xnox who is doing most of systemd uploads nowdays so that he attaches it to next upload. Many thanks! ** Changed in: systemd (Ubuntu) Assignee: Didier Roche (didrocks) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1692353 Title: systemd-fsckd : useless CR displayed on console Status in systemd package in Ubuntu: Triaged Bug description: Hello, My system is "Ubuntu 16.04.2 LTS" (grep DISTRIB_DESCRIPTION /etc/lsb- release). The systemd package is installed: $ dpkg -l | grep systemd > systemd 229-4ubuntu17 I noticed that approximately 15 seconds after the boot, a useless Carriage Return ('\r') is displayed on the console (/dev/console). This character interacts with the display of the user currently logued in on the console. This screws the current line, when users is pressing keys. After monitoring system activity, I found the culprit: /lib/systemd/system/systemd-fsckd.service To test, run: service systemd-fsckd stop# In case, it is still running. service systemd-fsckd start Go to the console, wait for approximately 15 seconds, and you see the cursor jumping from its current position to the beginning of the line. This is the BUG. Note: the console is not the X11 terminal (xterm, lxterminal, etc.) ; the console is the text tty reached with Control-Alt-F1. The systemd-fsckd.service starts the following daemon: /lib/systemd/systemd-fsckd This is the daemon which displays two useless '\r' characters. I went to: http://packages.ubuntu.com/xenial/systemd I downloaded: http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu10.debian.tar.xz The file debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch contains: +static int manager_write_console(Manager *m, const char *message) { [...] +if (message) { +fprintf(console, "\r%s\r%n", message, &l); +if (m->clear < (size_t)l) +m->clear = (size_t)l; +} else { +fputc('\r', console); +for (j = 0; j < m->clear; j++) +fputc(' ', console); +fputc('\r', console); +} So, when no message was previously displayed, "m->clear" is still set to 0. Then, when the program ends it calls: +/* clear last line */ +manager_write_console(m, NULL); However, in the "else" above, two '\r' characters are displayed, surrounding no space characters. So, when no message was previously displayed, there is nothing to clear, so no '\r' character to display. A trivial patch is attached. It is untested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1692353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Update: We have made sofar couple of discoveries, thanks to Petr Jediny. We suspected OpenSSL incompatibility in the OS, so as the PEAP is creating underlying TLS tunnel for auth and we see an error in wpa_supplicant regarding TLS negotiation (hello). tl;dr - Cypher set of Ubuntu bionic do not match (pass/negotiate) ciphers on our appliance/radius (We uses Aruba appliances, the firmware is not up to date with latest security standards; Aruba is working last three months on an update (obviously without pressure)). --- The radius/server or Aruba is accepting TLS_RSA_WITH_3DES_EDE_CBC_SHA The mentioned cipher suite is mandated by https://tools.ietf.org/html/rfc5216#section-2.4, but the TLS_RSA_WITH_AES_128_CBC_SHA should be supported too It looks like the radius server is not accepting any of these suggested by ubuntu bionic wpa_supplicant: Cipher Suites (28 suites) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f) Cipher Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9) Cipher Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8) Cipher Suite: TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xccaa) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x006b) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x0067) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d) Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff) TLS_RSA_WITH_AES_128_CBC_SHA is mentioned. We think the issue directly relates to remove 3DES from Bionic: openssl ciphers -V '3DES' Error in cipher list 13040823744:error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match:../ssl/ssl_lib.c:2129: --- Note similar issue was discovered on Fedora as well and has this workaround: https://www.systutorials.com/docs/linux/man/8-update-crypto-policies/ and set "LEGACY" crypto policy $ update-crypto-policies --set LEGACY --- I suggest keeping the bug open for a while, just for case somebody will come with a workaround. In a long-term this is not the problem of the Ubuntu or gnome, but the list of supported ciphers Ubuntu Bionic vs. HW appliances you connect to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4
[Touch-packages] [Bug 1783479] Re: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus 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/1783479 Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped Status in console-setup package in Ubuntu: New Bug description: I fixed my many random crashes by adding this to the grub menu: intel_idle.max_cstate=1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 24 18:35:35 2018 DuplicateSignature: package:console-setup:1.178ubuntu2.3 Setting up console-setup (1.178ubuntu2.3) ... update-initramfs: deferring update (trigger activated) dpkg: error processing package console-setup (--configure): installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped ErrorMessage: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-07-20 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped 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/1783479/+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 1783479] [NEW] package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error
Public bug reported: I fixed my many random crashes by adding this to the grub menu: intel_idle.max_cstate=1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 24 18:35:35 2018 DuplicateSignature: package:console-setup:1.178ubuntu2.3 Setting up console-setup (1.178ubuntu2.3) ... update-initramfs: deferring update (trigger activated) dpkg: error processing package console-setup (--configure): installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped ErrorMessage: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-07-20 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped 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/1783479 Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped Status in console-setup package in Ubuntu: New Bug description: I fixed my many random crashes by adding this to the grub menu: intel_idle.max_cstate=1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 24 18:35:35 2018 DuplicateSignature: package:console-setup:1.178ubuntu2.3 Setting up console-setup (1.178ubuntu2.3) ... update-initramfs: deferring update (trigger activated) dpkg: error processing package console-setup (--configure): installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped ErrorMessage: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-07-20 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped 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/1783479/+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 1769386] Re: Cable network does not get recognized anymore, wifi works
@6 for me its not related to suspend..it just has stopped working all the time, even after reboots so not related your bug? -- 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/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+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 1778844] Comment bridged from LTC Bugzilla
--- Comment From hbath...@in.ibm.com 2018-07-25 01:28 EDT--- (In reply to comment #34) > Created attachment 128858 [details] > sosreport_moduels=set > > Attached sosreport when MODULES=set used Cascardo, is the sosreport no good? Thanks Hari -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Triaged Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 0e4f79d56818 [
[Touch-packages] [Bug 1754106] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)
[Expired for procps (Ubuntu) because there has been no activity for 60 days.] ** Changed in: procps (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1754106 Title: E: Sub-process /usr/bin/dpkg returned an error code (1) Status in procps package in Ubuntu: Expired Bug description: after sudo apt-get install -f update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides insserv: There is a loop between service plymouth and urandom if started insserv: loop involving service urandom at depth 4 insserv: loop involving service hwclock at depth 3 insserv: There is a loop between service vpnagentd_init and udev if started insserv: loop involving service udev at depth 1 insserv: There is a loop at service vpnagentd_init if started insserv: There is a loop at service plymouth if started insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: Starting vpnagentd_init depends on plymouth and therefore on system facility `$all' which can not be true! insserv: St
[Touch-packages] [Bug 1773009] Re: Xorg freeze
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1773009 Title: Xorg freeze Status in xorg package in Ubuntu: Expired Bug description: I am using the Thunderbolt port on my Lenovo P50, driving 2 Samsung 4k monitors with DisplayPort. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 23 13:06:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-20-generic, x86_64: installed nvidia, 390.48, 4.15.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230] InstallationDate: Installed on 2018-05-20 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20ENCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=302a2c3a-904a-4171-b934-6df4162e0e1f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET75W (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ENCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET75W(1.48):bd12/13/2017:svnLENOVO:pn20ENCTO1WW:pvrThinkPadP50:rvnLENOVO:rn20ENCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20ENCTO1WW dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773009/+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 1758087] Re: pgrep -f fails for long command lines
[Expired for procps (Ubuntu) because there has been no activity for 60 days.] ** Changed in: procps (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1758087 Title: pgrep -f fails for long command lines Status in procps package in Ubuntu: Expired Bug description: If a command line is really long and the search term is toward the end of it, pgrep -f fails to find the process. Experimentally, it appears that the magic number is about 4084. The script below reproduces the problem. If the command line is short, pgrep -f reports both a sleep and a bash process. If the line is too long, pgrep -f only reports the sleep process. # pgrep -f fails if >= 4063, succeeds if < 4063 stringLength=4063 reallyLongString=$(cat /dev/urandom | tr -cd '[:alnum:]' | head -c $stringLength) bash -c "echo $reallyLongString > /dev/null ; sleep 999" 2> /dev/null& pid=$! sleep 1 echo no -f: pgrep -l sleep echo with -f: pgrep -fl sleep pkill sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1758087/+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 1769386] Re: Cable network does not get recognized anymore, wifi works
Same as LP: #1779817? -- 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/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+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 1782709] Re: Updating systemd kills network on bionic
Today, just another "apt-get upgrade": root@samson:~# apt-get upgrade Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig Die folgenden Pakete werden aktualisiert (Upgrade): base-files console-setup console-setup-linux grub-common grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common keyboard-configuration libnss-systemd libpam-systemd libperl5.26 libsystemd0 libudev1 mdadm perl perl-base perl-modules-5.26 python3-cryptography python3-software-properties python3-update-manager screen snapd software-properties-common systemd systemd-sysv udev unattended-upgrades update-manager-core 29 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. Es müssen 30,9 MB an Archiven heruntergeladen werden. Nach dieser Operation werden 176 kB Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] Holen:1 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 base-files amd64 10.1ubuntu2.1 [58,0 kB] Holen:2 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libperl5.26 amd64 5.26.1-6ubuntu0.2 [3.531 kB] Holen:3 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 perl amd64 5.26.1-6ubuntu0.2 [201 kB] Holen:4 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 perl-base amd64 5.26.1-6ubuntu0.2 [1.390 kB] Holen:5 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 perl-modules-5.26 all 5.26.1-6ubuntu0.2 [2.762 kB] Holen:6 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.3 [105 kB] Holen:7 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.3 [204 kB] Holen:8 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.3 [108 kB] Holen:9 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.3 [2.896 kB] Holen:10 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 udev amd64 237-3ubuntu10.3 [1.100 kB] Holen:11 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libudev1 amd64 237-3ubuntu10.3 [53,8 kB] Holen:12 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd-sysv amd64 237-3ubuntu10.3 [11,7 kB] Holen:13 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 console-setup-linux all 1.178ubuntu2.3 [982 kB] Holen:14 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 console-setup all 1.178ubuntu2.3 [105 kB] Holen:15 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 keyboard-configuration all 1.178ubuntu2.3 [372 kB] Holen:16 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-update-manager all 1:18.04.11.4 [34,1 kB] Holen:17 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 update-manager-core all 1:18.04.11.4 [8.500 B] Holen:18 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 grub-efi-amd64 amd64 2.02-2ubuntu8.2 [46,8 kB] Holen:19 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 grub2-common amd64 2.02-2ubuntu8.2 [531 kB] Holen:20 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 grub-efi-amd64-signed amd64 1.93.3+2.02-2ubuntu8.2 [297 kB] Holen:21 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 grub-efi-amd64-bin amd64 2.02-2ubuntu8.2 [654 kB] Holen:22 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 grub-common amd64 2.02-2ubuntu8.2 [1.771 kB] Holen:23 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 mdadm amd64 4.1~rc1-3~ubuntu18.04.1 [416 kB] Holen:24 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-cryptography amd64 2.1.4-1ubuntu1.2 [221 kB] Holen:25 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 software-properties-common all 0.96.24.32.4 [9.916 B] Holen:26 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-software-properties all 0.96.24.32.4 [22,3 kB] Holen:27 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 screen amd64 4.6.2-1ubuntu1 [564 kB] Holen:28 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 snapd amd64 2.34.2+18.04 [12,4 MB] Holen:29 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 unattended-upgrades all 1.1ubuntu1.18.04.5 [38,1 kB] Es wurden 30,9 MB in 5 s geholt (5.867 kB/s). Vorkonfiguration der Pakete ... (Lese Datenbank ... 67116 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../base-files_10.1ubuntu2.1_amd64.deb ... Warning: Stopping motd-news.service, but it can still be activated by: motd-news.timer Entpacken von base-files (10.1ubuntu2.1) über (10.1ubuntu2) ... base-files (10.1ubuntu2.1) wird eingerichtet ... Neue Version der Konfigurationsdatei /etc/issue wird installiert ... Neue Version der Konfigurationsdatei /etc/issue.net wird installiert ... Neue Version der Konfiguration
[Touch-packages] [Bug 1783462] Re: package libudev1:i386 237-3ubuntu10.3 failed to install/upgrade: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different
** Tags removed: need-duplicate-check -- 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/1783462 Title: package libudev1:i386 237-3ubuntu10.3 failed to install/upgrade: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) Status in systemd package in Ubuntu: New Bug description: i just did the automatic update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libudev1:i386 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 21:29:26 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libudev1:i386:237-3ubuntu10.3 Unpacking libudev1:i386 (237-3ubuntu10.3) over (237-3ubuntu10.3) ... dpkg: error processing package libudev1:amd64 (--configure): package libudev1:amd64 237-3ubuntu10.2 cannot be configured because libudev1:i386 is at a different version (237-3ubuntu10.3) ErrorMessage: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) InstallationDate: Installed on 2018-07-16 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package libudev1:i386 237-3ubuntu10.3 failed to install/upgrade: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783462/+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 1783462] [NEW] package libudev1:i386 237-3ubuntu10.3 failed to install/upgrade: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a differen
Public bug reported: i just did the automatic update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libudev1:i386 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 21:29:26 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libudev1:i386:237-3ubuntu10.3 Unpacking libudev1:i386 (237-3ubuntu10.3) over (237-3ubuntu10.3) ... dpkg: error processing package libudev1:amd64 (--configure): package libudev1:amd64 237-3ubuntu10.2 cannot be configured because libudev1:i386 is at a different version (237-3ubuntu10.3) ErrorMessage: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) InstallationDate: Installed on 2018-07-16 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package libudev1:i386 237-3ubuntu10.3 failed to install/upgrade: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- 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/1783462 Title: package libudev1:i386 237-3ubuntu10.3 failed to install/upgrade: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) Status in systemd package in Ubuntu: New Bug description: i just did the automatic update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libudev1:i386 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 21:29:26 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libudev1:i386:237-3ubuntu10.3 Unpacking libudev1:i386 (237-3ubuntu10.3) over (237-3ubuntu10.3) ... dpkg: error processing package libudev1:amd64 (--configure): package libudev1:amd64 237-3ubuntu10.2 cannot be configured because libudev1:i386 is at a different version (237-3ubuntu10.3) ErrorMessage: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) InstallationDate: Installed on 2018-07-16 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: systemd Title: package libudev1:i386 237-3ubuntu10.3 failed to install/upgrade: package libudev1:i386 237-3ubuntu10.3 cannot be configured because libudev1:amd64 is at a different version (237-3ubuntu10.2) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783462/+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 1769443] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769443 Title: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version
** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769443 Title: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Re-opening this bug as we had to revert the fix, because it was causing an installer regression: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1783326 That said, I think the "run it sometimes, but not always" fix was probably naive at best. The only two options that seem to make sense for fixing this properly are: 1) Make GNOME stop writing things to that file that console-setup doesn't understand, or 2) Make console-setup understand the things GNOME writes to that file. The second option is certainly the more appealing of the two, but it's clearly not going to happen before the point release in two days. ** Changed in: console-setup (Ubuntu Bionic) Status: Fix Released => Confirmed ** Changed in: console-setup (Ubuntu) Status: Fix Released => 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1783453] [NEW] gnome-twitch crashes upon attempting to open any stream
Public bug reported: The Twitch API has changed to disallow loading streams over HTTP. This causes gnome-twitch to crash whenever one tries to open any stream. The issue was tracked on the gnome-twitch github page ( https://github.com/vinszent/gnome-twitch/issues/356 ), a fix was written and merged ( https://github.com/vinszent/gnome-twitch/pull/357 ), and gnome-twitch release 0.4.2 includes the fix. Therefore, to restore the functionality of the package, the repository needs to be updated to 0.4.2, since 0.4.1 has been rendered useless by the API change. Release: Ubuntu 18.04.1 LTS gnome-twitch version: 0.4.1-2 Expected behaviour: stream opens and plays after a channel is selected. Actual behaviour: gnome-twitch says that no backend is installed. After clicking one one of the options in the resulting dialog box, gnome-twitch crashes with the message Error getting stream access token for channel 'lirik' because: Received unsuccessful response from url 'http://api.twitch.tv/api/channels/lirik/access_token' with code '400' and body '{"error":"Bad Request","status":400,"message":"Requests must be made over SSL"}' or similar. ** Affects: gnome-twitch (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Package changed: openssh (Ubuntu) => gnome-twitch (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1783453 Title: gnome-twitch crashes upon attempting to open any stream Status in gnome-twitch package in Ubuntu: New Bug description: The Twitch API has changed to disallow loading streams over HTTP. This causes gnome-twitch to crash whenever one tries to open any stream. The issue was tracked on the gnome-twitch github page ( https://github.com/vinszent/gnome-twitch/issues/356 ), a fix was written and merged ( https://github.com/vinszent/gnome-twitch/pull/357 ), and gnome-twitch release 0.4.2 includes the fix. Therefore, to restore the functionality of the package, the repository needs to be updated to 0.4.2, since 0.4.1 has been rendered useless by the API change. Release: Ubuntu 18.04.1 LTS gnome-twitch version: 0.4.1-2 Expected behaviour: stream opens and plays after a channel is selected. Actual behaviour: gnome-twitch says that no backend is installed. After clicking one one of the options in the resulting dialog box, gnome-twitch crashes with the message Error getting stream access token for channel 'lirik' because: Received unsuccessful response from url 'http://api.twitch.tv/api/channels/lirik/access_token' with code '400' and body '{"error":"Bad Request","status":400,"message":"Requests must be made over SSL"}' or similar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-twitch/+bug/1783453/+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 1783445] [NEW] Gdebi-gtk does not work on ubuntu 18.04
Public bug reported: The gdebi-gtk program does not work when used on the desktop. But being called by the terminal, it works normally. As in the ubuntu version 18.04 it does not have the gksu package, I tried adding the "admin: //" method in the "Exec =" field of the desktop entry. What did not work and the bug still remains! ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1783445 Title: Gdebi-gtk does not work on ubuntu 18.04 Status in gdebi package in Ubuntu: New Bug description: The gdebi-gtk program does not work when used on the desktop. But being called by the terminal, it works normally. As in the ubuntu version 18.04 it does not have the gksu package, I tried adding the "admin: //" method in the "Exec =" field of the desktop entry. What did not work and the bug still remains! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1783445/+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 1760910] Re: Gdebi crash in Ubuntu Studio 18.04
This new "admin: //" method did not work being changed in desktop entry. The bug still remains in gdebi-gtk. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1760910 Title: Gdebi crash in Ubuntu Studio 18.04 Status in gdebi package in Ubuntu: Confirmed Bug description: Gdebi opens normal, but when you click install package, it closes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10 Uname: Linux 4.15.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 3 12:31:17 2018 InstallationDate: Installed on 2018-03-29 (4 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180328) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1760910/+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 1783441] [NEW] [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all
Public bug reported: under sound panel output there is only a "dummy" profile and another is not possible to add. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 24 19:46:33 2018 InstallationDate: Installed on 2018-07-22 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio Symptom_Jack: Grey Line Out, Rear Symptom_Type: No sound at all Title: [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1783441 Title: [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: under sound panel output there is only a "dummy" profile and another is not possible to add. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 24 19:46:33 2018 InstallationDate: Installed on 2018-07-22 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joseph17719 F pulseaudio Symptom_Jack: Grey Line Out, Rear Symptom_Type: No sound at all Title: [Inspiron 530, Realtek ALC888, Grey Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0RY007 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0RY007:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1783441/+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 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-failed verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+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 1770248] Re: console-setup fails intermittently due to a missing file in /tmp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu Xenial) 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/1770248 Title: console-setup fails intermittently due to a missing file in /tmp Status in console-setup package in Ubuntu: Confirmed Status in console-setup source package in Xenial: Confirmed Bug description: In our testing of cloud images, we intermittently see an error along the lines of: May 09 17:59:27 ubuntu setupcon[476]: /bin/setupcon: 809: /bin/setupcon: cannot open /tmp/tmpkbd.7L3GEu: No such file This only happens from time-to-time which suggests that it's a race condition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: console-setup 1.108ubuntu15.3 ProcVersionSignature: User Name 4.13.0-1015.19-gcp 4.13.16 Uname: Linux 4.13.0-1015-gcp x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed May 9 19:29:50 2018 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1770248/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
Cool, thanks Andreas! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Triaged Bug description: Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate permissions to the slapd apparmor profile? I'm getting the following kinds of errors: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1783183/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Same. Except has now progressed to restart not providing workaround. On 25 July 2018 at 03:18, tom <1583...@bugs.launchpad.net> wrote: > Confirm 18.04 / 4.15 still happening for me too :*( > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1583801 > > Title: > No sound via headphones (headset) when Ubuntu boots with them plugged > in > > Status in PulseAudio: > Confirmed > Status in alsa-driver package in Ubuntu: > Confirmed > Status in pulseaudio package in Ubuntu: > Confirmed > > Bug description: > The bug is twofold, first when computer boots if the headset > (headphones with built-in mic, one audio jack) is plugged in, then > there is no sound (via headphones or otherwise). If you plug > headphones out and back in, then it usually works as expected. > > The second scenario is the same, except that plugging out and back in > again doesn't help. In that case, I just restart the laptop, then plug > them back in again and it works. > > In all cases, microphone works. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: crunch 3248 F pulseaudio > CurrentDesktop: Unity > Date: Thu May 19 22:13:20 2016 > InstallationDate: Installed on 2016-05-07 (12 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > 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/controlC0: crunch 3248 F pulseaudio > Symptom_Jack: Black Headphone Out, Left > Symptom_Type: No sound at all > Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No > sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/07/2016 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 01.02.00 > dmi.board.name: 0N7TVV > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.: > pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: > dmi.product.name: XPS 15 9550 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/pulseaudio/+bug/1583801/+subscriptions > -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV
[Touch-packages] [Bug 1783409] Re: package console-setup 1.178ubuntu2.2 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128
** 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/1783409 Title: package console-setup 1.178ubuntu2.2 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 Status in console-setup package in Ubuntu: New Bug description: se detuvo el instalador ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:01:40 2018 ErrorMessage: installed console-setup package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2018-07-23 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.2 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to bionic on 2018-07-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783409/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
I didn't know about default_client_keytab_name. That's definitely handy, so no more k5start needed! Thanks for your explanation, it makes sense. I'll give it a whirl, because I'll need to add testing instructions to the change that will be proposed. ** Changed in: openldap (Ubuntu) Status: Incomplete => Triaged ** Changed in: openldap (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Triaged Bug description: Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate permissions to the slapd apparmor profile? I'm getting the following kinds of errors: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1783183/+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 1783409] [NEW] package console-setup 1.178ubuntu2.2 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128
Public bug reported: se detuvo el instalador ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:01:40 2018 ErrorMessage: installed console-setup package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2018-07-23 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.2 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to bionic on 2018-07-23 (1 days ago) ** 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/1783409 Title: package console-setup 1.178ubuntu2.2 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 Status in console-setup package in Ubuntu: New Bug description: se detuvo el instalador ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:01:40 2018 ErrorMessage: installed console-setup package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2018-07-23 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.2 failed to install/upgrade: installed console-setup package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to bionic on 2018-07-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783409/+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 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions
I tried verifying this SRU today using apport version 2.20.9-0ubuntu7.3 from bionic-proposed. I was able to verify the first part of the test case, that a "Remember this in the future" option appeared when the privacy option was set to auto (the default). However, when I set the privacy option, "Problem Reporting", to Manual the crash report dialog just said "If you notice further problems, try restarting the computer." and there was no "Don't Send" button only a "Continue" one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+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 1776475] Re: Unlocking existing session often requires several attempts.
Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated. Details below. Bug just happened again on unlocking session (versus switching users). I compared the output of journalctl. ## Around unlock time: nothing to see Around unlock time, journalctl only shows lightdm cleanup activity. Then, only when bug happens, lightdm starts again the whole sequence : systemd[somepid]: Starting User Manager for UID 110... systemd-logind[749]: New session c9 of user lightdm. systemd[somepid]: Started Session c9 of user lightdm. ... ## Around lock time: same correlation between log order and bug occurrence Again Indeed, bug happens when log is in this order: at-spi-bus-launcher[25560]: dbus-daemon[25565]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") at-spi-bus-launcher[25560]: dbus-daemon[25565]: Successfully activated service 'org.a11y.atspi.Registry' at-spi-bus-launcher[25560]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry dbus-daemon[25559]: [session uid=110 pid=25559] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") and things go smoothly when log is in this order: at-spi-bus-launcher[15685]: dbus-daemon[15690]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") dbus-daemon[15684]: [session uid=110 pid=15684] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") at-spi-bus-launcher[15685]: dbus-daemon[15690]: Successfully activated service 'org.a11y.atspi.Registry' at-spi-bus-launcher[15685]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
I will try to get the point releases out today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Status in apparmor source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
Just to provide some more background, the specific scenarios in my case are syncrepl and a chain overlay. I have lines like this in slapd.conf: syncrepl rid=1 provider=ldap://providerhost starttls=yes bindmethod=sasl saslmech=GSSAPI and this: overlay chain chain-uri ldap://providerhost chain-tls start chain-idassert-bind mode=none starttls=yes bindmethod=sasl saslmech=GSSAPI -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Incomplete Bug description: Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate permissions to the slapd apparmor profile? I'm getting the following kinds of errors: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1783183/+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 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
The client.keytab path is standard functionality provided by libkrb5.so in Ubuntu 18.04. Here is the relevant documentation: http://manpages.ubuntu.com/manpages/bionic/man5/krb5.conf.5.html default_client_keytab_name This relation specifies the name of the default keytab for obtaining client credentials. The default is FILE:/etc/krb5/user/%{euid}/client.keytab.This relation is subject to parameter expansion (see below). New in release 1.11. It gets invoked by slapd when GSSAPI is specified as the sasl mechanism (e.g. with syncrepl). This was added as a feature to libkrb5 to streamline the process of automated authentication, so that people don't have to set up cron jobs to periodically run kinit. Regarding /tmp/krb5cc_*, that is the standard location for the credential cache file created by the kinit process. In this case, the equivalent of "kinit -k /etc/krb5/user/389/client.keytab" is done by slapd, leading to /tmp/krb5cc_389 being created. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Incomplete Bug description: Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate permissions to the slapd apparmor profile? I'm getting the following kinds of errors: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1783183/+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 1782709] Re: Updating systemd kills network on bionic
Do you have a way to reproduce this issue, or was it a one time event? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+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 1782893] Re: Bluetooth not working on Dell XPS 15
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1782893 Title: Bluetooth not working on Dell XPS 15 Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04. expected behavior: in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices what is happening: in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off some relevant output: $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 005: ID 0c45:6713 Microdia Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [3.905518] Bluetooth: Core ver 2.22 [3.905532] Bluetooth: HCI device and connection manager initialized [3.905534] Bluetooth: HCI socket layer initialized [3.905536] Bluetooth: L2CAP socket layer initialized [3.905539] Bluetooth: SCO socket layer initialized [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [3.857792] ath10k_pci :02:00.0: Direct firmware load for ath10k/pre-cal-pci-:02:00.0.bin failed with error -2 [3.857799] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [3.860582] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: am 5501 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582 InstallationDate: Installed on 2017-10-23 (272 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+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 1783328] Re: The option to select LTS notifications should be masked in non-LTS versions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1783328 Title: The option to select LTS notifications should be masked in non-LTS versions Status in software-properties package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I have been bitten by _not_ knowing that selecting "Notify me of a new Ubuntu version: For long-term support versions" in a non-LTS(17.10) software-properties-gtk dialog box would simply silently fail to inform users that they are no longer receiving updates to their Ubuntu installs. Please mask or hide the option to select "For long-term support versions" if the currently running version is a non-LTS version(grep or awk the /etc/os-release file or some-such for the LTS string). It is non-intuitive to see this option as available to select and not receive warning of its hazards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.21 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu Date: Tue Jul 24 07:30:11 2018 InstallationDate: Installed on 2018-05-21 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2018-05-24T11:23:48.670462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1783328/+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 1783328] Re: The option to select LTS notifications should be masked in non-LTS versions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1783328 Title: The option to select LTS notifications should be masked in non-LTS versions Status in software-properties package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: I have been bitten by _not_ knowing that selecting "Notify me of a new Ubuntu version: For long-term support versions" in a non-LTS(17.10) software-properties-gtk dialog box would simply silently fail to inform users that they are no longer receiving updates to their Ubuntu installs. Please mask or hide the option to select "For long-term support versions" if the currently running version is a non-LTS version(grep or awk the /etc/os-release file or some-such for the LTS string). It is non-intuitive to see this option as available to select and not receive warning of its hazards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.21 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu Date: Tue Jul 24 07:30:11 2018 InstallationDate: Installed on 2018-05-21 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2018-05-24T11:23:48.670462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1783328/+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 1776475] Re: Unlocking existing session often requires several attempts.
** Attachment added: "Example log when things fail (bug happens)." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+attachment/5167261/+files/2018y07m24d-16h34m12s_activite_repro_1776475_je_passe_sur_session_stephane_avec_export_xdg_seat_path__org_freedesktop_displaymanager_seat0___dm_tool_switch_to_user_stephaneexit.timestamped.log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1776475] Re: Unlocking existing session often requires several attempts.
In order to investigate this bug, I started to write down each time I switch user and whether it works. The time information allowed to obtain time-bounded log extracts that focus on relevant parts using journalctl --since ... --until ... . After 3 "work" and one "fail" case, I observed a correlation, which might or might not be relevant. ## Logs when no bug, things work The following log sequence happens all 3 times things work okay: 2018-07-24T13:00:38.327651+0200 n551jk systemd[16387]: Startup finished in 26ms. 2018-07-24T13:00:38.327693+0200 n551jk systemd[1]: Started User Manager for UID 110. 2018-07-24T13:00:38.360247+0200 n551jk systemd[16387]: Started D-Bus User Message Bus. 2018-07-24T13:00:38.363237+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] AppArmor D-Bus mediation is enabled 2018-07-24T13:00:38.363739+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.364556+0200 n551jk systemd[16387]: Starting Accessibility services bus... 2018-07-24T13:00:38.368461+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Successfully activated service 'org.a11y.Bus' 2018-07-24T13:00:38.368546+0200 n551jk systemd[16387]: Started Accessibility services bus. 2018-07-24T13:00:38.371337+0200 n551jk at-spi-bus-launcher[16408]: dbus-daemon[16413]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.373982+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.374774+0200 n551jk at-spi-bus-launcher[16408]: dbus-daemon[16413]: Successfully activated service 'org.a11y.atspi.Registry' 2018-07-24T13:00:38.374918+0200 n551jk at-spi-bus-launcher[16408]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry 2018-07-24T13:00:38.375082+0200 n551jk systemd[16387]: Starting Virtual filesystem service... ## Logs when bug happens, things fail The bug happened once since I started to write down each operation, and it shows a difference: 2018-07-24T16:34:15.777621+0200 n551jk systemd[23296]: Startup finished in 23ms. 2018-07-24T16:34:15.777665+0200 n551jk systemd[1]: Started User Manager for UID 110. 2018-07-24T16:34:15.820108+0200 n551jk systemd[23296]: Started D-Bus User Message Bus. 2018-07-24T16:34:15.822959+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] AppArmor D-Bus mediation is enabled 2018-07-24T16:34:15.823499+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.824373+0200 n551jk systemd[23296]: Starting Accessibility services bus... 2018-07-24T16:34:15.828552+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Successfully activated service 'org.a11y.Bus' 2018-07-24T16:34:15.828659+0200 n551jk systemd[23296]: Started Accessibility services bus. 2018-07-24T16:34:15.831689+0200 n551jk at-spi-bus-launcher[23317]: dbus-daemon[23322]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.835154+0200 n551jk at-spi-bus-launcher[23317]: dbus-daemon[23322]: Successfully activated service 'org.a11y.atspi.Registry' 2018-07-24T16:34:15.835289+0200 n551jk at-spi-bus-launcher[23317]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry 2018-07-24T16:34:15.835578+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.836417+0200 n551jk systemd[23296]: Starting Virtual filesystem service... ## Difference between "work" and "fail" All 3 lines mentioning at-spi-bus-launcher come *before* : dbus-daemon ... Activating via systemd: service name='org.gtk.vfs.Daemon'. I don't know it this is relevant at this point in time. No other salient difference in logs. Logs attached. ** Attachment added: "Example log when things work." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+attachment/5167260/+files/2018y07m24d-12h42m24s_activite_je_passe_sur_session_stephane_avec_export_xdg_seat_path__org_freedesktop_displaymanager_seat0___dm_tool_switch_to_user_stephaneexit.timestamped.log.txt -- You received this bug notification because you are a member of
[Touch-packages] [Bug 1783183] Re: apparmor profile denied for kerberos client keytab and credential cache files
"/etc/krb5/user/389/client.keytab" feels like a local modification you made, to store keytab files somewhere under /etc/krb5. I suggest you add an apparmor exception in /etc/apparmor.d/local/usr.sbin.slapd. Unless I'm wrong and that directory is being used as a standard location by some package. Please let me know which is the case. As to the /tpm/krb5cc_389 file, can you elaborate on the scenario that led to this behavior? Why is slapd trying to read that ticket cache file? Maybe because it failed to read the keytab file? ** Changed in: openldap (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1783183 Title: apparmor profile denied for kerberos client keytab and credential cache files Status in openldap package in Ubuntu: Incomplete Bug description: Can we get /etc/krb5/** and /tmp/krb5cc_* added with the appropriate permissions to the slapd apparmor profile? I'm getting the following kinds of errors: apparmor="DENIED" operation="open" profile="/usr/sbin/slapd" name="/etc/krb5/user/389/client.keytab" pid=19080 comm="slapd" requested_mask="r" denied_mask="r" fsuid=389 ouid=389 apparmor="DENIED" operation="file_lock" profile="/usr/sbin/slapd" name="/tmp/krb5cc_389" pid=19080 comm="slapd" requested_mask="k" denied_mask="k" fsuid=389 ouid=389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1783183/+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 1783377] [NEW] systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers
Public bug reported: Ubuntu 18.04.1 / bionic Fresh install on a VM, was facing a bug when connecting to strongswan ikev2 vpn (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705) -> Updated from cosmic the required packages for the VPN that has the bug fixed (5.6.2-2): network-manager-strongswan: Installé : 1.4.4-1 Candidat : 1.4.4-1 Table de version : *** 1.4.4-1 300 300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status 1.4.2-2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages libcharon-extra-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libcharon-standard-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-extra-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-standard-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Before connecting the VPN, `systemd-resolve --status` shows : DNS Servers: 192.168.1.254 # my home box resolver After connecting : DNS Servers: 10.0.0.254# DNS resolver provided by the VPN server 192.168.1.254 # my home box resolver This seems OK, but the resolution fails as it is still using the local DNS : systemd-resolved[270]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. After issuing `systemctl reload-or-restart systemd-resolved.service`, everything seems fine. systemd-resolved[5651]: Got DNS stub UDP query packet for id 24298 systemd-resolved[5651]: Looking up RR for my.host.inside.vpn IN A. systemd-resolved[5651]: Switching to DNS server 10.0.0.254 for interface enp0s3. systemd-resolved[5651]: Cache miss for my.host.inside.vpn IN A systemd-resolved[5651]: Transaction 9273 for scope dns on enp0s3/*. systemd-resolved[5651]: Using feature level UDP+EDNS0 for transaction 9273. systemd-resolved[5651]: Using DNS server 10.0.0.254 for transaction 9273. I was hoping that `systemd-resolved` could find the new DNS without restarting its service after connecting to the VPN. Thanks for reading Best Regards, Vincet ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783377 Title: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers Status in systemd package in Ubuntu: New Bug description: Ubuntu 18.04.1 / bionic Fresh install on a VM, was facing a bug when connecting to strongswan ikev2 vpn (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705) -> Updated from cosmic the required packages for the VPN that has the bug fixed (5.6.2-2): network-manager-strongswan: Installé : 1.4.4-1 Candidat : 1.4.4-1 Table de version : *** 1.4.4-1 300 300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status 1.4.2-2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages libcharon-extra-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libcharon-standard-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-extra-plugins: Installé : 5.6.2-2ubuntu1
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
I ran into this running a `do-release-upgrade -d` on a xenial machine at $work. The upgrade failed partway through leaving the system in a partial upgrade state afaict; lsb-release -a reports 18.04, but the apt sources are still xenial. -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Incomplete Status in systemd source package in Bionic: Confirmed Status in systemd-shim source package in Bionic: Confirmed Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Confirm 18.04 / 4.15 still happening for me too :*( -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1771033] Re: [needs-packaging] python3-avahi is missing in Ubuntu/debian
** Changed in: avahi (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - [needs-packaging] python3-avahi is missing in Ubuntu/debian + [needs-packaging] python3-avahi is not available in Ubuntu/debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1771033 Title: [needs-packaging] python3-avahi is not available in Ubuntu/debian Status in avahi package in Ubuntu: Triaged Status in avahi package in Debian: New Bug description: Under Ubuntu 18.04 if you install the package Gajim the local account is permanently disabled because of missing dependencies. https://dev.gajim.org/gajim/gajim/issues/9125 The required package is python3-avahi The python3-avahi package is missing, apt-get is unable to find it. This is a vital feature for us, we use Gajim internally without internet, and this simply works, no adding accounts, no information or messages sent over the internet, it all works locally. I hope this package can be added, if this is the wrong place to file this bug I applologize. I don't have a lot of experience reporting bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1771033/+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 1783225] Re: lxd-client from xenial-backports won't upgrade
Ok, so good that this appears to unstick things. Tentatively re- assigning to apt as this feels like a resolver problem. I looked through the debug output again and it's really not obvious why apt came to the conclusion that it'd be preferable to switch from juju2 to juju1 over just upgrading lxd and lxd-client. I suspect it's got to do with the way apt handles archives that are set with the backports flag (can't remember the Release field for that) as we ran into similar issues when users tried to use "lxd/xenial- backports" rather than use the "-t xenial-backports" trick, but it's the first time we see such an issue AFTER the initial opt-in to backports. ** Package changed: lxd (Ubuntu) => apt (Ubuntu) -- 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/1783225 Title: lxd-client from xenial-backports won't upgrade Status in apt package in Ubuntu: New Bug description: root@malefic:~# apt dist-upgrade; apt-get -o debug::pkgproblemresolver=1 install lxd-client Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: lxd-client 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) lxd [ amd64 ] < 2.21-0ubuntu3~16.04.2 -> 3.0.1-0ubuntu1~16.04.4 > ( admin ) Broken lxd:amd64 Depends on liblxc1 [ amd64 ] < 2.0.8-0ubuntu1~16.04.2 | 3.0.1-0ubuntu1~16.04.1 > ( admin ) (>= 3.0.0~) Considering liblxc1:amd64 9 as a solution to lxd:amd64 4 Reinst Failed early because of liblxc1:amd64 Removing lxd:amd64 rather than change liblxc1:amd64 Investigating (0) juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) Broken juju-2.0:amd64 Depends on lxd [ amd64 ] < 2.21-0ubuntu3~16.04.2 -> 3.0.1-0ubuntu1~16.04.4 > ( admin ) Considering lxd:amd64 4 as a solution to juju-2.0:amd64 4 Removing juju-2.0:amd64 rather than change lxd:amd64 Investigating (0) python3-juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net ) Broken python3-juju-deployer:amd64 Depends on juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) Considering juju-2.0:amd64 4 as a solution to python3-juju-deployer:amd64 4 Broken python3-juju-deployer:amd64 Depends on juju-core [ amd64 ] < none -> 1.25.6-0ubuntu1.16.04.2 > ( universe/devel ) Considering juju-core:amd64 2 as a solution to python3-juju-deployer:amd64 4 Try Installing juju-core [ amd64 ] < none -> 1.25.6-0ubuntu1.16.04.2 > ( universe/devel ) before changing python3-juju-deployer:amd64 Or group remove for python3-juju-deployer:amd64 Investigating (0) juju [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) Broken juju:amd64 Depends on juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) (>= 1:2.4.0-0ubuntu1~16.04.1~juju1) Considering juju-2.0:amd64 4 as a solution to juju:amd64 -1 Removing juju:amd64 rather than change juju-2.0:amd64 Investigating (1) juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net ) Broken juju-deployer:amd64 Depends on python3-juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net ) Considering python3-juju-deployer:amd64 4 as a solution to juju-deployer:amd64 5 Added python3-juju-deployer:amd64 to the remove list Fixing juju-deployer:amd64 via keep of python3-juju-deployer:amd64 Done The following packages were automatically installed and are no longer required: ebtables xdelta3 Use 'apt autoremove' to remove them. The following additional packages will be installed: juju-1.25 juju-core Suggested packages: lxd The following packages will be REMOVED juju juju-2.0 lxd The following NEW packages will be installed juju-1.25 juju-core The following packages will be upgraded: lxd-client 1 to upgrade, 2 to newly install, 3 to remove and 0 not to upgrade. Need to get 39.5 MB of archives. After this operation, 54.8 MB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. root@malefic:~# Relevant sources.list entry: deb http://archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse More info: https://paste.ubuntu.com/p/HKnnMcwTyS/ No apt pinning in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1783225/+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.n
[Touch-packages] [Bug 1780767] Re: Some tests are flaky due to timeout
This bug was fixed in the package apport - 2.20.10-0ubuntu7 --- apport (2.20.10-0ubuntu7) cosmic; urgency=medium * tests/test_ui_gtk.py: Increase the timeout so that when the autopkgtest infrastructure is busy the tests should not fail. (LP: #1780767) -- Brian Murray Tue, 24 Jul 2018 08:03:49 -0700 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1780767 Title: Some tests are flaky due to timeout Status in apport package in Ubuntu: Fix Released Bug description: The autopkgtests are sometimes passing, sometimes stuck for more than 2h: http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64. It's blocking randomly on different tests. All tests that are stucked, implements closing a request via a timeout (and then, executing "run"). The bet is that the timeout is short enough (1s) so that, when autopkgtests infra is busy, time to execute the bash subcommand is taking more than a second, and so "dismissing" is ran before execution happens and the whole testsuite hangs. There are few instances of setting this timeout function: $ grep eout_add_sec test/* test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) Short term solution could be to increase the timeout. Long term would be to eliminate this potential race implementing cancelling differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+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 1164016] Re: restore type-ahead find
Unbelievable. Upgraded to Ubuntu 18.04 to find out about this crappy behaviour. Please fix it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
Blocking launching (in useful ways) Debian testing & sid containers on Ubuntu as well. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Status in apparmor source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1783225] [NEW] lxd-client from xenial-backports won't upgrade
You have been subscribed to a public bug: root@malefic:~# apt dist-upgrade; apt-get -o debug::pkgproblemresolver=1 install lxd-client Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: lxd-client 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) lxd [ amd64 ] < 2.21-0ubuntu3~16.04.2 -> 3.0.1-0ubuntu1~16.04.4 > ( admin ) Broken lxd:amd64 Depends on liblxc1 [ amd64 ] < 2.0.8-0ubuntu1~16.04.2 | 3.0.1-0ubuntu1~16.04.1 > ( admin ) (>= 3.0.0~) Considering liblxc1:amd64 9 as a solution to lxd:amd64 4 Reinst Failed early because of liblxc1:amd64 Removing lxd:amd64 rather than change liblxc1:amd64 Investigating (0) juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) Broken juju-2.0:amd64 Depends on lxd [ amd64 ] < 2.21-0ubuntu3~16.04.2 -> 3.0.1-0ubuntu1~16.04.4 > ( admin ) Considering lxd:amd64 4 as a solution to juju-2.0:amd64 4 Removing juju-2.0:amd64 rather than change lxd:amd64 Investigating (0) python3-juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net ) Broken python3-juju-deployer:amd64 Depends on juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) Considering juju-2.0:amd64 4 as a solution to python3-juju-deployer:amd64 4 Broken python3-juju-deployer:amd64 Depends on juju-core [ amd64 ] < none -> 1.25.6-0ubuntu1.16.04.2 > ( universe/devel ) Considering juju-core:amd64 2 as a solution to python3-juju-deployer:amd64 4 Try Installing juju-core [ amd64 ] < none -> 1.25.6-0ubuntu1.16.04.2 > ( universe/devel ) before changing python3-juju-deployer:amd64 Or group remove for python3-juju-deployer:amd64 Investigating (0) juju [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) Broken juju:amd64 Depends on juju-2.0 [ amd64 ] < 1:2.4.0-0ubuntu1~16.04.1~juju1 > ( devel ) (>= 1:2.4.0-0ubuntu1~16.04.1~juju1) Considering juju-2.0:amd64 4 as a solution to juju:amd64 -1 Removing juju:amd64 rather than change juju-2.0:amd64 Investigating (1) juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net ) Broken juju-deployer:amd64 Depends on python3-juju-deployer [ amd64 ] < 0.10.0~bzr208~60~ubuntu17.04.1~bzr210~61~ubuntu16.04.1 > ( net ) Considering python3-juju-deployer:amd64 4 as a solution to juju-deployer:amd64 5 Added python3-juju-deployer:amd64 to the remove list Fixing juju-deployer:amd64 via keep of python3-juju-deployer:amd64 Done The following packages were automatically installed and are no longer required: ebtables xdelta3 Use 'apt autoremove' to remove them. The following additional packages will be installed: juju-1.25 juju-core Suggested packages: lxd The following packages will be REMOVED juju juju-2.0 lxd The following NEW packages will be installed juju-1.25 juju-core The following packages will be upgraded: lxd-client 1 to upgrade, 2 to newly install, 3 to remove and 0 not to upgrade. Need to get 39.5 MB of archives. After this operation, 54.8 MB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. root@malefic:~# Relevant sources.list entry: deb http://archive.ubuntu.com/ubuntu/ xenial-backports main restricted universe multiverse More info: https://paste.ubuntu.com/p/HKnnMcwTyS/ No apt pinning in play. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- lxd-client from xenial-backports won't upgrade https://bugs.launchpad.net/bugs/1783225 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt 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 1575779] Re: hostnamectl fails under lxd unpriv container
*** This bug is a duplicate of bug 1780227 *** https://bugs.launchpad.net/bugs/1780227 Marked as duplicate of 1780227 even though this bug report predates it, simply because the newer bug report has more discussion about how to actually get this resolved. ** This bug has been marked a duplicate of bug 1780227 locking sockets broken due to missing AppArmor socket mediation patches -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1575779 Title: hostnamectl fails under lxd unpriv container Status in apparmor package in Ubuntu: Confirmed Bug description: 1. % lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2. % apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy lxd lxd: Installed: 2.0.0-0ubuntu4 Candidate: 2.0.0-0ubuntu4 Version table: *** 2.0.0-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 4. hostnamectl status hangs indefinitely On the host, there are some audit messages for each invocation of hostnamectl [411617.032274] audit: type=1400 audit(1461695563.731:100): apparmor="DENIED" operation="file_lock" profile="lxd- x1_" pid=17100 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none It's related to socket activation. One can workaround this by running systemd-hostnamed in the background first root@x1:~# /lib/systemd/systemd-hostnamed & [1] 2462 root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Apr 27 11:19:27 2016 InstallationDate: Installed on 2016-01-01 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
In preparation for an SRU, here is a minimal C testcase provided by Wolfgang Bumiller: ``` /* # apparmor_parser -r /etc/apparmor.d/bug-profile # (tested without the flags here as well btw.) profile bug-profile flags=(attach_disconnected,mediate_deleted) { network, file, unix, } # gcc this.c # ./a.out lock = 2 (Success) # aa-exec -p bug-profile ./a.out lock = 2 (Permission denied) kernel: audit: type=1400 audit(1530774919.510:93): apparmor="DENIED" operation="file_lock" profile="bug-profile" pid=21788 comm="a.out" family="unix" sock_type="dgram" protocol=0 addr=none */ #include #include #include #include #include #include int main(int argc, char **argv) { int sp[2]; if (socketpair(AF_UNIX, SOCK_DGRAM, 0, sp) != 0) { perror("socketpair"); exit(1); } int rc = flock(sp[0], LOCK_EX); printf("lock = %i (%m)\n"); close(sp[0]); close(sp[1]); return 0; } ``` Another very easy way to reproduce the issue is to run "hostnamectl status" inside a container which will hang as the systemd unit (socket activated) will fail to trigger. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Status in apparmor source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
We need to clarify whether the other bug really is a verification- failed. I don't think it actually fails, it's just an incomplete fix given that there's existing config that we can't easily change post- install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' Status in initramfs-tools package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Fix Committed Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in netplan.io source package in Bionic: Fix Released Status in nplan source package in Bionic: Invalid Bug description: [Impact] Netboot users with a remote filesystem over NFS (possibly over other networked filesystems). [Test cases] 1) Boot a system with its root filesystem over NFS. 2) Run 'sudo netplan apply' 3) Validate that the system remains responsive and keeps connectivity over the same IP address as it had. [Regression potential] This SRU changes network properties, and enforces that networkd does not release and re-request an IP address from DHCP when it is restarted. Environments relying on the IP release/renew behavior may find themselves staying on the previous IP address, which might negatively impact connectivity. Changes in connectivity on a system running netplan should be investigated as a potential regression from this SRU. Other regression possibilities would include failure to get a new IP address over time (usually seen as losing connectivity) or possible IP conflicts on a network. --- With a system booted on the network, with its remote root fs on NFS: Running 'netplan apply' restarts systemd-networkd, which releases the IP received from DHCP. With no IP (and and IP potentially changing), the NFS server can't be reached so the system hangs. 'netplan apply' or restarting systemd-networkd should not affect teh system, it should continue working normally despite "changing" network states, as long as the effective IP remains the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
Per discussion above: - Closing the kernel tasks - Raising priority on apparmor tasks to Critical (to match what kernel had) - Assigning to jjohansen as the AppArmor maintainer As we care about xenial, bionic and cosmic, we need point releases (or cherry-pick) for: - AppArmor 2.10 (2.10.95 in xenial) - AppArmor 2.12 (2.12 in bionic and cosmic) John: Any ETA for those two point releases or pointer to a commit which we could SRU on its own? For now our focus is obviously on getting this resolved in Ubuntu as soon as possible, since it's breaking a number of systemd services that are now (18.04) shipping with more confinement than in the past. The same issue is also currently preventing us from starting newer Fedora and Arch containers on Ubuntu. Our standard response so far has been to tell users to turn off AppArmor for those containers, but it's obviously not an answer we like to give (I'm sure you'll agree). ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Invalid ** Changed in: apparmor (Ubuntu) Status: New => Triaged ** Changed in: apparmor (Ubuntu Xenial) Status: New => Triaged ** Changed in: apparmor (Ubuntu Bionic) Status: New => Triaged ** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Critical => Undecided ** Changed in: linux (Ubuntu Xenial) Importance: High => Undecided ** Changed in: linux (Ubuntu Bionic) Importance: High => Undecided ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: apparmor (Ubuntu Xenial) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: apparmor (Ubuntu Bionic) Assignee: (unassigned) => John Johansen (jjohansen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in apparmor source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Status in apparmor source package in Bionic: Triaged Status in linux source package in Bionic: Invalid Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1692353] Re: systemd-fsckd : useless CR displayed on console
Hello, Thank you for your reply. Unfortunately, the bug is NOT in upstream systemd, but in a Ubuntu specific patch. A few things changed since last year: Systemd version is now 229-4ubuntu21.2. Its source is now at: http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu21.2.debian.tar.xz The bugged function manager_write_console() is still there inside: debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch The new patch is attached. This patch can be used to patch the Ubuntu specific patch. Thank you. ** Patch added: "Patch version 2 for systemd version 229-4ubuntu21.2" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1692353/+attachment/5167175/+files/patch_to_remove_useless_crV2.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1692353 Title: systemd-fsckd : useless CR displayed on console Status in systemd package in Ubuntu: Incomplete Bug description: Hello, My system is "Ubuntu 16.04.2 LTS" (grep DISTRIB_DESCRIPTION /etc/lsb- release). The systemd package is installed: $ dpkg -l | grep systemd > systemd 229-4ubuntu17 I noticed that approximately 15 seconds after the boot, a useless Carriage Return ('\r') is displayed on the console (/dev/console). This character interacts with the display of the user currently logued in on the console. This screws the current line, when users is pressing keys. After monitoring system activity, I found the culprit: /lib/systemd/system/systemd-fsckd.service To test, run: service systemd-fsckd stop# In case, it is still running. service systemd-fsckd start Go to the console, wait for approximately 15 seconds, and you see the cursor jumping from its current position to the beginning of the line. This is the BUG. Note: the console is not the X11 terminal (xterm, lxterminal, etc.) ; the console is the text tty reached with Control-Alt-F1. The systemd-fsckd.service starts the following daemon: /lib/systemd/systemd-fsckd This is the daemon which displays two useless '\r' characters. I went to: http://packages.ubuntu.com/xenial/systemd I downloaded: http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu10.debian.tar.xz The file debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch contains: +static int manager_write_console(Manager *m, const char *message) { [...] +if (message) { +fprintf(console, "\r%s\r%n", message, &l); +if (m->clear < (size_t)l) +m->clear = (size_t)l; +} else { +fputc('\r', console); +for (j = 0; j < m->clear; j++) +fputc(' ', console); +fputc('\r', console); +} So, when no message was previously displayed, "m->clear" is still set to 0. Then, when the program ends it calls: +/* clear last line */ +manager_write_console(m, NULL); However, in the "else" above, two '\r' characters are displayed, surrounding no space characters. So, when no message was previously displayed, there is nothing to clear, so no '\r' character to display. A trivial patch is attached. It is untested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1692353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783328] Re: The option to select LTS notifications should be masked in non-LTS versions
** Tags added: rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1783328 Title: The option to select LTS notifications should be masked in non-LTS versions Status in software-properties package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I have been bitten by _not_ knowing that selecting "Notify me of a new Ubuntu version: For long-term support versions" in a non-LTS(17.10) software-properties-gtk dialog box would simply silently fail to inform users that they are no longer receiving updates to their Ubuntu installs. Please mask or hide the option to select "For long-term support versions" if the currently running version is a non-LTS version(grep or awk the /etc/os-release file or some-such for the LTS string). It is non-intuitive to see this option as available to select and not receive warning of its hazards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.21 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu Date: Tue Jul 24 07:30:11 2018 InstallationDate: Installed on 2018-05-21 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2018-05-24T11:23:48.670462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1783328/+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 1575779] Re: hostnamectl fails under lxd unpriv container
** Changed in: apparmor (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1575779 Title: hostnamectl fails under lxd unpriv container Status in apparmor package in Ubuntu: Confirmed Bug description: 1. % lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2. % apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy lxd lxd: Installed: 2.0.0-0ubuntu4 Candidate: 2.0.0-0ubuntu4 Version table: *** 2.0.0-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 4. hostnamectl status hangs indefinitely On the host, there are some audit messages for each invocation of hostnamectl [411617.032274] audit: type=1400 audit(1461695563.731:100): apparmor="DENIED" operation="file_lock" profile="lxd- x1_" pid=17100 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none It's related to socket activation. One can workaround this by running systemd-hostnamed in the background first root@x1:~# /lib/systemd/systemd-hostnamed & [1] 2462 root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Apr 27 11:19:27 2016 InstallationDate: Installed on 2016-01-01 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Triaged Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1783328] Re: The option to select LTS notifications should be masked in non-LTS versions
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1783328 Title: The option to select LTS notifications should be masked in non-LTS versions Status in software-properties package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: I have been bitten by _not_ knowing that selecting "Notify me of a new Ubuntu version: For long-term support versions" in a non-LTS(17.10) software-properties-gtk dialog box would simply silently fail to inform users that they are no longer receiving updates to their Ubuntu installs. Please mask or hide the option to select "For long-term support versions" if the currently running version is a non-LTS version(grep or awk the /etc/os-release file or some-such for the LTS string). It is non-intuitive to see this option as available to select and not receive warning of its hazards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.21 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu Date: Tue Jul 24 07:30:11 2018 InstallationDate: Installed on 2018-05-21 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2018-05-24T11:23:48.670462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1783328/+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 1692353] Re: systemd-fsckd : useless CR displayed on console
Thanks for submitting this patch and sorry for the time to review it! The patch looks good to me, I would love though to get that directly upstream rather than us carrying a distro-patch for a small issue like this, do you mind doing a PR there? https://github.com/systemd/systemd/ ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1692353 Title: systemd-fsckd : useless CR displayed on console Status in systemd package in Ubuntu: Incomplete Bug description: Hello, My system is "Ubuntu 16.04.2 LTS" (grep DISTRIB_DESCRIPTION /etc/lsb- release). The systemd package is installed: $ dpkg -l | grep systemd > systemd 229-4ubuntu17 I noticed that approximately 15 seconds after the boot, a useless Carriage Return ('\r') is displayed on the console (/dev/console). This character interacts with the display of the user currently logued in on the console. This screws the current line, when users is pressing keys. After monitoring system activity, I found the culprit: /lib/systemd/system/systemd-fsckd.service To test, run: service systemd-fsckd stop# In case, it is still running. service systemd-fsckd start Go to the console, wait for approximately 15 seconds, and you see the cursor jumping from its current position to the beginning of the line. This is the BUG. Note: the console is not the X11 terminal (xterm, lxterminal, etc.) ; the console is the text tty reached with Control-Alt-F1. The systemd-fsckd.service starts the following daemon: /lib/systemd/systemd-fsckd This is the daemon which displays two useless '\r' characters. I went to: http://packages.ubuntu.com/xenial/systemd I downloaded: http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu10.debian.tar.xz The file debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch contains: +static int manager_write_console(Manager *m, const char *message) { [...] +if (message) { +fprintf(console, "\r%s\r%n", message, &l); +if (m->clear < (size_t)l) +m->clear = (size_t)l; +} else { +fputc('\r', console); +for (j = 0; j < m->clear; j++) +fputc(' ', console); +fputc('\r', console); +} So, when no message was previously displayed, "m->clear" is still set to 0. Then, when the program ends it calls: +/* clear last line */ +manager_write_console(m, NULL); However, in the "else" above, two '\r' characters are displayed, surrounding no space characters. So, when no message was previously displayed, there is nothing to clear, so no '\r' character to display. A trivial patch is attached. It is untested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1692353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769893] Re: CUPS Unauthorized when using Chrome browser in Ubuntu 18.04
** Summary changed: - CUPS Unauthorized when using Chrome browser + CUPS Unauthorized when using Chrome browser in Ubuntu 18.04 -- 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/1769893 Title: CUPS Unauthorized when using Chrome browser in Ubuntu 18.04 Status in cups package in Ubuntu: Confirmed Bug description: Using Chrome Version 66.0.3359.139 (Official Build) (64-bit) I am able to access and add a printer through Chrome by going to the page http://localhost:631/admin/login and I can add a printer fine. But I cannot add the printer if I go directly to http://localhost:631/admin and bypass the login. If I need to change any defaults of the printer through the same pages it gives me the "Unauthorized" and will not change anything. I can change it in Firefox and the printers control panel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 (Authentication failure) E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Tue May 8 07:18:47 2018 InstallationDate: Installed on 2018-05-05 (2 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for Deskjet_3520_series_75C0A7_: ipp://HP6C3BE575C0A7.local:631/ipp/print device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253 MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', '/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 biosdevname=0 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9N2GM-FIH(MS-7508) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7508 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
This affects all academic users that uses eduroam to connect to the internet. Please fix. Eduroam did work with ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm-glib/libnm-util library ii gir1.2-nm-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm library ii gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1 amd64GObject introspection data for libnm-gtk ii libnm-glib-vpn1:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib VPN shared library) ii libnm-glib4:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib shared library) ii libnm-gtk0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm-glib version) ii libnm-util2:amd64 1.8.4-1ubuntu4 amd64network management framework (shared library) ii libnm0:amd64 1.8.4-1ubuntu4 amd64GObject-based client library for NetworkManager ii libnma0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm version) ii libproxy1-plugin-networkmanager:amd64 0.4.15-0ubuntu1 amd64automatic proxy configuration management library (Network Manager plugin) ii network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 all NetworkManager configuration to enable connectivity checking ii strongswan-nm 5.6.1-2ubuntu1 amd64strongSwan plugin to interact with NetworkManager ii wpasupplicant 2:2.6-15ubuntu2 amd64client support for WPA and WPA2 (IEEE 802.11i) [/code] 3,4) Connection to open or WPA secured wifi works withou any issues. Connection to WPA2/PLEAP (without cert, just with username/password fails). Although wifi layer get's is associated the client (network-manager) possibly due to bug deauthenticate itself without establishing an IP connection. Connect to network. 5) Logs (syslog/kernel) Core moments: [code] Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9125] keyfile: update /etc/NetworkManager/system-connections/WiFi (82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi") Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed and ... Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9450] device (wlp4s0): Activation: (wifi) connection 'WiFi' has security, and secrets exist. No new secrets needed. Feb 12 09:19:0
[Touch-packages] [Bug 1783170] Re: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1783170 Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post- installation script subprocess returned error exit status 128 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: 789 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18 Uname: Linux 4.15.0-29-lowlatency x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Jul 21 18:28:51 2018 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to bionic on 2018-05-13 (71 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-20T23:44:01.023912 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1783170/+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 1769893] Re: CUPS Unauthorized when using Chrome browser
I solved using this command # usermod -aG lpadmin YourUserName -- 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/1769893 Title: CUPS Unauthorized when using Chrome browser Status in cups package in Ubuntu: Confirmed Bug description: Using Chrome Version 66.0.3359.139 (Official Build) (64-bit) I am able to access and add a printer through Chrome by going to the page http://localhost:631/admin/login and I can add a printer fine. But I cannot add the printer if I go directly to http://localhost:631/admin and bypass the login. If I need to change any defaults of the printer through the same pages it gives me the "Unauthorized" and will not change anything. I can change it in Firefox and the printers control panel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:00:07:44 -0600] Filter \"pstops\" not found. E [08/May/2018:07:01:45 -0600] [Client 20] pam_authenticate() returned 7 (Authentication failure) E [08/May/2018:07:02:01 -0600] [cups-deviced] PID 15052 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Tue May 8 07:18:47 2018 InstallationDate: Installed on 2018-05-05 (2 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for Deskjet_3520_series_75C0A7_: ipp://HP6C3BE575C0A7.local:631/ipp/print device for HP_Color_LaserJet_CP1518ni: socket://10.0.0.253 MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd', '/etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Deskjet_3520_series_75C0A7_.ppd: Permission denied grep: /etc/cups/ppd/HP_Color_LaserJet_CP1518ni.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5dae0d38-9bbe-48de-b110-62763c862892 ro nosplash net.ifnames=0 biosdevname=0 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9N2GM-FIH(MS-7508) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.8:bd09/30/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7508 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769893/+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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version
** Attachment added: "EVERY TIME IT SHOWS,,,BUT I HAVE INSTALLED ON MY COMPUTER" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+attachment/5167138/+files/Screenshot%20from%202018-07-24%2017-33-12.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769443 Title: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version
see i have installed on my computer, if i want to launch it, i have to go software centre what to do, very disgusting, ** Attachment added: "there is no option to set preffercences to receive files via blutooth,only network etc etc" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+attachment/5167139/+files/Screenshot%20from%202018-07-24%2017-34-09.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769443 Title: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
I still observe this bug in Cosmic with v4.17.0-5 kernel from cosmic- proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Triaged Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version
I have installed personal file sharing app from software,and launch it,,but there is no option to set prefferences to receive files via bluetooth,and every time i have to go in software in order to search this applicalion because when i search it on dash it always shows-sorry there is nothing that matches you search..its very arriting Im proving some screenshot.. ** Attachment added: "there is no option to set preffercences to receive files via blutooth" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+attachment/5167137/+files/Screenshot%20from%202018-07-24%2017-49-03.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769443 Title: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
Ah, I need 2.12.1 apparmor as well, which is not in the archive yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Triaged Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]
** Tags added: patch -- 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/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] Status in console-setup package in Ubuntu: New Bug description: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error
How long? Errors were encountered while processing: /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb /var/cache/apt/archives/kaccounts-providers_4%3a15.12.3-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Got this on clean Ubuntu Xenial 16.04 LTS (!!!) installation without any PPA. ** Tags removed: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Fix Released Status in Telepathy KDE: Fix Released Status in kaccounts-integration package in Ubuntu: Fix Committed Status in kaccounts-providers package in Ubuntu: Fix Committed Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: Fix Released Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) SRU information === [Impact] It's not possible to install KDE and Unity in co-existence because of several file conflicts: many files under /usr/share/accounts/{providers,services}/ are provided by both the package "kaccounts-providers" and packages build from the "account- plugins" source package, for example 'account-plugin-facebook'. [Test case] Install both kaccounts-providers and account-plugin-facebook: you'll get file conflicts for /usr/share/accounts/services/facebook-im.service and /usr/share/accounts/providers/facebook.provider. You might get other conflicts as well, but those are due to bug 1565772 (also nominated for SRU). [Regression potential] Minimal: the changed packages belong to the default KDE installation, and have already landed in Yakkety. Things appear to be working fine there: account creation is still possible under KDE, even after changing the file paths as per this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1778844] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2018-07-24 06:36 EDT--- (In reply to comment #36) > Can you run apport-collect -p linux 1778844 ? > > Thank you. > Cascardo. HI Cascardo, I have tried to collect , but it fails as below root@woo:~# apport-collect -p linux 1778844 ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out You can reset the credentials by removing the file "/root/.cache/apport/launchpad.credentials" root@woo:~# export http_proxy="http://10.33.11.31:3128"; root@woo:~# apport-collect -p linux 1778844 ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out You can reset the credentials by removing the file "/root/.cache/apport/launchpad.credentials" root@woo:~# Regards, Indira -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Triaged Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: D
[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
** Changed in: linux (Ubuntu) Importance: High => Critical ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in apparmor source package in Xenial: New Status in linux source package in Xenial: Triaged Status in apparmor source package in Bionic: New Status in linux source package in Bionic: Triaged Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+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 1783305] Re: apparmor DENIED when a systemd unit with DynamicUsers=yes is launched in a lxd container
*** This bug is a duplicate of bug 1780227 *** https://bugs.launchpad.net/bugs/1780227 ** This bug has been marked a duplicate of bug 1780227 locking sockets broken due to missing AppArmor socket mediation patches -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1783305 Title: apparmor DENIED when a systemd unit with DynamicUsers=yes is launched in a lxd container Status in apparmor package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: $ lxc launch images:debian/sid test-dynamicusers $ lxc exec test-dynamicusers bash $ systemd-run --unit=testdynamic -p DynamicUser=yes --uid=xnox /bin/true $ systemctl status testdynamic.service # systemctl status testdynamic.service ● testdynamic.service - /bin/true Loaded: loaded (/run/systemd/transient/testdynamic.service; transient) Transient: yes Active: failed (Result: exit-code) since Tue 2018-07-24 10:16:13 UTC; 6s ago Process: 470 ExecStart=/bin/true (code=exited, status=217/USER) Main PID: 470 (code=exited, status=217/USER) Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Forked /bin/true as 470 Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed dead -> running Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Job testdynamic.service/start finished, result=done Jul 24 10:16:13 systemd239 systemd[1]: Started /bin/true. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed to send unit change signal for testdynamic.service: Connection reset by peer Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Child 470 belongs to testdynamic.service. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Main process exited, code=exited, status=217/USER Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed with result 'exit-code'. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed running -> failed Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Unit entered failed state. and on the host side, in journal there is: Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:934): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:935): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:936): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:937): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:938): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:939): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:940): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:941): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" ope
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I can also confirm this bug is still very much present (and an annoying feature) in 18.04, under Xorg. Ctrl+C works as expected though. Alt+[Arrow keys] switches VTs. -- 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/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+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 1783305] Re: apparmor DENIED when a systemd unit with DynamicUsers=yes is launched in a lxd container
*** This bug is a duplicate of bug 1780227 *** https://bugs.launchpad.net/bugs/1780227 This is an AppArmor bug that I reported and which is tracked here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780227 So please close here in favor of that bug. Christian ** Changed in: lxd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1783305 Title: apparmor DENIED when a systemd unit with DynamicUsers=yes is launched in a lxd container Status in apparmor package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: $ lxc launch images:debian/sid test-dynamicusers $ lxc exec test-dynamicusers bash $ systemd-run --unit=testdynamic -p DynamicUser=yes --uid=xnox /bin/true $ systemctl status testdynamic.service # systemctl status testdynamic.service ● testdynamic.service - /bin/true Loaded: loaded (/run/systemd/transient/testdynamic.service; transient) Transient: yes Active: failed (Result: exit-code) since Tue 2018-07-24 10:16:13 UTC; 6s ago Process: 470 ExecStart=/bin/true (code=exited, status=217/USER) Main PID: 470 (code=exited, status=217/USER) Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Forked /bin/true as 470 Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed dead -> running Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Job testdynamic.service/start finished, result=done Jul 24 10:16:13 systemd239 systemd[1]: Started /bin/true. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed to send unit change signal for testdynamic.service: Connection reset by peer Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Child 470 belongs to testdynamic.service. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Main process exited, code=exited, status=217/USER Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed with result 'exit-code'. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed running -> failed Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Unit entered failed state. and on the host side, in journal there is: Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:934): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:935): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:936): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:937): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:938): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:939): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:940): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:941): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="fil
[Touch-packages] [Bug 1783298] [NEW] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Public bug reported: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS /hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks,
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
** Tags removed: oneiric ** Tags added: xenial ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/958661 Title: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings Status in bluez package in Ubuntu: Confirmed Bug description: I often send image files via bluetooth from my android phone to my ubuntu PC. It worked fine until yesterday, but now I systematically get "the remote bluetooth device rejected the request". Nothing has changed in the way I transfer files and I'm trying from the very same phone. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-16-generic 3.0.0-16.29 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo 32650 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49' Mixer name : 'Realtek ALC660-VD' Components : 'HDA:10ec0660,1043,0011 HDA:10573055,10431316,00100700' Controls : 25 Simple ctrls : 16 Date: Sun Mar 18 17:55:36 2012 HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-16-generic N/A linux-backports-modules-3.0.0-16-generic N/A linux-firmware1.60.1 SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago) UserAsoundrc: pcm.!default { type pulse } ctl.!default { type pulse } pcm.pulse { type pulse } ctl.pulse { type pulse } dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn 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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+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 1458204] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Confirmed Status in update-notifier source package in Artful: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 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.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1701222] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Won't Fix -- 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/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Status in linux source package in Artful: Won't Fix Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+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 1783305] [NEW] apparmor DENIED when a systemd unit with DynamicUsers=yes is launched in a lxd container
Public bug reported: $ lxc launch images:debian/sid test-dynamicusers $ lxc exec test-dynamicusers bash $ systemd-run --unit=testdynamic -p DynamicUser=yes --uid=xnox /bin/true $ systemctl status testdynamic.service # systemctl status testdynamic.service ● testdynamic.service - /bin/true Loaded: loaded (/run/systemd/transient/testdynamic.service; transient) Transient: yes Active: failed (Result: exit-code) since Tue 2018-07-24 10:16:13 UTC; 6s ago Process: 470 ExecStart=/bin/true (code=exited, status=217/USER) Main PID: 470 (code=exited, status=217/USER) Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Forked /bin/true as 470 Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed dead -> running Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Job testdynamic.service/start finished, result=done Jul 24 10:16:13 systemd239 systemd[1]: Started /bin/true. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed to send unit change signal for testdynamic.service: Connection reset by peer Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Child 470 belongs to testdynamic.service. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Main process exited, code=exited, status=217/USER Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed with result 'exit-code'. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed running -> failed Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Unit entered failed state. and on the host side, in journal there is: Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:934): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:935): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:936): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:937): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:938): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:939): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:940): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:941): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Can we somehow make DynamicUser work in lxd containers? ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Impor
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
prompt on the phone (i.e. source device) ** Attachment added: "photo_2018-07-24_12-08-07.jpg" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+attachment/5167082/+files/photo_2018-07-24_12-08-07.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/958661 Title: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings Status in bluez package in Ubuntu: Confirmed Bug description: I often send image files via bluetooth from my android phone to my ubuntu PC. It worked fine until yesterday, but now I systematically get "the remote bluetooth device rejected the request". Nothing has changed in the way I transfer files and I'm trying from the very same phone. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-16-generic 3.0.0-16.29 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo 32650 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49' Mixer name : 'Realtek ALC660-VD' Components : 'HDA:10ec0660,1043,0011 HDA:10573055,10431316,00100700' Controls : 25 Simple ctrls : 16 Date: Sun Mar 18 17:55:36 2012 HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-16-generic N/A linux-backports-modules-3.0.0-16-generic N/A linux-firmware1.60.1 SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago) UserAsoundrc: pcm.!default { type pulse } ctl.!default { type pulse } pcm.pulse { type pulse } ctl.pulse { type pulse } dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn 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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+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 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
Now, several minutes after turning on Bluetooth on the computer, it was finally visible from the phone. So from the phone I tried sending a file, and I got the screen (on the phone) that I attached. It said: "Type the pairing code then press Return or Enter". (note: "the" pairing code. What pairing code? If I am supposed to type it on the computer, which "press return or enter" seems to suggest, then it should show up on the phone - or viceversa) So on the computer some prompt was supposed to show up, but it didn't. A small padlock showed up in the bluetooth icon on the computer, but there was no prompt for a code anywhere, nor did it show up by clicking on the bluetooth icon. After a while the operation timed out from the phone. Then I tried again. This time, at the prompt "type the pairing code then press Return or Enter" (again the one in the screenshot) I tapped on "pair". (the prompt is quite ambiguous: am I supposed to type the code, which I can't possibly know, in which case the "pair" button shouldn't be necessary, or should I press "pair" and *then* I'll be shown the code on the phone and prompted to insert it on the computer, in which case the message is confusing because it's telling me to enter it now??) So I tapped on "pair", and... The file was sent succesfully!! No code showed up anywhere and I didn't have to insert it anywhere. Of course I had paired these two particular devices before, literally years ago (and I'm not abusing the word "literally"). The UI of the whole process is a fucking mess on both sides, both Ubuntu AND Android. There are a bunch of bugs on both sides. Sharing files via bluetooth is a hell. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/958661 Title: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings Status in bluez package in Ubuntu: Confirmed Bug description: I often send image files via bluetooth from my android phone to my ubuntu PC. It worked fine until yesterday, but now I systematically get "the remote bluetooth device rejected the request". Nothing has changed in the way I transfer files and I'm trying from the very same phone. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-16-generic 3.0.0-16.29 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo 32650 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49' Mixer name : 'Realtek ALC660-VD' Components : 'HDA:10ec0660,1043,0011 HDA:10573055,10431316,00100700' Controls : 25 Simple ctrls : 16 Date: Sun Mar 18 17:55:36 2012 HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-16-generic N/A linux-backports-modules-3.0.0-16-generic N/A linux-firmware1.60.1 SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago) UserAsoundrc: pcm.!default { type pulse } ctl.!default { type pulse } pcm.pulse { type pulse } ctl.pulse { type pulse } dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn 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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+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 1769443] Re: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version
Please try hitting the Windows key and typing: Personal File Sharing Now launch the Personal File Sharing app and tick the box for: Receive files in Downloads folder over Bluetooth ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769443 Title: [RTL8723BE] Bluetooth is not working after updating my laptop to 18.04 - LTS version Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
Also, in "Personal File Sharing Preferences" (it's ridiculous that you have to look for these settings somewhere else, they should be under Bluetooth settings), "receive files over bluetooth" is turned on and "accept files" is set to "always". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/958661 Title: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings Status in bluez package in Ubuntu: Incomplete Bug description: I often send image files via bluetooth from my android phone to my ubuntu PC. It worked fine until yesterday, but now I systematically get "the remote bluetooth device rejected the request". Nothing has changed in the way I transfer files and I'm trying from the very same phone. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-16-generic 3.0.0-16.29 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo 32650 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49' Mixer name : 'Realtek ALC660-VD' Components : 'HDA:10ec0660,1043,0011 HDA:10573055,10431316,00100700' Controls : 25 Simple ctrls : 16 Date: Sun Mar 18 17:55:36 2012 HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-16-generic N/A linux-backports-modules-3.0.0-16-generic N/A linux-firmware1.60.1 SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago) UserAsoundrc: pcm.!default { type pulse } ctl.!default { type pulse } pcm.pulse { type pulse } ctl.pulse { type pulse } dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn 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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+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 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
On 16.04, now I can't even see the computer from another bluetooth device (my smartphone). Bluetooth is turned on and visibility is turned on. If I click on "ubuntu settings..." there is no other setting (I thought maybe there was something like "discoverability" that I should turn on). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/958661 Title: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings Status in bluez package in Ubuntu: Incomplete Bug description: I often send image files via bluetooth from my android phone to my ubuntu PC. It worked fine until yesterday, but now I systematically get "the remote bluetooth device rejected the request". Nothing has changed in the way I transfer files and I'm trying from the very same phone. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-16-generic 3.0.0-16.29 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo 32650 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49' Mixer name : 'Realtek ALC660-VD' Components : 'HDA:10ec0660,1043,0011 HDA:10573055,10431316,00100700' Controls : 25 Simple ctrls : 16 Date: Sun Mar 18 17:55:36 2012 HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MachineType: ASUSTeK Computer Inc. M51Sn ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-16-generic N/A linux-backports-modules-3.0.0-16-generic N/A linux-firmware1.60.1 SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago) UserAsoundrc: pcm.!default { type pulse } ctl.!default { type pulse } pcm.pulse { type pulse } ctl.pulse { type pulse } dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn 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.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+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 1783272] Re: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces
** Tags added: bionic -- 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/1783272 Title: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces Status in systemd package in Ubuntu: New Bug description: Upgrading the systemd package, which contains systemd-networkd, appears to restart networkd and subsequently reconfigure network interfaces causing a brief connectivity outage. This is a bionic system which has a network bridge as it's primary interface through netplan. You can see from the logs that the interface appears to have been briefly taken down > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered disabled state We also see logs of networkd restarting > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service... > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service. > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service... Based on the ordering of the messages from Avahi, I also believe that the IP address was first removed, then it was taken down, brought back up, and the IP re-added. But I can not state that with 100% certainty. However if you just set an interface down manually (ip link set br0 down), usually Avahi notes the interface is relevant before the address was removed. We see the opposite here. It's possible the ordering is just not entirely deterministic though. Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 10.48.134.22 on br0. Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer relevant for mDNS. The main reason I noticed this, is that the unofficial oracle- java8-installer package upgraded at the same time - and it's wget to download java failed due to "Network is unreachable" as it was upgraded as the same time. To be clear, I'm not suggesting necessarily that this specific package was affected is the bug, but it's the reason I noticed the restart and it did cause an upgrade failure which I resumed with "dpkg --configure -a". However there are many other implications of the network interface being reconfigured. Generally it's probably just not ideal to have networkd restart and reconfigure the network interfaces - no matter the possible causes. But from a quick thought about realistic implications - it seems the bridge was not deleted/re-created which would be bad for systems using libvirt/lxd/etc where the VMs may drop off the bridge. The interface index didn't change so hopefully we're safe from this one ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev exists, using existing without changing its parameters") - Another use case other than oracle-java8-installer that is highly likely to be impacted is daemons configured to bind to a specific IP address. By default, those binds will fail if the IP address doesn't exist. It's possible these two restarts will race and those services will fail to restart. An example where this could happen, is Apache2. It would probably be hard to reproduce but logically likely to occur in some small number of cases. - we potentially do want networkd to ideally restart to upgrade the code, but ideally it would "diff" the network interface config and not tear things down. I am using a 'switchport' match in my netplan config, I wonder if this is related? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies
Could we get a verification of this package? -- 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/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: (null) CPU min MHz: (null) L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 8-31 NUMA node1 CPU(s): 32-55 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 == Comment: #1 - Pridhiviraj Paidipeddi - 2017-01-11 07:06:59 == root@p8wookie:~# dmesg |grep -i powernv [0.00] Using PowerNV machine description [0.331564] EEH: PowerNV platform initialized [0.907250] powernv-rng: Registering arch random hook. [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0 [1.507167] powernv_idle_driver registered [ 34.184048] powernv_rng: Registered powernv hwrng. [ 34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree [ 34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, prod_id: 0x, dev_id: 0x00) root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ [ 42.297825315,7] OCC Common Area at 0x3b0 size 1MB [ 42.297854780,7] OCC Common Area at 0x200080 size 1MB [ 42.297884305,7] OCC Common Area at 0x200080 size 1
[Touch-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
This is still happening on Ubuntu 18.04 and kernel 4.15 :( (Dell XPS 9550) -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]
** Patch added: "setvtrgb.patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+attachment/5167040/+files/setvtrgb.patch -- 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/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] Status in console-setup package in Ubuntu: New Bug description: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+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 1783283] [NEW] setvtrgb.service incorrectly ordered [with patchy]
Public bug reported: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- 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/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] Status in console-setup package in Ubuntu: New Bug description: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+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 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
After: sudo apt-get install --reinstall hplip hplip-data sudo apt-get install --reinstall python3 I's ok with python3 and hp laserjet 1018 printer Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+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 1340250] Re: "#pragma weak" symbol is 0 even when defined
gcc u.c -Wl,--no-as-needed -lm; ./a.out; echo $? 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1340250 Title: "#pragma weak" symbol is 0 even when defined Status in binutils package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Status in libidn package in Ubuntu: New Status in libunistring package in Ubuntu: New Bug description: This compiler bug is making the gnulib tests dump core; see: http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html Compile and run the following program t.c with the shell commands "gcc u.c -lm; ./a.out; echo $?" #include #pragma weak tgamma int main (void) { if (!tgamma) return 2; if (tgamma (1) == 1) return 0; return 1; } The program will exit with status 2. It should exit with status 0, because the math library does have a tgamma function and the function pointer should be non-null. I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu 4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc 4:4.8.2-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 10 07:39:11 2014 InstallationDate: Installed on 2012-12-21 (566 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gcc-defaults UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250/+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 1340250] Re: "#pragma weak" symbol is 0 even when defined
Wl,--no-as-needed works, while adding a manual "-lpthread" doesn't, because the library doesn't get linked to the program. Reason is probably that weak symbols are not added by the linker -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1340250 Title: "#pragma weak" symbol is 0 even when defined Status in binutils package in Ubuntu: Invalid Status in gcc-defaults package in Ubuntu: Invalid Status in libidn package in Ubuntu: New Status in libunistring package in Ubuntu: New Bug description: This compiler bug is making the gnulib tests dump core; see: http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html Compile and run the following program t.c with the shell commands "gcc u.c -lm; ./a.out; echo $?" #include #pragma weak tgamma int main (void) { if (!tgamma) return 2; if (tgamma (1) == 1) return 0; return 1; } The program will exit with status 2. It should exit with status 0, because the math library does have a tgamma function and the function pointer should be non-null. I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu 4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc 4:4.8.2-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 10 07:39:11 2014 InstallationDate: Installed on 2012-12-21 (566 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gcc-defaults UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250/+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 1783272] Re: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces
** Attachment added: "netplan config" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+attachment/5167024/+files/01-netcfg.yaml -- 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/1783272 Title: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces Status in systemd package in Ubuntu: New Bug description: Upgrading the systemd package, which contains systemd-networkd, appears to restart networkd and subsequently reconfigure network interfaces causing a brief connectivity outage. This is a bionic system which has a network bridge as it's primary interface through netplan. You can see from the logs that the interface appears to have been briefly taken down > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered disabled state We also see logs of networkd restarting > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service... > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service. > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service... Based on the ordering of the messages from Avahi, I also believe that the IP address was first removed, then it was taken down, brought back up, and the IP re-added. But I can not state that with 100% certainty. However if you just set an interface down manually (ip link set br0 down), usually Avahi notes the interface is relevant before the address was removed. We see the opposite here. It's possible the ordering is just not entirely deterministic though. Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 10.48.134.22 on br0. Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer relevant for mDNS. The main reason I noticed this, is that the unofficial oracle- java8-installer package upgraded at the same time - and it's wget to download java failed due to "Network is unreachable" as it was upgraded as the same time. To be clear, I'm not suggesting necessarily that this specific package was affected is the bug, but it's the reason I noticed the restart and it did cause an upgrade failure which I resumed with "dpkg --configure -a". However there are many other implications of the network interface being reconfigured. Generally it's probably just not ideal to have networkd restart and reconfigure the network interfaces - no matter the possible causes. But from a quick thought about realistic implications - it seems the bridge was not deleted/re-created which would be bad for systems using libvirt/lxd/etc where the VMs may drop off the bridge. The interface index didn't change so hopefully we're safe from this one ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev exists, using existing without changing its parameters") - Another use case other than oracle-java8-installer that is highly likely to be impacted is daemons configured to bind to a specific IP address. By default, those binds will fail if the IP address doesn't exist. It's possible these two restarts will race and those services will fail to restart. An example where this could happen, is Apache2. It would probably be hard to reproduce but logically likely to occur in some small number of cases. - we potentially do want networkd to ideally restart to upgrade the code, but ideally it would "diff" the network interface config and not tear things down. I am using a 'switchport' match in my netplan config, I wonder if this is related? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+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 1783272] Re: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+attachment/5167022/+files/syslog -- 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/1783272 Title: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces Status in systemd package in Ubuntu: New Bug description: Upgrading the systemd package, which contains systemd-networkd, appears to restart networkd and subsequently reconfigure network interfaces causing a brief connectivity outage. This is a bionic system which has a network bridge as it's primary interface through netplan. You can see from the logs that the interface appears to have been briefly taken down > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered disabled state We also see logs of networkd restarting > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service... > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service. > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service... Based on the ordering of the messages from Avahi, I also believe that the IP address was first removed, then it was taken down, brought back up, and the IP re-added. But I can not state that with 100% certainty. However if you just set an interface down manually (ip link set br0 down), usually Avahi notes the interface is relevant before the address was removed. We see the opposite here. It's possible the ordering is just not entirely deterministic though. Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 10.48.134.22 on br0. Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer relevant for mDNS. The main reason I noticed this, is that the unofficial oracle- java8-installer package upgraded at the same time - and it's wget to download java failed due to "Network is unreachable" as it was upgraded as the same time. To be clear, I'm not suggesting necessarily that this specific package was affected is the bug, but it's the reason I noticed the restart and it did cause an upgrade failure which I resumed with "dpkg --configure -a". However there are many other implications of the network interface being reconfigured. Generally it's probably just not ideal to have networkd restart and reconfigure the network interfaces - no matter the possible causes. But from a quick thought about realistic implications - it seems the bridge was not deleted/re-created which would be bad for systems using libvirt/lxd/etc where the VMs may drop off the bridge. The interface index didn't change so hopefully we're safe from this one ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev exists, using existing without changing its parameters") - Another use case other than oracle-java8-installer that is highly likely to be impacted is daemons configured to bind to a specific IP address. By default, those binds will fail if the IP address doesn't exist. It's possible these two restarts will race and those services will fail to restart. An example where this could happen, is Apache2. It would probably be hard to reproduce but logically likely to occur in some small number of cases. - we potentially do want networkd to ideally restart to upgrade the code, but ideally it would "diff" the network interface config and not tear things down. I am using a 'switchport' match in my netplan config, I wonder if this is related? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+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 1783272] Re: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces
** Attachment added: "log of terminal session during upgrade" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+attachment/5167023/+files/apt-upgrade-console-log.txt ** Description changed: Upgrading the systemd package, which contains systemd-networkd, appears to restart networkd and subsequently reconfigure network interfaces causing a brief connectivity outage. This is a bionic system which has a network bridge as it's primary interface through netplan. You can see from the logs that the interface appears to have been briefly taken down > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered disabled state We also see logs of networkd restarting - > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service... - > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service. - > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service... + > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service... + > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service. + > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service... Based on the ordering of the messages from Avahi, I also believe that the IP address was first removed, then it was taken down, brought back up, and the IP re-added. But I can not state that with 100% certainty. However if you just set an interface down manually (ip link set br0 down), usually Avahi notes the interface is relevant before the address was removed. We see the opposite here. It's possible the ordering is just not entirely deterministic though. Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 10.48.134.22 on br0. Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer relevant for mDNS. - - The main reason I noticed this, is that the unofficial oracle-java8-installer package upgraded at the same time - and it's wget to download java failed due to "Network is unreachable" as it was upgraded as the same time. To be clear, I'm not suggesting necessarily that this specific package was affected is the bug, but it's the reason I noticed the restart and it did cause an upgrade failure which I resumed with "dpkg --configure -a". However there are many other implications of the network interface being reconfigured. + The main reason I noticed this, is that the unofficial oracle- + java8-installer package upgraded at the same time - and it's wget to + download java failed due to "Network is unreachable" as it was upgraded + as the same time. To be clear, I'm not suggesting necessarily that this + specific package was affected is the bug, but it's the reason I noticed + the restart and it did cause an upgrade failure which I resumed with + "dpkg --configure -a". However there are many other implications of the + network interface being reconfigured. Generally it's probably just not ideal to have networkd restart and reconfigure the network interfaces - no matter the possible causes. But - from a quick though about realistic implications + from a quick thought about realistic implications + - it seems the bridge was not deleted/re-created which would be bad for + systems using libvirt/lxd/etc where the VMs may drop off the bridge. The + interface index didn't change so hopefully we're safe from this one + ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev exists, + using existing without changing its parameters") - - it seems the bridge was not deleted/re-created which would be bad for systems using libvirt/lxd/etc where the VMs may drop off the bridge. The interface index didn't change so hopefully we're safe from this one ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev exists, using existing without changing its parameters") - - - Another use case other than oracle-java8-installer that is highly + - Another use case other than oracle-java8-installer that is highly likely to be impacted is daemons configured to bind to a specific IP address. By default, those binds will fail if the IP address doesn't exist. It's possible these two restarts will race and those services will fail to restart. An example where this could happen, is Apache2. It would probably be hard to reproduce but logically likely to occur in some small number of cases. + + - we potentially do want networkd to ideally restart to upgrade the + code, but ideally it would "diff" the network interface config and not + tear things down. I am using a 'switchport' match in my netplan config, + I wonder if this is related? -- 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/1783272 Title: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces Status in systemd package in Ubuntu: New
[Touch-packages] [Bug 1783272] [NEW] upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces
Public bug reported: Upgrading the systemd package, which contains systemd-networkd, appears to restart networkd and subsequently reconfigure network interfaces causing a brief connectivity outage. This is a bionic system which has a network bridge as it's primary interface through netplan. You can see from the logs that the interface appears to have been briefly taken down > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered > disabled state We also see logs of networkd restarting > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service... > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service. > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service... Based on the ordering of the messages from Avahi, I also believe that the IP address was first removed, then it was taken down, brought back up, and the IP re-added. But I can not state that with 100% certainty. However if you just set an interface down manually (ip link set br0 down), usually Avahi notes the interface is relevant before the address was removed. We see the opposite here. It's possible the ordering is just not entirely deterministic though. Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 10.48.134.22 on br0. Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer relevant for mDNS. The main reason I noticed this, is that the unofficial oracle- java8-installer package upgraded at the same time - and it's wget to download java failed due to "Network is unreachable" as it was upgraded as the same time. To be clear, I'm not suggesting necessarily that this specific package was affected is the bug, but it's the reason I noticed the restart and it did cause an upgrade failure which I resumed with "dpkg --configure -a". However there are many other implications of the network interface being reconfigured. Generally it's probably just not ideal to have networkd restart and reconfigure the network interfaces - no matter the possible causes. But from a quick thought about realistic implications - it seems the bridge was not deleted/re-created which would be bad for systems using libvirt/lxd/etc where the VMs may drop off the bridge. The interface index didn't change so hopefully we're safe from this one ("Jul 24 09:40:32 optane systemd-networkd[17118]: br0: netdev exists, using existing without changing its parameters") - Another use case other than oracle-java8-installer that is highly likely to be impacted is daemons configured to bind to a specific IP address. By default, those binds will fail if the IP address doesn't exist. It's possible these two restarts will race and those services will fail to restart. An example where this could happen, is Apache2. It would probably be hard to reproduce but logically likely to occur in some small number of cases. - we potentially do want networkd to ideally restart to upgrade the code, but ideally it would "diff" the network interface config and not tear things down. I am using a 'switchport' match in my netplan config, I wonder if this is related? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783272 Title: upgrading systemd package restarts systemd-networkd and briefly takes down network interfaces Status in systemd package in Ubuntu: New Bug description: Upgrading the systemd package, which contains systemd-networkd, appears to restart networkd and subsequently reconfigure network interfaces causing a brief connectivity outage. This is a bionic system which has a network bridge as it's primary interface through netplan. You can see from the logs that the interface appears to have been briefly taken down > Jul 24 09:40:32 optane kernel: [ 1935.046068] br0: port 1(eno1) entered disabled state We also see logs of networkd restarting > 248 Jul 24 09:40:32 optane systemd[1]: Stopping Network Service... > 253 Jul 24 09:40:32 optane systemd[1]: Stopped Network Service. > 254 Jul 24 09:40:32 optane systemd[1]: Starting Network Service... Based on the ordering of the messages from Avahi, I also believe that the IP address was first removed, then it was taken down, brought back up, and the IP re-added. But I can not state that with 100% certainty. However if you just set an interface down manually (ip link set br0 down), usually Avahi notes the interface is relevant before the address was removed. We see the opposite here. It's possible the ordering is just not entirely deterministic though. Jul 24 09:40:32 optane avahi-daemon[1611]: Withdrawing address record for 10.48.134.22 on br0. Jul 24 09:40:32 optane avahi-daemon[1611]: Interface br0.IPv4 no longer relevant for mDNS. The main reason I noticed this, is that the unofficial oracle- java