Calibre crashes the window manager on start-up

[PeterPall]

On my computer after setting the calibre user interface to "slim" any further try to start calibre crashed the window manager (tried with gnome-shell and metacity).
Gnome-shell did complain about a modal dialog with a ridiculously high minimal size.

Then I deleted all remains find -name calibre found from my home directoryand started anew.
This time a dialog popped up asking me where to put the library. A soon as I answer this question the window manager crashes again.

After switching to wm2 as window manager I got the following error messages:

(python2.7:4620): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed
QNativeImage: Unable to attach to shared memory segment.

X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id: 0x0

Before the window manager crashes my computer starts rapidly eating up any swap space I have (I use 4 Gigs of RAM and 10 Gigs of Swap).and all processes that run for a longer time (e.G. ogmrip) tend to get killed.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: calibre 0.8.51+dfsg-1ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
Uname: Linux 3.5.0-4-generic x86_64
ApportVersion: 2.3-0ubuntu4
Architecture: amd64
Date: Sat Jul 14 19:10:58 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/calibre
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
SourcePackage: calibre
UpgradeStatus: No upgrade log present (probably fresh install)

[PeterPall (peterpall)]

Using wm2 and gnome classic I now get an endless stream of messages indicating what might have eaten up all my RAM:

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

(python2.7:9372): Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)
QWidget::setMinimumSize: (MainWindow/Main) The largest allowed size is (16777215,16777215)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sasa Paporovic (melchiaros)]

Sory, for the confusion it has become late in my timezone and concentration has become low.

Anyway,
what we see here is a xorg crash.

What we need is a stacktrace of it.

1.Then reproduce the crash.

2.Log in again and run

apport-collect 1024750

from terminal.

Where there is a warning message that you are not the original reporter -> ignore it.

When we have luck the XorgOld.log should have a valuable stacktrace in it and I can isolate it(or you if you want) and give as comment here.

The best would be when the reproducing would be done under unity desktop.

Many thanks in advance

melchiaros

Please only one person(the first) do the apport-collect. The later ones should only identifying and reporting back. When it is not the same we do a separate report.

When the apport-collect run is done please set the status of the report back to confirmed.

[PeterPall (peterpall)]

Thanks a lot!

I Already have installed unity for the test - but will be able to do the
actual test tomorrow since today I have a task running on my computer I
don't want to risk to crash.

Kind regards,

       Gunter.

[PeterPall (peterpall)]

Hope the collection of data about the bug worked.
In the meantime I got the old error message again:

Window manages warning: Window 0x4200013 (calibre - ) sets an MWM hint
indicating it isn't resizable, but sets min size 16383 x 16383 and max
size 2147483647 x 2147483647; this doesn't make much sense.

A window this big that doesn't fit in the graphic's card's memory seems
to be a plausible reason for a crash.

Still it seems like the whole X server isn't always crashed:
Going to a console, killing the window manager, killing calibre (this
step is important, otherwise the window manager will immediately crash
again on re-launch - setting the DISPLAY variable to :0.0 and starting
the window manager again usually renders the system usable again.

Kind regards,

      Gunter.

[Bryce Harrington (bryce)]

No; it's not an X crash. "X error" messages are due to the client (or window manager) making improper X calls.

You can use the xtrace utility to study the communication between the client and server to diagnose where it's making the wrong call.

[PeterPall (peterpall)]

Did install xtrace - but something seems to be wrong:

#echo $DISPLAY
:9
#xtrace -c -D:10 -d:9 Calibre.txt
Error parsing xauth list data: less than three things in a line!

Does anybody know how to use it?

[PeterPall (peterpall)]

Calibre no more crashes the x server or window manager for me. But it still tries to create a ridiculously big main window rendering it useless since it cannot be displayed properly. What can I do?

[Barry Drake (b-drake)]

On the bugs of which this is said to be a duplicate, the command 'LIBOVERLAY_SCROLLBAR=0 calibre' is mentioned. This does seem to be a workaround and I am using Calibre perfectly well under 12.10 using this as a launcher.

[PeterPall (peterpall)]

Can confirm that: Uninstalling the package overlay-scrollbar solves the problem instantly.

[Barry Drake (b-drake)]

According to : https://launchpad.net/ubuntu/+source/overlay-scrollbar the package is needed to work the unity stuff such as the lenses .... I would have thought the above would have broken the Dash and possibly the HUD .... is this right?

[PeterPall (peterpall)]

I'm not using unity, but gnome-shell which is quite usable - if you install about twenty extensions along with it.
But as far as I know all the package does is hiding the scrollbars when you aren't scrolling and the mouse pointer is nowhere near the point the scrollbar would appear.

[Edward Donovan (edward.donovan)]

Well, as Barry said, then, that makes this a dupe of bug 1005677. I'll mark it a-thusly.