[Touch-packages] [Bug 1050787] Re: vim: unable to create updated files list
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1050787 Title: vim: unable to create updated files list Status in vim package in Ubuntu: Expired Bug description: Unpacking replacement vim ... dpkg: error processing /var/cache/apt/archives/vim_2%3a7.2.330-1ubuntu3_i386.deb (--unpack): unable to create updated files list file for package vim: No such file or directory No apport report written because MaxReports is reached already Errors were encountered while processing: /var/cache/apt/archives/libavutil49_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb /var/cache/apt/archives/libgsm1_1.0.13-3_i386.deb /var/cache/apt/archives/libschroedinger-1.0-0_1.0.9.is.1.0.8-0ubuntu1_i386.deb /var/cache/apt/archives/libavcodec52_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb /var/cache/apt/archives/libavformat52_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb /var/cache/apt/archives/libpostproc51_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb /var/cache/apt/archives/libswscale0_4%3a0.5.9-0ubuntu0.10.04.1_i386.deb /var/cache/apt/archives/gstreamer0.10-ffmpeg_0.10.10-1_i386.deb /var/cache/apt/archives/gstreamer0.10-fluendo-mp3_0.10.12.debian-2_i386.deb /var/cache/apt/archives/liba52-0.7.4_0.7.4-13ubuntu1_i386.deb /var/cache/apt/archives/libdvdread4_4.1.3-8ubuntu1_i386.deb /var/cache/apt/archives/libid3tag0_0.15.1b-10build2_i386.deb /var/cache/apt/archives/libmad0_0.15.1b-4ubuntu1_i386.deb /var/cache/apt/archives/libmpeg2-4_0.4.1-3_i386.deb /var/cache/apt/archives/lE: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1050787/+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 366040] Re: gvim broken: undefined symbol: initstrop
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/366040 Title: gvim broken: undefined symbol: initstrop Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim-gtk 1) Ubuntu 9.04 2) vim-gtk 2:7.2.079-1ubuntu5 (I _suppose_ it is this package) 3) Launched gvim, expected it to work. 4) Instead, it gave this error and died: gvim: symbol lookup error: gvim: undefined symbol: initstrop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/366040/+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 946734] Re: vim-gnome: difference between guifont 10 and guifont 11 is huge
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/946734 Title: vim-gnome: difference between guifont 10 and guifont 11 is huge Status in vim package in Ubuntu: Expired Bug description: I'm using vim-gnome with Monospace\ 11. Compared to vim-gnome on Ubuntu 11.10 the font is huge. If I set guifont=Monospace\ 10 it's too small. Looks like the step between 10 and 11 has increased. I tried it with different fixed widtht fonts and they all suffer from this problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: vim-gnome 2:7.3.429-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.94-0ubuntu1 Architecture: amd64 Date: Mon Mar 5 00:54:16 2012 EcryptfsInUse: Yes InstallationMedia: SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/946734/+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 1536193] Re: package vim-runtime 2:7.4.712-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package vim 20160113-1
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1536193 Title: package vim-runtime 2:7.4.712-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package vim 20160113-1 Status in vim package in Ubuntu: Expired Bug description: Upgrade failed ProblemType: Package DistroRelease: Ubuntu 15.10 Package: vim-runtime 2:7.4.712-2ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Mon Jan 18 11:39:49 2016 DuplicateSignature: package:vim-runtime:2:7.4.712-2ubuntu4:trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package vim 20160113-1 ErrorMessage: trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package vim 20160113-1 InstallationDate: Installed on 2015-11-12 (68 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: vim Title: package vim-runtime 2:7.4.712-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/optwin.vim', which is also in package vim 20160113-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1536193/+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 1567593] Re: package vim-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 20160401-1
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1567593 Title: package vim-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 20160401-1 Status in vim package in Ubuntu: Expired Bug description: I have recently compiled and installed my own version of vim ProblemType: Package DistroRelease: Ubuntu 15.10 Package: vim-common (not installed) ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Thu Apr 7 11:12:41 2016 DpkgHistoryLog: Start-Date: 2016-04-07 11:12:38 Install: vim-common:amd64 (7.4.712-2ubuntu4, automatic), linux-headers-4.2.0-35:amd64 (4.2.0-35.40, automatic), linux-headers-4.2.0-35-generic:amd64 (4.2.0-35.40, automatic), linux-image-extra-4.2.0-35-generic:amd64 (4.2.0-35.40, automatic), linux-image-4.2.0-35-generic:amd64 (4.2.0-35.40, automatic), vim-runtime:amd64 (7.4.712-2ubuntu4, automatic) Upgrade: linux-headers-generic:amd64 (4.2.0.34.37, 4.2.0.35.38), vim:amd64 (20160401-1, 7.4.712-2ubuntu4), linux-libc-dev:amd64 (4.2.0-34.39, 4.2.0-35.40), linux-image-generic:amd64 (4.2.0.34.37, 4.2.0.35.38), linux-generic:amd64 (4.2.0.34.37, 4.2.0.35.38) DuplicateSignature: package:vim-common:(not installed):trying to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 20160401-1 ErrorMessage: trying to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 20160401-1 InstallationDate: Installed on 2015-02-22 (410 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: vim Title: package vim-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/pl/man1/xxd.1.gz', which is also in package vim 20160401-1 UpgradeStatus: Upgraded to wily on 2016-03-18 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1567593/+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 1592177] Re: Built-in search almost impossible to use in GTK file chooser
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1592177 Title: Built-in search almost impossible to use in GTK file chooser Status in GTK+: Expired Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME 16.04 that the built-in search functionality is almost impossible to use in the GTK file chooser (though it is the same one that allows you to save files as well as choose them). So if one types something into the search, after they have typed the first letter it will immediately select the top search result meaning one has to re-select the search box, this happens for every letter so searching for a long string becomes very annoying. If one carries on typing once it has selected the top result and unselected the search box it will start searching in the other search which only looks at results. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1592177/+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 1811009] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)
*** This bug is a duplicate of bug 1592177 *** https://bugs.launchpad.net/bugs/1592177 https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1592177 First reported here in June 2016 with a link to an upstream report. GNOME developers day this is due to Ubuntu type ahead patches. ** This bug has been marked a duplicate of bug 1592177 Built-in search almost impossible to use in GTK file chooser -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1811009 Title: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour) Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/1572 Steps: 1. Open Gedit 2. Choose Open -> Other Documents... to open a GtkFileChooserDialog 3. Press on the search button next to Open 4. Type what you are searching for Expected behaviour: Focus remains in the search input until I finish typing then results come up What happens instead: Searching stops after I enter the first characters because focus is lost from the search input ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk-3-0 3.22.30-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 8 23:42:23 2019 InstallationDate: Installed on 2018-11-29 (40 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1811009/+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 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
Also here is my git branch in case you prefer to view the merge commit directly: https://salsa.debian.org/openldap-team/openldap/tree/ubuntu/merge-2.4.47 ** Tags added: patch -- 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/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) Status in openldap package in Ubuntu: New Bug description: Hello, I have prepared the merge of openldap 2.4.47+dfsg-2. This will probably be the version released in Debian buster unless any release critical bugs show up. I made changes in Debian to how the contrib modules are built. I made the same changes for nssov in this merge and tested it with the current nss/pam-ldapd. I also added its man page which doesn't seem to have been included before. I performed a test build in a PPA: https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47 Please consider sponsoring this update. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+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 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
** Attachment added: "openldap_2.4.47+dfsg-2ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+attachment/5228960/+files/openldap_2.4.47+dfsg-2ubuntu1.debian.tar.xz -- 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/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) Status in openldap package in Ubuntu: New Bug description: Hello, I have prepared the merge of openldap 2.4.47+dfsg-2. This will probably be the version released in Debian buster unless any release critical bugs show up. I made changes in Debian to how the contrib modules are built. I made the same changes for nssov in this merge and tested it with the current nss/pam-ldapd. I also added its man page which doesn't seem to have been included before. I performed a test build in a PPA: https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47 Please consider sponsoring this update. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+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 1811630] [NEW] Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
Public bug reported: Hello, I have prepared the merge of openldap 2.4.47+dfsg-2. This will probably be the version released in Debian buster unless any release critical bugs show up. I made changes in Debian to how the contrib modules are built. I made the same changes for nssov in this merge and tested it with the current nss/pam-ldapd. I also added its man page which doesn't seem to have been included before. I performed a test build in a PPA: https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47 Please consider sponsoring this update. Thank you! ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- 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/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) Status in openldap package in Ubuntu: New Bug description: Hello, I have prepared the merge of openldap 2.4.47+dfsg-2. This will probably be the version released in Debian buster unless any release critical bugs show up. I made changes in Debian to how the contrib modules are built. I made the same changes for nssov in this merge and tested it with the current nss/pam-ldapd. I also added its man page which doesn't seem to have been included before. I performed a test build in a PPA: https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47 Please consider sponsoring this update. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+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 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
** Attachment added: "openldap_2.4.47+dfsg-2ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+attachment/5228959/+files/openldap_2.4.47+dfsg-2ubuntu1.dsc -- 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/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) Status in openldap package in Ubuntu: New Bug description: Hello, I have prepared the merge of openldap 2.4.47+dfsg-2. This will probably be the version released in Debian buster unless any release critical bugs show up. I made changes in Debian to how the contrib modules are built. I made the same changes for nssov in this merge and tested it with the current nss/pam-ldapd. I also added its man page which doesn't seem to have been included before. I performed a test build in a PPA: https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47 Please consider sponsoring this update. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+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 1811628] [NEW] Ubuntu 18.04 systemctl is-system-running always shows degraded in LXD containers
Public bug reported: Issue in Ubuntu 18.04 LTS: lxc launch ubuntu-daily:18.04 lxc shell # systemctl is-system-running degraded # systemctl --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● sys-kernel-config.mount loaded failed failed Kernel Configuration File System ● systemd-modules-load.service loaded failed failed Load Kernel Modules Fixed in Ubuntu 19.04: lxc launch ubuntu-daily:19.04 lxc shell systemctl is-system-running running It appears to be fixed by adding: ConditionVirtualization=!container to both. Can this be backported to 18.04 or are we stuck with special casing 18.04 vs future versions? As far as I know this is the easiest way to see if a container finished starting. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811628 Title: Ubuntu 18.04 systemctl is-system-running always shows degraded in LXD containers Status in systemd package in Ubuntu: New Bug description: Issue in Ubuntu 18.04 LTS: lxc launch ubuntu-daily:18.04 lxc shell # systemctl is-system-running degraded # systemctl --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● sys-kernel-config.mount loaded failed failed Kernel Configuration File System ● systemd-modules-load.service loaded failed failed Load Kernel Modules Fixed in Ubuntu 19.04: lxc launch ubuntu-daily:19.04 lxc shell systemctl is-system-running running It appears to be fixed by adding: ConditionVirtualization=!container to both. Can this be backported to 18.04 or are we stuck with special casing 18.04 vs future versions? As far as I know this is the easiest way to see if a container finished starting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811628/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
** Changed in: hud (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: New Status in unbuntu-fr Scripts - apt: Fix Committed Status in hud package in Ubuntu: Fix Committed Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
** Bug watch added: github.com/zeromq/libzmq/issues #3351 https://github.com/zeromq/libzmq/issues/3351 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
https://github.com/zeromq/libzmq/issues/3351 https://github.com/zeromq/libzmq/pull/3353 https://github.com/zeromq/libzmq/releases/tag/v4.3.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
This issue has been assigned CVE-2019-6250 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1811531]
(In reply to Luca Boccassi from comment #0) > The latest version will hopefully arrive in disco via debian unstable soon, > but I would recommend patching older releases. s/disco/tumbleweed/ s/debian unstable/obs factory/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Does it fixes also bionic with ext4? If yes, how? Problem starting some services since november updates Now I installed these last upgrades with 237-3ubuntu10.11 but this didnt fix error... ● systemd-tmpfiles-setup-dev.service loaded failed failedCreate Static Device Nodes in /dev ● systemd-tmpfiles-setup.service loaded failed failedCreate Volatile Files and Directories Description:Ubuntu 18.04.1 LTS Release:18.04 systemd: Installed: 237-3ubuntu10.11 Candidate: 237-3ubuntu10.11 Version table: *** 237-3ubuntu10.11 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs8173584 0 8173584 0% /dev tmpfs tmpfs 1640840 2672 1638168 1% /run /dev/sda3 ext4 1026876725534228 91894180 6% / tmpfs tmpfs 8204192 0 8204192 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock tmpfs tmpfs 8204192 0 8204192 0% /sys/fs/cgroup /dev/md0 ext4 5325203376 4998238260 58519832 99% /phototdata /dev/loop1 squashfs 91648 91648 0 100% /snap/core/6130 /dev/loop0 squashfs 90368 90368 0 100% /snap/core/5897 /dev/loop2 squashfs 91648 91648 0 100% /snap/core/6034 tmpfs tmpfs 1640836 0 1640836 0% /run/user/0 -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1808333] Re: Some servises not-found inactive dead
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => SV (smvl) ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1808333 Title: Some servises not-found inactive dead Status in systemd package in Ubuntu: Invalid Bug description: Hello! After last update ALL my VPS (OpenVZ, diffrent providers) this services is not-found systemctl list-units --type service -all | grep not-found ● apparmor.service not-found inactive dead apparmor.service ● auditd.servicenot-found inactive dead auditd.service ● display-manager.service not-found inactive dead display-manager.service ● keyboard-setup.servicenot-found inactive dead keyboard-setup.service ● rpcbind.service not-found inactive dead rpcbind.service ● systemd-sysusers.service not-found inactive dead systemd-sysusers.service ● systemd-update-done.service not-found inactive dead systemd-update-done.service ● systemd-vconsole-setup.servicenot-found inactive dead systemd-vconsole-setup.service lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808333/+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 1811592] [NEW] systemd-tmpfiles-setup.service fails after update
Public bug reported: 1. Description: Ubuntu 16.04.5 LTS Release:16.04 2. apt-cache policy systemd systemd: Installed: 229-4ubuntu21.15 Candidate: 229-4ubuntu21.15 Version table: *** 229-4ubuntu21.15 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3. After VPS was rebooted I can't to connect via SSH 4. SSH Service fail because systemd-tmpfiles service fail to start after update I can connect to VPS (openVZ) only via emergency console journalctl -b 0 -u systemd-tmpfiles-setup.service -- Logs begin at Sun 2019-01-13 18:34:20 EET, end at Sun 2019-01-13 18:50:00 EET. -- Jan 13 18:34:20 wok.f.time4vps.cloud systemd[1]: Starting Create Volatile Files and Directories... Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/screen: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sudo/ts: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/utmp failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/systemd/netif failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/systemd/netif/links failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/systemd/netif/leases failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: Failed to start Create Volatile Files and Directories. Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state. Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. workaround to start SSH is mkdir /run/sshd The situation like this https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: ssh sshd systemd-tmpfiles -- 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/1811592 Title: systemd-tmpfiles-setup.service fails after update Status in systemd package in Ubuntu: New Bug description: 1. Description: Ubuntu 16.04.5 LTS Release: 16.04 2. apt-cache policy systemd systemd: Installed: 229-4ubuntu21.15 Candidate: 229-4ubuntu21.15 Version table: *** 229-4ubuntu21.15 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3. After VPS was rebooted I can't to connect via SSH 4. SSH Service fail because systemd-tmpfiles service fail to start after update I can connect to VPS (openVZ) only via emergency console journalctl -b 0 -u systemd-tmpfiles-setup.service -- Logs begin at Sun 2019-01-13 18:34:20 EET, end at Sun 2019-01-13 18:50:00 EET. -- Jan 13 18:34:20 wok.f.time4vps.cloud systemd[1]: Starting Create Volatile Files and Directories... Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/screen: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sudo/ts: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/utmp failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/systemd/netif failed: Invalid argument Jan 13
[Touch-packages] [Bug 1811531] Re: remote execution vulnerability
This issue has been assigned CVE-2019-6250 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6250 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeromq3 in Ubuntu. https://bugs.launchpad.net/bugs/1811531 Title: remote execution vulnerability Status in zeromq3 package in Ubuntu: New Status in zeromq3 package in Debian: Fix Released Status in zeromq package in Suse: Confirmed Bug description: Dear Maintainer, A remote execution vulnerability has been reported in zeromq. Full details can be found on the upstream issue tracker [1]. The issue is fixed in upstream version v4.3.1, just released, or with the attached patch which is targeted for v4.2.5 (bionic and cosmic). The latest version will hopefully arrive in disco via debian unstable soon, but I would recommend patching older releases. As mentioned in the upstream tracker and the changelog, the issue can be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as I am aware no CVEs have been assigned nor have been requested as of now. [1] https://github.com/zeromq/libzmq/issues/3351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1811531/+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 1666203] Re: pam_tty_audit failed in pam_open_session
Please see https://wiki.ubuntu.com/SponsorshipProcess and https://wiki.ubuntu.com/StableReleaseUpdates#Procedure if you can volunteer to get the fix landed. Note that I don't expect anyone to work on this any time soon. It needs volunteers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1666203] Re: pam_tty_audit failed in pam_open_session
** Changed in: pam (Ubuntu) Status: Confirmed => Triaged ** Changed in: pam (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1791196] Re: [USB-Audio - US122 MKII, recording] Recording problem
Hi guys, I managed to have this working (on lubuntu) following https://linuxmusicians.com/viewtopic.php?t=16711 In short, blacklist snd_usb_audio (and get the board listed as US-122L instead of US-122mkII) lfredo@alfredo-pc:~$ cat /proc/asound/cards 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xdbff8000 irq 23 1 [US122L ]: USB US-122L - TASCAM US-122L TASCAM US-122L (644:8021 if 0 at 001/002) Then create .asoundrc file. And finally run jackd with the following presets jackd -RP60 -dalsa -dusb_stream:1 -r48000 -p256 -n2 Hope someone find this useful. Regards, Alfredo -- 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/1791196 Title: [USB-Audio - US122 MKII, recording] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: Can't get the US122 MKII listed as an input device. Not in pavucontrol, nor in sound settings nor in jackd. May be this helps, alfredo@alfredo-ubuntu:~$ jackd -d alsa -d hw:MKII jackdmp 1.9.12 ... Acquire audio card Audio1 creating alsa driver ... hw:MKII|hw:MKII|1024|2|48000|0|0|nomon|swmeter|-|32bit ALSA: Cannot open PCM device alsa_pcm for capture. Falling back to playback-only mode ... Please let me know if you need further information. Regards, Alfredo ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alfredo7890 F pulseaudio /dev/snd/controlC1: alfredo7890 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 22:02:55 2018 InstallationDate: Installed on 2018-03-03 (187 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:MKII failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 8 8 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: TASCAM US-122mkII - US122 MKII Symptom_Type: None of the above Title: [USB-Audio - US122 MKII, recording] Recording problem UpgradeStatus: Upgraded to bionic on 2018-09-02 (4 days ago) dmi.bios.date: 03/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX SE Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1791196/+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 1811580] [NEW] systemd fails to start sshd at reboot
Public bug reported: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre-existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: New Bug description: Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+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 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound
I did, it didn't work I forgot to mention -- 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/1810861 Title: USB type C audio adapter (from a Pixel 3) doesn't produce any sound Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use a logitech z200 that works fine, i use it with a usb type c adapter that came with my pixel 3, my speakers arent shown at all in the settings or make sound, its not the usb c adapter because it works fine on my windows dual boot and has worked at one point on ubuntu, regardless of the fact that ubuntu has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i use lsusb, one of the results is google inc., which is my headphone adapter, i can tell because when i unplug it it goes away, even when i plug it into the 3.5 mm headphone jack it doesn't work, i don't know if im forgetting something or not, this is the second time im typing this because i accidentally closed the first tab of this, whats interesting, is now that i go to alsamixer, and press f6 i see option 1.Headphone Adapter, i select it and set the volume all the way up and go to something that makes audio and nothing happens, then i unplug it and see if it disappears, surely enough it does --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-21 (78 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: pulseaudio 1:12.2-0ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 07/05/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.00 dmi.board.name: AB350 Gaming K4 dmi.board.vendor: ASRock 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.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+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
