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

[David Kastrup]

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 because I needed it working, so I could not
easily test with that).

Definitely a showstopper kind of bug; surprised there weren't more
reports to be found.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062526

Title:
  DNS for snaps like Firefox and Chromium fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2062526/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 to refer to my login
data.

There is a report on Stackexchange that sounds like what I experience:
https://askubuntu.com/questions/1510668/network-problems-with-snap-apps

My own system, however, is not Kubuntu but an Ubuntu Studio variation.
Also there have been some very manual recoveries in its history (because
the system was completely broken after some updates, I had to boot a
recovery system, mount the file system of the broken system and do
updates with changed root settings).

As a result, I cannot rule out that not all permissions and other
package details may be the same as on a pristine system: after all, it
would appear that few other people see this problem.  However, I am out
of my depth regarding how to address this, why the problem suddenly
manifested itself about a week ago (the last manual recovery is a few
months back) and how to get back to a working system.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: snapd 2.62+24.04build1
ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
Uname: Linux 6.8.0-25-lowlatency x86_64
ApportVersion: 2.28.1-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Apr 19 11:27:37 2024
InstallationDate: Installed on 2011-10-14 (4571 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: snapd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

** Description changed:

  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 to refer to my login
  data.
  
  There is a report on Stackexchange that sounds like what I experience:
  https://askubuntu.com/questions/1510668/network-problems-with-snap-apps
  
  My own system, however, is not Kubuntu but an Ubuntu Studio variation.
  Also there have been some very manual recoveries in its history (because
  the system was completely broken after some updates, I had to boot a
  recovery system, mount the file system of the broken system and do
  updates with changed root settings).
  
  As a result, I cannot rule out that not all permissions and other
- package details may be other than on a pristine system: after all, it
+ package details may be the same as on a pristine system: after all, it
  would appear that few other people see this problem.  However, I am out
  of my depth regarding how to address this, why the problem suddenly
  manifested itself about a week ago (the last manual recovery is a few
  months back) and how to get back to a working system.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: snapd 2.62+24.04build1
  ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1
  Uname: Linux 6.8.0-25-lowlatency x86_64
  ApportVersion: 2.28.1-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Fri Apr 19 11:27:37 2024
  InstallationDate: Installed on 2011-10-14 (4571 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062526

Title:
  DNS for snaps like Firefox and Chromium fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2062526/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058807] [NEW] Segmentation fault

[David Kastrup]

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 ubuntustudio has no size field


(modem-manager-gui:186352): Gtk-WARNING **: 12:49:10.872: Theme directory 
places/scalable of theme ubuntustudio has no size field

Connection manager: Network Manager >= 0.9.0
Modem manager: Modem Manager >= 0.7.0
Segmentation fault at address: 0x5e3ad4a2869e
Stack trace:
1. /lib/x86_64-linux-gnu/libc.so.6(+0x1a71da) [0x7415623a71da]
2. /lib/x86_64-linux-gnu/libc.so.6(+0x1a71da) [0x7415623a71da]
3. modem-manager-gui(mmgui_notifications_new+0x1d3) [0x5e3f36422db3]
4. modem-manager-gui(+0x4205e) [0x5e3f3644705e]
5. modem-manager-gui(mmgui_svcmanager_start_services_activation+0x12c) 
[0x5e3f3642cb2c]
6. modem-manager-gui(+0x27deb) [0x5e3f3642cdeb]
7. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x14a) 
[0x7415631cd2fa]
8. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x4490c) [0x7415631fc90c]
9. /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x35591) [0x7415631ed591]

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: modem-manager-gui 0.0.20-6
ProcVersionSignature: Ubuntu 6.8.0-7.7.1-lowlatency 6.8.0-rc3
Uname: Linux 6.8.0-7-lowlatency x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Sat Mar 23 12:50:13 2024
InstallationDate: Installed on 2011-10-14 (4544 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: modem-manager-gui
UpgradeStatus: Upgraded to noble on 2023-11-04 (140 days ago)

** Affects: modem-manager-gui (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058807

Title:
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/2058807/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
Uname: Linux 5.15.0-22-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: XFCE
Date: Thu Mar 10 14:01:36 2022
ExecutablePath: /usr/bin/xiccd
InstallationDate: Installed on 2011-10-14 (3807 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xiccd
Signal: 11
SourcePackage: xiccd
StacktraceTop:
 outstring_func (done=115, length=5896079697154171687, string=0x7ffcb01b81c0, 
s=0x63) at ../libio/libioP.h:947
 __vfwprintf_internal (s=0x63, format=0x557b5b34c0f0 
L"\x64616f6c\x20676e69\x666f7270\x20656c69\x27732527\x726f6620\x73696420\x79616c70\x732520",
 ap=0x7ffcb01b8410, mode_flags=1) at ./stdio-common/vfprintf-internal.c:1516
 ()
 ()
 ()
Title: xiccd crashed with SIGSEGV in outstring_func()
UpgradeStatus: Upgraded to jammy on 2022-01-28 (49 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd netdev plugdev 
pulse-access sambashare video
separator:

** Affects: xiccd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash jammy

** 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/1965531

Title:
  xiccd crashed with SIGSEGV in outstring_func()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xiccd/+bug/1965531/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: 2.20.11-0ubuntu79
Architecture: amd64
AssertionMessage: double free or corruption (!prev)
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Mon Mar 14 23:54:42 2022
ExecutablePath: /usr/bin/guvcview
InstallationDate: Installed on 2011-10-14 (3807 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: guvcview -d /dev/video2
Signal: 6
SourcePackage: guvcview
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fb958561b8c 
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
 malloc_printerr (str=str@entry=0x7fb9585647d0 "double free or corruption 
(!prev)") at ./malloc/malloc.c:5664
 _int_free (av=0x7fb94830, p=0x7fb949d4f460, have_lock=) at 
./malloc/malloc.c:4591
 __GI___libc_free (mem=) at ./malloc/malloc.c:3391
 clean_v4l2_frames () at /lib/x86_64-linux-gnu/libgviewv4l2core-2.0.so.2
Title: guvcview assert failure: double free or corruption (!prev)
UpgradeStatus: Upgraded to jammy on 2022-01-28 (49 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd netdev plugdev 
pulse-access sambashare video
separator:

** Affects: guvcview (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash jammy need-amd64-retrace

** 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/1965532

Title:
  guvcview assert failure: double free or corruption (!prev)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guvcview/+bug/1965532/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964402] [NEW] atril crashed with SIGSEGV

[David Kastrup]

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: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Mar  9 20:20:17 2022
ExecutablePath: /usr/bin/atril
InstallationDate: Installed on 2011-10-14 (3799 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/atril file:///home/username/tex/clt/obsstudio.pdf
RebootRequiredPkgs: Error: path contained symlinks.
SegvAnalysis:
 Segfault happened at: 0x7f3a8029c9e7:  mov(%rbx),%rdi
 PC (0x7f3a8029c9e7) ok
 source "(%rbx)" (0x7f3a91d52) not located in a known VMA region (needed 
readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: atril
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libpoppler.so.118
 Gfx8BitFont::Gfx8BitFont(XRef*, char const*, Ref, GooString*, GfxFontType, 
Ref, Dict*) () at /lib/x86_64-linux-gnu/libpoppler.so.118
 GfxFont::makeFont(XRef*, char const*, Ref, Dict*) () at 
/lib/x86_64-linux-gnu/libpoppler.so.118
 () at /lib/x86_64-linux-gnu/libpoppler.so.118
 GfxResources::GfxResources(XRef*, Dict*, GfxResources*) () at 
/lib/x86_64-linux-gnu/libpoppler.so.118
Title: atril crashed with SIGSEGV
UpgradeStatus: Upgraded to jammy on 2022-01-28 (40 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd netdev plugdev 
pulse-access sambashare video
separator:

** Affects: atril (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash jammy need-amd64-retrace

** 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/1964402

Title:
  atril crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/atril/+bug/1964402/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 that this was really really a one-off error nobody else will
see because I will not be able to provide any further information with
something like 1500+ packages now having been upgraded.

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 upgraded:
  libc-bin libc6
2 upgraded, 0 newly installed, 0 to remove and 1884 not upgraded.
6 not fully installed or removed.
Need to get 0 B/4050 kB of archives.
After this operation, 225 kB disk space will be freed.
Do you want to continue? [Y/n] 
Preconfiguring packages ...
(Reading database ... 676266 files and directories currently installed.)
Preparing to unpack .../libc6_2.34-0ubuntu2_amd64.deb ...
D000200: process_archive conffile '/etc/ld.so.conf.d/x86_64-linux-gnu.conf' in 
package libc6:amd64 - conff ?
D000200: pkg_conffiles_mark_old '/etc/ld.so.conf.d/x86_64-linux-gnu.conf' 
namenode '/etc/ld.so.conf.d/x86_64-linux-gnu.conf' flags 5
Checking for services that may need to be restarted...
Checking init scripts...
Checking for services that may need to be restarted...
Checking init scripts...
Stopping some services possibly affected by the upgrade (will be restarted 
later):

Unpacking libc6:amd64 (2.34-0ubuntu2) over (2.33-0ubuntu5) ...
D000200: conffderef in='/etc/ld.so.conf.d/x86_64-linux-gnu.conf' current 
working='/etc/ld.so.conf.d/x86_64-linux-gnu.conf'
D000200: tarobject conffile extracted
dpkg: error processing archive 
/var/cache/apt/archives/libc6_2.34-0ubuntu2_amd64.deb (--unpack):
 unable to open '/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2.dpkg-new': Text 
file busy
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.34-0ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 /usr/bin/locale doesn't seem to be the
principal problem but more a side effect of the broken state after libc-
bin managed to get upgraded and libc6 didn't.

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 `apt --fix-broken install` run complains about this.  I removed the
locale binary temporarily to get

Can't exec "locale": No such file or directory at 
/usr/share/perl5/Debconf/Encoding.pm line 16.
Use of uninitialized value $Debconf::Encoding::charmap in scalar chomp at 
/usr/share/perl5/Debconf/Encoding.pm line 17.

I have no idea what this is being used for but maybe it is in some way
related to unexpected things happening and culminating in the listed
error?

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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.confzz_amd64-biarch-compat.conf  
zz_i386-biarch-compat.conf.dpkg-new
fakeroot-x86_64-linux-gnu.conf  i386-linux-gnu.conf.dpkg-new  
libc.conf.dpkg-new  x86_64-linux-gnu_guile-1.8.conf  zz_i386-biarch-compat.conf 
  zz_x32-biarch-compat.conf

So there is a number of .dpkg-new files in /etc/ld.so.conf.d left over
that might sabotage the update.  Removing them now, rerunning ldconfig
and trying again...

Nope.  The .dpkg-new files remain gone but the upgrade still fails in
the same manner and there is no /etc/ld.so.cache anymore afterwards.

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 condition, it would not appear to depend on
having multiple CPUs even though of course there still is preemptive
scheduling even with a single CPU.

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
system to a single core (it's a 4-core right now) via BIOS settings or
whatever and try again?  Problem of course being that if it works I
cannot get back to the failing state again for further testing.

** Attachment added: "/var/log/apt/ contents"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+attachment/5524375/+files/var-log-apt.tgz

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

Florian Weimer <1943...@bugs.launchpad.net> writes:

> The ldconfig aspect is just a guess on my part. Assuming that
> /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2.dpkg-new was not created by
> renaming of /lib/x86_64-linux-gnu/ld-linux-x86-64.so, it is unclear to
> me how a process would end up using it—it has to be listed in
> /etc/ld.so.cache for that to happen.

Are you sure about that?  My botched upgrade left me without
/etc/ld.so.cache in place and the system appeared mostly functional: the
main problem I saw was a refusal to execute a few self-compiled binaries
(relying on shared libraries in non-standard places) and probably a
number of GUI-related stuff (fonts were wrong size and so on).  But
overall it was a "slightly defective but overall workable" situation
until I figure out I'd better run `ldconfig`.

So there must be a healthy dose of standard 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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 before calling 'apt'), I am not sure how likely it is that
'ldconfig' has been run too early.

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 following additional packages will be installed:
  libc6 linux-headers-lowlatency linux-lowlatency
The following packages will be upgraded:
  libc6 linux-headers-lowlatency linux-lowlatency
3 upgraded, 0 newly installed, 0 to remove and 1855 not upgraded.
8 not fully installed or removed.
Need to get 0 B/3032 kB of archives.
After this operation, 391 kB disk space will be freed.
Do you want to continue? [Y/n] 
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found 
(required by locale)
Preconfiguring packages ...
(Reading database ... 683369 files and directories currently installed.)
Preparing to unpack .../libc6_2.34-0ubuntu2_amd64.deb ...
locale: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found 
(required by locale)
Checking for services that may need to be restarted...
Checking init scripts...
Checking for services that may need to be restarted...
Checking init scripts...
Stopping some services possibly affected by the upgrade (will be restarted 
later):

Unpacking libc6:amd64 (2.34-0ubuntu2) over (2.33-0ubuntu5) ...
dpkg: error processing archive 
/var/cache/apt/archives/libc6_2.34-0ubuntu2_amd64.deb (--unpack):
 unable to open '/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2.dpkg-new': Text 
file busy
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.34-0ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

There is no actual file '/lib/x86_64-linux-gnu/ld-
linux-x86-64.so.2.dpkg-new' left after the aborted install.  Renaming
the file '/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' manually turns out
to be a rather bad idea.  Not found a recipe to get past that so far.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: libc6 2.33-0ubuntu5 [modified: usr/share/doc/libc6/NEWS.gz 
usr/share/doc/libc6/changelog.Debian.gz usr/share/lintian/overrides/libc6]
ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
Uname: Linux 5.13.0-14-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Thu Sep  9 12:51:28 2021
InstallationDate: Installed on 2011-10-14 (3617 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
SourcePackage: glibc
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glibc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

-- 
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"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: 6: cannot create /tmp/nohup: Permission denied

Basically, I need to find some other place for my logs I guess.

I get in dmesg now
[146468.234320] audit: type=1400 audit(1585218755.403:2590): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/gpsd" 
pid=504973 comm="apparmor_parser"
[146504.975241] audit: type=1400 audit(1585218792.144:2591): apparmor="DENIED" 
operation="mknod" profile="/usr/sbin/gpsd" name="/tmp/bubu" pid=506327 
comm="device-hook" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[146504.975735] audit: type=1400 audit(1585218792.145:2592): apparmor="DENIED" 
operation="mknod" profile="/usr/sbin/gpsd" name="/tmp/nohup" pid=506328 
comm="device-hook" requested_mask="c" denied_mask="c" fsuid=0 ouid=0
[146504.978485] audit: type=1400 audit(1585218792.148:2593): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[146504.978493] audit: type=1400 audit(1585218792.148:2594): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[146504.978499] audit: type=1400 audit(1585218792.148:2595): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[146504.978505] audit: type=1400 audit(1585218792.148:2596): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[146504.978511] audit: type=1400 audit(1585218792.148:2597): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[146504.978517] audit: type=1400 audit(1585218792.148:2598): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[146504.978523] audit: type=1400 audit(1585218792.148:2599): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[146504.978528] audit: type=1400 audit(1585218792.148:2600): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=506325 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"

But I don't see any obvious adverse effect from the refused ptrace
operations.

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1868363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1868363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 system shell is sandwiched in between in some other manner.  I seem
to remember that for potential interpreter scripts there once was
something called "sanitized_helper" that worked in rules.

Sorry not to be able to be more specific: this whole underdocumented
mess and framework is just beyond me.

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1868363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655358] audit: type=1400 audit(1585146074.313:1471): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655363] audit: type=1400 audit(1585146074.313:1472): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655366] audit: type=1400 audit(1585146074.313:1473): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655369] audit: type=1400 audit(1585146074.313:1474): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655373] audit: type=1400 audit(1585146074.313:1475): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655376] audit: type=1400 audit(1585146074.313:1476): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655388] audit: type=1400 audit(1585146074.313:1477): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[113847.655391] audit: type=1400 audit(1585146074.313:1478): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=363199 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1868363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 audit(1585144947.602:72): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973976] audit: type=1400 audit(1585144947.602:73): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973978] audit: type=1400 audit(1585144947.602:74): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973980] audit: type=1400 audit(1585144947.602:75): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973983] audit: type=1400 audit(1585144947.602:76): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973985] audit: type=1400 audit(1585144947.602:77): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973987] audit: type=1400 audit(1585144947.602:78): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973989] audit: type=1400 audit(1585144947.602:79): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"
[112720.973991] audit: type=1400 audit(1585144947.602:80): apparmor="DENIED" 
operation="ptrace" profile="/usr/sbin/gpsd" pid=353555 comm="gpsd" 
requested_mask="read" denied_mask="read" peer="unconfined"

