[Bug 2062526] Re: DNS for snaps like Firefox and Chromium fails

I can certify that after today's system upgrade (mainly including the 6.8.0-28-lowlatency kernel), booting into the new kernel made the difference between Chromium-browser not working and working (I had previously replaced my Firefox browser with a native version from Mozilla's APT repository

[Bug 2062526] [NEW] DNS for snaps like Firefox and Chromium fails

Public bug reported: While this sounds somewhat similar to the currently reported showstopper, none of the workarounds in that report helps for me and all snaps are affected. This started about a week ago. I am currently making do with using the natively installed Epiphany while using Firefox

[Bug 2058807] [NEW] Segmentation fault

Public bug reported: Frequently (but not always, haven't figured out what makes the difference) I cannot start modem-manager-gui, getting the following crash output on the console: modem-manager-gui (modem-manager-gui:186352): Gtk-WARNING **: 12:49:10.872: Theme directory places/128 of theme

[Bug 1965531] [NEW] xiccd crashed with SIGSEGV in outstring_func()

Public bug reported: Don't have further details since apport for some reason tends to queue its reports and then offers to report them weeks later when it's impossible to remember the circumstances. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xiccd 0.3.0-1 ProcVersionSignature:

[Bug 1965532] [NEW] guvcview assert failure: double free or corruption (!prev)

Public bug reported: No further information available. Possible that occured when exiting the app. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: guvcview 2.0.7-2-1 ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 ApportVersion:

[Bug 1964402] [NEW] atril crashed with SIGSEGV

Public bug reported: Happened without user interaction I believe. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: atril 1.26.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture:

[Bug 1943124] Re: Upgrade fails due to "text file busy"

It was not an option to keep my system broken for longer, so I mounted my system disk to a working Ubuntu installation and used 'dpkg --root=/mnt --force-script-chrootless -i ...' from there for getting libc installed, after which a native apt install -f was able to take it from there. Let's hope

[Bug 1943124] Re: Upgrade fails due to "text file busy"

Not really? It's just apt install -o dpkg::options::=-D7200 -f Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libc-bin libc6 The following packages will be

[Bug 1943124] Re: Upgrade fails due to "text file busy"

Downgraded libc-bin to Focal, then did apt --fix-broken install . It attempted to install both libc-bin and libc6 and failed with the same error as previously while I didn't get the loader complaint associated with not being able to run /usr/bin/locale . So the inability to execute

[Bug 1943124] Re: Upgrade fails due to "text file busy"

I did and sent the tar file encrypted to your Gmail account. Hope you got it. Another thing: libc6-bin is already installed in the new version, and calling `locale` gives an error message like locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by locale) The

[Bug 1943124] Re: Upgrade fails due to "text file busy"

Ok, here is another possible problem source: I just did 'ls /etc/ld*' by accident and got this: $ ls /etc/ld* /etc/ld.so.conf /etc/ld.so.nohwcap /etc/ldap: ldap.conf /etc/ld.so.conf.d: fakeroot-i386-linux-gnu.confi386-linux-gnu.conf libc.conf x86_64-linux-gnu.conf

[Bug 1943124] Re: Upgrade fails due to "text file busy"

Additional info: switched in the BIOS to single CPU with no hyperthreading and booted into recovery mode (and checked with cat /proc/cpuinfo that there was only a single CPU present to Linux). No change, still bombed out with the same error on apt --fix-broken install . So if there is a race

[Bug 1943124] Re: Upgrade fails due to "text file busy"

Here you are. I actually got here via `do-release-update -d` (I tried adding a few packages manually via `dpkg` afterwards to get out of the current bad situation but they are likely not having much of an impact on the logs). If you say this may be a race condition, should I try reducing the

Re: [Bug 1943124] Re: Upgrade fails due to "text file busy"

rd locations that are consulted in the absence of the cache file. -- David Kastrup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943124 Title: Upgrade fails due to "text file busy"

[Bug 1943124] Re: Upgrade fails due to "text file busy"

