calibre crashed with SIGSEGV in _int_malloc()

Bug #1538278 reported by fabianbur
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
calibre (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Calibre stays in the Welcome screen and then crash.

Is the official package in Ubuntu 16.04

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: calibre 2.48.0+dfsg-1build1
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 26 15:02:38 2016
ExecutablePath: /usr/bin/calibre
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/calibre
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=es_EC.UTF-8
 LANGUAGE=es_EC:es
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f5e54bce84f <_int_malloc+31>: mov %rsi,0x10(%rsp)
 PC (0x7f5e54bce84f) ok
 source "%rsi" ok
 destination "0x10(%rsp)" (0x7ffd5a19cfb0) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: calibre
StacktraceTop:
 _int_malloc (av=av@entry=0x7f5e54f11c00 <main_arena>, bytes=bytes@entry=52) at malloc.c:3326
 __GI___libc_malloc (bytes=52) at malloc.c:2895
 QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags<QArrayData::AllocationOption>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: calibre crashed with SIGSEGV in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
fabianbur (fabianbur) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _int_malloc (av=av@entry=0x7f5e54f11c00 <main_arena>, bytes=bytes@entry=52) at malloc.c:3326
 __GI___libc_malloc (bytes=52) at malloc.c:2895
 QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags<QArrayData::AllocationOption>) () from /tmp/apport_sandbox_TR9rmQ/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QVector<QScriptItem>::reallocData(int, int, QFlags<QArrayData::AllocationOption>) () from /tmp/apport_sandbox_TR9rmQ/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 QVector<QScriptItem>::append(QScriptItem const&) () from /tmp/apport_sandbox_TR9rmQ/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in calibre (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
fabianbur (fabianbur) wrote :

I solved disabling overlay scrollbar

This commnand:
gsettings set com.canonical.desktop.interface scrollbar-mode normal

Revision history for this message
fabianbur (fabianbur) wrote :

But the window has a strange behavior with some blur to resize.
Also it lose the overlay feature. It is there that is the problem I think.

fabianbur (fabianbur)
information type: Private → Public
Revision history for this message
fabianbur (fabianbur) wrote :

The kernel was updated today to version 4.4
Calibre continues to fail

Changed in calibre (Ubuntu):
status: New → Confirmed
Revision history for this message
Ruairi (ruhann) wrote :

I have the same issue. Shows the welcome screen only. Launching from a terminal shows

"(python2.7:2300): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion 'GTK_IS_WIDGET (widget)' failed"

repeately. Followed by

"Segmentation fault (core dumped)"

Revision history for this message
Ruairi (ruhann) wrote :

I can also confirm that fabianburs fix

gsettings set com.canonical.desktop.interface scrollbar-mode normal

resolved the issue for me.

Revision history for this message
fabianbur (fabianbur) wrote :

This moment is fixed the bug

Changed in calibre (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.