![]() Registered Member ![]()
|
If I try to open an image in my desktop folder with Gwenview, it locks up. This does not happen in any other folder on my file system, but I cannot seem to figure out what is actually causing this to happen. I've launched gwenview from konsole to see if any useful information comes up there, but I don't seem to be getting anywhere doing that as I've moved the folder it seems to be complaining about yet gwenview still locks up and the suspect folder changes.
Here is the konsole read out when launching gwenview and navigating to my desktop folder.
Any ideas on why this might be happening or how I further debug this? —Thanks. |
![]() Manager ![]()
|
open kdebugdialog -> deselect all -> search for: gwenview -> select it -> ok
then try opening the file and then open in kate ~/.xsession-errors and at the bottom should be any errors found |
![]() Registered Member ![]()
|
Same print out as the one from launching within konsole |
![]() Manager ![]()
|
does the file open ok with other programs such as Okular? or a non-KDE one?
|
![]() Registered Member ![]()
|
yes |
![]() Manager ![]()
|
can you place the image on a pic hosting site where I could access try it
|
![]() Registered Member ![]()
|
The image is not the problem, it's that the file browser component of gwenview is running into an issue indexing (or whatever it does) something on my desktop |
![]() Manager ![]()
|
|
![]() Registered Member ![]()
|
I'm unclear on what file I should be examining |
![]() Manager ![]()
|
sorry I might have gotten confused, its a specific folder and no matter where that folder resides trying to open it in Gwenview freezes Gwenview?
let's go back to your 1st post and retry opening the folder and a file in that folder with gwenview from within Konsole and then again look at ~/.xsession-errors using the command
and
also run the file command from my previous post on that specific folder |
![]() Registered Member ![]()
|
Thanks again for your help and bearing with me!
|
![]() Administrator ![]()
|
Please run Gwenview under a debugger such as gdb, and generate a backtrace. Based on the "Killed" message which is printed to the terminal, I suspect Gwenview could be attempting to exceed resource usage limits (ulimit -a) or is entering into a recursive loop.
A debugger should clarify which of these is the case, or highlight the code which is at fault.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Thanks again for your replies and your patience (especially your patience ![]() I've installed ddd and gdb and attempted to run gwenview though it, but it just informs me that I do not have debugging symbols for it and finishes without launching the app or doing anything useful. |
![]() Administrator ![]()
|
You should be able to install debugging symbols using your package manager - they usually have a -dbg or -debug suffix. For Gwenview, you'll want to get the debugging symbols for Qt and kdelibs as well.
In terms of starting Gwenview in a debugger, I would suggest looking at the information provided at https://wiki.debian.org/HowToGetABacktrace#Running_gdb
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Moderator ![]()
|
Alternatively, you may want to run Gwenview with strace like this:
strace -s 100 gwenview > strace.log 2>&1 and post the generated strace.log file. |
Registered users: Bing [Bot], Evergrowing, Google [Bot], rblackwell