[konsole] [Bug 444136] New: Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen
https://bugs.kde.org/show_bug.cgi?id=444136 Bug ID: 444136 Summary: Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen Product: konsole Version: 21.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ericrfonta...@hotmail.com Target Milestone: --- Created attachment 142686 --> https://bugs.kde.org/attachment.cgi?id=142686=edit how Konsole looks when I reopen it SUMMARY Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen. STEPS TO REPRODUCE Glitch happens when I have konsole's "Remember Window Size" checked in preferences (as is default), but doesn't happen if I unchecked that setting. I have a 3-monitor setup*: - Screen 0: DP 1080x1920 (vertical orientation on right) - Screen 1: HDMI 1280x1024 (on left) - Screen 2: DVI-D 2560x1600 (primary in middle, with panel) The first time I opened Konsole, it is fine. However upon reopening it, the glitch happens... OBSERVED RESULT When konsole is closed, the file .config/konsolerc is created with what I believe are buggy settings: [Desktop Entry] DefaultProfile=Profile 1.profile [MainWindow] DVI-D-0 DisplayPort-0 HDMI-A-0 XPosition 2560x1600=2269 DVI-D-0 DisplayPort-0 HDMI-A-0 YPosition 2560x1600=29 RestorePositionForNextInstance=false State=/wD9BTcYBAQICPwBAgIWAG0AYQBpAG4AVABvAG8AbABCAGEAcgEA/wAAHABzAGUAcwBzAGkAbwBuAFQAbwBvAGwAYgBhAHIBAAAFD/8AAA== StatusBar=Disabled ToolBarsMovable=Disabled At this point if I open konsole again, its window height is very short...can only see about half a row of the terminal (see attached konsole-resize.png). However if I delete that konsolerc file before opening konsole again, it displays fine. So the bug seems to be in how this file is saved when I have my particular monitor setup. *for reference here is output of xrandr (which I configured using KDE's Display Configuration gui) so you know exactly my screen settings: Screen 0: minimum 320 x 200, current 4920 x 1920, maximum 16384 x 16384 DisplayPort-0 connected 1080x1920+3840+0 left (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00*+ 59.94 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1440x900 59.89 1280x800 59.81 1152x864 75.00 1280x720 60.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6760.0059.94 720x400 70.08 HDMI-A-0 connected 1280x1024+0+576 (normal left inverted right x axis y axis) 375mm x 300mm 1280x1024 60.02*+ 75.02 1920x1080 60.0050.0059.94 1280x800 60.02 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 DVI-D-0 connected primary 2560x1600+1280+0 (normal left inverted right x axis y axis) 641mm x 401mm 2560x1600 59.86* 1280x800 59.91 EXPECTED RESULT Konsole remembers my window size. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.23 User Edition (fresh install https://files.kde.org/neon/images/user/20211014-1524/neon-user-20211014-1524.iso) on Linux v5.11.0-38-generic (#42~20.04.1-Ubuntu SMP Tue Sep 28 20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I login to KDE plasma with X as is the default, not wayland. I can work around the bug by simply disabling that checkmark in preferences to remember window size. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #4 from Eric Fontaine --- Created attachment 142646 --> https://bugs.kde.org/attachment.cgi?id=142646=edit New crash information added by DrKonqi plasmashell (5.23.1) using Qt 5.15.3 - What I was doing when the application crashed: did another update and reboot and same crash -- Backtrace (Reduced): #4 0x7f50a87647c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x55a2ddf09ee0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #5 0x7f5103ced380 in QQuickWindowPrivate::updateDirtyNode (this=0x55a2db25e880, item=0x55a2ddf09ee0) at items/qquickwindow.cpp:3872 #6 0x7f5103cedc3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x55a2db25e880) at items/qquickwindow.cpp:3617 #7 0x7f5103cef330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x55a2db25e880) at items/qquickwindow.cpp:524 #8 0x7f5103c8ce97 in QSGRenderThread::sync (this=this@entry=0x55a2dc63f8a0, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #3 from Eric Fontaine --- Created attachment 142645 --> https://bugs.kde.org/attachment.cgi?id=142645=edit New crash information added by DrKonqi plasmashell (5.23.1) using Qt 5.15.3 - What I was doing when the application crashed: did another update and rebooted and got the same exact crash when mousing over the bottom panel on my fresh 23.1 install. -- Backtrace (Reduced): #4 0x7ff9501647c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x55fd51b251b0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #5 0x7ff98c694380 in QQuickWindowPrivate::updateDirtyNode (this=0x55fd4ec3bed0, item=0x55fd51b251b0) at items/qquickwindow.cpp:3872 #6 0x7ff98c694c3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x55fd4ec3bed0) at items/qquickwindow.cpp:3617 #7 0x7ff98c696330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x55fd4ec3bed0) at items/qquickwindow.cpp:524 #8 0x7ff98c633e97 in QSGRenderThread::sync (this=this@entry=0x55fd4efcf930, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #2 from Eric Fontaine --- Created attachment 142643 --> https://bugs.kde.org/attachment.cgi?id=142643=edit New crash information added by DrKonqi plasmashell (5.23.1) using Qt 5.15.3 - What I was doing when the application crashed: same thing I did in my last crash, though I had now installed updates and rebooted. It seems the botttom panel is cursed somehow. -- Backtrace (Reduced): #4 0x7f271818f7c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x559e27ab2eb0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #5 0x7f2766d76380 in QQuickWindowPrivate::updateDirtyNode (this=0x559e263124e0, item=0x559e27ab2eb0) at items/qquickwindow.cpp:3872 #6 0x7f2766d76c3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x559e263124e0) at items/qquickwindow.cpp:3617 #7 0x7f2766d78330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x559e263124e0) at items/qquickwindow.cpp:524 #8 0x7f2766d15e97 in QSGRenderThread::sync (this=this@entry=0x559e266ed100, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 Eric Fontaine changed: What|Removed |Added CC||ericrfonta...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #1 from Eric Fontaine --- Created attachment 142641 --> https://bugs.kde.org/attachment.cgi?id=142641=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] New: fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 Bug ID: 444068 Summary: fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button Product: plasmashell Version: 5.23.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ericrfonta...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.1) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-38-generic x86_64 Windowing System: X11 Distribution: KDE neon Testing Edition DrKonqi: 5.23.1 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: fresh install KDE neon testing 23.1, all I had done was setup my 3 monitors with display and add Konsole and chromium to bottom panel. Whenever I press bottom left button, the panel crashes. The crash can be reproduced every time. -- Backtrace (Reduced): #3 0x7f81442b37c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x561d4b2b85a0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #4 0x7f81893da380 in QQuickWindowPrivate::updateDirtyNode (this=0x561d4a012bb0, item=0x561d4b2b85a0) at items/qquickwindow.cpp:3872 #5 0x7f81893dac3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x561d4a012bb0) at items/qquickwindow.cpp:3617 #6 0x7f81893dc330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x561d4a012bb0) at items/qquickwindow.cpp:524 #7 0x7f8189379e97 in QSGRenderThread::sync (this=this@entry=0x561d4a4c6b60, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 Possible duplicates by query: bug 444015, bug 437811, bug 435618, bug 430276, bug 427426. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398121] New: Feature Request: Record new clip directly into timeline track during project playback
https://bugs.kde.org/show_bug.cgi?id=398121 Bug ID: 398121 Summary: Feature Request: Record new clip directly into timeline track during project playback Product: kdenlive Version: 18.08.0 Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ericrfonta...@hotmail.com Target Milestone: --- I would like to be able to record a new video clip directly into a track of the timeline while the rest of the project is playing back. This functionality is built-in to any multi-track audio editor such as Audacity or Ardour. One important consideration is round-trip latency compensation to account for the time that audio/video from playback takes to be heard/seen by computer output plus the time for audio/video input takes to be grabbed by ffmpeg. Then when the clip is recorded, it is shifted back a number of frames corresponding to this round-trip latency. That way the recorded clip will be perfectly in sync to what output the user was responding to. I would be very happy to implement this, as this feature is something I strongly desire as a musician who likes to overdub multiple instruments into a video. Without this feature, I have to record audio into ardour while separately recording video to a file, and then have to import every track into kdenlive to sync with the video files. I'm a contributor to MuseScore, so am familiar with Qt and open-source development. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398118] New: crash when stop record
https://bugs.kde.org/show_bug.cgi?id=398118 Bug ID: 398118 Summary: crash when stop record Product: kdenlive Version: 18.08.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ericrfonta...@hotmail.com Target Milestone: --- Created attachment 114727 --> https://bugs.kde.org/attachment.cgi?id=114727=edit konqi crash report What I was doing when the application crashed: I start kdenlive and select recording to use USB webcam, and press the record button, and see my video being recorded, and then when press record button again to stop, I get this crash. On a fresh install of arch linux running kdenlive 18.08.0, and also happens with self built git build sha 8bda4a1b46b139e7e2ec2e63c3c57eb20dd9f6d7 on refactoring_timeline branch. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 394354] New: scale project resolution
https://bugs.kde.org/show_bug.cgi?id=394354 Bug ID: 394354 Summary: scale project resolution Product: kdenlive Version: 18.04.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: ericrfonta...@hotmail.com Target Milestone: --- This is a feature request to allow user to change the project resolution, and have all the transitions and effects which were expressed in terms of canvas pixels to be scaled appropriately (without scaling the actual clip pixels values). This is distinguished from simply chainging the project resolution currently, which simply leaves the pixel values unmodified. I'd be happy to implement. Additionally would be nice to simply perform this operation in the render window. Currently there is the option to resize, but as far as I can tell that simply performs a resize *after* rendering the frames. But what I want to do is to is to resize *before* rendering the frames. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 386398] Export Project - Feature Request
https://bugs.kde.org/show_bug.cgi?id=386398 Eric Fontaine <ericrfonta...@hotmail.com> changed: What|Removed |Added CC||ericrfonta...@hotmail.com --- Comment #1 from Eric Fontaine <ericrfonta...@hotmail.com> --- I'd find this feature useful too. In addition to sharing, would be useful for simply archiving projects. Note, compressing video files with zip (or gzip or bzip2 for that matter) is not practical because the video files already have very high information entropy, since they are already compressed. So trying to do another compression on them will mostly just eat up CPU cycles. The more important part of this feature request is having all the files together and to have the files be referenced by their relative paths (not absolute paths), from where the kden project file is located. Also maybe there should be an option to include or not include generated proxies, previews, and renders, because depending on the need (e.g. simply transfer to another computer versus archiving) may or may not want all of that. And if not having proxies, then will need to update the project file to indicate that the proxies don't exist. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 392625] "Disable Effect" button very small
https://bugs.kde.org/show_bug.cgi?id=392625 Eric Fontaine <ericrfonta...@hotmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eric Fontaine <ericrfonta...@hotmail.com> --- installing kde plasma desktop and associated things fixes this. Maybe the proper way to resolve this issue is by talking to the arch linux maintainer and request that kdenlive package requests to have some of these particular kde packages installed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 352489] 15.13 git master: MLT processing threads>1 causes (re)positioning playhead to not work any longer
https://bugs.kde.org/show_bug.cgi?id=352489 Eric Fontaine <ericrfonta...@hotmail.com> changed: What|Removed |Added CC||ericrfonta...@hotmail.com --- Comment #16 from Eric Fontaine <ericrfonta...@hotmail.com> --- I'm noting this happens on my machine too (arch linux kdenlive 18.04.1 mlt 6.8.0 on intel i7-6500U), and the workaround of reducing MLT thread count to 1 works. I'm also noting that I can't step through individual frames with right or left keyboard buttons when I have >1 thread, but I can with only 1 thread. I suspect this is related to this issue. I'm also noting that on demanding multi-track videos, that with >1 thread I notice that pressing spacebar to initiate playback will result in playback playing like half a second and then restarting playback a few times (similar to how a CD player would loop when stuck on a bad disc). However on the same video with only 1 thread, the playback won't experience that multiple false start looping problem, but will instead simply take a little bit longer to get rolling. I'm thinking while this might be related to the issue of the playhead not working properly...(maybe the multiple threads send conflicting information about the progress of processing of the start frame, which confuses the playhead cursor). I can't find this issue in the issue tracker...so I'm mentioning it here cause I think might be the same underlying issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 394303] Crash when deleting something in /var folder (for which I don't believe Trash is setup for)
https://bugs.kde.org/show_bug.cgi?id=394303 --- Comment #1 from Eric Fontaine <ericrfonta...@hotmail.com> --- hmm...I can't reproduce now. I opened /var/videos folder again, and this time deleted the same file, and kde does move it to my home's trash folder. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 394303] New: Crash when deleting something in /var folder (for which I don't believe Trash is setup for)
https://bugs.kde.org/show_bug.cgi?id=394303 Bug ID: 394303 Summary: Crash when deleting something in /var folder (for which I don't believe Trash is setup for) Product: dolphin Version: 18.04.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ericrfonta...@hotmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (18.04.1) Qt Version: 5.10.1 Frameworks Version: 5.46.0 Operating System: Linux 4.16.8-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Opened dolphin and navigated to /var/videos (which is a folder when I save a bunch of videos). Then pressed delete on keyboard. - Custom settings of the application: As I mentioned, I don't actually have trash setup for that folder. If I were to use mate's file manager, then the same action of pressing delete will delete those files permanently. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff5ab236800 (LWP 20982))] Thread 3 (Thread 0x7ff588f14700 (LWP 20985)): #0 0x7ff5aaaf7934 in read () from /usr/lib/libc.so.6 #1 0x7ff59b6feed1 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7ff59b6b8ff8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7ff59b6b94c6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7ff59b6b963e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7ff5a4cf3264 in QEventDispatcherGlib::processEvents (this=0x7ff58b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff5a4c9e96c in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7ff5a4acda09 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7ff5a4ad285e in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #9 0x7ff5a013c075 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7ff5aab0653f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7ff591403700 (LWP 20984)): #0 0x7ff5aaaf7934 in read () from /usr/lib/libc.so.6 #1 0x7ff59b6feed1 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7ff59b6b8ff8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7ff59b6b94c6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7ff59b6b963e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7ff5a4cf3264 in QEventDispatcherGlib::processEvents (this=0x7ff584000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff5a4c9e96c in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7ff5a4acda09 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7ff5a511fb56 in QDBusConnectionManager::run (this=0x7ff5a5395080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #9 0x7ff5a4ad285e in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:376 #10 0x7ff5a013c075 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7ff5aab0653f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7ff5ab236800 (LWP 20982)): [KCrash Handler] #6 0x7ff5aa774fcf in KStandardItem::setDataValue(QByteArray const&, QVariant const&) () from /usr/lib/libdolphinprivate.so.5 #7 0x7ff5aa775582 in KStandardItem::setIcon(QString const&) () from /usr/lib/libdolphinprivate.so.5 #8 0x7ff5aae2f63a in ?? () from /usr/lib/libkdeinit5_dolphin.so #9 0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaa7b0, r=0x7ff5ab09e070, this=0x55d6ecdc5aa0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378 #10 QMetaObject::activate(QObject*, int, int, void**) () at kernel/qobject.cpp:3750 #11 0x7ff5aae56190 in ?? () from /usr/lib/libkdeinit5_dolphin.so #12 0x7ff5aae24949 in ?? () from /usr/lib/libkdeinit5_dolphin.so #13 0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaa8c0, r=0x7ff5ab09e070, this=0x55d6ec982fd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378 #14 QMetaObject::activate(QObject*, int, int, void**) () at kernel/qobject.cpp:3750 #15 0x7ff5a90a82fd in ?? () from /usr/lib/libKF5KIOCore.so.5 #16 0x7ff5a4cca450 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8ceaab80, r=0x7ff5a9313400, this=0x55d6ed10e720) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:378 #17 QMetaObject::activate(QObject*, int, int, void**) () at kernel/qobject.cpp:3750 #18 0x7ff5a66386ed in KJob::result(KJob*,
[kdenlive] [Bug 392745] New: transition properties combo-boxes unreadable dark text on black backgrounds
https://bugs.kde.org/show_bug.cgi?id=392745 Bug ID: 392745 Summary: transition properties combo-boxes unreadable dark text on black backgrounds Product: kdenlive Version: 17.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ericrfonta...@hotmail.com Target Milestone: --- Created attachment 111834 --> https://bugs.kde.org/attachment.cgi?id=111834=edit transition properties make them unreadable on arch linux w/ mate. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 392625] New: "Disable Effect" button very small
https://bugs.kde.org/show_bug.cgi?id=392625 Bug ID: 392625 Summary: "Disable Effect" button very small Product: kdenlive Version: 17.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ericrfonta...@hotmail.com Target Milestone: --- Created attachment 111777 --> https://bugs.kde.org/attachment.cgi?id=111777=edit disable effect button too small See attachment of an example of an effects property view. The "Disable Effect" button is too small such that can only read "le". I don't remember this happening on kdenlive on my computer in the past. I'm on Mate Desktop, with most up-to-date repos. about->Kdenlive->libraries says: KDE Frameworks 5.44.0 Qt 5.10.1 (built against 5.10.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland
https://bugs.kde.org/show_bug.cgi?id=386892 Eric Fontaine <ericrfonta...@hotmail.com> changed: What|Removed |Added CC||ericrfonta...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland
https://bugs.kde.org/show_bug.cgi?id=386892 --- Comment #2 from Eric Fontaine <ericrfonta...@hotmail.com> --- Created attachment 108855 --> https://bugs.kde.org/attachment.cgi?id=108855=edit New crash information added by DrKonqi plasmashell (5.11.3) using Qt 5.9.2 I've just reproduced the crash, and this time am using the crash reporting assistant. (Note again I'm on fresh install of Parabola Linux, the FOSS-only version of Arch) -- Backtrace (Reduced): #5 0x7fd62018cc81 in wl_proxy_create_wrapper () at /usr/lib/libwayland-client.so.0 #6 0x7fd60258185a in () at /usr/lib/libEGL_mesa.so.0 #7 0x7fd60256e6df in () at /usr/lib/libEGL_mesa.so.0 #8 0x7fd602bba722 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so #9 0x7fd602bb8bce in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libwayland-egl.so -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386892] Segfault on fresh install of parabola (Arch) linux with kde plasa wayland
https://bugs.kde.org/show_bug.cgi?id=386892 --- Comment #1 from Eric Fontaine <ericrfonta...@hotmail.com> --- I can reproduce with these following steps: 1. Right click panel 2. select "Panel Settings" 3. press the "+ Add Widgets" button at this point the background wallpaper flickers (although all my other applications that are up don't seem to be affected). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386892] New: Segfault on fresh install of parabola (Arch) linux with kde plasa wayland
https://bugs.kde.org/show_bug.cgi?id=386892 Bug ID: 386892 Summary: Segfault on fresh install of parabola (Arch) linux with kde plasa wayland Product: plasmashell Version: 5.11.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ericrfonta...@hotmail.com Target Milestone: 1.0 Created attachment 108853 --> https://bugs.kde.org/attachment.cgi?id=108853=edit backtrace I right clicked on panel and tried to add wiget, then screen briefly flashed, and the error reporter appeared and produced the attached kcrash.txt -- You are receiving this mail because: You are watching all bug changes.
