Summary: | digikam doesn't show "big view" | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Michael <m.mickey> |
Component: | Preview-Image | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alinm.elena, caulier.gilles, danielwelch, gsking1, kyle.altendorf, madgenius, marcel.wiesweg, mcguire, ploujj, renda.krell, sts |
Priority: | NOR | ||
Version: | 0.10.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Sentry Crash Report: | |||
Attachments: |
Log of bug occurring
digikamrc that causes this problem another digikam debug log vimdiff SplitterState |
Description
Michael
2008-10-28 11:12:37 UTC
Same thing here. I can add that "Edit" works fine also. This is from SVN about 2 days ago. I guess this is the old splitter problem again... I hate this bug (really!!!), no clue why this is happening all the time. I just looked at the code again, I can't find anything. Try to grab the bottom of the gray area (above the quickfilter bar) and drag it up. You should see a thumbnail bar and the image. Andi I have been trying to hunt down this bug, but I could not because I failed to reproduce it, it just works fine for me now :-( So if either of you did not yet follow Andi's hint and resized the splitter, and can reliably reproduce the problem even after restarting, would you mind sending me your digikamrc file (~/.kde4/share/config/digikamrc) by private mail? Marcel, this bug still happens to me, even with a clean rc file. This is really annoying, but I don't know what is wrong. Also the size of the thumbbar (the splitter?) is not remembered, so after restarting digiKam it takes half the space of the screen so that I have to scale it down all the time. Something is really broken there. *** Bug 173986 has been marked as a duplicate of this bug. *** Andi, I have committed some debugs statements to albumwidgetstack. If you can still reproduce the problem please give us the console output (of starting digikam and opening one image in preview mode). Neither Gilles nor me can currently reproduce this. Created attachment 28428 [details]
Log of bug occurring
(In reply to comment #7) > Created an attachment (id=28428) [details] > Log of bug occurring > First attempt at using this bug system, hopefully I'll end up being more of a help than a hinderance. I was experiencing this trouble with the Kubuntu KDE4 Digikam so I managed to do an SVN compile and it still happened. At least with the SVN version I was able to drag the bar as recommended and the image and filmstrip showed up. They were still there after reopening, so I have not yet replicated this bug with the SVN build except for the once in the attachment. In case I am able to guess at the most relevant lines from the log: digikam(21544) Digikam::AlbumWidgetStackPriv::dumpSplitter: Splitter widgets sizes " are in setPreviewMode" QRect(-101,-1 100x0) QRect(-101,-1 100x91) digikam(21544) Digikam::EventDebugger::eventFilter: Resizing Digikam::ImagePreviewView QSize(533, 0) digikam(21544) Digikam::EventDebugger::eventFilter: Resizing Digikam::ImagePreviewBar QSize(533, 91) *** Bug 175326 has been marked as a duplicate of this bug. *** *** Bug 172730 has been marked as a duplicate of this bug. *** Created attachment 28941 [details]
digikamrc that causes this problem
sredna on IRC gave me this digikamrc file after describing an error similar to the one that this bug is about. After I replaced my digikamrc, I was able to reproduce the blank/grey image display until I move the bottom splitter. I'm using digikam from SVN revision 888644 while sredna was using some 0.10.0-beta2 build from an Arch repository.
Comment on attachment 28941 [details]
digikamrc that causes this problem
Also, note that I ran sed -i 's/anders/plouj/g' ~.kde/share/config/digikamrc/ before using this file.
Created attachment 28942 [details]
another digikam debug log
Just to make sure that I'm dealing with the same problem, here is a log file with similar messages at the end as those in Kyle Altendorf's log.
I got this log by:
- running (a script that sets up my environment and rungs digikam) ./run.sh > digikam.log 2>&1
- changing to the calendar tab
- selecting year 2003
- clicking on one of the thumbnails
Oh man how I hate this bug. It is getting weirder every time I look at this issue. I took the provided digikamrc and moved it to my kde4 folder. Then I used vimdiff to replace my rc file with the one from this bugreport, line by line. After a line had been merged, I started digiKam to see if the splitter problem is solved. But no luck :-( After merging everything, the splitter (the image view) still is not visible, although I practically copied my digikamrc (that worked before) over the broken one. Now I used the "real" copy command to replace my working digikamrc with the broken one, still the splitter is gone. This is really weird, because it worked before, but after using this broken rc file, even my working copy is not showing images anymore. I even restored by digikam database, to see if something has been changed in there, but still no images!!! I will reboot my system now... (the old windows way :-)), maybe it will solve the problem. If this doesn't solve the problem, well... Maybe this value (SplitterState?) is saved somewhere else in the kde4 configuration, not only in digikamrc? Marcel, Gilles, can you confirm this for your system, too? 1. backup digikamrc and digikam4.db 2. copy broken digikamrc file into .kde4/share/config 3. Splitter issue should appear again 4. Merge line by line (or skip it, just replace the broken one with your working digikamrc) 5. Still the splitter issue is reproducible 6. Scratch your head 7. Go crazy like I will do now!!! :-( Andi Wow, this really sucks :-)
My old rc worked fine since 5 months, but since I used the broken rc file attached in here, it isn't anymore.
I copied my formally working rc file into kde4 config folder, started digikam, fixed the splitter and did a diff:
[andi@laptop ~]$ diff digikam-save/digikamrc /home/andi/.kde4/share/config/digikamrc
288c288
< SplitterState=AAAA/wAAAAAAAAACAAAAAAAAAAABAAAAAwAAAAAC
---
> SplitterState=AAAA/wAAAAAAAAACAAAB2gAAAFsBAAAAAwAAAAAC
Funny!
Sure this value has changed, but why was it not working anymore?
I again replaced the digikamrc with my formally working one, the splitter is gone..... ??????????????????
This is too much for me right now, how can the SplitterState work for 5 months, and then become invalid... my rc file worked just 20 minutes ago, and now it is broken? Really... this is too high for me now.
I think I will go outside and build a snowman... :-)
Andi
Created attachment 28945 [details]
vimdiff SplitterState
This screenshot shows the difference between the broken rc file and my currently working one.
I get the same difference when using my formally working digikamrc and a newly generated rc file.
Both times the red part (AAAAAAAAA) seems to be the problem. Maybe this is some invalid code?
Still I don't understand why my formally working rc file is not working anymore.
A quickfix to solve this problem is to delete the SplitterState line in PreviewView.
Andi
Let me make it clear that I also deleted the digikam.db from "Database File Path" each time I tried comparing this broken digikamrc file with working ones. Only after deleting the database everything behaved as expected (broken rc's caused images not to display, while proper rc's allowed images to show properly). *** Bug 176699 has been marked as a duplicate of this bug. *** *** Bug 170340 has been marked as a duplicate of this bug. *** Also happens for me with 0.10.0 beta7. Short progress update: The splitter state from the digikamrc file has stored 0 and 0 as (vertical) size of the preview view and the thumbbar. When this is loaded, both widgets are set as collapsed. Setting the widgets as not collapsible makes them show up. This does not solve the bug because we need to find out why a situation of saving sizes 0,0 (or collapsed widgets) can ever occur. Can't you simply prevent saving and loading 0 values? E.g. when loading, check if the stored values are 0. If they are, fall back to a default. Same when saving: if the values are 0, don't save them to the config. We have this digikamrc here for debugging, but typically this situation occurs when users are starting digikam for the first time. Saving 0,0 values is only secondary to something setting both widgets collapsed. I am investigating into the sizeHint area that Andi pointed to on the ML. Unfortunately I could never reproduce first-startup the problem. How to reproduce the original bug: 1) Remove [PreviewView] SplitterState from your digikamrc 2) Start digikam. 3) Close immediately, do _not_ enter preview mode 4) Start digikam. 5) Enter preview mode and enjoy SVN commit 894943 by mwiesweg: It seems that QSplitter only validly intializes when it has been shown. If the splitter was never shown since application startup and the state is saved at shutdown, invalid values may be saved. If no state was loaded at all (empty SplitterState config), the infamous 0,0 values are stored. Add a flag that stores if the image preview mode was ever entered, and only write splitter state to config if this is the case. CCBUG: 173746 M +15 -5 albumwidgetstack.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=894943 SVN commit 894944 by mwiesweg: Add a workaround for all users who have created an invalid config with the preview-slider bug CCBUG: 173746 M +5 -1 albumwidgetstack.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=894944 I could reproduce the problem and it is now working nicely for me. Closing. Still doesn't fix the issue when converting from KDE3 rc file. Just tested it... Andi What is the difference of an empty config to conversion from KDE3? There is no such setting in KDE3. What can be found in the digikamrc then? Is it fixed for you when deleting the relevant config file line? |