[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs
same problem here. Did a fresh install of Ubuntu 24.04. After using autologin a lot of programs have no border and shadow. They also cant be resized any more. If I log out and in again, this effects are gone. After a restart with autologin the effects are here again. If I disable autologin, everything works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064192] Re: Unable to resize windows
same problem here with programs e. g. libreoffice, geany ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064192 Title: Unable to resize windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056152] [NEW] errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: see summary. after skipping the error message, thunderbird seems to work well ProblemType: Package DistroRelease: Ubuntu 22.04 Package: dnsmasq 2.90-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: dnsmasq:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Mar 5 09:50:12 2024 DpkgHistoryLog: Start-Date: 2024-03-05 09:50:11 Commandline: /usr/bin/unattended-upgrade Upgrade: dnsmasq:amd64 (2.86-1.1ubuntu0.5, 2.90-0ubuntu0.22.04.1) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2022-11-08 (482 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: dnsmasq Title: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2022-11-15T02:41:03.690882 mtime.conffile..etc.dnsmasq.conf: 2022-11-15T02:41:10.043282 ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056152 Title: errors when starting thunderbird, directly after boot. error message: package dnsmasq 2.90-0ubuntu0.22.04.1 failed to install/upgrade: end of file on stdin at conffile prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2056152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976307] Re: Stack smashing in gamatronic driver
Thanks Lucas. I'm installing the version you prepared and will run it for a few days to see if it's stable, and then report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976307 Title: Stack smashing in gamatronic driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1976307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976307] [NEW] Stack smashing in gamatronic driver
Public bug reported: The gamatronic UPS driver in nut 2.7.4-14ubuntu2 randomly crashes after a memory violation attempt. This usually happens after many hours of operation, typically after 20h or more, and started after the update to jammy. No similar problems happened on focal. 116159.602986 UPS<--PC: "0,599,1,1237,0015,00172,020" 116159.603047 PC-->UPS: "^P003ST5" 116159.603130send returned: 8 116160.836034 UPS<--PC: "0,0,0,0,0,0,0,0,0,0,0,0,0,0,0" 116160.836062 PC-->UPS: "^P003ST1" 116160.836143send returned: 8 116162.085828 UPS<--PC: "0,0,0,0,999,100,0273,0004,00" 116162.085881 PC-->UPS: "^P003ST4" 116162.085973send returned: 8 116163.308513 UPS<--PC: "600,1,1237,0015,00173,," 116163.308537 PC-->UPS: "^P003ST2" 116163.308614send returned: 8 116164.513013 UPS<--PC: "000,1,600,1294,," 116164.513076 PC-->UPS: "^P003ST3" 116164.513159send returned: 8 116165.785520 UPS<--PC: "0,599,1,1237,0015,00174,021" *** stack smashing detected ***: terminated Aborted Broadcast message from nut@hiccup (somewhere) (Mon May 30 16:49:10 2022): Communications with UPS nhs@localhost lost The driver is being used with the following device: device.mfr: NHS Sistemas de Energia device.model: PDV SENOIDAL 1400 VA device.type: ups driver.name: gamatronic driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyACM0 driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.internal: 0.02 Additional contextual information: Description:Ubuntu 22.04 LTS Release:22.04 nut-server: Installed: 2.7.4-14ubuntu2 Candidate: 2.7.4-14ubuntu2 Version table: *** 2.7.4-14ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen: process not crashing What happened instead: process crashed (boo) ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Attachment added: "core dump" https://bugs.launchpad.net/bugs/1976307/+attachment/5593932/+files/core.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976307 Title: Stack smashing in gamatronic driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1976307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973462] [NEW] Empty indicator plugin
Public bug reported: After boot I have to remove and add again indicator plugin to show the contants ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xfce4-indicator-plugin 2.4.1-1 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun May 15 16:51:09 2022 InstallationDate: Installed on 2021-01-23 (477 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: xfce4-indicator-plugin UpgradeStatus: Upgraded to jammy on 2022-04-05 (39 days ago) ** Affects: xfce4-indicator-plugin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973462 Title: Empty indicator plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-indicator-plugin/+bug/1973462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973269] [NEW] Upgrading LibreOffice 7 on Ubuntu 20.04 reset app and settings
Public bug reported: Hi everyone, I have a problem with LibreOffice 7.3, every time I upgrade the snap app it will reset my LibreOffice settings, recent files and extensions! Does anyone has the same problem? Some details: snap 2.55.3 snapd 2.55.3 series 16 ubuntu 20.04 kernel 5.14.0-1036-oem Description:Ubuntu 20.04.4 LTS Release:20.04 libreoffice 7.3.3.2 254 latest/stable canonical✓ - ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: focal libreoffice ** Tags added: libreoffice ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973269 Title: Upgrading LibreOffice 7 on Ubuntu 20.04 reset app and settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1973269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972093] [NEW] Notification empties at reboot
Public bug reported: Notification empties at reboot. I had ro remove and add again the plugin to show notifications ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xfce4-notifyd 0.6.3-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: 8821ce ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun May 8 13:09:34 2022 InstallationDate: Installed on 2021-01-23 (469 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=it_IT TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-notifyd UpgradeStatus: Upgraded to jammy on 2022-04-05 (32 days ago) ** Affects: xfce4-notifyd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972093 Title: Notification empties at reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1972093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972091] [NEW] rtl8821ce wifi not working ubuntu 22.04
Public bug reported: rtl8821ce wifi not working ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rtl8821ce-dkms 5.5.2.1-0ubuntu10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: 8821ce ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun May 8 12:57:11 2022 InstallationDate: Installed on 2021-01-23 (469 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=it_IT TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: rtl8821ce UpgradeStatus: Upgraded to jammy on 2022-04-05 (32 days ago) ** Affects: rtl8821ce (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972091 Title: rtl8821ce wifi not working ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1972091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970251] [NEW] panel notification sometimes not working
Public bug reported: panel notification sometimes not working. I had to remove and add again the plugin. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xfce4-notifyd 0.6.3-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Apr 25 19:33:08 2022 InstallationDate: Installed on 2021-01-23 (457 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=it_IT TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-notifyd UpgradeStatus: Upgraded to jammy on 2022-04-05 (19 days ago) ** Affects: xfce4-notifyd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970251 Title: panel notification sometimes not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-notifyd/+bug/1970251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967484] Re: Tomcat9 April 1st update resets tomcat9.service file
Sorry, I have reported the incorrect package version. The correct one is: 9.0.16-3ubuntu0.18.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967484 Title: Tomcat9 April 1st update resets tomcat9.service file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967484] [NEW] Tomcat9 April 1st update resets tomcat9.service file
Public bug reported: The lastest update of the tomcat9 package on my Ubuntu 18.04 systems that run this morning has reset the /lib/systemd/system/tomcat9.service file causing the loss of the ReadWritePaths entries I added, causing several webservices running in my tomcat9 instance to not being able to write in specified directories. The package version is: 9.0.16-3ubuntu0.18.04.1 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967484 Title: Tomcat9 April 1st update resets tomcat9.service file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960643] [NEW] wifi adapter sometimes not working after startup
Public bug reported: 1) Description:Ubuntu 20.04.3 LTS Release:20.04 2) ii iw 5.4-1 amd64tool for configuring Linux wireless devices 3) wifi adapter working on every boot 4) Sometimes wifi does not work after booting and I need to restart laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-oem-20.04b 5.10.0.1057.57 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 11 16:17:11 2022 InstallationDate: Installed on 2021-02-03 (373 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-meta-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960643 Title: wifi adapter sometimes not working after startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.10/+bug/1960643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586528] Re: Avahi-daemon withdraws address record
I've just seen this issue the first time on a Ubuntu 20.04 (updated several months ago from 16.04) AWS EC2 machine. Looking closer into this, the machine lost its IP address multiple times in the last hours. The following avahi-daemon log messages made me find this bug report: ck@focal:~$ grep avahi-daemon /var/log/syslog | grep -i withdrawing Jan 18 20:17:42 inf-mon04-p avahi-daemon[941]: Withdrawing address record for 10.10.1.41 on eth0. Jan 18 21:44:52 inf-mon04-p avahi-daemon[941]: Withdrawing address record for 10.10.1.41 on eth0. It's very interesting, that both of these events happened EXACTLY one hour after the system boot: ck@focal:~$ last | head ck pts/0xx.xx.xx.xxx Tue Jan 18 22:11 still logged in root ttyS0 Tue Jan 18 21:50 still logged in reboot system boot 5.4.0-91-generic Tue Jan 18 20:44 still running reboot system boot 5.4.0-91-generic Tue Jan 18 19:17 - 20:39 (01:22) Running "dhclient" on the EC2 console, as suggested in comment #46, re- assigns the IP address. Relevant versions installed: ck@focal:~$ dpkg -l|egrep "(dhcp|network-manager)" ii isc-dhcp-client 4.4.1-2.1ubuntu5.20.04.2 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.4.1-2.1ubuntu5.20.04.2 amd64common manpages relevant to all of the isc-dhcp packages ii network-manager 1.22.10-1ubuntu2.2 amd64network management framework (daemon and userspace tools) ii network-manager-gnome1.8.24-1ubuntu3 amd64network management framework (GNOME frontend) ii network-manager-pptp 1.2.8-2 amd64network management framework (PPTP plugin core) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953595] [NEW] Executable h5c++ is not in the expected location
Public bug reported: I have installed libhdf5-mpi-dev (version 1.10.6+repack-5), which depends on libhdf5-openmpi-dev (version 1.10.6+repack-5). Package libhdf5-openmpi-dev currently seems to use update-alternatives to create a symlink from /usr/bin/h5pcc to the installed HDF5 C compiler wrapper at /usr/bin/h5pcc.openmpi. However the package doesn't seem to create a matching symlink for the HDF5 C++ compiler wrapper, that is it doesn't create a symlink from /usr/bin/h5c++ to /usr/bin/h5c++.openmpi. This results in a confusing scenario where the HDF5 C compiler wrapper can be invoked using command h5pcc but the HDF5 C++ compiler wrapper can only be invoked using command h5c++.openmpi. The current behaviour also breaks building HDF5 C++ programs using CMake because CMake expects the HDF5 C++ compiler wrapper to be available as h5c++. It is possible that the inability to invoke the HDF5 C++ compiler wrapper as h5c++ breaks other things that I'm unaware of. Because I'm using Ubuntu to compile HDF5 C++ programs, I've worked around the issue by creating a similar symlink manually using command: update-alternatives --install /usr/local/bin/h5c++ h5c++ /usr/bin/h5c++.openmpi 40 Creating the symlink using the above command has also fixed building HDF5 C++ programs using CMake. I think libhdf5-openmpi-dev should be updated to automatically symlink h5c++ just as it currently symlinks h5pcc. I have used Ubuntu 21.10 (Impish Indri) to reproduce this issue. Please note that I have used Ubuntu via the official Docker image, but I'm sure this issue is reproducible on a proper installation as well. ** Affects: hdf5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953595 Title: Executable h5c++ is not in the expected location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdf5/+bug/1953595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950751] Re: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart)
> I see you run "service docker stop" before deleting the contents of "/var/lib/docker" but I do not see that in your first example, service docker stop is part of the general clean up strategies, for Rancher related Docker hosts anyway (see https://www.claudiokuenzler.com/blog/674/reset-clean-up-a-rancher- docker-host). So yes, this command definitely happened. The command would also throw a ton of errors, if Docker service would still be running due to busy/opened files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950751 Title: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1950751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950751] [NEW] docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart)
Public bug reported: Dear maintainers, I noticed a changed behaviour when starting the Docker service after the docker.io package was upgraded from 19.3.6 to 20.10.7. When the Docker host was reset/cleaned, which involves a 'rm -rf /var/lib/docker/*', the sub-directories are not automatically created anymore after a start of the service: root@dockerhost:~# rm -rf /var/lib/docker/* root@dockerhost:~# service docker start root@dockerhost:~# ll /var/lib/docker/ total 0 Without these directories, Docker containers cannot be created. Example with a 'docker pull': root@dockerhost:~# docker pull rancher/rke-tools:v0.1.78 v0.1.78: Pulling from rancher/rke-tools 540db60ca938: Pulling fs layer 0ae30075c5da: Pulling fs layer 9da81141e74e: Pulling fs layer b2e41dd2ded0: Pulling fs layer 7f40e809fb2d: Pulling fs layer 758848c48411: Pulling fs layer 4aa8101d7589: Pulling fs layer 68bd44136930: Pulling fs layer ae3790b81ced: Pulling fs layer f9c62a2baf95: Pulling fs layer 759049e20249: Pulling fs layer 6713b6a87a77: Pulling fs layer e1631138f00b: Pulling fs layer 063b41c39c12: Pulling fs layer c7844f3999c4: Pulling fs layer d8473758fa62: Pulling fs layer f83b3d05af4e: Pulling fs layer open /var/lib/docker/tmp/GetImageBlob573083372: no such file or directory However a restart does re-create the missing folders: root@dockerhost:~# service docker restart root@dockerhost:~# ll /var/lib/docker/ total 44 drwx--x--x 4 root root 4096 Nov 11 13:49 buildkit drwx--x--- 2 root root 4096 Nov 11 13:49 containers drwx-- 3 root root 4096 Nov 11 13:49 image drwxr-x--- 3 root root 4096 Nov 11 13:49 network drwx--x--- 3 root root 4096 Nov 11 13:49 overlay2 drwx-- 4 root root 4096 Nov 11 13:49 plugins drwx-- 2 root root 4096 Nov 11 13:49 runtimes drwx-- 2 root root 4096 Nov 11 13:49 swarm drwx-- 2 root root 4096 Nov 11 13:49 tmp drwx-- 2 root root 4096 Nov 11 13:49 trust drwx-x 2 root root 4096 Nov 11 13:49 volumes This happens with docker.io 20.10.x on both Ubuntu 18.04 Bionic and 20.04 Focal. Compared to the behaviour of docker.io 19.3.x: root@focal:~# docker info | head Client: Debug Mode: false Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 19.03.8 root@focal:~# service docker stop root@focal:~# rm -rf /var/lib/docker/* root@focal:~# service docker start root@focal:~# ll /var/lib/docker/ drwx--x--x 14 root root 4096 Nov 12 07:33 ./ drwxr-xr-x 29 root root 4096 Oct 29 14:06 ../ drwx-- 2 root root 4096 Nov 12 07:33 builder/ drwx--x--x 4 root root 4096 Nov 12 07:33 buildkit/ drwx-- 2 root root 4096 Nov 12 07:33 containers/ drwx-- 3 root root 4096 Nov 12 07:33 image/ drwxr-x--- 3 root root 4096 Nov 12 07:33 network/ drwx-- 3 root root 4096 Nov 12 07:33 overlay2/ drwx-- 4 root root 4096 Nov 12 07:33 plugins/ drwx-- 2 root root 4096 Nov 12 07:33 runtimes/ drwx-- 2 root root 4096 Nov 12 07:33 swarm/ drwx-- 2 root root 4096 Nov 12 07:33 tmp/ drwx-- 2 root root 4096 Nov 12 07:33 trust/ drwx-- 2 root root 4096 Nov 12 07:33 volumes/ Conclusion: The start script in docker.io 20.10.x should create the sub- directories in /var/lib/docker if they are missing (same as service restart). cheers, ck ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950751 Title: docker.io 20.10.x does not create sub-directories in /var/lib/docker on start (but does on restart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1950751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
I got the same kernel panic error showed in the "S13 kernel panic" image by Pietro Mingo (skar395). I workarounded the problem by entering the BIOS and disabling the trackpoint. The trackpad can remain active. This is not a solution, but it works. Please, forgive my bad English -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944065] Re: Invalid multiple red dots when Android Studio is running
there are also some others problems: if I've a simulator launched(android simulator) I can't launch a new instance of the Studio. Example: open AS, run Simultaor, close AS(the simulator remain active) -> click on icon -> no choice allowed (not possible to run a new AS instance) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944065 Title: Invalid multiple red dots when Android Studio is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1944065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944065] Re: invalid multiple red dots android studio running
** Description changed: On ubuntu application bar I see multiple red dots like when I've many instances of the same app but instead of five(see the annexed image) I've only two. - My ubuntu data are: + My ubuntu system info: - Linux claudio-i7 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 + Linux claudio-i7 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 18.04.6 LTS Release: 18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944065 Title: invalid multiple red dots android studio running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1944065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944065] [NEW] invalid multiple red dots android studio running
Public bug reported: On ubuntu application bar I see multiple red dots like when I've many instances of the same app but instead of five(see the annexed image) I've only two. My ubuntu data are: Linux claudio-i7 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 18.04.6 LTS Release:18.04 Codename: bionic ** Affects: ubuntu Importance: Undecided Status: New ** Tags: android studio ** Attachment added: "Schermata da 2021-09-19 07-59-32.png" https://bugs.launchpad.net/bugs/1944065/+attachment/5526217/+files/Schermata%20da%202021-09-19%2007-59-32.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944065 Title: invalid multiple red dots android studio running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1944065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940525] Re: check_http regression, 2.2 ignores -k Host header
Or you can close this bug issue. I don't think that it's actually something Ubuntu/Canonical can do in this case. I might check with upstream but the workaround (combination of the two) works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940525 Title: check_http regression, 2.2 ignores -k Host header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940525] Re: check_http regression, 2.2 ignores -k Host header
Hi Robie Thx for checking. The problem with the host header set by -H parameter is that it automatically applies the port, if a port is used with the -p parameter. $ /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -H www.example.com -p 8083 -v GET / HTTP/1.1 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close Host: www.example.com:8083 (this can cause problems depending on the infrastructure, e.g. using load balancers forwarding the requested host header to the backend) To get rid of the port in the Host header, the workaround using -k and defining the "Host" header again has worked in the past. But it seems that by using a combination of -H and -k "Host" the previous behaviour can be established again: $ /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -p 8083 -k "Host: www.example.com" -H www.example.com -v |more GET / HTTP/1.1 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close Host: www.example.com So it's strange, that the "Host" header is ignored when using -k - but in combination with -H it works. I can live with that workaround but if you want to report it upstream let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940525 Title: check_http regression, 2.2 ignores -k Host header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940525] [NEW] check_http regression, 2.2 ignores -k Host header
Public bug reported: With Ubuntu 20.04 focal, the monitoring-plugins package is at version 2.2 This seems to have introduced a regression in the check_http plugin: When using -k parameter to set a "Host" header, this is ignored instead of used. In 2.1.2 on Ubuntu 16.04, the following behavior is seen: # /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -p 4007 -k "Host: www.example.com" -v |more GET / HTTP/1.0 User-Agent: check_http/v2.1.2 (monitoring-plugins 2.1.2) Connection: close Host: www.example.com Ubuntu 20.04 with monitoring-plugins 2.2: # /usr/lib/nagios/plugins/check_http -I 127.0.0.1 -p 4007 -k "Host: www.example.com" -v |more GET / HTTP/1.0 User-Agent: check_http/v2.2 (monitoring-plugins 2.2) Connection: close ** Affects: monitoring-plugins (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940525 Title: check_http regression, 2.2 ignores -k Host header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933396] [NEW] fwsnort rule blocks canonical ip
Public bug reported: am trying to update and I get the following error from synaptic: W: Failed to get http://archive.ubuntu.com/ubuntu/pool/main/l/linux-hwe-5.4 /linux-modules-extra-5.4.0-77-generic_5.4.0-77.86~18.04.1_amd64 .deb Connection failed [IP: 2001: 67c: 1360: 8001 :: 23 80] checking mutt mail I get psad crash alerts configured with fwsnort: Danger level: [2] (out of 5) Scanned TCP ports: [42400: 1 packets] TCP flags: [ACK: 1 packets] iptables chain: FWSNORT_INPUT_ESTAB (prefix "[401] REJ SID1797 ESTAB"), 1 packets fwsnort rule: 401 Source: 2001: 067c: 1360: 8001: : : : 0023 DNS: [No reverse dns info available] [+] TCP scan signatures: "PORN BDSM" dst port: 42400 (no server bound to local port) flags: ACK content: "BDSM" sid: 1797 chain: FWSNORT_INPUT_ESTAB packets: 1 classtype: kickass-porn and the same for ipv4 Danger level: [2] (out of 5) Scanned TCP ports: [51378: 1 packets] TCP flags: [ACK: 1 packets] iptables chain: FWSNORT_INPUT_ESTAB (prefix "[515] REJ SID1797 ESTAB"), 1 packets fwsnort rule: 515 Source: 91.189.88.152 DNS: [No reverse dns info available] [+] TCP scan signatures: "PORN BDSM" dst port: 51378 (no server bound to local port) flags: ACK content: "BDSM" sid: 1797 chain: FWSNORT_INPUT_ESTAB packets: 1 classtype: kickass-porn I am trying to download the file http://archive.ubuntu.com/ubuntu/pool/main/l/linux-hwe-5.4/linux- modules-extra-5.4.0-77-generic_5.4.0-77.86~18.04.1_amd64. deb from brave browser manually and the malwarebyte extension blocks the download as a suspicious site. Could I be facing a DNS hijacking? or consider this a bug and disable psad-fwsnort and update without risk of infecting my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.44 ProcVersionSignature: Ubuntu 5.4.0-74.83~18.04.1-generic 5.4.114 Uname: Linux 5.4.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 20:33:55 2021 InstallationDate: Installed on 2020-04-16 (433 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933396 Title: fwsnort rule blocks canonical ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1933396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931380] Re: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child
Same as last comment of user iononsbalgiomai for me. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931380 Title: Snap-store fails to launch - libgtk-3.so.0: undefined symbol: atk_plug_set_child To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1931380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897561] Re: libperl.so.5.30.0 causes nginx to segfault
Can confirm, this bug is still a reality in Ubuntu 20.04 (focal) and is triggered by two reloads in a row. root@nginx:~# ps aux|grep nginx root 3356067 0.0 0.1 71600 9788 ?Ss 15:46 0:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; www-data 3356068 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356069 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356070 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356071 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356072 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356073 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356074 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process www-data 3356075 0.0 0.1 73012 15348 ?S15:46 0:00 nginx: worker process root 3356102 0.0 0.0 8900 676 pts/0S+ 15:46 0:00 grep --color=auto nginx root@nginx:~# service nginx reload root@nginx:~# ps aux|grep nginx root 3356067 0.2 0.3 81404 28848 ?Ss 15:46 0:00 nginx: master process /usr/sbin/nginx -g daemon on; master_process on; www-data 3356266 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356267 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356268 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356269 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356270 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356271 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356272 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process www-data 3356273 0.0 0.2 81644 22608 ?S15:46 0:00 nginx: worker process root 3356296 0.0 0.0 17196 7168 ?R15:46 0:00 /usr/bin/pgrep nginx root 3356309 0.0 0.0 8900 736 pts/0S+ 15:46 0:00 grep --color=auto nginx root@nginx:~# service nginx reload root@nginx:~# ps aux|grep nginx root 3356355 0.0 0.0 8900 736 pts/0S+ 15:46 0:00 grep --color=auto nginx At the time of the second reload, the following segfault is logged in /var/log/kern.log: May 4 15:46:50 onl-paylb02-p kernel: [4141537.262674] nginx[3356067]: segfault at 51 ip 7f6b7d1535c9 sp 7ffe634334d0 error 4 in libperl.so.5.30.0[7f6b7d0eb000+166000] May 4 15:46:50 onl-paylb02-p kernel: [4141537.262681] Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76 10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83 39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897561 Title: libperl.so.5.30.0 causes nginx to segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1897561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917682] Re: rules url error fwsnort
changing the address from http to https seems to fix psad's crash, but i still get data from unconfigured servers in: /etc/fwsnort/fwsnort.conf ### AOL AIM server nets AIM_SERVERS [64.12.24.0/24, 64.12.25.0/24, 64.12.26.14/24, 64.12.28.0/24, 64.12.29.0/24, 64.12.161.0/24, 64.12.163.0/24, 205.188.5.0/24, 205.188.9.0/24]; sudo fwsnort --update-rules [+] Downloading latest rules into /etc/fwsnort/snort_rules/--2021-03-13 12:23:40-- https://rules.emergingthreats.net/open/snort-2.9.0/emerging-all.rules Resolviendo rules.emergingthreats.net (rules.emergingthreats.net)... 18.214.66.196, 23.21.164.163 Conectando con rules.emergingthreats.net (rules.emergingthreats.net)[18.214.66.196]:443... conectado. Petición HTTP enviada, esperando respuesta... 200 OK Longitud: 17054303 (16M) [text/plain] Guardando como: “emerging-all.rules” emerging-all.rules 100%[=>] 16,26M 509KB/sen 30s 2021-03-13 12:24:11 (551 KB/s) - “emerging-all.rules” guardado [17054303/17054303] [+] Finished. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917682 Title: rules url error fwsnort To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwsnort/+bug/1917682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917682] Re: rules url error fwsnort
** Changed in: fwsnort (Ubuntu) Assignee: (unassigned) => claudio javier fernandez (cjfjavier) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917682 Title: rules url error fwsnort To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwsnort/+bug/1917682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917682] Re: rules url error fwsnort
** Changed in: fwsnort (Ubuntu) Status: Incomplete => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/fwsnort/+question/696031 ** Description changed: psad detects the default url of fwsnort rules and blocks the ip when executing the following commands the ip addresses do not correspond to the servers configured in the fwsnort and psad files - sudo psad --sig-update + EDIT (sudo psad --sig-update) corrected sudo fwsnort --update-rules Resolviendo rules.emergingthreats.net (rules.emergingthreats.net)... 23.21.164.163, 18.214.66.196 Conectando con rules.emergingthreats.net (rules.emergingthreats.net)[23.21.164.163]:80... falló: Expiró el tiempo de conexión. Conectando con rules.emergingthreats.net (rules.emergingthreats.net)[18.214.66.196]:80... ^C[-] Could not download emerging-all.rules file. [*] Could not move emerging-all.rules -> emerging-all.rules.tmp at /usr/sbin/fwsnort line 4387. I receive mail alert in mutt Subject: [psad-status] tcpwrappers AUTO-BLOCK against 18.214.66.196 Subject: [psad-status] tcpwrappers AUTO-BLOCK against 23.21.164.163 added iptables auto-block against 18.214.66.196 added iptables auto-block against 23.21.164.163 Danger level: [2] (out of 5) Scanned TCP ports: [48356: 1 packets] TCP flags: [ACK: 1 packets] iptables chain: FWSNORT_INPUT_ESTAB (prefix "[498] REJ SID1310 ESTAB"), 1 packets fwsnort rule: 498 Source: 18.214.66.196 DNS: ec2-18-214-66-196.compute-1.amazonaws.com MAC: [+] TCP scan signatures: "PORN free XXX" dst port: 48356 (no server bound to local port) flags: ACK content: "FREE XXX" sid: 1310 chain: FWSNORT_INPUT_ESTAB packets: 1 classtype: kickass-porn - Danger level: [2] (out of 5) Scanned TCP ports: [54500: 2 packets] TCP flags: [ACK: 2 packets] iptables chain: FWSNORT_INPUT_ESTAB (prefix "[514] REJ SID1795 ESTAB"), 1 packets fwsnort rule: 514 iptables chain: FWSNORT_INPUT_ESTAB (prefix "[93] REJ SID10105 ESTAB"), 1 packets fwsnort rule: 93 Source: 23.21.164.163 DNS: ec2-23-21-164-163.compute-1.amazonaws.com MAC: [+] TCP scan signatures: "PORN ejaculation" dst port: 54500 (no server bound to local port) flags: ACK content: "ejaculat" sid: 1795 chain: FWSNORT_INPUT_ESTAB packets: 1 classtype: kickass-porn "COMMUNITY INAPPROPRIATE lolita sex" dst port: 54500 (no server bound to local port) flags: ACK content: "lolita" content: "sex" sid: 10105 chain: FWSNORT_INPUT_ESTAB packets: 1 classtype: kickass-porn /etc/psad/psad.conf AOL AIM server nets AIM_SERVERS [64.12.24.0/24, 64.12.25.0/24, 64.12.26.14/24, 64.12.28.0/24, 64.12.29.0/24, 64.12.161.0/24, 64.12.163.0/24, 205.188.5.0/24, 205.188.9.0/24]; /etc/fwsnort/fwsnort.conf ### AOL AIM server nets AIM_SERVERS [64.12.24.0/24, 64.12.25.0/24, 64.12.26.14/24, 64.12.28.0/24, 64.12.29.0/24, 64.12.161.0/24, 64.12.163.0/24, 205.188.5.0/24, 205.188.9.0/24]; --- ubuntu Linux 5.4.0-66-generic #74~18.04.2-Ubuntu SMP Fri Feb 5 11:17:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy fwsnort fwsnort: Instalados: 1.6.7-3 Candidato: 1.6.7-3 Tabla de versión: *** 1.6.7-3 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status apt-cache policy psad psad: Instalados: 2.4.3-1.2 Candidato: 2.4.3-1.2 Tabla de versión: *** 2.4.3-1.2 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fwsnort 1.6.7-3 ProcVersionSignature: Ubuntu 5.4.0-66.74~18.04.2-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 3 20:12:08 2021 InstallationDate: Installed on 2020-04-16 (321 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: fwsnort UpgradeStatus: No upgrade log present (probably fresh install) edit:psad corrected without changing configuration
[Bug 1917682] Re: rules url error fwsnort
** Description changed: + psad detects the default url of fwsnort rules and blocks the ip - psad detects the default url of fwsnort rules and blocks the ip + + when executing the following commands the ip addresses do not correspond to the servers configured in the fwsnort and psad files sudo psad --sig-update + sudo fwsnort --update-rules - Resolviendo rules.emergingthreats.net (rules.emergingthreats.net)... 23.21.164.163, 18.214.66.196 Conectando con rules.emergingthreats.net (rules.emergingthreats.net)[23.21.164.163]:80... falló: Expiró el tiempo de conexión. Conectando con rules.emergingthreats.net (rules.emergingthreats.net)[18.214.66.196]:80... ^C[-] Could not download emerging-all.rules file. [*] Could not move emerging-all.rules -> emerging-all.rules.tmp at /usr/sbin/fwsnort line 4387. + I receive mail alert in mutt added iptables auto-block against 18.214.66.196 added iptables auto-block against 23.21.164.163 Danger level: [2] (out of 5) - Scanned TCP ports: [48356: 1 packets] - TCP flags: [ACK: 1 packets] -iptables chain: FWSNORT_INPUT_ESTAB (prefix "[498] REJ SID1310 ESTAB"), 1 packets - fwsnort rule: 498 + Scanned TCP ports: [48356: 1 packets] + TCP flags: [ACK: 1 packets] + iptables chain: FWSNORT_INPUT_ESTAB (prefix "[498] REJ SID1310 ESTAB"), 1 packets + fwsnort rule: 498 -Source: 18.214.66.196 - DNS: ec2-18-214-66-196.compute-1.amazonaws.com - MAC: 8c:c5:b4:dd:fe:e0 + Source: 18.214.66.196 + DNS: ec2-18-214-66-196.compute-1.amazonaws.com + MAC: 8c:c5:b4:dd:fe:e0 [+] TCP scan signatures: -"PORN free XXX" -dst port: 48356 (no server bound to local port) -flags: ACK -content: "FREE XXX" -sid: 1310 -chain: FWSNORT_INPUT_ESTAB -packets: 1 -classtype: kickass-porn + "PORN free XXX" + dst port: 48356 (no server bound to local port) + flags: ACK + content: "FREE XXX" + sid: 1310 + chain: FWSNORT_INPUT_ESTAB + packets: 1 + classtype: kickass-porn - Danger level: [2] (out of 5) - Scanned TCP ports: [54500: 2 packets] - TCP flags: [ACK: 2 packets] -iptables chain: FWSNORT_INPUT_ESTAB (prefix "[514] REJ SID1795 ESTAB"), 1 packets - fwsnort rule: 514 -iptables chain: FWSNORT_INPUT_ESTAB (prefix "[93] REJ SID10105 ESTAB"), 1 packets - fwsnort rule: 93 + Scanned TCP ports: [54500: 2 packets] + TCP flags: [ACK: 2 packets] + iptables chain: FWSNORT_INPUT_ESTAB (prefix "[514] REJ SID1795 ESTAB"), 1 packets + fwsnort rule: 514 + iptables chain: FWSNORT_INPUT_ESTAB (prefix "[93] REJ SID10105 ESTAB"), 1 packets + fwsnort rule: 93 -Source: 23.21.164.163 - DNS: ec2-23-21-164-163.compute-1.amazonaws.com - MAC: 8c:c5:b4:dd:fe:e0 + Source: 23.21.164.163 + DNS: ec2-23-21-164-163.compute-1.amazonaws.com + MAC: 8c:c5:b4:dd:fe:e0 [+] TCP scan signatures: -"PORN ejaculation" -dst port: 54500 (no server bound to local port) -flags: ACK -content: "ejaculat" -sid: 1795 -chain: FWSNORT_INPUT_ESTAB -packets: 1 -classtype: kickass-porn + "PORN ejaculation" + dst port: 54500 (no server bound to local port) + flags: ACK + content: "ejaculat" + sid: 1795 + chain: FWSNORT_INPUT_ESTAB + packets: 1 + classtype: kickass-porn -"COMMUNITY INAPPROPRIATE lolita sex" -dst port: 54500 (no server bound to local port) -flags: ACK -content: "lolita" -content: "sex" -sid: 10105 -chain: FWSNORT_INPUT_ESTAB -packets: 1 -classtype: kickass-porn + "COMMUNITY INAPPROPRIATE lolita sex" + dst port: 54500 (no server bound to local port) + flags: ACK + content: "lolita" + content: "sex" + sid: 10105 + chain: FWSNORT_INPUT_ESTAB + packets: 1 + classtype: kickass-porn - /etc/psad/psad.conf + /etc/psad/psad.conf AOL AIM server nets - AIM_SERVERS [64.12.24.0/24, 64.12.25.0/24, 64.12.26.14/24, 64.12.28.0/24, 64.12.29.0/24, + AIM_SERVERS [64.12.24.0/24, 64.12.25.0/24, 64.12.26.14/24, 64.12.28.0/24, 64.12.29.0/24, 64.12.161.0/24, 64.12.163.0/24, 205.188.5.0/24, 205.188.9.0/24]; - /etc/fwsnort/fwsnort.conf ### AOL AIM server nets
Re: [Bug 1917682] Re: rules url error fwsnort
Thank you for your response and sorry for the delay in my response, changed to public, good morning El mar, 9 de mar. de 2021 a la(s) 09:00, Marc Deslauriers ( 1917...@bugs.launchpad.net) escribió: > Thanks for reporting this issue. Can I make this bug public so that the > fwsnort community can see it and possibly fix the issue? > > ** Changed in: fwsnort (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1917682 > > Title: > rules url error fwsnort > > Status in fwsnort package in Ubuntu: > Incomplete > > Bug description: > > psad detects the default url of fwsnort rules and blocks the ip > > sudo psad --sig-update > > sudo fwsnort --update-rules > > > Resolviendo rules.emergingthreats.net (rules.emergingthreats.net)... > 23.21.164.163, 18.214.66.196 > Conectando con rules.emergingthreats.net > (rules.emergingthreats.net)[23.21.164.163]:80... > falló: Expiró el tiempo de conexión. > Conectando con rules.emergingthreats.net > (rules.emergingthreats.net)[18.214.66.196]:80... > ^C[-] Could not download emerging-all.rules file. > [*] Could not move emerging-all.rules -> emerging-all.rules.tmp at > /usr/sbin/fwsnort line 4387. > > > added iptables auto-block against 18.214.66.196 > > added iptables auto-block against 23.21.164.163 > > Danger level: [2] (out of 5) > > Scanned TCP ports: [48356: 1 packets] > TCP flags: [ACK: 1 packets] > iptables chain: FWSNORT_INPUT_ESTAB (prefix "[498] REJ SID1310 > ESTAB"), 1 packets >fwsnort rule: 498 > > Source: 18.214.66.196 > DNS: ec2-18-214-66-196.compute-1.amazonaws.com > MAC: 8c:c5:b4:dd:fe:e0 > [+] TCP scan signatures: > > "PORN free XXX" > dst port: 48356 (no server bound to local port) > flags: ACK > content: "FREE XXX" > sid: 1310 > chain: FWSNORT_INPUT_ESTAB > packets: 1 > classtype: kickass-porn > - > > Danger level: [2] (out of 5) > > Scanned TCP ports: [54500: 2 packets] > TCP flags: [ACK: 2 packets] > iptables chain: FWSNORT_INPUT_ESTAB (prefix "[514] REJ SID1795 > ESTAB"), 1 packets >fwsnort rule: 514 > iptables chain: FWSNORT_INPUT_ESTAB (prefix "[93] REJ > SID10105 ESTAB"), 1 packets >fwsnort rule: 93 > > Source: 23.21.164.163 > DNS: ec2-23-21-164-163.compute-1.amazonaws.com > MAC: 8c:c5:b4:dd:fe:e0 > > [+] TCP scan signatures: > > "PORN ejaculation" > dst port: 54500 (no server bound to local port) > flags: ACK > content: "ejaculat" > sid: 1795 > chain: FWSNORT_INPUT_ESTAB > packets: 1 > classtype: kickass-porn > > "COMMUNITY INAPPROPRIATE lolita sex" > dst port: 54500 (no server bound to local port) > flags: ACK > content: "lolita" > content: "sex" > sid: 10105 > chain: FWSNORT_INPUT_ESTAB > packets: 1 > classtype: kickass-porn > > >/etc/psad/psad.conf > AOL AIM server nets > AIM_SERVERS [64.12.24.0/24, 64.12.25.0/24, > 64.12.26.14/24, 64.12.28.0/24, 64.12.29.0/24, > 64.12.161.0/24, 64.12.163.0/24, 205.188.5.0/24, 205.188.9.0/24]; > > > /etc/fwsnort/fwsnort.conf > ### AOL AIM server nets > AIM_SERVERS [64.12.24.0/24, 64.12.25.0/24, 64.12.26.14/24, > 64.12.28.0/24, 64.12.29.0/24, >64.12.161.0/24, 64.12.163.0/24, 205.188.5.0/24, 205.188.9.0/24]; > --- > > ubuntu Linux 5.4.0-66-generic #74~18.04.2-Ubuntu SMP Fri Feb 5 > 11:17:31 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > > apt-cache policy fwsnort > fwsnort: > Instalados: 1.6.7-3 > Candidato: 1.6.7-3 > Tabla de versión: >*** 1.6.7-3 500 > 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 > Packages > 500 http://archive.ubuntu.com/ubuntu bionic/universe i386 > Packages > 100 /var/lib/dpkg/status > > apt-cache policy psad > psad: > Instalados: 2.4.3-1.2 > Candidato: 2.4.3-1.2 > Tabla de versión: >*** 2.4.3-1.2 500 > 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 > Packages > 100 /var/lib/dpkg/status > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: fwsnort 1.6.7-3 > ProcVersionSignature: Ubuntu 5.4.0-66.74~18.04.2-generic 5.4.86 > Uname: Linux 5.4.0-66-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.23 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Mar 3
[Bug 1917682] Re: rules url error fwsnort
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917682 Title: rules url error fwsnort To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwsnort/+bug/1917682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917769] [NEW] fresh installation
Public bug reported: grub error message ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckMismatches: ./dists/groovy/main/binary-amd64/Packages.gz CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 14:21:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917769 Title: fresh installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1917769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916639] Re: failed to write the boot onto EFI partition alongside Win7
my 100MB win reserved partition was visible on win as D: this is very unusual -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916639 Title: failed to write the boot onto EFI partition alongside Win7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916639] [NEW] failed to write the boot onto EFI partition alongside Win7
Public bug reported: After installation of Windows 7 ultimate onto SSD I shrinked the original size in order to make room for Ubuntu 2020-04 - the installation manager notified me that an EFI partition was need, I added it but the finalization failed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-ifr1-390_390.138-0ubuntu2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 23 14:49:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916639 Title: failed to write the boot onto EFI partition alongside Win7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879580] Re: Screencast interface missing
Chromimm output: [110445:110445:1013/141808.679718:ERROR:base_capturer_pipewire.cc(517)] Failed to create a screen cast session: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.portal.ScreenCast” on object at path /org/freedesktop/portal/desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879580] Re: Screencast interface missing
The build without `org.freedesktop.portal.ScreenCast` prevents e.g. Chrome/Chromium to share the desktop through MS teams when using Wayland, e.g. like it works on Fedora (https://uwot.eu/blog/microsoft- teams-on-fedora-and-wayland-with-screenshare/). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668891] Re: Can install non classic snap with --classic, but classic flag isn't set
** Changed in: snapd Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668891 Title: Can install non classic snap with --classic, but classic flag isn't set To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1668891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668891] Re: Can install non classic snap with --classic, but classic flag isn't set
@didrocks: installing a non-classic snap with --classic with current snapd issues the following warning. (Using --classic shouldn't override the package confinement, the flag is still ignored but not silently.) $ snap install word-salad --classic Warning: flag --classic ignored for strictly confined snap word-salad word-salad 0.1 from Alan Pope (popey) installed I'll close this bug as fix-released (this was addressed in 2.37), however if you feel this is not a proper solution please reopen. @pachulo: I can't reproduce the situation you describe (strictly confined snap seeing the real /). If this is still an issue, please open a new bug and it will be investigated. ** Changed in: snapd Status: Confirmed => Fix Released ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668891 Title: Can install non classic snap with --classic, but classic flag isn't set To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1668891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660316] Re: apparmor denial of CUPS
Same happens in 18.04 (Linux Mint 19.3). Needed to manually add the net_admin caps as mentioned by Jamie. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660316 Title: apparmor denial of CUPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1660316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314160] Re: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb
Still present in 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314160 Title: Apparmor profile violated: cupsd does mknod on /var/cache/samba/gencache.tdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1314160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.
Michael, could you confirm this was a cosmic-specific bug as there's a report of a similar problem with an upgrade from eoan to focal? ** Changed in: snapd Importance: Undecided => High ** Changed in: snapd Assignee: (unassigned) => Michael Vogt (mvo) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776622 Title: snapd updates on focal never finish installing. Can't install any other updates. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631514] Re: snap doesnt work. error: cannot communicate with server
This is a collection of bug reports and it seems that at least some of them are already solved either by manually enabling services or using newer versions of snapd. Are any of these issues still happening? ** Changed in: snapd Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631514 Title: snap doesnt work. error: cannot communicate with server To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1631514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860851] Re: blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte
Reproduced on Ubuntu 20.04. The error message appears starting or
stopping the bluetooth service ("sudo systemctl start bluetooth.service"
or ""sudo systemctl stop bluetooth.service"").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860851
Title:
blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't
decode byte 0x8e in position 4: invalid start byte
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1860851/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886113] Re: snap-store Does Not Run with XAUTHORITY error
** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886113 Title: snap-store Does Not Run with XAUTHORITY error To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1886113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886113] Re: snap-store Does Not Run with XAUTHORITY error
Thanks for reporting and sorry for not getting back to you earlier. It seems that we have a mismatch between the contents of the XAUTHORITY environment variable (under /home/william) and the actual location of the file on the filesystem (under /Moort/home/william) after resolving symlinks and cleaning the pathname. Are you symlinking an alternate home directory location to /home? Using an alternate location for home directories can be related to the other problems you've been experiencing. If you're using an alternate location, could you try to bind-mount this alternate location on /home? Reference: https://forum.snapcraft.io/t/how-can-i-use-snap-when-i-dont- use-home-user/3352/11 ** Changed in: snapd Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886113 Title: snap-store Does Not Run with XAUTHORITY error To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1886113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
** Changed in: snapd Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879290] Re: pc: no message on the screen for ~30s on fast HW
Result of systemd-analyze in both systems on the Thinkcentre machine: uc18: Startup finished in 30.880s (kernel) + 4.727s (userspace) = 35.608s graphical.target reached after 4.721s in userspace uc20: Startup finished in 38.338s (kernel) + 17.902s (userspace) = 56.240s graphical.target reached after 17.892s in userspace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879290 Title: pc: no message on the screen for ~30s on fast HW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882114] [NEW] do-release-upgrade -d fails. Upgrading from Ubuntu 18.04 to 20.04
Public bug reported: I get the following message when trying the upgrade. It doesn't seem to be transient, I've tried several times. An unresolvable problem occurred while calculating the upgrade. This was caused by: * Upgrading to a pre-release version of Ubuntu This is most likely a transient problem, please try again later. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CrashDB: ubuntu Date: Thu Jun 4 13:10:51 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-06-04 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882114 Title: do-release-upgrade -d fails. Upgrading from Ubuntu 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1882114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877752] Re: No sound from headphones if inserted after boot
Fixed with this ppa https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877752 Title: No sound from headphones if inserted after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1877752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877752] Re: No sound from headphones if inserted after boot
With the command alsactl restore the sound works again. If I disconnect and reconnect the audio jack the sound is off again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877752 Title: No sound from headphones if inserted after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1877752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746429] Re: System crash at boot when the computer previously was hibernate
** Changed in: hibernate (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hibernate (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746429 Title: System crash at boot when the computer previously was hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hibernate/+bug/1746429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746613] Re: freezes after resuming from disk hibernation
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746613 Title: freezes after resuming from disk hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821686] Re: wrapper-2.0 crashed with SIGSEGV in g_list_foreach()
** Changed in: xfce4-panel (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821686 Title: wrapper-2.0 crashed with SIGSEGV in g_list_foreach() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1821686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761128] Re: [TOSHIBA Satellite Pro L350] hibernate/resume failure
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761128 Title: [TOSHIBA Satellite Pro L350] hibernate/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)
I tested the chromium snap (1165) on a focal machine with IPv6 and
couldn't reproduce DNS lookup problems. I did, however, find a
difference between this chromium and unconfined chrome when handling
IPv6 large packets (unconfined chrome works as expects and chromium
times out).
Unconfined chrome output:
Test with IPv4 DNS record ok (0.032s) using ipv4
Test with IPv6 DNS record ok (0.034s) using ipv6
Test with Dual Stack DNS record ok (0.039s) using ipv6
Test for Dual Stack DNS and large packet ok (0.043s) using ipv6
Test IPv4 without DNS ok (0.033s) using ipv4
Test IPv6 without DNS ok (0.048s) using ipv6
Test IPv6 large packet ok (0.046s) using ipv6
Test if your ISP's DNS server uses IPv6 ok (0.052s) using ipv6
Find IPv4 Service Provider ok (0.447s) using ipv4 ASN 14868
Find IPv6 Service Provider ok (0.398s) using ipv6 ASN 14868
Chromium from snap:
Test with IPv4 DNS record ok (0.140s) using ipv4
Test with IPv6 DNS record ok (0.142s) using ipv6
Test with Dual Stack DNS record ok (0.159s) using ipv6
Test for Dual Stack DNS and large packet ok (0.094s) using ipv6
Test IPv4 without DNS skipped (0.087s)
Test IPv6 without DNS skipped (0.155s)
Test IPv6 large packet timeout (15.011s)
Test if your ISP's DNS server uses IPv6 ok (0.194s) using ipv6
Find IPv4 Service Provider ok (0.222s) using ipv4 ASN 14868
Find IPv6 Service Provider ok (0.208s) using ipv6 ASN 14868
Test IPv6 large packet description:
Validates that IPv6 requests with large packets work. If this test times out,
but other IPv6 tests work, it suggests that there may be PMTUD issues; possibly
involving IP tunnels. Double check to make sure that ICMPv6 Type 2 ("Packet Too
Big") messages are not filtered by your firewall.
Test us from https://test-ipv6.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876083
Title:
chromium snap from focal fails DNS lookups, or delays them (ipv6)
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1876083/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879630] Re: No sound output from HDMI audio
** Changed in: snapd Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879630 Title: No sound output from HDMI audio To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1879630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879630] Re: No sound output from HDMI audio
Thanks Vic. I see from logs that the HDA codec is an ALC 233, which happens to be the same Realtek HDA codec I have in my Lenovo Thinkcentre machine that's running UC20 20200529.3. Unfortunately my Thinkcentre doesn't have any HDMI ports, but I was able to send sound through one of the displayports. It's interesting to note that, despite being the same kernel and same codec, the log messages seem different (for instance, I didn't see SOF messages in your logs. Here I see something like: Jun 01 20:06:33 stormfly kernel: sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 (...) Jun 01 20:06:33 stormfly kernel: sof-audio-pci :00:1f.3: hda codecs found, mask 5 Jun 01 20:06:33 stormfly kernel: sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now To send audio to my displayport, I used something like: # aplay -D hw:sofhdadsp,5 -f S16_LE -c 2 /bin/ls (or, to play music instead of noise, mpg123-cm.mpg123 -o alsa -a hw:sofhdasp,5 test.mp3) In amixer, my device is 'PGA9.0 9 Master'. I wonder if the IEC958 in your mixer settings could be a digital audio output such as a S/PDIF port or something similar? Could you post the output of # aplay -l and # aplay -L so we can see the all the available cards/devices? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879630 Title: No sound output from HDMI audio To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1879630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878541] Re: Grub fails to load kernel from squashfs if mem < 1500mb
Chris Coulson's patch should also solve the problem that breaks install on the Thinkcentre m920s with TPM enabled. The last printed message when booting with grub debug enabled is the type of the loopback file, and nothing happens after that. It finishes installing if you rmmod tpm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878541 Title: Grub fails to load kernel from squashfs if mem < 1500mb To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1878541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831629] Re: snapd hammers SSD for long periods
I experienced a similar problem, with constant disk writing at low rate (few hundred KB/s) and after inspecting the snapd process running on a container we found the following: root@focal:/# snap changes ID Status Spawn Ready Summary 234 Doing 2 days ago, at 16:40 UTC - Auto-refresh snap "snapd" root@focal:/# snap change 234 Status Spawn Ready Summary Done2 days ago, at 16:40 UTC 2 days ago, at 16:40 UTC Ensure prerequisites for "snapd" are available Doing 2 days ago, at 16:40 UTC - Download snap "snapd" (8008) from channel "latest/edge" (8.71%) Do 2 days ago, at 16:40 UTC - Fetch and check assertions for snap "snapd" (8008) Do 2 days ago, at 16:40 UTC - Mount snap "snapd" (8008) Do 2 days ago, at 16:40 UTC - Run pre-refresh hook of "snapd" snap if present Do 2 days ago, at 16:40 UTC - Stop snap "snapd" services Do 2 days ago, at 16:40 UTC - Remove aliases for snap "snapd" Do 2 days ago, at 16:40 UTC - Make current revision for snap "snapd" unavailable Do 2 days ago, at 16:40 UTC - Copy snap "snapd" data Do 2 days ago, at 16:40 UTC - Setup snap "snapd" (8008) security profiles Do 2 days ago, at 16:40 UTC - Make snap "snapd" (8008) available to the system Do 2 days ago, at 16:40 UTC - Automatically connect eligible plugs and slots of snap "snapd" Do 2 days ago, at 16:40 UTC - Set automatic aliases for snap "snapd" Do 2 days ago, at 16:40 UTC - Setup snap "snapd" aliases Do 2 days ago, at 16:40 UTC - Run post-refresh hook of "snapd" snap if present Do 2 days ago, at 16:40 UTC - Start snap "snapd" (8008) services Do 2 days ago, at 16:40 UTC - Remove data for snap "snapd" (7988) Do 2 days ago, at 16:40 UTC - Remove snap "snapd" (7988) from the system Do 2 days ago, at 16:40 UTC - Clean up "snapd" (8008) install Do 2 days ago, at 16:40 UTC - Run health check of "snapd" snap Doing 2 days ago, at 16:40 UTC - Consider re-refresh of "snapd" The download is stalled at 8.71%. It's worth noting that I experienced connectivity issues two days ago and snap downloads were affected and they were very slow for a couple of hours before getting back to normal. ** Changed in: snapd (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831629 Title: snapd hammers SSD for long periods To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1831629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878928] Re: Call trace occurred when running `netplan apply` after an yaml is removed
Systems tested: qemu, rpi4 (1GB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878928 Title: Call trace occurred when running `netplan apply` after an yaml is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1878928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878928] Re: Call trace occurred when running `netplan apply` after an yaml is removed
Fix seems good, I couldn't reproduce this bug using core20 663/665 from edge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878928 Title: Call trace occurred when running `netplan apply` after an yaml is removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1878928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879290] Re: pc: no message on the screen for ~30s on fast HW
UC18 on the same hardware starts to display kernel messages at the 14s mark. UC18 logs shows no delay between the "console [tty1] enabled" and "console [ttyS0] enabled" messages, but otherwise the behavior is similar (blank screen for some time and slow output rate). [0.00] console [tty1] enabled [0.00] console [ttyS0] enabled ** Attachment added: "dmesg-thinkcentre-uc18.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879290/+attachment/5376576/+files/dmesg-thinkcentre-uc18.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879290 Title: pc: no message on the screen for ~30s on fast HW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879290] Re: pc: no message on the screen for ~30s on fast HW
I finally managed to install a beta image on a Thinkcentre m920 (by removing the tpm module in grub before booting). Console output appears at the 32s mark, see full dmesg below. Some interesting console-related excerpts: [0.049211] printk: console [tty1] enabled [ 14.088918] printk: console [ttyS0] enabled [ 17.020856] fbcon: Taking over console [ 32.840867] efifb: probing for efifb [ 32.883328] efifb: framebuffer at 0x4000, using 4128k, total 4128k ** Attachment added: "dmesg-thinkcentre-20200521.2.txt" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1879290/+attachment/5375226/+files/dmesg-thinkcentre-20200521.2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879290 Title: pc: no message on the screen for ~30s on fast HW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)
FYI I stumbled on this problem after a system update (which broke production!) and collected data in a troubleshooting session and documented this here https://www.claudiokuenzler.com/blog/959 /keepalived-virtual-ip-addresses-gone-lost-after-systemd-update. Once I found out the restart of systemd-networkd causes the keepalived vips to be gone, I finally came across this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815101 Title: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877752] [NEW] No sound from headphones if inserted after boot
Public bug reported: Heaphones works only if present at boot. If I insert the while computer is working or I remove and insert again they do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pavucontrol 4.0-1build1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 9 16:58:48 2020 InstallationDate: Installed on 2018-02-21 (807 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=it_IT TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pavucontrol UpgradeStatus: Upgraded to focal on 2020-05-02 (7 days ago) ** Affects: pavucontrol (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877752 Title: No sound from headphones if inserted after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1877752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877750] [NEW] Web camera not working in guest O.S. (Win 7 and Win10)
Public bug reported: I tried using skyper and Microsoft Teams in guest O.S. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox 6.1.6-dfsg-1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 9 16:53:02 2020 InstallationDate: Installed on 2018-02-21 (807 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=it_IT TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: Upgraded to focal on 2020-05-02 (7 days ago) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877750 Title: Web camera not working in guest O.S. (Win 7 and Win10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1877750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
The same bug affect my system xubuntu 20.04 over a DELL Precision 7510. Manufacturer: Dell Inc. Product Name: Precision 7510 Product Version: Firmware Version: 1.16.3 Board Vendor: Dell Inc. Board Name:02H5GH Kernel release:5.4.0-29-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes snd_hda_intel snd_hda_intel Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdfe48000 irq 141 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xdf08 irq 17 With nominal installation fully updated when plugged-in any headphone no sound at all. After the update of pulseaudio package as provided by https://launchpad.net/~kaihengfeng/+archive/ubuntu/fix-lp1869819 inserting a cheap no name headphone I'm able to hear the sound even if a rustle in background is present. Inserting a SADES game headset no sound only distorted noise is audible. To be noted that the pulsaudio mixer seems to work perfectly, having the headphone jack inserted I'm able to move the output sound to laptop speakers and move back but without fixing the problem. Last but not least the same configuration with xubuntu 16.04 worked perfectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870861] Re: chromium-browser is unable to open downloads
Also please include any additional information, if any, on how to reproduce this problem. Just downloading/opening a file worked correctly for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870861 Title: chromium-browser is unable to open downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1870861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870861] Re: chromium-browser is unable to open downloads
Thanks for reporting. The invalid opcode error seems odd, are you running on an uncommon architecture/cpu? Could you provide more information about the hardware you're running on such as the /proc/cpuinfo output? ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870861 Title: chromium-browser is unable to open downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1870861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762163] Re: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it
I tried your PPA and it fixes the issue, thank you Curtis. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762163 Title: [Kubuntu 18.04]Device notifier pretends it cannot mount usb device while actually mounting it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solid/+bug/1762163/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: How to handle tmpfiles.d in non-systemd environments
Hi Christian
According to https://www.debian.org/vote/2019/vote_002#outcome the
decision was to use "Systemd but we support exploring alternatives".
>From the proposal:
"Packages should include service units or init scripts to start daemons
and services. Packages may use any systemd facility at the package
maintainer's discretion, provided that this is consistent with other
Policy requirements and the normal expectation that packages shouldn't
depend on experimental or unsupported (in Debian) features of other
packages. Packages may include support for alternate init systems
besides systemd and may include alternatives for any systemd-specific
interfaces they use. Maintainers use their normal procedures for
deciding which patches to include."
>From my understanding this means that supporting an alternative init
system is optional ("Packages may include support for alternate init
systems besides systemd"). So basically this is up to the package
maintainer whether or not the package should support an alternative init
system.
Given the (still rising) popularity of Docker/Kubernetes containers, it
would indeed by very nice that the affected packages (such as haproxy)
do adjust for a non-systemd environment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855140
Title:
How to handle tmpfiles.d in non-systemd environments
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863210] [NEW] apache2 event mpm: keeps hanging in gracefully finishing when reloading (logrotate)
Public bug reported: This is Apache2 bug 53555 (https://bz.apache.org/bugzilla/show_bug.cgi?id=53555). It was fixed in 2.4.25 but on Ubuntu Xenial, Apache2 runs with 2.4.18 and the fix was not backported yet. This particular Apache2 setup runs with event mpm and is used as reverse proxy in front of a Tomcat (but that's irrelevant I guess). A daily log rotation happens on the Apache2 logs, causing an Apache2 reload (graceful restart). A check of apache-status each day confirms Apache bug 53555. February 4th: Current Time: Tuesday, 04-Feb-2020 17:19:28 CET Restart Time: Monday, 03-Feb-2020 09:20:48 CET Parent Server Config. Generation: 2 Parent Server MPM Generation: 1 Server uptime: 1 day 7 hours 58 minutes 39 seconds Server load: 0.00 0.00 0.00 Total accesses: 59027 - Total Traffic: 1.7 GB CPU Usage: u175.56 s424.83 cu0 cs0 - .522% CPU load .513 requests/sec - 15.7 kB/second - 30.6 kB/request 1 requests currently being processed, 49 idle workers PIDConnectionsThreads Async connections total accepting busy idle writing keep-alive closing 31339 1 no000 0 0 31340 1 no000 0 0 21534 0 yes 025 0 0 0 21535 0 yes 124 0 0 0 Sum 2 149 0 0 0 GG__ __W_ .. A couple of days later, February 7th: Current Time: Friday, 07-Feb-2020 14:06:52 CET Restart Time: Monday, 03-Feb-2020 09:20:48 CET Parent Server Config. Generation: 5 Parent Server MPM Generation: 4 Server uptime: 4 days 4 hours 46 minutes 3 seconds Server load: 0.00 0.00 0.00 Total accesses: 152913 - Total Traffic: 20.9 GB CPU Usage: u520.6 s1424.31 cu0 cs0 - .536% CPU load .422 requests/sec - 60.5 kB/second - 143.5 kB/request 1 requests currently being processed, 24 idle workers PIDConnectionsThreads Async connections total accepting busy idle writing keep-alive closing 31339 1 no000 0 0 31340 1 no000 0 0 11925 0 yes 124 0 0 0 21535 1 no000 0 0 4156 1 no000 0 0 29454 1 no000 0 0 Sum 5 124 0 0 0 GG__W___ ___G GG On February 8th, the remaining open slots were fully used and HTTP didn't respond anymore. Error logs filling up with the following message: "[mpm_event:error] [pid 5587:tid 139748587677568] AH00485: scoreboard is full, not at MaxRequestWorkers" Solution a) Update package to a newer upstream version for xenial-updates Solution b) Backport the fix from Apache bug 53555 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apache2 2.4.18-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 Apache2ConfdDirListing: False ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Fri Feb 14 07:43:55 2020 InstallationDate: Installed on 2017-01-26 (1113 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apache2 UpgradeStatus: No upgrade log present (probably fresh install) error.log: [Fri Feb 14 06:25:06.928096 2020] [ssl:warn] [pid 27506:tid 140172129879936] AH01909: mcp-somcwc01-p.nzzmg.local:443:0 server certificate does NOT include an ID which matches the server name [Fri Feb 14 06:25:06.930524 2020] [mpm_event:notice] [pid 27506:tid 140172129879936] AH00489: Apache/2.4.18 (Ubuntu) mod_jk/1.2.41 OpenSSL/1.0.2g configured -- resuming normal operations [Fri Feb 14 06:25:06.930532 2020] [core:notice] [pid 27506:tid 140172129879936] AH00094: Command line: '/usr/sbin/apache2' modified.conffile..etc.apache2.sites-available.000-default.conf: [modified] modified.conffile..etc.apache2.sites-available.default-ssl.conf: [modified] mtime.conffile..etc.apache2.sites-available.000-default.conf: 2017-02-14T07:38:24.570441 mtime.conffile..etc.apache2.sites-available.default-ssl.conf: 2018-04-09T15:47:05.141386 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863210 Title: apache2 event mpm: keeps hanging in gracefully finishing when reloading (logrotate) To manage notifications about this bug go to:
[Bug 1862642] Re: cannot use snapcraft to build snapd on focal
Assigned to Ian as a reminder to unblock PR #7904 once the prerequisites are cleared. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862642 Title: cannot use snapcraft to build snapd on focal To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1862642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862642] Re: cannot use snapcraft to build snapd on focal
** Changed in: snapd Status: New => In Progress ** Changed in: snapd Assignee: (unassigned) => Ian Johnson (anonymouse67) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862642 Title: cannot use snapcraft to build snapd on focal To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1862642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
This model file is used to build both the spread test image and the manually built image. The two generated images, however, seem to behave differently regarding the conditions leading to the crash: while it always happen in the spread test, higher KDF iteration times values allow the encrypted device to be opened correctly in the image created using the steps described in the bug description. Michael Vogt also reports that the crash doesn't happen in a classic system running the same kernel version. ** Attachment added: "Model file used to build the image" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+attachment/5321427/+files/ubuntu-core-20-amd64.model -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860231 Title: 5.4.0-11 crash on cryptsetup open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
Snap versions used to build the image: pc-kernel_374.snap pc_83.snap snapd_6113.snap core20_322.snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860231 Title: 5.4.0-11 crash on cryptsetup open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860231] Re: 5.4.0-11 crash on cryptsetup open
** Attachment added: "Screenshot of the procedure to trigger the crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+attachment/5321426/+files/Screenshot%20from%202020-01-18%2016-16-19.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860231 Title: 5.4.0-11 crash on cryptsetup open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860231] [NEW] 5.4.0-11 crash on cryptsetup open
Public bug reported: An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc- kernel_374.snap. Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Kernel backtrace" https://bugs.launchpad.net/bugs/1860231/+attachment/5321425/+files/trace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860231 Title: 5.4.0-11 crash on cryptsetup open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path in Docker container
Can't edit my comment (#2) so I just wanted to correct the sentence "That's (most likely) the reason why the official HAProxy docker image builds on Alpine Linux which uses Open RC as init system.". The official HAProxy Docker image runs on Debian but also supports Alpine Linux. The big difference there: They don't install HAProxy from a deb package but rather build HAProxy from source (during image build). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path in Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
Thanks, Christian, for your response. I agree, this might likely have a bigger impact than expected (I only figured this out after package analysis), because a lot of packages now depend on systemd for the package installation - yet systemd does not run in Docker. That's (most likely) the reason why the official HAProxy docker image builds on Alpine Linux which uses Open RC as init system. I could of course switch to Alpine but during early development phase of that container I wanted to use Ubuntu 18.04 for additional troubleshooting purposes. It will probably come down whether or not the Ubuntu packages officially support being installed/run in a Docker container or not. I can already imagine the fuss and heavily debated conversations about this topic :-/ . Let me know if I can be of help somehow. ** Summary changed: - haproxy package misses creation of default stats socket path + haproxy package misses creation of default stats socket path in Docker container -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path in Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
** Description changed: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners Starting HAProxy manually will show the following error: # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] After manual creation of the directory, the start works: # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg This can be reproduced with a simple Docker container the following Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy","-f","/etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 + + *** + + Update: After analysis of the haproxy package (see + https://www.claudiokuenzler.com/blog/917/haproxy-ubuntu-18.04-docker- + image-not-starting-cannot-bind-unix-socket), it turns out that the + /run/haproxy directory is defined in debian/haproxy.tmpfile. However + tmpfile's are only considered in systems with SystemD. As Docker + containers run without Systemd, this directory is never created. + + Suggestion: Do not rely on Systemd to create /run/haproxy. Maybe use + debian/haproxy.dirs? However the permissions are not set in this case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
** Description changed: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: - - stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners - + stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd + listeners Starting HAProxy manually will show the following error: - # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] - After manual creation of the directory, the start works: - # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg - - This can be reproduced with a simple Docker container the following Dockerfile: + This can be reproduced with a simple Docker container the following + Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy - CMD ["/usr/sbin/haproxy -c -f /etc/haproxy/haproxy.cfg"] + CMD ["/usr/sbin/haproxy","-f","/etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: - # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] Re: haproxy package misses creation of default stats socket path
** Summary changed: - haproxy package misses creation of default socket path + haproxy package misses creation of default stats socket path -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855140] [NEW] haproxy package misses creation of default stats socket path
Public bug reported: When installing the haproxy package from the current Ubuntu 18.04 Bionic repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file /etc/haproxy/haproxy.cfg: stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners Starting HAProxy manually will show the following error: # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] After manual creation of the directory, the start works: # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg This can be reproduced with a simple Docker container the following Dockerfile: -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy -c -f /etc/haproxy/haproxy.cfg"] -- Checking the haproxy package for the run directory shows nothing: # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Description changed: When installing the haproxy package from the current Ubuntu 18.04 Bionic - repos, the package does not install the directory `/run/haproxy`. This + repos, the package does not install the directory /run/haproxy. This directory is mentioned in the default config file - `/etc/haproxy/haproxy.cfg`: + /etc/haproxy/haproxy.cfg: - ``` - stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners - ``` + + stats socket /run/haproxy/admin.sock mode 660 level admin expose-fd listeners + Starting HAProxy manually will show the following error: - ``` - # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg + + # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg [ALERT] 337/154339 (24) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock] - ``` + After manual creation of the directory, the start works: - ``` + # mkdir /run/haproxy # /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg # ps auxf USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root10 0.1 0.0 18616 3416 pts/0Ss 15:42 0:00 /bin/bash root32 0.0 0.0 34400 2900 pts/0R+ 15:45 0:00 \_ ps auxf root 1 0.0 0.0 18376 3016 ?Ss 15:40 0:00 bash /root/entrypoint.sh haproxy 31 0.0 0.0 54284 1252 ?Ss 15:45 0:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg - ``` - This can be reproduced with a simple Docker container the following - Dockerfile: - ``` + This can be reproduced with a simple Docker container the following Dockerfile: + + -- FROM ubuntu:18.04 MAINTAINER Claudio Kuenzler # install packages RUN apt-get update \ - && apt-get install -y -qq haproxy + && apt-get install -y -qq haproxy CMD ["/usr/sbin/haproxy -c -f /etc/haproxy/haproxy.cfg"] - ``` + -- Checking the haproxy package for the run directory shows nothing: - ``` - # dpkg -L haproxy | grep run ; date + + # dpkg -L haproxy | grep run ; date Wed Dec 4 15:58:52 UTC 2019 - ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855140 Title: haproxy package misses creation of default stats socket path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1855140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853730] Re: package snapd (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1
** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853730 Title: package snapd (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1853730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849740] Re: arp-scan returns an empty scan
I can confirm this bug in Ubuntu 19.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849740 Title: arp-scan returns an empty scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arp-scan/+bug/1849740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830183] Re: Absence of updates is labelled a critical error in syslog
Interesting. This is what I see here with Ksystemlog. ** Attachment added: "Screenshot from 2019-11-04 20-01-25.png" https://bugs.launchpad.net/snapd/+bug/1830183/+attachment/5302839/+files/Screenshot%20from%202019-11-04%2020-01-25.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830183 Title: Absence of updates is labelled a critical error in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1830183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830183] Re: Absence of updates is labelled a critical error in syslog
Oh, but I see you read from `/var/log/syslog` instead of the systemd journal. I don't have snapd entries in the syslog file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830183 Title: Absence of updates is labelled a critical error in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1830183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830183] Re: Absence of updates is labelled a critical error in syslog
** Changed in: snapd Status: Incomplete => Triaged ** Changed in: snapd (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830183 Title: Absence of updates is labelled a critical error in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1830183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830183] Re: Absence of updates is labelled a critical error in syslog
Could you confirm this still happens with snapd 2.42? I quickly tested it and this type of message was logged in the system journal as `info` (level 6). ** Changed in: snapd Status: Triaged => Incomplete ** Changed in: snapd (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830183 Title: Absence of updates is labelled a critical error in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1830183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832963] Re: sound doesn't work
I installed the latest mainline kernel and it still fails: - https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc4/ - it is linux-image-unsigned-5.2.0-050200rc4-generic 5.2.0-050200rc4.201906091240 The workaround for me is to use the last kernel that works: ``` Linux HP-Notebook 5.0.15-050015-generic #201905101332 SMP Fri May 10 17:34:56 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832963 Title: sound doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work
Fixed also on 5.4-rc1 and 5.3.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work
The video works with kernel 5.4-rc4 form https://kernel.ubuntu.com /~kernel-ppa/mainline/. Thank you for your patience. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it
I did some test, with kernel 5.2.21 everything works (linux-image- unsigned-5.2.21-050221-generic_5.2.21-050221.201910111731_amd64.deb). I also tried kernel 5.3.6 and the screen is again black at boot (linux- headers-5.3.6-050306_5.3.6-050306.201910111731_all.deb) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] Re: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17
black screen ** Attachment added: "Black screen" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847980/+attachment/5297221/+files/20191015_085022.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux- image-5.3.0-17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] Re: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17
Black screen log ** Attachment added: "Black screen log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847980/+attachment/5297223/+files/blackscreendmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux- image-5.3.0-17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] Re: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17
Datail of black screen ** Attachment added: "Datail of black screen" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847980/+attachment/5297222/+files/20191015_085028.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux- image-5.3.0-17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847980] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1847980/+attachment/5297110/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux- image-5.3.0-17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1847980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
