I just installed Mint 14 with its Cinnamon desktop environment (Gnome Shell fork) because, well... who doesn't love the smell of a fresh OS install on a Friday morning? ;)
(Mint 14 64-bit [based on Ubuntu 12.10] w/Cinnamon; on AMD...)
Anyway... after installing calibre, I noticed some glitches (before anyone gets excited--I expected glitches; this isn't a "why won't calibre work perfectly in every single environment I toss it into?" kind of post) with the main user interface. I've seen a few other posts where calibre was crashing on MATE or Cinnamon on Mint 13, but not much else. Calibre's not crashing on me; it's just that when the main window opens, it's very small and out of sync with the mouse-pointer. At the top left-hand corner, everything is in sync, but gets worse the farther down and right you go. Once you get used to clicking on a button that isn't under your mouse-pointer, all other dialogs open and function as expected--normal size; pointer in sync.
It's the same whether I use the System Default UI theme or calibre's UI theme -- NVidia Proprietary X drivers or X.org's Nouveau display driver: small main window w/out of sync pointer and all other dialogs behaving as expected.
Then I discovered that if I start calibre in GUI debug mode (calibre-debug -g), everything works as expected! Which isn't that much of an inconvenience for me, truthfully--I run calibre in debug mode a lot for plugin development. So I don't mind--and maybe the info will help others out in a pinch.
I guess my questions are:
1) Why? What's different about the non-debug GUI main window-launch? Any under the hood tweaks that I can look into to alleviate the issue?
NOTE: no errors or warnings in the debug output. And each time a new terminal is launched, the first "calibre-debug -g" might result in the same quirky behavior as first described... the second (and consecutive) "calibre-debug -g" issued in that terminal will behave correctly. A desktop shortcut created as "calibre-debug -g" seems to work every time. session? .bashrc/bash_profile? env var?
2) What kind of performance hit can I realistically expect by running in debug mode? I'll be honest; I don't do any bulk-(imports|metadata edits|conversions)--I'm a one-book-at-a-time, no-custom-column-having, dabbler at plugin development. :)
(Mint 14 64-bit [based on Ubuntu 12.10] w/Cinnamon; on AMD...)
Anyway... after installing calibre, I noticed some glitches (before anyone gets excited--I expected glitches; this isn't a "why won't calibre work perfectly in every single environment I toss it into?" kind of post) with the main user interface. I've seen a few other posts where calibre was crashing on MATE or Cinnamon on Mint 13, but not much else. Calibre's not crashing on me; it's just that when the main window opens, it's very small and out of sync with the mouse-pointer. At the top left-hand corner, everything is in sync, but gets worse the farther down and right you go. Once you get used to clicking on a button that isn't under your mouse-pointer, all other dialogs open and function as expected--normal size; pointer in sync.
It's the same whether I use the System Default UI theme or calibre's UI theme -- NVidia Proprietary X drivers or X.org's Nouveau display driver: small main window w/out of sync pointer and all other dialogs behaving as expected.
Then I discovered that if I start calibre in GUI debug mode (calibre-debug -g), everything works as expected! Which isn't that much of an inconvenience for me, truthfully--I run calibre in debug mode a lot for plugin development. So I don't mind--and maybe the info will help others out in a pinch.
I guess my questions are:
1) Why? What's different about the non-debug GUI main window-launch? Any under the hood tweaks that I can look into to alleviate the issue?
NOTE: no errors or warnings in the debug output. And each time a new terminal is launched, the first "calibre-debug -g" might result in the same quirky behavior as first described... the second (and consecutive) "calibre-debug -g" issued in that terminal will behave correctly. A desktop shortcut created as "calibre-debug -g" seems to work every time. session? .bashrc/bash_profile? env var?
2) What kind of performance hit can I realistically expect by running in debug mode? I'll be honest; I don't do any bulk-(imports|metadata edits|conversions)--I'm a one-book-at-a-time, no-custom-column-having, dabbler at plugin development. :)