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:
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
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
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
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.
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
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
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
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
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
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
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
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
** 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()
14 matches
Mail list logo
