running from source dbus error

[eschwartz]

The latest source will not allow me to start calibre:

calibre 2.7*  isfrozen: True is64bit: False
Linux-3.17.1-1-ARCH-i686-with-glibc2.0 Linux ('32bit', 'ELF')
('Linux', '3.17.1-1-ARCH', '#1 SMP PREEMPT Wed Oct 15 15:36:07 CEST 2014')
Python 2.7.8
Linux: ('', '', '')
Successfully initialized third party plugins: DeDRM && KindleUnpack - The Plugin && Modify ePub && Annotations && Kindle Collections && Quality Check && Overdrive Link && Diaps Editing Toolbag && Open With && Goodreads Sync
Traceback (most recent call last):
  File "site.py", line 51, in main
  File "/home/eschwartz/git/calibre/src/calibre/debug.py", line 217, in main
    calibre(['calibre'])
  File "/home/eschwartz/git/calibre/src/calibre/gui_launch.py", line 45, in calibre
    init_dbus()
  File "/home/eschwartz/git/calibre/src/calibre/gui_launch.py", line 39, in init_dbus
    from dbus.mainloop.glib import DBusGMainLoop, threads_init
  File "site-packages/dbus/mainloop/glib.py", line 29, in <module>
ImportError: /usr/lib/libdbus-glib-1.so.2: undefined symbol: g_type_check_instance_is_fundamentally_a

Restarted after unsetting CALIBRE_DEVELOP_FROM, working fine.

[chaley]

You have probably run into an instance where the binary must and will change, but isn't yet available. Revert your source to before the dbus commit, wait for Friday, and see if the problem goes away. I don't see Kovid releasing a beta binary for one day, but of course he may feel differently.

[eschwartz]

IIRC there was a previous time when the same kind of problem happened, and he set it up so only newer binaries would run the newer code. Besides, that was an instance of compiled C++ extensions that were part of calibre. Only .py files have changed in the git log.

[chaley]

It has happened to me several times in my 4 years of calibre work. In those cases, every time my development was stopped, Kovid made a binary for me. If I could work around it by not pulling changes then we did that.

Of course, you might have found a distro incompatibility that may require a different approach.

[kovidgoyal]

Here are builds that include the needed dbus-glib library (I had to generate these anyway for my own testing on different VMs)

http://download.calibre-ebook.com/betas/

[eschwartz]

Originally Posted by kovidgoyal

Here are builds that include the needed dbus-glib library (I had to generate these anyway for my own testing on different VMs)

http://download.calibre-ebook.com/betas/

Why thanks!

(I figured that would be the issue, so I wanted to make sure you didn't get caught out on Friday.)

[kovidgoyal]

Always good to get a heads up from people running from source, often saves release time pain. In this case, this issue would only affect people on bleeding edge distros like Arch/Gentoo~ but it is still good to have caught it before release.

[eschwartz]

Always happy to be of service.

And good to see we have systray functionality back. Thanks for your hard work.