Application: calligrawords (2.9.7) KDE Platform Version: 4.14.13 Qt Version: 4.8.6 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Prerequisites Operating system: Kubuntu 15.10 Installed Calligra suite from binary distributions of ubuntu Version of Calligra words was 2.9.7 Steps to reproduce 1 Launch Konqueror 2. At Konqueror, navigate to some web site (e.g. http://wiki.freepascal.org/Main_Page) 3. press pulldown menu at draw area of page. Pulldown menu opens 4. Select item Actions -> Print with Calligra words -- Backtrace: Application: Calligra Words (calligrawords), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x00007f9ce281e24f in KoMainWindow::slotFilePrint (this=this@entry=0x1d9b560) at /build/calligra-ld8dSW/calligra-2.9.7/libs/main/KoMainWindow.cpp:1410 #7 0x00007f9ce27f6d32 in KoApplication::start (this=this@entry=0x7ffd844a2b40) at /build/calligra-ld8dSW/calligra-2.9.7/libs/main/KoApplication.cpp:556 #8 0x00007f9ce2e833b0 in kdemain (argc=<optimized out>, argv=<optimized out>) at /build/calligra-ld8dSW/calligra-2.9.7/words/app/main.cpp:42 #9 0x00007f9ce2ad6a40 in __libc_start_main (main=0x4006e0 <main(int, char**)>, argc=3, argv=0x7ffd844a2c88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd844a2c78) at libc-start.c:289 #10 0x0000000000400719 in _start () Reported using DrKonqi
If you have set up konq trying to print via calligra that is your own fault- if not then please report it elsewhere afaik we havn't supported such embedded behaviour for years
Calligra installs .desktop files for the service type KonqPopupMenu/Plugin to offer the option to use some Calligra programs as printing handlers for certain file types (see in the sources the folder extras/quickprint). With Words this will result in the command "calligrawords --print %U". It worked some versions ago. Cannot test right now, but ideally it would still work and not result in Words crashing. So not any fault by the user here I assume, but by us in our code :) The backtrace shows a valid problem when starting Words and using the "--print" argument. It should not crash in any case, so reopening the report. Hannu, I could not follow your example though. What do you mean with "draw area of page"? The quickprint service with Words does not register for the mimetype "text/html", so it possibly is something special, which needs more information.
I meant rendering area of the browser window I.e. the area, where browser renders the web page.