[Powerdevil] [Bug 486250] black lock screen on X11
https://bugs.kde.org/show_bug.cgi?id=486250 Sebastian Kuhne changed: What|Removed |Added CC||sebastian.ku...@mailbox.org --- Comment #1 from Sebastian Kuhne --- I can confirm this behavior. However, I cannot confirm the WiFi-behavior since I am connected to a LAN. I would like to add, that from time to time it is working as expected - but I couldn't find out yet what was the trigger. It seems to be more of a race issue. At the moment I am on Wayland - here it works for me. My system: Operating System: openSUSE Tumbleweed 20240426 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G Memory: 14.6 GiB of RAM Graphics Processor: AMD Radeon R7 Graphics -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423684] Akonadi crashing due to MySQL Socket is gone
https://bugs.kde.org/show_bug.cgi?id=423684 --- Comment #5 from Sebastian Kuhne --- (In reply to Justin Zobel from comment #4) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Hi Justin, I am sorry but meanwhile I moved to Evolution. I have uninstalled all Akonadi and Kontact modules. Best regards Sebastian -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 Sebastian Kuhne changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED --- Comment #16 from Sebastian Kuhne --- I change the status to RESOLVED-WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #15 from Sebastian Kuhne --- (In reply to farid from comment #14) > Can you please provide these files so I can try to reproduce? Hi farid, this topic is quite old, and I have used the workaround described above so far. However, I tried today to reproduce the issue with the current setup: Kdenlive 22.08.0 Operating System: openSUSE Tumbleweed 20220826 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.2-1-default (64-bit) Graphics Platform: X11 Processors: 4 × AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G Memory: 14.6 GiB of RAM Graphics Processor: AMD KAVERI I can say that I was not able to reproduce the failure anymore – the rendering process finished without any issues. So, obviously the issue disappeared, and in my view we can close this topic. Many thanks! Best regards Sebastian -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 Sebastian Kuhne changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #13 from Sebastian Kuhne --- Hi Jean-Baptiste, I need to come back to this issue since I have updated information. If I render a .m2t- file to .mp4 with *Video Settings* - Frame size: 1920 x 1080 (16:9) - Frame rate: 25 fps - Pixel Aspect Ratio: 1 - Colour Space: ITU-R 709 - Interlaced: no all is OK, and there is no crash. If I render the *same* .m2t- file to .mp4 with *Video Settings* - Frame size: 720 x 576 (16:9) - Frame rate: 25 fps - Pixel Aspect Ratio: 1,4 - Colour Space: ITU-R 601 - Interlaced: no the crash occurs. I do not know if we should follow up on this, but it might be reasonable to prevent other users from the same experience. Happy to provide the m2t-file and .kdenlive-file. Let me know how to proceed. Best regards Sebastian -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 Sebastian Kuhne changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #12 from Sebastian Kuhne --- (In reply to Jean-Baptiste Mardelle from comment #11) > Thanks for your report. From the log, I would say that your source video > file is corrupted: > [mpeg2video @ 0x7fcd9819a900] Invalid frame dimensions 0x0 > > Could you try to remux the source file with FFmpeg ? In a terminal, type: > > ffmpeg -i yoursource.m2t converted.mp4 -vcodec copy -acodec copy > > This will create a "converted.mp4" file that might be usable in Kdenlive. > If this does not work you can re-encode it with: > > ffmpeg -i yoursource.m2t converted.mp4 > > This will re-encode the video and should work. To further debug the issue > (probably an upstream problem in MLT), we would need access to the source > file but I guess it's a huge file. So please first try my workarounds. Hi Jean-Baptiste, Many thanks for the advice, and I am sorry that I did not realize that the original file was corrupted. However, your workaround worked perfectly. Obviously there is nothing more to add; I will close this issue and sorry again for the inconveniences. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #10 from Sebastian Kuhne --- Just want to touch base and ask if there is any progress, and if I can further help. I have tested the issue again with Nightly kdenlive-22.03.70-2668251-x86_64.appimage - the issue is still persistent. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 Sebastian Kuhne changed: What|Removed |Added Attachment #144699|ErrorLog|ErrorLog - AppImage description|| -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #9 from Sebastian Kuhne --- Created attachment 144701 --> https://bugs.kde.org/attachment.cgi?id=144701=edit mp4 log - AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #8 from Sebastian Kuhne --- Created attachment 144700 --> https://bugs.kde.org/attachment.cgi?id=144700=edit Screenshot of Scene - AppImage -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #7 from Sebastian Kuhne --- Created attachment 144699 --> https://bugs.kde.org/attachment.cgi?id=144699=edit ErrorLog -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #6 from Sebastian Kuhne --- (In reply to emohr from comment #5) > Thank you for reporting. Difficult to say what happens here. > Please try with the current Kdenlive AppImage version 21.21.0 to see if > there are any packaging issues > https://download.kde.org/stable/kdenlive/21.12/linux/ Many thanks for taking that issue. I tried the current Kdenlive AppImage version 21.21.0 as you proposed. Unfortunately, the same issue appears. I am attaching the same file structure again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed in version 21.12.0
https://bugs.kde.org/show_bug.cgi?id=446886 Sebastian Kuhne changed: What|Removed |Added Summary|Rendering Crashed |Rendering Crashed in ||version 21.12.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #4 from Sebastian Kuhne --- I am attaching several files that hopefully will help to identify the root cause. The files should be self-explaining. Happy to help. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #3 from Sebastian Kuhne --- Created attachment 144486 --> https://bugs.kde.org/attachment.cgi?id=144486=edit mp4 log -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #2 from Sebastian Kuhne --- Created attachment 144485 --> https://bugs.kde.org/attachment.cgi?id=144485=edit kdenlive File -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] Rendering Crashed
https://bugs.kde.org/show_bug.cgi?id=446886 --- Comment #1 from Sebastian Kuhne --- Created attachment 144484 --> https://bugs.kde.org/attachment.cgi?id=144484=edit Screenshot of Scene -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 446886] New: Rendering Crashed
https://bugs.kde.org/show_bug.cgi?id=446886 Bug ID: 446886 Summary: Rendering Crashed Product: kdenlive Version: 21.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: sebastiankuh...@googlemail.com Target Milestone: --- Created attachment 144483 --> https://bugs.kde.org/attachment.cgi?id=144483=edit ErrorLog SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Load *.kdenlive file based on a *.m2t video 2. Start Rendering (mp4) 3. OBSERVED RESULT Rendering crashed after ~about 10% of rendering time EXPECTED RESULT no crash, output mp4 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION There is no crash with Kdenlive 21.08.3 (still available on another computer) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #13 from Sebastian Kuhne --- For confirmation - update 5.22.4. has solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #12 from Sebastian Kuhne --- Many thanks for your efforts. If I understand correctly, there is a commit already, and it should be fixed in 5.22.4. Just to mention, 5.22.4. has not released yet for openSUSE Tumbleweed. Usually the rollout takes some days. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #6 from Sebastian Kuhne --- Yes indeed, I have KSysGuard still installed, and it is working (that leads to my conclusion that actually all sensors are detectable). Well, as you said, I also hope this is all helpful information. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #4 from Sebastian Kuhne --- Here comes what I found: - 'kstatsviewer --list' provides info, so is NOT empty - ksystemstats is not running (checked with 'ps -ax | grep ksystemstats') - start of ksystemstats as user: Stops with message "Segmentation fault (Speicherabzug geschrieben)" - start of ksystemstats as root: Stops with message "kf.dbusaddons: DBus session bus not found. To circumvent this problem try the following command (with bash): export $(dbus-launch)" - Start of 'export $(dbus-launch)' as recommended: No output, no change in the behaviour of ksystemstats -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini
https://bugs.kde.org/show_bug.cgi?id=440261 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #1 from Sebastian Kuhne --- I confirm the same behavior on Operating System: openSUSE Tumbleweed 20210723 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.2-1-default (64-bit) Graphics Platform: X11 Processors: 4 × AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G Memory: 14.6 GiB of RAM Graphics Processor: AMD KAVERI I do not remember exactly what update caused that issue. However, it was working at the introduction of the new "System Monitor". Two notes: - "Total Sensors", "Sensors" and "Text-only Sensors" are empty. Looking for new sensors is failing (search field remains empty) - The old "KSysGuard" is working fine - all sensors seem to be available. Happy to help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #29 from Sebastian Kuhne --- Same problem here on openSUSE Tumbleweed. Login - Logout - Login required to make the battery symbol visible. Operating System: openSUSE Tumbleweed 20200925 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.8.10-1-default OS Type: 64-bit Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426512] Google Tasks - several use cases - synchronization doesn't work properly in Kontact
https://bugs.kde.org/show_bug.cgi?id=426512 Sebastian Kuhne changed: What|Removed |Added Summary|Google Tasks - several use |Google Tasks - several use |cases - synchronization |cases - synchronization |doesn't work properly |doesn't work properly in ||Kontact -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 334480] marking tasks as complete is not synced to google tasks
https://bugs.kde.org/show_bug.cgi?id=334480 Sebastian Kuhne changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=426512 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426512] Google Tasks - several use cases - synchronization doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=426512 Sebastian Kuhne changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=334480 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 426512] New: Google Tasks - several use cases - synchronization doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=426512 Bug ID: 426512 Summary: Google Tasks - several use cases - synchronization doesn't work properly Product: kontact Version: 5.15.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: sebastiankuh...@googlemail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Google account + Google Tasks Android App/Google WebInterface in place, Use of Google Tasks 2. In Kontact/Calendar: Google Groupware activated and set up 3. Apply different uses cases as below OBSERVED RESULT ACTIVITIES IN KONTACT / TASKS - Generate a new task in Kontact/Tasks: OK, synchronized and visible in GoogleAndroidApp and/or GoogleWebInterface - Mark an open task as finished in Kontact/Tasks: OK, synchronized and visible in GoogleAndroidApp and/or GoogleWebInterface - Delete an open task in Kontact/Tasks: NOT OK, NOT synchronized and NOT visible in GoogleAndroidApp and/or GoogleWebInterface - Delete a closed task in Kontact/Tasks: NOT OK, NOT synchronized and NOT visible in GoogleAndroidApp and/or GoogleWebInterface ACTIVITIES IN GOOGLE ANDROID APP - Generate a new task in GoogleAndroidApp/GoogleWebInterface: OK, synchronized and visible in Kontact/Tasks - Delete an open task in GoogleAndroidApp/GoogleWebInterface: OK, synchronized and visible in Kontact/Tasks - Close an open task in GoogleAndroidApp/GoogleWebInterface: NOT OK, NOT synchronized and NOT visible in Kontact/Tasks EXPECTED RESULT - All activities should be synchronized SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200910 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.7-1-default OS Type: 64-bit Processors: 4 × AMD A8-7650K Radeon R7, 10 Compute Cores 4C+6G Memory: 6.7 GiB of RAM Graphics Processor: AMD KAVERI ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 334480] marking tasks as complete is not synced to google tasks
https://bugs.kde.org/show_bug.cgi?id=334480 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 411093] Unable to start Akonadi: Could not open required defaults file
https://bugs.kde.org/show_bug.cgi?id=411093 Sebastian Kuhne changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=423684 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423684] Akonadi crashing due to MySQL Socket is gone
https://bugs.kde.org/show_bug.cgi?id=423684 Sebastian Kuhne changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=411093 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423684] Akonadi crashing due to MySQL Socket is gone
https://bugs.kde.org/show_bug.cgi?id=423684 --- Comment #3 from Sebastian Kuhne --- Additionally worth to be mentioned: I am running akonadi on another computer with openSUSE Tumbleweed: Operating System: openSUSE Tumbleweed 20200717 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.15.0 Kernel Version: 5.7.7-1-default On that computer there is NO issue with akonadi. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423684] Akonadi crashing due to MySQL Socket is gone
https://bugs.kde.org/show_bug.cgi?id=423684 --- Comment #2 from Sebastian Kuhne --- Created attachment 130272 --> https://bugs.kde.org/attachment.cgi?id=130272=edit akonadictl start log -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 423684] Akonadi crashing due to MySQL Socket is gone
https://bugs.kde.org/show_bug.cgi?id=423684 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #1 from Sebastian Kuhne --- I experience the same with KDE Neon: Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 Kernel Version: 4.15.0-111-generic The issue disappears after deleting all *akonadi* files in $HOME/. However, after some new boots (max. three) the issue is back. Also I tried to reinstall all Akonadi and Kontact modules - no success, same behavior. Help is needed please. Happy to support! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #51 from Sebastian Kuhne --- Hi Daniel, many thanks for taking care. I am sorry for my clear words now but I hope my statements aren't too hurtful. If you defined yourself as responsible maintainer for the KDE PIM - Goggle interface, the statement not having time to take care is frightening. Many people using this piece of KDE software trusting that someone is taking care. If you are no longer willing to support this topic someone else should be assigned as responsible person. However, I can understand your frustration with Google's policies but this should not lead to a situation as we are facing it right now. Thanks again, Sebastian -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #20 from Sebastian Kuhne --- Many thanks - #203 is working fine now. I am happy to help further, for example with tests on my low/mid-end machines (performance issue?) - let me know if this is something you need. I leave it with you to close this thread or to keep it open until the next formal revision. Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #17 from Sebastian Kuhne --- Please have a look to the clip attached - I have used another machine with KDE Neon, same kdenlive-19.04.2d-x86_64.appimage and the same video as shared yesterday. The thumbnails to the right of the cut are again not displayed. That said I think we can exclude any GPU issues. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #16 from Sebastian Kuhne --- Created attachment 120855 --> https://bugs.kde.org/attachment.cgi?id=120855=edit Clip -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #15 from Sebastian Kuhne --- Indeed, that's strange. I have no idea. What I can say is that I have not intentionally disabled GPU capabilities. Let me check this on an alternative laptop with KDE neon standard installation and settings (and not with openSUSE Tumbleweed as I during that experiment). I will use the same Kdenlive version, and the same video. Unfortunately, can do it by tomorrow morning only. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #13 from Sebastian Kuhne --- The 21.5MiB is just the size. I sent a dropbox link 1 minute ago. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #11 from Sebastian Kuhne --- Ok, tested with kdenlive-19.04.2d-x86_64.appimage again: - Used a short mp4 clip (about 8 sec, 21 Mib) - track thumbnails -> all frames - Zoom into max level somewhere in the middle of the clip --> All thumbnails are shown (OK) - Cut the clip with the razor tool somewhere in the middle --> The thumbnails to the right of the cut are again *not* displayed I just submitted three screenshots (clip loaded, max zoom level, after cut). Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #10 from Sebastian Kuhne --- Created attachment 120833 --> https://bugs.kde.org/attachment.cgi?id=120833=edit Screen shot: Loading short clip with max zoom and cut -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #9 from Sebastian Kuhne --- Created attachment 120832 --> https://bugs.kde.org/attachment.cgi?id=120832=edit Screen shot: Loading short clip with max zoom -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #8 from Sebastian Kuhne --- Created attachment 120831 --> https://bugs.kde.org/attachment.cgi?id=120831=edit Screen shot: Loading short clip without zoom -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #6 from Sebastian Kuhne --- Thanks again for your help. I didn't know the menu you described yet - it is probably new in 19.XX. It seems to work anyway, even if I have to say that the computer performance requirements have obviously increased. This leads to crashes and the computer stops responding, at least on my computer, and this did not happen before in 18.XX. Then, I found another inconsistency. If I switch on all thumbnails frames (Right click on the track header -> track thumbnails -> all frames) and then perform a cut somewhere in the middle of the video by using the Razor tool, then the thumbnails to the right of the cut are again not displayed. This is a little strange, and I don't know if this makes sense. Otherwise I would say, we can close this thread here since the actual issue has been solved. What is your opinion? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #5 from Sebastian Kuhne --- Obviously, that changed the behaviour. Now, I can see the single thumbnails which is great news. However, using that setting my computer crashed several times with a 3GB m2t file (it never crashed with 18.xx version before). Please let me investigate that further - I will come back to you. Many thanks so far! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #3 from Sebastian Kuhne --- Created attachment 120799 --> https://bugs.kde.org/attachment.cgi?id=120799=edit Screen shot -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 --- Comment #2 from Sebastian Kuhne --- Very good idea. I did the run with kdenlive-19.04.2d-x86_64.appimage Unfortunately, the issue still persists. Attached a screenshot of what I see. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 408556] New: In the timeline, video thumbnails are not visible by using the highest zoom level
https://bugs.kde.org/show_bug.cgi?id=408556 Bug ID: 408556 Summary: In the timeline, video thumbnails are not visible by using the highest zoom level Product: kdenlive Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: sebastiankuh...@googlemail.com Target Milestone: --- SUMMARY In the timeline, video thumbnails are not visible by using the highest zoom level STEPS TO REPRODUCE 1. Start Kdenlive with no project 2. In project bin, add clip (.mp4) 3. Move clip to the timeline 4. Click into the timeline (somewhere) 5. Zoom ip to zoom level 21/21 6. "show video thumbnails" is checked. OBSERVED RESULT No single video thumbnails visible since version 19.xx EXPECTED RESULT Single video thumbnails visible as it was in Version 18.xx SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE NEON 5.15 and/or openSUSE Tumbleweed KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION All Kdenlive settings are on default. Hope someone can confirm that behavior to ensure that I am not misuse something. Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380292] akonadi_imap_resource crash trying to modify IMAP account in kmail
https://bugs.kde.org/show_bug.cgi?id=380292 Sebastian Kuhne <sebastiankuh...@googlemail.com> changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #2 from Sebastian Kuhne <sebastiankuh...@googlemail.com> --- And probabaly a duplicate of #379548. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379548] IMAP resource crashes on configure operation
https://bugs.kde.org/show_bug.cgi?id=379548 Sebastian Kuhne <sebastiankuh...@googlemail.com> changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #8 from Sebastian Kuhne <sebastiankuh...@googlemail.com> --- I am on openSUSE Tumbleweed (latest update), with KDE applications 17.04. I am facing the same issue. Once generated an IMAP resource in KDE's Kontact it can't be configured properly. The same happens using aconadiconsole (Agents --> IMAP resource --> Configure --> Configure Natively) - no window opens for configuration. The IMAP resource; however, is a standard Google mail account. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373111] Crash During Start Up After Login
https://bugs.kde.org/show_bug.cgi?id=373111 --- Comment #7 from Sebastian Kuhne <sebastiankuh...@googlemail.com> --- It seems that KDE Applications 16.12 stabilize the system. I have not recognized any further plasmashell crashes after the update. It would be great if someone else could confirm that the issue is vanished, then we should close this bug thread. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373111] Crash During Start Up After Login
https://bugs.kde.org/show_bug.cgi?id=373111 --- Comment #6 from Sebastian Kuhne <sebastiankuh...@googlemail.com> --- I am fully updated with Tumbleweed, and the issue is still persistent. It is hard to reproduce the issue but I am quite sure it is related to Akonadi. If I send an email via Kontact/IMAP/googlemail the Shell crashes. The only workaround I found after the crash is to stop the shell via 'killall plasmashell' and to restart with 'kstart plasmashell'. That is working but is of course not nice to handle. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373111] Crash During Start Up After Login
https://bugs.kde.org/show_bug.cgi?id=373111 Sebastian Kuhne <sebastiankuh...@googlemail.com> changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #4 from Sebastian Kuhne <sebastiankuh...@googlemail.com> --- I can confirm the same issue. To my knowledge this is new with 5.8.4. Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 Sebastian Kuhne <sebastiankuh...@googlemail.com> changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #15 from Sebastian Kuhne <sebastiankuh...@googlemail.com> --- I have a similar issue reported to openSUSE bugzilla already (https://bugzilla.opensuse.org/show_bug.cgi?id=1008797) I am running openSUSE tumbleweed, Plasma 5.8.3, KDE Framework 5.27.0, QT 5.7.0. Maybe my analysis helps in the finding of the issue: - If I enable standard calendar applet with default settings, everything is ok. - If I enable "PIM events Plugin" only in "Settings", the applet crashes and also plasmashell crahes. - If I additionally enable in the settings "PIM events Plugin" a certain number of calendars synchronized with google calendar in PIM everything is fine again. Again, I know this is not exactly the same behaviour as described in the original thread but maybe it helps to understand the issue. -- You are receiving this mail because: You are watching all bug changes.