https://bugs.kde.org/show_bug.cgi?id=365873
--- Comment #4 from Misko <sko...@uns.ac.rs> --- On 12/07/2016 12:14 AM, Johannes Zarl-Zierl wrote: > https://bugs.kde.org/show_bug.cgi?id=365873 > > Johannes Zarl-Zierl <johan...@zarl-zierl.at> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |REMIND > > --- Comment #3 from Johannes Zarl-Zierl <johan...@zarl-zierl.at> --- > Were you able to replicate the bug? > and also on 07/20/2016 10:16 PM: > Does it crash? Is there a window after exit that says something like "Sorry, > the program kphotoalbum closed unexpectedly"? > > Does this always happen on the last mpeg file, regardless of which files you > are viewing, or does it happen on the same video file? Hello, First of all sorry for not responding earlier with this. Yes I just replicated the bug again: Laptop (Wheezy 7.11) running KDE/Openbox: During the first try, the software crashed during Slideshow session - it exited without any window, and did that just at the beginning of the *first* mpg file I have in the ~/Image folder. (By the way, there I have several jpg files that were played in the slideshow completely fine, followed by several mpg files where the problem occurs.) During the second try, the software exited with the window you have mentioned (see the attached snapshot1.png). After clicking on 'Developer Information', I got the snapshot2.png that did not provide much info. Laptop (Wheezy 7.11) running KDE Plasma Workspace: After changing the environment, the crash window was as in the snapshot3.png while the click on 'Developer Information' resulted in snapshot4.png (I copied the whole output in attached KPhotoAlbum.odt). Btw, I used different jpg's & mpeg's content from the one I used few months ago when I discovered the problem for the first time. For example, now they are jpg files ranging 150 kB - 6.5 MB in size (that play well), and mpg files ranging 7-80 MB (that fail). The only difference in between the 1st test and the 2nd test above was that in the 1st test there was no playing any video at all (it failed immediately with the first mpg), while in the 2nd test it played the first 2-3 mpg's fine, and then crashed. That's all for now. Let me know if that helps. When find time I will try to replicate the bug in some other system configurations ... M.S. -- You are receiving this mail because: You are watching all bug changes.
