[Touch-packages] [Bug 1753433] [NEW] jackd crashed with SIGABRT
Public bug reported: Probably happened in connection with shotcut crashing while being connected to Jackd. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: jackd2 1.9.12~dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3 Uname: Linux 4.15.0-10-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Mon Mar 5 11:12:22 2018 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2333 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 96000 -p 512 -d hw:Intel,0 Signal: 6 SourcePackage: jackd2 StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0 Title: jackd crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1753433 Title: jackd crashed with SIGABRT Status in jackd2 package in Ubuntu: New Bug description: Probably happened in connection with shotcut crashing while being connected to Jackd. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: jackd2 1.9.12~dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3 Uname: Linux 4.15.0-10-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Mon Mar 5 11:12:22 2018 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2333 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: /usr/bin/jackd -T -ndefault -t 200 -p 2048 -R -T -d alsa -n 2 -r 96000 -p 512 -d hw:Intel,0 Signal: 6 SourcePackage: jackd2 StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_rethrow () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libjackserver.so.0 Title: jackd crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-01-23 (41 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1753433/+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 1786635] [NEW] (appstreamcli:8218): GLib-CRITICAL error on exit of apt-get update
Public bug reported: # sudo apt-get update Get:1 http://archive.ubuntu.com/ubuntu cosmic InRelease [242 kB] Hit:2 http://archive.canonical.com/ubuntu cosmic InRelease Hit:3 http://archive.ubuntu.com/ubuntu cosmic-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu cosmic-security InRelease Hit:5 http://archive.ubuntu.com/ubuntu cosmic-backports InRelease Get:6 http://archive.ubuntu.com/ubuntu cosmic/universe Sources [9310 kB] Get:7 http://archive.ubuntu.com/ubuntu cosmic/main amd64 DEP-11 Metadata [470 kB] Get:8 http://archive.ubuntu.com/ubuntu cosmic/main DEP-11 48x48 Icons [120 kB] Get:9 http://archive.ubuntu.com/ubuntu cosmic/main DEP-11 64x64 Icons [243 kB] Get:10 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages [8764 kB] Get:11 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 DEP-11 Metadata [3320 kB] Get:12 http://archive.ubuntu.com/ubuntu cosmic/universe DEP-11 48x48 Icons [2464 kB] Get:13 http://archive.ubuntu.com/ubuntu cosmic/universe DEP-11 64x64 Icons [8480 kB] Get:14 http://archive.ubuntu.com/ubuntu cosmic/multiverse amd64 DEP-11 Metadata [48.4 kB] Get:15 http://archive.ubuntu.com/ubuntu cosmic/multiverse DEP-11 64x64 Icons [221 kB] Fetched 33.7 MB in 13s (2607 kB/s) (appstreamcli:8218): GLib-CRITICAL **: 20:12:55.088: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Reading package lists... Done The GLib-CRITICAL message sounds like there should be something done about it. It does not appear when everything is completely up to date (and consequently to "Fetched ..." message appears either). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apt 1.7.0~alpha2 ProcVersionSignature: Ubuntu 4.17.0-6.7-lowlatency 4.17.9 Uname: Linux 4.17.0-6-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 11 20:14:01 2018 InstallationDate: Installed on 2011-10-14 (2493 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: apt UpgradeStatus: Upgraded to cosmic on 2018-07-30 (12 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1786635 Title: (appstreamcli:8218): GLib-CRITICAL error on exit of apt-get update Status in apt package in Ubuntu: New Bug description: # sudo apt-get update Get:1 http://archive.ubuntu.com/ubuntu cosmic InRelease [242 kB] Hit:2 http://archive.canonical.com/ubuntu cosmic InRelease Hit:3 http://archive.ubuntu.com/ubuntu cosmic-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu cosmic-security InRelease Hit:5 http://archive.ubuntu.com/ubuntu cosmic-backports InRelease Get:6 http://archive.ubuntu.com/ubuntu cosmic/universe Sources [9310 kB] Get:7 http://archive.ubuntu.com/ubuntu cosmic/main amd64 DEP-11 Metadata [470 kB] Get:8 http://archive.ubuntu.com/ubuntu cosmic/main DEP-11 48x48 Icons [120 kB] Get:9 http://archive.ubuntu.com/ubuntu cosmic/main DEP-11 64x64 Icons [243 kB] Get:10 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages [8764 kB] Get:11 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 DEP-11 Metadata [3320 kB] Get:12 http://archive.ubuntu.com/ubuntu cosmic/universe DEP-11 48x48 Icons [2464 kB] Get:13 http://archive.ubuntu.com/ubuntu cosmic/universe DEP-11 64x64 Icons [8480 kB] Get:14 http://archive.ubuntu.com/ubuntu cosmic/multiverse amd64 DEP-11 Metadata [48.4 kB] Get:15 http://archive.ubuntu.com/ubuntu cosmic/multiverse DEP-11 64x64 Icons [221
[Touch-packages] [Bug 1766310] [NEW] apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+
Public bug reported: Removing/purging the file and/or using --reinstall options do not help. Removing the file and installing it with dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb works. When calling dpkg --verify on the apt-installed package, the missing file is flagged. I have no idea what causes this. The file name ending in + maybe? But wouldn't apt call dpkg for installation anyway? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Mon Apr 23 19:15:11 2018 InstallationDate: Installed on 2011-10-14 (2383 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: apt UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago) ** Affects: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1766310 Title: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+ Status in apt package in Ubuntu: New Bug description: Removing/purging the file and/or using --reinstall options do not help. Removing the file and installing it with dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb works. When calling dpkg --verify on the apt-installed package, the missing file is flagged. I have no idea what causes this. The file name ending in + maybe? But wouldn't apt call dpkg for installation anyway? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Mon Apr 23 19:15:11 2018 InstallationDate: Installed on 2011-10-14 (2383 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: apt UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1766310/+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 1766310] Re: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+
Note that https://askubuntu.com/questions/126160/how-can-i-add-the-memtest86 -options-back-to-the-grub-menu would suggest that this strange situation has been subsisting for years by now so it would not appear that many packages apart from memtest86+ are affected by this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1766310 Title: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+ Status in apt package in Ubuntu: New Bug description: Removing/purging the file and/or using --reinstall options do not help. Removing the file and installing it with dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb works. When calling dpkg --verify on the apt-installed package, the missing file is flagged. I have no idea what causes this. The file name ending in + maybe? But wouldn't apt call dpkg for installation anyway? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Mon Apr 23 19:15:11 2018 InstallationDate: Installed on 2011-10-14 (2383 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: apt UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1766310/+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 1766310] Re: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+
I haven't removed /etc/grub.d/memtest86+ myself: maybe it has been declared a configuration file at some point of time and/or some intermediate version of memtest86+ decided to remove it. The independent askubuntu experience would suggest something like that. I have to admit that _now_ purging memtest86+ and reinstalling it via apt-get install also installs the memtest+ program. So while I really had to put up a fight until I got /etc/grub.d/memtest86+ back into my system, I cannot at the current point offer a recipe for how it got lost originally. The anecdotal report from the linked Askubuntu question would suggest that I am not alone in this particular respect but I am currently not able to state how to get there. The system in question might have been changed from an i386 system to an amd64 system without installing from scratch. I'd not rule out that the procedure changing the packages and architecture to amd64 might have been involved. At the point of time of reporting the problem, I thought I had a better grasp of the situation. Maybe a removed conffile should be treated differently from a changed (like empty) conffile? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1766310 Title: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+ Status in apt package in Ubuntu: Incomplete Bug description: Removing/purging the file and/or using --reinstall options do not help. Removing the file and installing it with dpkg -i /var/cache/apt/archives/memtest86+_5.01-3ubuntu2_amd64.deb works. When calling dpkg --verify on the apt-installed package, the missing file is flagged. I have no idea what causes this. The file name ending in + maybe? But wouldn't apt call dpkg for installation anyway? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Mon Apr 23 19:15:11 2018 InstallationDate: Installed on 2011-10-14 (2383 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: apt UpgradeStatus: Upgraded to bionic on 2018-01-23 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1766310/+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 1791132] [NEW] package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of pa
Public bug reported: Don't think I changed the configuration file manually ever. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.23.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-lowlatency 4.17.17 Uname: Linux 4.17.0-9-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Thu Sep 6 18:36:08 2018 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 InstallationDate: Installed on 2011-10-14 (2519 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu4 apt 1.7.0~alpha3 SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 UpgradeStatus: Upgraded to cosmic on 2018-07-30 (38 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- 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/1791132 Title: package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 Status in gtk+3.0 package in Ubuntu: New Bug description: Don't think I changed the configuration file manually ever. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libgtk-3-0 3.23.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-lowlatency 4.17.17 Uname: Linux 4.17.0-9-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Thu Sep 6 18:36:08 2018 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 InstallationDate: Installed on 2011-10-14 (2519 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu4 apt 1.7.0~alpha3 SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.23.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:amd64 UpgradeStatus: Upgraded to cosmic on 2018-07-30 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1791132/+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 1707083] [NEW] mkrfc2734 crashed with SIGSEGV in get_leaf_size()
Public bug reported: Happened when called with sudo. As normal user, there did not seem to be a problem. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: libavc1394-tools 0.5.4-4 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency i686 ApportVersion: 2.20.6-0ubuntu4 Architecture: i386 Date: Fri Jul 28 01:30:27 2017 Dependencies: gcc-7-base 7.1.0-7ubuntu1 libavc1394-0 0.5.4-4 libc6 2.24-12ubuntu1 libgcc1 1:7.1.0-7ubuntu1 libraw1394-11 2.1.2-1 ExecutablePath: /usr/bin/mkrfc2734 InstallationDate: Installed on 2011-10-14 (2113 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: mkrfc2734 SegvAnalysis: Segfault happened at: 0xb7726304 :mov(%eax),%eax PC (0xb7726304) ok source "(%eax)" (0xc374a91c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libavc1394 StacktraceTop: get_leaf_size () from /usr/lib/i386-linux-gnu/librom1394.so.0 rom1394_get_size () from /usr/lib/i386-linux-gnu/librom1394.so.0 ?? () __libc_start_main (main=0x80487b0, argc=1, argv=0xbff4d5c4, init=0x8048a70, fini=0x8048ad0, rtld_fini=0xb7788080 <_dl_fini>, stack_end=0xbff4d5bc) at ../csu/libc-start.c:291 ?? () Title: mkrfc2734 crashed with SIGSEGV in get_leaf_size() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: libavc1394 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash artful i386 need-i386-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libavc1394 in Ubuntu. https://bugs.launchpad.net/bugs/1707083 Title: mkrfc2734 crashed with SIGSEGV in get_leaf_size() Status in libavc1394 package in Ubuntu: New Bug description: Happened when called with sudo. As normal user, there did not seem to be a problem. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: libavc1394-tools 0.5.4-4 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency i686 ApportVersion: 2.20.6-0ubuntu4 Architecture: i386 Date: Fri Jul 28 01:30:27 2017 Dependencies: gcc-7-base 7.1.0-7ubuntu1 libavc1394-0 0.5.4-4 libc6 2.24-12ubuntu1 libgcc1 1:7.1.0-7ubuntu1 libraw1394-11 2.1.2-1 ExecutablePath: /usr/bin/mkrfc2734 InstallationDate: Installed on 2011-10-14 (2113 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: mkrfc2734 SegvAnalysis: Segfault happened at: 0xb7726304 : mov(%eax),%eax PC (0xb7726304) ok source "(%eax)" (0xc374a91c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libavc1394 StacktraceTop: get_leaf_size () from /usr/lib/i386-linux-gnu/librom1394.so.0 rom1394_get_size () from /usr/lib/i386-linux-gnu/librom1394.so.0 ?? () __libc_start_main (main=0x80487b0, argc=1, argv=0xbff4d5c4, init=0x8048a70, fini=0x8048ad0, rtld_fini=0xb7788080 <_dl_fini>, stack_end=0xbff4d5bc) at ../csu/libc-start.c:291 ?? () Title: mkrfc2734 crashed with SIGSEGV in get_leaf_size() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libavc1394/+bug/1707083/+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 1709461] [NEW] jackd assert failure: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed.
Public bug reported: Daisy-chained devices, trying to select one for operation. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed. CrashCounter: 1 CurrentDesktop: XFCE Date: Tue Aug 8 20:47:34 2017 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2125 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3 Signal: 6 SourcePackage: jackd2 StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92 __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at assert.c:101 IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoTask::updateShadowMapHelper() () at /usr/lib/libffado.so.2 Title: jackd assert failure: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare ** Affects: jackd2 (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash artful ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1709461 Title: jackd assert failure: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed. Status in jackd2 package in Ubuntu: New Bug description: Daisy-chained devices, trying to select one for operation. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AssertionMessage: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed. CrashCounter: 1 CurrentDesktop: XFCE Date: Tue Aug 8 20:47:34 2017 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2125 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: jackd -d firewire -d fw:0 -r 96000 -p 512 -n 3 Signal: 6 SourcePackage: jackd2 StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f5fe688a1b7 "m_handle == NULL", file=file@entry=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=line@entry=1795, function=function@entry=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at assert.c:92 __GI___assert_fail (assertion=0x7f5fe688a1b7 "m_handle == NULL", file=0x7f5fe6889058 "src/libieee1394/IsoHandlerManager.cpp", line=1795, function=0x7f5fe688ada0 "bool IsoHandlerManager::IsoHandler::enable(int)") at assert.c:101 IsoHandlerManager::IsoHandler::enable(int) () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::updateState() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoTask::updateShadowMapHelper() () at /usr/lib/libffado.so.2 Title: jackd assert failure: jackd: src/libieee1394/IsoHandlerManager.cpp:1795: bool IsoHandlerManager::IsoHandler::enable(int): Assertion `m_handle == NULL' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1709461/+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 1705570] Re: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped()
Only a single device connected, the connection might have been unreliable while I plugged a headphone. dmesg says: [ 566.417496] firewire_core :15:00.1: created device fw1: GUID 0005950400400fc2, S400 [ 567.712261] firewire_core :15:00.1: BM lock failed (timeout), making local node (ffc0) root [ 567.712267] firewire_core :15:00.1: phy config: new root=ffc0, gap_count=5 [ 3122.465682] firewire_ohci :15:00.1: DMA context still active (0x2411) [ 3157.256925] jackd[3206]: segfault at 64 ip 7f47653b56fc sp 7ffc73e76980 error 6 in libffado.so.2.3.0[7f47651fe000+37f000] [ 3232.497578] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.497941] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.498649] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.499225] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.499422] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.499799] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.500279] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.500547] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.500924] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.501283] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.501679] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.502076] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.502411] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.502779] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.503139] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.503536] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.503898] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.504280] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.504654] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.505051] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.505400] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.505779] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.506133] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.506526] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3232.507288] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3233.016244] firewire_core :15:00.1: rediscovered device fw0 [ 3245.052188] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3245.052351] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3245.052558] firewire_ohci :15:00.1: isochronous cycle inconsistent [ 3245.052990] firewire_ohci :15:00.1: node ID not valid, new bus reset in progress [ 3245.560197] firewire_core :15:00.1: giving up on node ffc0: reading config rom failed: bus reset [ 3245.560247] firewire_core :15:00.1: rediscovered device fw0 [ 3245.560255] firewire_core :15:00.1: giving up on node ffc1: reading config rom failed: bus reset [ 3245.560261] firewire_core :15:00.1: giving up on node ffc0: reading config rom failed: bus reset and on the command line I get dak@lola:~$ ffado-test Discover --- FFADO test and diagnostic utility Part of the FFADO project -- www.ffado.org Version: 2.3.0- (C) 2008, Daniel Wagner, Pieter Palmers This program comes with ABSOLUTELY NO WARRANTY. --- Could not initialize device manager 1503588845175934: Fatal (devicemanager.cpp)[ 187] initialize: No firewire adapters (ports) found. no message buffer overruns Which is a bit unsettling because the firewire adapter is actually built-in: 15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) Syslog also contains: Aug 24 17:31:41 lola kernel: [ 3122.465682] firewire_ohci :15:00.1: DMA context still active (0x2411) Aug 24 17:32:16 lola kernel: [ 3157.256925] jackd[3206]: segfault at 64 ip 7f47653b56fc sp 7ffc73e76980 error 6 in libffado.so.2.3.0[7f47651fe000+37f000] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1705570 Title: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped() Status in jackd2 package in Ubuntu: New Bug description: Started jackd (version 2) with jackd -d firewire -r 96000 and had a Mackie Onyx
[Touch-packages] [Bug 1665359] Re: apport-gtk crashed with SIGABRT in g_assertion_message()
** Information type changed from Private to Public -- 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/1665359 Title: apport-gtk crashed with SIGABRT in g_assertion_message() Status in apport package in Ubuntu: New Bug description: No further information available. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: apport-gtk 2.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-lowlatency 4.9.5 Uname: Linux 4.9.0-15-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Thu Feb 16 14:46:52 2017 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2011-10-14 (1952 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk Signal: 6 SourcePackage: apport StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to zesty on 2017-01-05 (41 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1665359/+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 1674072] [NEW] fluidsynth crashed with SIGSEGV in jack_port_get_buffer()
Public bug reported: Just tried starting it from the command line with a midi file. Jack available but not running at the time I tried this. I cannot vouch whether this was started with or without pasuspender: I tried both since without pasuspender fluidsynth (or jack) complained about Pulseaudio hogging the device. It could have crashed after the complaint, or it could have crashed independently without such a complaint. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: fluidsynth 1.1.6-4 ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1 Uname: Linux 4.10.0-11-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sun Mar 19 09:28:47 2017 ExecutablePath: /usr/bin/fluidsynth InstallationDate: Installed on 2011-10-14 (1982 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: fluidsynth /home/username/scores/tabber.midi SegvAnalysis: Segfault happened at: 0xf72d9194 :mov 0xc(%esi),%edx PC (0xf72d9194) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: fluidsynth StacktraceTop: jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0 fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1 ?? () from /usr/lib/i386-linux-gnu/libjack.so.0 start_thread (arg=0xf6809b40) at pthread_create.c:333 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113 Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer() UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare ** Affects: fluidsynth (Ubuntu) Importance: Medium Status: New ** Tags: apport-crash i386 zesty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fluidsynth in Ubuntu. https://bugs.launchpad.net/bugs/1674072 Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer() Status in fluidsynth package in Ubuntu: New Bug description: Just tried starting it from the command line with a midi file. Jack available but not running at the time I tried this. I cannot vouch whether this was started with or without pasuspender: I tried both since without pasuspender fluidsynth (or jack) complained about Pulseaudio hogging the device. It could have crashed after the complaint, or it could have crashed independently without such a complaint. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: fluidsynth 1.1.6-4 ProcVersionSignature: Ubuntu 4.10.0-11.13-lowlatency 4.10.1 Uname: Linux 4.10.0-11-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sun Mar 19 09:28:47 2017 ExecutablePath: /usr/bin/fluidsynth InstallationDate: Installed on 2011-10-14 (1982 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: fluidsynth /home/username/scores/tabber.midi SegvAnalysis: Segfault happened at: 0xf72d9194 : mov 0xc(%esi),%edx PC (0xf72d9194) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: fluidsynth StacktraceTop: jack_port_get_buffer () from /usr/lib/i386-linux-gnu/libjack.so.0 fluid_jack_driver_process () from /usr/lib/i386-linux-gnu/libfluidsynth.so.1 ?? () from /usr/lib/i386-linux-gnu/libjack.so.0 start_thread (arg=0xf6809b40) at pthread_create.c:333 clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:113 Title: fluidsynth crashed with SIGSEGV in jack_port_get_buffer() UpgradeStatus: Upgraded to zesty on 2017-01-05 (72 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1674072/+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 1703176] [NEW] jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed.
Public bug reported: This may or may not be an artifact of me running a 32-bit userland on a 64-bit kernel (for debugging and testing purposes). However, preceding the command line with "setarch i386" does not help. The exact command line used was jackd -d alsa -X raw -d hw:0 To trigger the bug, it is important that there actually is a raw Midi device available on the system. Any such device will trigger the problem in my experience. Here is the complete output: jackdmp 1.9.11 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 2 periods for playback scan: added port hw:1,0,0 in-hw-1-0-0-UM-4-MIDI-1 scan: added port hw:1,0,1 in-hw-1-0-1-UM-4-MIDI-2 scan: added port hw:1,0,2 in-hw-1-0-2-UM-4-MIDI-3 scan: added port hw:1,0,3 in-hw-1-0-3-UM-4-MIDI-4 scan: added port hw:1,0,0 out-hw-1-0-0-UM-4-MIDI-1 scan: added port hw:1,0,1 out-hw-1-0-1-UM-4-MIDI-2 scan: added port hw:1,0,2 out-hw-1-0-2-UM-4-MIDI-3 scan: added port hw:1,0,3 out-hw-1-0-3-UM-4-MIDI-4 ALSA lib rawmidi_hw.c:100:(snd_rawmidi_hw_params) SNDRV_RAWMIDI_IOCTL_PARAMS failed: Invalid argument jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. Aborted (core dumped) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17 Uname: Linux 4.10.0-26-lowlatency x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 AssertionMessage: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. CurrentDesktop: MATE Date: Sun Jul 9 10:27:38 2017 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2094 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: jackd -d alsa -X raw -d hw:0 Signal: 6 SourcePackage: jackd2 StacktraceTop: __assert_fail_base (fmt=0xf743009c "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0xf6f38cd3 "err >= 0", file=0xf6f48d35 "rawmidi.c", line=268, function=0xf6f49588 "snd_rawmidi_open_conf") at assert.c:92 __GI___assert_fail (assertion=0xf6f38cd3 "err >= 0", file=0xf6f48d35 "rawmidi.c", line=268, function=0xf6f49588 "snd_rawmidi_open_conf") at assert.c:101 () at /usr/lib/i386-linux-gnu/libasound.so.2 () at /usr/lib/i386-linux-gnu/libasound.so.2 snd_rawmidi_open () at /usr/lib/i386-linux-gnu/libasound.so.2 Title: jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. UpgradeStatus: Upgraded to artful on 2017-05-03 (66 days ago) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare ** Affects: jackd2 (Ubuntu) Importance: Medium Status: New ** Tags: apport-crash artful i386 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1703176 Title: jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed. Status in jackd2 package in Ubuntu: New Bug description: This may or may not be an artifact of me running a 32-bit userland on a 64-bit kernel (for debugging and testing purposes). However, preceding the command line with "setarch i386" does not help. The exact command line used was jackd -d alsa -X raw -d hw:0 To trigger the bug, it is important that there actually is a raw Midi device available on the system. Any such device will trigger the problem in my experience. Here is the complete output: jackdmp 1.9.11 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period
[Touch-packages] [Bug 1703176] Re: jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed.
I think that the problem is likely in
/usr/include/sound/asound.h:625
struct snd_rawmidi_params {
int stream;
size_t buffer_size; /* queue size in bytes */
size_t avail_min; /* minimum avail bytes for wakeup */
unsigned int no_active_sensing: 1; /* do not send active sensing byte
in close() */
unsigned char reserved[16]; /* reserved for future use */
};
struct snd_rawmidi_status {
int stream;
struct timespec tstamp; /* Timestamp */
size_t avail; /* available bytes */
size_t xruns; /* count of overruns since last status
(in bytes) */
unsigned char reserved[16]; /* reserved for future use */
};
Here are 4 uses of size_t which will result in different structures for
32-bit and 64-bit compilations even though 32-bit binaries can
communicate with a 64-bit kernel via ioctl.
So this would appear to require fixing in the ALSA headers of the kernel
and recompiling alsa-lib with the changed headers.
I think using unsigned rather than size_t should work fine in this
regard. However, there are also structures using snd_pcm_uframes_t
which is typedeffed to unsigned long and thus should also be
architecture-dependent.
It's not clear to me why or how the respective ioctl calls would work
for PCM here when running with a 32-bit alsalib/executable and a 64-bit
kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1703176
Title:
jackd assert failure: jackd: rawmidi.c:268: snd_rawmidi_open_conf:
Assertion `err >= 0' failed.
Status in jackd2 package in Ubuntu:
New
Bug description:
This may or may not be an artifact of me running a 32-bit userland on
a 64-bit kernel (for debugging and testing purposes).
However, preceding the command line with "setarch i386" does not help.
The exact command line used was
jackd -d alsa -X raw -d hw:0
To trigger the bug, it is important that there actually is a raw Midi
device available on the system. Any such device will trigger the
problem in my experience.
Here is the complete output:
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
scan: added port hw:1,0,0 in-hw-1-0-0-UM-4-MIDI-1
scan: added port hw:1,0,1 in-hw-1-0-1-UM-4-MIDI-2
scan: added port hw:1,0,2 in-hw-1-0-2-UM-4-MIDI-3
scan: added port hw:1,0,3 in-hw-1-0-3-UM-4-MIDI-4
scan: added port hw:1,0,0 out-hw-1-0-0-UM-4-MIDI-1
scan: added port hw:1,0,1 out-hw-1-0-1-UM-4-MIDI-2
scan: added port hw:1,0,2 out-hw-1-0-2-UM-4-MIDI-3
scan: added port hw:1,0,3 out-hw-1-0-3-UM-4-MIDI-4
ALSA lib rawmidi_hw.c:100:(snd_rawmidi_hw_params) SNDRV_RAWMIDI_IOCTL_PARAMS
failed: Invalid argument
jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err >= 0' failed.
Aborted (core dumped)
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17
Uname: Linux 4.10.0-26-lowlatency x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: i386
AssertionMessage: jackd: rawmidi.c:268: snd_rawmidi_open_conf: Assertion `err
>= 0' failed.
CurrentDesktop: MATE
Date: Sun Jul 9 10:27:38 2017
ExecutablePath: /usr/bin/jackd
InstallationDate: Installed on 2011-10-14 (2094 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: jackd -d alsa -X raw -d hw:0
Signal: 6
SourcePackage: jackd2
StacktraceTop:
__assert_fail_base (fmt=0xf743009c "%s%s%s:%u: %s%sAssertion `%s'
failed.\n%n", assertion=0xf6f38cd3 "err >= 0", file=0xf6f48d35 "rawmidi.c",
line=268, function=0xf6f49588 "snd_rawmidi_open_conf") at assert.c:92
__GI___assert_fail (assertion=0xf6f38cd3 "err >= 0", file=0xf6f48d35
"rawmidi.c", line=268, function=0xf6f49588 "snd_rawmidi_open_conf") at
assert.c:101
() at /usr/lib/i386-linux-gnu/libasound.so.2
() at /usr/lib/i386-linux-gnu/libasound.so.2
snd_rawmidi_open () at /usr/lib/i386-linux-gnu/lib
[Touch-packages] [Bug 1705570] [NEW] jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped()
Public bug reported: Started jackd (version 2) with jackd -d firewire -r 96000 and had a Mackie Onyx 1620 (with Firewire extension card) and an Alesis iO|14 connected in series. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency i686 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 20 22:22:11 2017 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2106 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: jackd -d firewire -r 96000 SegvAnalysis: Segfault happened at: 0xb5e9df68 <_ZN9Streaming15StreamProcessor14packetsStoppedEv+16>:movl $0x2,0x34(%eax) PC (0xb5e9df68) ok source "$0x2" ok destination "0x34(%eax)" (0x0034) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: jackd2 StacktraceTop: Streaming::StreamProcessor::packetsStopped() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::disable() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::~IsoHandler() () at /usr/lib/libffado.so.2 IsoHandlerManager::pruneHandlers() () at /usr/lib/libffado.so.2 IsoHandlerManager::unregisterStream(Streaming::StreamProcessor*) () at /usr/lib/libffado.so.2 Title: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash artful i386 need-i386-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1705570 Title: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped() Status in jackd2 package in Ubuntu: New Bug description: Started jackd (version 2) with jackd -d firewire -r 96000 and had a Mackie Onyx 1620 (with Firewire extension card) and an Alesis iO|14 connected in series. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: jackd2 1.9.10+20150825git1ed50c92~dfsg-2ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency i686 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 CurrentDesktop: MATE Date: Thu Jul 20 22:22:11 2017 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2011-10-14 (2106 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) ProcCmdline: jackd -d firewire -r 96000 SegvAnalysis: Segfault happened at: 0xb5e9df68 <_ZN9Streaming15StreamProcessor14packetsStoppedEv+16>: movl $0x2,0x34(%eax) PC (0xb5e9df68) ok source "$0x2" ok destination "0x34(%eax)" (0x0034) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: jackd2 StacktraceTop: Streaming::StreamProcessor::packetsStopped() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::disable() () at /usr/lib/libffado.so.2 IsoHandlerManager::IsoHandler::~IsoHandler() () at /usr/lib/libffado.so.2 IsoHandlerManager::pruneHandlers() () at /usr/lib/libffado.so.2 IsoHandlerManager::unregisterStream(Streaming::StreamProcessor*) () at /usr/lib/libffado.so.2 Title: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1705570/+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
