In openSUSE 13.1/i586 skanlite has two problems: 1) The preview scan shows the scanned object, but the real scan does not update the preview image. You will not see your scanned result until the Save Image windows shows up. 2) Skanlite crashes when you want to save the image, it does not respond to any interaction exept the Window-buttons in the upper right corner. When you attempt to close the window a message comes up which says that the application has crashed. Tested with skanlite 1.0-2.1.4 (original openSUSE 13.1) and 1.1-4.2 (from openSUSE build-service). The system has all latest updates. FYI: Simplescan has no problems at all to scan and save the image. Reproducible: Always Steps to Reproduce: 1. Start openSUSE 13.1 and use skanlite 2. Scan an object Actual Results: 1. Watch that no progress can be seen in the preview window while scanning. 2. Experience that the apllication crashes after scanning or when you want to save the scan result. Expected Results: 1. Progress of the scan should be seen in the preview window, as is while the preview scan is performed. 2. The application must not crash when the scan result shall be saved to dusk As simplescan works for me, I don't think the problem has any ralation to the used scanner Canon Lide 30.
also filed at https://bugzilla.novell.com/show_bug.cgi?id=801852 at 2014-01-13
If the crash is reproducible, please add the backtrace of the crash. For more information, please see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Created with KDbg: warning: GDB: Failed to set controlling terminal: Operation not permitted Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Skanlite(9907): couldn't create slave: "Unable to create io-slave: klauncher said: Unknown protocol ''. " QProcess: Destroyed while process is still running. --- Created with GDB: (gdb) run /usr/bin/skanlite Starting program: /usr/bin/skanlite /usr/bin/skanlite Missing separate debuginfo for /lib/ld-linux.so.2 Try: zypper install -C "debuginfo(build-id)=4b4510c03712a8dd812604c4040cefff4fceb4d7" Missing separate debuginfo for /usr/lib/libkio.so.5 Try: zypper install -C "debuginfo(build-id)=f00b0fd770b67e5160cf0b4ee7c565ddb24b2921" Missing separate debuginfo for /usr/lib/libksane.so.0 Try: zypper install -C "debuginfo(build-id)=46dbd2a9c8a1c5ac77a371f9f3d634d17fc0d903" Missing separate debuginfo for /usr/lib/libpng16.so.16 Try: zypper install -C "debuginfo(build-id)=fea06f082445b1764e7d146423c94f942038fcc2" Missing separate debuginfo for /usr/lib/libkdeui.so.5 Try: zypper install -C "debuginfo(build-id)=7e8d1111f121b19bb56b22b551aaed6f6c37ef9d" Missing separate debuginfo for /usr/lib/libkdecore.so.5 Try: zypper install -C "debuginfo(build-id)=6ac6cffbb15e66dcf5db4636fbea080325befd67" Missing separate debuginfo for /usr/lib/libQtCore.so.4 Try: zypper install -C "debuginfo(build-id)=f62654cff49451c7fba4bb47b8534d571042e73d" Missing separate debuginfo for /lib/libpthread.so.0 Try: zypper install -C "debuginfo(build-id)=3983532c49eeb3a1f250cabd326d82f4b0f52993" [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Missing separate debuginfo for /usr/lib/libQtGui.so.4 Try: zypper install -C "debuginfo(build-id)=3a8cf19a3167307a4ac7679f177e319a7fdc7319" Missing separate debuginfo for /usr/lib/libstdc++.so.6 Try: zypper install -C "debuginfo(build-id)=72496933dbed98d16b4ac17012f038de95dfd876" Missing separate debuginfo for /lib/libc.so.6 Try: zypper install -C "debuginfo(build-id)=7d29f2a83708b2dfa38839769c6b19f455f27d7d" Missing separate debuginfo for /usr/lib/libnepomuk.so.4 Try: zypper install -C "debuginfo(build-id)=d1eb2441dd726827567ae4f46edaf89c3e3b05ae" Missing separate debuginfo for /usr/lib/libQtNetwork.so.4 Try: zypper install -C "debuginfo(build-id)=50d808a0a015eeb0bd03412abb5f03fb3f5997b1" Missing separate debuginfo for /usr/lib/libQtXml.so.4 Try: zypper install -C "debuginfo(build-id)=d7a821603651b47b362a450d93461527373e11e6" Missing separate debuginfo for /usr/lib/libQtSvg.so.4 Try: zypper install -C "debuginfo(build-id)=745c6a6c54b4e8edc0bee5c653b48ae2daf2d44e" Missing separate debuginfo for /usr/lib/libX11.so.6 Try: zypper install -C "debuginfo(build-id)=af775657442f017fd4fb88c94aebf6914e01f663" Missing separate debuginfo for /usr/lib/libstreamanalyzer.so.0 Try: zypper install -C "debuginfo(build-id)=f7cda15296236bf2ab808793b6c476c719594319" Missing separate debuginfo for /usr/lib/libsolid.so.4 Try: zypper install -C "debuginfo(build-id)=064822869cb2d44aaf919ba54482011ae77762e2" Missing separate debuginfo for /usr/lib/libksuseinstall.so.1 Try: zypper install -C "debuginfo(build-id)=a0878fa03d294091ae1c416e790eb908f4db3916" Missing separate debuginfo for /lib/libacl.so.1 Try: zypper install -C "debuginfo(build-id)=e6eaafbc18d2cd998b3c8db4a061671ee968fc75" Missing separate debuginfo for /lib/libattr.so.1 Try: zypper install -C "debuginfo(build-id)=6583f1c60e4816e248c3477e3f77f001f08405d4" Missing separate debuginfo for /usr/lib/libXrender.so.1 Try: zypper install -C "debuginfo(build-id)=b76e4c2b091b19fbd4ae000bd5387fdd0f0d03f3" Missing separate debuginfo for /usr/lib/libQtDBus.so.4 Try: zypper install -C "debuginfo(build-id)=42d0709c78e7e00754183a20dca1fac2f7edab01" Missing separate debuginfo for /lib/libm.so.6 Try: zypper install -C "debuginfo(build-id)=7a18d05eb7fef493f59965f3e65debaf832d5872" Missing separate debuginfo for /lib/libgcc_s.so.1 Try: zypper install -C "debuginfo(build-id)=27f19299af6c68d7903ba16244eb3a0c157dd1df" Missing separate debuginfo for /usr/lib/libsane.so.1 Try: zypper install -C "debuginfo(build-id)=a4e8f827a8e78b7810eca7f3a5f5981a4456a7e8" Missing separate debuginfo for /lib/libz.so.1 Try: zypper install -C "debuginfo(build-id)=db6c20d993721c2ab4467b0728b2d0145822c867" Missing separate debuginfo for /usr/lib/libSM.so.6 Try: zypper install -C "debuginfo(build-id)=9ab27988d85aca047e8b77dc71cd5f40925daa3d" Missing separate debuginfo for /usr/lib/libICE.so.6 Try: zypper install -C "debuginfo(build-id)=83aa033e8432cc02aafb443f7f763e19ba74503e" Missing separate debuginfo for /usr/lib/libattica.so.0.4 Try: zypper install -C "debuginfo(build-id)=62b4ec4439c5d53a31d1fb8dd1eb36c6bad2b4fe" Missing separate debuginfo for /usr/lib/libdbusmenu-qt.so.2 Try: zypper install -C "debuginfo(build-id)=6ab1e02aa3e9a94909c69aef4c08325a754d7f9a" Missing separate debuginfo for /usr/lib/libXtst.so.6 Try: zypper install -C "debuginfo(build-id)=da34e3717d921524c7dc78ac4a4fb18b1c8c04f4" Missing separate debuginfo for /usr/lib/libXcursor.so.1 Try: zypper install -C "debuginfo(build-id)=016596c24a019840398d52723ce24faca07ef189" Missing separate debuginfo for /usr/lib/libXfixes.so.3 Try: zypper install -C "debuginfo(build-id)=2ee8a0528f3cb8077eae55a4a1bb7d34f5d00bad" Missing separate debuginfo for /usr/lib/libbz2.so.1 Try: zypper install -C "debuginfo(build-id)=ab1f0cc02211e09cc613326703f35e9833978c6a" Missing separate debuginfo for /usr/lib/liblzma.so.5 Try: zypper install -C "debuginfo(build-id)=8fa41eef1afb7b8641c395937135e9063f79c5c8" Missing separate debuginfo for /usr/lib/libfam.so.0 Try: zypper install -C "debuginfo(build-id)=5794f5a0e22c0b8d98a9fe5d4dac4ab7ba3809fd" Missing separate debuginfo for /lib/libdl.so.2 Try: zypper install -C "debuginfo(build-id)=65fb6112a451cb54c72649af0ebdfc48b62aba8a" Missing separate debuginfo for /usr/lib/libglib-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=e13442f21374e59f9702422f37e43400e6759ffe" Missing separate debuginfo for /lib/librt.so.1 Try: zypper install -C "debuginfo(build-id)=3e2b7ed006eee880bdd6548336df81780bc72514" Missing separate debuginfo for /usr/lib/libfreetype.so.6 Try: zypper install -C "debuginfo(build-id)=6d2250fe6c7e4633e02db65030dcacc430d20d68" Missing separate debuginfo for /usr/lib/libgobject-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=b9abfda2376658f67eedf540b7d2174cb1194f6d" Missing separate debuginfo for /usr/lib/libXi.so.6 Try: zypper install -C "debuginfo(build-id)=f726b6d0da9ba8c7be0362be0c13f448809b210e" Missing separate debuginfo for /usr/lib/libXrandr.so.2 Try: zypper install -C "debuginfo(build-id)=62985134d26765c9510f3d94592f3a3cefd13886" Missing separate debuginfo for /usr/lib/libXinerama.so.1 Try: zypper install -C "debuginfo(build-id)=9b49d0ca22be365d9b7ceb2300d85446002dc3aa" Missing separate debuginfo for /usr/lib/libfontconfig.so.1 Try: zypper install -C "debuginfo(build-id)=4229c352dfa4f53feebbc22272d1c177dc713567" Missing separate debuginfo for /usr/lib/libXext.so.6 Try: zypper install -C "debuginfo(build-id)=4036d5787909ff707ba4c6d346f6f644270e5eb0" Missing separate debuginfo for /usr/lib/libsoprano.so.4 Try: zypper install -C "debuginfo(build-id)=1e6f92c84a195b523052664458c253abccda024d" Missing separate debuginfo for /lib/libssl.so.1.0.0 Try: zypper install -C "debuginfo(build-id)=1f9fe9ccb4b8d47c9353fce94a39e02167b1716f" Missing separate debuginfo for /lib/libcrypto.so.1.0.0 Try: zypper install -C "debuginfo(build-id)=5f32793507c0c1e18ca1b093da821b46485f7a31" Missing separate debuginfo for /usr/lib/libxcb.so.1 Try: zypper install -C "debuginfo(build-id)=b2c64c1b6007eae5daa340530d7082c50449ff34" Missing separate debuginfo for /usr/lib/libstreams.so.0 Try: zypper install -C "debuginfo(build-id)=fd7d02f557a68359534e0c34f1b7dc5379d59184" Missing separate debuginfo for /usr/lib/libxml2.so.2 Try: zypper install -C "debuginfo(build-id)=2870de31a8dbe2ad6d9e13a0259a2dd2bbf3a6b2" Missing separate debuginfo for /usr/lib/libudev.so.1 Try: zypper install -C "debuginfo(build-id)=d81c2893e9c48b04113b8450e981ffdb42f3506d" Missing separate debuginfo for /lib/libdbus-1.so.3 Try: zypper install -C "debuginfo(build-id)=2c4d577206d7a11d79a9f8cb6a025d601e2d5040" Missing separate debuginfo for /usr/lib/libieee1284.so.3 Try: zypper install -C "debuginfo(build-id)=1f055ce66e932e16f80685f0a3cd86407529e5ad" Missing separate debuginfo for /usr/lib/libusb-1.0.so.0 Try: zypper install -C "debuginfo(build-id)=16d0137bf031fb0fcd4220e163d03d6bb7ab781b" Missing separate debuginfo for /usr/lib/libuuid.so.1 Try: zypper install -C "debuginfo(build-id)=6d30bb44046ab72212c45466f38e9187269f954f" Missing separate debuginfo for /usr/lib/libpcre.so.1 Try: zypper install -C "debuginfo(build-id)=f5fca1474dbee9604f20d1449c91531a6d7ecf8b" Missing separate debuginfo for /usr/lib/libffi.so.4 Try: zypper install -C "debuginfo(build-id)=7aeb4c4461890aae32ad033a75c5c288b24c493d" Missing separate debuginfo for /usr/lib/libexpat.so.1 Try: zypper install -C "debuginfo(build-id)=3f60f19ec71306778d58ed06ee4a26cd91f710ec" Missing separate debuginfo for /usr/lib/libXau.so.6 Try: zypper install -C "debuginfo(build-id)=56a7b53690ce817099c7d538faea936582d73995" Missing separate debuginfo for /lib/libselinux.so.1 Try: zypper install -C "debuginfo(build-id)=e618fffd54975f81f26d8c42127e2234b692b5d1" Missing separate debuginfo for /usr/lib/gconv/UTF-16.so Try: zypper install -C "debuginfo(build-id)=bc01c4acdf3d7dc8470c6fa8e11ea6f60e258cfc" Missing separate debuginfo for /usr/lib/libicui18n.so.51_2 Try: zypper install -C "debuginfo(build-id)=7a36ce637b363e13c224465b558c537478a9a2b6" Missing separate debuginfo for /usr/lib/libicuuc.so.51.2 Try: zypper install -C "debuginfo(build-id)=71f10e2a53f5b1024fea275cf9a02acccc3a8bd2" Missing separate debuginfo for /usr/lib/libicudata.so.51.2 Try: zypper install -C "debuginfo(build-id)=448013f804ec7c1ef715212f9b4602d52d4efee4" skanlite: Unexpected argument '/usr/bin/skanlite'. skanlite: Use --help to get a list of available command line options. [Inferior 1 (process 10085) exited with code 0376] (gdb) --- If this is not helpful, please be so kind to tell me what to do instead. Thanks.
Hi, Read the relevant parts (openSUSE): http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#openSUSE Then install the debug packages for skanlite, kdebase and kdegraphics and run GDB again. When you execute 'run' in gdb you do not add the path to the application, just parameters if need. In the case of Skanlite no parameters are needed. Regards, Kåre
Detlef, any progress creating a backtrace? See also comment #4. # gdb skanlite (gdb) run ...provoke crash... (gdb) bt
If you can provide the information requested in comment #4, please add it.
Tried again after installing several KDE-related debug-packages. This is what I got after executing "gdb skanlite" as root: First I got lots of 'Missings' as shown in comment #3, then came this: ... Reading symbols from /usr/bin/skanlite...Reading symbols from /usr/lib/debug/usr/bin/skanlite.debug...done. done. (gdb) run Starting program: /usr/bin/skanlite [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb2ad4b40 (LWP 3253)] [Thread 0xb2ad4b40 (LWP 3253) exited] [New Thread 0xb2ad4b40 (LWP 3254)] [New Thread 0xb1b73b40 (LWP 3279)] [New Thread 0xb0abdb40 (LWP 3280)] [Thread 0xb0abdb40 (LWP 3280) exited] [Thread 0xb1b73b40 (LWP 3279) exited] [New Thread 0xb1b73b40 (LWP 3281)] [New Thread 0xafcb9b40 (LWP 3282)] [Thread 0xafcb9b40 (LWP 3282) exited] [Thread 0xb1b73b40 (LWP 3281) exited] [New Thread 0xb1b73b40 (LWP 3283)] Program received signal SIGINT, Interrupt. 0xb66537b1 in poll () from /lib/libc.so.6 (gdb) Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Skanlite(3249): couldn't create slave: "Unable to create io-slave: klauncher said: Unknown protocol ''. " Detaching after fork from child process 3284. QProcess: Destroyed while process is still running. Detaching after fork from child process 3296. QProcess: Destroyed while process is still running. Skanlite(3249): couldn't create slave: "Unable to create io-slave: klauncher said: Unknown protocol ''. " That's all, I hope this gives you useful information.
Detlef, thanks, we have progress :) But you forgot to use the "bt" command in gdb to actually get the backtrace. Please see steps in comment #5.
Sorry that I forgot the bachtrace, I'm not familiar with that sort of things. I did it again: ----Begin GDB---- Minseneroog:~ # gdb skanlite GNU gdb (GDB; openSUSE 13.1) 7.6.50.20130731-cvs Copyright (C) 2013 Free Software Foundation, Inc. <...> This GDB was configured as "i586-suse-linux". <...> .. Reading symbols from /usr/bin/skanlite...Reading symbols from /usr/lib/debug/usr/bin/skanlite.debug...done. done. (gdb) run Starting program: /usr/bin/skanlite Missing separate debuginfo for /lib/ld-linux.so.2 Try: zypper install -C "debuginfo(build-id)=4b4510c03712a8dd812604c4040cefff4fceb4d7" Missing separate debuginfo for /usr/lib/libksane.so.0 Try: zypper install -C "debuginfo(build-id)=46dbd2a9c8a1c5ac77a371f9f3d634d17fc0d903" <my comment: lots of "Missing separate debuginfo for"> Missing separate debuginfo for /lib/libnss_files.so.2 Try: zypper install -C "debuginfo(build-id)=4386dc9163fc7f19f99821cdef2f9e67de0ee524" [New Thread 0xb2ad4b40 (LWP 3707)] Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) <my comment: This is prescan:> [New Thread 0xb1b73b40 (LWP 3739)] [New Thread 0xb0abdb40 (LWP 3740)] [Thread 0xb0abdb40 (LWP 3740) exited] [Thread 0xb1b73b40 (LWP 3739) exited] <my comment: This is regular scan:> [New Thread 0xb1b73b40 (LWP 3751)] [New Thread 0xa9be4b40 (LWP 3752)] [Thread 0xa9be4b40 (LWP 3752) exited] [Thread 0xb1b73b40 (LWP 3751) exited] Skanlite(3676): couldn't create slave: "Unable to create io-slave: klauncher said: Unknown protocol ''. " [New Thread 0xb1b73b40 (LWP 3774)] Detaching after fork from child process 3775. QProcess: Destroyed while process is still running. [Thread 0xb1b73b40 (LWP 3774) exited] [Thread 0xb2ad4b40 (LWP 3707) exited] Program terminated with signal SIGKILL, Killed. The program no longer exists. (gdb) bt No stack. (gdb) ----End GDB---- Please see bug description above about what happens and what I do when skanlite crashes.
Hi, Thanks for the update. Unfortunately you have not installed the debug packages needed. I'm not familiar with how zypper and openSUSE works, but I think the output might hold a clue ;) Try running the zypper teminal commands for libkio and libksane and re-generate the backtrace. Missing separate debuginfo for /usr/lib/libkio.so.5 Try: zypper install -C "debuginfo(build-id)=f00b0fd770b67e5160cf0b4ee7c565ddb24b2921" Missing separate debuginfo for /usr/lib/libksane.so.0 Try: zypper install -C "debuginfo(build-id)=46dbd2a9c8a1c5ac77a371f9f3d634d17fc0d903" I think it should be possible to install the debug packages also from a package manager. The line "Program terminated with signal SIGKILL, Killed." suggests that the application did not crash but was terminated. Please wait at least 60 seconds. There has been other similar reports where the save dialog has been stuck for a looong time and then saves the file. Unfortunately I have not been able to reproduce it... Thanks, Kåre
> Program terminated with signal SIGKILL, Killed. Detlef, did you manually kill the process before using "bt" command? If the process is killed, gdb will not be able to create a backtrace.
Thanks to the comment from Kåre I did not kill the skanlite process today. I tried to save the scanned image. After waiting for ~60 seconds the scan actually was saved to disk. Before I installed all missing packages for debuginfo. After start of 'gdb skanlie' I got this: Minseneroog:~ # gdb skanlite GNU gdb (GDB; openSUSE 13.1) 7.6.50.20130731-cvs Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i586-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". .. Reading symbols from /usr/bin/skanlite...Reading symbols from /usr/lib/debug/usr/bin/skanlite.debug...done. done. (gdb) run Starting program: /usr/bin/skanlite [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> from gobject import register File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> import gdb.backtrace ImportError: No module named backtrace [New Thread 0xb2ad4b40 (LWP 3839)] [Thread 0xb2ad4b40 (LWP 3839) exited] [New Thread 0xb2ad4b40 (LWP 3841)] Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) [New Thread 0xb1b72b40 (LWP 3866)] [New Thread 0xa9be3b40 (LWP 3867)] [Thread 0xa9be3b40 (LWP 3867) exited] [Thread 0xb1b72b40 (LWP 3866) exited] Skanlite(3835): couldn't create slave: "Unable to create io-slave: klauncher said: Unknown protocol ''. " [New Thread 0xb1b72b40 (LWP 3874)] Detaching after fork from child process 3875. QProcess: Destroyed while process is still running. Detaching after fork from child process 3884. QProcess: Destroyed while process is still running. Skanlite(3835): couldn't create slave: "Unable to create io-slave: klauncher said: Unknown protocol ''. " [Thread 0xb1b72b40 (LWP 3874) exited] [Thread 0xb548b7c0 (LWP 3835) exited] [Inferior 1 (process 3835) exited normally] (gdb) bt No stack. (gdb) quit Minseneroog:~ #
> the scan actually was saved to disk ... and it still crashed? Kåre, does Skanlite detach (i.e. use KUniqueApplication)? Then --nofork option is needed when using gdb, this is explained at the link from comment #2.
Hi, Sorry Detlef, I have somehow missed your reply... Skanlite uses KApplication, so the GDB output is from a non-crashing run. The real problem here is the timeout in KFileDialog... Christoph: Maybe this should be reassigned to KFileDialog/KIO or is this fixed already?
I have yet to see a backtrace for the crash to decide where the bug is. Also, I am not aware of a timeout issue in KFileDialog. Can you clarify?
I think there is no "crash" just a freezing for about 60 seconds... Unfortunately I have no idea why the KFileDialog is freezing for 60 seconds... and I cannot reproduce it...
@Christoph: As proposed in comment #13, I tried --nofork with gdb, but this option is unknown. It could not be found in gdb's internal help. @Kåre: You are right. I misinterpreted the stalling of skanlite as a crash. It didn't come to my mind that it might be a problem of KDE. When I tested today , the first scan was saved after ~120 seconds. The following scans were saved instantly after pressing 'save' in the dialogue window.
The --nofork parameter is for the application, i.e. when you type "run" in gdb. But now that we understand this is not a crash at all, you do not have to try again; we will never get a backtrace, if there is no crash. I keep this here until I understand where the freeze is. Does the freeze happen before, during, or after the file save dialog shows? Or does it freeze before or after the dialog is closed? Are there any remote folders in the places panel?
Also, please try this in Konsole: kdialog --getsaveurl /path Where /path is the full path that Skanlite shows when showing the file save dialog. If you can reproduce the same freeze, the issue is indeed in the file dialog.
Additionally, whenever you mention a dialog window, please state if you are talking about the scan dialog, or KDE's file save dialog. (sorry for comment spam)
When skanlite has finished the scan, the save dialogue pops up. After I click on 'Save', the dialogue hangs for ~ 120 seconds. So it is the save dialogue. I worked as root and the scan ist finally saved to the default folder - I never changed that. @ Christoph: What do you mean with 'remote folders' in comment 18?, local network folders? I don't have network folders, it's a standalone PC with internet connection.
In addition to comment 21: Skanlite - Settings - Save Location: /root Minseneroog:~ # kdialog --getsaveurl /root Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) Minseneroog:~ #
The problem with the saving of the first scan is also present in openSUSE 13.2. When the scan is finished and the 'save'-dialogue is popped up, you have to wait about two minutes before the first scan is saved. The following scan can be saved without this first 'waitstate'. After closing skanlite and opening it again in the same openSUSE session, the problem with the first saving is back. Will this problem be resolved in near future?
Detlef, we still lack the information about WHEN you see the freeze. Please be precise between which steps the freeze occurs: 1. scan is finished 2. click Save button 3. Save dialog appears 4. Save dialog is filled with contents 5. Enter name 6. Click OK or press Enter 7. Save dialog disappears 8. File is written to disk
And why do you save files to /root? Are you running Skanlite as root user? You should never do this.
Detlef, do you get a freeze with 'kdialog' too? I think the freeze is between 3 and 4. Am I correct? Argh... Why did I not come to think of this before... Can you start Skanlite with gdb and when you get the freeze. In stead of killing it just break and make a backtrace? gdb skanlite run press 'Ctrl+C' int the gdb console bt
Kåre, you are right, the crash comes between steps 3 and 4 as described in comment #24. The save dialogue pops up but cannot be used for about 2 minutes. However, after that time the click on the non responding 'save'-button is accepted and the scan is saved with the default settings (path and filename). Please see my comment #23 again. Only the first attempt to save a scan takes that two minutes. As long as skanlite is not closed the following scans can be saved without delay. I hope that the bug can be fixed now, since gdb with openSUSE 13.2 does not find skanlite an misses a .py file, which I could not find with YaST in an installation package.
Detlef thanks for the report. I know it's been a while since this was filed. Are you able to please test and confirm if this issue is still occurring or if this bug report can be marked as resolved? I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
(In reply to Justin Zobel from comment #28) > Are you able to please test and confirm if this issue is still occurring or > if this bug report can be marked as resolved? I've set the bug status to > "needsinfo" pending your response, please change back to "reported" or > "resolved" when you respond, thanks. I currently cannot use Linux because of a hardware incompatibility. Please set the status as you you consider it appropriate.
As the user can no longer test bug and no other users have commented here or added duplicate bugs I am setting this to resolved.