Some more info: After the upgrade fails, there is no '/lib/x86_64-linux-gnu/ld- linux-x86-64.so.2.dpkg-new' and there is no '/etc/ld.so.cache', meaning that I need to run 'ldconfig' to get back a mostly working system. With no '/etc/ld.so.cache' after the failure (even if you started with one

[Bug 1943124] [NEW] Upgrade fails due to "text file busy"

Public bug reported: I cannot upgrade to the current impish, getting the following error (even in a root shell in recovery mode): $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The

[Bug 1868363] Re: /etc/gpsd/device-hook not actually called

The script now gets executed but doesn't have the original permissions, so I need to rework what it does. Here is what I get on the console: dak@lola:/usr/local/tmp/lilypond$ sudo gpsd -n -N /dev/ttyACM2 /etc/gpsd/device-hook: 2: cannot create /tmp/bubu: Permission denied /etc/gpsd/device-hook:

[Bug 1868363] Re: /etc/gpsd/device-hook not actually called

Audit mentions /bin/dash, not /usr/bin/dash . Sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868363 Title: /etc/gpsd/device-hook not actually called To manage notifications about this bug

[Bug 1868363] Re: /etc/gpsd/device-hook not actually called

Version 3.20-5ubuntu2-ppa1 is what I have installed. I don't even think it directly calls the interpreter: I discovered that my hashbang was #!/bin/bash while the complained was about /usr/bin/dash (and still is). That rather sounds like system rather than exec is being used here. Or the

[Bug 1868363] Re: /etc/gpsd/device-hook not actually called

PPA doesn't help. [113847.653970] audit: type=1400 audit(1585146074.312:1469): apparmor="DENIED" operation="exec" profile="/usr/sbin/gpsd" name="/bin/dash" pid=363200 comm="gpsd" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 [113847.655351] audit: type=1400 audit(1585146074.313:1470):

[Bug 1868363] Re: /etc/gpsd/device-hook not actually called

The dmesg output looks like the following: [112720.972130] audit: type=1400 audit(1585144947.600:71): apparmor="DENIED" operation="exec" profile="/usr/sbin/gpsd" name="/bin/dash" pid=353559 comm="gpsd" requested_mask="x" denied_mask="x" fsuid=0 ouid=0 [112720.973971] audit: type=1400

[Bug 1868884] [NEW] thunar crashed with SIGSEGV

Public bug reported: This has been happening for years on end now with SDcards in a card reader at random times while browsing. Possibly short after automount, but also on other occasions. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: thunar 1.8.12-1 ProcVersionSignature: Ubuntu

[Bug 1868363] [NEW] /etc/gpsd/device-hook not actually called

Public bug reported: The manual page of gpsd states When a device is activated (i.e. a client requests data from it), gpsd attempts to execute a hook from /etc/gpsd/device-hook with first command line argument set to the pathname of the device and the second to ACTIVATE. On

[Bug 1868119] [NEW] thunar crashed with SIGSEGV

*** This bug is a duplicate of bug 1834014 *** https://bugs.launchpad.net/bugs/1834014 Public bug reported: Happened while browing an SDcard. I keep getting these kind of crashes for years now. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: thunar 1.8.12-1 ProcVersionSignature:

[Bug 1843337] Re: thunar crashed with SIGSEGV in g_mutex_lock()

Happened to me right now without any Thunar window open (I think), just with it providing XFCE4 desktop icons. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843337 Title: thunar crashed with

[Bug 1846965] [NEW] Bad German words in /usr/share/dict/ogerman: Bauernbefeiung, Anschlußleitung, Devalvierung, Geisterbwegung, Herabsetztung

Public bug reported: Bauernbefeiung -> Bauernbefreiung Anschlußleitung -> Anschlußleistung (Anschlußleitung could be an EE or plumbing term but seems a lot less common than Anschlußleistung which has meanings both in EE and civil administration) Devalvierung -> Devaluierung Geisterbwegung ->

[Bug 1845550] [NEW] xfdesktop crashed with SIGSEGV in g_type_check_instance_is_a()

Public bug reported: Bug text superficially is that of #733822 but that one is supposed to be fixed for a long time. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xfdesktop4 4.14.1-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-lowlatency 5.3.0-rc8 Uname: Linux 5.3.0-10-lowlatency x86_64

[Bug 1843337] [NEW] thunar crashed with SIGSEGV in g_mutex_lock()

Public bug reported: Another crash while doing basic file viewing with several Thunar windows open. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: thunar 1.8.9-1 ProcVersionSignature: Ubuntu 5.2.0-15.16-lowlatency 5.2.9 Uname: Linux 5.2.0-15-lowlatency x86_64 ApportVersion:

[Bug 1834014] [NEW] thunar crashed with SIGSEGV

Public bug reported: This happens so frequently by now that Thunar is becoming almost unusable for browsing memory cards. One particularly surefire way to crash Thunar is to unmount a memory card with some application still accessing it. Thunar pops up a notification that an application is

[Bug 1832992] [NEW] thunar crashed with SIGSEGV in g_mutex_lock()

Public bug reported: This is getting increasingly frequent and annoying. This time just trying to open a memory card was enough to trigger it. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: thunar 1.8.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-lowlatency 5.0.8 Uname: Linux

[Bug 1820130] Re: modem-manager-gui assert failure: munmap_chunk(): invalid pointer

I've since updated to Eoan. Don't know under what circumstances the bug triggers exactly but startup here appears to work currently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820130 Title:

[Bug 1830621] [NEW] thunar crashed with SIGSEGV

Public bug reported: This one happened when trying to unmount an extfs device (SDcard) which was still busy. Notification appeared, so I closed two eom image windows still open on the device (probably blocking it by virtue of having their cwd on the device rather than any file actively open).

[Bug 1829921] [NEW] thunar crashed with SIGSEGV

Public bug reported: Not sure what other bug this may be equal to. Crashed while exploring folders, possibly in connection with SDcard in a USB reader (Expresscard size factor, Sony VGP-MCA20). Bus 002 Device 006: ID 054c:0281 Sony Corp. Device Descriptor: bLength18

[Bug 1816245] Re: xfdesktop crashed with SIGSEGV

Random crashes are _never_ reproducible. I report those as I encounter them but often are thwarted by the bug reporting system telling me that this bug has already been reported and I can add information to it but then redirects me to a bug page that refuses to let me view/access anything because

[Bug 1821589] [NEW] thunar crashed with SIGSEGV

Public bug reported: Double-clicked on an SDcard icon (only mounted on-demand on my desktop). Works most of the time: this is a sporadic occurence. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: thunar 1.8.4-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux

[Bug 1820130] [NEW] modem-manager-gui assert failure: munmap_chunk(): invalid pointer

Public bug reported: No idea since when it does that. Must be some Disco Dingo problem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: modem-manager-gui 0.0.19.1-1build1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 ApportVersion:

[Bug 1817330] [NEW] digikam crashed with SIGSEGV in QMutex::lock()

Public bug reported: Barely started it. Don't run KDE regularly so the crash might have to do with it having to start/stop the KDE subsystem. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: digikam 4:5.9.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-lowlatency 4.19.20 Uname:

[Bug 1816245] [NEW] xfdesktop crashed with SIGSEGV

Public bug reported: Upon waking up computer from sleep. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: xfdesktop4 4.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-lowlatency 4.19.18 Uname: Linux 4.19.0-12-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64

[Bug 1815986] [NEW] wrapper-2.0 crashed with SIGABRT in g_slice_alloc()

Public bug reported: No idea what triggered this. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: libxfce4panel-2.0-4 4.13.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-lowlatency 4.19.18 Uname: Linux 4.19.0-12-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64

[Bug 1765860] Re: blueman-browse crashed with blueman.bluez.errors.DBusInProgressError in warp(): Operation already in progress

Post scriptum: the USB_BLACKLIST_BTUSB thing only very temporarily appeared to do the trick. I currently am back at the situation where no matter what I do, blueman-browse crashes with an "operation still in progress" exception within an "operation still in progress" exception and find no way to

[Bug 1814129] [NEW] xfce4-appfinder crashed with SIGSEGV in g_slice_alloc()

*** This bug is a duplicate of bug 1814112 *** https://bugs.launchpad.net/bugs/1814112 Public bug reported: No idea what this is about. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: xfce4-appfinder 4.13.2-1 ProcVersionSignature: Ubuntu 4.18.0-11.12-lowlatency 4.18.12 Uname: Linux

[Bug 1814112] [NEW] xfce4-appfinder crashed with SIGSEGV in g_slice_alloc()

Public bug reported: After screen was locked, I think. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: xfce4-appfinder 4.13.2-1 ProcVersionSignature: Ubuntu 4.18.0-11.12-lowlatency 4.18.12 Uname: Linux 4.18.0-11-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64

[Bug 1811479] [NEW] wrapper-2.0 crashed with SIGSEGV in g_slice_alloc()

Public bug reported: Right after system update. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: libxfce4panel-2.0-4 4.13.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-lowlatency 4.18.12 Uname: Linux 4.18.0-11-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64

[Bug 1713432] Re: Ristretto crawls to a halt on USB1.1 file systems

Good call, but disabling the thumbnail bar doesn't help with the startup time, either when starting by double-clicking on a file in the file manager or by starting it on the command line (with a directory name). -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1713432] Re: Ristretto crawls to a halt on USB1.1 file systems

To put a perspective on a "best implementation" perspective: in the WYSIWYG LaTeX rendering environment "preview-latex" on Emacs, the strategy was to place all unrendered images of a document (corresponding to Ristretto's file lists) in a list and feed a queue with something like 4 places from

[Bug 1713432] Re: Ristretto crawls to a halt on USB1.1 file systems

It is still the case in 18.10 and it even happens on USB2.0 or even image directories on the internal SSD drive. From the visual appearance, I suspect on-the-fly thumbnail generation for the side bar to be at fault. It should likely be made to happen in its own thread or process without the main

[Bug 1798838] [NEW] package elpa-magit 2.13.0-3 failed to install/upgrade: installed elpa-magit package post-installation script subprocess returned error exit status 1

Public bug reported: Just apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 18.10 Package: elpa-magit 2.13.0-3 ProcVersionSignature: Ubuntu 4.18.0-10.11-lowlatency 4.18.12 Uname: Linux 4.18.0-10-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19

[Bug 1797454] [NEW] gvfsd-gphoto2 assert failure: malloc_consolidate(): invalid chunk size

Public bug reported: Could have been in the connection with removing a PTP source from the system. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gvfs-backends 1.38.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-lowlatency 4.18.7 Uname: Linux 4.18.0-8-lowlatency x86_64

[Bug 1765860] Re: blueman-browse crashed with blueman.bluez.errors.DBusInProgressError in warp(): Operation already in progress

So I finally figured out how to avoid triggering this problem. The clue was from dmesg: [ 4130.799255] Bluetooth: hci0: last event is not cmd complete (0x0f) Which finally led me to changing in /etc/default/tlp the following line from 0 to 1 : # Bluetooth devices are excluded from USB

[Bug 1765860] Re: blueman-browse crashed with blueman.bluez.errors.DBusInProgressError in warp(): Operation already in progress

Whenever I try reporting additional circumstances, I get directed to the page https://bugs.launchpad.net/bugs/1754147 with the message Lost something? This page does not exist, or you may not have permission to see it. If you have been to this page before, it is possible it has been removed.

[Bug 1792809] [NEW] simple-scan crashed with SIGSEGV

Public bug reported: Scanner failed to power up for some reason (it's blacklisted from USB power saving since that was what made it fail at some time before). The SIGSEGV occured afterwards. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: simple-scan 3.30.0-1 ProcVersionSignature:

[Bug 1760092] Re: blueman-assistant crashed with blueman.bluez.errors.DBusInProgressError in warp(): Operation already in progress

This happens every time I search for Bluetooth devices. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760092 Title: blueman-assistant crashed

[Bug 1791134] Re: update-manager crashed with signal 5

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791134 Title: update-manager crashed with signal 5 To manage notifications about this bug go to:

[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 package libgtk-3-0:

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:

[Bug 1790707] [NEW] ffado-mixer crashed with RuntimeError in /usr/share/ffado-mixer-qt4/ffado/import_pyqt.py: the PyQt5.QtCore and PyQt4.QtCore modules both wrap the QObject class

Public bug reported: Crashes on startup ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: ffado-mixer-qt4 2.4.1-0.1 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 CurrentDesktop: XFCE

[Bug 1790232] [NEW] xfdesktop crashed with SIGSEGV in malloc_consolidate()

Public bug reported: Wakeup after suspend-to-ram, immediately followed by the crash. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xfdesktop4 4.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-lowlatency 4.17.17 Uname: Linux 4.17.0-9-lowlatency x86_64 ApportVersion:

[Bug 1787414] [NEW] ardour-5.12.0 crashed with SIGSEGV in calf_plugins::lv2_wrapper::cb_instantiate()

Public bug reported: Trying to insert the plugin. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: ardour 1:5.12.0-3 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 CrashCounter: 1

[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

[Bug 1786626] Re: check-new-release-gtk crashed with TypeError in __main__: Gtk.init_check() takes exactly 0 arguments (1 given)

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786626 Title: check-new-release-gtk crashed with TypeError in __main__: Gtk.init_check() takes

[Bug 1784400] [NEW] sudo upgrade-manager -d crashes on update attempt

Public bug reported: Here is the error output: $ sudo update-manager -d (update-manager:16978): dbind-WARNING **: 16:32:59.558: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-DUH5f3BRKD: Connection refused WARNING:root:can not import unity GI Namespace Dbusmenu

[Bug 1783337] [NEW] mididings fails to start

Public bug reported: Starting mididings results in Traceback (most recent call last): File "/usr/bin/mididings", line 18, in import mididings File "/usr/lib/python2.7/dist-packages/mididings/__init__.py", line 13, in from mididings.setup import config, hook File

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

Pretty sure at least I did at several points in the past. Not sure they were active at the time of the report, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768541 Title: package

[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

[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

[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.

[Bug 1765860] [NEW] blueman-browse crashed with blueman.bluez.errors.DBusInProgressError in warp(): Operation already in progress

Public bug reported: Just pressed the Device Search button, nothing else. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: blueman 2.0.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu5

[Bug 1765658] Re: thunar crashed with SIGSEGV

*** This bug is a duplicate of bug 1758577 *** https://bugs.launchpad.net/bugs/1758577 > Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug

[Bug 1765658] [NEW] thunar crashed with SIGSEGV

*** This bug is a duplicate of bug 1758577 *** https://bugs.launchpad.net/bugs/1758577 Public bug reported: Unfortunately I don't quite remember what I did when this happened. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: thunar 1.6.15-0ubuntu1 ProcVersionSignature: Ubuntu

[Bug 1753958] Re: deja-dup-monitor crashed with SIGSEGV

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753958 Title: deja-dup-monitor crashed with SIGSEGV To manage notifications about this bug go to:

[Bug 1753963] Re: Xorg crashed with SIGABRT

** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753963 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to:

[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

[Bug 1753102] [NEW] Typo in default message: "intsalled"

Public bug reported: Calling command_not_found flowblade gives the message The command 'flowblade' can be intsalled by typing: sudo apt install flowblade "intsalled" is a pretty embarrassing typo. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: command-not-found 18.04.0~pre1

[Bug 1752456] [NEW] package libp11-kit-gnome-keyring 3.27.4-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

Public bug reported: I think this occured during a large package update. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libp11-kit-gnome-keyring 3.27.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion:

[Bug 1708027] Re: aeolus crashed with SIGSEGV in memset()

Since a crash is a pretty bad kind of problem, wouldn't that warrant a backport? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708027 Title: aeolus crashed with SIGSEGV in memset() To manage

[Bug 1731037] [NEW] package openjdk-8-jre-headless 8u144-b01-2 failed to install/upgrade: trying to overwrite shared '/etc/java-8-openjdk/security/java.security', which is different from other instanc

Public bug reported: Normal security update, prompted by the system. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: openjdk-8-jre-headless 8u144-b01-2 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1

[Bug 1722824] [NEW] Xorg crashed with SIGABRT

*** This bug is a duplicate of bug 1557346 *** https://bugs.launchpad.net/bugs/1557346 Public bug reported: Happened after an upgrade. First the desktop became unresponsive (Emacs window stopped accepting input even while appearing to have focus according to cursor shape, Alt-Tab did

[Bug 1721485] [NEW] wrapper-2.0 crashed with SIGSEGV

Public bug reported: After waking up from sleep mode, and using sudo service NetworkManager restart (no idea why that has become necessary with xfce4 in recent months), this crash got flagged. Cannot vouch for an actual connection to the NetworkManager, but thought it better to mention it.

[Bug 1708104] Re: scp-dbus-service.py crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has no attribute 'STOCK_CANCEL'

Getting this rather regularly by now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708104 Title: scp-dbus-service.py crashed with AttributeError in __getattr__(): 'gi.repository.Gtk' object has

[Bug 1708027] Re: aeolus crashed with SIGSEGV in memset()

>From the Linux audio users list: From: Fons Adriaensen Subject: Re: [LAU] Trying to start Aeous gives me seg faults Newsgroups: gmane.linux.audio.users To: linux-audio-user-cunTk1MwBs/cejeg2xfrv2d2fqjk+...@public.gmane.org Date: Mon, 18 Sep 2017

[Bug 1708027] Re: aeolus crashed with SIGSEGV in memset()

#6 also would be consistent with me seeing this problem only after converting my system to 64 bits: it is perfectly conceivable that this would increase the stack size requirements. When I started computing, 128kB would have been double the total address space (let alone local variables). Sigh.

[Bug 1715350] Re: package libxvmc1 2:1.0.9-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/X11/XvMCConfig', which is different from other instances of package libxvmc1:amd64

Ok, this looks really strange: dak@lola:/usr/local/tmp/lilypond$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libxvmc1 1 upgraded, 0 newly installed, 0 to

[Bug 1715350] Re: package libxvmc1 2:1.0.9-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/X11/XvMCConfig', which is different from other instances of package libxvmc1:amd64

So I _purged_ the already removed libxvmc1:i386 (no idea how it actually got installed though) and then libxvmc1 (:amd64) updated/installed fine. Very peculiar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1715350] [NEW] package libxvmc1 2:1.0.9-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/X11/XvMCConfig', which is different from other instances of package libxvmc1:amd64

Public bug reported: Upgrade attempt. Basic installation is Ubuntu Studio amd64. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libxvmc1 2:1.0.9-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-lowlatency 4.12.8 Uname: Linux 4.12.0-12-lowlatency x86_64 ApportVersion:

[Bug 1714292] [NEW] ffado-test crashed with SIGSEGV

Public bug reported: When running ffado-test Discover (admittedly after there already were problems with the Firewire connection) I got the following console output: --- FFADO test and diagnostic utility Part of the FFADO project -- www.ffado.org

[Bug 1714250] [NEW] ffado-test-streaming crashed with SIGSEGV in __GI___libc_free()

Public bug reported: Just called ffado-test-streaming on the current setup (one builtin Ricoh Firewire controller without attached hardware, one Expresscard with TI chipset and an Alesis io|14 attached) and it crashed after some test duration, apparently before wanting to exit. ProblemType:

[Bug 1714243] [NEW] caja crashed with SIGSEGV

*** This bug is a duplicate of bug 1701276 *** https://bugs.launchpad.net/bugs/1701276 Public bug reported: No idea. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: caja 1.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency 4.12.5 Uname: Linux 4.12.0-11-lowlatency

[Bug 1714108] [NEW] wrapper-2.0 assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0': corrupted double-linked list: 0x0000001d9680d5f0 ***

Public bug reported: No idea what caused this now. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: libxfce4panel-2.0-4 4.12.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency 4.12.5 Uname: Linux 4.12.0-11-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64

[Bug 1714089] [NEW] ffado-test-streaming crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped()

Public bug reported: No idea what this is about. Ffado seems very unstable recently. C++ API change or something? ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: ffado-tools 2.3.0-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency 4.12.5 Uname: Linux 4.12.0-11-lowlatency x86_64

[Bug 1714058] [NEW] blueman-manager crashed with TypeError in close_rfcomm(): a bytes-like object is required, not 'str'

Public bug reported: Closing a modem port on a bluetooth-connected mobile phone. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: blueman 2.0.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency 4.12.5 Uname: Linux 4.12.0-11-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu1

[Bug 1713432] [NEW] Ristretto crawls to a halt on USB1.1 file systems

Public bug reported: I often hook up my camera with a USB cable, and it's USB 1.1. I can browse fine (including thumbnails), and I can copy files over with useful speed ("full speed"). But whenever I start Ristretto on such a file, I have to eventually kill it because it never comes back in

[Bug 1713216] [NEW] caja crashed with SIGSEGV

*** This bug is a duplicate of bug 1701276 *** https://bugs.launchpad.net/bugs/1701276 Public bug reported: Possibly related with a proceeding upgrade in parallel. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: caja 1.18.3-1 ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency

[Bug 1713139] [NEW] wrapper-2.0 crashed with SIGSEGV

Public bug reported: This happened while browsing a medium in an SD card reader. No idea whether that's related: no actual panel activity at the time. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: libxfce4panel-2.0-4 4.12.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency

[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

[Bug 1712382] [NEW] caja crashed with SIGSEGV

*** This bug is a duplicate of bug 1701276 *** https://bugs.launchpad.net/bugs/1701276 Public bug reported: Happened when deleting a file I think. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: caja 1.18.3-1 ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency 4.12.5 Uname: Linux

[Bug 1711702] [NEW] package lilypond-data 2.18.2-8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Public bug reported: Tried installing. There might have been an earlier (removed) installation. However, apt-purge did not help for getting into installable state. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: lilypond-data 2.18.2-8 ProcVersionSignature: Ubuntu

[Bug 1711307] [NEW] aeolus crashed with SIGSEGV in FT_Load_Glyph()

*** This bug is a duplicate of bug 1708027 *** https://bugs.launchpad.net/bugs/1708027 Public bug reported: Happened when switching registers. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: aeolus 0.9.0-2 ProcVersionSignature: Ubuntu 4.11.0-13.19-lowlatency 4.11.12 Uname: Linux

[Bug 1710849] [NEW] ffmpeg crashed with SIGSEGV in avformat_open_input()

Public bug reported: Startup message stated: ffmpeg -f libdc1394 -video_size 640x480 -framerate 15 -i fw.0 -pix_fmt bgr24 -f v4l2 /dev/video0 ffmpeg version 3.3.3-1ubuntu1 Copyright (c) 2000-2017 the FFmpeg developers built with gcc 6.4.0 (Ubuntu 6.4.0-2ubuntu1) 20170724 configuration:

[Bug 1710844] [NEW] ekiga crashed with SIGSEGV in OpalPluginControl::Call()

Public bug reported: I think that this crash happened when trying to quit Ekiga by using "Quit" in the xfce4 panel icon. Though I don't really think that the manner of quitting Ekiga would be relevant here. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: ekiga 4.0.1-7

[Bug 1710379] [NEW] jack-keyboard crashed with SIGABRT in init_jack()

Public bug reported: Started jack-keyboard with Jackd not running. An abort+coredump seems exaggerated for this rather straightforward error condition: this is to be expected often enough to warrant a proper termination with suitable error message. ProblemType: Crash DistroRelease: Ubuntu 17.10

[Bug 1710374] [NEW] package libsane-hpaio 3.17.6+repack0-2build1 failed to install/upgrade: trying to overwrite shared '/etc/hp/hplip.conf', which is different from other instances of package libsane-

Public bug reported: Just an upgrade. Failed to complete due to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane-hpaio 3.17.6+repack0-2build1 ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8 Uname: Linux 4.11.0-10-lowlatency x86_64 ApportVersion:

  1   2   3   >