[Touch-packages] [Bug 1838370] [NEW] slapd segfault on filter parse error
Public bug reported: Hello! We have faced slapd crash, seems an attacker was trying to brute force one of our services and uid parsing failures caused slapd crash: Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH base="ou=test,dc=test,dc=com" scope=2 deref=0 filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadow Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host loginDisabled loginExpirationTime loginAllowedTimeMap sshPublic Key Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text=massaged filter parse error Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip 7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so [7fc8d1868000+1c] Another faulty filter example: filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0" filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ slapd -VVV @(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $ buildd@lcy01-amd64-019 :/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd Included static backends: config ldif $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error Status in openldap package in Ubuntu: New Bug description: Hello! We have faced slapd crash, seems an attacker was trying to brute force one of our services and uid parsing failures caused slapd crash: Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH base="ou=test,dc=test,dc=com" scope=2 deref=0 filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadow Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host loginDisabled loginExpirationTime loginAllowedTimeMap sshPublic Key Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text=massaged filter parse error Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip 7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so [7fc8d1868000+1c] Another faulty filter example: filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0" filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ slapd -VVV @(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $ buildd@lcy01-amd64-019 :/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd Included static backends: config ldif $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1838370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launch
[Touch-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se
The new version of the SRU is in bug 1834138. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Cosmic: Fix Released Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04&package=pulseaudio&period=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1556439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838380] [NEW] slapd does not automatically restart on failure
Public bug reported: Slapd does not restart after a failure. Slapd package does not include systemd unit file at all, only init.d script. Makes sense to make a unitfile with a Restart=on-failure option. $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838380 Title: slapd does not automatically restart on failure Status in openldap package in Ubuntu: New Bug description: Slapd does not restart after a failure. Slapd package does not include systemd unit file at all, only init.d script. Makes sense to make a unitfile with a Restart=on-failure option. $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1838380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop"; SUPPORT_URL="http://support.system76.com"; BUG_REPORT_URL="https://github.com/pop-os/pop/issues"; PRIVACY_POLICY_URL="https://system76.com/privacy"; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq /#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838372] [NEW] 'ubuntu-bug -w' doesn't work under wayland
You have been subscribed to a public bug: 'ubuntu-bug -w' doesn't work for most applications such nautilus, gedit, settings, etc. under wayland. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- 'ubuntu-bug -w' doesn't work under wayland https://bugs.launchpad.net/bugs/1838372 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838372] Re: 'ubuntu-bug -w' doesn't work under wayland
** Package changed: ubuntu => apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1838372 Title: 'ubuntu-bug -w' doesn't work under wayland Status in apport package in Ubuntu: New Bug description: 'ubuntu-bug -w' doesn't work for most applications such nautilus, gedit, settings, etc. under wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1838372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices
Here is my status. The hidd binary seems to be gone. The bluetooth-wizard binary worked fine for me in bionic just now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059185] Re: bluetooth-wizard doesn't find any devices
** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => Fix Released ** Changed in: bluez (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1059185 Title: bluetooth-wizard doesn't find any devices Status in bluez package in Ubuntu: Fix Released Status in gnome-bluetooth package in Ubuntu: Fix Released Bug description: I have just upgrade to Quantal from Precise. I have a bluetooth usb dongle, that lets me use my bluetooth keyboard and mouse. They worked without problems before the upgrade, but now they don't. I removed them and tried to add them again, but the bluetooth-wizard is stuck searching for devices, and doesn't find any. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-bluetooth 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 Date: Sun Sep 30 11:45:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to quantal on 2012-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1059185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830858] Re: TOCTOU vulnerability in _get_ignore_dom (report.py)
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3560 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1830858 Title: TOCTOU vulnerability in _get_ignore_dom (report.py) Status in Apport: Fix Committed Status in apport package in Ubuntu: Fix Released Bug description: Dear Ubuntu Security Team, I would like to report a privilege escalation vulnerability in Apport. The vulnerability is a TOCTOU which enables me to trick Apport into reading any file on the system and including it in a crash report file. I have attached a proof-of-concept which triggers the vulnerability. I have tested it on an up-to-date Ubuntu 18.04. Run it as follows: bunzip2 PoC.tar.bz2 tar -xf PoC.tar cd PoC make ./gencrashreport /etc/shadow At this point the following file has been created: /var/crash/_usr_share_apport_apport.0.crash You can use the apport-unpack tool to decompress this file. If you look at the contents of the CoreDump file then you will see that it contains the contents of /etc/shadow (or whichever other file you passed on the command line of gencrashreport). The bug has a couple of mitigations: 1. My PoC does not work if a file named /var/crash/.lock already exists and is owned by root. This file will only exist if Apport has previously generated a crash report. Based on an informal survey of my own 4 computers (yes - maybe I don't need that many), it usually does not exist (unless the computer is used for security research). 2. The generated crash report file, /var/crash/_usr_share_apport_apport.0.crash, is only readable by root and by the whoopsie user. It will be uploaded to daisy.ubuntu.com if you create a file named /var/crash/_usr_share_apport_apport.0.upload, but that is not a huge security concern because it wouldn't be of much benefit to an attacker. However, I have found some integer overflow vulnerabilities in whoopsie (which I will report separately). If those overflows can be exploited to gain code execution in whoopsie, then this will enable an attacker to read the contents of the crash report file. To improve the effectiveness of the first mitigation, I would recommend that you make sure that /var/crash/.lock is created (and owned by root) by the Ubuntu installer and/or whoopsie when it starts up. It does not fix the root cause though, which I will describe next. This is the source location of the TOCTOU vulnerability: https://git.launchpad.net/ubuntu/+source/apport/tree/apport/report.py?h=applied/ubuntu /bionic-devel&id=2fc8fb446c78e950d643bf49bb7d4a0dc3b05429#n962 Apport allows the user to place a file in their home directory named `~/.apport-ignore.xml`. The call to os.access() on line 962 is intended to check that this file belongs to the correct user. But on line 967, the file is read again using xml.dom.minidom.parse. This creates a window of opportunity for an attacker to replace the file with a symlink. The symlink does not need to point to a valid XML file, because there is a try-except around the call to the parser, so if the file is invalid then Apport just ignores it and continues. However, the contents of the file still ends up in Apport's heap. Here's a summary of how the PoC works: 1. Start a /bin/sleep and kill it with a SIGSEGV. 2. Apport starts up to generate a crash report for /bin/sleep 3. Replace ~/.apport-ignore.xml with a symlink at exactly the right moment, so that Apport loads a forbidden file into memory. 4. Wait until Apport drops privileges so that we can kill it with a SIGTRAP. 5. A second Apport starts up to generate a crash report for the first Apport. 6. The second Apport writes out a crash report for the first, containing a copy of the forbidden file in the core dump. Apport tries quite hard to not run recursively on itself, so I had to jump through a few hoops to make the PoC work: 1. Apport sets a lock on /var/crash/.lock, using lockf. But locks created by lockf are only "advisory". If I own the file, then I can replace it with a different file, thereby deactivating the lock. This is why my PoC only works if /var/crash/.lock doesn't already exist. I need to create it before Apport does, so that I can maintain ownership of it. 2. Apport has signal handlers for most of the core-generating signals, like SIGSEGV. But it doesn't have a handler for SIGTRAP, so that's what my PoC uses. 3. Apport is started with an RLIMIT_CORE value of 1, which is another recursion detection mechanism (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/498525/comments/3). But it is possible for another process to change it to zero, using prlimit. As I mentioned earlier, I have also found a few other vulnerabilities in whoopsie and Apport. I will file them as separate bugs
[Touch-packages] [Bug 1718927] Re: No HDMI sound after suspend/resume
OS: Ubuntu 18.04.2 DE: Gnome Shell 3.28.2 Kernel: 4.18.0-25-generic Nvidia driver: 430.26 Audio: Headphones (Motherboard) + Speakers (HDMI) Found an workaround (https://askubuntu.com/questions/1053076/18-04-sound-through-hdmi) and it worked for me: "When signal is lost to HDMI (during sleep) Pulse Audio is automatically configured to active source (your laptop's speakers). Upon resume the sound device is still your laptop. To override this setting, tell Pulse Audio to never switch sound devices automatically: edit the file /etc/pulse/default.pa find the line load-module module-switch-on-port-available insert a # at the beginning of the line to disable automatic port switching save the file and reboot." Steps to test workaround: 1) Change sound output to HDMI; 2) Open a browser (in my case Chromium snap) and wait for it to open; 3) Open media player (in my case VLC snap) and wait for it to open; 4) Play random video or music in both; 5) Pause playback; 6) Put Computer to sleep and wait like 30 sec; 7) Wake up from sleep; 8) Resume what was playing before going into sleep; 9) First time it could change output to Headphones, but at least I could switch to HDMI at least in settings; 10) Repeat step .6 through .9 a couple of times; The sound through HDMI should be working, could be switched and remains the default even after waking up from suspend, except first time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838258] Re: Unable to configure VLAN on an additional OSA interface
** Tags added: id-5d3f1092c9ff2f192b03a448 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Triaged Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838258] Re: Unable to configure VLAN on an additional OSA interface
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Triaged Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802225] Re: LightDM login doesn't display after screen lock
*** This bug is a duplicate of bug 1801609 *** https://bugs.launchpad.net/bugs/1801609 Any update on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1802225 Title: LightDM login doesn't display after screen lock Status in lightdm package in Ubuntu: Confirmed Bug description: When locking the screen via the xfce menu or light-locker tool the screen sits at a blank/black screen. Moving the mouse or pressing a button on the keyboard does nothing. After searching I found I could just enter my password blindly and it would unlock the screen. Also going to a console tty and back to the graphical login would then show a login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 Uname: Linux 4.19.0-041900-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 8 13:29:14 2018 InstallationDate: Installed on 2017-11-06 (366 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) LightdmConfig: [LightDM] logind-check-graphical=true display-setup-script=xrandr --output eDP-1 --primary SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1802225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Disco) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835922 Title: missing gl* symbols in version 19.0.2 Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Disco: New Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture' OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::r
[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
Maybe unrelated (but those communications channel might be worth watching for related news): Robert Hallock of AMD has announced a new beta driver for the chipset that is/was available via google drive. It is said this fixes something relevant for at least the game Destiny 2. As the test phase was closed already a quick follow up in about 1 day was promised. https://www.reddit.com/r/Amd/comments/ciajef/placeholder_update_on_whea_warnings_destiny_2_and/evayush/ https://drive.google.com/file/d/1mojPNWcOuuhxvdBkYJlkLbsDXwGLImGp/view -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: In Progress Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Given comment #40 and the fixed dpkg, we're going to decline the rls nomination for eoan. It's possible/probable that those patches are right anyway - please could you submit them ideally via a merge request on salsa.debian.org? ** Tags removed: rls-ee-incoming ** Tags added: rls-ee-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837173] Re: shall allow local save even it's neither ubuntu nor native.
** Changed in: apport (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1837173 Title: shall allow local save even it's neither ubuntu nor native. Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Won't Fix Bug description: For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is a local test one, it won't save the log. Let's skip package check if --save option is used. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1837173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837466] Re: [SRU] Please make ubuntu-wsl recommend dbus-x11
This bug was fixed in the package ubuntu-meta - 1.431.1 --- ubuntu-meta (1.431.1) disco; urgency=medium * Added dbus-x11 to wsl-recommends (LP: #1837466) -- Balint Reczey Mon, 22 Jul 2019 23:07:09 +0200 ** Changed in: ubuntu-meta (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-meta source package in Disco: Fix Released Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837466] Update Released
The verification of the Stable Release Update for ubuntu-meta has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1837466 Title: [SRU] Please make ubuntu-wsl recommend dbus-x11 Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in ubuntu-meta source package in Disco: Fix Released Bug description: [Impact] * Some graphical apps such as gedit complain about not being able to start dbus using dbus-launch when they are started from the WSL Ubuntu terminal because dbus-x11 is not installed. [Test Case] * Test if ubuntu-wsl recommends dbus-x11 (check the version to be verified): $ apt-cache show ubuntu-wsl=1.435 | grep dbus Recommends: dbus-x11 [Regression Potential] * Recommending the new dbus-x11 package comes with an increased installation size, but this is accepted to make the WSL experience more pleasant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1837466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835809] Re: AMD Ryzen 3000 series fails to boot
A bunch of updates went public - the AGESA component update is still due as its pushed to the end user via the integration and qualification pipeline of the board vendors. It got said this will take several weeks. https://community.amd.com/community/gaming/blog/2019/07/30/community-update-5-let-s-talk-clocks-voltages-and-destiny-2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835809 Title: AMD Ryzen 3000 series fails to boot Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: In Progress Bug description: [Impact] * Systems with AMD Ryzen 3000 series CPUs don't boot. [Test Case] * Boot with fixed systemd on an AMD Ryzen 3000 series system. [Regression Potential] * The fix itself is very small, it ignores known to be faulty random values returned by the rdrand instruction and use a different random source. Those values can still be returned by a properly working rdrand implementation in 2 in 2^32 cases on 32 bit arches and in 2 in 2^64 cases on 64 bit arches, but the fallback to the other random source ensures that in those rare occasions a random number can be generated. [Original Bug Text] On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd preventing the boot process from completing. This issue does not affect the older systemd version in 18.04, but affects the 19.04 version. Here is a screenshot showing what happens: https://www.phoronix.net/image.php?id=ryzen-3700x-3900x-linux&image=amd_zen2_14_show I am currently testing a patch to systemd, derived from this pull request: https://github.com/systemd/systemd/pull/12536 This is a high severity issue, as I do not believe there is no potential workaround without either a firmware update or an ISO respin. I have attached a rebase of the potential patch on the current 19.04 version of systemd for reference. I will provide more details after testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838436] [NEW] popt download location broken
Public bug reported: rpm5.org disappeared, with download area, home page and CVS repo. See also https://bugs.archlinux.org/task/62888?project=1&string=popt ** Affects: popt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to popt in Ubuntu. https://bugs.launchpad.net/bugs/1838436 Title: popt download location broken Status in popt package in Ubuntu: New Bug description: rpm5.org disappeared, with download area, home page and CVS repo. See also https://bugs.archlinux.org/task/62888?project=1&string=popt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popt/+bug/1838436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1838370] [NEW] slapd segfault on filter parse error
Hello, thank you for the report. I was able to reproduce the crash locally by intentionally mis-configuring the rwm overlay. Could you please provide a copy of your rwm overlay configuration? I would like to see what the actual parse failure was in your instance. ** Changed in: openldap (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error Status in openldap: Fix Released Status in openldap package in Ubuntu: Confirmed Bug description: Hello! We have faced slapd crash, seems an attacker was trying to brute force one of our services and uid parsing failures caused slapd crash: Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH base="ou=test,dc=test,dc=com" scope=2 deref=0 filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadow Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host loginDisabled loginExpirationTime loginAllowedTimeMap sshPublic Key Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text=massaged filter parse error Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip 7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so [7fc8d1868000+1c] Another faulty filter example: filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0" filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ slapd -VVV @(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $ buildd@lcy01-amd64-019 :/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd Included static backends: config ldif $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1838370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1838380] [NEW] slapd does not automatically restart on failure
Hello, You can configure that yourself with a systemd drop-in file that modifies the generated unit. A similar one was recently added to set RemainOnExit=false; see bug 1821343. I can't comment on whether it's appropriate to add that behaviour in the package by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838380 Title: slapd does not automatically restart on failure Status in openldap package in Ubuntu: New Bug description: Slapd does not restart after a failure. Slapd package does not include systemd unit file at all, only init.d script. Makes sense to make a unitfile with a Restart=on-failure option. $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1838380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error
Looks like this is fixed upstream already: https://openldap.org/its/?findid=8964 fixed in 2.4.48. Cherry-picking upstream commit d40b357f5da9a94d2f4f541c21bde02610d9cd3b fixes the crash for me. ** Also affects: openldap Importance: Undecided Status: New ** Changed in: openldap Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error Status in openldap: Fix Released Status in openldap package in Ubuntu: Confirmed Bug description: Hello! We have faced slapd crash, seems an attacker was trying to brute force one of our services and uid parsing failures caused slapd crash: Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH base="ou=test,dc=test,dc=com" scope=2 deref=0 filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadow Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host loginDisabled loginExpirationTime loginAllowedTimeMap sshPublic Key Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text=massaged filter parse error Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip 7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so [7fc8d1868000+1c] Another faulty filter example: filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0" filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ slapd -VVV @(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $ buildd@lcy01-amd64-019 :/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd Included static backends: config ldif $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1838370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838352] Re: package python3 3.7.3-1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1838352 Title: package python3 3.7.3-1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: New Bug description: trying to upgrade ProblemType: Package DistroRelease: Ubuntu 19.04 Package: python3 3.7.3-1 ProcVersionSignature: Ubuntu 4.18.0-1024.25~18.04.1-azure 4.18.20 Uname: Linux 4.18.0-1024-azure x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Jul 29 19:44:42 2019 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: python3-defaults Title: package python3 3.7.3-1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to disco on 2019-07-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1838352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838380] Re: slapd does not automatically restart on failure
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openldap (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838380 Title: slapd does not automatically restart on failure Status in openldap package in Ubuntu: Confirmed Bug description: Slapd does not restart after a failure. Slapd package does not include systemd unit file at all, only init.d script. Makes sense to make a unitfile with a Restart=on-failure option. $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1838380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error
** Also affects: openldap (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: openldap (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error Status in openldap: Fix Released Status in openldap package in Ubuntu: Confirmed Status in openldap source package in Xenial: New Status in openldap source package in Bionic: New Status in openldap source package in Disco: New Bug description: Hello! We have faced slapd crash, seems an attacker was trying to brute force one of our services and uid parsing failures caused slapd crash: Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH base="ou=test,dc=test,dc=com" scope=2 deref=0 filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadow Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host loginDisabled loginExpirationTime loginAllowedTimeMap sshPublic Key Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text=massaged filter parse error Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip 7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so [7fc8d1868000+1c] Another faulty filter example: filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0" filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ slapd -VVV @(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $ buildd@lcy01-amd64-019 :/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd Included static backends: config ldif $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1838370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/370689 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Status in openldap source package in Bionic: Fix Released Status in openldap source package in Cosmic: Fix Released Status in openldap package in Debian: New Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) 6) Check if systemd has loaded both /run/systemd/generator.late/slapd.service & /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf $ systemctl cat slapd [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd
** Merge proposal unlinked: https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/370689 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1821343 Title: slapd process failure is not detected by systemd Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Fix Released Status in openldap source package in Bionic: Fix Released Status in openldap source package in Cosmic: Fix Released Status in openldap package in Debian: New Bug description: [Impact] Systemd service reports slapd as active, even though it may have failed [Description] The slapd package for OpenLDAP is shipped with a SysV-style init script (/etc/init.d/slapd). Systemd automatically converts this to a systemd service by generating the unit file using the systemd-sysv-generator(8) utility. The generated unit file contains Type=forking and RemainAfterExit=yes directives. If the slapd daemon process exits due to some failure (e.g., it receives a SIGTERM or SIGKILL), the failure is not detected properly by systemd. The service is still reported as active even though the child (daemon) process has exited with a signal. We can easily fix this by including a proper systemd service file for slapd in the openldap package. Since the init.d script already does most of the necessary work (parsing configs, setting up PID files, etc.), we don't need anything complicated for the systemd unit file. Just making sure that RemainAfterExit is set to "no" makes the systemd service behave in the expected way. [Test Case] 1) Deploy a disco container $ lxc launch images:ubuntu/disco disco 2) Install slapd ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y 3) Verify that slapd is running with the auto-generated service ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) Tasks: 3 (limit: 4915) Memory: 712.6M CGroup: /system.slice/slapd.service └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d 4) SIGKILL the slapd process (PID is displayed in systemctl status output) ubuntu@disco:~$ sudo kill -9 1109 5) Check if systemd service lists slapd as still active, even though it was terminated ubuntu@disco:~$ systemctl status slapd ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory Access Protocol) Loaded: loaded (/etc/init.d/slapd; generated) Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago Docs: man:systemd-sysv-generator(8) Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, status=0/SUCCESS) 6) Check if systemd has loaded both /run/systemd/generator.late/slapd.service & /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf $ systemctl cat slapd [Regression Potential] The regression potential for this fix should be very low, if we keep the new systemd unit file close to the one generated by systemd-sysv-generator(8). The only significant change would be the RemainAfterExit directive, and this should make the slapd service behave like a "normal" forking service. Nonetheless, we'll perform scripted test runs to make sure no regressions arise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1821343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837734] Re: Firefox crash on a FIPS enabled machine due to libnss3
Hello Vineetha, or anyone else affected, Accepted nss into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nss/2:3.42-1ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nss (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: nss (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1837734 Title: Firefox crash on a FIPS enabled machine due to libnss3 Status in nss package in Ubuntu: Fix Released Status in nss source package in Xenial: In Progress Status in nss source package in Bionic: Fix Committed Status in nss source package in Disco: Fix Committed Status in nss source package in Eoan: Fix Released Bug description: [IMPACT] nss is not a FIPS certified library. On a machine running FIPS enabled kernel, the library by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from libnss3 before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts libnss3 versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. libnss3 is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in standard ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1837734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837734] Please test proposed package
Hello Vineetha, or anyone else affected, Accepted nss into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nss/2:3.35-2ubuntu2.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1837734 Title: Firefox crash on a FIPS enabled machine due to libnss3 Status in nss package in Ubuntu: Fix Released Status in nss source package in Xenial: In Progress Status in nss source package in Bionic: Fix Committed Status in nss source package in Disco: Fix Committed Status in nss source package in Eoan: Fix Released Bug description: [IMPACT] nss is not a FIPS certified library. On a machine running FIPS enabled kernel, the library by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from libnss3 before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts libnss3 versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. libnss3 is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in standard ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1837734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837734] Re: Firefox crash on a FIPS enabled machine due to libnss3
Hello Vineetha, or anyone else affected, Accepted nss into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nss/2:3.28.4-0ubuntu0.16.04.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nss (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1837734 Title: Firefox crash on a FIPS enabled machine due to libnss3 Status in nss package in Ubuntu: Fix Released Status in nss source package in Xenial: Fix Committed Status in nss source package in Bionic: Fix Committed Status in nss source package in Disco: Fix Committed Status in nss source package in Eoan: Fix Released Bug description: [IMPACT] nss is not a FIPS certified library. On a machine running FIPS enabled kernel, the library by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from libnss3 before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts libnss3 versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. libnss3 is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in standard ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1837734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Running 18.04.2 and the mouse started to jump to top right corner on screen 1 out of 2 a few days ago. Tried #32, but ...libinput-all was also removed and after reboot, no response from mouse or keyboard. Started in protected mode and reinstalled libinput. Still same problem. I've tried Logitech wireless, Bluetooth and wired mouse. When running sudo cat /dev/input mice, there is continuous input, even when the mouse has jumped to the top right corner. I've also changed batteries in the Logitech mouse. I certainly would like this problem to be solved. For now, I'll continue to search for solutions on the web. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Ref #64, it was the external switch. I restarted it and everything works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838464] [NEW] NFS volume not mounting with systemd
You have been subscribed to a public bug:
Hello,
I'm unable to mount NFS volume at boot time with systemd. Using Ubuntu 18.04.2
LTS.
I commented out /etc/fstab entry:
#192.168.1.103:/Multimedia/Music/mnt/nas/music/ nfs
_netdev,auto,user,vers=30 0
I created "/etc/systemd/system/mnt-nas-music.mount":
[Unit]
Description=NAS volume - Music
After=network.target
[Mount]
What=192.168.1.103:/Multimedia/Music
Where=/mnt/nas/music/
Type=nfs
Options=_netdev,auto,user,nfsvers=3
TimeoutSec=10
[Install]
WantedBy=multi-user.target
I enabled it with "systemctl enable mnt-nas-music.mount" so that when I run
"systemctl is-enabled mnt-nas-music.mount" I obtain:
enable
But I keep obtaining this error ("systemctl status mnt-nas-
music.mount"):
mnt-nas-music.mount - NAS volume - Music
Loaded: loaded (/etc/systemd/system/mnt-nas-music.mount; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-07-30 21:23:42 CEST; 29min
ago
Where: /mnt/nas/music
What: 192.168.1.103:/Multimedia/Music
Process: 1530 ExecMount=/bin/mount 192.168.1.103:/Multimedia/Music
/mnt/nas/music -t nfs -o _netdev,user,nfsvers=3 (code=exited, status=32)
lug 30 21:23:42 ubuntu-desktop systemd[1]: Mounting NAS volume - Music...
lug 30 21:23:42 ubuntu-desktop mount[1530]: mount.nfs: Network is unreachable
lug 30 21:23:42 ubuntu-desktop systemd[1]: mnt-nas-music.mount: Mount process
exited, code=exited status=32
lug 30 21:23:42 ubuntu-desktop systemd[1]: mnt-nas-music.mount: Failed with
result 'exit-code'.
lug 30 21:23:42 ubuntu-desktop systemd[1]: Failed to mount NAS volume - Music.
If I run "journalctl -b" I notice that the attempt to mount NFS volume happens
before network is ready:
lug 30 21:23:42 ubuntu-desktop systemd[1]: Failed to mount NAS volume - Music.
lug 30 21:23:48 ubuntu-desktop NetworkManager[978]: [1564514628.2750]
device (enp2s0): Activation: successful, device activated.
I think this is a bug.
Thanks in advance
Michele
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
NFS volume not mounting with systemd
https://bugs.launchpad.net/bugs/1838464
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to systemd in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838464] Re: NFS volume not mounting with systemd
** Package changed: ubuntu => systemd (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1838464
Title:
NFS volume not mounting with systemd
Status in systemd package in Ubuntu:
New
Bug description:
Hello,
I'm unable to mount NFS volume at boot time with systemd. Using Ubuntu
18.04.2 LTS.
I commented out /etc/fstab entry:
#192.168.1.103:/Multimedia/Music /mnt/nas/music/ nfs
_netdev,auto,user,vers=30 0
I created "/etc/systemd/system/mnt-nas-music.mount":
[Unit]
Description=NAS volume - Music
After=network.target
[Mount]
What=192.168.1.103:/Multimedia/Music
Where=/mnt/nas/music/
Type=nfs
Options=_netdev,auto,user,nfsvers=3
TimeoutSec=10
[Install]
WantedBy=multi-user.target
I enabled it with "systemctl enable mnt-nas-music.mount" so that when I run
"systemctl is-enabled mnt-nas-music.mount" I obtain:
enable
But I keep obtaining this error ("systemctl status mnt-nas-
music.mount"):
mnt-nas-music.mount - NAS volume - Music
Loaded: loaded (/etc/systemd/system/mnt-nas-music.mount; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 2019-07-30 21:23:42 CEST;
29min ago
Where: /mnt/nas/music
What: 192.168.1.103:/Multimedia/Music
Process: 1530 ExecMount=/bin/mount 192.168.1.103:/Multimedia/Music
/mnt/nas/music -t nfs -o _netdev,user,nfsvers=3 (code=exited, status=32)
lug 30 21:23:42 ubuntu-desktop systemd[1]: Mounting NAS volume - Music...
lug 30 21:23:42 ubuntu-desktop mount[1530]: mount.nfs: Network is unreachable
lug 30 21:23:42 ubuntu-desktop systemd[1]: mnt-nas-music.mount: Mount process
exited, code=exited status=32
lug 30 21:23:42 ubuntu-desktop systemd[1]: mnt-nas-music.mount: Failed with
result 'exit-code'.
lug 30 21:23:42 ubuntu-desktop systemd[1]: Failed to mount NAS volume - Music.
If I run "journalctl -b" I notice that the attempt to mount NFS volume
happens before network is ready:
lug 30 21:23:42 ubuntu-desktop systemd[1]: Failed to mount NAS volume - Music.
lug 30 21:23:48 ubuntu-desktop NetworkManager[978]: [1564514628.2750]
device (enp2s0): Activation: successful, device activated.
I think this is a bug.
Thanks in advance
Michele
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1838464/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
Hello Alejandro, or anyone else affected, Accepted libarchive into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libarchive/3.2.2-3.1ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libarchive (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories Status in libarchive package in Ubuntu: Fix Released Status in libarchive source package in Bionic: Fix Committed Bug description: * Impact The bionic version has a known problem when reading file entries in ZIP files, where it incorrectly identifies directories and files entries. * Test case $ wget https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip $ bsdtar -vxf example.zip $ ls -l The 'ABCD_1234' and 'empty' entries should be directories * Regression potential Check that extracting zips from bsdtar or nautilus work without issue It has been confirmed that the previous and following versions (3.3.1+) do not have this problem and the library handles the ZIP files correctly. Is it possible to include a newer version of libarchive (3.3.1+) in Bionic? This problem is seriously affecting some of our systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836258] Re: Update hyperlink when enabling UCA
Hello Peter, or anyone else affected, Accepted software-properties into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /software-properties/0.96.20.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: software-properties (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Fix Committed Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Eoan: Fix Released Bug description: [Impact] When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 [Test Case] The "More info:" link should be https://wiki.ubuntu.com/OpenStack/CloudArchive, for example: root@b1:~# sudo add-apt-repository cloud-archive:queens Ubuntu Cloud Archive for OpenStack Queens More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. [Regression Potential] This change is extremely minimal as it only updates a string that points to a wiki URL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835711] Re: Ubuntu-bug collects bug data but does not upload it
Could you paste the results of "cat /var/log/installer/media-info"? I'm curious if this might have been an issue when upgrading between Ubuntu releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1835711 Title: Ubuntu-bug collects bug data but does not upload it Status in apport package in Ubuntu: New Bug description: I'm trying to report some bugs from a stable release, 18.04. I enabled apport reporting as suggested here:https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash_in_the_stable_release and also here: https://www.linuxbabe.com/ubuntu/disable-apport-error- reporting-ubuntu-16-04-lts I also have whoopsie package installed. When I try to report a bug using `ubuntu-bug $package_name` it seem to be collecting data, but then it doesn't send them to launchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1835711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838481] [NEW] /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:GlassTable::set_
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 1.0-0.1ubuntu1, the problem page at https://errors.ubuntu.com/problem/92d81d05bda3d09dfe6b31c85f2efa317ab4c4c0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1838481 Title: /usr/lib/zeitgeist/zeitgeist/zeitgeist- fts:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:GlassTable::set_overwritten Status in zeitgeist package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding zeitgeist. This problem was most recently seen with package version 1.0-0.1ubuntu1, the problem page at https://errors.ubuntu.com/problem/92d81d05bda3d09dfe6b31c85f2efa317ab4c4c0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1838481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836258] Re: Update hyperlink when enabling UCA
For Bionic, $ lsb_release -c Codename: bionic $ dpkg-query -W software-properties-common software-properties-common 0.96.24.32.11 $ sudo add-apt-repository cloud-archive:rocky Ubuntu Cloud Archive for OpenStack Rocky More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. Link works. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Fix Committed Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Eoan: Fix Released Bug description: [Impact] When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 [Test Case] The "More info:" link should be https://wiki.ubuntu.com/OpenStack/CloudArchive, for example: root@b1:~# sudo add-apt-repository cloud-archive:queens Ubuntu Cloud Archive for OpenStack Queens More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. [Regression Potential] This change is extremely minimal as it only updates a string that points to a wiki URL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836258] Re: Update hyperlink when enabling UCA
For Xenial, $ lsb_release -c Codename: xenial $ dpkg-query -W software-properties-common software-properties-common 0.96.20.9 $ sudo add-apt-repository cloud-archive:ocata Ubuntu Cloud Archive for OpenStack Ocata More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or ctrl-c to cancel adding it Link works. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1836258 Title: Update hyperlink when enabling UCA Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Fix Committed Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Eoan: Fix Released Bug description: [Impact] When enabling UCA a hyperlink is printed: $ sudo add-apt-repository cloud-archive:train-proposed Ubuntu Cloud Archive for OpenStack Train [proposed] More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. The hyperlink redirects to: https://wiki.ubuntu.com/OpenStack/CloudArchive so it should just be corrected at the source: https://git.launchpad.net/ubuntu/+source/software- properties/tree/softwareproperties/cloudarchive.py#n50 [Test Case] The "More info:" link should be https://wiki.ubuntu.com/OpenStack/CloudArchive, for example: root@b1:~# sudo add-apt-repository cloud-archive:queens Ubuntu Cloud Archive for OpenStack Queens More info: https://wiki.ubuntu.com/OpenStack/CloudArchive Press [ENTER] to continue or Ctrl-c to cancel adding it. [Regression Potential] This change is extremely minimal as it only updates a string that points to a wiki URL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1836258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838485] Re: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1838485 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: I don't have Window. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: policykit-1 0.105-14.1ubuntu0.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 30 11:19:23 2019 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-07-27 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: policykit-1 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1838485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838485] [NEW] package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: I don't have Window. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: policykit-1 0.105-14.1ubuntu0.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 30 11:19:23 2019 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-07-27 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: policykit-1 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1838485 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in policykit-1 package in Ubuntu: New Bug description: I don't have Window. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: policykit-1 0.105-14.1ubuntu0.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 30 11:19:23 2019 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-07-27 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: policykit-1 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1838485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838488] [NEW] [20217, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: Recently installed Ubuntu in my Lenvo Ideapad and sound quality is very poor. Most of the times audio is very little even though increased the volume to 100 and sound is crackling. I followed many sites to try to fix it but nothing works. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vomisha2164 F pulseaudio /dev/snd/controlC0: vomisha2164 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 30 21:10:46 2019 InstallationDate: Installed on 2019-04-21 (100 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [20217, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00141556 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: YB00141556 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1838488 Title: [20217, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Recently installed Ubuntu in my Lenvo Ideapad and sound quality is very poor. Most of the times audio is very little even though increased the volume to 100 and sound is crackling. I followed many sites to try to fix it but nothing works. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vomisha2164 F pulseaudio /dev/snd/controlC0: vomisha2164 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jul 30 21:10:46 2019 InstallationDate: Installed on 2019-04-21 (100 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [20217, Realtek ALC282, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN32WW(V2.02) dmi.board.asset.tag: YB00141556 dmi.board.name: 20217 dmi.board.vendor: LENOVO dmi.board.version: 3194WIN8 STD SGL dmi.chassis.asset.tag: YB00141556 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN32WW(V2.02):bd06/04/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rn20217:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://he
[Touch-packages] [Bug 1838485] Re: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. I note you are using an EOL Ubuntu 17.04 kernel, rather than the standard Ubuntu 16.04 (4.4) or Ubuntu 16.04 HWE (4.15) kernel, and loads of tainted messages in your `dmesg` [28275.945575] WARNING: CPU: 2 PID: 514 at /build/linux-hwe-vH8Hlo/linux-hwe-4.10.0/net/wireless/sme.c:891 cfg80211_roamed+0x8a/0xa0 [cfg80211] .. [28275.945632] CPU: 2 PID: 514 Comm: wl_event_handle Tainted: PW OE 4.10.0-28-generic #32~16.04.2-Ubuntu These I suspect are the reason for your problem, ie. Failed to execute operation: Connection timed out dpkg: error processing archive /var/cache/apt/archives/policykit-1_0.105-14.1ubuntu0.5_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 thus I would suggest using a supported Ubuntu 16.04 LTS kernel, either the standard 4.4 or HWE (hardware-enablement-stack) 4.15 and trying again. I've marked this bug incomplete, if you believe I'm wrong or missing something, please return it to new and leave a comment explaining why. Thanks again for reporting this issue, and helping making Ubuntu a better system. ** Changed in: policykit-1 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1838485 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in policykit-1 package in Ubuntu: Incomplete Bug description: I don't have Window. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: policykit-1 0.105-14.1ubuntu0.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 30 11:19:23 2019 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-07-27 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: policykit-1 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1838485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837700] Re: Dell system takes a long time to connect network with external dock
** Also affects: systemd Importance: Undecided Status: New ** Project changed: systemd => oem-priority ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => cktenn (cktenn) ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: In Progress Bug description: Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1837700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog
This bug resurfaced in Ubuntu 19.04 and persists in 19.10. I installed a fresh copy of both, installed network-manager-openconnect and network- manager-openconnect-gnome, and connected to the company VPN. The password is saved but the username is not saved and it must be manually entered. I didn't see this issue in 18.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835520] Re: Radeon Palm vdpau broke with update bionic
I am not sure, where the problem was. But after new installation of all mesa packages, it worked. ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835520 Title: Radeon Palm vdpau broke with update bionic Status in mesa package in Ubuntu: Invalid Bug description: Ubuntu: Ubuntu 18.04.2 LTS (Release: 18.04) Graphiccard is a AMD Radeon Palm using the r600 driver. Two days ago i installed the updatet mesa packages for bionic: from 18.2.8-0ubuntu0~18.04.2 to 19.0.2-1ubuntu1.1~18.04.1 My Kodi-Mediacenter doesn't play videos with vdpau-hardwareacceleration anymore. It just hangs and crashes after a few seconds. I identified two workarounds: 1. Deactivating vdpau 2. downgrading of these packages helps, but the screen is flickering, assumingly because of the combination of 19.0.2-1ubuntu1.1~18.04.1 and 18.0.0~rc5-1ubuntu1 packages: libgl1-mesa-dri:amd64 to 18.0.0~rc5-1ubuntu1 mesa-vdpau-drivers:amd64 to 18.0.0~rc5-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1835520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
