[Touch-packages] [Bug 1865219] [NEW] [USB-Audio - HyperX Virtual Surround Sound, recording] fails after a while
Public bug reported: It happens regularly that my headset microphone stops working. Sometimes I manage to get it back by unplugging it and replugging to another USB port, sometimes it doesn't work. It's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 21:31:04 2020 InstallationDate: Installed on 2019-09-03 (178 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: QuickCam E 3500 - USB Device 0x46d:0x9a4 Symptom_PulseAudioLog: févr. 28 20:22:04 zavacHome dbus-daemon[1171]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.39' (uid=121 pid=1762 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") févr. 28 20:22:10 zavacHome pulseaudio[1762]: W: [pulseaudio] sink.c: Default and alternate sample rates are the same. févr. 28 20:22:13 zavacHome dbus-daemon[1171]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.109' (uid=121 pid=1762 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - HyperX Virtual Surround Sound, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** 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/1865219 Title: [USB-Audio - HyperX Virtual Surround Sound, recording] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: It happens regularly that my headset microphone stops working. Sometimes I manage to get it back by unplugging it and replugging to another USB port, sometimes it doesn't work. It's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 21:31:04 2020 InstallationDate: Installed on 2019-09-03 (178 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: QuickCam E 3500 - USB Device 0x46d:0x9a4 Symptom_PulseAudioLog: févr. 28 20:22:04 zavacHome dbus-daemon[1171]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.39' (uid=121 pid=1762 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") févr. 28 20:22:10 zavacHome pulseaudio[1762]: W: [pulseaudio] sink.c: Default and alternate sample rates are the same. févr. 28 20:22:13 zavacHome dbus-daemon[1171]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.109' (uid=121 pid=1762 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - HyperX Virtual Surround Sound, recording] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Touch-packages] [Bug 1859319] Re: widget factory slighty too wide for common 1366x768 display
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1859319 Title: widget factory slighty too wide for common 1366x768 display Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I'm using a ThinkPad X220 to test the Ubuntu default theme. It has a wildly common 1366x768 display panel. At the time of writing, around 25% of installs have such a resolution - https://ubuntu.com/desktop/statistics The default non-hiding 48px launcher, and width of the widget factory, means that it's impossible to get the entire application on screen at once. There appears to be some space which could be saved by shrinking horizontally a couple of components on each page. Steps to reproduce * Install Ubuntu 20.04. * Set system resolution to 1366x768 * Install gtk3-examples * Alt-f2, gtk3-widget-factory Expected outcome * Entire widget factory should fit on the screen Actual outcome * The widget factory window is off the right hand side of the screen Workaround Set the launcher to auto hide, to make room. I don't consider this suitable, because part of the point of gtk widget factory is to test the theme, the experience, the out of the box install. Being unable to actually get the window on the screen seems a flawed set of tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gtk-3-examples 3.24.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:13:41 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1859319/+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 1809438] Re: systemd-resolved segfaults
How should I persistently bypass systemd-resolved ? The DNS failures are causes other applications to fail. I'd like resolv.conf to update with dhcp returned data for DNS servers, but, for the time being, I'd like applications to talk to the upstream DNS servers until this issue is resolved. -- 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/1809438 Title: systemd-resolved segfaults Status in systemd package in Ubuntu: Confirmed Bug description: I regularly (once almost every hour) get segfaults resported in systemd-resolved. The syslog is not always the same: Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in systemd-resolved[556f74bcf000+59000] Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process exited, code=dumped, status=11/SEGV Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with result 'core-dump'. Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in libsystemd-shared-237.so[7f4810e1f000+1b5000] Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process exited, code=dumped, status=11/SEGV Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with result 'core-dump'. Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' failed at ../src/resolve/resolved-dns-packet.c:210, function dns_packet_unref(). Aborting. Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process exited, code=dumped, status=6/ABRT Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with result 'core-dump'. Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 'DNS_TRANSACTION_IS_LIVE(q->state)' failed at ../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). Aborting. Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process exited, code=dumped, status=6/ABRT Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with result 'core-dump'. The system in question uses dnsmasq as local DNS server. Logging that is probably unrelated, but often seen (possibly due to the setup with dnsmasq) is: dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set (TCP) for DNS server 127.0.0.1. # dpkg --status systemd Package: systemd Installed-Size: 12444 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: foreign Version: 237-3ubuntu10.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809438/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
The problem exists on my system: Ubuntu 18.04LTS with Gnome Classic Desktop ASUS N3050M-E M/B with the Intel N3050 (Braswell) CPU VGA video connector (not HDMI) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: 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.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/gnome-shell/+bug/1767654/+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 1865254] [NEW] After fresh installation 19.10 on Dell vostro 15 3568 it is showing screen blinking when I try to unlock and locking with Super+L
Public bug reported: I am new to report such issues so I just don't know what to share here. though below is the kernel and syslog of the system. I having this issue with this model only as many of this model to test. Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Syslog:- Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 5603e0fd7930 i resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 5603e0fd7930 i resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4540 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4ed0 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button (0x5603e0eaccd0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for context 0x5603df1c4330 == Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0 7ffceebe4ed0 b resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15) Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1 7ffceebe4f80 b self-hosted:975 (7fdf75834160 @ 392) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 11:49:13 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793] InstallationDate: Installed on 2020-02-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 15-3568 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=e4c9da5a-c5ed-4509-ac83-acf0ed89a193 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0793 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri:
[Touch-packages] [Bug 1861408] Re: firefox apparmor messages
message when switching to read mode:
Feb 26 13:13:13 dinar-HP-Pavilion-g7-Notebook-PC kernel: [64008.165294] audit:
type=1400 audit(1582711993.444:302): apparmor="DENIED" operation="exec"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/usr/bin/speech-dispatcher" pid=30443 comm=7370656563686420696E6974
requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
--
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/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Isn't this because HSP is not handled by pulse audio but ofono since PA11.0? https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ Ofono is HSP 1.6 and wideband audio 16khz but ubuntu conf doesn't implement? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in xorg package in Ubuntu: New Bug description: when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN46WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined
[Touch-packages] [Bug 1865130] [NEW] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
You have been subscribed to a public bug: when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN46WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G510 dmi.modalias: dmi:bvnLENOVO:bvr79CN46WW(V3.05):bd12/23/2013:svnLENOVO:pn20238:pvrLenovoG510:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG510: dmi.product.family: IDEAPAD dmi.product.name: 20238 dmi.product.sku: LENOVO_MT_20238 dmi.product.version: Lenovo G510 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I think you'll need to enable logind debug and reboot or restart systemd-logind: $ sudo systemctl edit systemd-logind in the editor that opens, put: [Service] Environment=SYSTEMD_LOG_LEVEL=debug then save the file, and reboot (or restart systemd-logind). After the number of sessions have grown for a while, re-capture the journalctl logs for logind and attach here. -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
There is still something wrong here.
The site in question has fixed the issue in response to my query, and
SSL Labs now gives it an A grade:
https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com
According to SSL Labs, it supports these two ciphers for TLS 1.2:
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)
According to openssl ciphers -s -V, both of these are supported by
openssl:
$ openssl ciphers -s -V | egrep '0xC0,0x(30|2F)'
0xC0,0x30 - ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA
Enc=AESGCM(256) Mac=AEAD
0xC0,0x2F - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=RSA
Enc=AESGCM(128) Mac=AEAD
And yet I'm still unable to connect to this server through openssl
unless I downgrade the security level to 1.
You mentioned there being an SHA1 certificate in the chain, but I don't
see one. The certs all seem to be SHA256.
I cannot find any evidence that security level 2 blocks the use of
certificates with lifetimes of more than a year. Is that an undocumented
"feature" of security level 2?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in openssl package in Ubuntu:
New
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1862169] Re: rhythmbox crashed with SIGSEGV in build_flavored_key()
Confirmed to be fixed. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1862169 Title: rhythmbox crashed with SIGSEGV in build_flavored_key() Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1862169/+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 1865055] Re: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:
** Tags added: champagne ** Changed in: iptables (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1865055 Title: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 Status in iptables package in Ubuntu: Confirmed Bug description: Running standard upgrades in focal. Unpacking libip4tc-dev:amd64 (1.8.4-3ubuntu1) over (1.8.3-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-vyGukq/07-libip4tc-dev_1.8.4-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 dpkg: considering deconfiguration of libip4tc-dev:amd64, which would be broken by installation of libiptc-dev:amd64 ... dpkg: yes, will deconfigure libip4tc-dev:amd64 (broken by libiptc-dev:amd64) Preparing to unpack .../08-libiptc-dev_1.8.4-3ubuntu1_amd64.deb ... De-configuring libip4tc-dev:amd64 (1.8.3-2ubuntu5) ... Left my system in this state... $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: gobject-introspection : Depends: libgirepository-1.0-1 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed hplip : Depends: hplip-data (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed Depends: libhpmud0 (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed Depends: printer-driver-hpcups (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed libcryptsetup-dev : Depends: libcryptsetup12 (= 2:2.2.2-3ubuntu1) but 2:2.2.2-2ubuntu1 is installed libgirepository1.0-dev : Depends: libgirepository-1.0-1 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed Depends: gir1.2-glib-2.0 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed Depends: gir1.2-freedesktop (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed libip4tc-dev : Depends: libip4tc2 (= 1.8.3-2ubuntu5) but 1.8.4-3ubuntu1 is installed libiptc-dev : Depends: libip4tc-dev (= 1.8.4-3ubuntu1) but 1.8.3-2ubuntu5 is installed Breaks: libip4tc-dev (< 1.8.4-2) but 1.8.3-2ubuntu5 is installed libnss-systemd : Depends: systemd (= 244.3-1ubuntu1) libpam-systemd : Depends: systemd (= 244.3-1ubuntu1) libsmbclient : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed libsystemd-dev : Depends: libsystemd0 (= 244.3-1ubuntu1) but 244.1-0ubuntu2 is installed libudev-dev : Depends: libudev1 (= 244.3-1ubuntu1) but 244.1-0ubuntu2 is installed python3-ldb : Depends: libldb2 (= 2:2.0.8-1ubuntu1) but 2:2.0.7-4 is installed python3-samba : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libldb2 (>= 2:2.0.8~) but 2:2.0.7-4 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed samba-common-bin : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed systemd-sysv : Depends: systemd (= 244.3-1ubuntu1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libip4tc-dev 1.8.3-2ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Thu Feb 27 10:28:46 2020 ErrorMessage: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 InstallationDate: Installed on 2019-04-05 (327 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190405) Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.8 SourcePackage: iptables Title: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 UpgradeStatus: Upgraded to focal on 2019-11-21 (97 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1865055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
> lxc.net.0.ipv4.gateway = 192.168.252.1 > lxc.net.0.ipv4.address = 192.168.252.171/32 > 3. inside the container, deactivate dhcp (dhcp4: false )in `/etc/netplan/10-lxc.yaml`, ok, this is your problem; you're misconfiguring the instance. Unfortunately, you were just 'lucky' that it worked before, but this is absolutely intended behavior of systemd: when you tell it to manage an interface, it expects to control 100% of the interface's addresses and routing (with the minor exception that newer systemd has added 'KeepConfiguration' config for specific situations where externally- configured networking should be kept on the interface, such as some HA setups). Your problem here is that you're configuring the interface networking *outside* networkd, but then also telling networkd it should manage the interface. It's fine to use lxc to externally configure the interface networking, but then inside the container you must make sure networkd does not think it's managing eth0, which means you must completely remove the 'eth0' section inside the netplan config yaml - if you leave any 'eth0' config there at all, it will create a network file telling networkd that it should manage eth0, even though it's not assigning any ipv4 addresses (it does setup ipv6 link-local by default, however). The file that netplan creates for the eth0 interface will be /run/systemd/network/10-netplan-eth0.network. You can see in the output of networkctl: root@bionic:/# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 29 eth0 ether degradedconfigured since in your use case you do not use (or want!) networkd to manage eth0, you want the 'SETUP' column to show 'unmanaged', not 'configured'. What you need to do is, instead of simply changing the netplan eth0 dhcp4 configuration to false, you need to remove the eth0 section completely. If that's the only section you have, you'll need to remove the entire 'ethernets' section, or just remove the yaml file entirely (or rename it to anything that doesn't end in '.yaml'). Then, when you 'netplan apply' or reboot, you should notice that the /run/systemd/network/ file for eth0 is no longer created, and networkd no longer thinks it manages eth0, and your externally-configured eth0 networking should work again. I hope this works for you, and very sorry for the disruption of your production environment. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Invalid Bug description: In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal Fossa, installing the latest systemd package results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
Thank you so much for your very detailed answer! I understand my mistake and fixed our set-up. -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Invalid Bug description: In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal Fossa, installing the latest systemd package results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n]
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
> is there anything I should be aware of like the consequence of such editing and restarting? enabling debug logging will significantly increase the amount of log messages that logind sends to your log journal/syslog. > You wrote reboot or restart, reboot you mean VPS and restart you mean systemd-logind service? yes -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1865055] Re: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:
** Changed in: iptables (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: iptables (Ubuntu) Status: Confirmed => Triaged ** Changed in: iptables (Ubuntu) Status: Triaged => In Progress ** Changed in: iptables (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1865055 Title: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 Status in iptables package in Ubuntu: Fix Committed Bug description: Running standard upgrades in focal. Unpacking libip4tc-dev:amd64 (1.8.4-3ubuntu1) over (1.8.3-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-vyGukq/07-libip4tc-dev_1.8.4-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 dpkg: considering deconfiguration of libip4tc-dev:amd64, which would be broken by installation of libiptc-dev:amd64 ... dpkg: yes, will deconfigure libip4tc-dev:amd64 (broken by libiptc-dev:amd64) Preparing to unpack .../08-libiptc-dev_1.8.4-3ubuntu1_amd64.deb ... De-configuring libip4tc-dev:amd64 (1.8.3-2ubuntu5) ... Left my system in this state... $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: gobject-introspection : Depends: libgirepository-1.0-1 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed hplip : Depends: hplip-data (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed Depends: libhpmud0 (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed Depends: printer-driver-hpcups (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed libcryptsetup-dev : Depends: libcryptsetup12 (= 2:2.2.2-3ubuntu1) but 2:2.2.2-2ubuntu1 is installed libgirepository1.0-dev : Depends: libgirepository-1.0-1 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed Depends: gir1.2-glib-2.0 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed Depends: gir1.2-freedesktop (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed libip4tc-dev : Depends: libip4tc2 (= 1.8.3-2ubuntu5) but 1.8.4-3ubuntu1 is installed libiptc-dev : Depends: libip4tc-dev (= 1.8.4-3ubuntu1) but 1.8.3-2ubuntu5 is installed Breaks: libip4tc-dev (< 1.8.4-2) but 1.8.3-2ubuntu5 is installed libnss-systemd : Depends: systemd (= 244.3-1ubuntu1) libpam-systemd : Depends: systemd (= 244.3-1ubuntu1) libsmbclient : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed libsystemd-dev : Depends: libsystemd0 (= 244.3-1ubuntu1) but 244.1-0ubuntu2 is installed libudev-dev : Depends: libudev1 (= 244.3-1ubuntu1) but 244.1-0ubuntu2 is installed python3-ldb : Depends: libldb2 (= 2:2.0.8-1ubuntu1) but 2:2.0.7-4 is installed python3-samba : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libldb2 (>= 2:2.0.8~) but 2:2.0.7-4 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed samba-common-bin : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed systemd-sysv : Depends: systemd (= 244.3-1ubuntu1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libip4tc-dev 1.8.3-2ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Thu Feb 27 10:28:46 2020 ErrorMessage: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 InstallationDate: Installed on 2019-04-05 (327 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190405) Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.8 SourcePackage: iptables Title: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 UpgradeStatus: Upgraded to focal on 2019-11-21 (97 days ago) To manage notifications
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
Before doing so, is there anything I should be aware of like the consequence of such editing and restarting? You wrote reboot or restart, reboot you mean VPS and restart you mean systemd-logind service? Ofcourse I prefer to restart the service only and not the whole vps, is there a recommended way to do it without breaking anything? I ask because during my searches for the problem, I read that it should be done with cautious. Thanks -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 953424] Re: add-apt-repository does not handle malformed repo URL nicely
This specific case appears to have been fixed a while ago. I couldn't
find the specific commit, but running this test case in 20.04, an error
is printed in the terminal, but no exception is raised.
** Changed in: software-properties (Ubuntu)
Status: Confirmed => Fix Released
--
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/953424
Title:
add-apt-repository does not handle malformed repo URL nicely
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
add-apt-repository doesn't handle URLs nicely when they are malformed
in a particular way. If you forget to add a repository name to a full-
form ppa url it should fail gracefully but instead crashes:
sudo add-apt-repository http://ppa.launchpad.net/username/ubuntu
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 95,
in run
self.add_ppa_signing_key(self.ppa_path)
File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line
103, in add_ppa_signing_key
owner_name, ppa_name, distro = ppa_path[1:].split('/')
ValueError: need more than 2 values to unpack
In this case I simply forgot to add the ppa name between the owner
name and the distro. The 'correct' lines for the malformed URL are
added to sources.list. It would be much nicer if add-apt-repository
could handle this issue more gracefully. This is on Ubuntu 11.10,
version 0.81.13.3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/953424/+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 1865181] Re: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127
** 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/1865181 Title: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 Status in systemd package in Ubuntu: New Bug description: upgrade to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 244.3-1ubuntu1 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Fri Feb 28 18:06:33 2020 DuplicateSignature: package:systemd:244.3-1ubuntu1 Installing new version of config file /etc/systemd/user.conf ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-242.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 127 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: Hetzner vServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.4-050504-generic root=UUID=a19fc250-48f4-458e-a151-15fd77030b56 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: systemd Title: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-02-28 (0 days ago) dmi.bios.date: 11/11/2017 dmi.bios.vendor: Hetzner dmi.bios.version: 2017 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnHetzner:bvr2017:bd11/11/2017:svnHetzner:pnvServer:pvr2017:cvnQEMU:ct1:cvrNotSpecified: dmi.product.family: Hetzner_vServer dmi.product.name: vServer dmi.product.version: 2017 dmi.sys.vendor: Hetzner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1865181/+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 1865181] [NEW] package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127
Public bug reported: upgrade to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 244.3-1ubuntu1 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Fri Feb 28 18:06:33 2020 DuplicateSignature: package:systemd:244.3-1ubuntu1 Installing new version of config file /etc/systemd/user.conf ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-242.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 127 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: Hetzner vServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.4-050504-generic root=UUID=a19fc250-48f4-458e-a151-15fd77030b56 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: systemd Title: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-02-28 (0 days ago) dmi.bios.date: 11/11/2017 dmi.bios.vendor: Hetzner dmi.bios.version: 2017 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnHetzner:bvr2017:bd11/11/2017:svnHetzner:pnvServer:pvr2017:cvnQEMU:ct1:cvrNotSpecified: dmi.product.family: Hetzner_vServer dmi.product.name: vServer dmi.product.version: 2017 dmi.sys.vendor: Hetzner ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages uec-images -- 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/1865181 Title: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 Status in systemd package in Ubuntu: New Bug description: upgrade to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: systemd 244.3-1ubuntu1 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Fri Feb 28 18:06:33 2020 DuplicateSignature: package:systemd:244.3-1ubuntu1 Installing new version of config file /etc/systemd/user.conf ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-242.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 127 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: Hetzner vServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.4-050504-generic root=UUID=a19fc250-48f4-458e-a151-15fd77030b56 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: systemd Title: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-02-28 (0 days ago) dmi.bios.date: 11/11/2017 dmi.bios.vendor: Hetzner dmi.bios.version: 2017 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnHetzner:bvr2017:bd11/11/2017:svnHetzner:pnvServer:pvr2017:cvnQEMU:ct1:cvrNotSpecified: dmi.product.family: Hetzner_vServer dmi.product.name: vServer dmi.product.version: 2017 dmi.sys.vendor: Hetzner To manage notifications
[Touch-packages] [Bug 1865204] [NEW] Multiple packages broke with openssl 1.1.1 upgrade
Public bug reported: While I welcome the adding of security features by upgrading vital packages like openssl, there are at least two packages that I know of which ran fine with libssl 1.1.0 and do not with libssl 1.1.1. This bug has been introduced with the migration from openssl 1.1.0 to 1.1.1 in one of the last point releases. 1. stunnel4 3:5.44-1ubuntu3 stunnel4 breaks with openssl 1.1.1 (which supports TLS 1.3). I get errors when a Windows stunnel client connects to the stunnel4 daemon: Feb 20 14:10:03 peterpan.neverland stunnel[24427]: LOG3[0]: s_connect: connect ::1:3128 : Connection refused (111) This can be fixed when I manually add "MaxProtocol = TLSv1.2" to /etc/ssl/openssl.conf, showing that TLS 1.3 introduced by openssl 1.1.1 is the culprit. stunnel4 needs an update. At least for stunnel4, another fix would be to specify "sslVersion = TLSv1.2" in its config file. 2. pure-ftpd 1.0.46-1build1 Same thing here. You cannot connect once you use "tls=2" or higher if openssl 1.1.1 with TLS 1.3 is active. Only fix here I found is to limit the max protocol. pure-ftpd itself has no means of solving that problem, at least not in the bionic version. I use Ubuntu Server 18.04.04 LTS, BTW and openssl was 1.1.1-1ubuntu2.1~18.04.5. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1865204 Title: Multiple packages broke with openssl 1.1.1 upgrade Status in openssl package in Ubuntu: New Bug description: While I welcome the adding of security features by upgrading vital packages like openssl, there are at least two packages that I know of which ran fine with libssl 1.1.0 and do not with libssl 1.1.1. This bug has been introduced with the migration from openssl 1.1.0 to 1.1.1 in one of the last point releases. 1. stunnel4 3:5.44-1ubuntu3 stunnel4 breaks with openssl 1.1.1 (which supports TLS 1.3). I get errors when a Windows stunnel client connects to the stunnel4 daemon: Feb 20 14:10:03 peterpan.neverland stunnel[24427]: LOG3[0]: s_connect: connect ::1:3128 : Connection refused (111) This can be fixed when I manually add "MaxProtocol = TLSv1.2" to /etc/ssl/openssl.conf, showing that TLS 1.3 introduced by openssl 1.1.1 is the culprit. stunnel4 needs an update. At least for stunnel4, another fix would be to specify "sslVersion = TLSv1.2" in its config file. 2. pure-ftpd 1.0.46-1build1 Same thing here. You cannot connect once you use "tls=2" or higher if openssl 1.1.1 with TLS 1.3 is active. Only fix here I found is to limit the max protocol. pure-ftpd itself has no means of solving that problem, at least not in the bionic version. I use Ubuntu Server 18.04.04 LTS, BTW and openssl was 1.1.1-1ubuntu2.1~18.04.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1865204/+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
