Ok, "any file" was wrong. The problem appears to be "any file in the
/tmp hierarchy". That is a common destination for downloading and
unpacking stuff, including by software that displays HTML by reverting
to the system browser.
The error message then is
File not found
Firefox can’t find the
Public bug reported:
The way this configures/installs the snap makes it impossible to open
any file either from the command-line or by specifying a link of the
file:/// kind. That makes firefox unusable for browsing local HTML
documentation.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package:
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
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:
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:
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 Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1753963
Title:
Xorg crashed with SIGABRT
Status in xorg-server package in
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1753958
Title:
deja-dup-monitor crashed with SIGSEGV
Status in deja-dup package in
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
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:
*** 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
Getting this rather regularly by now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1708104
Title:
scp-dbus-service.py crashed with AttributeError in __getattr__():
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 Desktop
Packages, which is subscribed to libxvmc in Ubuntu.
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
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:
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
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:
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
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:
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:
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:
No idea what triggered this. Happened some time after printing and
leaving stuff in the queue.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: system-config-printer-common 1.5.9+20170619-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
Uname:
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:
Just calling
ffado-diag --help
is sufficient for triggering the bug.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: ffado-tools 2.3.0-2
ProcVersionSignature: Ubuntu 4.11.0-10.15-lowlatency 4.11.8
Uname: Linux 4.11.0-10-lowlatency i686
ApportVersion:
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
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jack-audio-connection-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1665743
Title:
jackd crashed with SIGILL in _xend()
Status in
** Also affects: jack
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jack-audio-connection-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1665979
Title:
jack_server_control crashed with
This is an upstream bug. I read in a source repository (mirror?)
https://github.com/jackaudio/example-clients/blob/master/server_control.c#L151-L154
struct option long_options[] = {
{"driver", 1, 0, 'd'},
{"client", 1, 0, 'c'},
};
This is missing
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jack-audio-connection-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1665979
Title:
jack_server_control crashed with SIGSEGV in
I'm pretty sure by now that this issue has been video-driver or
compositor related. After upgrading to Wily and a different NVidea
driver, it seems to have disappeared. Prior to that, I noticed lag for
several other operations, like scolling in browser windows, with the
result being unconsistent
it. Sometimes the cursor blinking causes a refresh, so it's
also more likely with the cursor off-screen.
--
David Kastrup
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1460062
Public bug reported:
I am often using Scrollback in GNOME-Terminal. The current version
forgets to refresh the screen timely afterwards. For one thing, it
means that one is wildly pressing Shift-PageUp Shift-PageDown too often
and it is hard to find things.
For another, when trying to
Public bug reported:
The Metapost binary distributed on the TeXlive2013 CDROM is broken; an
upgrade using tlmgr will fix it.
The brokenness exhibits itself in both i386 as well as amd64 binaries:
one result is that the fonts generated when building LilyPond are
broken, showing (among other
The Debian unstable changelog lists as additional changes over the Saucy
version (among others):
texlive-bin (2013.20130722.31261-1) unstable; urgency=low
* allow for different origin in make-orig-tar
* Imported Upstream version 2013.20130722.31261
- fix for crash of luatex on x32 archs
Public bug reported:
Crash on upgrade
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: unity-webapps-common 2.4.16+13.10.20130814-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
upstream claims works for me, but the respective mails don't indicate
that they actually ran ps2pdf (rather than just gs) on the supplied test
files. Even if they did, it would appear that the core dump is seen due
by Ubuntu specific stack protection options.
That makes it likely that upstream
Here is a much smaller file triggering the core dump. Run ps2pdf on it.
My guess is that it tries to print an error message but the formatting
of the error message is done to insufficient or unallocated memory.
** Attachment added: Minimal file crashing ps2pdf
Downgrading to ghostscript 9.06 (last version from Quantal) along with
dependencies and putting it on hold did the trick for me:
hi ghostscript9.06~dfsg-0ubuntu4 i386
ii ghostscript-x 9.06~dfsg-0ubuntu4 i386
ii libgs9
An independent tester has corroborated that the problem occurs for a
default Raring Ringtail installation with the i386 package. Several
testers have reported that the amd64 package is not affected.
Downgrading to 9.06 solves the problem.
** Changed in: ghostscript (Ubuntu)
Status: New =
Public bug reported:
When running
ps2pdf toc.preview.eps
I get
*** buffer overflow detected ***: /usr/bin/gs terminated
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(__fortify_fail+0x63)[0xb6d20bc3]
/lib/i386-linux-gnu/libc.so.6(+0x10593a)[0xb6d1f93a]
42 matches
Mail list logo