Note that in my case, /etc/gpsd/device-hook is a shell script, starting
with

#!/bin/sh

and it would appear that the exec permission gpsd needs is tied to the
shell rather than /etc/gpsd/device-hook?

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1868363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868884] [NEW] thunar crashed with SIGSEGV

[David Kastrup]

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 5.4.0-18.22-lowlatency 5.4.24
Uname: Linux 5.4.0-18-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Tue Mar 24 22:53:05 2020
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (3084 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f 
--daemon
SegvAnalysis:
 Segfault happened at: 0x55caf3921f5c:  mov(%r14),%r12
 PC (0x55caf3921f5c) ok
 source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_hash_table_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to focal on 2020-03-09 (15 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash focal need-amd64-retrace

** 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/1868884

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1868884/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 deactivation it does the same 
passing DEACTIVATE for the second argument.

and when such an executable is present, the debug info/log of gpsd
indicates that /etc/gpsd/device-hook is being called and exits with
state 0.  However, this is a lie.

I assume that there is a suitable line missing in

/etc/apparmor.d/usr.sbin.gpsd

but my apparmor-foo is not sufficient to figure out what incantation is
required to allow gpsd executing this hook.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gpsd 3.20-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
Uname: Linux 5.4.0-18-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Mar 21 09:00:23 2020
InstallationDate: Installed on 2011-10-14 (3080 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
SourcePackage: gpsd
UpgradeStatus: Upgraded to focal on 2020-03-09 (11 days ago)

** Affects: gpsd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-bug focal

** Tags added: apparmor

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/gpsd/+bug/1868363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868119] [NEW] thunar crashed with SIGSEGV

[David Kastrup]

*** 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: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
Uname: Linux 5.4.0-18-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Mar 19 16:19:10 2020
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (3079 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f 
--daemon
SegvAnalysis:
 Segfault happened at: 0x562a39eb1f5c:  mov(%r14),%r12
 PC (0x562a39eb1f5c) ok
 source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_hash_table_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to focal on 2020-03-09 (9 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash focal

** 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/1868119

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1868119/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 SIGSEGV in g_mutex_lock()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1843337/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 -> Geisterbewegung
Herabsetztung -> Herabsetzung

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: wogerman 1:2-35
ProcVersionSignature: Ubuntu 5.3.0-13.14-lowlatency 5.3.0
Uname: Linux 5.3.0-13-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Oct  6 18:25:37 2019
InstallationDate: Installed on 2011-10-14 (2914 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
PackageArchitecture: all
SourcePackage: hkgerman
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: hkgerman (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846965

Title:
  Bad German words in /usr/share/dict/ogerman: Bauernbefeiung,
  Anschlußleitung, Devalvierung, Geisterbwegung, Herabsetztung

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hkgerman/+bug/1846965/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Sep 26 20:31:01 2019
ExecutablePath: /usr/bin/xfdesktop
InstallationDate: Installed on 2011-10-14 (2904 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xfdesktop --display :0.0 --sm-client-id 
2f1767d95-cd68-4ef9-8cc1-b6f11f43976c
SegvAnalysis:
 Segfault happened at: 0x7fc8d243b0b0 :  testb  
$0x4,0x16(%rax)
 PC (0x7fc8d243b0b0) ok
 source "$0x4" ok
 destination "0x16(%rax)" (0x1020a) not located in a known VMA region 
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: xfdesktop4
StacktraceTop:
 g_type_check_instance_is_a () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ()
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xfdesktop crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: xfdesktop4 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash eoan

** 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/1845550

Title:
  xfdesktop crashed with SIGSEGV in g_type_check_instance_is_a()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845550/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Sep  9 22:15:58 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2887 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f 
--daemon
SegvAnalysis:
 Segfault happened at: 0x7fe88c8b2bf9 : lock xadd %eax,(%rdi)
 PC (0x7fe88c8b2bf9) ok
 source "%eax" ok
 destination "(%rdi)" (0x0030) not located in a known VMA region (needed 
writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: thunar crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash eoan

** 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/1843337

Title:
  thunar crashed with SIGSEGV in g_mutex_lock()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1843337/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1834014] [NEW] thunar crashed with SIGSEGV

[David Kastrup]

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
still accessing it, one closes the application, then right-clicks on the
media in the file tree display to check whether the current state is
mounted or unmounted (the menu should then offer the opposite).

This crash here, however, just happened while using an image editor from
within Thunar.  Exiting the editor likely left another saved file on the
memory card.  Thunar crashed just spontaneously at some time while
editing was in progress or right afterwards.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: thunar 1.8.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-17.18-lowlatency 5.0.8
Uname: Linux 5.0.0-17-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Mon Jun 24 13:36:58 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2809 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f 
--daemon
SegvAnalysis:
 Segfault happened at: 0x55d2b24d7677:  mov0x0(%r13),%rbp
 PC (0x55d2b24d7677) ok
 source "0x0(%r13)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_hash_table_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to eoan on 2019-05-12 (43 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash eoan

** 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/1834014

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1834014/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 5.0.0-16-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Sun Jun 16 15:34:50 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2802 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/Thunar --daemon
SegvAnalysis:
 Segfault happened at: 0x7f02eb85baf5 : lock xadd %eax,(%rdi)
 PC (0x7f02eb85baf5) ok
 source "%eax" ok
 destination "(%rdi)" (0x0030) not located in a known VMA region (needed 
writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: thunar crashed with SIGSEGV in g_mutex_lock()
UpgradeStatus: Upgraded to eoan on 2019-05-12 (35 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash eoan need-amd64-retrace

** 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/1832992

Title:
  thunar crashed with SIGSEGV in g_mutex_lock()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1832992/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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:
  modem-manager-gui assert failure: munmap_chunk(): invalid pointer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1820130/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1830621] [NEW] thunar crashed with SIGSEGV

[David Kastrup]

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).
Then the notification window disappeared on its own (which would be
close to what I expected) and Thunar crashed.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: thunar 1.8.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6
Uname: Linux 5.0.0-15-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon May 27 16:04:44 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2782 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/Thunar --daemon
SegvAnalysis:
 Segfault happened at: 0x559720bd8220:  mov0x28(%rdi),%rax
 PC (0x559720bd8220) ok
 source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 ()
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to eoan on 2019-05-12 (15 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash eoan need-amd64-retrace

** 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/1830621

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1830621/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829921] [NEW] thunar crashed with SIGSEGV

[David Kastrup]

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
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x054c Sony Corp.
  idProduct  0x0281 
  bcdDevice4.52
  iManufacturer   1 Sony
  iProduct2 UMH-U09
  iSerial 3 F020B320
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   0x0027
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass  6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   1
:

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: thunar 1.8.6-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
Uname: Linux 5.0.0-13-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue May 21 21:36:03 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2776 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f 
--daemon
SegvAnalysis:
 Segfault happened at: 0x5610d9563220:  mov0x28(%rdi),%rax
 PC (0x5610d9563220) ok
 source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 ()
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to eoan on 2019-05-12 (9 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash eoan need-amd64-retrace

** 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/1829921

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1829921/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816245] Re: xfdesktop crashed with SIGSEGV

[David Kastrup]

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 it is marked as containing private information.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816245

Title:
  xfdesktop crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1816245/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821589] [NEW] thunar crashed with SIGSEGV

[David Kastrup]

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 5.0.0-7-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 25 14:10:07 2019
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2718 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f 
--daemon
SegvAnalysis:
 Segfault happened at: 0x56109cd91166:  mov(%rdx),%rax
 PC (0x56109cd91166) ok
 source "(%rdx)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_tree_row_reference_free () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash disco need-amd64-retrace

** 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/1821589

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1821589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: 2.20.10-0ubuntu23
Architecture: amd64
AssertionMessage: munmap_chunk(): invalid pointer
CrashCounter: 1
CurrentDesktop: XFCE
Date: Thu Mar 14 22:44:38 2019
ExecutablePath: /usr/bin/modem-manager-gui
InstallationDate: Installed on 2011-10-14 (2708 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: modem-manager-gui
Signal: 6
SourcePackage: modem-manager-gui
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f8a1b39b952 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f8a1b39d5a0 "munmap_chunk(): invalid 
pointer") at malloc.c:5352
 munmap_chunk (p=) at malloc.c:2840
 () at /usr/lib/x86_64-linux-gnu/modem-manager-gui/modules/libmodmm_mm07.so
 mmgui_module_devices_information () at 
/usr/lib/x86_64-linux-gnu/modem-manager-gui/modules/libmodmm_mm07.so
Title: modem-manager-gui assert failure: munmap_chunk(): invalid pointer
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: modem-manager-gui (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash disco

** 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/1820130

Title:
  modem-manager-gui assert failure: munmap_chunk(): invalid pointer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1820130/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: Linux 4.19.0-13-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Feb 22 15:16:12 2019
ExecutablePath: /usr/bin/digikam
InstallationDate: Installed on 2011-10-14 (2688 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: digikam -qwindowtitle digiKam
SegvAnalysis:
 Segfault happened at: 0x7f730e68ee17 <_ZN6QMutex4lockEv+7>:lock cmpxchg 
%rdx,(%rdi)
 PC (0x7f730e68ee17) ok
 source "%rdx" ok
 destination "(%rdi)" (0x0098) not located in a known VMA region (needed 
writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: digikam
StacktraceTop:
 QMutex::lock() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 () at /usr/lib/digikam/libdigikamcore.so.5.9.0
 Digikam::LoadSaveThread::run() () at /usr/lib/digikam/libdigikamcore.so.5.9.0
 Digikam::DynamicThread::DynamicThreadPriv::run() () at 
/usr/lib/digikam/libdigikamcore.so.5.9.0
 () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
Title: digikam crashed with SIGSEGV in QMutex::lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
separator:

** Affects: digikam (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash disco need-amd64-retrace

** 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/1817330

Title:
  digikam crashed with SIGSEGV in QMutex::lock()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1817330/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816245] [NEW] xfdesktop crashed with SIGSEGV

[David Kastrup]

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
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Feb 16 15:34:36 2019
ExecutablePath: /usr/bin/xfdesktop
InstallationDate: Installed on 2011-10-14 (2682 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xfdesktop --display :0.0 --sm-client-id 
2f1767d95-cd68-4ef9-8cc1-b6f11f43976c
Signal: 11
SourcePackage: xfdesktop4
Stacktrace:
 #0  0x7f0fcae59505 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #1  0x7f0fcae39a1e in g_object_get () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #2  0x7f0fbc007840 in  ()
 #3  0x7f0fcad4f780 in g_source_get_context () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #4  0x in  ()
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_get () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ()
 g_source_get_context () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
Title: xfdesktop crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfdesktop4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash apport-failed-retrace disco

** 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/1816245

Title:
  xfdesktop crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1816245/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
CurrentDesktop: XFCE
Date: Fri Feb 15 01:40:34 2019
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2011-10-14 (2680 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libwhiskermenu.so 1 10485771 
whiskermenu Whisker\ Menu Show\ a\ menu\ to\ easily\ access\ installed\ 
applications
Signal: 6
SourcePackage: xfce4-panel
StacktraceTop:
 g_slice_alloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_value_reset () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_freopen () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: wrapper-2.0 crashed with SIGABRT in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfce4-panel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash disco need-amd64-retrace

** 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/1815986

Title:
  wrapper-2.0 crashed with SIGABRT in g_slice_alloc()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1815986/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 make this work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765860

Title:
  blueman-browse crashed with blueman.bluez.errors.DBusInProgressError
  in warp(): Operation already in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1765860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

*** 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 4.18.0-11-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 31 01:42:40 2019
ExecutablePath: /usr/bin/xfce4-appfinder
ExecutableTimestamp: 1545999336
InstallationDate: Installed on 2011-10-14 (2665 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xfrun4
ProcCwd: /home/dak
SegvAnalysis:
 Segfault happened at: 0x7fa374a7d76a :  mov
(%rbx),%rdx
 PC (0x7fa374a7d76a) ok
 source "(%rbx)" (0x002c) not located in a known VMA region (needed 
readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-appfinder
StacktraceTop:
 g_slice_alloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_with_properties () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xfce4-appfinder crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfce4-appfinder (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash disco

** 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/1814129

Title:
  xfce4-appfinder crashed with SIGSEGV in g_slice_alloc()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-appfinder/+bug/1814129/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
CurrentDesktop: XFCE
Date: Thu Jan 31 01:42:40 2019
ExecutablePath: /usr/bin/xfce4-appfinder
InstallationDate: Installed on 2011-10-14 (2665 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xfrun4
SegvAnalysis:
 Segfault happened at: 0x7fa374a7d76a :  mov
(%rbx),%rdx
 PC (0x7fa374a7d76a) ok
 source "(%rbx)" (0x002c) not located in a known VMA region (needed 
readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-appfinder
StacktraceTop:
 g_slice_alloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_with_properties () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: xfce4-appfinder crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfce4-appfinder (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash disco need-amd64-retrace

** 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/1814112

Title:
  xfce4-appfinder crashed with SIGSEGV in g_slice_alloc()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-appfinder/+bug/1814112/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Jan 12 01:32:48 2019
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2011-10-14 (2646 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libwhiskermenu.so 1 10485771 
whiskermenu Whisker\ Menu Show\ a\ menu\ to\ easily\ access\ installed\ 
applications
SegvAnalysis:
 Segfault happened at: 0x7fb0b568976a :  mov
(%rbx),%rdx
 PC (0x7fb0b568976a) ok
 source "(%rbx)" (0x002b) not located in a known VMA region (needed 
readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
 g_slice_alloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_list_append () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_queue_push_tail () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: wrapper-2.0 crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfce4-panel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash disco need-amd64-retrace

** 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/1811479

Title:
  wrapper-2.0 crashed with SIGSEGV in g_slice_alloc()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1811479/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713432

Title:
  Ristretto crawls to a halt on USB1.1 file systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1713432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 that list.  However, if there were any _on-screen_
unrendered images, those were fed into the rendering queue in
preference.  This strategy resulted in stable working screens fast even
when it took a minute for a whole document to have its images rendered
in background and leafing back and forward uncovered unfinished work
momemntarily during that time.

We are talking about rendering with Ghostscript here, on 200MHz Pentium
processors.

So if a strategy like that could be made to work smoothly for
Emacs+Ghostscript, a quite slower combination on a quite slower
processor, it should work well enough for something like Ristretto.
Maybe there are even frameworks/libraries catering to most of that task.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713432

Title:
  Ristretto crawls to a halt on USB1.1 file systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1713432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 image viewer waiting for its completion.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713432

Title:
  Ristretto crawls to a halt on USB1.1 file systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1713432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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 17:04:25 2018
ErrorMessage: installed elpa-magit package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2011-10-14 (2562 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, 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.5ubuntu5
 apt  1.7.0
SourcePackage: magit
Title: package elpa-magit 2.13.0-3 failed to install/upgrade: installed 
elpa-magit package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to cosmic on 2018-07-30 (80 days ago)

** Affects: magit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798838

Title:
  package elpa-magit 2.13.0-3 failed to install/upgrade: installed elpa-
  magit package post-installation script subprocess returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/magit/+bug/1798838/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AssertionMessage: malloc_consolidate(): invalid chunk size
Date: Thu Oct 11 21:43:42 2018
ExecutablePath: /usr/lib/gvfs/gvfsd-gphoto2
InstallationDate: Installed on 2011-10-14 (2554 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/gvfs/gvfsd-gphoto2 --spawner :1.12 
/org/gtk/gvfs/exec_spaw/9
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f373b3b4c00 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
 malloc_printerr (str=str@entry=0x7f373b3b6490 "malloc_consolidate(): invalid 
chunk size") at malloc.c:5336
 malloc_consolidate (av=av@entry=0x7f373b3ebc40 ) at malloc.c:4427
 _int_malloc (av=av@entry=0x7f373b3ebc40 , bytes=bytes@entry=2048) 
at malloc.c:3687
 __libc_calloc (n=, elem_size=) at malloc.c:3420
Title: gvfsd-gphoto2 assert failure: malloc_consolidate(): invalid chunk size
UpgradeStatus: Upgraded to cosmic on 2018-07-30 (73 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: gvfs (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash cosmic

** 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/1797454

Title:
  gvfsd-gphoto2 assert failure: malloc_consolidate(): invalid chunk size

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1797454/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 autosuspend:
#   0=do not exclude, 1=exclude.
USB_BLACKLIST_BTUSB=1

Which seems to do the trick.  This means that for me the problem is
fixed.  However, the tlp package is specific to Thinkpads and the
prevalence of at least the "last event is not cmd complete" line on the
net would suggest that other systems can be similarly afflicted.  The
crash triggered here is too obscure to let the average user make the
connection to USB autosuspend.  So there really should be some more
helpful error message for this form of interaction resulting from USB
misconfiguration.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765860

Title:
  blueman-browse crashed with blueman.bluez.errors.DBusInProgressError
  in warp(): Operation already in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1765860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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.

Check that you are logged in with the correct account, or that you
entered the address correctly, or search for it:

This precludes me from adding anything useful to this bug.  Merging a
bug to a private bug seems like an excellent way to put a stop to future
bug reports but it does not help getting a reasonable assessment of a
bug's impact.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765860

Title:
  blueman-browse crashed with blueman.bluez.errors.DBusInProgressError
  in warp(): Operation already in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1765860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: Ubuntu 4.18.0-7.8-lowlatency 4.18.5
Uname: Linux 4.18.0-7-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Sep 16 19:04:18 2018
ExecutablePath: /usr/bin/simple-scan
InstallationDate: Installed on 2011-10-14 (2529 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
MachineType: LENOVO 4238A15
ProcCmdline: simple-scan
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-lowlatency 
root=UUID=94cc5598-598e-4720-bd5a-8f6faca1388e ro quiet splash threadirqs 
resume=UUID=1fa23628-ebfe-4749-a5a9-15cb151a682b
SegvAnalysis:
 Segfault happened at: 0x7f121a443d1a:  mov0x10(%rax),%edx
 PC (0x7f121a443d1a) ok
 source "0x10(%rax)" (0x0010) 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: simple-scan
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/sane/libsane-avision.so.1
 sane_avision_get_devices () at 
/usr/lib/x86_64-linux-gnu/sane/libsane-avision.so.1
 sane_dll_get_devices () at /usr/lib/x86_64-linux-gnu/libsane.so.1
 ()
 ()
Title: simple-scan crashed with SIGSEGV
UpgradeStatus: Upgraded to cosmic on 2018-07-30 (48 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare
dmi.bios.date: 06/04/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET82WW (1.52 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4238A15
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr83ET82WW(1.52):bd06/04/2018:svnLENOVO:pn4238A15:pvrThinkPadT420:rvnLENOVO:rn4238A15:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T420
dmi.product.name: 4238A15
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash cosmic need-amd64-retrace

** 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/1792809

Title:
  simple-scan crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1792809/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 with
  blueman.bluez.errors.DBusInProgressError in warp(): Operation already
  in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1760092/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

** 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:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1791134/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
Bugs, which is subscribed to 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1791132/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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
Date: Tue Sep  4 21:02:40 2018
ExecutablePath: /usr/bin/ffado-mixer
InstallationDate: Installed on 2011-10-14 (2517 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/ffado-mixer
Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1
PythonArgs: ['/usr/bin/ffado-mixer']
PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
SourcePackage: libffado
Title: 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
UpgradeStatus: Upgraded to cosmic on 2018-07-30 (36 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: libffado (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash cosmic

** 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/1790707

Title:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1790707/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: 2.20.10-0ubuntu9
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Sep  1 01:07:06 2018
ExecutablePath: /usr/bin/xfdesktop
InstallationDate: Installed on 2011-10-14 (2513 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xfdesktop --display :0.0 --sm-client-id 
2f1767d95-cd68-4ef9-8cc1-b6f11f43976c
SegvAnalysis:
 Segfault happened at: 0x7f39db09d9a5 : cmp
%rax,0x10(%r13)
 PC (0x7f39db09d9a5) ok
 source "%rax" ok
 destination "0x10(%r13)" (0x7f390011) not located in a known VMA region 
(needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: xfdesktop4
StacktraceTop:
 malloc_consolidate (av=av@entry=0x7f39db3f8c40 ) at malloc.c:4456
 _int_malloc (av=av@entry=0x7f39db3f8c40 , bytes=bytes@entry=3340) 
at malloc.c:3703
 __GI___libc_malloc (bytes=3340) at malloc.c:3065
 () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
 () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
Title: xfdesktop crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to cosmic on 2018-07-30 (32 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfdesktop4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash cosmic need-amd64-retrace

** 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/1790232

Title:
  xfdesktop crashed with SIGSEGV in malloc_consolidate()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1790232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
CurrentDesktop: XFCE
Date: Thu Aug 16 15:54:41 2018
ExecutablePath: /usr/lib/ardour5/ardour-5.12.0
InstallationDate: Installed on 2011-10-14 (2498 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/ardour5/ardour-5.12.0
Signal: 11
SourcePackage: ardour
StacktraceTop:
 
calf_plugins::lv2_wrapper::cb_instantiate(_LV2_Descriptor
 const*, double, char const*, _LV2_Feature const* const*) () at 
/usr/lib/lv2/calf.lv2/calf.so
 lilv_plugin_instantiate () at /usr/lib/x86_64-linux-gnu/liblilv-0.so.0
 ARDOUR::LV2Plugin::init(void const*, long) () at 
/usr/lib/ardour5/libardour.so.3
 ARDOUR::LV2Plugin::LV2Plugin(ARDOUR::AudioEngine&, ARDOUR::Session&, void 
const*, long) () at /usr/lib/ardour5/libardour.so.3
 ARDOUR::LV2PluginInfo::load(ARDOUR::Session&) () at 
/usr/lib/ardour5/libardour.so.3
Title: ardour-5.12.0 crashed with SIGSEGV in 
calf_plugins::lv2_wrapper::cb_instantiate()
UpgradeStatus: Upgraded to cosmic on 2018-07-30 (16 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: ardour (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash cosmic 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787414

Title:
  ardour-5.12.0 crashed with SIGSEGV in
  calf_plugins::lv2_wrapper::cb_instantiate()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ardour/+bug/1787414/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1786635] [NEW] (appstreamcli:8218): GLib-CRITICAL error on exit of apt-get update

[David Kastrup]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786635

Title:
  (appstreamcli:8218): GLib-CRITICAL error on exit of apt-get update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1786635/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

** 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 exactly 0 arguments (1 given)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1786626/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 not available
Checking for a new Ubuntu release

(python3:17891): dbind-WARNING **: 16:33:28.026: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-DUH5f3BRKD: Connection 
refused
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23: 
PyGIWarning: Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '4.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import Gtk, Gdk
Traceback (most recent call last):
  File "/usr/bin/do-release-upgrade", line 168, in 
fetcher = get_fetcher(options.frontend, m.new_dist, options.data_dir)
  File "/usr/bin/do-release-upgrade", line 33, in get_fetcher
_("Downloading the release upgrade tool"))
  File "/usr/lib/python3/dist-packages/DistUpgrade/GtkProgress.py", line 34, in 
__init__
self.widgets = SimpleGtkbuilderApp(uifile, "ubuntu-release-upgrader")
  File "/usr/lib/python3/dist-packages/DistUpgrade/SimpleGtk3builderApp.py", 
line 33, in __init__
self.builder.add_from_file(path)
GLib.Error: gtk-builder-error-quark: 
/usr/share/ubuntu-release-upgrader/gtkbuilder/AcquireProgress.ui:6:36 Invalid 
property: GtkWindow.border_width (11)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.21
ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18
Uname: Linux 4.15.0-29-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashDB: ubuntu
Date: Mon Jul 30 16:34:45 2018
InstallationDate: Installed on 2011-10-14 (2481 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptHistorylog:
 Start-Date: 2018-07-12  12:38:22
 Requested-By: dak (1000)
 Remove: navit-gui-internal:amd64 (0.5.0+dfsg.1-2build1)
 End-Date: 2018-07-12  12:38:23
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2018-04-05T21:30:42.599279

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784400

Title:
  sudo upgrade-manager -d crashes on update attempt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1784400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783337] [NEW] mididings fails to start

[David Kastrup]

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 "/usr/lib/python2.7/dist-packages/mididings/setup.py", line 13, in 

import _mididings
ImportError: dynamic module does not define init function (init_mididings)

This problem is of somewhat recent nature while the package itself is
comparatively old.  I suspect that a Python 2.7 update might have
resulted in more stringent requirements for modules.  Reinstalling
either mididings or python-mididings with apt-get install --reinstall
did not help.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python-mididings 0~20120419~ds0-6
ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18
Uname: Linux 4.15.0-29-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jul 24 15:21:56 2018
InstallationDate: Installed on 2011-10-14 (2474 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
SourcePackage: mididings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mididings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783337

Title:
  mididings fails to start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mididings/+bug/1783337/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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 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-gnome-keyring
  which has multiple installed instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766310] Re: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

[David Kastrup]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766310

Title:
  apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1766310/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766310] Re: apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

[David Kastrup]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766310

Title:
  apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1766310/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766310] [NEW] apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

[David Kastrup]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766310

Title:
  apt-get install memtest86+ fails to create /etc/grub.d/20_memtest86+

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1766310/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Apr 21 00:17:31 2018
ExecutablePath: /usr/bin/blueman-browse
InstallationDate: Installed on 2011-10-14 (2380 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
InterpreterPath: /usr/bin/python3.6
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-browse
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonArgs: ['/usr/bin/blueman-browse']
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
SourcePackage: blueman
Title: blueman-browse crashed with blueman.bluez.errors.DBusInProgressError in 
warp(): Operation already in progress
UpgradeStatus: Upgraded to bionic on 2018-01-23 (87 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: blueman (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash bionic

** 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/1765860

Title:
  blueman-browse crashed with blueman.bluez.errors.DBusInProgressError
  in warp(): Operation already in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1765860/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765658] Re: thunar crashed with SIGSEGV

[David Kastrup]

*** 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 should
occur in the other report.

is a bad joke when the other bug is marked "private" and I don't have
permission to look at it.  It's not the first time this has happened to
me: maybe check the blurb you send out for this case.

Also "Remember, this bug report is a duplicate of a private bug.
Comment here only if you think the duplicate status is wrong." on this web page 
is a bad joke since I cannot judge whether the duplicate status is wrong 
without being allowed to look at the report supposed to be duplicated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765658

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1765658/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765658] [NEW] thunar crashed with SIGSEGV

[David Kastrup]

*** 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 4.15.0-15.16-lowlatency 4.15.15
Uname: Linux 4.15.0-15-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 20 07:48:38 2018
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2011-10-14 (2379 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: Thunar --sm-client-id 2aa52746e-14dd-4b9b-9ec7-f65c0e3b707f 
--daemon
SegvAnalysis:
 Segfault happened at: 0x5560d6fce676:  mov0x18(%rdi),%rax
 PC (0x5560d6fce676) ok
 source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ()
 ()
 ()
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2018-01-23 (87 days ago)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash bionic

** 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/1765658

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1765658/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

** 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:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1753958/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753963] Re: Xorg crashed with SIGABRT

[David Kastrup]

** 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:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1753963/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753433] [NEW] jackd crashed with SIGABRT

[David Kastrup]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753433

Title:
  jackd crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1753433/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
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
CurrentDesktop: XFCE
Date: Sat Mar  3 15:13:40 2018
InstallationDate: Installed on 2011-10-14 (2332 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
PackageArchitecture: all
SourcePackage: command-not-found
UpgradeStatus: Upgraded to bionic on 2018-01-23 (39 days ago)

** Affects: command-not-found (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753102

Title:
  Typo in default message: "intsalled"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1753102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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: 2.20.8-0ubuntu10
Architecture: amd64
Date: Wed Feb 28 23:40:38 2018
Dependencies:
 gcc-8-base 8-20180218-1ubuntu1
 libc6 2.26-0ubuntu2.1
 libgcc1 1:8-20180218-1ubuntu1
DuplicateSignature:
 package:libp11-kit-gnome-keyring:3.27.4-1ubuntu1
 Unpacking glib-networking-common (2.55.90-1) over (2.54.1-2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Ko9Wpj/040-libp11-kit-gnome-keyring_3.27.4-2ubuntu1_all.deb
 (--unpack):
  libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
ErrorMessage: libp11-kit-gnome-keyring:all 3.27.4-2ubuntu1 (Multi-Arch: no) is 
not co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
InstallationDate: Installed on 2011-10-14 (2329 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu2
SourcePackage: gnome-keyring
Title: 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-gnome-keyring which has multiple 
installed instances
UpgradeStatus: Upgraded to bionic on 2018-01-23 (37 days ago)

** Affects: gnome-keyring (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752456

Title:
  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-gnome-keyring which
  has multiple installed instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1752456/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aeolus/+bug/1708027/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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
AptOrdering:
 libssl1.0.0:i386: Install
 libssl1.0.0:amd64: Install
 openssl:amd64: Install
 openjdk-8-jre-headless:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Nov  8 20:58:57 2017
DuplicateSignature:
 package:openjdk-8-jre-headless:8u144-b01-2
 Unpacking openjdk-8-jre-headless:amd64 (8u151-b12-0ubuntu0.17.10.2) over 
(8u144-b01-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/openjdk-8-jre-headless_8u151-b12-0ubuntu0.17.10.2_amd64.deb
 (--unpack):
  trying to overwrite shared '/etc/java-8-openjdk/security/java.security', 
which is different from other instances of package openjdk-8-jre-headless:amd64
ErrorMessage: trying to overwrite shared 
'/etc/java-8-openjdk/security/java.security', which is different from other 
instances of package openjdk-8-jre-headless:amd64
InstallationDate: Installed on 2011-10-14 (2217 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: openjdk-8
Title: 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 instances of package openjdk-8-jre-headless:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openjdk-8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731037

Title:
  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 instances of package openjdk-8-jre-headless:amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1731037/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1722824] [NEW] Xorg crashed with SIGABRT

[David Kastrup]

*** 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 nothing, nor did clicking on any
desktop icons).  Console switching still worked.  SIGTERM failed to
impress panel and desktop, so turned to SIGKILL.  No change on the
desktop (still a working mouse cursor but no reaction to keys or clicks)
when console-switching back.  Finally, switching back stopped working
also, displaying just a blinking text cursor on a blank screen, then
this abort.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-core 2:1.19.3-1ubuntu7
ProcVersionSignature: Ubuntu 4.13.0-12.13-lowlatency 4.13.3
Uname: Linux 4.13.0-12-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Oct 11 16:14:49 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5]
   Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5]
InstallationDate: Installed on 2011-10-14 (2189 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
MachineType: LENOVO 7661LN8
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-lowlatency 
root=UUID=a5b30f2d-d555-4bea-9b89-e322f13656be ro quiet splash threadirqs 
resume=UUID=29869a91-5410-4e9b-9bd9-2aea1ecb1637
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ()
 ()
 ()
 xf86VTEnter ()
 WakeupHandler ()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 03/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC9WW (2.29 )
dmi.board.name: 7661LN8
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 000L004051
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7661LN8:pvrThinkPadT61:rvnLENOVO:rn7661LN8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T61
dmi.product.name: 7661LN8
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful ubuntu

** 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/1722824

Title:
  Xorg crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1722824/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libxfce4panel-2.0-4 4.12.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-lowlatency 4.13.3
Uname: Linux 4.13.0-12-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Oct  5 10:00:02 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2011-10-14 (2182 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 11 
10485792 indicator Indicator\ Plugin Provides\ a\ panel\ area\ for\ Unity\ 
indicators.\ Indicators\ allow\ applications\ and\ system\ services\ to\ 
display\ their\ status\ and\ interact\ with\ the\ user.
SegvAnalysis:
 Segfault happened at: 0x7f30a3e49926:  mov%rdi,0x10(%rax)
 PC (0x7f30a3e49926) ok
 source "%rdi" ok
 destination "0x10(%rax)" (0x0010) not located in a known VMA region 
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: wrapper-2.0 crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfce4-panel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace

** 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/1721485

Title:
  wrapper-2.0 crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1721485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 no attribute 'STOCK_CANCEL'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1708104/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

>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 16:39:21 + (31 minutes, 45 seconds ago)

On Mon, Sep 18, 2017 at 07:31:41AM +0200, Hermann Meyer wrote:
 
> Am 18.09.2017 um 06:44 schrieb david:
> >Starting Aeolus from command line returns this:
> >
> >Reading '/usr/share/aeolus/stops/Aeolus/definition'
> >Reading '/home/david/.aeolus-presets'
> >Segmentation fault
>
> First shot in such cases is remove/rename config files in home
> '/home/david/.aeolus-presets'

No, this is due to recent versions of the font libs requiring
more stack space. 

In main.cc, line 253, increase the stack size of the interface
thread:

  iface->thr_start (SCHED_OTHER, 0, 0x0002);

This should solve the issue.

Ciao,

-- 
FA

A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aeolus/+bug/1708027/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aeolus/+bug/1708027/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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 remove and 0 not upgraded.
Need to get 0 B/13.7 kB of archives.
After this operation, 19.5 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 353836 files and directories currently installed.)
Preparing to unpack .../libxvmc1_2%3a1.0.10-1_amd64.deb ...
Unpacking libxvmc1:amd64 (2:1.0.10-1) over (2:1.0.9-1ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libxvmc1_2%3a1.0.10-1_amd64.deb (--unpack):
 trying to overwrite shared '/etc/X11/XvMCConfig', which is different from 
other instances of package libxvmc1:amd64
Errors were encountered while processing:
 /var/cache/apt/archives/libxvmc1_2%3a1.0.10-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
dak@lola:/usr/local/tmp/lilypond$ dpkg -S !$
dpkg -S /etc/X11/XvMCConfig
libxvmc1:i386: /etc/X11/XvMCConfig
dak@lola:/usr/local/tmp/lilypond$ sudo apt-get remove libxvmc1:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package 'libxvmc1:i386' is not installed, so not removed. Did you mean 
'libxvmc1'?
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
dak@lola:/usr/local/tmp/lilypond$ cat /etc/X11/XvMCConfig 
libXvMC.so.1
dak@lola:/usr/local/tmp/lilypond$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715350

Title:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxvmc/+bug/1715350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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.
https://bugs.launchpad.net/bugs/1715350

Title:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxvmc/+bug/1715350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[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

[David Kastrup]

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: 2.20.7-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Sep  6 11:29:45 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 tp_smapi, 0.42, 4.12.0-11-lowlatency, x86_64: installed
 tp_smapi, 0.42, 4.12.0-12-lowlatency, x86_64: installed
 v4l2loopback, 0.10.0, 4.12.0-11-lowlatency, x86_64: installed
 v4l2loopback, 0.10.0, 4.12.0-12-lowlatency, x86_64: installed
DuplicateSignature:
 package:libxvmc1:2:1.0.9-1ubuntu1
 Unpacking libxvmc1:amd64 (2:1.0.10-1) over (2:1.0.9-1ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-uVoBwf/68-libxvmc1_2%3a1.0.10-1_amd64.deb (--unpack):
  trying to overwrite shared '/etc/X11/XvMCConfig', which is different from 
other instances of package libxvmc1:amd64
ErrorMessage: trying to overwrite shared '/etc/X11/XvMCConfig', which is 
different from other instances of package libxvmc1:amd64
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5]
   Subsystem: Lenovo ThinkPad T61/R61 [17aa:20b5]
InstallationDate: Installed on 2011-10-14 (2153 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
MachineType: LENOVO 7661LN8
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-12-lowlatency 
root=UUID=a5b30f2d-d555-4bea-9b89-e322f13656be ro quiet splash threadirqs 
resume=UUID=29869a91-5410-4e9b-9bd9-2aea1ecb1637 vt.handoff=7
Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~rc1~ubuntu1
SourcePackage: libxvmc
Title: 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
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC9WW (2.29 )
dmi.board.name: 7661LN8
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 000L004051
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn7661LN8:pvrThinkPadT61:rvnLENOVO:rn7661LN8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T61
dmi.product.name: 7661LN8
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: libxvmc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict single-occurrence ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1715350

Title:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxvmc/+bug/1715350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
Version: 2.3.0-
(C) 2008, Daniel Wagner, Pieter Palmers
This program comes with ABSOLUTELY NO WARRANTY.
---

01367863317: Debug (devicemanager.cpp)[ 354] discover: Starting discovery...
01367938381: Debug (Configuration.cpp)[ 163] showSetting:   Group: (null)
01367938415: Debug (Configuration.cpp)[ 185] showSetting: vendorid = 1429 
(0x0595)
01367938427: Debug (Configuration.cpp)[ 185] showSetting: modelid = 1 
(0x0001)
01367938438: Debug (Configuration.cpp)[ 209] showSetting: vendorname = 
Alesis
01367938442: Debug (Configuration.cpp)[ 209] showSetting: modelname = io|14
01367938448: Debug (Configuration.cpp)[ 209] showSetting: driver = DICE
01367938560: Debug (Configuration.cpp)[ 163] showSetting:   Group: (null)
01367938569: Debug (Configuration.cpp)[ 185] showSetting: vendorid = 1429 
(0x0595)
01367938573: Debug (Configuration.cpp)[ 185] showSetting: modelid = 1 
(0x0001)
01367938578: Debug (Configuration.cpp)[ 209] showSetting: vendorname = 
Alesis
01367938582: Debug (Configuration.cpp)[ 209] showSetting: modelname = io|14
01367938588: Debug (Configuration.cpp)[ 209] showSetting: driver = DICE
01367938648: Debug (Configuration.cpp)[ 163] showSetting:   Group: (null)
01367938657: Debug (Configuration.cpp)[ 185] showSetting: vendorid = 1429 
(0x0595)
01367938660: Debug (Configuration.cpp)[ 185] showSetting: modelid = 1 
(0x0001)
01367938666: Debug (Configuration.cpp)[ 209] showSetting: vendorname = 
Alesis
01367938668: Debug (Configuration.cpp)[ 209] showSetting: modelname = io|14
01367938674: Debug (Configuration.cpp)[ 209] showSetting: driver = DICE
01367938721: Debug (Configuration.cpp)[ 163] showSetting:   Group: (null)
01367938730: Debug (Configuration.cpp)[ 185] showSetting: vendorid = 1429 
(0x0595)
01367938733: Debug (Configuration.cpp)[ 185] showSetting: modelid = 1 
(0x0001)
01367938739: Debug (Configuration.cpp)[ 209] showSetting: vendorname = 
Alesis
01367938742: Debug (Configuration.cpp)[ 209] showSetting: modelname = io|14
01367938747: Debug (Configuration.cpp)[ 209] showSetting: driver = DICE
01367938797: Debug (Configuration.cpp)[ 163] showSetting:   Group: (null)
01367938805: Debug (Configuration.cpp)[ 185] showSetting: vendorid = 1429 
(0x0595)
01367938809: Debug (Configuration.cpp)[ 185] showSetting: modelid = 1 
(0x0001)
01367938820: Debug (Configuration.cpp)[ 209] showSetting: vendorname = 
Alesis
01367938828: Debug (Configuration.cpp)[ 209] showSetting: modelname = io|14
01367938835: Debug (Configuration.cpp)[ 209] showSetting: driver = DICE
01367938966: Debug (devicemanager.cpp)[ 616] discover: driver found for device 1
01367939040: Debug (Configuration.cpp)[ 163] showSetting:   Group: (null)
01367939046: Debug (Configuration.cpp)[ 185] showSetting: vendorid = 1429 
(0x0595)
01367939053: Debug (Configuration.cpp)[ 185] showSetting: modelid = 1 
(0x0001)
01367939058: Debug (Configuration.cpp)[ 209] showSetting: vendorname = 
Alesis
01367939065: Debug (Configuration.cpp)[ 209] showSetting: modelname = io|14
01367939068: Debug (Configuration.cpp)[ 209] showSetting: driver = DICE
01368031604: Warning (dice_eap.cpp)[ 115] init: no EAP mixer (device does not 
support EAP)
01368031671: Warning (dice_avdevice.cpp)[ 201] discover: Could not init EAP
01368031870: Debug (devicemanager.cpp)[ 653] discover: discovery of node 1 on 
port 0 done...
01368031913: Debug (devicemanager.cpp)[ 661] discover: Discovery finished...
01368031989: Debug (devicemanager.cpp)[1258] showDeviceInfo: = Device 
Manager =
01368032298: Debug (Element.cpp)[ 121] show: Element DeviceManager
01368032349: Debug (devicemanager.cpp)[1266] showDeviceInfo: --- IEEE1394 
Service  0 ---
01368032389: Debug (devicemanager.cpp)[1276] showDeviceInfo: --- Device  0 ---
01368032430: Debug (dice_avdevice.cpp)[ 710] showDevice: Device is a DICE device
01368032464:  (dice_avdevice.cpp)[ 713] showDevice:  DICE Parameter Space info:
01368032501:  (dice_avdevice.cpp)[ 714] showDevice:   Global  : offset=0x0028 
size=0360
01368032533:  (dice_avdevice.cpp)[ 715] showDevice:   TX  : offset=0x0190 
size=0568
01368032571:  (dice_avdevice.cpp)[ 716] showDevice: nb=   2 
size=0280
01368032603:  (dice_avdevice.cpp)[ 717] showDevice:   RX  : offset=0x03C8 
size=1128
01368032642:  (dice_avdevice.cpp)[ 718] showDevice: nb=   1 
size=0280
01368032674:  (dice_avdevice.cpp)[ 719] showDevice:   UNUSED1 : offset=0x 
size=
01368032713:  (dice_avdevice.cpp)[ 720] showDevice:   UNUSED2 : offset=0x 

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

[David Kastrup]

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: 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
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 31 15:28:05 2017
ExecutablePath: /usr/bin/ffado-test-streaming
InstallationDate: Installed on 2011-10-14 (2148 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: ffado-test-streaming
SegvAnalysis:
 Segfault happened at: 0x7f25bb6b9d32 <__GI___libc_free+34>:mov
-0x8(%rdi),%rax
 PC (0x7f25bb6b9d32) ok
 source "-0x8(%rdi)" (0x03f9) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libffado
StacktraceTop:
 __GI___libc_free (mem=0x401) at malloc.c:2966
 ()
 __libc_start_main (main=0xf6ba13cd97, argc=1, argv=0x7ffc0fddf5f8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc0fddf5e8) at ../csu/libc-start.c:291
 ()
Title: ffado-test-streaming crashed with SIGSEGV in __GI___libc_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: libffado (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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714250

Title:
  ffado-test-streaming crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1714250/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714243] [NEW] caja crashed with SIGSEGV

[David Kastrup]

*** 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 x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 31 13:53:09 2017
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2011-10-14 (2147 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/caja --no-default-window
SegvAnalysis:
 Segfault happened at: 0x7ff0fb0018b0:  mov(%rdi),%rax
 PC (0x7ff0fb0018b0) ok
 source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: caja
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: caja crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: caja (Ubuntu)
 Importance: Undecided
 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714243

Title:
  caja crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1714243/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
AssertionMessage: *** Error in 
`/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0': corrupted double-linked 
list: 0x001d9680d5f0 ***
CrashCounter: 1
CurrentDesktop: XFCE
Date: Thu Aug 31 00:12:47 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2011-10-14 (2147 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 11 
10485792 indicator Indicator\ Plugin Provides\ a\ panel\ area\ for\ Unity\ 
indicators.\ Indicators\ allow\ applications\ and\ system\ services\ to\ 
display\ their\ status\ and\ interact\ with\ the\ user.
Signal: 6
SourcePackage: xfce4-panel
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f464b98cf68 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (ar_ptr=0x7f464bbbdb00 , ptr=0x1d9680d5f0, 
str=0x7f464b989afb "corrupted double-linked list", action=) at 
malloc.c:5049
 _int_malloc (av=av@entry=0x7f464bbbdb00 , bytes=bytes@entry=16) at 
malloc.c:3765
 __GI___libc_malloc (bytes=16) at malloc.c:2928
 __GI___libc_realloc (oldmem=0x0, bytes=16) at malloc.c:3011
Title: wrapper-2.0 assert failure: *** Error in 
`/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0': corrupted double-linked 
list: 0x001d9680d5f0 ***
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfce4-panel (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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714108

Title:
  wrapper-2.0 assert failure: *** Error in `/usr/lib/x86_64-linux-
  gnu/xfce4/panel/wrapper-2.0': corrupted double-linked list:
  0x001d9680d5f0 ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1714108/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Wed Aug 30 22:45:15 2017
ExecutablePath: /usr/bin/ffado-test-streaming
InstallationDate: Installed on 2011-10-14 (2147 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: ffado-test-streaming
SegvAnalysis:
 Segfault happened at: 0x7f70246776fc 
<_ZN9Streaming15StreamProcessor14packetsStoppedEv+12>:movl   $0x2,0x64(%rax)
 PC (0x7f70246776fc) ok
 source "$0x2" ok
 destination "0x64(%rax)" (0x0064) not located in a known VMA region 
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: libffado
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: ffado-test-streaming crashed with SIGSEGV in 
Streaming::StreamProcessor::packetsStopped()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: libffado (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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714089

Title:
  ffado-test-streaming crashed with SIGSEGV in
  Streaming::StreamProcessor::packetsStopped()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1714089/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Wed Aug 30 19:28:23 2017
ExecutablePath: /usr/bin/blueman-manager
InstallationDate: Installed on 2011-10-14 (2147 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
InterpreterPath: /usr/bin/python3.6
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-manager
Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
PythonArgs: ['/usr/bin/blueman-manager']
PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
SourcePackage: blueman
Title: blueman-manager crashed with TypeError in close_rfcomm(): a bytes-like 
object is required, not 'str'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: blueman (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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714058

Title:
  blueman-manager crashed with TypeError in close_rfcomm(): a bytes-like
  object is required, not 'str'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1714058/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 time.
The access on the camera is on while Ristretto hangs, so presumably it
is doing something that causes it to reread the same information
unbuffered again and again or doing something else that is very, very
inefficient on a file system mounted via USB (reading bytewise and
adjusting the access time every time?).

Here is the camera description:
Bus 005 Device 023: ID 054c:0010 Sony Corp. DSC-S30/S70/S75/F505V/F505/FD92/W1 
Cybershot/Mavica Digital Camera
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 8
  idVendor   0x054c Sony Corp.
  idProduct  0x0010 DSC-S30/S70/S75/F505V/F505/FD92/W1 Cybershot/Mavica 
Digital Camera
  bcdDevice4.50
  iManufacturer   1 Sony
  iProduct2 Sony DSC
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   39
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0 
bmAttributes 0xc0
  Self Powered
MaxPower2mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass255 
  bInterfaceProtocol  1 
  iInterface  0 
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0040  1x 64 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval 255
Device Status: 0x0001
  Self Powered

Here is the mount entry:
/dev/sdd1 on /media/dak/8867-BE11 type vfat 
(rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)


This is a reasonably straightforward amd64 Ubuntustudio installation.

All other basic utilities and operations on that "drive" provided by the
camera are reasonably fast and corresponding to what you can expect from
"full speed" USB 1.1.

But Ristretto is unusable.  It needs to do something differently when
reading files: this just doesn't work.  I've never seen fit to let it
complete but rather killed it after a few minutes.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ristretto 0.8.2-1
ProcVersionSignature: Ubuntu 4.12.0-11.12-lowlatency 4.12.5
Uname: Linux 4.12.0-11-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Aug 28 10:49:16 2017
InstallationDate: Installed on 2011-10-14 (2144 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
SourcePackage: ristretto
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ristretto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713432

Title:
  Ristretto crawls to a halt on USB1.1 file systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1713432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1713216] [NEW] caja crashed with SIGSEGV

[David Kastrup]

*** 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 4.12.5
Uname: Linux 4.12.0-11-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Sat Aug 26 11:10:27 2017
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2011-10-14 (2142 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/caja --no-default-window
SegvAnalysis:
 Segfault happened at: 0x7f49f8fce8b0:  mov(%rdi),%rax
 PC (0x7f49f8fce8b0) ok
 source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: caja
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: caja crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: caja (Ubuntu)
 Importance: Undecided
 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713216

Title:
  caja crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1713216/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 4.12.5
Uname: Linux 4.12.0-11-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Aug 25 21:20:44 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2011-10-14 (2142 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 11 
10485792 indicator Indicator\ Plugin Provides\ a\ panel\ area\ for\ Unity\ 
indicators.\ Indicators\ allow\ applications\ and\ system\ services\ to\ 
display\ their\ status\ and\ interact\ with\ the\ user.
SegvAnalysis:
 Segfault happened at: 0x71e2a6e310:(bad)
 PC (0x71e2a6e310) in non-executable VMA region: 0x71e2522000-0x71e2c5 rw-p 
[heap]
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
 ()
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 dbusmenu_client_menuitem_new () at 
/usr/lib/x86_64-linux-gnu/libdbusmenu-glib.so.4
Title: wrapper-2.0 crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: xfce4-panel (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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713139

Title:
  wrapper-2.0 crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1713139/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1705570] Re: jackd crashed with SIGSEGV in Streaming::StreamProcessor::packetsStopped()

[David Kastrup]

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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705570

Title:
  jackd crashed with SIGSEGV in
  Streaming::StreamProcessor::packetsStopped()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1705570/+subscriptions

-- 
ubuntu-bugs mailing list

[Bug 1712382] [NEW] caja crashed with SIGSEGV

[David Kastrup]

*** 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 4.12.0-11-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
Date: Tue Aug 22 17:33:26 2017
ExecutablePath: /usr/bin/caja
InstallationDate: Installed on 2011-10-14 (2139 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: /usr/bin/caja --no-default-window
SegvAnalysis:
 Segfault happened at: 0x7f501ccb9870:  mov(%rdi),%rax
 PC (0x7f501ccb9870) ok
 source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: caja
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: caja crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: caja (Ubuntu)
 Importance: Undecided
 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712382

Title:
  caja crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1712382/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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 4.12.0-11.12-lowlatency 4.12.5
Uname: Linux 4.12.0-11-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu5
AptOrdering:
 lilypond-data:amd64: Install
 lilypond:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Aug 18 17:20:36 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2011-10-14 (2135 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~beta1
SourcePackage: lilypond
Title: package lilypond-data 2.18.2-8 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lilypond (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711702

Title:
  package lilypond-data 2.18.2-8 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1711702/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

*** 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 4.11.0-13-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Aug 17 10:14:44 2017
ExecutablePath: /usr/bin/aeolus
InstallationDate: Installed on 2011-10-14 (2133 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: aeolus -I Aeolus2 -S /home/username/.aeolus/stops
SegvAnalysis:
 Segfault happened at: 0x7f3f75cfe2e4:  rep stos %rax,%es:(%rdi)
 PC (0x7f3f75cfe2e4) ok
 source "%rax" ok
 destination "%es:(%rdi)" (0x7f3f744c2e10) in non-writable VMA region: 
0x7f3f744c2000-0x7f3f744c4000 r--p 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
Signal: 11
SourcePackage: aeolus
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6
 XftFontLoadGlyphs () from /usr/lib/x86_64-linux-gnu/libXft.so.2
Title: aeolus crashed with SIGSEGV in FT_Load_Glyph()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: aeolus (Ubuntu)
 Importance: Undecided
 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711307

Title:
  aeolus crashed with SIGSEGV in FT_Load_Glyph()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aeolus/+bug/1711307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: --prefix=/usr --extra-version=1ubuntu1 --toolchain=hardened 
--libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu 
--enable-gpl --disable-stripping --enable-avresample --enable-avisynth 
--enable-gnutls --enable-ladspa --enable-libass --enable-libbluray 
--enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite 
--enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme 
--enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt 
--enable-libopus --enable-libpulse --enable-librubberband --enable-libshine 
--enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh 
--enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx 
--enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid 
--enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl 
--enable-sdl2 --enable-libdc1394 --enable-libiec61883 --enable-chromaprint 
--enable-frei0r --enable-libopencv --en
 able-libx264 --enable-shared
  WARNING: library configuration mismatch
  avcodec configuration: --prefix=/usr --extra-version=1ubuntu1 
--toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu 
--incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping 
--enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa 
--enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca 
--enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype 
--enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame 
--enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse 
--enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr 
--enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame 
--enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp 
--enable-libx265 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx 
--enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 
--enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-li
 bopencv --enable-libx264 --enable-shared --enable-version3 --disable-doc 
--disable-programs --enable-libopencore_amrnb --enable-libopencore_amrwb 
--enable-libtesseract --enable-libvo_amrwbenc --enable-netcdf
  libavutil  55. 58.100 / 55. 58.100
  libavcodec 57. 89.100 / 57. 89.100
  libavformat57. 71.100 / 57. 71.100
  libavdevice57.  6.100 / 57.  6.100
  libavfilter 6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.  0
  libswscale  4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc54.  5.100 / 54.  5.100
Segmentation fault (core dumped)

I don't know whether the reported library version mismatch in the
warning might be relevant.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: ffmpeg 7:3.3.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-13.19-lowlatency 4.11.12
Uname: Linux 4.11.0-13-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 15 11:42:18 2017
ExecutablePath: /usr/bin/ffmpeg
InstallationDate: Installed on 2011-10-14 (2131 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: ffmpeg -f libdc1394 -video_size 640x480 -framerate 15 -i fw.0 
-pix_fmt bgr24 -f v4l2 /dev/video0
SegvAnalysis:
 Segfault happened at: 0x7f6f755ffb7d:  mov0xa8(%rdi),%eax
 PC (0x7f6f755ffb7d) ok
 source "0xa8(%rdi)" (0x00a8) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ffmpeg
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libavdevice.so.57
 avformat_open_input () from /usr/lib/x86_64-linux-gnu/libavformat.so.57
 ?? ()
 ?? ()
 main ()
Title: ffmpeg crashed with SIGSEGV in avformat_open_input()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: ffmpeg (Ubuntu)
 Importance: Undecided
 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710849

Title:
  ffmpeg crashed with SIGSEGV in avformat_open_input()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1710849/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
ProcVersionSignature: Ubuntu 4.11.0-13.19-lowlatency 4.11.12
Uname: Linux 4.11.0-13-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Tue Aug 15 11:21:42 2017
ExecutablePath: /usr/bin/ekiga
InstallationDate: Installed on 2011-10-14 (2131 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: ekiga
SegvAnalysis:
 Segfault happened at: 0x7f345fa11d69 
<_ZNK17OpalPluginControl4CallEPvPjS0_+45>:mov0x8(%rax),%rax
 PC (0x7f345fa11d69) ok
 source "0x8(%rax)" (0x7f3444d04638) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: ekiga
StacktraceTop:
 OpalPluginControl::Call(void*, unsigned int*, void*) const () at 
/usr/lib/libopal.so.3.10.10
 OpalPluginVideoTranscoder::EncodeFrames(RTP_DataFrame const&, 
PList&) () at /usr/lib/libopal.so.3.10.10
 OpalPluginVideoTranscoder::ConvertFrames(RTP_DataFrame const&, 
PList&) () at /usr/lib/libopal.so.3.10.10
 OpalMediaPatch::Sink::WriteFrame(RTP_DataFrame&) () at 
/usr/lib/libopal.so.3.10.10
 OpalMediaPatch::DispatchFrame(RTP_DataFrame&) () at /usr/lib/libopal.so.3.10.10
Title: ekiga crashed with SIGSEGV in OpalPluginControl::Call()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: ekiga (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace

** 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/1710844

Title:
  ekiga crashed with SIGSEGV in OpalPluginControl::Call()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/1710844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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
Package: jack-keyboard 2.7.1-1build1
ProcVersionSignature: Ubuntu 4.11.0-13.19-lowlatency 4.11.12
Uname: Linux 4.11.0-13-lowlatency x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Aug 12 16:20:39 2017
ExecutablePath: /usr/bin/jack-keyboard
InstallationDate: Installed on 2011-10-14 (2129 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: jack-keyboard
Signal: 6
SourcePackage: jack-keyboard
StacktraceTop:
 init_jack ()
 main ()
Title: jack-keyboard crashed with SIGABRT in init_jack()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev 
pulse-access sambashare

** Affects: jack-keyboard (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace

** 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/1710379

Title:
  jack-keyboard crashed with SIGABRT in init_jack()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jack-keyboard/+bug/1710379/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

[David Kastrup]

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: 2.20.6-0ubuntu4
Architecture: amd64
CupsErrorLog:
 W [12/Aug/2017:00:09:05 +0200] Duplicate listen address 
"/var/run/cups/cups.sock" ignored.
 E [12/Aug/2017:00:09:05 +0200] Unknown directive JobPrivateAccess on line 85 
of /etc/cups/cupsd.conf.
 E [12/Aug/2017:00:09:05 +0200] Unknown directive JobPrivateValues on line 86 
of /etc/cups/cupsd.conf.
 E [12/Aug/2017:00:09:05 +0200] Unknown directive SubscriptionPrivateAccess on 
line 87 of /etc/cups/cupsd.conf.
 E [12/Aug/2017:00:09:05 +0200] Unknown directive SubscriptionPrivateValues on 
line 88 of /etc/cups/cupsd.conf.
Date: Sat Aug 12 15:53:23 2017
DuplicateSignature:
 package:libsane-hpaio:3.17.6+repack0-2build1
 Unpacking libsane-hpaio:amd64 (3.17.7+repack0-2) over (3.17.6+repack0-2build1) 
...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-xaS5A5/079-libsane-hpaio_3.17.7+repack0-2_amd64.deb 
(--unpack):
  trying to overwrite shared '/etc/hp/hplip.conf', which is different from 
other instances of package libsane-hpaio:amd64
ErrorMessage: trying to overwrite shared '/etc/hp/hplip.conf', which is 
different from other instances of package libsane-hpaio:amd64
InstallationDate: Installed on 2011-10-14 (2129 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
Lpstat:
 device for Canon-PIXMA-MP150: usb://Canon/MP150?serial=21BD86=1
 device for HP-Officejet-Pro-276dw-MFP: 
dnssd://HP%20Officejet%20Pro%20276dw%20MFP%20%5BD7A6FB%5D._ipp._tcp.local/
 device for ML-4600: usb://Samsung/ML-4600
 device for Roger-Router-Fax: roger-cups:/
MachineType: LENOVO 766112G
Papersize: a4
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
PpdFiles:
 HP-Officejet-Pro-276dw-MFP: HP Officejet Pro 276dw MFP Postscript (recommended)
 Roger-Router-Fax: roger fax printer, 1.0
 ML-4600: Samsung ML-4600 Foomatic/ljet4
 Canon-PIXMA-MP150: Canon PIXMA MP150 - CUPS+Gutenprint v5.2.13
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-lowlatency 
root=UUID=a5b30f2d-d555-4bea-9b89-e322f13656be ro quiet splash threadirqs 
resume=UUID=29869a91-5410-4e9b-9bd9-2aea1ecb1637 vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~beta1
SourcePackage: hplip
Title: 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-hpaio:amd64
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC9WW (2.29 )
dmi.board.name: 766112G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn766112G:pvrThinkPadT61:rvnLENOVO:rn766112G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 766112G
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO

** Affects: hplip (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710374

Title:
  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-hpaio:amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1710374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs